Tuning the Infrastructure Management database for performance
The BMC TrueSight Infrastructure Management Server supports a SAP SQL Anywhere or Oracle database.
- A SAP SQL Anywhere ASA database comes embedded with BMC TrueSight Infrastructure Management Server. Most of the settings are optimized out-of-the-box. You can tune the SAP SQL Anywhere database according to your Performance tuning recommendations for data and event management. . For more information, see
- An Oracle Database requires the database installation on a separate computer. You can tune several Infrastructure Management properties and Oracle Database parameters to optimize performance. The following tables provides the most common properties and changes that you should consider before installing BMC TrueSight Infrastructure Management Server.
Tuning recommendations for Oracle database
Set the number of processes and sessions.
Set memory allocation.
Set memory allocation to half of the system memory.
Tuning recommendations for Oracle database with Report Engine
The following tuning recommendations apply only when you integrate a BMC TrueSight Operations Management Report Engine with BMC TrueSight Infrastructure Management.
After you change these settings, restart the Oracle server and then restart the Infrastructure Management server.
Set the number of processes.
Set memory allocation.
|Set the number of job queue processes.|
To resize available REDO log files before Infrastructure Management installation
Check status of redo log files.
Set status of one redo log file to
Set audit_trail and scope.
In a production environment, it is important to size the redo log files to ensure that the frequency of redo log switches is not more than 5 log switches per hour during peak DML activity. Oracle provides the v$log_history view that tracks the historical frequency of log switches, and this can be correlated to periods of high update activity when log switching is peaking.
Set a redo log file with an initial size of minimum 500 MB and increase the size (1 GB → 1.5 GB → 2 GB) based on the log switch rate.
To set the CURSOR_SHARING attribute
By default, Oracle sets the CURSOR_SHARING attribute to EXACT.
You can change this attribute to FORCE, which reduces the number of new cursors created in the database. This setting creates new cursors only when needed and reduces memory consumption, resulting in better performance.
To change the CURSOR_SHARING attribute value:
- Log on to the Oracle server as the Super Admin user. For example:
sqlplus sys/<sys password> as sysdba
- Run the following command:
alter system set CURSOR_SHARING=’FORCE';
- Restart the Infrastructure Management server.