Explanation of the log entries from the System Property mxe.db.logSQLTimeOut

Technote (FAQ)


Question

What is the format of these entries, what does each element mean and when does the timer for execution start and stop?

Answer

In the Performance Tuning guides found here:
http://www.ibm.com/developerworks/wikis/display/maximo/Performance+and+Tuning

And the Performance Must Gather document here:

http://www-01.ibm.com/support/docview.wss?uid=swg21313341

We recommend using this system property to look for SQL statements that take too long to run.

The format of the log entries generated is:
<Timestamp> [WARN] BMXAA6720W - User = (<username>) SPID = (<spid>) App = (<application name>) Object = (<object name>) <SQL statement> (execution took xxxxx milliseconds)

where:

User = the User that executed the query

SPID = The DB driver connection reference

App = The Application where the query was executed. If this is null it is a system generated query not done by a user. If there is an entry here the query was generated from the List tab of that Application.

Object = The Object the query was executed against.

The timer that measures the execution time will start right before Maximo/TPAE issues the statement execution and the timer will stop right after it completes the SQL execution. This SQL time will be for parse/bind/execute of the query but not retrieving the data into the Maximo/TPAE server through the Java objects.

If the JVM is operating normally, this SQL time is equal to the time the database takes for execution.

It is possible that this time on Maximo/TPAE server could be higher than the time the query took to execute on the database due to the JVM being GC (Garbage Collection) bound which means all threads would be paused.

This will happen if the SQL was a slow running query and while being executed the JVM went into full garbage collection and essentially paused while the SQL was completed. Then when the JVM comes back it will continue and print the time, but the database had already finished the work.

This is a very small percentage of the time and only when the JVM is GC bound. Verbose GC will indicate whether the JVM was paused during this time.


Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management IBM SmartCloud Control Desk
Systems and Asset Management Tivoli Change and Configuration Management Database
Systems and Asset Management Tivoli Asset Management for IT
Systems and Asset Management Tivoli Service Request Manager

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Maximo Asset Management

Software version:

7.1.1, 7.5

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1625060

Modified date:

2013-05-15

Translate my page

Machine Translation

Content navigation