Supporting multiple Infrastructure Management Servers on a single Oracle database instance

Guidelines and recommendations for supporting multiple TrueSight Infrastructure Management Servers on a single Oracle database instance

• Hardware resources of the computer in which multiple Infrastructure Management Servers share the same Oracle instance must be increased to accommodate the extra load. Also increase the disk capacity based onPerformance benchmarks and tuning for Infrastructure Management.

• The Infrastructure Management Server can have the following load:
  
  Load on each TrueSight Infrastructure Management Server

  Instance	Attributes	Events
  250 K	1.7 Million	350 K per day

• To configure the Oracle database instance on a Windows or a Linux operating system, seeHardware requirements to support small, medium, and large environments.

• The following parameters require to be tuned and increased if you are hosting multiple Infrastructure Management Servers:

   Parameter tuning for each TrueSight Infrastructure Management Server

  Parameter Name	Recommended Size
  memory_target When you add multiple TrueSight Infrastructure Management servers, the 50% of total system memory is calculated from the total memory of the system. For example, if you configure two medium TrueSight Infrastructure Management server and the requirement is 32GB for the each Oracle database server that sums up to 64GB. The 50% is calculated from the 64GB.	50% of total system memory
  memory_max_target When you add multiple TrueSight Infrastructure Management servers, the 50% of total system memory is calculated from the total memory of the system. For example, if you configure two medium TrueSight Infrastructure Management server and the requirement is 32GB for the each Oracle database server that sums up to 64GB. The 50% is calculated from the 64GB.	50% of total system memory
  Processes	1000
  Open_cursors	4000
  Db_writer_processes	2
  Job_queue_processes	20
  Session_max_open_files	30
  /dev/shm	Should be > 20 GB
  /root	Space should be > 40 GB
  Table Spaces	Space should be > 30 GB

• For each additional TrueSight Infrastructure Management server, it is recommended that you use a separate Pluggable database (PDB) and set the tuning for individual Pluggable databases as specified above.

• If you plan to use the same SID for multiple TrueSight Infrastructure Management servers, set the tuning as specified above.

  Important

  If you use a single SID for multiple TrueSight Infrastructure Management servers, ensure that no other BMC product is using the same Oracle SID. BMC supports two TrueSight Infrastructure Management servers into one Oracle SID.

• If you have TrueSight Operations Management Report Engine integration with the same SID, then adjust system memory, processes, and job queue processes as specified inTuning recommendations for Oracle database with Report Engine.

  Make the following parameter tuning additions for each TrueSight Operations Management Report Engine integration: 

  Parameter Name	Recommended Size
  memory_target and memory_max_target If you integrate the TrueSight Operations Management Report Engine, the 50% of total system memory is calculated by including the additional memory.	4GB
  Processes	250
  Job_queue_processes	5

• If you want to add more than one TrueSight Infrastructure Management servers, you must update the INIT parameters. To update the INIT parameters, perform the following steps:
  1. Navigate to %temp%\pw\pronto\conf\ directory.
  2. Open the oracle_parameters.conf file. 
  3. Remove the values mentioned in the Parameter tuning table of the INIT parameter from file.
  4. Save the file and restart the installation.

• On UNIX platforms, the Oracle memory_target and memory_max_target parameters are dependent on the space available in the /dev/shm file system. You can check the space using the df -kh /dev/shm command and based on the space available, set the values of the memory_target and memory_max_target parameters. The space available at /dev/shm (tmpfs) must be greater than the value that you set for memory_target.  For example:

  <- 
  Cmd# 
  df -kh 
  tmpfs 7.9G 1.3G 
  6.6G 17% /dev/shm 
  ->

  In this case, you can set the memory_target parameter to about 6 GB. If you want to set memory_target to a higher value, proportionally increase the space in the tmpfs directory.

• To export or import data from/to Oracle Real Application Clusters (RAC), you can use one of the SIDs or services to connect to the database as follows:
  expdp <sys of instance-b>/<password>@< SID of instance-b>|<service name of the instance> PARFILE=<path of the pnet_exp_all_tables.par file>

  impdp sys/<password>@< SID of instance-a>|<service name of the instance> PARFILE=<path of the pnet_imp_all_tables.par file>

  Note

  The service name of the RAC is common to both the instances.

• When you are migrating the BMC TrueSight Infrastructure Management Server’s database from one instance to another, ensure that you stop the BMC TrueSight Infrastructure Management Server and then export the contents of the database. If the BMC TrueSight Infrastructure Management Server is running during the database export, data may be lost.

Best practices to configure multiple Infrastructure Management Servers:

• Back up the each BMC TrueSight Infrastructure Management Server level schema to restore at a user level.
• The ADDMR and AWR reports do not complain about Disk I/O, CPU requirements.
• Have sufficient disk space for archiving and backing up by using current redo log switch rate.
• Monitor the file size of redo log to reduce the number of switches.
• The Oracle monitor solution is set up to have values for buffer cache hit ratio and dictionary cache hit ratio.
• Monitor the listener and alert log for exhaust of cursors, and assign enough sessions.

For information on the guidelines and tuning recommendations for supporting multiple BMC TrueSight Infrastructure Management Servers on a single Oracle database instance, seeTuning the Infrastructure Management database for performance.

For more information about the best practices, see Considerations and best practices for deploying the Oracle database.