SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Falling Back From NonStop SQL/MX Release 2.1 or
Release 2.0
HP NonStop SQL/MX Installation and Management Guide—523723-004
A-7
Install Compatible Versions of Independent Products
°
To view the online help for DIRCHECK, enter $system.zutil.dircheck
help. To view the online help for the DIRCHECK DELETE command, enter
$system.zutil.dircheck help delete.
3. Rebuild the disk free-space table by using the SCF CONTROL DISK $volume,
REBUILDDFS command. For more information about CONTROL DISK, see the
SCF Reference Manual for the Storage Subsystem.
Install Compatible Versions of Independent Products
Independent products required by Release 1.8 are not installed when you install or
reload a previous RVU. You must follow each independent product’s installation
instructions to ensure correct installation.
Start TMF
When you have loaded a previous RVU, start TMF using your site’s established
procedures.
Fall Back SQL/MX Applications and Their User Modules From
Release 2.1 or Release 2.0
For instructions, see Managing Module Files and Their Applications During Fallback
From Release 2.1 or Release 2.0 on page 11-25.
Initialize Release 1.8 (Optional)
If necessary, reinitialize your Release 1.8 database environment by running the
mxinit initialization script from the /usr/tandem/sqlmx/bin directory.
Note that the OSS environment is case-sensitive, so enter the command in the
appropriate case. The mxinit script will re-create the Release 1.8 metadata tables for
use by NonStop SQL/MX if they do not already exist.
1. Log on to the NonStop server by using the super ID (user ID 255,255).
2. Start the OSS shell by entering this command at the TACL prompt:
osh
You are now in the OSS environment. To run mxinit:
a. Change the directory by entering:
cd /usr/tandem/sqlmx/bin
Note. If your Release 1.8 environment is intact (for example, you did not alter or purge the
PROCS and PARAMS tables and SQL/MP MPALIAS and DEFAULTS tables), this step is
unnecessary.