Correcting Incorrect Nonstop Sql/Mx Name Mapping; Primary And Backup Ansi Catalog Are The Same; Primary And Backup Ansi Schema Names Are Not The Same; Schema Subvolume Names Are Not The Same - HP NonStop RDF J-series RVUs Management Manual

Perform the steps described in
(page 328). In this case, you are only dealing with a single partition. If you create a temporary
table on your primary system, you only need to populate the one partition with the INSERT
statement shown in
If you synchronize the backup partition directly from the primary system, first delete all rows
from the backup partition, as described in
(page 330), 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
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.
332 NonStop SQL/MX and RDF
"Online Database Synchronization With NonStop SQL/MX Objects"
"Offline Synchronization for a Single Partition" (page
"Offline Synchronization for a Single Partition"
330).
332). When you issue the