Is your Oracle database on the same server as the SCM software?
If no, do you plan to upgrade the Oracle client software on the broker machine at the same time? (The version of Oracle Client you have installed might already be compatible with the new version number for the Oracle server. Check the Oracle Client/Server Compatibility Matrix to be sure)
If the answer to both is no, the only thing necessary is to update your $ORACLE_HOME/network/admin/tnsnames.ora file with the hostname and port number of the new location for your Oracle database.
If your Oracle client software is being updated at the same time (either because the database is on the same machine and the Oracle server software is getting updated, or because you plan to update the Oracle client software at the same time), the steps to take for Linux/Unix would be:
1. Install or upgrade your Oracle client software.
2. Update the environment variables for the Linux/Unix userid that owns the SCM software with the new location for ORACLE_HOME
3. Update your $ORACLE_HOME/network/admin/tnsnames.ora file with the hostname and port number of the new location for your Oracle database.
4. Test to make sure SQL Plus can connect with "sqlplus
[email protected]/password"
5. Re-run $CA-SCM_HOME/install/
install.sh and choose option 3.
6. Run HDBSetup and execute options "CO" (configure ODBC datasource), "TR" (test to make sure the repository can be found), and "EP" (updated the .hsvr.dfo file with the login credentials for the SCM database)
After this, try to start the broker and confirm it is able to start normally using the following:
ps -ef | grep -E 'bkrd|hserver|rtserver'
The steps to take for Windows would be:
1. Install or upgrade your Oracle client software.
2. Update the System environment variables with the new location for ORACLE_HOME
3. Update your %ORACLE_HOME%\network\admin\tnsnames.ora file with the hostname and port number of the new location for your Oracle database.
4. Test to make sure SQL Plus can connect with "sqlplus
[email protected]/password"
5. Run HDBSetup and execute options "CO" (configure ODBC datasource), "TR" (test to make sure the repository can be found), and "EP" (updated the hsvr.dfo file with the login credentials for the SCM database)
After this, try to start the broker service and confirm it is able to start normally using Task Manager.