[
https://issues.apache.org/jira/browse/TRAFODION-2311?focusedWorklogId=256393&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-256393
]
ASF GitHub Bot logged work on TRAFODION-2311:
---------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Jun/19 08:19
Start Date: 08/Jun/19 08:19
Worklog Time Spent: 10m
Work Description: arvind-narain commented on issue #1844:
[TRAFODION-2311] Avoid logging error 8605 and 8609 during SQLEndTrans if no
trans active
URL: https://github.com/apache/trafodion/pull/1844#issuecomment-500106339
Thanks @sbroeder and @selvaganesang. Sorry for the delay. Will check
SQL_EXEC_Xact and update. This change is mainly needed since some packages
written for other databases may expect a transaction to be started even for a
select. If the code is ported over then such application fills up the logs on
every commit done after a select. As stated above ODBC standards do state that
SQL_SUCCESS should be returned on a SQLEndTrans if there are no transactions
pending. If numerous 8605 and 8609 messages are present in the logs then
troubleshooting other issues becomes difficult.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 256393)
Time Spent: 1h (was: 50m)
> Avoid error 8605 and 8609 during SQLEndTran if no transaction active
> --------------------------------------------------------------------
>
> Key: TRAFODION-2311
> URL: https://issues.apache.org/jira/browse/TRAFODION-2311
> Project: Apache Trafodion
> Issue Type: Bug
> Reporter: Arvind Narain
> Assignee: Arvind Narain
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Frequently , during performance test runs like OE and other regression tests
> following errors are observed in master logs:
> ERROR[8605] Committing a transaction which has not started.
> ERROR[8609] Waited rollback performed without starting a transaction.
> MXOSRVR does return success to the client for these errors but since
> commit/rollback is executed, the error gets logged in master exec logs.
> Some of these can be avoided if mxosrvr implements the following ODBC
> standard and skips executing the commit/rollback statement.
> "For drivers and data sources that support transactions, calling SQLEndTran
> with either SQL_COMMIT or SQL_ROLLBACK when no transaction is active returns
> SQL_SUCCESS (indicating that there is no work to be committed or rolled back)
> and has no effect on the data source."
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
