NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
A-9
Examples—ALTER CATALOG
independently from the other tables in the system catalog. You can use ALTER
TABLE to set the security for SQL.CATALOGS.
•
Relationship between ownership and security
Changing the OWNER attribute of a catalog affects the interpretation of the
SECURE file attribute, because authorization is determined at run time using the
current group and owner.
If another process is using a catalog when the owner changes, the process might not
be able to reaccess the catalog after the change.
Examples—ALTER CATALOG
•
The following statement makes user 201,43 the owner of the catalog named SALES,
gives read and execute authority to all local and remote users, and gives write and
purge authority to all users in group 201:
ALTER CATALOG SALES OWNER 201,43 SECURE "NUNU";
ALTER COLLATION Statement
ALTER COLLATION is a DDL statement that renames a collation or alters security
attributes for a collation.
collation
is the name of the collation to alter (or an equivalent DEFINE). If ServerWare
Storage Management Foundation (SMF) is installed on your node, collation
must be either a virtual or direct name.
RENAME new-name
specifies a new Guardian name (or an equivalent DEFINE) for the object. SQL
changes all references in the catalog to the new name.
OWNER or SECURE
specifies the owner and security for the collation. See OWNER FILE ATTRIBUTE
on page O-10, Security
on page S-11, or SECURE File Attribute on page S-11 for
more information.
Considerations—ALTER COLLATION
•
Authorization requirements
{| RENAME new-name |}
ALTER COLLATION collation {| OWNER group,user |}
{| SECURE "rwep" |}