Collecting Data: Maximo Performance/Stability

Technote (FAQ)


Question

Collecting data for performance and stability problems with Maximo. Gathering this information before calling IBM support will help you with the troubleshooting process and save time analyzing the data.

Answer

Maximo Performance/Stability specific Collecting Data information

This technote describes what information you need to begin troubleshooting a Maximo performance/stability issue.

If you have not compiled the General information, Please see General Collecting Data document 1313647 and include that information.

Please answer the following regarding the Infrastructure:

1. Did you make any changes to your infrastructures around the time the problem started. If yes,
a. Hardware
b. Did you add/remove any members to/from your cluster
c. Did you move any software components to new hardware
d. Have you introduced any new appliances to your network such as network accelerators

2. Did you reconfigure or apply any software updates to any of the following Software?
(If the answer is yes, please also describe the change including the old and new versions)
a. Network Configuration such as DNS
b. Cluster environment
c. Load balancer
d. Application server
e. Database server
f. Server Operating System
g. Browser

3. Have you recently increased the number of users accessing the system


Logging Configuration

For performance and stability problems IBM recommends capturing up to 24 hours of logs so that application server trending can be done.

1. Turn on Maximo performance related properties.

The information provided by the application debug properties is critical to the resolution process. The three properties listed in the following setup do not impact performance and provide valuable information about the system. It is recommended that these properties be left on at all times to help with root cause analysis if there is an event.

Maximo 5.2 (Patch 5 or later)

Filename: {maximo_home}\mxserver.properties file
Steps to enable logging:
1. Uncomment or add (if they do not exist) the following properties:
mxe.db.logSQLTimeLimit=1000
mxe.cronTask.psdi.server.MboCountCronTask=1m
mxe.db.fetchResultLogLimit=200
2. Rebuild and redeploy the maximo.ear

Maximo 6

Ensure that that the following file contains the settings below:
Filename: {maximo_home}\applications\maximo\properties\logging.properties
log4j.rootLogger=ERROR, A1, A2
log4j.logger.maximo=INFO
log4j.appender.A2=org.apache.log4j.RollingFileAppender
log4j.appender.A2.File={SomeFileAndPath}
log4j.appender.A2.MaxFileSize=20MB
log4j.appender.A2.MaxBackupIndex=24

Note: Windows uses double backslash (\\) in path of the log4j.appender.A2.File property. Example: C:\\Maximo\\Logs\\Maximo.log

Note: The above settings will allow you to log up to 20MB per hour and still capture up to 24 hours of logs before the log rolls over the first index.

Steps to enable logging:
1. Uncomment and modify the following properties in the
maximo\applications\maximo\properties\maximo.properties file:
mxe.mbocount=YES
mxe.db.logSQLTimeLimit=1000
mxe.db.fetchResultLogLimit=200
2. Rebuild and redeploy the maximo.ear

Maximo 7

Steps to enable logging:
1. Set the Root Logger in Logging Application to INFO and the appender to Rolling.



2. Also set the Rolling Appender to a file size of 20 and backup index of 24.




3. Apply the settings


4. Set the following properties in the System Properties Application



a) mxe.db.logSQLTimeLimit=1000



b) mxe.mbocount=1


c) mxe.db.fetchResultLogLimit=200


5. Select those 3 properties and Select Action / Live Refresh



1. Turn on verbosegc logging (Stop and start the Maximo Application Server after making the change).
If WebSphere, from the Process Definition\Java Virtual Machine page check the verbose garbage
collection checkbox
If WebLogic, add the command line argument -verbose:gc to the WebLogic startup file(s) or
service install cmd file. (If running as a Windows service the service needs to be uninstalled and
reinstalled to see the change or the administrator must edit the service using the Windows
REGEDIT tool)

2. Move or remove all WebSphere, WebLogic and Maximo logs
Maximo logs as defined from general information collection
WebSphere, ibm\websphere\appserver\profiles\<profilename>\logs\<servername>
WebLogic 8, bea\user_projects\domains\<domainname>\<servername\<servername>.log
WebLogic 9, bea\user_projects\domains\<domainname>\servers\<servername>\logs\
<servername>.log
When the issue happens collect the above logs

