ADOP Patching Fails Due To ETCC Error During The Apply Phase ' [ERROR] ETCC not run in the database node'

Applies To:

Oracle Applications DBA - Version 12.2 and later
Information in this document applies to any platform.

Symptoms:

E-Business Suite 12.2.x, Online Patching ADOP Utilities issues ETCC errors when applying a patch in Apply phase.

Receiving an ETCC error while executing the following ADOP command:

$ adop phase=apply apply_mode=downtime patches=21865610

ERROR
-----------:
Validating credentials.

Initializing.
Run Edition context :/d01/oracle/inst/fs1/inst/apps/odbdev_oadev/appl/admin/odbdev_oadev.xml
Patch edition context: /d01/oracle/inst/fs2/inst/apps/odbdev_oadev/appl/admin/odbdev_oadev.xml
Reading driver file (up to 50000000 bytes).
Patch file system free space: 45.86 GB

Validating system setup.

Node registry is valid.
[ERROR] ETCC not run in the database node odbdev
The EBS Technology Codelevel Checker needs to be run on the database node.
It is available as Patch 17537119.

Encountered the above errors when performing database validations.
Resolve the above errors and restart adop.


STEPS
------:

The issue can be reproduced at will with the following steps:

1. Running the Apply phase.

Cause:

The ETCC scripts had not been successfully run prior to applying the patch.

1. Patch error:

[ERROR] ETCC not run in the database node odbdev
The EBS Technology Codelevel Checker needs to be run on the database node.
It is available as Patch 17537119.

2. ETCC error:

[oracle@odbdev ~]$ checkMTpatch.sh

+===============================================================+
| Copyright (c) 2005, 2016 Oracle and/or its affiliates. |
| All rights reserved. |
| Oracle E-Business Suite Release 12.2 |
| Middle Tier Technology Codelevel Checker |
+===============================================================+

Using context file from currently set applications environment:
/d01/oracle/odbdev/db/tech_st/12.1.0/appsutil/odbdev_odbdev.xml
Unable to read the value of s_tools_oh from the context file
Verify location and rerun this script.

Solution:

To resolve the issue test the following steps in a development instance and then migrate accordingly:

1. Stop the instance and run AutoConfig.

2. After AutoConfig completes successfully, then run both the ETCC scripts according to Sections 2 & 3 Note 2008451.1 - How To Run The 12.2 EBS Technology Code Level Checker (ETCC):
checkDBpatch.sh
checkMTpatch.sh

3. Reapply the patch with ADOP:
$ adop phase=apply patches=xxxxxxxx

(Note: If the ETCC reports show that some patches need to be applied, at some point apply all of the patches identified in the ETCC reports.)

Reference metalink Doc ID 2190263.1