SQL/MP Installation and Management Guide

Creating a Database
HP NonStop SQL/MP Installation and Management Guide—523353-004
5-7
Securing Catalog Tables
not explicitly specify a catalog in the CREATE CATALOG statement, SQL/MP creates
the catalog on the current default volume and subvolume.
This example specifies the location of the catalog. The catalog name is the subvolume
name.
>> CREATE CATALOG \SYS1.$VOL1.MFG;
--- SQL operation complete.
You can use a DEFINE name to specify a catalog name. In this example, the catalog is
created on \SYS1.$VOL1.MFG as defined by the DEFINE =MFG. The INFO DEFINE
command displays the DEFINE, showing the actual catalog name.
>> INFO DEFINE =MFG;
DEFINE NAME =MFG
CLASS CATALOG
SUBVOL \SYS1.$VOL1.MFG
>> CREATE CATALOG =MFG;
--- SQL operation complete.
If you are running SQL/MP on a system using the SMF product and you want to ensure
that you can fall back to a non-SMF system, make sure that a given catalog’s tables
reside on one physical volume. If you specify a virtual volume for a catalog, SMF can
distribute the catalog tables among multiple physical volumes in the storage pool.
When this configuration is in place, there is no guarantee that you can return to using a
nonvirtual volume. When you are certain you will not need to fall back to a non-SMF
system, you can specify a virtual volume for a catalog without being concerned with the
physical location of the files.
To ensure that a catalog’s tables reside on one physical volume, you can specify a
direct volume that is not in any storage pool, or you can use the PHYSVOL option, as
follows:
>> CREATE CATALOG $virtual_vol.subvol PHYSVOL $physical_vol;
With the PHYSVOL option, you specify only the volume name. Also, the virtual volume
specified with the CREATE CATALOG clause must be associated with the same
storage pool that contains the physical volume specified with PHYSVOL. For more
information about using this option, see the SQL/MP Reference Manual and the
Storage Management Foundation User’s Guide.
Securing Catalog Tables
When you create a catalog, SQL/MP assigns the catalog ownership to your Guardian
user ID with your default security, unless you specify the SECURE attribute in the
CREATE CATALOG statement.
The catalog tables compose the data dictionary, a vital part of an application’s integrity.
The security of a catalog should protect the data dictionary information from
unauthorized removal or alteration.