Using global_names parameter for Oracle databases


If your company policy requires global_names parameter to be set back to true after the TrueSight Server Automation - Data Warehouse installation is completed, your database administrator must do the following:

  1. Log in to SQL Plus as the sysdba user on the Oracle database instance where the TrueSight Server Automation user is located.
  2. Set the value of the global_names parameter to true by using the following query:
    Alter system set global_names = true scope=both;commit;
  3. On the database server in your TrueSight Server Automation - Data Warehouse environment, navigate to the ORACLE_HOME/network/admin directory.
  4. Ensure that the tnsnames.ora file contains the connection information (TNS Alias) for the TrueSight Server Automation instance and the TrueSight Server Automation - Data Warehouse instance. 

    Click here for an example of the connection information.
    BLDW =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = bldb-xxx-xx.bmc.com)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = blrdw.bmc.com)
        )
      )

    BLOGIC =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = bldb-xxx-xx.bmc.com)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = blogic.bmc.com)
        )
      )
  5. Configure the database link.
    1. In the TrueSight Server Automation - Data Warehouse database, create a new database link with the same name as the TrueSight Server Automation database by running the following command:
      CREATE DATABASE link <dbLink_name> connect TO <user> identified BY <password> USING '<global_name>';where,

      • <dbLink_name> is the database link name.
      • <user> and <password> are the TrueSight Server Automation user name and password for logging on to the TrueSight Server Automation database.
      • <global_name> is the global name for the TrueSight Server Automation instance.

      Query example: CREATE DATABASE link ORA121DB connect TO bladelogic identified BY sa USING 'ORA121DB';

    2. Navigate to the following directory: <TSSA-DWInstallationDirectory>\TSSA-DW\shared\ConfigurationManagement
    3. Open the bds.properties file and update the TSSA_SITE1_SOURCE_DATABASE_LINK_NAME parameter with the new database link name.
      For example, TSSA_SITE1_SOURCE_DATABASE_LINK_NAME=ORA121DB.
    4. In the BL_SITE table, update the LINK_NAME field with the new database link name for the corresponding BL_SITE_ID.

      UPDATE TSSADW_DW.BL_SITE SET LINK_NAME = '<newDbLink>' WHERE BL_SITE_ID = <SiteID>;
      For example, UPDATE TSSADW_DW.BL_SITE SET LINK_NAME = 'ORA121DB' WHERE BL_SITE_ID = 1;
    5. In the dwh_connect_info table, update the LINK_NAME field with the new database link name for the corresponding CON_NAME.
      update dwh_connect_info SET DB_LINK_NAME = '<newDbLink>' WHERE CON_NAME = <CON_NAME>;
      For example, update dwh_connect_info SET DB_LINK_NAME = 'ORA121DB' WHERE CON_NAME='BSA_phy_om_svr_site1';
    6. Exit the command prompt.

      Exit
  6. Run the ETL process. 
  7. Verify that the ETL process is successful. Do the following:
    1. As a TrueSight Server Automation - Data Warehouse administrator (DWAdmin), launch the TrueSight Server Automation - Data Warehouse console.
    2. Click ETL Management > ETL Status to check the status.


 

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