This topic provides the steps to support multiple BMC ProactiveNet Child Servers on a single Oracle database instance on Microsoft Windows. It includes the following use cases:
More than two BMC ProactiveNet Server 9.6 must be connected to a single Oracle database instance. The BMC ProactiveNet Server 9.6 must have the following load:
Load on each BMC ProactiveNet Server
Instance | Attributes | Events |
---|---|---|
1.7 Million | 250 K | 350 K per day |
The following are the requirements to configure the Oracle database instance on a Windows or a Linux operating system:
Recommended Configuration
Component | Minimum requirement | Maximum requirement |
---|---|---|
RAM | 64 GB | 74GB |
CPU | 12 CPUs | 16CPUs |
Disk space | 750 GB | 1 TB |
The following parameters require to be tuned if you are hosting multiple BMC ProactiveNet Child Servers:
Parameter tuning
Parameter Name | Recommended Size |
---|---|
memory_target | 37.5 % |
memory_max_target | 40% of total System RAM |
Processes | 1500 |
Open_cursors | 6000 |
Db_writer_processes | 4 |
Job_queue_processes | 30 |
Session_max_open_files | 30 |
/dev/shm | Should be > 20 GB |
/root | Space should be > 40 GB |
Table Spaces | Space should be > 30 GB |
If you want to add more than one child servers, you must update the INIT parameters. To update the INIT parameters, perform the following steps:
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 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.
Ensure that you back up each BMC ProactiveNet Server level schema to restore at a user level.
For information on the guidelines and tuning recommendations for supporting multiple BMC ProactiveNet Servers on a single Oracle database instance, see Guidelines and tuning recommendations for supporting multiple BMC ProactiveNet Servers on a single Oracle database instance.