Upgrading Oracle Client Software on the Broker Machine
search cancel

Upgrading Oracle Client Software on the Broker Machine

book

Article ID: 280242

calendar_today

Updated On:

Products

CA Harvest Software Change Manager CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

After upgrading Harvest to the latest release, we are finding that the version of Oracle Client on the Harvest broker machine is very old and no longer compatible with the latest version of Oracle server or with Harvest.  What are the steps to upgrade the Oracle Client software and then reconfigure Harvest to use it?

Environment

Harvest Software Change Manager all versions

Resolution

On the broker machine, install the Oracle Client.  Be sure to select the same version as your Oracle Server software.  If your Harvest broker software is the 64-bit version, you will need the 64-bit version of the Oracle Client.  For 32-bit Harvest broker you will need 32-bit Oracle Client.

Copy the tnsnames.ora file from your previous version of Oracle client's network\admin folder to the new version's network\admin folder.  Or ensure it is accessible using the TNSADMIN environment variable to indicate the correct location of the tnsnames.ora file.  If your operating system is Linux or Unix, ensure that this file is world-readable.

Once the Oracle client is installed, execute the %CA_SCM_HOME%\HDBSetup.exe utility ($CA_SCM_HOME/bin/hdbsetup for Linux/Unix) and select following options;

  • CO to configure the ODBC data source to use the new 19c ODBC drivers
  • TR to ensure we could connect to the Harvest database
  • EP to encrypt the username and password for connecting to Oracle

After this, test to ensure you can start the broker and HServers and that SCM is accessible via command line utilities or Workbench.