3. Windows only, ensure userdump utility is installed. If it is not installed, Download utility from

http://download.microsoft.com/download/win2000srv/Utility/3.0/NT45/EN-US/Oem3sr2.zip.

Unzip to Application Server machine

Run the application and when you experience the performance issue:

Generate 3-4 thread dumps 4-5 minutes apart and save that data

Windows:
userdump.exe {PID of Java Process} {path and filename for dump}

Example:. userdump.exe 9999 c:\dumps\threads1.txt

Unix/Linux:

kill -3 <PID>

Example: kill –3 9999

4. Maximo session data
Connect to Maximo database via a SQL tool and send the output from the following:
select * from maxsession


Network Topology Information

1) Are some clients connected through Citrix or Terminal Server
2) User geographic locations in relation to the application server
3) Total Concurrent users
4) Is a firewall employed between the client and Maximo server
5) Is a proxy/reverse proxy server is employed between the client and Maximo server. If yes, describe
6) Is network compression (Riverbed, Cisco, Juniper, etc) enabled?
7) Does the environment use Clustering & Load Balancing
8) If load balancing:
a) Using a hardware or software load balancer (describe)
b) Type of load balancing (round-robin, weight based, random, etc.)
c) Using IBM HTTP Server w/ plugin?
d) How many IBM HTTP Servers?
9) Execute the following command from a slow performing client:
At a command prompt enter the following (substitute the actual server name for the {app_server_name} value:

Ping {app_server_Name} –n 100 >clientping.txt
Tracert {app_server_name} >clienttrace.txt

Application Servers
1) Manufacturer/Model
2) Processor Speed
3) Number of processors per server
4) Number of physical servers used for the application
5) How much physical memory is dedicated to each physical server and/or VM
6) Disk Space
7) Is this server an LPAR
8) If using LPARs or VMs, how many per physical server
9) If using LPARs or VMs, how much physical (not virtual) memory has been allocated to the
entity?
10) If using LPARs or VMs, how many processors have been allocated to each entity? Are they
physical or virtual?
11) What operating system is running on each of the application servers
12) Is the application running on a virtual server
13) Is the operating system 32 bit or 64 bit
For best server information in Windows at the command prompt execute:
"C:\Program Files\Common Files\Microsoft Shared\MSINFO\MSINFO32.EXE" /report serverinfo.txt
This runs in the background and may take 5 minutes or more to complete. The file will not
appear until the process is complete. Include the resulting file.
14) Is the application server software 32 bit or 64 bit
If WebSphere, At a command prompt on the WebSphere Application Server execute:
IBM\WebSphere\AppServer\java\jre\bin\java –fullversion >serverjavainfo.txt
15) Number of Maximo JVMs on each server, LPAR, or VM
16) Are there any dedicated JVMs for cron tasks, escalations, reports, or interfaces
If yes, what is the role of the JVMs and how many
17) What is the initial and maximum memory defined to each of the JVMs
If WebSphere, heapsize values in server.xml (
ibm\WebSphere\AppServer\profiles\<app server
profile>\config\cells\<cell>\nodes\<node>\servers\<app server name>). Please send that
server.xml.
If WebLogic 8, memory variable may be defined in the commEnv.cmd if Windows or
commEnv.sh if Unix/Linux (bea\weblogic81\common\bin). Please send the commEnv file.
Or the memory variable may be defined in the startWebLogic.cmd if Windows or
startWebLogic.sh if Unix/Linux (bea\user_projects\domains\<domainname). Please send
the startWebLogic file.
If WebLogic 9, memory variable is defined in the setDomainEnv.cmd if Windows or
setDomainEnv.sh if Uinx/Linux (bea\user_projects\domains\<domainname>\bin)
18) Generic Java Parameters
If WebSphere, value in server.xml (
ibm\WebSphere\AppServer\profiles\<app server
profile>\config\cells\<cell>\nodes\<node>\servers\<app server name>). Please send that
server.xml.
If WebLogic 8, Java parameters variable may be defined in the commEnv.cmd if Windows or
commEnv.sh if Unix/Linux (bea\weblogic81\common\bin). Please send the commEnv file.
Or the Java parameters variable may be defined in the startWebLogic.cmd if Windows or
startWebLogic.sh if Unix/Linux (bea\user_projects\domains\<domainname). Please send
the startWebLogic file.
If WebLogic 9, Java parameters variable is defined in the setDomainEnv.cmd if Windows or
setDomainEnv.sh if Uinx/Linux (bea\user_projects\domains\<domainname>\bin)
19) Are the JVMs clustered using WebSphere or WebLogic clustering
If WebSphere, please send the ibm\httpserver\plugins\config\webserver1\plugin-cfg.xml
and
IBM\WebSphere\AppServer\profiles\<profilename>\config\cells\<cell name>\<cluster
name>\cluster.xml
If WebLogic 8, please send the bea\user_projects\domains\<domainname>\config.xml
If WebSphere 9, please send the bea\user_projects\domains\<domainname>\ config\config.xml

