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

name for the -node option. Alternatively, you can use the SHOWDDL command to obtain
the fully qualified filenames of the objects you want replicated and specify the same Guardian
subvol.filenames in the corresponding LOCATION clauses when creating the temporary
objects.
For example, suppose you have a primary table that has two partitions, for which you want
make a fuzzy copy, and the fully qualified Guardian names are:
$DATA01.ZSDABCDE.HWEFGH00
$DATA02.ZSDABCDE.HWEFHJ00
When you create the temporary table, you might list these Guardian names in the LOCATION
clause:
$DATAXX.ZSDABCDE.HWEFGH00
$DATAYY.ZSDABCDE.HWEFHJ00
4. Populate the temporary tables.
INSERT INTO temporary-table SELECT * FROM primary-table;
5. Use BACKUP to put the temporary objects onto tape.
6. Create a catalog on your backup system to correspond to your primary catalog on your
primary system whose objects you want RDF to replicate.
7. Create the schema on the backup node using the same schema name and the same subvolume
name as the schema for your primary database. See “Creating NonStop SQL/MX Primary
and Backup Databases From Scratch” (page 296) for details and an example.
8. 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;
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, this command (if executed on the primary system) registers the primary catalog
on the backup system:
REGISTER CATALOG pcat ON \bnode.$data00;
If executed on the backup system, this command registers the backup catalog on the primary
system:
REGISTER CATALOG bcat ON \pnode.$data00;
9. Use RESTORE to place the temporary objects on the backup system, but specifying the
backup catalog as the target. See “Creating a NonStop SQL/MX Backup Database From an
Existing Primary Database” (page 299) for details. Note that:
• The subvolume.filename of the primary and temporary objects are identical.
• The schema and object names of the primary and temporary objects are identical.
Be sure that when you restore the ANSI names you specify the backup catalog name,
not the temporary catalog name. Also, be sure you use the LOCATION clause to specify
the explicit Guardian subvolume.filenames with the volume names where you
want the objects placed.
The backup database is now ready for RDF replication, and you can drop the temporary
catalog.schema.objects on your primary system.
302 NonStop SQL/MX and RDF