RDF System Management Manual for H-Series RVUs (RDF 1.8)

4. Create the schema on the primary system.
If you do not use the LOCATION clause, NonStop SQL/MX will set the subvolume itself.
In that case, you must query NonStop SQL/MX to obtain the subvolume name because the
subvolume name is needed when creating the schema on the backup system.
If you specify the LOCATION clause, the subvolume name must start with "ZSD" and the
entire name must be eight characters in length.
For example, if issued on the primary system, this command (without a LOCATION clause)
creates a schema called PCAT.SCH on the primary system:
CREATE SCHEMA PCAT.SCH;
If you omit the LOCATION clause, then, after creating the schema, you must use this query
to obtain the subvolume of the schema (where you fill in the correct node-name,
schema-name, and catalog-name):
SELECT S.schema_subvolume
FROM NONSTOP_SQLMX_node-name.system_schema.schemata S,
NONSTOP_SQLMX_node-name.system_schema.catsys C
WHERE S.schema_name = 'schema-name' AND
C.cat_name = 'catalog-name' AND
S.cat_uid = C.cat_uid;
Node-name is a Guardian system name that excludes the backslash (\).
In this example, the node-name is PNODE, the schema-name is SCH, and the catalog-name
is PCAT.
SELECT S.schema_subvolume
FROM NONSTOP_SQLMX_PNODE.system_schema.schemata S,
NONSTOP_SQLMX_PNODE.system_schema.catsys C
WHERE S.schema_name = 'SCH' AND
C.cat_name = 'PCAT' AND
S.cat_uid = C.cat_uid;
For the rest of this procedure assume that the above query returns the value ZSDXYZ3A.
5. Create the schema on the backup system using the same schema name and the same
subvolume name as on the primary system.
Because RDF is replicating based on the underlying Guardian file locations, you must use
the LOCATION clause. If you specified the LOCATION clause when creating the primary
system's schema, you must use the same subvolume here. If you did not specify the
LOCATION clause when creating the primary system's schema, you must query the primary
system to obtain the Guardian subvolume name, and you must use the Guardian subvolume
name with the LOCATION clause here.
For example, if issued on the backup system, this command creates a schema on the backup
system called SCH in catalog BCAT using subvolume ZSDXYZ3A:
CREATE SCHEMA BCAT.SCH LOCATION ZSDXYZ3A;
6. Create each object (table or index) on the primary system.
The ANSI name of the object must be constructed as follows:
• catalog name: use the name of the primary catalog you created in Step 1.
• schema name: use the name you used in Steps 4 and 5.
• table or index name: whatever ANSI name you choose for the object.
For example, this command creates a table called TAB1 in schema PCAT.SCH, with
three partitions, located on volumes $DATA02, $DATA03, $DATA04, respectively.
CREATE TABLE PCAT.SCH.TAB1 (a int not null, b int, primary key (a))
LOCATION $DATA02
PARTITION ( ADD FIRST KEY (100) LOCATION $DATA03,
ADD FIRST KEY (200) LOCATION $DATA04 );
Creating NonStop SQL/MX Primary and Backup Databases From Scratch 297