How do I reconfigure CO to change the database user passwords or update the database instance configuration information?

Version 3

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    TrueSight Capacity Optimization


    Capacity Optimization


    BMC TrueSight Capacity Optimization 10.x and 11.x; BMC Capacity Optimization 9.5.02


    Which steps are needed to reconfigure the TrueSight Capacity Optimization (CO) version 10.x or BMC Capacity Optimization version 9.5 database
    instance information or change the database user password

    For example, what is the process to point the CO Application Server to the database instance after it has been moved to a new server (or the hostname
    of the database server has changed) or update the database username and/or password that CO uses to access the database?



    IMPORTANT NOTE: When changing the "Database Schema Owner" database account's password it is necessary to reconfigure all of the servers that are part of the TrueSight Capacity Optimization (TSCO) instance (All Application Servers and ETL Engine Servers).


    Updating the database passwords within the TSCO configuration files if they have already been changed by the DBA


    In TSCO 10.5 or newer, the following link to the product documentation describes how to to update the database password within the TSCO configuration if it has already been changed by your DBA:

      Validate database connection using Database Credentials Tool  
    The command should be run on the TSCO Application Servers first and then on the TSCO ETL Engines.  The utility can only update the TSCO database user password if it has already been changed on the database side.  To update the TSCO database user passwords on the database side and change them within the TSCO configuration it is necessary to run the in Reconfigure mode. 

    Changing Database Instance Information or updating the TSCO database user passwords within the database and within the TSCO configuration

    For information on changing the password in TSCO 9.5 and earlier see the   Database passwords changes section at the end of the document.  

    If the TSCO database has been moved to a new server or migrated to a new instance, as first step, you should manually change the tnsnames.ora file or validate that the appropriate entry is there, or ask to DBA to do this.

    Typically only the DBA will have access to modify this file (although any Oracle Client user should have access to view it).


    After, you have to run the TSCO installer similar to performing an install or an upgrade (please refer to official documentation of your TSCO version).

    The only officially supported method to change the TSCO database instance information (database hostname, instance/service name, or TNS name) is by running the in Reconfigure mode as described below.


    Select "Reconfigure BMC Capacity Optimization" when you will be in step "Existing installation detected"





    When you will be in the step "Oracle Database Information" change the parameters you need.



    A the end of the configuration, all BCO services will be restarted.


    There are no additional operations to do after the run of the installer


    Note: DB passwords changes

    These steps are required only for version 9.0. The newer versions automatically detect if the password has been already changed by the DBA  

    The reconfigure is able to change the passwords of the DB users (BCO_OWN, BCO_REP, BCO_DASH).  When changing the password for the
    BCO_OWN, BCO_REP, or BCO_DASH accounts the BCO installer reconfigure expects to be able to log into the database as each of these
    accounts using the previously valid password, and then issue the password change command.  This means that if the DBA has already
    changed the password outside of the BCO installer reconfigure wizard it will be necessary to tell the installer what the new passwords are
    so it can log into the database.


    The recommended method to change the password for the BCO_OWN, BCO_REP, and BCO_DASH users is to use the BCO installer reconfigure
    wizard to make the password change within the database.  The GUI will both make the password change and update the necessary configuration
    files within BCO with the updated password.


    Note that the BCO installer reconfigure must be run on both the BCO Application Server first and then run on all BCO ETL Engine servers.  On the BCO 
    ETL Engine server side it will not request the current password it will request the network address and port of the BCO console and the installer will
    extract the updated password from the database.


    If you need to change the password, you can follow two ways:

      1. If the DBA allows the change of the password through the installer reconfiguration, you can run it and after type the new passwords in the  
    right fields. The password will be changed as fist step on database, afterwards all the configuration files will be changed with the new passwords 
    2. If the DBA wants to change the passwords, follow these steps 
    • Get the new passwords from DBA
    • Go in the directory with the installation packages (the same with the reconfigure tool) and run the script

    Please type plain text and press enter:

       After entering the new passwords the command will output the encrypted version as seen above 
    3. Go into BCO installation directory (default is    /opt/bmc/BCO/) and edit the file    BCOInstalledConfiguration.xml
      Change the current passwords with the new encrypted ones. They are in these 3 tag (OWN, REP, DASH)  
    4. Run the installer and perform the reconfigure. Remember to type the new db password.  
      NOTE: It is recommended that if the DBA has manually changed the password for the BCO_OWN user outside of the Reconfigure
    that when the Reconfigure is run a new different password for the BCO_OWN user is specified in the Reconfigure GUI
    (a password that is different than the password that the DBA changed to BCO_OWN account to use).  This will both update the password
    for the BCO_OWN database user and push that new password into the BCO configuration files.  Some environments have experienced
    problems with the BCO ETL Engines (EE) locking the BCO_OWN account even after the Reconfigure has been run on them
    when the DBA has changed the password manually for the BCO_OWN user and then the Reconfigure has been used to propagate
    that password into the BCO AS configuration files.  This is because the Reconfigure run on the EE ends up extracting an old
    cached password from the BCO database due to the lack of an apparent password change during the Reconfigure execution.
      OPTIONAL: If the reconfigure has been run without changing the password (so using the same password the DBA changed the password  
    to manually) then it is recommended, particularly for CO 9.5.02, to re-enter the passwords under  
    Administration -> System -> Maintenance -> Global Configuration -> General Tab for the "Database Password" and then restarted the BCO Web  
    component.  This is because in some situations when the password hasn't been updated via the reconfigure run it fails to update the  
    passwords within the CO database (so it updates the password in the local configuration files on the AS, so the AS components work properly,  
    but it doesn't update the password in the database itself which is the password downloaded by the reconfigure run on the ETL Engine Server. 

    Changing the password on the BCO ETL Engine or Presentation AS machines


    After changing the password for the BCO_OWN user it is necessary to run the Reconfigure on each of the ETL Engine or Presentation AS (Non-primary AS)
    servers in the environment.  The Reconfigure will not require the updated password to be entered -- it will instead download it from the BCO Primary AS server.

    Additional Password Notes

    Note that for BCO 9.5.02 the BCO_OWN database user's password should not include a '$' as it can cause sqlldr to fail with a bad username/password error.   
    Also, we're experienced problems when the password contained an '@' character as that caused sqlplus and sqlldr to fail with an error that the TNS name of the 
    database couldn't be resolved.  Results may differ depending on the product version, patch level, and environment. 

    Related Products:  
    1. BMC TrueSight Capacity Optimization
    3. BMC Capacity Management
       Legacy ID:KA380046


    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles