Reason:
When applying an ADDIT transaction during forward recovery, CA Datacom/DB places the added record in the same physical location that it placed it originally after verifying that position's availability. Before applying the current ADDIT transaction, CA Datacom/DB encountered another record in the required location and therefore bypassed the transaction. 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. Revise the JCL or RECOVERY option control statements, if in error.
|
Copyright © 2014 CA.
All rights reserved.
|
|