RDF System Management Manual for H-Series RVUs (RDF 1.8)

11. Use the BACKUP utility with the PARTONLY option to back up just the partition you need
synchronized to tape (the primary partition, in this example). Remember that the duplicate
table now has the name of the original table. Thus, you now have on tape the loaded partition
that you need to synchronize. Because it has the correct name, you will not need to use MAP
NAMES when you eventually restore it.
12. Rename the duplicate table back to its original duplicate table name ($DATA. TEST.PART
becomes $DATA.DUP.PART).
13. Use SQLCI to drop the duplicate table. By renaming the duplicate table back to its original
name before dropping it, you can preserve whatever indexes exist on the backup system
that are associated with the table being synchronized.
14. Rename the original table on the backup system from its temporary name back to its original
name using the SQLCI ALTER TABLE command ($DATA. TEMP.PART becomes
$DATA.TEST.PART).
15. Use the RESTORE utility with the PARTONLY option to put the loaded primary partition
of the duplicate table into the correct location. MAP NAMES is not required because the
loaded partition now has the correct name on tape and can be restored directly.
16. When the extractor has logged the message indicating it has completed its role in the online
synchronization operation, issue the RDFCOM START UPDATE command on your primary
system.
NonStop SQL/MP Indexes (With or Without Partitions)
To synchronize indexes with or without partitions, do the following:
1. Drop the indexes on the backup system.
2. Create new indexes on the backup system.
You do not use the RDFCOM STOP SYNCH command when you use this method.
Phases of Online Database Synchronization
Online database synchronization, whether for entire databases or selected volumes, occurs in
two phases for both the extractor and all updaters.
Extractor Phases
The extractor phases of online database synchronization are:
Phase 1, Part 1
The extractor has received the STOP SYNCH message (indicating the load or backup operation
is complete) and has reached the first TMP control point record in the audit trail that was generated
after the load or backup operation completed. At this time, the extractor begins building a list
of all transactions that might have been started during the create/load or backup operation.
Upon completion of phase 1, part 1, the extractor logs message 766.
Phase 1, Part 2
The extractor has reached the next TMP control point record in the audit trail and now has a list
of all transactions that might have been started during the create/load or backup operation. The
extractor generates a synch-phase-1-complete record, and then continues its normal
operation.
Upon completion of phase 1, part 2, the extractor logs message 767.
Phase 1, Part 3
When the extractor encounters the next TMP control point record and all of the transactions in
the list have finished, the extractor generates a special synch-complete image record (which
Phases of Online Database Synchronization 169