KB34041: "The transaction was aborted by the user" error message occurs when attempting to run a report in MicroStrategy against a Teradata database

• Strategy

This article describes a transaction aborted error that can be seen against Teradata.

SYMPTOM:
User obtains the following error message when attempting to run a report in Strategy Developer (or Strategy Web) against a Teradata database:


QueryEngine encountered error: Execute Query failed.Error type: Odbc error. Odbc operation attempted: SQLExecDirect. The transaction was aborted by the user.

CAUSE:
Teradata puts out “The transaction was aborted by the user” message either in response to a query cancellation (SQLCancel ODBC command) or due to a disconnect from the network/database. The SQLCancel ODBC command may result from a user manually cancelling the report or an automatic issuance of this ODBC command by the Strategy Query Engine when a Strategy governor or timeout setting in reached.

Refer to the following Knowledge Base article for an outline of different scenarios that could lead to cancellation of an executing query (report) :
KB17934: Different methods of canceling an executing report job on the MicroStrategy Intelligence Server

Also, refer to the following Knowledge Base article for information on how query cancellation is facilitated by the Strategy Query Engine:
KB9868: How is query cancellation facilitated by the MicroStrategy Query Engine?

ACTION:
The following steps will help troubleshoot and resolve the issue:

1. First determine whether there is evidence of query cancellation. Such evidence may be ascertained from messages in the DSSErrors.log that would show the reaching of a governor/timeout or more directly, from the ODBC trace log that would show the presence of SQLCancel command.

2. If there is evidence of SQLCancel being issued by the Strategy query engine, examine the following Strategy related governors and suitably change/increase their value to resolve the issue:

Maximum values for report execution and elapsed times under Project Configuration > Governing - Result Sets
Maximum query execution time (sec)
User Session Idle Time (sec)
Web User Session Idle Time (sec)
VLDB setting, 'SQL Time Out (Per Pass)'
'Cancel this session's pending requests?' setting in Strategy Web
Other settings outlined in KB17934 as appropriate

Make sure to re-start Strategy Intelligence Server for the setting changes to take effect.

It is recommended to set the ‘Maximum query execution time (sec)’ and 'Maximum connection attempt time (sec)' settings (these two settings are located at Database Connection > Advanced) to a reasonably high finite number (such as 3600 seconds). It is recommended to not set either of these to -1.

3. If there is no evidence of SQLCancel being issued by the Strategy query engine, consider enabling the following ODBC options on the Teradata DSN:

Run in Quiet Mode
Enable Reconnect

To enable these options for Teradata DSN on UNIX/Linux, add the following parameters to the odbc.ini file:
EnableReconnect=Yes
RunInQuietMode=Yes

Third Party Software Installation WARNING
The third-party product(s) discussed in this article is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.

Comment

0 comments

Details

Knowledge Article

Published:

May 12, 2017

Last Updated:

May 12, 2017