The fetchResultLogLimit Property and Its Use

Technote (FAQ)


Is there a use for the fetchResultLogLimit property and is it possible to generate critical debug information for troubleshooting performance, stability, and runtime issues?


In V6 the mxe.db.fetchResultLogLimit property can be found in the path:
<application source root>/applications/maximo/properties/
The default value for this property is 200.

In V7 the fetchResultLogLimit property can be found in the system properties application
The default value for this property is 200

When enabled, this property generates a forced exception in the log each time the specified number of objects is loaded into a single set. The resulting stack trace shows what process is loading the objects.

When too many objects are being loaded and not released, this property can show how often a given process is loading the threshold count of objects. When set to 200, this will generate a stack trace when 200, 400, 600…etc objects are loaded into any single set.

This property will not generate any output if the threshold is not met. This means that setting the value to a higher number may not provide the necessary results to diagnose a problem. Even if 10,000 objects are in memory but there are more than 50 sets, it is possible that the threshold of 200 will not be met.

Typical output to the logs might look as follows:

IBM has internal tools that can correlate and trend this information combined with the output of the mbocount property and the LogSQLTimeLimit to determine many causes of performance, stability, and runtime problems. Since mbocount runs every minute, IBM can gather an understanding of the health of the JVM over a period of time. Often IBM will request up to 24 hours of logs to determine trends in user loads, memory requirements and many other points of interest.

This property should be left running at all times since a problem can often not be foreseen or replicated. In order to troubleshoot or find root cause of many issues, the data from this property is required.

For more information on debug properties see the document Using debug properties to monitor and troubleshoot performance

Also see:

The document what is the mbocount property
The document what is the logSQLTimeLimit property

Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management IBM Maximo Asset Management Essentials
Systems and Asset Management Tivoli Asset Management
Systems and Asset Management Tivoli Asset Management for IT
Systems and Asset Management Tivoli Asset Management for Service Providers
Systems and Asset Management Tivoli Change and Configuration Management Database
Systems and Asset Management Tivoli Service Automation Manager
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
System Related

Software version:

6.0, 6.1, 6.2, 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.2.6, 6.2.7, 6.2.8, 7.1, 7.1.1, 7.1.2, 7.2, 7.2.1, 7.5

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:


Modified date:


Translate my page

Machine Translation

Content navigation