EBS Technology Codelevel Checker (ETCC)

++++++++++++++++++++++++++++++++++++++++:

The EBS Technology Codelevel Checker (ETCC) utility provides two scripts you can
run to help ensure you have the necessary database and application tier bugfixes
installed on your Oracle E-Business Suite Release 12.2 system. Oracle strongly
recommends the use of this utility to ensure that all required database and
application tier bugfixes have been installed.

ETCC can be downloaded via Patch 17537119 from My Oracle Support. ETCC maps missing
bugfixes to the default corresponding patches and displays them in a patch
recommendation summary. If your Oracle E-Business Suite 12.2 installation has
additional patches installed as well as the recommended patches, you may need to
install a merge patch from Oracle Support. As well as installation instructions and
basic commands, the README for this patch includes a number of usage scenarios and
examples so should be carefully reviewed before running ETCC.

Note: Always use the latest version of ETCC, as new bugfixes will not be checked by
older versions of the utility. Also, patch recommendation summaries are only
provided for the latest and latest but one quarterly bundles supported by Oracle E-
Business Suite Release 12.2. Refer to Section 3: Database Patches and Bug Numbers
for the Oracle database releases and bundle documentation.

The two scripts that make up ETCC are:

-checkDBpatch.sh (checkDBpatch.cmd on Microsoft 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. When using Oracle Real Application
Clusters (Oracle RAC) ensure ETCC is run on every database ORACLE_HOME.

-checkMTpatch.sh (checkMTpatch.cmd on Microsoft Windows). This is the Application

Tier EBS Technology Codelevel Checker (MT-ETCC), which determines if all the needed
bugfixes exist in the application tier file system.
For bugfixes reported as missing when patch mapping is not available, you will need
to manually identify the patch that includes the missing fix. You can do this by
referring to the relevant table in this document for your component version. Next,
locate the relevant bug in the Bug Numbers column, and then work leftwards to the
Patch column for your platform. If more than one patch mentions the bug number,
install the most recent patch listed in the table.

Note: If you are applying database patch set updates (PSUs), or using the Quarterly
Database Patch (QDPE) for either Exadata or SuperClusters, you should also refer to
the Database Patch Set Updates and Exadata/SuperClusters Patches section of this
document.