Installing a BMC TrueSight Infrastructure Management Server on a separate Oracle instance and merging it into an instance that has another BMC TrueSight Infrastructure Management Server installed


This topic lists the procedure to install a BMC TrueSight Infrastructure Management Server on an Oracle instance and merge it into another Oracle instance that also has a BMC TrueSight Infrastructure Management Server installed.

Assume you have the following deployment scenario:

  • One BMC TrueSight Infrastructure Management Server (bppm-1)
  •  An Oracle database that the BMC TrueSight Infrastructure Management Server uses (instance-a)
  1.  Apply Infrastructure Management 9.6 on bppm-1.
  2.  Create an additional Oracle database instance (instance-b) on the same computer in which the first Oracle database (instance-a) is present.
  3.  On the new Oracle database instance (instance-b), run the following script:

     

    InstallationDirectory\Utilities\oracle\custom_db_scripts_pnet\

    set_system_parameter_oracle_pnet.sql 

    If you are using Oracle version 11.2.0.3, use the set_system_parameter_oracle_pnet.sql script available in the installation directory of Infrastructure Management. The set_system_parameter_oracle_pnet.sql script available in the installation directory of Infrastructure Management works only on Oracle version 11.2.0.2.

    You must be a SYS user or a user with SYSDBA privileges to run this script. This script sets the required Oracle parameters.

  4.  Install a new BMC TrueSight Infrastructure Management Server (bppm-2) and connect to the instance-b database.
  5. Select the Create New User option during the installation. The Create New User option creates the required tablespaces and users on instance-b. 

    BMC recommends you to enter a user name tablespace name different from the one you used while installing bppm-1 with instance-a. This is necessary to ensure that when the second user's information is migrated to the first Oracle database instance, the user names do not clash.
  6. Run the Infrastructure Management Oracle schema creation script  on instance-a as a SYS user:

     

    InstallationDirectory\Utilities\oracle\custom_db_scripts_pnet\

    create_oracle_ts_user.sql

     

    This script creates the additional tablespaces and users for storing the schema of bppm-2.

    Choose the same tablespace and user that you selected when installing bppm-2.

    Note

    If the user name and tablespace name that you entered in step 5 are the same as the ones you used while installing bppm-1 with instance-a, specify a different user name and tablespace name here.

  7.  After installing bppm-2, apply Infrastructure Management 9.6 on bppm-2. This service pack contains a fix for the known issue of supporting multiple BMC TrueSight Infrastructure Management Servers on the same Oracle database at run time.
  8.  Stop bppm-2 by running the pw sys stop command. You can now start the migration process by following the rest of the steps below:
  9.  In the computer in which Oracle is installed, set the SID of instance-b by performing the following steps:
    1.  Set ORACLE_SID=<SID of instance-b>
    2.  Type sqlplus
    3.  Enter user name: sys/<password>@< SID of instance-b> as sysdba
  10.  Run the following SQL script and specify the location of the export dump directory and user at the prompt:

    InstallationDirectory\Utilities\oracle\custom_db_scripts_pnet\

    custom_dump_dir_pnet.sql 

  11.  Update the InstallationDirectory\Utilities\oracle\custom_db_scripts_pnet\pnet_exp_users.par file as follows: 

    SCHEMAS=<instance-b user name>, <instance-b reporting user name>

     

    This creates two files in the PNET_DUMP_DIR directory:

    EXP_ALL_TABLE_DATA.DMP and exp_all_table_data.LOG

  12. Export all the bppm-2 data from instance-b to instance-a by running the following command:

     

    expdp <sys of instance-b>/<password>@< SID of instanceb> PARFILE=<path of the pnet_exp_users.par file>

     

    This step completes the export process. The import process starts from the next step.

  13. Connect to the instance-a database as follows:
    1.  Set ORACLE_SID=<SID of instance-a>
    2. Type sqlplus
    3.  Enter user name: sys/<password>@< SID of instance-a> as sysdba
  14. Run the following SQL script and specify the location of the directory and user after prompting.

    InstallationDirectory
    \Utilities\oracle\custom_table_dump_pnet\

    custom_dump_dir_pnet.sql
  15. Copy EXP_ALL_TABLE_DATA.DMP (created in step 11) to the dump directory created in step 14.
  16. Update the InstallationDirectory\Utilities\oracle\custom_table_dump_pnet\pnet_imp_users.par file as follows:

    #for different Source/Target Tablespace name/Schema name uncomment REMAP parameter and change the name accordingly
    REMAP_TABLESPACE= TS_<instance-b tablespace name>:TS_<instance-a tablespace name>
    REMAP_SCHEMA=<instance-b user name>:<instance-a user name>
    REMAP_SCHEMA=<instance-b reporting user name>:<instance-a reporting user name>
  17. Import all the data to instance-a using the following command:

     

    impdp sys/<password>@< SID of instance-a> PARFILE=<pnet_imp_users.par with full path>

  18. After the data is imported to instance-a, use the pw dbconfig command to change the database configuration of bppm-2 to point to the new user on instance-a as follows:

     

    pw dbconfig set -database oracle -host <host name of oracle server:1521> -sid <SID of instance-a> -username <main user name of instance-a> 
     
    -password <main password> -repusername <report user name of instance-a> -reppassword <report user password>
  19. Start bppm-2.

     

    The bppm-2 system now uses the same Oracle instance (instance-a) that is used by bppm-1.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*