16 Nonstop Sql/Mx And Rdf; Including And Excluding Sql/Mx Objects; Creating Nonstop Sql/Mx Primary And Backup Databases - HP NonStop RDF J-series RVUs Management Manual

16 NonStop SQL/MX and RDF

RDF supports replication of NonStop SQL/MX user tables (file code 550) and indexes (file code
552). These operations are supported in much the same way as they are with NonStop SQL/MP,
and the same types of data and DDL operations are replicated.
This chapter describes these operations:
•

"Including and Excluding SQL/MX Objects"

• "Creating NonStop SQL/MX Primary and Backup Databases" (page 323)
• "Creating a NonStop SQL/MX Backup Database From an Existing Primary Database"
(page 326)
• "Online Database Synchronization With NonStop SQL/MX Objects" (page 328)
• "Offline Synchronization for a Single Partition" (page 330)
• "Correcting Incorrect NonStop SQL/MX Name Mapping" (page 332)
• "Consideration for Creating Backup Tables" (page 333)
• "Restoring to a Specific Location" (page 333)
• "Comparing NonStop SQL/MX Tables" (page 335)
Given the way the name mapping works between NonStop SQL/MX objects and their underlying
Guardian file names, there are special considerations when setting up NonStop SQL/MX objects
to be replicated by RDF. This chapter describes those issues.
The command interface for NonStop SQL/MX is MXCI.
Including and Excluding SQL/MX Objects
By default, RDF provides volume-level protection, wherein changes to all audited files and tables
on each protected primary system data volume are replicated to an associated backup system
data volume.
RDF also supports subvolume- and file-level replication. To use this capability, you use INCLUDE
and EXCLUDE clauses when configuring updaters to identify specific database objects you want
replicated or not replicated. INCLUDE and EXCLUDE clauses require the use of Guardian names.
If you have an ANSI-named NonStop SQL/MX object that you want to include or exclude, you
first must get the underlying Guardian name by using the MXGNAMES utility or the MXCI
SHOWDLL command. The use of INCLUDE and EXCLUDE clauses is described in
(page 279).

Creating NonStop SQL/MX Primary and Backup Databases

To create a NonStop SQL/MX primary and backup database from scratch, perform these 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 this command creates a catalog named PCAT
on volume $DATA01 on the primary system:
CREATE CATALOG PCAT LOCATION $DATA01;
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 this command creates a catalog named BCAT
on volume $DATA01 on the backup system:
CREATE CATALOG BCAT LOCATION $DATA01;
Including and Excluding SQL/MX Objects
Chapter 11
323