Database Server
1) Database platform and version (DB2, Oracle, SQL Server)
2) Manufacturer/Model
3) Processor Speed
4) Number of processors per server
5) Number of physical servers used for the application
6) How much physical memory
7) Disk Space
8) Is this server an LPAR
9) If using LPARs or VMs, how many per physical server
10) If using LPARs or VMs, how much physical (not virtual) memory has been allocated to the
entity?
11) If using LPARs or VMs, how many processors have been allocated to each entity? Are they
physical or virtual?
12) What operating system is running
13) Is the operating system 32 bit or 64 bit
For best server information in Windows at the command prompt execute:
"C:\Program Files\Common Files\Microsoft Shared\MSINFO\MSINFO32.EXE" /report serverinfo.txt
This runs in the background and may take 5 minutes or more to complete. The file will not
appear until the process is complete. Include the resulting file.
14) Is this database use only for Maximo deployment
15) Size of database
16) Oracle information
a) select name,value from v$parameter
b) Generate an AWR report
To Create AWR Report:
Login in to the database using Sqlplus as Sys user
Example: connect sys/password@db as sysdba
- At Sqlplus Prompt : <ORACLE_HOME>\RDBMS\ADMIN\awrrpt.sql;
- Script will prompt for Report Type - Select HTML, Provide a folder name to Save the
Report, Provide Begin and End Snapshot Numbers.
c) Generate an ADDM report
To Create ADDM Report:
Login in to the database using Sqlplus as Sys user
Example: connect sys/password@db as sysdba
- At Sqlplus Prompt : <ORACLE_HOME>\RDBMS\ADMIN\addmrpt.sql;
- Script will prompt for Report Type - Select HTML, Provide a folder name to Save the
Report
17) SQL Server information
select indexproperty (object_id('workorder'),'workorder_ndx1','IsPageLockDisallowed')
18) DB2 information
a) db2 get dbm cfg
b) db2 get admin cfg
c) db2 get db cfg

Report Server
1) If using reports, what is the Report Server and version
Examples include Birt, Actuate, Crystal
2) Manufacturer/Model
3) Processor Speed
4) Number of processors per server
5) Number of physical servers used for the application
6) How much physical memory is dedicated to each physical server and/or VM
7) Disk Space
8) Is this server an LPAR
9) What operating system is running on each of the application servers
10) Is the application running on a virtual server
11) Is the operating system 32 bit or 64 bit
For best server information in Windows at the command prompt execute:
"C:\Program Files\Common Files\Microsoft Shared\MSINFO\MSINFO32.EXE" /report serverinfo.txt
This runs in the background and may take 5 minutes or more to complete. The file will not
appear until the process is complete. Include the resulting file.

Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management Tivoli Asset Management for IT All
Systems and Asset Management IBM Maximo Asset Management Essentials All
Systems and Asset Management IBM Maximo Asset Management Essentials All
Systems and Asset Management IBM Maximo Asset Management Essentials All
Systems and Asset Management IBM Maximo Asset Management Essentials All

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Maximo Asset Management

Software version:

5.2, 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.5

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows

Reference #:

1313341

Modified date:

2010-08-30

Translate my page

Machine Translation

Content navigation