RDF/IMP, IMPX, and ZLT System Management Manual

NonStop SQL/MX and RDF

HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002

15-2

Creating NonStop SQL/MX Primary and Backup

Databases from Scratch

2. Create the catalog on the backup system.

The catalog name must be different from that of the primary catalog.

For example, if issued on the backup system the command

CREATE CATALOG BCAT LOCATION $DATA01;

creates a catalog named BCAT on volume $DATA01 on the backup system.

3. If you want each catalog to be seen from both systems, register your primary and

backup catalogs.

To register the primary catalog on the backup system, issue a REGISTER

CATALOG command on the primary system.

To register the backup catalog on the primary system, issue a REGISTER

CATALOG command on the backup system.

The format of the REGISTER CATALOG command is:

Where catalog is the local catalog, node is the remote system where you want

the local catalog registered, and volume is where the local catalog is to be

registered on the remote system.

For example, the following command (if executed on the primary system) registers

the primary catalog on volume $DATA00 of the backup system:

The following command (if executed on the backup system) registers the backup

catalog on volume $DATA00 of the primary system:

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 the following command (without a

LOCATION clause) creates a schema called PCAT.SCH on the primary system:

CREATE SCHEMA PCAT.SCH;