SYMPTOM:
When running reports in Strategy Developer 9.x, the following two errors are displayed:
Sample Code/Error
"Error: SQL Generation Complete[]QueryEngine encountered error: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Access Logging step has failed. The transaction was aborted. [] Error in Process method of Component: QueryEngineServer, Project XXXX, Job XXX, Error Code = -2147212544."
The following error may also be thrown when running the reports:
Sample Code/Error
"Error: SQL Generation Complete[]QueryEngine encountered error: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Too many simultaneous transactions. []Error in Process method of Component: QueryEngineServer, Project XXX, Job XXX, Error Code= -2147212544."
Further symptoms include that at the time the errors are encountered, the following entries can be seen in the DSSErrors log:
Sample Code/Error
"2009-06-30 09:24:53.897-07:00 QueryEngine encountered error: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Too many simultaneous transactions."
Sample Code/Error
"2009-06-30 09:47:09.681-07:00 Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Access Logging step has failed. The transaction was aborted."
CAUSE:
These errors are coming directly from the Teradata database and are the result of database connection user sessions on the database side that have remained idle for a long period of time and have become unresponsive (hung) but are still taking up space from the database user connection pool leading ultimately to the errors above.
Further information about the error codes above can be found in the following document:
http://www.info.teradata.com/eDownload.cfm?itemid=032370007&redirectfromfle=y
ACTION:
For further information and troubleshooting contact Teradata Technical Support.
WORKAROUND:
Once the Teradata database administrator has identified and deleted the idle (hung) database user sessions and restarted the database, no errors will be thrown when running reports in Strategy Developer 9.x.
