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.

Changing multiple databases

When changing multiple databases (connection string parameters such as host name, port, or instance name), using the Report Administration Utility, you must run the commands in a specific sequence to modify all of the databases. 

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

databases have dependencies on each other. If you change multiple database settings at the same time, you need to run the Report Administration Utility commands in the correct sequence to ensure that each database change is complete.

This topic describes the following database change scenarios:

Use the instructions that meet your database change scenario. For command syntax, use the command line help.

Notes

  • Before using these instructions, review the requirements for modifying the portal content store (see Modifying-the-parameters-for-the-portal-content-store).
  • With the exception of the portal content store, when you are creating new databases, you must use backups to restore the database to the latest configuration.

To change warehouse, portal content store, and ETL repositories if they reside on the same database servers

  1. If you are using an Oracle database, complete the following steps:
    1. On the reports server, make a backup copy of the tnsnames.ora file.
       The file is usually located in the ORACLE_HOME\NETWORK\ADMIN directory.
    2. Update the tnsnames.ora file with the new connection string information for the 

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

      database and the 

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

      databases.
  2. If you are changing the 

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

    database, perform the following steps:
    1. If a linked server (database link) exists, drop it.
    2. Create the linked server (database link) to point to the new 

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

      database (see Creating-a-linked-server-for-the-BMC-Server-Automation-databases).
  3. Run the 

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

    .
  4. Run the set dbinfo command.
  5. Exit the Report Administration Utility and then run it again. This ensures that the Report Administration Utility has read the latest information.
  6. If you have multiple 

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

    sites, run the set context command for each site or, if you only have the primary 

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

    site, run the set context command for that site.
  7. Try logging on to 

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

    .
     If you are able to log on successfully, your changes were successful.

To change warehouse, portal content store, and ETL repositories if they reside on different database servers

  1. If you are using an Oracle database, complete the following steps:
    1. On the reports server, make a backup copy of the tnsnames.ora file.
       The file is usually located in the ORACLE_HOME\NETWORK\ADMIN directory.
    2. Update the tnsnames.ora file with the new connection string information for the 

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

      database and the 

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

      databases.
  2. If you are changing the 

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

    database, perform the following steps:
    1. If a linked server (database link) already exists, drop it.
    2. Create the linked server (database link) to point to the new 

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

      database (see Creating-a-linked-server-for-the-BMC-Server-Automation-databases).
  3. Run the 

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

    .
  4. Run the set warehouse command.
     The command makes some of the required changes to configuration files, but other database detail changes are not yet complete and some errors are displayed in the command output.
  5. Run the set portalcontentstore command.
     The portal content store changes are complete.
  6. Run the set etldb command.
     The ETL master and work repository changes are complete.
  7. Run the set warehouse command.
     The data warehouse changes are complete.
  8. Exit the Report Administration Utility and then run it again. This ensures that the Report Administration Utility has read the latest information.
  9. If you have multiple 

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

    sites, run the set context command for each site or, if you only have the primary 

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

    site, run the set context command for that site.
  10. Try logging on to 

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

    .
     If you are able to log on successfully, your changes were successful.

To change warehouse and portal content store or changing warehouse and ETL repositories if they reside on different database servers

Use the following command sequence when making one of the following combinations of database changes:

  • Changing the data warehouse and the portal content store
  • Changing the data warehouse and the ETL master and work repositories
  1. If you are using an Oracle database, complete the following steps:
    1. On the reports server, make a backup copy of the tnsnames.ora file.
       The file is usually located in the OracleHome\NETWORK\ADMIN directory.
    2. Update the tnsnames.ora file with the new connection string information for the 

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

      database and the 

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

      databases.
  2. If you are changing the 

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

    database, perform the following steps:
    1. If a linked server (database link) already exists, drop it.
    2. Create the linked server (database link) to point to the new 

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

      database (see Creating-a-linked-server-for-the-BMC-Server-Automation-databases).
  3. Run the 

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

    .
  4. Run the set warehouse command.
    The command makes some of the required changes to configuration files, but other database detail changes are not yet complete and some errors are displayed in the command output.
  5. Run one of the following commands based on the database changes you are making:
    • Run the set portalcontentstore command.
       or
    • Run the set etldb command.
       The database changes are complete.
  6. Run the set warehouse command.
     The data warehouse changes are complete.
  7. Exit the Report Administration Utility and then run it again.
    This ensures that the Report Administration Utility has read the latest information.
  8. If you have multiple 

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

    sites, run the set context command for each site or, if you only have the primary 

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

    site, run the set context command for that site.
  9. Try logging on to 

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

    .
     If you are able to log on successfully, your changes were successful.

 

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