SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

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 want to drop.
3. Enter the DROP SCHEMA statement.
4. 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.
For more information, see the SQL/MX Reference Manual.
Dropping Sequence Generators
Use the DROP SEQUENCE statement to drop a sequence generator from the current schema.
To drop a sequence generator, you must be the schema owner, super ID or the object owner.
For more information, see the SQL/MX Reference Manual.
Steps for Dropping a Sequence Generator
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 sequence generator that you want to drop.
3. Enter the DROP SEQUENCE statement.
4. 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.
For more information, see the SQL/MX Reference Manual.
Dropping SQL/MP Aliases
Use the DROP SQLMP ALIAS statement to drop an SQL/MP alias from a schema (remove its
mapping from an SQL/MX ANSI name to a physical SQL/MP file name).
The DROP SQLMP ALIAS statement does not cause the underlying SQL/MP object to be dropped.
Similarly, dropping an underlying SQL/MP object does not cause any SQL/MP aliases to be
dropped. Those aliases remain unchanged and orphaned.
For more information, see the SQL/MX Reference Manual.
Steps for Dropping an SQL/MP Alias
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 SQLMP alias that you want to drop.
3. Enter the DROP SQLMP ALIAS statement.
4. 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.
For more information, see the SQL/MX Reference Manual.
174 Adding, Altering, and Dropping SQL/MX Database Objects