I installed fresh Harvest SCM v13.0.2 on NEW machine/box with Windows Server 2012 R2 -64bit in Testing enviroment.
1. Install and configure Oracle 11g Client -64bit
2. Test database connection - Machine/box able to connect to database
3. Install fresh SCM Server v13 -64bit - Reboot machine
. Install SCM Server v13 Increment 02 -64bit - Reboot machine Problem: Broker and server not running.
The current Harvest database (Oracle 11g) for this Testing environment is the duplicate/backup from current production database that is currently in place by Harvest SCM v12.1
Do I need to run HDBSetup ?
Indeed, you need to run hdbsetup Database Configuration Utility when installing Harvest and specifically on your use case, because you need to upgrade Harvest DB from 12.1.x to 13
Use the hdbsetup Database Configuration Utility for the following reasons:
-Configure ODBC DSN -option CO-
-Upgrade your product database from the 12.x release -option UR-
-Configure your CA Harvest SCM database -option CO-
-Test For SCM Repository Existence -option TR-
-Encrypt DB Username and Password -option EP-
-Load project template information -option LP-
-Load XML form templates -option LF-
hdbsetup will display this menu:
CR Create SCM Repository
CO Configure ODBC DSN
TR Test For SCM Repository Existence
UR Upgrade SCM Repository
CU Create SCM Database User
DR Delete SCM Repository
CM Convert MDB to Standalone
EP Encrypt DB Username and Password
LP Load Projects
LF Load Forms
Run the utility either during or after the CA Harvest SCM server installation. During the product server installation, you are automatically prompted to run hdbsetup after the prerequisite tasks are completed. The utility records all its activities in the hdbsetup.log file in the CA_SCM_HOME\log directory.
If your DBMS is Oracle, CA Harvest SCM uses the service name to connect to local or remote Oracle server. When prompted by the hdbsetup Database Configuration Utility for the service name, do the following:
For a local DBMS server, press Enter to use a blank service name.
For a remote DBMS server, enter the service name that points to the remote server.
Further reading on our online documentation: