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

Table 13 Authorization Requirements for Dropping Database Objects (continued)
Authorization RequirementsOperation
To drop a schema with the DROP SCHEMA statement, you must own the schema or
be the super ID. In a distributed environment, you must have remote password set up
for all nodes where the schema's catalog is visible.
“Dropping Schemas” (page 173)
To drop a sequence generator with the DROP SEQUENCE statement, you must be
the owner of the sequence generator, or own its schema, or be the super ID.
“Dropping Sequence
Generators” (page 174)
To drop an SQL/MP alias with the DROP SQLMP ALIAS statement, you must be the
owner of the schema in which the alias resides or be the super ID.
“Dropping SQL/MP Aliases”
(page 174)
To drop an SPJ with the DROP PROCEDURE statement, you must own the SPJ, or own
its schema, or be the super ID. For more information, see the SQL/MX Guide to
Stored Procedures in Java.
“Dropping SPJs” (page 175)
To drop a table with the DROP TABLE statement, you must be the owner of the table,
or own its schema or be the super ID.
“Dropping SQL/MX Tables”
(page 175)
To drop a trigger with the DROP TRIGGER statement, you must be the owner of the
trigger, or own its schema or be the super ID.
“Dropping Triggers” (page 176)
To drop a view with the DROP VIEW statement, you must be the owner of the view,
or own its schema or be the super ID.
“Dropping Views” (page 177)
Dropping Catalogs
To drop a catalog, use the DROP CATALOG statement.
DROP CATALOG automatically removes all definition schema tables associated with the catalog
and all entries in the system catalog associated with the catalog. All metadata tables for the catalog
must be accessible at the time DROP CATALOG executes.
Before you can drop a catalog, it must be empty. Any user can drop any empty catalog visible on
the local node. No user can drop a nonempty catalog, even if the catalog contains only empty
schemas.
For more information, see the SQL/MX Reference Manual.
Steps for Dropping a Catalog
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 catalog you want to drop.
3. If necessary, use the DROP SCHEMA statement to drop any schemas from the catalog. (See
“Dropping Schemas” (page 173).)
4. Enter the DROP CATALOG statement.
For more information, see the SQL/MX Reference Manual.
Dropping Columns from an SQL/MX Table
You cannot drop a column from an SQL/MX table, view or index directly. To drop a column
indirectly, you must do the following:
• Create a new table, view or index identical to the old one, but without the offending column.
• Copy the contents of the remaining columns from the old table to the new one.
• Drop the old table.
• Then rename the new table to have the name of the old table.
For more information, see the SQL/MX Reference Manual.
170 Adding, Altering, and Dropping SQL/MX Database Objects