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 deployment type. For more information, see Performance tuning recommendations for data and event management.
  • 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

Parameter description

Value command

Procedure

Set the number of processes and sessions.

alter system set processes = 1000 scope=spfile;
alter system set sessions = 1000 scope=spfile;

  1. Set the number of processes and sessions to 1000.
  2. Run the commands on the database and then restart the database.
  3. Connect to the database as system or sys in sysdba mode.

Set the sga_max_size.

alter system set sga_max_size=0 scope=spfile

Reset sga_max_size to 0.

Set memory allocation.

alter system set memory_max_target=8192M scope=spfile
alter system set memory_target=8192M scope=spfile

Set memory allocation to half of the system memory.
For example, if the system has 16 GB RAM, then set to memory_max_target=8192M.


Tuning recommendations for Oracle database with Report Engine

The following tuning recommendations apply only when you integrate 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.

Parameter description

Value command

Set the number of processes.

alter system set processes = 1250 scope=spfile;

Set memory allocation.

alter system set memory_max_target=20480M scope=spfile;

alter system set memory_target=20480M scope=spfile;

Set the number of job queue processes.alter system set job_queue_processes = 25 scope=spfile;

To resize available REDO log files before Infrastructure Management installation

Parameter description

Value command

Procedure

Set REDO01.

alter database add logfile group Inactive group number ('Path\Redo Filename Without Group NumberInactive group number.LOG') size 500m reuse;

To avoid Cannot allocate new log error.
For status of redo log file select group# status from v$log;

Set REDO02.

alter database add logfile group Inactive group number ('Path\Redo Filename Without Group NumberInactive group number.LOG') size 500m reuse;

To avoid Cannot allocate new log error.
For status of redo log file select group# status from v$log;

Set REDO03.

alter database add logfile group Inactive group number ('Path\Redo Filename Without Group NumberInactive group number.LOG') size 500m reuse;

To avoid Cannot allocate new log error.
For status of redo log file select group# status from v$log;

Check status of redo log files.

select group# status from v$log;
alter system switch logfile;
alter system switch logfile;

Set status of one redo log file to CURRENT, and the other two to ACTIVE.

Set audit_trail and scope.

alter system set audit_trail=none scope=spfile

Alter the audit_trail and scope values.

Set CONNECT_TIMEOUT_LISTENER.

CONNECT_TIMEOUT_LISTENER = 0

Add CONNECT_TIMEOUT_LISTENER = 0 in the listener.ora file.

Best Practice

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:

  1. Log on to the Oracle server as the Super Admin user. For example:
    sqlplus sys/<sys password> as sysdba
  2. Run the following command:
    alter system set CURSOR_SHARING=’FORCE';
  3. Restart the Infrastructure Management server.

Related topics

Supported databases and Web consoles requirements for Infrastructure Management

Performance tuning recommendations for Cloud Lifecycle Management

Performance tuning recommendations for data and event management

Performance tuning recommendations for event and impact management

Best practices and configuration guidelines for performance and scalability

Was this page helpful? Yes No Submitting... Thank you

Comments