DB2 Enterprise LOAD APPEND

[gauravrb]

Hi,

The Load job design

Dataset--->Copy Stage---->DB2 Enteprise (LOAD APPEND method)

The job aborted giving the following error

"SQLCODE = -668; SQLSTATE=57016/tmp Operation not allowed for reason code "3" on table SQLSTATE=57016"

The table was in inconsistent state as the reslut the job aborted giving above reason.

what are the possible reasons the table might make the table go in inconsistent state when loading through datastage by load append method?

Will the cleanup on failure property in load append method help?

If the above property is set to TRUE and failure occurs will it prevent the table from going in to inconsistent state and what will be effect on consistency of data loaded in the table?

[attu]

Reason code = 3 means, check diskspace to run load, database is full, clear the database

[gauravrb]

Reason code = 3 means, check diskspace to run load, database is full, clear the database

Does this mean this process will always need to be done manually when ever such failure occurs.