 |
 |
Archives of the TeradataForum
Message Posted: Sun, 31 Mar 2013 @ 10:21:19 GMT
| Subj: | | Re: Why BT-ET not working on large volume of data? |
| |
| From: | | sughesh iyyani |
Anomy.Anom wrote:
| | 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. | |
Hi Anomy,
Thanks a lot for the info.
We are executing these BTEQ scripts in batch and I am validating the data in table using SQL Assistant.
Even batch job got abended in between, we are seeing changes are reflected.
I checked the same even after some hours, but changes are not roll backed.
Kindly let me know your suggestions.
Thanks in advance,
Sughesh.
| |
