When Applying the Latest TXK Patches ADOP Apply Phase Fails With Error ' [ERROR] Cannot connect to database Error occurred while calling ad_zd_log.' and '[UNEXPECTED]Error occurred while trying to determine admin node' (Doc ID 2041291.1)

Last updated on JULY 15, 2016

Applies to:

Oracle Applications DBA - Version 12.2.4 and later
Oracle Solaris on SPARC (64-bit)
This is specific to Solaris Sparc operating systems.
Issue occurs when following PATH A step 6 of Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2

On the run edition application tier file system, use hotpatch mode to apply Patch 19330775:R12.TXK.C.Delta.6 merged with Patch 20677045:R12.TXK.C and Patch 20864702:R12.TXK.C (plus additional critical patches - see note box).

$ adop phase=apply patches=19330775,20677045,20864702 hotpatch=yes merge=yes

Symptoms

 E-Business Suite 12.2 Application DBA, Upgrade issues

 

The following ADOP command fails with the below error:

$ adop phase=apply patches=19330775,20677045,20864702 hotpatch=yes merge=yes

[ERROR]     Cannot connect to database
[ERROR]     Error Message :
[ERROR]     *** Error occurred while calling ad_zd_log. Please check log file for the details. ***

[ERROR]     *** Error occurred while calling ad_zd_log. Please check log file for the details. ***
[ERROR]     *** Error occurred while calling ad_zd_log. Please check log file for the details. ***
[ERROR]     *** Error occurred while calling ad_zd_log. Please check log file for the details. ***
[ERROR]     *** Error occurred while calling ad_zd_log. Please check log file for the details. ***
[UNEXPECTED]Error occurred while trying to determine admin node

Changes

 Upgraded E-Business Suite from 11.5.10.2 to 12.2.4.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms