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-5
Drop Release 2.1 or Release 2.0 Objects
these schemas and all subordinate objects. For complete command syntax and
descriptions, see the SQL/MX Reference Manual.
a. Drop all Release 2.1 or Release 2.0 schemas and their subordinate objects.
Use the DROP SCHEMA schema CASCADE command to drop these
objects:
•
Schemas
•
Tables
•
Views
•
Indexes
•
Constraints
•
Triggers
•
SPJs
•
SQL/MP aliases
b. Drop each Release 2.1 or Release 2.0 catalog by using the DROP CATALOG
command. For complete command syntax and descriptions, See the SQL/MX
Reference Manual.
c. Drop Release 2.1 or Release 2.0 itself by using the DROP SQL command. For
complete command syntax and descriptions, see the SQL/MX Reference
Manual.
2. Remove Release 2.1 or Release 2.0 system modules, user modules, and DDL files
containing SHOWDDL output:
cd /usr/tandem/sqlmx/SYSTEMMODULES
rm *
cd /usr/tandem/sqlmx/USERMODULES
rm *
cd /usr/tandem/sqlmx/ddl
rm *
3. Remove the Release 2.1 or Release 2.0 anchor file.
Note. If you encounter problems using MXCI to drop Release 2.1 or Release 2.0 objects,
you can use the mxtool GOAWAY command instead. For information about this
command, see the SQL/MX Reference Manual.
Note. If the schema is fairly large and contains a very large number of rows, the
DROP SCHEMA command can fail with a 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 need use SCF to
update MaxLocksPerTCB to 10000, minimum. For more information, see the SQL/MX
Reference Manual.
Note. This example uses the system default locations for these files.