Archives of the TeradataForum
Message Posted: Mon, 01 Apr 2002 @ 16:37:36 GMT
The DBCEndQuery command does NOT terminate the transaction, it simply tells cli and the dbms to terminate processing for that request. This may involve releasing spool files and will typically involve cleaning up cli memory. The dbms will only release locks IF the dbms knows this request is also the end of a transaction.
So in your scenario, -- if there is a system crash between steps 2 and 3, the dbms will rollbackto prior to step 1.
Teradata has no built-in timeout for automatically aborting sessions based on 'no activity' (this feature is included within Teradata Manager -- but that is an application working out who has been idle, not the dbms).
As far as I'm aware, the only time the dbms will check that clients are still there is following a restart. The dbms will check it's session info table and start a timer. If the client system for a particular client has not responded by the time the timer expires, it is assumed that the client has died and the sessions will be cancelled. That's my understanding but I may be of course a little (or a lot?)
Ward Analytics Ltd: Information in motion (www.ward-analytics.com)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|