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

Falling Back to NonStop SQL/MP
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
12-2
Steps for Falling Back to NonStop SQL/MP
and c.cat_uid=cr.cat_uid
and cr.replication_rule='A';
SCHEMA_NAME CAT_NAME NODE_NAME
------------------------------ ------------------ ---------
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 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.
Note. If you encounter problems using MXCI to drop SQL/MX objects, use the mxtool
GOAWAY command instead. For information about this command, see 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 you must use Subsystem Control Facility (SCF) to update
MaxLocksPerTCB to 10000, minimum. For instructions, see the SQL/MX Reference
Manual.