RDF/IMP, IMPX, and ZLT System Management Manual

Online Database Synchronization
HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002
7-23
When Is Online Database Synchronization
Complete?
•
If the restart condition occurs after phase 1 has begun, the extractor may choose
to resume at an earlier position than the receiver tells it to. It does this to ensure
that it has handled all committed and aborted transactions correctly. If the
extractor does resume at an earlier position, it logs message 775. Additionally,
regardless of whether or not it adjusted the restart position, the extractor may log
messages 766, 767, and 768 again, even if it had logged any of them prior to the
restart condition.
When Is Online Database Synchronization
Complete?
The following RDF messages assist you in knowing when the various phases of online
database synchronization are complete:
Extractor Messages
Messages 766, 767, and 768 in combination report the completion of phase 1.
Message 782 reports the completion of phase 2. Message 782 indicates that the
extractor has finished its involvement in the online synchronization operation.
Updater Messages
Message 782 reports the completion of phase 2 and indicates that the updater has
finished its involvement in the online synchronization operation. Please note that even
in a partial database synchronization, all updaters will log event 782 because, in a
partial database synchronization, you follow the guildelines of a complete database
synchronization, except that you are only loading the specific volumes, table, and files
you need. Therefore all updaters log the 782 event.
Additionally, the STATUS RDF display has been enhanced to identify which database
volumes are still being synchronized. That information is reported in the error column
of the display. If a volume is still being synchronized, its entry in the error column is
sync. As soon as a volume is successfully synchronized, its entry in the error column
is blank. If an updater encounters an error during synchronization, the associated
entry in the error column is ****.
The following sample display shows that the updater process $MUP1 for the data
volume $DATA1 has successfully completed synchronization while the updater
process $MUP2 for the data volume $DATA2 is still doing the synchronization:
RDF Process Name RTD Time Pri Volume Seqnce Rel Byte Addr Cpus Error
------------------ ----- --------- --- ------- ------ ------------- ----- -----
Monitor $MMON 185 $TRAILS 5 2:3
Extractor (0) $MEXT 0:00 185 $TRAILS 5 7110636 2:3
Receiver (0) $MRCV 0:00 185 $TRAILS 37 806912 1:2
$DATA1 -> $DATA2 $MUP1 0:00 185 $TRAILS 37 806912 1:2
$DATA2 -> $DATA3 $MUP2 1:58 185 $TRAILS 32 712704 1:2 sync