Archives of the TeradataForum
Message Posted: Sat, 31 Mar 2002 @ 05:57:06 GMT
If I issue the following sequence via CLI:
1) DBCquery: bt; update ... ; 2) DBCendQuery 3) DBCquery: update ...; et; 4) DBCendQuery
What happens if there is a system crash (network failure, client crashes) between steps 2 and 3? Will the transaction be rolled back because there was no "et;" generated? Or does DBCendQuery issue an implicit "et;", so the transaction will not be atomic? (We have to break up the transaction this way because there are too many Updates and we get out-of-memory errors on the server.)
If there is a rollback, how does Teradata determine when to do the rollback, i.e. when does it "realize" that there will be no further calls from the client (calls 3 and 4 above) and it rolls back what it did in steps 1 and 2?
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|