RDF System Management Manual

NonStop SQL/MX and RDF
HP NonStop RDF System Management Manual—524388-003
15-2
Obtaining ANSI Object Names From Updater Event
Messages
Obtaining ANSI Object Names From Updater
Event Messages
Updater event messages list Guardian filenames. If an updater generates an event
against an MX object (subvolume name starts with ZSD), you can obtain the ANSI
name of the object by issuing a FUP INFO <guardian-name> , DETAIL
command.
Creating NonStop SQL/MX Primary and
Backup Databases from Scratch
To create a NonStop SQL/MX primary and backup database from scratch, perform the
following steps:
1. Create the catalog on the primary system.
CREATE CATALOG <catalog_name> LOCATION <optional_Guardian_location>;
For example, if issued on the primary system the command
CREATE CATALOG PCAT LOCATION $DATA01;
creates a catalog named PCAT on volume $DATA01 on the primary system.
For the rest of this procedure assume that the name of the primary system is
\PNODE and the name of the backup system is \BNODE.
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:
REGISTER CATALOG catalog ON node.volume;