SQL/MX 2.x Reference Manual (G06.24+, H06.03+)

SQL/MX Statements

HP NonStop SQL/MX Reference Manual—523725-004

2-124

DROP SCHEMA Statement

Considerations for DROP SCHEMA

Examples of DROP SCHEMA

The DROP SCHEMA statement deletes an SQL/MX schema. See Schemas on

page 6-104.

Syntax Description of DROP SCHEMA

schema

is the name of the schema to drop. If you specify RESTRICT, an error is reported if

the specified schema is not empty. If you specify CASCADE, objects in the

specified schema in addition to the schema itself are dropped. The default is

RESTRICT.

Considerations for DROP SCHEMA

Reserved Schemas

Schema names of the form DEFINITION_SCHEMA_VERSION_ are reserved in all

catalogs for system metadata.

Schema names SYSTEM_SCHEMA and SYSTEM_DEFAULTS_SCHEMA are

reserved, but only in catalogs with a name of the form NONSTOP_SQLMX_. These

schema names are not reserved when used in a user-created catalog. Schemas

named MXCS_SCHEMA in all catalogs are reserved for use by MXCS.

You cannot drop any of these reserved schemas or the objects contained in them.

Authorization and Availability Requirements

To drop a schema, you must own the schema or be the super ID. You must have

remote passwords for any nodes to which the schema’s catalog has been registered.

Transaction Limits on DROP SCHEMA

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.

DROP SCHEMA schema [CASCADE | [RESTRICT]