RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

and then load the data into the backup partition using the INSERT statement also described in that
topic.
Correcting Incorrect NonStop SQL/MX Name Mapping
Primary and Backup ANSI Catalog Are the Same
If you created the primary and backup catalogs and used the same name for both, you cannot
use the REGISTER CATALOG command to make either catalog visible on the other system. So you
cannot perform NonStop SQL/MX operations that refer to both catalogs, such as the method for
populating NonStop SQL/MX objects for online database synchronization, nor use more advanced
ANSI name support features in a future release.
To correct the problem:
1. Use the BACKUP utility to store one entire catalog on tape.
2. Drop the entire catalog.
3. Use the RESTORE utility to put the catalog back on disk, but specify a different target catalog
name, taking care that you explicitly map all source Guardian file names to identical targets
using the LOCATION clause.
Alternatively, you can drop the entire catalog, and then recreate it and all dependent schemas
and objects.
Primary and Backup ANSI Schema Names Are Not the Same
If you created the primary and backup schemas to have different ANSI schema names, RDF
replication can proceed, but you must remember that the backup database has a different schema
name in the event of a planned or unplanned outage that requires you resume transaction activity
on the backup system. Furthermore, you will not be able to use more advanced RDF ANSI name
mapping features in subsequent releases of the NonStop SQL/MX product.
If you created the primary and backup schemas to have different names, use BACKUP and RESTORE
to restore the entire schema to a different target schema, similar to the procedure described in
“Primary and Backup ANSI Catalog Are the Same” (page 316). When you issue the RESTORE
command, you must explicitly map all source Guardian file names to identical targets.
Schema Subvolume Names Are Not the Same
If you created the primary and backup schemas to have different subvolume names, underlying
Guardian names for objects in the schemas will not match, and RDF will not replicate correctly.
To correct the problem:
1. Back up the entire schema.
2. Drop the schema, and re-create it using the correct subvolume name.
3. Restore the entire schema. When you issue the RESTORE command, you must explicitly map
all source Guardian filenames to targets that have the corrected subvolume portion.
Guardian Filename Is Incorrect for Partition
You can modify all or any portion of an individual partition's Guardian file name by using the
MODIFY TABLE MOVE PARTITION command.
Consideration for Creating Backup Tables
Currently, you cannot use the CREATE LIKE statement to create backup or temporary tables because
CREATE LIKE does not preserve the original Guardian file names that are essential for RDF.
At some point in the future when ANSI names are supported, CREATE LIKE will be a viable means
of creating backup or temporary tables, but until then the following discussion has the utmost
significance. NonStop SQL/MX will store data in rows on disk in a private format, which does not
316 NonStop SQL/MX and RDF