Problem:Backout kept ending with a return code of 0 after application abends, but upon restart of the jobs, it kept saying DUPLICATE records. IMS Backout for Indexes having marked as nonrecoverable in DBRC.
Reason:For databases or indexes marked as UNRECOVERABLE in DBRC, if the abending job is using batch DASD logging, and the archiving process has run BEFORE a backout of any type is submitted, check that the backout job does not use the archived log. This is because when the archive process runs, it will discard any changes to databases marked as UNRECOVERABLE, therefore no changes will be undone by the backout process and the database will not be in a state of integrity related to any other databases in the PSB. The database must then be restored using alternative methods, such as a reload or an index rebuild. The backout will complete with a return code of zero (RC=0) even though no changes were made to the UNRECOVERABLE databases.
Solution:After recovering the primary databse run REBUILD index to bring the database and indexes to a sync point.
Follow up : Requested IBM to update the backout process to notify the user that UNRECOVERABLE databases are participating in a backout using an archived DASD log.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment