Installation Procedures

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 G2 format. The method used depends upon the version of ALLBASE/SQL you are currently running. The version options are:

Updating from G0 or G1 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:

Start ISQL and issue a START DBE statement. This ensures that the DBEnvironment is logically consistent. Type the following:
isql isql=> START DBE 'DBEnvironmentName' isql=> exit

Start SQLUtil and issue the STORE command to backup each DBEnvironment. Type the following:

sqlutil
>>store
WARNING:  If you are using STORE to support RollForward
          .
          .
          .
Do you wish to proceed (y/n)?: y
DBEnvironment Name: DBEnvironmentName
Maintenance Word: MaintenanceWord
To File Name: TAPE




	NOTE: Log files are not stored using this command.

See the ALLBASE/SQL Database Administration Guide appendix, "SQLUtil," for more information.

Backup the ALLBASE/SQL software. Refer to the Release Notes for your current release of ALLBASE/SQL for a complete listing of files.
If you are updating the operating system, make sure you have a backup of the operating system. Refer to the System Administration Tasks HP 9000 for information on how to do a system backup.

Installing the Software

Install the 10.30 version of the HP-UX operating system. Refer to Installing and Updating HP-UX 10.30 for information. If you are not installing a new operating system, omit this step.
Install the G2 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 G0 or G1 Using SQLINSTL

If your release of ALLBASE/SQL is G0 or G1, execute the SQLINSTL script to migrate to the current version G2. ALLBASE/SQL has added new views and modified some existing views. The SQLINSTL script is provided to make it easy for a database administrator to migrate between versions of a release (such as G1.14 to G1.15) or minor releases (such as G1 to G2). Using SQLINSTL ensures that you 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.

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.

Example using SQLINSTL:

HP-UX   /usr/bin/isql
        isql=> start /usr/lib/allbase/hpsql/sqlinstl (mydbe);
        isql=> exit;

Read the SQLINSTL file on your system for more information.

If you are using ARCHIVE MODE LOGGING, you 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.




	NOTE: Customers installing G2 cannot apply rollforward recovery to a backup created using the G0 version (or earlier) of ALLBASE/SQL.

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 G2. A backup of the DBE should be done prior to running SQLMigrate. The procedures below also appear in the ALLBASE/SQL Database Administration Guide (36217-90005).

Use the following procedure to convert a DBEnvironment from E0, E1, or F0 format to the G2 format:

Enter the command:
:sqlmig
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:
SQLMIGRATE=> EXIT;
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.

Installation Procedures

Technical documentation

» Table of Contents

Backing Up your DBEnvironment and Software

Installing the Software

Updating from Versions G0 or G1 Using SQLINSTL

Updating from Versions E0, E1, or F0 Using SQLMigrate