Teradata End loading command issue

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Vinothbaskaran
Participant
Posts: 22
Joined: Mon Aug 25, 2008 4:01 am

Teradata End loading command issue

Post by Vinothbaskaran »

Hi,

The issue is regarding the datastage parallel jobs not failing despite reporting fatal errors after the fast load. The job has finished writing orchestrate load summary but the end loading and collect stats issued by datastage has failed because "Too many END TRANSACTION statements". Although these were fatal errors on datastage, the job did not abort. The only reason that i could think of the successful completion of the job is that it did not recieve any CLI error.

The error messages are below (time-wise):

Error msg 1:

tr_load,0: APT_TeraWriteSubOperator:DB Call Failure(success check) Info = 0, Code = 2631, Message = Transaction ABORTed due to Deadlock.
DBCAREA msg_txt: Completed successfully.
CLI Error Message: Completed successfully.
APT_TeraWriteSubOperator:ExecuteImmediate failed for 'END LOADING'. Error Code = 2631
DBCAREA msg_txt: Completed successfully.
CLI Error Message: Completed successfully.
APT_TeraWriteSubOperator: END LOADING failed for 'END LOADING'.
APT_TeraWriteSubOperator:DB Call Failure(success check) Info = 0, Code = 3510, Message = Too many END TRANSACTION statements.
DBCAREA msg_txt: Completed successfully.
CLI Error Message: Completed successfully.
APT_TeraWriteSubOperator:ExecuteImmediate failed for 'ET'. Error Code = 3510
DBCAREA msg_txt: Completed successfully.
CLI Error Message: Completed successfully.
APT_TeraWriteSubOperator: END TRANSACTION failed

Error msg 2

tr_load,0: TeraGenericQuery Error: DB Call Failure(success check) Info = 0, Code = 2652, Message = Operation not allowed: GRID_WORK.CC_Agrmnt_Indicators_T0 is being Loaded. Session return code = 2,652 , DBC return code = 0
DBC message: Completed successfully.
TeraGenericQuery Error: DB Call Failure(success check) Info = 0, Code = 2652, Message = Operation not allowed: GRID_WORK.ERR_872082297_1 is being Loaded. Session return code = 2,652 , DBC return code = 0
DBC message: Completed successfully.
TeraGenericQuery Error: DB Call Failure(success check) Info = 0, Code = 2652, Message = Operation not allowed: GRID_WORK.ERR_872082297_2 is being Loaded. Session return code = 2,652 , DBC return code = 0
DBC message: Completed successfully.

Error msg 3

tr_load,0: TeraUtils:DB Call Failure(success check) Info = 0, Code = 2652, Message = Operation not allowed: GRID_WORK.CC_Agrmnt_Indicators_T0 is being Loaded.

Error msg 4

tr_load,0: TeraUtils:ExecuteImmediate failed for 'COLLECT STATISTICS ON GRID_WORK.CC_Agrmnt_Indicators_T0'. Error Code = 2652


Can anyone of you please let us know the reason why the job has not aborted?
Vinothbaskaran
Vinothbaskaran
Participant
Posts: 22
Joined: Mon Aug 25, 2008 4:01 am

Post by Vinothbaskaran »

Any replies/ideas gents :D ?
Vinothbaskaran
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Apparently not. I don't believe there are many active posters on Teradata here, so you might just need to ping your official support provider instead.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply