Setting global_names to true for Oracle databases

After completing all post-installation steps, you can set the global_names parameter to true for Oracle databases, if you need this setting for your environment.

Before the product installation, you were instructed to set global_names to false for your Oracle databases. After you install the product, change the global_names parameter to true for those databases.

Before you begin

Before beginning this procedure, ensure that the db_domain parameter is configured for the database instances in the environment (

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 

   The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

   installation contains the connection information (TNS Alias) for the BMC Server Automation instance, the 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)
       )
     )

3. Create a link between the reports data warehouse and the 

   The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

   database by logging on to the data warehouse as the BSARA_DW user (you might have changed the user name at your site) and running the following command:

   CREATE DATABASE link <dbLink_name> connect TO <user> identified BY <password> USING '<global_name>';

   • <dbLink_name> is the database link name.
   • <user> and <password> are the 

     The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

     user name and password for logging on to the 

     The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

     database.

   • <global_name> is the global name for the 

     The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

     instance.
     In the following example, the database link name is bladelink, the user name is bladelogic, the password is sa, and the 

     The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

     instance's global_name is bladelogic.int.bmc.com.

     CREATE DATABASE link bladelink connect TO bladelogic identified BY sa USING 'bladelogic.int.bmc.com';

4. Verify that the links are created by running the following query on each database server:

   SELECT count(*) FROM agent_state@<global_name>f;

   If the link was created successfully, some table rows are returned. The table row information can vary, for example, you might see an agent_state table.

5. Run the Report Administration Utility gencred command to renew credentials and then the set contextcommand to set the primary 

   The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

   database site's context for data transfer.
   
   For information about Report Administration Utility commands, see Report-Administration-Utility-commands. When you run the commands, your session should look similar to the following example, in which the authentication type is SRP, the site name is Primary, and the database global_name is bladelogic.int.bmc.com. Substitute the correct values for your installation.

   blrptadmin> gencred
   Enter options for gencred
   Enter GlobalReportAdmin Site: Primary
   Enter GlobalReportAdmin User Name: BLAdmin
   Enter GlobalReportAdmin role name: GlobalReportAdmins
   Enter authentication type: 1
   Enter password:
   
   User credentials file bmcsareports_user.dat generated successfully.
   File is placed under : /root/.bmcsareports
   Make sure only user has permissions to file.
   
   blrptadmin> set context
   Enter options for set context
   Enter site name: Primary
   Enter linked server name: bladelogic.int.bmc.com
   Enter database type (sqlserver | oracle): oracle
   Enter database user: bladelogic
   Enter database password:
   Accept argument for command:JDBC Connection Params For ORACLE JDBC Url (y/n):y
   Enter options for set context
   Enter JDBC URL: jdbc:oracle:thin:@database.bmc.com:1521:BLADELOGIC
   Database link bladelogic.int.bmc.com tested successfully
   Set context successfully.

   If you are using Oracle RAC, your JDBC URL should look like the following:

   jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=db1.bmc.com)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=db2.bmc.com)(PORT=1521))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=db.bmc.com)))
6. Restart the reports server.
7. Run ETL.