Second WCC node install fails claiming a Reporting DB failure to connect
search cancel

Second WCC node install fails claiming a Reporting DB failure to connect

book

Article ID: 191609

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Workload Automation AE

Issue/Introduction

When using the Oracle TNS option, having installed the first WCC node successfully where the WCCDB and ReportingDB are shared on one Database, the following error is seen when installing a second WCC node:

***  HA mode detected  ***
**************************
Another instance of CA WCC is connected to the database you specified.
If you continue with the installation, this instance of CA WCC will be
installed as a member of the CA WCC cluster.
The Reporting database and CA EEM settings will be copied from the first CA WCC
instance.
Do you want to continue? (Y/N): Y
******************************************************************************
*
The Reporting database is not shared with WCC database. All available
Reporting database parameters were automatically retrieved from other HA node.
Please review the database settings and fill-in the parameters specific to
local machine.

tnsnames.ora directory path (Default: /path/oracle/network/admin/):
Net service alias : <ORACLE_SID> (non-editable)
User :  (non-editable)

******************************************************************************
*
***  Reporting database error  ***
**********************************
The database is not responding. Please enter the correct information and
continue.

Error details:
ORA-01017: invalid username/password; logon denied

---- 

The error claims the ReportingDB is not shared with the WCCDB despite the fact that it is shared and being used by the Primary WCC node. The details are being imported automatically and cannot be edited.

Environment

Release : 11.4 SP7

Component : WORKLOAD CONTROL CENTER

Cause

This error occurs when using Oracle TNS and the following parameters in the $CA_WCC_INSTALL_LOCATION/data/config/application/config/resources/connection.properties file do not match exactly:

wcc.database.tnspath=
reporting.database.tnspath=

In the particular case where this issue was reported, a forward slash was missing at the end of the 'reporting.database.tnspath' value.

Example:

wcc.database.tnspath=/path/oracle/network/admin/
reporting.database.tnspath=/path/oracle/network/admin

This small mis-match lead to WCC interpreting the WCC and Reporting databases as not shared. This was confirmed with the following query on the shared WCCDB/ReportingDB which gave a value of "false":

SELECT prefvalue FROM cfg_global_pref where PREFKEY='internal.reportingDBShared';

PREFVALUE                                                                       
--------------------------------------------------------------------------------
false

The missing backslash also lead to a malformed jdbc string when trying to connect to the ReportingDB, which resulted in the 'ORA-01017: invalid username/password; logon denied' error.

Resolution

Check the reporting.database.tnspath value in the $CA_WCC_INSTALL_LOCATION/data/config/application/config/resources/connection.properties file and make sure it matches the wcc.database.tnspath value, including any slashes and removing any hidden spaces.

Restart the WCC services on the Primary WCC for the change to take effect.

After this, you should see the database query return a value of "true" :

SELECT prefvalue FROM cfg_global_pref where PREFKEY='internal.reportingDBShared';

PREFVALUE                                                                       
--------------------------------------------------------------------------------
true


The secondary WCC will now be able to proceed with the installation.


Additional Information

It is worth checking the $CA_WCC_INSTALL_LOCATION/data/config/application/config/resources/connection.properties file on both nodes after the installation and double checking that all the aforementioned parameters match.