In conversion Job AL2DCC50 it is executed the Database Export Import utility to import into Datacom/AD tables the export file created by conversion job AL2DCC20.
During conversion job AL2DCC50 execution, frequent CA Datacom DBUTLTY SPILLs are requested if there is a big file to import in Datacom/AD tables, so there is a lot of logging activity which can cause LXX file to fill quickly.
While running this CA Datacom DBUTLTY SPILL job, the error
DB13074E - ACTIVE JOB AL2DCC50 PREVENTING SPILL
can occur and the SPILL job fails, preventing the conversion job AL2DCC50 to complete successfully.
How to correct this problem?
This is the message text for the DB13074E message, as reported in the Datacom DB R14
DB13074E
ACTIVE JOB jjjjjjjj PREVENTING SPILL
Reason:
The SPILL utility function was executed when the log had data, but none was spillable. The job name appears in the message text. This is an error situation and the utility abends.
Action:
Wait to attempt a spill until Multi-User indicates data is spillable.
Since the CA Datacom Log file keeps records based on time, when it is time to spill, the utility will start at the "oldest" block that has not already been spilled, and will spill the log - block by block. This message indicates that the oldest block (or "first" block) eligible to be spilled could not, because some job was still running that had active log records in that block, and the block was held in case the job failed and needed to back out.
If the batch job AL2DCC50 requests a new SPILL too quickly (so before the above DB00104I message is got after the last SPILL) the error DB13074E occurs.
Resubmit the AL2DBSPL job.