Archives of the TeradataForum

Message Posted: Mon, 04 Oct 2010 @ 08:55:31 GMT

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

(environment)

Teradata: V2R6

SAS application (campaign studio with Sas Access to Teradata)

(fact)

Query-2 does not finish caused by (hunged-up) Query-1's session from SAS. This event happened a few times this month.

          Query-1: Teradata user-A' access from SAS application (campaign studio).
                   Query is [Select ... FROM tableX].
                   This Query was finished ( found in dbc.querylog),
                   but this session was NOT finished ( found in dbc.sessioninfo).

          Query-2: Teradata user-B' access from SAS application (campaign studio).
                   Query is [Locking table tableX for WRITE].
                   This Query was in the situation of WAIT caused by Query-1.

(question)

- Similar events happen in the other sites ?

- There is a good way to handle ?

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