This topic provides information about performance settings for BMC BladeLogic Atrium Integration. After installing BMC BladeLogic Atrium Integration and before using it, perform the following procedure for the data that BMC BladeLogic Atrium Integration transfers to BMC Atrium CMDB.
Use the AR System Administration Console to perform this task. See the BMC Remedy Action Request System Configuration Guide for the version of BMC Remedy AR System that you are using.
Before you begin
You must have a user account on the BMC Remedy AR System with privileges to perform these operations.
To enhance the performance of BMC BladeLogic Atrium Integration
- Use BMC Atrium Core Console or CMDB Class Manager to create indexes in BMC Atrium CMDB on the following forms:
- Index on BMC_BaseElement on TokenId
- Index on BMC_BaseElement on CDMachineID
- Index on BMC_BaseElement on CDMachineID, Name
- Index on BMC_BaseElement on CDMachineID, VersionNumber
- Provide Fast Thread and List Thread (minimum and maximum depending on the number of CPUs).
- Tune the AR database:
- Create separate disks for data and logs.
- Ensure cursor sharing is done at the database level.
- Move index and log on to separate tablespaces.
Use the following query on an Oracle database to generate statistics on all tables in the schema and their indexes:
execute dbms_stats.gather_database_stats (estimate_percent>10, cascade>TRUE);
- Make sure that the tablespace has enough free space (see the Performance Tuning for Business Service Management white paper).
The autoextend on next command adds to the size of the tablespace if the amount of data exceeds the current size of the tablespace. It adds to the tablespace according to its SIZE value and continues extending the tablespace until it runs out of disk space. To avoid this, set the AUTOEXTEND ON NEXT value to
512by using the following command:
ALTER DATABASE DATAFILE 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\AR75\ARSYS' AUTOEXTEND ON NEXT 4M;