July 2020 Updates to EBS Technology Codelevel Checker (ETCC)

 

July 2020 Updates to EBS Technology Codelevel Checker (ETCC)

 

The E-Business Suite Technology Codelevel Checker (ETCC) utility identifies patches that need to be applied to your Oracle E-Business Suite 12.2 technology stack for the application and database tiers.

Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (MOS Note 1594274.1)

 

Database

·         Oracle Database Release Update RU 19.8.0.0.200714

·         Oracle JavaVM Component Database RU 19.8.0.0.200714

·         Oracle Database Proactive BP 12.1.0.2.200714

·         Oracle Database PSU 12.1.0.2.200714

·         Oracle JavaVM Component Database PSU 12.1.0.2.200714

·         Oracle Database Patch for Exadata BP 11.2.0.4.200714

·         Oracle Database PSU 11.2.0.4.200714

·         Oracle JavaVM Component Database PSU 11.2.0.4.200714

·         Microsoft Windows Database BP 19.7.0.0.200414

·         Microsoft Windows Database BP 12.1.0.2.200114

·         Oracle JavaVM Component 12.1.0.2.200114 on Windows

·         Microsoft Windows Database BP 11.2.0.4.180417

·         Oracle JavaVM Component 11.2.0.4.180417 on Windows

Fusion Middleware

·         WebLogic Patch Set Update 10.3.6.0.200714

·         Oracle Fusion Middleware 11.1.1.9

·         Forms and Reports 10.1.2.3.2

 

Obtaining ETCC

·         We recommend always using the latest version of ETCC, as new bugfixes will not be checked by prior versions of the utility. The latest version of the ETCC tool can always be downloaded via Patch 17537119 from My Oracle Support.

Oracle E-Business Suite Release 12 Critical Patch Update (JULY 20)

Oracle E-Business Suite Release 12 Critical Patch Update Knowledge Document (July 2020) (Doc ID 2679563.1)

Overview

 When applying any of the patches . Ensure that each product is patched completely before continuing to the next.

• Make a list of all the Oracle E-Business Suite homes on your system, together with their associated Oracle products and full versions.
• Identify the CPU patches needed for each Oracle product. Depending on your configuration, you may need to apply multiple Oracle Database and/or Oracle Fusion Middleware patches.
• Set the environment to point to the relevant Oracle home or product before applying a patch.
• Shut down all processes running from an Oracle home before patching the products there.
• Apply patches to one Oracle product at a time, then move on to the next Oracle product.
• Ensure the database post-installation scripts have been run before the application tier services are restarted.
• Patch your system where applicable as follows:
• Any separate or remote Oracle Fusion Middleware or Oracle HTTP Server database home, including a separate metadata repository home.
• Oracle E-Business Suite database home.
• Oracle Identity Management and infrastructure homes.
• Oracle Fusion Middleware application tier home.
• Oracle E-Business Suite applications

Security Patches for this CPU

Recommended that you apply the latest CPU both to Oracle E-Business Suite and its associated technologies.

lists CPU patches for Oracle E-Business Suite

Specifically for 12.2

Oracle E-Business Suite Release	CPU Patch	Prerequisite Patches or Components for the CPU Patch	Patches to be Applied After the CPU Patch
12.2	Patch 31198342		If you are on Oracle E-Business Suite Release 12.2.9, apply following patches:
			Patch 31354997:R12.FWK.C
			Patch 31206584:R12.FND.C.
			If you are on Oracle E-Business Suite Release 12.2.7 or 12.2.8, apply following patches:
			Patch 31444257:R12.FWK.C
			Patch 31206584:R12.FND.C.
			If you are on Oracle E-Business Suite Release 12.2.4,    apply Patch 31444255:R12.FWK.C.

Oracle E-Business Suite Release               

Release 12.2.9     

          Patches to be Applied                            

• Patch 30980446:R12.JTT.C
• Patch 30367367:R12.IBU.C
• Patch 25229413:R12.PAY.C
• Patch 26282050:R12.BNE.C
• Patch 29662975:R12.EAM.C

Release 12.2.8

• Patch 30948437:R12.FWK.C
• Patch 30980446:R12.JTT.C
• Patch 25229413:R12.PAY.C
• Patch 26282050:R12.BNE.C
• Patch 29662975:R12.EAM.C

Release 12.2.7

• Patch 30980446:R12.JTT.C
• Patch 25229413:R12.PAY.C
• Patch 26282050:R12.BNE.C
• Patch 29662975:R12.EAM.C

Release 12.2.4

• Patch 23708498:R12.FRM.C
• Patch 22261731:R12.JTT.C
• Patch 26527007:R12.BNE.C

Oracle Product

Latest Security Patches	My Oracle Support Knowledge Document References and Supplementary Comments
Oracle Database 19.0.0.0	Combo OJVM Release Update 19.8.0.0.200714 and Database Release Update 19.8.0.0.200714  (Patch 31326362)
Oracle Database 12.1.0.2	OJVM PSU 12.1.0.2.200714 and Database PSU 12.1.0.2.200714 Combo Patch 31326396

