RDF System Management Manual

NonStop SQL/MX and RDF
HP NonStop RDF System Management Manual—524388-003
15-12
Offline Synchronization for a Single Partition
Offline Synchronization for a Single Partition
You must first determine the key ranges for each of your partitions.
For the partition that you want to synchronize, find out whether a partition already
exists on the backup system. If a partition exists, then there are two methods to
synchronize the backup partition to the primary: directly and indirectly.
Directly From the Primary to the Backup
1. Delete all rows in the backup partition. If the partition whose rows you want to
delete has the key range of "F"-"J" and the next partition starts with "K", delete
rows from the F-J partition as follows:
DELETE FROM name
WHERE key-column >= 'F' and key-column < 'K';
2. Load the rows from the primary partition into the backup partition (this requires
each catalog to be registered on the other node as described in Step 3 of Creating
NonStop SQL/MX Primary and Backup Databases from Scratch, above):
INSERT INTO backup-table SELECT * FROM primary-table
WHERE key-column >= 'F' AND key-column < 'K';
Indirectly From the Primary to the Backup By Way of a
Temporary File
If the number of rows to load over the network is too great, you can use a temporary
file on the primary system, as follows:
1. Create a temporary catalog on your primary system to correspond to your regular
catalog on your primary system whose objects you want RDF to replicate.
2. Create a temporary schema for your temporary catalog. Follow the instructions
given above in Creating a NonStop SQL/MX Backup Database From an Existing
Primary Database. Note that the name of the temporary schema need not be
identical to the name of the schema whose objects you want replicated, nor must
the subvolume name be identical.
3. Create a temporary table in your temporary schema, including all partitions. Note
that the partition ranges must be identical to those of your primary table. Follow the
guidelines outlined in Creating a NonStop SQL/MX Backup Database From an
Existing Primary Database, above, except that you must create the temporary table
on the primary system and on different volumes from those used for your primary
objects.