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.

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.

Related topics

Supported databases and Web consoles system requirements

Performance tuning recommendations for BMC 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
© Copyright 2013-2015 BMC Software, Inc.
© Copyright 2013-2015 BladeLogic, Inc.
Legal notices