HP e3000 MPE/iX Release 6.5 System Software Maintenance Manual (30216-90325)

Appendix A 193
Manually Installed Products
Installing ALLBASE/ SQL or IMAGE/SQL
Updating from Version E.1 or F.0
If your old release of ALLBASE/SQL is E.1 or F.0, use SQLMigrate to migrate to version
G.3. Backup the DBEnvironment prior to running SQLMigrate. The steps listed below
also appear in the ALLBASE/SQL Database Administration Guide.
Use the following procedure to convert a DBEnvironment from either an E.1 or F.0 format
to the G.3 format:
1. Prior to updating the operating system and ALLBASE/SQL software, do the following
for each DBEnvironment that will be migrated:
a. Run ISQL.PUB.SYS and issue a START DBE command. This ensures that the
DBEnvironment is logically consistent in the event that it has not been accessed
since a system failure occurred.
b. Run SQLUTIL.PUB.SYS and issue the STORE command to backup each
DBEnvironment.
Log files are not stored using this command. In addition, you should use the SHOWDBE
command to ensure that all parameters are OK.
2. Backup the ALLBASE/SQL software. This can be done as part of the system backup.
3. Update the operating system. The ALLBASE/SQL software is updated as part of the
SUBSYS add-on process.
4. Start SQLMigrate.
:RUN SQLMIG.PUB.SYS
5. For each DBEnvironment that you are migrating, check for potential errors by using
the PREVIEW command below:
SQLMIGRATE=> PREVIEW ' DBEnvironmentName ' FORWARD;
The PREVIEW command is not a read-only command. Make sure that you have a backup
of the DBEnvironment prior to issuing the PREVIEW command.
During the PREVIEW check, you may receive messages indicating that there is
insufficient disk 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;
Note that the syntax of the above 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
6. Issue the MIGRATE command as follows:
SQLMIGRATE=> 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