RDF/IMP and IMPX System Management Manual (RDF 1.3+)

Online Database Synchronization
Compaq NonStop™ RDF/IMP and IMPX System Management Manual—522204-001
7-13
Partial Database Synchronization Considerations
Enscribe Alternate Key Files (With or Without Partitions)
There are no special considerations for such files. Use one of the methods described
above for key-sequenced files. Note, however, that if you use the create and load
method, you must use LOAD, not LOADALTFILE.
SQL Tables Without Partitions
Key-sequenced Tables
First create a non-audited duplicate table on the primary system and then load it.
Issue the RDFCOM STOP SYNCH command and then use BACKUP and RESTORE
(or SQLCI DUP) to move the duplicate table to the backup system.
Alternatively, you can use the create and load method to put the duplicate tables directly
onto the backup system, provided you have enough Expand capacity to handle both the
data being loaded and the audit being shipped to the backup system by the extractor.
There are no special considerations for key-sequenced tables with indexes, but see below
for issues regarding the synchronization of indexes.
Relative Tables
No special considerations apply. You can use the same methods described for key-
sequenced tables, above.
SQL Tables With Partitions
The SQL utilities have limitations that make synchronization of individual partitions
more complicated and difficult.
1. SQLCI DUP does not have a PARTONLY option. Therefore, you cannot duplicate
only an individual partition.
2. While BACKUP and RESTORE have the PARTONLY option, if you have backed
up tables from the primary system, you must use the MAP NAMES option when
restoring them on the backup system in order to specify the correct system name.
You cannot, however, include both the MAP NAMES and PARTONLY options in
the RESTORE operation. Therefore, because you must use MAP NAMES, you
cannot restore only a single partition.
Described below is a set of steps that can be used to synchronize individual partitions of
SQL tables (either primary or secondary partitions).
Requirements for Synchronization of Individual Partitions
The following methods work only if all the partitions of a given table still reside on disk
on the backup system. If you do not have all partitions of a given table backed up on
Note. Because the SQLCI LOAD operation generates new SYSKEY values in the backup
table, key-sequenced tables containing SYSKEYs cannot be synchronized online.