NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
C-128
Considerations—CREATE CATALOG
SECURE "rwep"
specifies security for the new catalog. If you omit the SECURE clause, SQL uses
the default security of the user who creates the catalog. (See Security on page S-11
for more information.)
PHYSVOL volume-name
If ServerWare SMF is installed on your node, specifies a physical volume on which
to place the set of catalog tables. This option overrides ServerWare SMF features.
volume-name can be either the name of a physical volume or equivalent
DEFINE.
This option is available only if you specify a virtual volume and subvolume for
catalog. volume-name must belong to the virtual volume you specify.
Considerations—CREATE CATALOG
•
Authorization requirements
CREATE CATALOG requires authority to write to the SQL.CATALOGS table,
because SQL adds an entry to that table for the new catalog.
The owner of the new catalog is the user whose process created the catalog.
However, the operations allowed on the tables and indexes that make up the catalog
itself (as described under Catalogs
on page C-6) are more limited than those allowed
on ordinary tables and indexes, even for the owner. You can delete catalog tables
only with DROP CATALOG (not even with CLEANUP unless you specify
CLEANUP *,CATALOG;), you cannot partition catalog tables, and you cannot alter
file attributes of catalog tables except for those related to security.
Secure catalogs so that other users who need to access them have appropriate
authority. Users who require write access must have read access as well. Programs
that use objects described in a catalog must have write access to the TRANSIDS and
USAGES tables. For programs to be registered in a catalog, the SQL-compiling
process must have write access to the PROGRAMS, TRANSIDS, and USAGES
tables.
Catalogs can be resecured with ALTER CATALOG. The PROGRAMS,
TRANSIDS, and USAGES tables (but not other catalog tables) can be individually
resecured with ALTER TABLE.
Only one DDL statement can operate on a given SQL object (or partition of an SQL
object) at a time. An error occurs if you attempt to execute a CREATE CATALOG
statement while another process is executing a DDL operation on the same object.
The specific error depends on the DDL operation involved and the phase of the
operation at which the conflict occurs. (See DDL (Data Definition Language)
Statements on page D-19 for more information.)
•
Performance considerations
For better performance when several SQL catalogs are on the same disk volume, the
system administrator should set the disk process cache to an appropriate value with
the Peripheral Utility Program (PUP) SETCACHE command. This strategy is