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

Table 9 Authorization Requirements for Adding Database Objects (continued)
Authorization RequirementsOperation
Adding a trigger can affect up to three schemas, each with its own authorization
requirements:
“Adding Triggers” (page 161)
• The schema where the trigger is created. You must either own this schema or
be the super ID.
• The schema where the subject table exists. You must either own this schema
or be the super ID.
• The schema where the referenced table exists. You must have correct privileges
on the referenced table or be the super ID.
To use the CREATE VIEW statement to add a view, you must have SELECT
privileges for the objects underlying the view and either own the schema where
the view resides or be the super ID.
“Adding Views” (page 161)
Adding Catalogs
To add a catalog, use the CREATE CATALOG statement.
A catalog is owned by the user ID that created it, although catalog ownership does not imply
authorization over schemas or objects in that catalog. Each of the schemas described in a catalog
has an owner. A catalog can contain multiple schemas, each possibly owned by a different user.
A catalog cannot contain other catalogs.
Any user on a node can create a catalog on that node and create a schema in the catalog. Any
user can drop an empty catalog, regardless of who the catalog owner is. Catalog names beginning
with NONSTOP_SQLMX_ are reserved for system metadata and you are not allowed to create or
to drop catalogs with these reserved names.
For more information, see the SQL/MX Reference Manual.
Steps for Adding 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 a name for the catalog you want to add.
3. Ensure your catalog name is unique among existing catalog names on your node.
4. Check whether or not your catalog name is unique across all the nodes in your Expand network
(if applicable).
NOTE: After you have created (registered) your catalog on your node, you will be unable
to register any catalog with the same name from another node (for example, to be able to
access objects in the other catalog from your node).
5. Choose a location for the metadata tables for the catalog. You must choose an audited,
non-SMF DAM disk volume.
6. Enter the CREATE CATALOG statement.
For more information, see “Creating Catalogs” (page 77).
Adding Columns to an SQL/MX Table
To add a column to an SQL/MX table, use the ALTER TABLE statement with the ADD COLUMN
clause.
You can add columns to SQL/MX tables, but not to views or indexes. Each ALTER TABLE statement
adds only one column. To add several columns, use the statement once for each column.
152 Adding, Altering, and Dropping SQL/MX Database Objects