ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

WCC fails to connect to Oracle database after Webui 12.0.01.00 upgrade from WCC 11.4 sp7

book

Article ID: 228317

calendar_today

Updated On:

Products

CA Workload Automation AE

Issue/Introduction

Following yesterdays' successful upgrade from WCC 11.4 SP7 to WebUi 12.0.1 on our Primary WCC server
The upgrade on our Secondary (aka Shadow) WCC 11.4 SP7 instance was as well successful.

However noticed that the CA-wcc process  is failing to connect the Oracle database that it shares with the Primary WCC
Following errors are repeatedly being issued 


INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Nov 10, 2021 5:14:58 PM com.ca.wcc.dbresource.datasource.WccDataSource setPrefix
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | INFO: Initializing datasource for MAIN DB.
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | **********************************************
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Username: c##autosys_master
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Schema Username: null
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Password: ****
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Host: null
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Port: null
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Database name: null
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Platform: ORACLE
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Max active connections: 50
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Initial size: 10
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | DB Access Mode : null
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Path to tnsnames.ora : /u01/app/oracle/product/network/admin
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Server definition name in tnsnames.ora : AUTOSYS_WCC
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Path to CredentialCache : null
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Trust store path : null
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Trust store type : null
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | SSL Server DN match : null
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | MSSQL SSL :
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | MSSQL Encryption :
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | **********************************************
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Nov 10, 2021 5:14:58 PM com.ca.wcc.dbresource.datasource.UnlockingDatasource setParameters
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | INFO: URL= jdbc:oracle:thin:@AUTOSYS_WCC, Driver= oracle.jdbc.driver.OracleDriver
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | Nov 10, 2021 5:14:58 PM com.ca.wcc.dbresource.datasource.WccDataSource registerMBean
INFO   | jvm 1    | 2021/11/10 17:14:58 |        3 | INFO: Trying to create connection pool, retry attempt - 1
INFO   | jvm 1    | 2021/11/10 17:15:11 |       16 | Nov 10, 2021 5:15:11 PM org.apache.tomcat.jdbc.pool.ConnectionPool init
INFO   | jvm 1    | 2021/11/10 17:15:11 |       16 | SEVERE: Unable to create initial connections of pool.
INFO   | jvm 1    | 2021/11/10 17:15:11 |       16 | java.sql.SQLRecoverableException: IO Error: could not resolve the connect identifier  "AUTOSYS_WCC"
INFO   | jvm 1    | 2021/11/10 17:15:11 |       16 |    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:774)
INFO   | jvm 1    | 2021/11/10 17:15:11 |       16 |    at oracle.jdbc.driver.PhysicalConnection.connect(PhysicalConnection.java:688)
INFO   | jvm 1    | 2021/11/10 17:15:11 |       16 |    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:39)
INFO   | jvm 1    | 2021/11/10 17:15:11 |       16 |    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:691)

Environment

Release : 12.0

Component :

Resolution

Issue was that the autosys user (that WCC runs under) was not able to read tnsnames.ora.
Corrected the permissions and this resolved the issue.