Archives of the TeradataForum
Message Posted: Mon, 08 Sep 2008 @ 13:59:03 GMT
This question is related to Teradata JDBC Connection autoCommit() setting. In our application we have set autoCommit() to "false" to attain application driven transaction behavior.
Surprising though, I found that autoCommit set to false results in some extra commits getting fired which are definitely not from the application.
Came to know about this while checking DBC Query Logs for a single query transaction. Log contained "Too many end transaction" error message before execution of the query which is redundant as no commit is being fired from the application. There is only one commit that is being fired after the execution of query.
Has anyone seen this kind of behavior earlier. Is this a known problem with Teradata JDBC driver ?
Any response in this regard is highly appreciated.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|