This applies to ALLBASE/SQL only if you have created SQL data
using an earlier release of ALLBASE/SQL.
If you are updating from an earlier release of ALLBASE/SQL,
you must perform the ALLBASE/SQL migration to migrate your DBEnvironments
to the G.3 format. The method used depends upon the version of ALLBASE/SQL
you are currently running. The version update options are:
Updating from any version of G
Updating from F.0
Updating from versions prior to E.1
CAUTION: Execute SQLINSTL or SQLMigrate to migrate to the
current version of ALLBASE/SQL.
Updating from Any G Version
If your old release of ALLBASE/SQL is G.0, G.1, G.2, or G.3, execute the
SQLINSTL script to migrate to the current version. ALLBASE/SQL
has added new views and modified some existing views to support TurboIMAGE
indexes in IMAGE/SQL. The SQLINSTL script is provided in ALLBASE/SQL
to make it easy
for a database administrator to migrate between versions of a release
(such as G2.01 to G2.03) or minor releases (such as G.2 to G.3).
Using SQLINSTL ensures that you will have access to the most
recent version of the SYSTEM and CATALOG views, and it also
uses VALIDATE FORCE statements to revalidate all stored sections for
the current version of ALLBASE/SQL.
If SQLINSTL is not executed on a DBEnvironment after installing
a new version of ALLBASE/SQL, stored sections may not be properly
revalidated causing run-time errors. Revalidating stored sections
at run-time during production hours can also cause concurrency problems
due to exclusive locks placed on the system catalog. You must execute
SQLINSTL whenever a new version of ALLBASE/SQL is installed
unless you need to use SQLMigrate. SQLINSTL does not need to be
executed if SQLMigrate is being executed to migrate between major releases.
Run the SQLINSTL script as follows:
Please read the SQLINSTL file on your system for more information.
Customers who are using ARCHIVE MODE logging must make a backup of the
DBEnvironment after using SQLINSTL. This backup must be used if
rollforward recovery is to be performed at some point in the future.
Customers installing G.3 cannot apply rollforward recovery to a backup created
using the G.2 version (or earlier) of ALLBASE/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:
Prior to updating the operating system and ALLBASE/SQL software,
do the following for each DBEnvironment that will be migrated:
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.
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.
Backup the ALLBASE/SQL software. This can be done
as part of the system backup.
Update the operating system. The ALLBASE/SQL software is updated
as part of the SUBSYS add-on process.
Start SQLMigrate.
:RUN SQLMIG.PUB.SYS
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
systemDBEFileSet. If this occurs, use the
following commands to create a new DBEFile and add it to
the SYSTEMDBEFileSet:
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
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 DBENEWLOG to create a new log file using the parameters
stored in the DBECON file.
This creates a new log file under the current SQL version. If you
are using ARCHIVE MODE logging, issue the following commands:
isql=> BEGIN ARCHIVE;
isql=> COMMIT ARCHIVE;
Exit ISQL:
isql=> EXIT;
Run SQLUTIL and issue a SHOWDBE command to check
the parameters of the new version of the DBEnvironment. To use
archive mode logging, run SQLUTIL and use the
STOREONLINE command. Issue the SHOWLOG command to
verify that the ARCHIVE MODE is set properly.
Exit SQLUTIL.
isql=> EXIT
DBEnvironment is now ready for access.
Updating from Versions Prior to E.1
If your old release of ALLBASE/SQL is earlier than E.1, you
must perform two updates:
Update to ALLBASE/SQL, release E.1 or F.0
Perform the ALLBASE/SQL migration update to release
G.3 from E.1 or F.0.
Additional ALLBASE/SQL References
For additional information, please refer to the following
ALLBASE/SQL reference materials.
Up and Running with ALLBASE/SQL
ALLBASE/SQL Reference Manual
ISQL Reference Manual for ALLBASE/SQL and IMAGE/SQL