Processing, DBUTLTY and SQL Messages › DBUTLTY Messages (DB1xxxxc) › DB13002W

DB13002W

DATA AT REQUIRED LOCATION DOES NOT MATCH RECOVERY IMAGE

Reason:

CA Datacom/DB encountered some inconsistency in the recovery technique. For example:

• If loading multiple Recovery File tapes, the tapes are probably in the wrong order.
• If attempting to perform forward/backward recovery with RECJOB control statements, the most likely reason that the before/after image in the log record does not match the current database record is that this record was updated by a previous/subsequent job for which no RECJOB was included. In this case, the transaction cannot be recovered/backed out.
• If performing forward recovery using an active system backup and the resource being recovered has RXX data that originated prior to the backup being taken.

RECOVERY prints a hex dump of the log record and the data area location in contention.

Action:

Analyze the image of the database record and the Recovery File record and attempt to determine the cause of contention (see the chapter on using dumps in problem determination in the CA Datacom/DB Database and System Administration Guide). Revise the JCL or RECOVERY option control statements, if in error. If the contention occurred due to an unrecorded UPDAT transaction, rerun the forward/backward recovery either after adding the missing RECJOB card or after removing all RECJOB cards to recover/back out all jobs on the Recovery File affecting the specified tables.