RDF System Management Manual

NonStop SQL/MX and RDF
HP NonStop RDF System Management Manual—524388-003
15-5
Creating NonStop SQL/MX Primary and Backup
Databases from Scratch
Now, the full CREATE TABLE statement for CAT.SCH.TAB1, including the full
Guardian names of the partitions, can be displayed in MXCI by using the
command:
SHOWDDL PCAT.SCH.TAB1;
Assume the system generates the following Guardian file names:
$DATA02.ZSDXYZ3A.KQY8KY00
$DATA03.ZSDXYZ3A.KQY8RK00
$DATA04.ZSDXYZ3A.KQY8YG00
Note that the volumes specified in the LOCATION clauses of the CREATE TABLE
statement are used and that the subvolume is the subvolume created by the
CREATE SCHEMA statement in Step 3.
If you want to specify the complete Guardian filename for your object yourself, you
must use the LOCATION clause specifying the volume on which you want the
object placed and using the Guardian subvolume associated with the object's
schema. The Guardian filename must be exactly eight characters long and end in
"00" (zero-zero).
You cannot specify a volume and subvolume portion without also specifying the
filename. Note that all NonStop SQL/MX partitions for a table must have the same
Guardian subvolume name but the Guardian filename will not normally be the
same, even if the partitions are on different volumes.
7. Create each object on the backup system.
The ANSI name of the object must be constructed as follows:
catalog name: use the name of the backup catalog you created in Step 2.
schema name: use the name you used in Steps 4 and 5.
table or index name: must match on the primary and backup systems.
The following command creates a table called TAB1 in the schema BCAT.SCH,
with three partitions, located on volumes $data02, $data13, $data14, respectively.
CREATE TABLE BCAT.SCH.TAB1 (a int not null, b int, primary key (a))
LOCATION $DATA02.ZSDXYZ3A.KQY8KY00
PARTITION
(ADD FIRST KEY (100) LOCATION $DATA13.ZSDXYZ3A.KQY8RK00,
ADD FIRST KEY (200) LOCATION $DATA14.ZSDXYZ3A.KQY8YG00);
Note that the subvolume.filenames are identical between the primary and backup
systems in this example, but two of the volumes have been remapped for RDF
between the primary and backup systems: $data02 is replicated to $data02, but
$data03 is replicated to $data13 and $data04 is replicated to $data14.
With regard to the Guardian filename, you must use a fully-qualified LOCATION
clause, thereby ensuring that the underlying Guardian subvolume.filenames are
identical on the primary and backup systems; otherwise, the updater will report a
736 event, listing the underlying Guardian subvolume.filename of the object, and