Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

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:

Guidelines and recommendations for supporting multiple BMC ProactiveNet Child Servers on a single Oracle database instance

  • Hardware resources of the computer in which BMC ProactiveNet multiple Child Servers share the same Oracle instance must be increased to accommodate the extra load. For example, if you have 8 GB RAM for one BMC ProactiveNet Server, increase it to 16 GB if you want to host two child servers. Also increase the disk capacity based on Performance and scalability details for common deployments.
  • More than two Child Servers must be connected to a single Oracle database instance. The BMC ProactiveNet Server 9.5 must have the following load:

    Load on each BMC ProactiveNet Server

    InstanceAttributes Events 
    1.7 Million250 K350 K per day
  • The following are the requirements to configure the Oracle database instance on a Windows or a Linux operating system:

    Recommended Configuration

    ComponentMinimum requirementMaximum 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 child servers:

     Parameter tuning

    Parameter NameRecommended Size
    memory_target37.5 %
    memory_max_target40% of total System RAM
    Processes1500
    Open_cursors6000
    Db_writer_processes4
    Job_queue_processes30
    Session_max_open_files30
    /dev/shmShould be > 20 GB
    /rootSpace should be > 40 GB
    Table SpacesSpace 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:

    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_targetparameters. 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.

  • If you are installing BMC ProactiveNet 9.5 with multiple Child Servers option, perform the following steps:

    1. Install BMC ProactiveNet Server 9.5 as central server with Central Monitoring Administration and select multiple server option on the Oracle database SID.
    2. Install the BMC ProactiveNet Child Servers on the same Oracle database SID that you had specified in step 1.
  • If you are upgrading to BMC ProactiveNet 9.5 with multiple Child Servers option, you must export or import Oracle Real Application Clusters, 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.

  • When you are migrating the BMC ProactiveNet Server’s database from one instance to another, ensure that you stop the BMC ProactiveNet Server and then export the contents of the database. If the BMC ProactiveNet Server is running during the database export, information may be lost.
  • 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.

  • No labels