Archives of the TeradataForum
Message Posted: Tue, 29 Nov 2005 @ 23:17:49 GMT
I am using a JDBC driver (version 03.02.00.03) to connect to Teradata. It appears that sessions created via my JDBC connection have something wrong with them. Consider this:
1) I login to Teradata with a JDBC connection.
2) I execute a select statement from a view.
3) I get the results back, Teradata is DONE processing my query.
4) PMON shows me this: AMP State = Idle and PE State = Response.
Idle/Response? What does that mean? After a query is done, the session should be Idle/Idle, not Idle/Response. It's like the JDBC driver is not managing the session characteristics properly.
Moreover, sessions that get caught in this "Idle/Response state" begin blocking new sessions. For example, session 1 does a select from a view and is now caught in the Idle/Response state. Then another session, session 2, comes in and tries to update the table that session 1 used. Session 2 then shows up as blocked (by session 1) in PMON. Yet session 1 has no active SQL.
Has anyone encountered something like this? I really need help here. I need to be able to connect using JDBC and not have sessions (that should be idle) block other sessions.
Thanks in advance.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|