Recommended Resources
Abstract
This document is a list of information to provide to support when a performance problem occurs in your IBM Initiate environment. The document is specific to environments that are backed by an Oracle(tm) database
Content
This is a must gather document for performance problems on IBM Initiate MDS that is configured with Oracle as the database.
As performance issues are often complex and unique, more information will likely be requested. However, gathering this
information before calling support will usually speed the analysis and resolution of performance problems.
- Description of the performance issue.
Here is a non-exhaustive list or of questions that may help characterize the problem:
- Exactly what functionality of the product appears to be performing poorly?
- How are you measuring the performance?
End User complaints?
TIMER log entries?
Logs from applications that are integrated with the environment?
- Is the performance issue occuring at specific times of day, or continuously?
- Has there been a time in the past when performance was acceptable?
- Exactly what functionality of the product appears to be performing poorly?
- AWR reports in HTML format for each snap interval during a minimum of 24 hours.
- Oracle defaults the snap interval to 30 minutes, this will mean 48 reports.
- It is very important to gather the individual snaps, as an Oracle AWR has averaged statistics, and a longer timeframe can hide important information
- We use all of the AWR reports to pull relevant statistics across the entire timeframe.
- Longer timeframes can also be helpful ( For example, if a problem happens on one day in a week, a 7 day, or 14 day span may be helpful )
- Oracle defaults the snap interval to 30 minutes, this will mean 48 reports.
- TIMER logs from all engines and entity managers in the environment during the same timeframe, and while the problem is occurring
- If your environment has less than approximately 8 million members, please gather "madconfig support" on one of the installed instances.
- This will gather entity sizes, bucket sizes, and member counts from your installation.
- Some of the queries are resource intensive. If this is run in a production environment, consideration should be taken to run these queries during non peak usage.
- If you are running an earlier version of IBM Initiate MDS, "madconfig support" may not be implemented.
In that case, please contact support for the appropriate queries to run to gather entity and bucket size.
- This will gather entity sizes, bucket sizes, and member counts from your installation.
- Please gather configuration information from each application server
- How many, and what type of CPU's?
- How much memory is installed on the application servers?
- engine.properties ( for versions prior to 9.2)
- zip of $MAD_HOMEDIR\inst\mpi_instname\conf directory ( for versions including and after 9.2 )
- How many, and what type of CPU's?
- Please provide a list of recent changes to the environment.
Here is a non-exhaustive list of environmental changes that may have performance impacts.
- Changes in member loads
- IBM Initiate algorithm, or configuration changes
- Network changes, or issues
- SAN changes, or issues
- Changes in scheduling for database backups, data loads, or end user access times.
- Changes in member loads
[{"Product":{"code":"SSLVY3","label":"Initiate Master Data Service"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"Version Independent","Edition":"All Editions","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21572031