The Technology Codelevel Checker (ETCC) utility provides two shell scripts (checkDBpatch.sh & checkMTpatch.sh) to ensure all the necessary database and application tier patches are installed on a 12.2 system.
Is it mandatory to Run The EBS Technology Code Level Checker?
The scripts are usually updated on a quarterly basis, to include the latest defect patches released for the 12.2 database and apps tiers.
Follow the below steps to run the Technology Codelevel Checker (ETCC):
1) The EBS Technology Code Level Checker (ETCC):-
It provides two scripts which analyze the Database and the Middle tier Oracle Homes and warns of missing bug fixes required for Oracle E-Business Suite Release 12.2.
Oracle strongly recommends the use of this utility to ensure that all required database and middle tier bugfixes have been installed.
The two scripts are:
– checkDBpatch.sh (checkDBpatch.cmd on Windows)
This is the Database EBS Technology Codelevel Checker (DB-ETCC), which determines if all the needed bugfixes exist in the specified database ORACLE_HOME.
– checkMTpatch.sh (checkMTpatch.cmd on Windows)
This is the Middle Tier EBS Technology Codelevel Checker (MT-ETCC), which determines if all the needed bugfixes exist in the middle tier file system.
2) To run the DB Technology Codelevel Checker (DB-ETCC) :
1. Download Patch 17537119 from My Oracle Support
[[email protected]***apps 17537119_R12]$ sh checkDBpatch.sh
| Copyright (c) 2005, 2020 Oracle and/or its affiliates. |
| All rights reserved. |
| Oracle E-Business Suite Release 12.2 |
| Database EBS Technology Codelevel Checker |
Validating context file: /data01/GSTUAT3/orahome1124/appsutil/PHASE1_apps.xml
Using context file from currently set database environment:
Starting Database EBS Technology Codelevel Checker, Version 120.75
Fri Jun 26 11:53:29 IST 2020
Log file for this session : /home/oracle/17537119_R12/log/checkDBpatch_29642.log
Identifying database release.
Database release set to 18.104.22.168.
Connecting to database.
[WARNING] DB-ETCC: Could not connect to database, so unable to check:
– Whether database is in READ-WRITE mode.
– Existence of table needed to store DB-ETCC results.
Resolve the database connectivity issue, and then rerun DB-ETCC.
Bugfix file ./db/onprem/txk_R1220_DB_base_bugs.xml : 120.0.12020000.54
This file will be used for identifying missing bugfixes.
Mapping file ./db/onprem/txk_R1220_DB_mappings.xml : 120.0.12020000.29
This file will be used for mapping bugfixes to patches.
[WARNING] DB-ETCC: Bugfix XML file (./db/onprem/txk_R1220_DB_base_bugs.xml) is more than 30 days old.
Check if a newer version is available in patch 17537119.
Checking Bugfix XML file for 22.214.171.124_PSU
Obtained list of bugfixes to be applied and the list to be rolled back.
Now checking Database ORACLE_HOME.
The opatch utility is version 126.96.36.199.15.
DB-ETCC is compatible with this opatch version.
Found patch records in the inventory.
Checking Mapping XML file for 188.8.131.52.180417
Patch mapping not available.
Patch mapping data is not available for 184.108.40.206.180417
Refer to Doc ID 1147107.1 for the required overlay patches for PSUs and Oracle E-Business Suite
Some required one-off bugfixes are missing from the Database ORACLE_HOME.
The missing bugfixes are:
** Refer to MOS Doc ID “1147107.1:Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite” to find the corresponding overlay patch that delivers the bug fix. **
Apply the missing bugfixes and then rerun the script.
[WARNING] Database not available. DB-ETCC results cannot be stored.
Finished checking fixes for Oracle Database: Fri Jun 26 11:53:44 IST 2020
Log file for this session: /home/oracle/17537119_R12/log/checkDBpatch_29642.log
3) To run the MT Technology Codelevel Checker (MT-ETCC) :
4. Apply all missing bugfix:-
Take the appropriate actions based on what the script reports about any missing bugfixes.