SQL/MP to SQL/MX Database and Application Migration Guide

Falling Back to NonStop SQL/MP
HP NonStop SQL/MP to NonStop SQL/MX Database and Application Migration Guide666211-001
6-2
Steps for Falling Back to NonStop SQL/MP
------------------------------ ------------------ ---------
DEFINITION_SCHEMA_VERSION_1200 NONSTOP_SQLMX_FIGARO \FIGARO
SYSTEM_SQLJ_SCHEMA NONSTOP_SQLMX_FIGARO \FIGARO
SYSTEM_SCHEMA NONSTOP_SQLMX_FIGARO \FIGARO
SYSTEM_DEFAULTS_SCHEMA NONSTOP_SQLMX_FIGARO \FIGARO
MXCS_SCHEMA NONSTOP_SQLMX_FIGARO \FIGARO
DEFINITION_SCHEMA_VERSION_1200 CAT \FIGARO
SCH CAT \FIGARO
DEFINITION_SCHEMA_VERSION_1200 SAMDBCAT \FIGARO
SALES SAMDBCAT \FIGARO
PERSNL SAMDBCAT \FIGARO
INVENT SAMDBCAT \FIGARO
b. Use the DROP SCHEMA schema CASCADE command to drop all SQL/MX
user schemas (highlighted in bold in Step a) and their subordinate objects,
such as:
Tables
Views
Indexes
Constraints
Triggers
SPJs
SQL/MP aliases
For complete command syntax and descriptions, see MXCI Commands in 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 MXCI Commands in 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 3.0 system
catalog. For complete command syntax and descriptions, see SQL Statements
in the
SQL/MX Reference Manual.
Note. If you encounter problems using MXCI to drop SQL/MX objects, use the mxtool
GOAWAY command instead. For information about this command, see SQL/MX Utilities in
the SQL/MX Reference Manual.
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 Subsystem Control Facility (SCF) must be used to update
MaxLocksPerTCB to a minimum of 10000. For instructions, see SQL/MX Statements
in the SQL/MX Reference Manual.