Kbase P67662: How to migrate one or more tables (partial schema holder) from existing schema holder to a new schem
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
Status: Verified
GOAL:
How to migrate one or more tables (partial schema holder) from existing schema holder to a new schema holder?
GOAL:
How to move a few tables from existing schema holder to a new schema holder?
GOAL:
How do I load definitions for tables into a new schema holder?
FACT(s) (Environment):
DataServers
FIX:
1. Dump a .df from an existing schema holder by choosing one or the tables you want to migrate.
Go to Data Administration -> Dump -> Table definitions -> when the list of tables comes up, select individual tables you need to dump, then dump to a file.
2. Create an empty progress database or connect to existing database. Empty progress database can be created using progress data administration GUI tool or using proenv prompt (in windows, Start > Program > progress > proenv; in UNIX, $DLC/bin/proenv as
prodb <name of the schema holder> empty
3. Connect to the empty progress database created in step 2 as a single user mode. If proenv prompt is used connect to it using the following command:
prowin32 <schema holder name> -1 (Windows GUI client)
_progres <schema holder name> -1 (character client) or
pro <schema holder name> (UNIX single user command)
4. Go to the Data Administration tool in windows or Data Dictionary screen in UNIX > DataServer menu > Select one of the foreign database utilities but not the DB2/400 Utilities > Create DataServer Schema...
5. Create a schema holder supplying all the foreign database connection parameters but the schema holder name can be anything or similar to the one you are moving the table from. When the Pre-selection criteria screen comes up, press cancel to abort the creation of the schema holder.
The step 4 and 5 are to fake out the creation of a schema holder so that the foreign database type is added in the meta schema. These two steps were done to avoid the wrong database type error when the .df is loaded to a new progress database because the df dumped does not contain _db record.
6. While connected to the foreign database after the abort of the creation of the schema holder, choose the Admin menu > Load Data and Definitions > Data Definitions (.df files)... Choose the appropriate .df and load it to the schema holder.