SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

Falling Back to SQL/MX Release 1.8
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
8-5
Load a Previous RVU
For complete command syntax and descriptions, see the SQL/MX Reference
Manual.
c. Use the DROP CATALOG command to drop each SQL/MX user catalog. For
complete command syntax and descriptions, see the
SQL/MX Reference
Manual.
d. If you are using MXCS, uninitialize it before executing the DROP SQL
command. For more information, see the
SQL/MX Connectivity Service
Manual.
e. Use the DROP SQL command to drop the SQL/MX Release 2.x system
catalog. For complete command syntax and descriptions, see the
SQL/MX
Reference Manual.
2. Remove SQL/MX system modules and DDL files containing SHOWDDL output:
cd /usr/tandem/sqlmx/SYSTEMMODULES
rm *
cd /usr/tandem/sqlmx/ddl
rm *
3. Remove the SQL/MX anchor file.
The
InstallSqlmx installation script creates an anchor file that contains the
locations of system metadata tables. This ASCII text file resides in Guardian space
in $SYSTEM.ZSQLMX.MXANCHOR. To remove this file:
a. Log on using the super ID (user ID 255,255).
b. At a TACL prompt, enter:
PURGE $SYSTEM.ZSQLMX.MXANCHOR
Load a Previous RVU
To fall back to a previous RVU, follow the instructions in the G06.nn Software
Installation and Upgrade Guide. SQL/MX Release 1.8 is supported only on G06.18 to
G06.22 RVUs.
Note. If the schema is large and contains many rows, the DROP SCHEMA command
might fail with file system error 35 (“Unable to obtain an I/O process control block, or
the transaction or open lock unit limit has been reached.”). In this case, too many
locks were requested, and you must use the Subsystem Control Facility (SCF) to
update MaxLocksPerTCB to 10000, minimum. For instructions, see the SQL/MX
Reference Manual.
Note. This example uses the system default locations for these files.