SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

ManualsBrandsHP ManualsServerHP NonStop G-Series

121

122

123

124

125

126

127

128

129

130

Planning Database Security and Recovery

HP NonStop SQL/MX Installation and Management Guide—523723-004

5-22

Configuring Disk Volumes for RDF

You perform disk volume configuration for RDF as you do for SQL/MX databases. HP

recommends that volume names match exactly on the primary and backup nodes. If

they do not, they can be remapped for RDF with the RDF SET VOLUME configuration

command.

Creating RDF Backup Catalogs

Create RDF backup catalogs with different names from their corresponding primary

node catalogs to enable:

•

Certain database creation and population features to work with the catalog

distribution feature

•

Migration to future releases of NonStop SQL/MX that might involve optional

catalog-to-catalog replication

You cannot define the primary or backup catalogs as remote catalogs on their

respective nodes. That is, you should create primary catalogs on the primary node and

node and register them on the primary node to ensure that each automatic catalog

reference exists on the same nodes as its corresponding database.

For example, if the primary catalog is named CAT, you can create the backup catalog

as CATB:

CREATE CATALOG CATB [LOCATION $DATA03];

Execute this statement on the RDF backup node. The optional location clause

specifies that you place the metadata files on volume $DATA03.

Creating RDF Backup Schemas

SQL/MX schemas are created with a designated subvolume name where all Guardian

files associated with objects in that schema are placed. This subvolume name is stored

in the SCHEMATA.SCHEMA_SUBVOLUME column in the system schema entry for

each user schema.

For example, if the node name is NODE1, this query returns the schema subvolume

name for a schema called CAT.SCH1:

SELECT S.schema_subvolume

FROM nonstop_sqlmx_node1.system_schema.schemata S,

nonstop_sqlmx_node1.system_schema.catsys C

WHERE S.schema_name = ’SCH1’ AND C.cat_name = ’CAT’ AND

S.cat_uid = C.cat_uid;

When you create the schema on the RDF backup node, create it with the same

schema subvolume name as that on the primary node.