Job status is successful, even with fatal error in it
Posted: Wed Oct 08, 2008 11:16 am
Hello,
We have a parallel job that had a fatal error in it (when looked into the log), but still had a statement "Sucessfully Finished" at the end of the job log. Why would it do that? Has anyone see this before? Are there any configuration settings that I am missing?
Not all the jobs are ignoring the fatal errors. If there is a fatal error, the job status shows that it is aborted.
The kind of fatal error that I got and still the job finished successfully was ""TDEnt_Store_Inventory,0: TeraGenericQuery Error: DB Call Failure(success check) Info = 0, Code = 2616, Message = Numeric overflow occurred during computation. Session return code = 2,616 , DBC return code = 0
DBC message: Completed successfully.
TeraGenericQuery Error: DB Call Failure(success check) Info = 0, Code = 2616, Message = Numeric overflow occurred during computation. Session return code = 2,616 , DBC return code = 0
DBC message: Completed successfully."
Any help regarding this is greatly appreciated
We have a parallel job that had a fatal error in it (when looked into the log), but still had a statement "Sucessfully Finished" at the end of the job log. Why would it do that? Has anyone see this before? Are there any configuration settings that I am missing?
Not all the jobs are ignoring the fatal errors. If there is a fatal error, the job status shows that it is aborted.
The kind of fatal error that I got and still the job finished successfully was ""TDEnt_Store_Inventory,0: TeraGenericQuery Error: DB Call Failure(success check) Info = 0, Code = 2616, Message = Numeric overflow occurred during computation. Session return code = 2,616 , DBC return code = 0
DBC message: Completed successfully.
TeraGenericQuery Error: DB Call Failure(success check) Info = 0, Code = 2616, Message = Numeric overflow occurred during computation. Session return code = 2,616 , DBC return code = 0
DBC message: Completed successfully."
Any help regarding this is greatly appreciated