KB171185: "The database execution thread hung" error message appears when the MicroStrategy Query Engine attempts to open a new connection to the Statistics database on a Teradata machine.

Suppose a user is logging project statistics into a Teradata database. Statistics become disabled for the project when Strategy Intelligence Server starts up because it is unable to connect to the Statistics database.
 
NOTE: When Strategy Intelligence Server is started, it searches for a valid connection to the Statistics database for every project that has statistics enabled. If there is an error when checking the connection to the Statistics database (a connection cannot be made, the database is down, the database returns an out of space error, etc.), Strategy Intelligence Server will disable the Statistics logging for that specific project. Refer to the following Strategy Knowledge Base document for details on this behavior:
 

• KB8077 (KB5300-71X-0334): 'MsiStatisticsMgr::Init() failed: project=, HR=0x80004005, statistics will be disabled for this project!' message appears in the DSSErrors.log of MicroStrategy Intelligence Server 9.x and 10.x

The DSSDatabaseClasses.log shows the occurrence of the 'The database execution thread hung' error message during the creation of a new connection. The following is a snippet from the log with keys Connection Management and Database Errors enabled:
2152:Connection created: Connection ID: 7, Database Instance: ###, Connection: ###, Login: ###, Connection String: DSN=###;UID=###, Multiprocess, Non-extended Fetch, Row by Row Insertion, MBCS encoding, Synchronous
2152:The database execution thread hung.. Connection String:DSN=###;UID=###;. SQL Statement:
As can be seen from the snippet above, there is a 20 second time-lag between the time Statistics connection is created and the occurrence of the error message. This could lead the user to believe that Strategy Query Engine issues a 20 second timeout on the duration of establishment of a connection to the Statistics database.
 
However, that is not the case. Strategy Query Engine does issue a timeout on the duration of establishment of a connection, but that timeout is 60 seconds. The above error occurs after 20 seconds.The above error occurs because Strategy Query Engine could not establish a connection to this Statistics database due to certain issues pertaining to configuration on the database side. The 20 second timeout comes from the default value for the 'Login Timeout' setting on the Teradata ODBC DSN (Teradata ODBC Driver Options > Advanced). This setting is illustrated in the following screen shot:

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