Upgrading Harvest on an New Server

Products

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

Issue/Introduction

We have installed Harvest v14.5.01 on a new server, and have connected it to a cloned copy of our production database for testing purposes, while the regular users still do their work using the original Harvest 14.0.2 server. We are ready to complete our upgrade to 14.5.01 by connecting our 14.5.01 server to the production database and upgrade the production database to 14.5.01, making our test server the new production server. Please recommend a general upgrade plan for Harvest from v14.0.2 to v14.5.1 including a rollback plan.

Environment

Harvest Software Change Manager all versions
Windows Server and Oracle database

Resolution

The basic steps will be:

Before the upgrade

Complete user testing
Test all UDP scripts on the new test server to confirm they will work with 14.5.1.
Schedule a maintenance window and notify all users of the down time and that they should be logged off before the maintenance window begins.

At the time of upgrade:

Shut down the Harvest broker, hservers, and rtserver on the current 14.0.2 production server
Shut down the Harvest broker, hservers, and rtserver on the test server
Request that your DBA backup your Harvest database in Oracle.
Once database backup is complete, on the test server, update the tnsnames.ora file if necessary and execute the hdbsetup utility to
- (CO) connect to the production database
- (UR) upgrade the database schema
- (EP) encrypt the database login credentials
Review the %CA_SCM_HOME%\log\updateschema.log file to ensure the database schema upgrade succeeded.
Startup Harvest on the test (new production) server
Once HServers are started, connect with Workbench to ensure connectivity and that the database schema upgrade was successful.
Notify users that the maintenance window is complete and that they can now login to Harvest with the new brokername for the new production (previously test) server.

If any problems were found and a rollback of the upgrade is needed this can be accomplished by restoring the Harvest database schema from the backup and restarting the Harvest software on the old production server.