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

Adding, Altering, and Dropping SQL/MX Database
Objects
HP NonStop SQL/MX Installation and Management Guide—523723-004
9-34
Dropping Schemas
•
You must own the schema or be the super ID.
•
You must have remote passwords for any nodes to which the catalog of the
schema has been registered.
The RESTRICT option, by default, will not allow a schema to be dropped if the schema
is not empty of specifications for dependent objects. However, the CASCADE option, if
specified, will drop both the schema and any such dependent objects.
If the schema is fairly large and contains many rows, DROP SCHEMA with the
CASCADE 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. When this occurs, you need to update
MAXLOCKSPERTCB to 10000 or more.
For more information, see the SQL/MX Reference Manual.
Steps for Dropping a Schema
1. Start an MXCI session. Enter a LOG command to initiate a log file for statements
and commands entered in this session. Keep the log for your records.
2. Determine the name of the schema that you wish to drop.
3. Use the DISPLAY USE OF command to identify which user modules are
associated with this object. See the similarity check criteria in the SQL/MX
Programming Manual for C and COBOL and the SQL/MX Programming Manual for
Java to determine if your changes are likely to cause similarly check to fail and
force automatic recompilation. If they will, you should SQL compile these modules
after making the changes to avoid expensive automatic recompilations at run time.
SQL applications that are running while you make these changes will still undergo
automatic recompilation.
For information about explicit and automatic recompilation, see the SQL/MX
Programming Manual for C and COBOL and the SQL/MX Programming Manual for
Java. For information about using DISPLAY USE OF, see Checking Module
Dependencies With DISPLAY USE OF on page 11-20 and the SQL/MX Reference
Manual.
4. Enter the DROP SCHEMA statement.
5. Revise the application source code as needed to reflect your changes to the
database. Process and compile the updated source file. For more information, see
the SQL/MX Programming Manual for C and COBOL and the SQL/MX
Programming Manual for Java.
For more information and examples of dropping schemas, see the SQL/MX Reference
Manual.