Tools for troubleshooting

Tools are available to collect and analyze both system and performance diagnostic data.

Troubleshooting in Product Master focuses primarily on analyzing system log files, but following tools are available that can help you during the troubleshooting process.
  • Diagnostic data collection
    • Using pimSupport.sh script
    • Using Db2® server tools
    • Using Oracle Database server tools
    • Using IBM® Support Assistant
  • Monitoring Java™ virtual machine (JVM)
  • Using Sumall utility
  • Using LTA tool
  • Using the built-in cache mechanism
  • Using the built-in profiling mechanism

Diagnostic data collection

Using pimSupport.sh script
Use the pimSupport.sh script to collect basic environment configuration and system status information along with Product Master and application server log files as a starting point when requiring assistance from support. For more information, see pimSupport.sh script.
Using Db2 server tools
Using a single command for each tool, basic configuration and error message logs (db2diag.log) can be collected from Db2 server.
db2support archives all of the files into a compressed file containing either the file name that is specified by the user (-o option), or the default file name, db2support.zip.
db2support . -d MyDbName -c
db2pd collects all the db2pd diagnostics. For more information, see Monitoring and troubleshooting using db2pd command.
Using Oracle Database server tools
The database instance stores various types of diagnostic data in the Automatic Diagnostic Repository. Especially when performance problems are investigated, IBM support requires Automatic Diagnostic Repository reports. You can query V$DIAG_INFO to see where to find various logs.
select * from v$diag_info;
1;Diag Enabled;TRUE
1;ADR Base;/opt/oracle/11
1;ADR Home;/opt/oracle/11/diag/rdbms/jora11g/jora11g
1;Diag Trace;/opt/oracle/11/diag/rdbms/jora11g/jora11g/trace
1;Diag Alert;/opt/oracle/11/diag/rdbms/jora11g/jora11g/alert
1;Diag Incident;/opt/oracle/11/diag/rdbms/jora11g/jora11g/incident
1;Diag Cdump;/opt/oracle/11/admin/jora11g/cdump
1;Health Monitor;/opt/oracle/11/diag/rdbms/jora11g/jora11g/hm
1;Default Trace File;/opt/oracle/11/diag/rdbms/jora11g/jora11g/trace/jora11g_s011_1114164.trc
1;Active Problem Count;3
1;Active Incident Count;186
By default, the Oracle Database generates snapshots once every hour, and retains the statistics in the workload repository for 7 days. When necessary, you can use DBMS_WORKLOAD_REPOSITORY procedures to manually create, drop, and modify the snapshots. To launch these procedures, a user must be granted the database administrator role. For more information, see Managing the Automatic Workload Repository.
To generate an HTML or text Automatic Workload Repository report for a range of snapshot IDs, run the awrrpt.sql script at the SQL prompt.
sqlplus system/manager @$ORACLE_HOME/rdbms/admin/awrrpt.sql
You can then specify snapshots to be used for the report in an interactive mode and generate the workload repository report.
First, you need to specify whether you want an HTML or a text report.
Enter value for report_type: html

Specify the number of days for which you want to list snapshot Ids.
Enter value for num_days: 2

After the list displays, you are prompted for the beginning and ending snapshot Id for the workload repository report.
Enter value for begin_snap: 150
Enter value for end_snap: 160

Next, accept the default report name or enter a report name. The default name is accepted in the following example:
Enter value for report_name: 
Using the report name awrrpt_1_150_160
Using IBM Support Assistant
For more information, see Collecting data with the IBM Support Assistant.

Monitoring Java virtual machine (JVM)

For more information, see Monitoring Java virtual machine (JVM).

Using Sumall utility

For more information, see Using Sumall utility.

Using LTA tool

For more information, see Using LTA tool.

Using the built-in cache mechanism

Product Master has a built-in cache mechanism for some Product Master objects. Ensuring high cache hit ratios can be the key for optimal performance. If you need to monitor cache hit utilization, you can trigger a cache snapshot by running the following command.
[<code>]
$JAVA_RT com.ibm.ccd.common.wpcsupport.util.SupportUtil --cmd=getRunTimeCacheDetails
[</code>]
For more information, see Cache management.

Using the built-in profiling mechanism

For more information, see Using profiling mechanism.