SQL/MP Installation and Management Guide

Adding, Altering, Removing, and Renaming
Database Objects
HP NonStop SQL/MP Installation and Management Guide—523353-004
7-36
Renaming Objects
•
Both DROP and PURGE automatically initiate a TMF transaction for the operation
if one has not already been started. You cannot drop or purge a nonaudited object
within a user-defined transaction.
•
Only the DROP statement is valid for purging a constraint or catalog.
•
PURGE enables you to purge shadow labels, as described under Managing
Shadow Disk Labels on page 11-36.
•
Both the DROP statement and PURGE command can be entered interactively
through SQLCI. Only DROP, however, can be used programmatically.
Renaming Objects
You can rename most objects by using an ALTER statement with the RENAME option.
This table lists the objects you can rename and the ALTER statements for renaming.
To rename these objects, use these guidelines:
•
You can rename an object only on the same volume where it already exists.
•
When you rename a table, all associated protection views, shorthand views, and
indexes must be accessible during the renaming so that catalog references can be
altered.
•
When you rename an index, the underlying table must also be accessible so that
catalog references can be altered.
•
When you rename a protection view, the underlying table and indexes must be
accessible so that file-label references can be altered.
•
When you rename a shorthand view, the underlying protection view and table must
be accessible so that catalog references can be altered.
•
When you rename a partitioned table or index, all partitions of that object must be
available. All partitions are automatically renamed.
•
When you rename a collation, all dependent objects must be available so that file-
label and catalog references can be altered.
Object Operation Statement
Table Rename ALTER TABLE
View Rename ALTER VIEW
Index Rename ALTER INDEX
Collation Rename ALTER COLLATION
Constraint (Not Allowed) (Not Applicable)