Browse Prior Art Database

Migration Simplification and Migration On-the-fly for DB2 (Catalog Changes)

IP.com Disclosure Number: IPCOM000014665D
Original Publication Date: 2001-Jan-01
Included in the Prior Art Database: 2003-Jun-20
Document File: 2 page(s) / 46K

Publishing Venue

IBM

Abstract

This disclosure requires four works/line items as a pre-requisite. Only the last one is completed, the rest are still in queue. Alter table on line change column (ie. alter column and drop column) RECREATE VIEW AS () (referred as 2nd item below) RECREATE VIEW AS () MATCH COLUMNS (referred

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 2

Migration Simplification and Migration On-the-fly for DB2 (Catalog Changes)

This disclosure requires four works/line items as a pre-requisite. Only the last one is completed, the rest are still in queue.

Alter table on line change column (ie. alter column and drop column)

RECREATE VIEW <table_name> AS (<query_expr>) (referred as 2nd item below)

RECREATE VIEW <table_name> AS (<query_expr>) MATCH COLUMNS (referred


1.


2.


3.


4.

The idea is to provide catalog migration via SQL PSM procedure. RDS portion of migration consists of two parts: catalog migration and on disk descriptors migration. This disclosure targets the catalog migration. Catalog migration mainly consists of three steps:

changing the SYSIBM base table;

handling the customer view that is based on SYSIBM base table or SYSCAT view.

as 3rd item below) SQL procedure (PSM) - completed in V7


1.


2.


3.

We can write a PSM procedure to accompany all three of them by using the pre-requisite items 1, 2 , 3 correspondingly. For SYSIBM base table changes, it is a matter of alter column data type or drop the column or add another column. This could be using ALTER TABLE ADD COLUMN, ALTER TABLE DROP COLUMN, ALTER TABLE ALTER COLUMN with some bypass to allow the schema SYSIBM to go through. For SYSCAT view changes, RECREATE VIEW (2nd item) will allow the redefinition of the view completely without touching dependent object. FOR customer view that depends on SYSIBM or SYSCAT, RECREATE VIEW (3rd item) will allow the customer view to be "regenerated" and reusable. Of course, it is up-to-date with respect to the base table/view column definition. Depending on the implement...