WCC 11.4.1 Upgrade Fails with Oracle time out.

Article Id: 38993
Status: Published
Updated On: 14-02-2018 07:55
Legacy Id: TEC1093615
Products:
CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation Agent
Issue/Introduction:

Issue:

The upgrade from WCC 11.3.5 INC2 to WCC 11.4sp1 (or SP2) fails with Oracle login timeout error. 

Usually, no traffic is seen on the network going to the database servers. The error can be against the WCC database (like below), the Reporting Database and may also occur when accessing EEM. 

2015-11-19 15:10:29 : DatabaseUtil:: reporting.database.username = WCCADM 
2015-11-19 15:10:29 : DatabaseUtil:: reporting.database.tnspath = /database/oracle/opt/tnsnames.ora 
2015-11-19 15:10:29 : DatabaseUtil:: setting $WCC_TNSNamesFilePath$ to </database/oracle/opt/tnsnames.ora> 
2015-11-19 15:10:29 : DatabaseUtil:: testDBConnection - Begin
2015-11-19 15:10:29 : DatabaseUtil:: getDBConnection - Begin 
2015-11-19 15:10:29 : DatabaseUtil:: Driver class name: com.ca.wcc.jdbc.oracle.OracleDriver 
2015-11-19 15:10:29 : DatabaseUtil:: getSelectedDBConnectionString - Begin 
2015-11-19 15:10:29 : DatabaseUtil:: Substitute on $WCC_TNSNamesFilePath$ yields </database/oracle/opt/tnsnames.ora> 
2015-11-19 15:10:29 : DatabaseUtil:: Generated URL = jdbc:ca:oracle:TNSNamesFile=/database/oracle/opt/tnsnames.ora;TNSServerName=WCCQA02 
2015-11-19 15:10:29 : DatabaseUtil:: getSelectedDBConnectionString - Return 
2015-11-19 15:10:43 : DatabaseUtil:: Trying to establish connection second time.. 
2015-11-19 15:10:43 : DatabaseUtil:: getSelectedDBConnectionString - Begin...

Cause:

This kind of error may happen when entropy is low. 

On Linux, random number generation is affected by the entropy value, which in turn is affected by random events. On virtual machines, the entropy value can be very low (below 200) which causes random numbers to be generated slowly. As a result, it can take as long as 30 minutes for CA WCC to generate the encrypted connection with the database. 

 

Resolution: 

Run the following command to find out what your entropy number is. 

cat /proc/sys/kernel/random/entropy_avail 

For Red Hat Linux, rng-tools is included with the installation DVD. Alternatively, rng-tools is available from :

http://sourceforge.net/projects/gkernel/files/rng-tools/

then run either: 

rngd -r /dev/urandom -o /dev/random -b -t 3

or

rngd -r /dev/urandom -o /dev/random -b 

 

The upgrade should then work. 

 

Environment:

Release: ATSYHA99000-11.4-Workload Automation AE-High Availability Option
Component: