Adop Exiting With Status = 2 (Fail) (Doc ID 1967441.1)

Last updated on JULY 25, 2016

Applies to:

Oracle Applications DBA - Version 12.2.4 to 12.2.4 [Release 12.2Cloud]
Information in this document applies to any platform.

Symptoms

With E-Business Suite 12.2.4, the adop utility is failing with the error message

Log file: /ERPP/applerpp/fs_ne/EBSapps/log/adop/adop_20150131_205257.log
[START 2015/01/31 20:52:57]Arguments passed to adop
  phase=apply hotpatch=yes options=nocopyportion,nogenerateportion,forceapply
[END 2015/01/31 20:52:57]Arguments passed to adop
[START 2015/01/31 20:52:57] Performing verification of parameters
[END 2015/01/31 20:53:15] Performing verification of parameters
[STATEMENT] Sourcing the Run Edition environment: /ERPP/applerpp/fs2/EBSapps/appl/APPSERPP_ora12.env
[EVENT] [START 2015/01/31 20:53:16] Checking for the required ENV setup
[EVENT] [END 2015/01/31 20:53:16] Checking for the required ENV setup
[STATEMENT] Using 4 workers (Default: 4, Recommended maximum limit: 188)
[PROCEDURE] [START 2015/01/31 20:53:16] Determining admin node
  [STATEMENT] Admin node : "<domain name>"
[PROCEDURE] [END 2015/01/31 20:53:16] Determining admin node
Validation successful. All expected nodes are listed in ADOP_VALID_NODES table.
[UNEXPECTED]adop is not able to detect any application tier nodes in FND_NODES table.
[UNEXPECTED]Ensure ICM is running and run autoconfig on all nodes
[UNEXPECTED]Error while checking if this is a multi node instance

 

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