Reduce Utlrp Execution Time

 

Utlrp-Execution-Time

We need to execute utlrp.sql script compile the invalid objects in the database,

as a part of database upgrades/migrations between different versions of

Oracle Application and non-application databases. 

Utlrp.sql script is located at $ORACLE_HOME/rdbms/admin directory. 

Oracle recommends executing the utlrp.sql script to compile the invalid’s objects

in restricted mode to avoid any users connecting to the database.

Compiling objects in restricted mode not enables parallel process compilation

and compilation will take long time. 

Here I will illustrate two scenarios’ to compile the objects and second method will be

 faster than the first one [Oracle recommended one] 

1^st Method

Perform upgrade steps like executing catpatch.sql. Now we need to compile invalid objects in the database.

Start database listener 

Start database in restricted mode 

sqlplus “/as sysdba” 

SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql 

In this method utlrp not running in parallel, we can verify the same by using the following queries. 

SQL> SELECT job_name FROM dba_scheduler_running_jobs WHERE job_name

 like 'UTL_RECOMP_SLAVE_%'; 

no rows selected 

SQL> SELECT job_name FROM dba_scheduler_jobs WHERE job_name like 'UTL_RECOMP_SLAVE_%'; 

no rows selected 

2nd Method (recommended)

Perform upgrade steps like executing catpatch.sql. Now we need to compile invalid objects in the database. 

Start database listener Start database in normal mode 

Set the job_queue_processes=0 to avoid any jobs scheduled

using dba_jobs, it is dynamic parameter, we can issue when database is up and running also 

sqlplus “/as sysdba” 

SQL> Alter system set job_queue_processes=0 

SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql 

Now we can verify that parallel compilation is running 

SQL> SELECT job_name FROM dba_scheduler_running_jobs WHERE job_name 

like 'UTL_RECOMP_SLAVE_%'; 

JOB_NAME ------------------------------ UTL_RECOMP_SLAVE_2 UTL_RECOMP_SLAVE_4 UTL_RECOMP_SLAVE_3 

SQL> SELECT job_name FROM dba_scheduler_jobs WHERE job_name  like 'UTL_RECOMP_SLAVE_%'; 

JOB_NAME

 UTL_RECOMP_SLAVE_4 

UTL_RECOMP_SLAVE_3 

UTL_RECOMP_SLAVE_2 

This process will reduce the time to compile invalid objects, which in turn helps to reduce

 the upgrade time. 

Note: Since database is opened in normal mode and listener is up and running, any 

user can connect to database and can 

perform activity, this will causes issue in compiling invalid objects. 

To avoid this problem we have to configure the database listener port to new port number

 to avoid the users to connect to the database. 

Configure the database listener with new port number 

Make the changes in tnsnames.ora file with new port number for this database, otherwise

 parallel process will not start. 

 

Autonomus Database

 Autonomus Database :

From O to hero 

Very nice article and explanation 

Click on the link----->    Autonomus Database (PDF)

• Migration to Autonomous Database
• Optimizing with autonomous
• Optimized by Workload
• Automatic Indexing
• Workload Optimizations.

move data to Autonomous Database in "one-click" (Doc ID 2463574.1)

FND_DIAGNOSTICS Is Invalid In Oracle Apps R12.2

 FND_DIAGNOSTICS Is Invalid In Oracle Apps R12.2

After applying the PSU patch.

Ran @utlrp.sql  at Apps schema FND_DIAGNOSTICS package is invalid .

Error :- 

When we Compile the object the following error is observed:

Alter package APPS.FND_DIAGNOSTICS compile body;

Warning: Package Body altered with compilation errors.

SQL> show errors;

Errors for PACKAGE BODY APPS.FND_DIAGNOSTICS:

LINE/COL ERROR

-------- -----------------------------------------------------------------

1839/17 PL/SQL: SQL Statement ignored

1839/31 PL/SQL: ORA-00942: table or view does not exist

1841/9 PL/SQL: Statement ignored

1841/14 PLS-00364: loop index variable 'X' use is invalid

Solution:

1. Add grant to DBA_DATAPUMP_JOBS view;

sqlplus / as sysdba

SQL> grant select on dba_datapump_jobs to apps;

SQL> alter package APPS.FND_DIAGNOSTICS compile body;

Unable to access Weblogic Console page

EBS 12.2 Weblogic 

IF unable to access Weblogic Console page

a) Delete the deny rule line form following file 

b) stop  Application:

Changes to be done 

vi $EBS_DOMAIN_HOME/config/config.xml

. . . . .

<connection-filter-rule>0.0.0.0/0 * * deny</connection-filter-rule>

. . . . .

Save the file and

c) start Application: