Setting global_names to true for Oracle databases

Before you set the global_names parameter to true, ensure that the db_domain parameter is configured for the database instances in the environment (BMC Server Automation, the reports data warehouse, and the portal content store instances). Log on to each database server as a sysdba user and type the following query:

The value of db_domain is returned. This value should not be blank and should be the appropriate value for your site configuration.

If the db_domain parameter is not configured properly, work with the database administrator to configure it properly for your environment.

To set the global_names parameter to true

1. Log on to your database as a sysdba user and type the following query:

   Alter system set global_names = true scope=both;

2. Ensure that the ORACLE_HOME/network/admin/tnsnames.ora file on all database servers in your BMC Decision Support for Server Automation installation contains the connection information (TNS Alias) for the BMC Server Automation instance, the reports data warehouse instance, and the portal content store instance. 

   The same connection information must be used for all instances, as illustrated in the following examples:

   CP =
     (DESCRIPTION =
       (ADDRESS = (PROTOCOL = TCP)(HOST = bldb-ora-01.bmc.com)(PORT = 1521))
       (CONNECT_DATA =
         (SERVER = DEDICATED)
         (SERVICE_NAME = cp.bmc.com)
       )
     )
   
   BLDW =
     (DESCRIPTION =
       (ADDRESS = (PROTOCOL = TCP)(HOST = bldb-ora-01.bmc.com)(PORT = 1521))
       (CONNECT_DATA =
         (SERVER = DEDICATED)
         (SERVICE_NAME = blrdw.bmc.com)
       )
     )
   
   BLOGIC =
     (DESCRIPTION =
       (ADDRESS = (PROTOCOL = TCP)(HOST = bldb-ora-01.bmc.com)(PORT = 1521))
       (CONNECT_DATA =
         (SERVER = DEDICATED)
         (SERVICE_NAME = blogic.bmc.com)
       )
     )

To configure database link for ETL when  global_names is true

When global_names parameter is set to true in BSA and BDSSA databases, perform the following steps for the ETL to work successfully:

1. Create a new database link with the same name as the BSA database on BDSSA_DW database. For example, ORA121DB.
2. Update the BSA_SITE1_SOURCE_DATABASE_LINK_NAME parameter in the "...\BDSSA\shared\ConfigurationManagement\bds.properties file with the new database link name. For example, BSA_SITE1_SOURCE_DATABASE_LINK_NAME=ORA121DB
3. Update the LINK_NAME field in the BL_SITE table in the BDSSA_DW database, with the new database link name, for the corresponding BL_SITE_ID.
   UPDATE BDSSA_DW.BL_SITE SET LINK_NAME = 'ORA121DB' WHERE BL_SITE_ID = 1;
4. Update the DSERV_NAME field in the SNP_CONNECT table in the BDSSA_ETL_MASTER database with the new database link name WHERE I_CONNECT=3000.
   UPDATE BDSSA_ETL_MASTER.SNP_CONNECT SET DSERV_NAME = 'ORA121DB' where I_CONNECT = 3000;
   where I_CONNECT value should be corresponding to the added site.
5. Run ETL and ETL should be successful.