We are currently performing Oracle upgrade from 11g to 12c. We are not upgrading the Harvest product. (Current version 12.6). Do we really need to upgrade the Harvest SCM repository as well post the DB upgrade ?

[Legacy User]

Is SCM repository upgrade required post the upgrade of Oracle Database from 11g to 12c ?

[Legacy User]

Hi, @Jagan M,

 

thank you for contacting us through our Community channel. One of our Harvest engineers will review your question and will provide an answer very soon.

 

Regards, Iuliana

[Eduard-de-Quadras]

Hello Jagan,

If you are using Oracle and you are upgrading from an earlier release of CA Harvest SCM, then you would need to upgrade Harvest respository.
Fo further details on how to go through this process, please review our online documentation:
https://docops.ca.com/ca-harvest-scm/13-0/en/installing/configure-the-database/configure-the-repository-using-the-hdbsetup.

Let me know if this helps.

Thanks,

Eduard

[Legacy User]

Hi Eduard,

 

Thanks for your quick reply. 

 

We are not upgrading Harvest from earlier release. DBA team is upgrading the database of Harvest from 11g to 12c. Currently we are using Harvest DB running on oracle 11g, after upgrade of DB Harvest will be running on oracle 12c. Harvest version is not being updated.

 

What's the approach in the above scenario ?

 

Thanks,

MJ

[Eduard-de-Quadras]

Hi Jagan,

There is no need to upgrade Harvest respository if you are just upgrading Oracle DB.

Harvest 12.6 supports up to Oracle 12c R1 (12.1.0.1).  

 

TECH TIP: Caveats with Harvest and Oracle 12c 

 

Thanks,

 

[Melinda Skelton]

There are a lot of factors that determine how much will need to be done with Harvest so that it can connect to your Oracle database after it has been upgraded:

- Is your Oracle database on the same server with your SCM Broker?

- If both are on the same server, is it a Windows operating system?

- Do you intend to also upgrade the Oracle client software on the broker machine?  (if Oracle and SCM are on the same server and it's a Windows operating system this is an automatic "Yes")

 

The simplest scenario is if your SCM Broker is on a Linux or Unix server, and you do not intend to also upgrade the Oracle client software.  In this case, all you will need to do is update your $ORACLE_HOME/network/admin/tnsnames.ora file so that the service name paragraph contains the correct hostname and port number for your upgraded Oracle database.  After this you will need to restart your SCM Broker. No further change would be necessary.

 

If your SCM Broker is on a Linux or Unix server, and you also intend to upgrade the Oracle client software on the broker machine, you would need to:

- Shut down the SCM Broker, HServers and RTServer.

- Upgrade the Oracle client software

- Set up the new $ORACLE_HOME/network/admin/tnsnames.ora file to point to the hostname and port number of your upgraded Oracle database.  Make sure this file is world-readable (chmod 755 ...)

- Test the connection using "sqlplus <userid>/<password>@<servicename>.  If SQL plus cannot connect, then SCM will not be able to connect either.

- Update the SCM Software owner's user profile (.profile or .bash_profile) to have the correct values for ORACLE_HOME, ORACLE_SID, PATH (should include the new $ORACLE_HOME/bin), LD_LIBRARY_PATH (should include the new $ORACLE_HOME/lib), LIBPATH (on AIX, should include the new $ORACLE_HOME/lib).

- Login as the SCM Software owner with the newly updated profile

- Reinstall SCM's odbc module (odbc.tar.gz or caiptodbc.tar.gz).  This will reconfigure it to pick up the new Oracle client's ODBC drivers.

- Navigate to $CA_SCM_HOME/install, and execute "./install.sh".  Select option "3".  This will update all the scripts in the $CA_SCM_HOME/bin folder with the new location for $ORACLE_HOME.

- Navigate to $CA_SCM_HOME/bin and execute "./hdbsetup".  Select option "CO" to configure and test the new ODBC data source information.

 

If your SCM Broker is on a Windows server and you do not intend to also upgrade the Oracle Client software, the only thing to be done is update your %ORACLE_HOME%\Network\admin\tnsnames.ora file so that the service name that SCM uses is pointing to the correct hostname and port number, and then restart the SCM Broker service.

 

If your SCM Broker is on a Windows server and you do intend to also upgrade Oracle Client, the steps would be:

- Shut down the SCM Broker service

- Upgrade the Oracle Client software

- Set up the new %ORACLE_HOME%/network/admin/tnsnames.ora file to point to the hostname and port number of your upgraded Oracle database.

- Test the connection from a command prompt window using "sqlplus <userid>/<password>@<servicename>.  If SQL plus cannot connect, then SCM will not be able to connect either.

- Update the System environment variables have the correct values for ORACLE_HOME, ORACLE_SID, and PATH (should include the new %ORACLE_HOME%/bin)

- Use the ODBC Data Source Administrator tool (for 64-bit SCM and Oracle, or 32-bit SCM and Oracle on a 32-bit machine execute C:\Windows\System32\odbcad32.exe; for 32-bit SCM and Oracle on a 64-bit machine execute C:\Windows\Syswow64\odbcad32.exe).  On the System DSN tab, drop the existing data source for SCM and create a new one with the same name that will use the new version of the Oracle ODBC driver and the correct TNS Service name to your SCM database.

- Restart the broker and use Task Manager to assure all HServers are able to start correctly.

 

If you have any trouble getting the SCM Broker or HServers to start after completing this change, here is an article with tips on how to troubleshoot the problem: Tuesday Tip: When your broker won't start - troubleshooting tips 

[Legacy User]

My case would be the simplest scenario explained above. This helps Melinda. Thanks for your response. We can cancel our quick call, I'll reach out to you if I face any issues during the upgrade. Scheduled time - 2AM ET to 10AM ET (26th August).