Reason:
All the log data recorded for this transaction cannot be contained in the Log Area. This occurs when the Log Area reaches 100 percent full (or a lower percent when the MUF startup option LOGSPILL is specified with a 'b' option of less than 100) and log records for an active transaction exist in the oldest Log Area block. The transaction reflected by the job name and run unit number has log blocks spilled and is not available for direct transaction backout access.
Note: If the connection by the application to the CA Datacom/DB MUF is not successful, it is possible to see this message with a value of 0 for NUMBER representing the run unit.
This condition is best avoided, when possible, by allocating a larger Log Area or by having the job in question issue interim commits.
This message does not indicate a problem, it is informational. If the transaction being forced to spill were to later fail for any reason and be subject to transaction backout (rollback), then transaction backout would reverse any of the transaction work still on the Log Area. At that time, the actions taken are based upon the MUF startup option RXXROLLBACK.
When RXXROLLBACK is set to NO, the backout stops and issues the DB00103I message indicating completion of the backout. When a return code (RC) of 94(085) is received, it indicates that the backout of the transaction did not complete and the status of the database is now inconsistent relative to the transaction. Some manual effort should be attempted to correct the partial rollback.
When RXXROLLBACK is set to YES, when transaction backout completes backing out the data on the Log Area to a forced checkpoint, it presents the DB00109W message. This message indicates the backout job is waiting to complete.
Action:
Evaluate the program to determine whether it is issuing checkpoints as frequently as needed. If not, modify the program. If the program is issuing checkpoints at a reasonable rate, enlarge the Log Area as follows:
|
Copyright © 2014 CA.
All rights reserved.
|
|