RDF System Management Manual

NonStop SQL/MX and RDF
HP NonStop RDF System Management Manual—524388-003
15-15
Primary and Backup ANSI Schema Names Not the
Same
Primary and Backup ANSI Schema Names 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, above. Note
that when you issue the RESTORE command, you must explicitly map all source
Guardian file names to identical targets.
Schema Subvolume Names 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. Note that 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.