HP 3000 Manuals HP 3000 Manuals
MIGRATE
Modifies a DBEnvironment to make it compatible with a different release
of ALLBASE/SQL software.
Scope
SQLMigrate Only
SQLMigrate Syntax
MIGRATE 'DBEnvironmentName' {FORWARD [TO 'Version']};
{BACKWARD TO 'Version' }
Parameters
DBEnvironmentName identifies the DBEnvironment to be migrated.
Version indicates the version to which you want to migrate
your DBEnvironment. Version is optional in forward
migration. The default is to migrate the
DBEnvironment to the most recent version supported
by SQLMigrate. Version must be indicated for
backward migration. Use the SHOW VERSIONS command
to determine the value that may be entered as the
version parameter to migrate a DBEnvironment to the
desired release of ALLBASE/SQL software.
Description
* SQLMigrate cannot be used remotely.
* The following message is always displayed:
All stored sections have been invalidated.
Stored sections will be revalidated transparently when they are executed.
Production should be faster if revalidation is done before that time.
Revalidation can be accomplished by preprocessing the application programs
that contain the stored sections.
* When a forward migration completes, SQLMigrate automatically
issues a START DBE NEWLOG statement, unless NEWLOG has been set to
OFF. You cannot connect to the DBEnvironment until the START DBE
NEWLOG statement has been successfully performed.
* At the end of a backward migration, you must perform the START DBE
NEWLOG statement with ISQL. SQLMigrate does not automatically
issue the statement.
* System catalog views often change during migration. If
authorities have been granted or user views have been defined on
system catalog views, then create a schema file with SQLGEN before
the migration. See the GENERATE VIEWAUTH and GENERATE VIEWS
commands in the SQLGEN appendix of this manual for more
information.
* For detailed instructions on how to perform a migration, see
"Using SQLMigrate" in the "DBA Tasks and Tools" chapter of this
manual.
Authorization
You must be the DBECreator or have SM capability to use the MIGRATE
command.
Example 1
In the example below, a forward migration is shown.
SQLMIGRATE=> migrate 'PartsDBE' forward;
WARNING - Before continuing, please verify that a
complete backup of the DBEnvironment exists. (DBWARN 20550)
Do you want to continue (yes,[no]) ? yes
MIGRATE BEGINNING (TUE, AUG 17, 1993, 10:16 AM)
All stored sections have been invalidated.
Stored sections will be revalidated transparently when they are executed.
Production should be faster if revalidation is done before that time.
Revalidation can be accomplished by preprocessing the application programs
that contain the stored sections.
At the end of this processing, the following message is issued:
MIGRATE SUCCEEDED with 1 WARNING(s) (TUE, AUG 17, 1993, 10:17 AM)
SQLMigrate automatically issues a START DBE NEWLOG command and echoes it
to the screen:
START DBE NEWLOG BEGINNING (TUE, AUG 17, 1993, 10:17 AM)
START DBE 'PartsDBE' MULTI NEWLOG
DUAL LOG,
BUFFER = (100,24),
TRANSACTION = 5,
MAXIMUM TIMEOUT = NONE,
DEFAULT TIMEOUT = MAXIMUM,
RUN BLOCK = 37
LOG DBEFILE log1 AND log2 WITH PAGES = 256,
NAME = 'PartsLG1'
AND 'PartsLG2';
START DBE NEWLOG SUCCEEDED (TUE, AUG 17, 1993, 10:17 AM)
The DBEnvironment is ready to be accessed! If you desire archive mode
logging, you must run SQLUTIL and issue a STOREONLINE command.
SQLMIGRATE=>
The previous message applies if you have TurboSTORE software on your
system. If you do not have TurboSTORE, refer to the section "Static
Backup Procedures in Archive Mode" in the "Backup and Recovery" chapter
of this guide.
Example 2
In the example that follows a backward migration is shown.
SQLMIGRATE=> migrate 'PartsDBE' backward to 'F';
WARNING - Before continuing, please verify that a complete backup of
the DBEnvironment exists. (DBWARN 20550)
Do you want to continue (yes,[no]) ? yes
MIGRATE BEGINNING (TUE, AUG 17, 1993, 10:27 AM)
All stored sections have been invalidated.
Stored sections will be revalidated transparently when they are executed.
Production should be faster if revalidation is done before that time.
Revalidation can be accomplished by preprocessing the application programs
that contain the stored sections.
WARNING - Views and stored sections created under later releases of
ALLBASE/SQL may not function correctly under the target version
of ALLBASE/SQL. (DBWARN 20580)
Please drop all views created under later releases, and recreate them.
Also drop all stored sections created under later releases, and either
1) INSTALL backup installable module files that were created under the
target version of ALLBASE/SQL, or
2) Preprocess programs again to obtain stored sections that are compatible
with the target version of ALLBASE/SQL.
At the end of this processing, the following message is issued:
MIGRATE SUCCEEDED with 2 WARNING(s) (TUE, AUG 17, 1993, 10:27 AM)
During backward migration, SQLMigrate does not automatically execute a
START DBE NEWLOG statement.
Please note that you will not be able to use this DBEnvironment until
you have run ISQL and issued a START DBE NEWLOG command. This action will
create a new log file that is compatible with the target release. If you
desire archive mode logging, you must run SQLUTIL and issue a STOREONLINE
command after the START DBE NEWLOG command.
SQLMIGRATE=>
The previous message applies if you have TurboSTORE software on your
system. If you do not have TurboSTORE, refer to the section, "Static
Backup Procedures in Archive Mode," in the "Backup and Recovery" chapter
of this guide.