Archives of the TeradataForum

Message Posted: Fri, 29 Mar 2013 @ 15:46:01 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

<-- Anonymously Posted: Friday, March 29, 2013 09:42 -->

Are you using ACCESS lock when checking to see if rollback happened? To be a valid check with this logic, you will need to use a table READ lock to ensure you wait for rollback to complete and release the UPDATE lock(s).

If you insert/update/delete 100's of millions of rows, rollback will take some time. Simply exiting BTEQ without ET will close the session immediately, which will cause the database to start rolling back the changes - but without the session context, the rollback progress is harder to track. You could GOTO a LABEL that does an explicit ROLLBACK / ABORT before exiting, but then you would have to set a fixed return code since BTEQ would not preserve the original ERRORCODE value.

	<Prev	Next>		<<First	<Prev	Next>	Last>>