RDF System Management Manual for H-Series and J-Series RVUs (RDF 1.9)

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 and NonStop SQL/MX 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
is stored in all image trails by the receiver). All transactions that might have been started during
the create/load or backup operations are now finished.
NOTE: TMP control points are generated as the result of transaction activity. For high rates of
transaction activity, the TMP control points might be only 1 or 2 minutes apart. For lower rates,
they might be 5 to 10 minutes apart. On a completely idle system, TMP control points can be
approximately 30-60 minutes apart. Therefore, if your applications and TMF are idle or nearly
so, it could take an hour or more for the extractor to encounter two TMP control points.
Upon completion of phase 1, part 3, the extractor logs message 768.
Phases of Online Database Synchronization 183