Reclone services

These services can be used during the software reclone process for Db2® Mirror.

CONFIRM_RECLONED_LIBRARY_DIFFERENCES table function
The CONFIRM_RECLONED_LIBRARY_DIFFERENCES table function returns a row for each replicated object in a library that appears to be different between the two nodes. The differences can be checked for user libraries in SYSBAS or the current IASP, or for all user libraries with tracked entries in the Object Tracking List (OTL) from the most recent software reclone operation.
CONFIRM_RECLONE_SECURITY_OBJECTS view
The CONFIRM_RECLONE_SECURITY_OBJECTS view returns one row for each *AUTL, *FCNUSG, *SECATR, or *USRPRF object that is different from the same object on the other node. Any differences in the security attributes could result in failures when a software reclone is attempted.
EVALUATE_RECLONE_JOURNALED_OBJECTS table function
The EVALUATE_RECLONE_JOURNALED_OBJECTS table function is used prior to a software reclone to identify objects on the copy node which will have journaling ended during the software reclone. A row will be returned for each non-replicated object on the copy node which is journaled to a replicated journal.
EVALUATE_RECLONE_RELATED_OBJECTS table function
The EVALUATE_RECLONE_RELATED_OBJECTS table function returns a row for each non-replicated database object dependent upon a replicated object that will be deleted on the copy node during a software reclone.
EVALUATE_RECLONE_REPLICATION_CRITERIA table function
The EVALUATE_RECLONE_REPLICATION_CRITERIA table function returns a row for each replicated and non-replicated object that will be deleted on the copy node during a software reclone based on any library differences detected for replicated objects that only exist on the copy node.
RECLONE_REPLICATED_OBJECTS procedure
The RECLONE_REPLICATED_OBJECTS procedure forces all replicated objects to be recloned in a Db2 Mirror environment. The procedure is run on the source node of a Db2 Mirror pair when replication is suspended. All replicated objects that exist on the source node are added to the Object Tracking List (OTL) to be saved and then restored on the copy node when replication is resumed. The resynchronization process replaces the replicated objects on the copy node if they already exist.

Parent topic: Db2 Mirror services