 |
» |
|
|
|
|  |  |
ALLBASE/SQL is auto-installable. However, if you are updating
from an earlier release of ALLBASE/SQL, you must perform the ALLBASE/SQL
migration to migrate your DBEnvironments to the G4 format. The method
used depends upon the version of ALLBASE/SQL you are currently running.
The version options are: Updating from G0, G1 or G2 using SQLINSTL Updating from E0, E1, or F0 using SQLMigrate Updating from versions prior to E0—contact
your Hewlett-Packard Response Center for procedures if updating
from these old versions.
Backing Up your DBEnvironment and Software |  |
Unless this is a new installation, create a backup of each
DBEnvironment and the ALLBASE/SQL software prior to updating the
operating system and ALLBASE/SQL software. Do the following for each DBEnvironment that will be migrated: Installing the Software |  |
Install the appropriate version of the HP-UX operating system.
Refer to the documentation on Installing and Updating
HP-UX for information. If you are not installing a new
operating system, omit this step. Install the G3 version of the ALLBASE/SQL software.
Refer to "HP-UX SWINSTALL Utility" later in these Release
Notes. If you are updating from an earlier version, proceed
to the appropriate section for your older version.
Updating from Versions E0, E1, or F0 Using SQLMigrate |  |
If your old release of ALLBASE/SQL is E0, E1, or F0, use SQLMigrate
to migrate to version G3. A backup of the DBE should be done prior
to running SQLMigrate. The procedures below also appear in the ALLBASE/SQL
Database Administration Guide. Use the following procedure to convert a DBEnvironment from
E0, E1, or F0 format to the G3 format: Enter the command: For each DBE that is to be migrated, check for potential
errors during the migration by using the PREVIEW command, which follows: SQLMIGRATE=> PREVIEW 'DBEnvironmentName' FORWARD;
|
 |  |  |  |  | NOTE: Make sure that you have a backup of the DBEnvironment
prior to issuing the PREVIEW command since PREVIEW is not a read-only command. |  |  |  |  |
During the PREVIEW check, you may receive messages stating that there
is not enough space in the SYSTEM DBEFileSet. If this occurs, use
the following commands to create a new DBEFile and add it to the
SYSTEM DBEFileSet: SQLMIGRATE=> CREATE DBEFILE DBEFileName
WITH PAGES = DBEFileSize, NAME = 'SystemFileName';
SQLMIGRATE=> ADD DBEFILE DBEFileName TO DBEFILESET SYSTEM;
|
The syntax of these commands is the same as in ISQL. Repeat this step until no errors are encountered and SQLMigrate
returns the following message: The proposed migration should be successful
|
Issue the MIGRATE command as follows: MIGRATE=> MIGRATE 'DBEnvironmentName' FORWARD;
|
When the forward migration has successfully completed, SQLMigrate
purges the old log files and performs a START DBE NEWLOG to create a new log file using the parameters stored
in the DBECON file. This is shown in the following example. START DBE NEWLOG BEGINNING (TUE, JUL 09, 1996, 4:12 PM)
START DBE 'DBENAME' NEWLOG
BUFFER = (100,24),
TRANSACTION = 50,
MAXIMUM TIMEOUT = 3600 SECONDS,
DEFAULT TIMEOUT = 30 SECONDS,
RUN BLOCK = 37
LOG DBEFILE log1 WITH PAGES = 250,
NAME = 'DBELog1';
START DBE NEWLOG SUCCEEDED (TUE, JUL 19, 1996, 4:13 PM)
|
If the START DBE NEWLOG (issued by SQLMigrate) should fail for any reason,
you must run ISQL and issue the START DBE NEWLOG command from ISQL. To enable archive-mode logging, run SQLUtil and
issue the STOREONLINE command. Exit SQLMigrate: Make a backup of the migrated DBEnvironment immediately
after the START DBE NEWLOG statement completes. SQLUtil STOREONLINE
should be used for switching on archive logging and STORE for keeping
up non-archive logging. Start SQLUtil (if you are not already in SQLUtil
from the previous step) and issue the SHOWDBE command to check the parameters of the new version of
the DBEnvironment. Use the ALTDBE command if changes are necessary. Use the SHOWLOG command to display current log information. Exit SQLUtil. The DBEnvironment should be ready
for access.
|