Applying Patch 20844228: WLS PATCH SET UPDATE 12.1.2.0.6

Applying Patch 20844228: WLS PATCH SET UPDATE 12.1.2.0.6


Pre-Installation Instructions:


- Check if OPatch version is 13.1 or higher

- Ensure access to valid OUI Inventory by running opatch lsinventory -jdk $JAVA_HOME 

- Validate the executables in system PATH after setting $ORACLE_HOME by running 'which opatch', 'which unzip'

- Make sure WebLogic services are down including Admin & Managed Servers if any.

- Download & copy the patch to PATCH_TOP (any staging directory with proper permissions)

Applying the Patch


1. Unzip the patch unzip -d PATCH_TOP p20844228_121200_Generic.zip

2. cd PATCH_TOP/20844228

3. Apply patch by running opatch apply -jdk $JAVA_HOME

4. If patch successful, verify patch applied by running opatch lsinventory | grep 20844228 & start all the services


5. If patch fails for some reason, roll back the patch by running 

$ opatch rollback -id 20844228 -jdk $JAVA_HOME

Related posts:

Oracle WebLogic Server 12.2.1.0.0 - Applying Patch 22331568: WLS PATCH SET UPDATE 12.2.1.0.160119

Applying Patch 21364493: WLS PATCH SET UPDATE 12.1.2.0.7

FMW 12.1.3.0.0 - Applying Patch 20838345: WLS PATCH SET UPDATE 12.1.3.0.4

Oracle WebLogic Server WLS 10.3.6.0.13 - Applying Patch 21984589: SU Patch [S8C2]: WLS PATCH SET UPDATE 10.3.6.0.13

Applying Patch 20780171: SU Patch [EJUW]: WLS PATCH SET UPDATE 10.3.6.0.12

Applying Patch 19637463: SU Patch [12UV]: Oracle WebLogic Server (WLS) PATCH SET UPDATE 10.3.6.0.10

Applying Patch 19182814: SU Patch [FSR2]: Weblogic Server (WLS) PATCH SET UPDATE 10.3.6.0.9

Applying Patch 20474010: SU Patch [S8H6]: SPURIOUS HARVESTING OF CONNECTION BY WLS POOL

Error starting the Oracle Data Integrator 11g Studio at ODI_HOME/oracledi/client/odi.sh

Error starting the Oracle Data Integrator 11g Studio at ODI_HOME/oracledi/client/odi.sh


When trying to start the Oracle Data Integrator Studio to create the agent definition for Oracle Data Integrator Agent, you may hit errors as below and ODI studio fails to load.

When you do echo $JAVA_HOME, it may be set correctly but the issue still persists.

Verify if odi.conf under $ODI_HOME/oracledi/client/odi/bin has Set JAVA Home parameter defined correctly. 

You end up seeing errors as below and ODI Studio fails to load if Java home parameter is set incorrectly.

      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at oracle.ide.boot.PCLMain.callMain(PCLMain.java:63)
        at oracle.ide.boot.PCLMain.main(PCLMain.java:55)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at oracle.classloader.util.MainClass.invoke(MainClass.java:128)
        at oracle.ide.boot.IdeLauncher.bootClassLoadersAndMain(IdeLauncher.java:190)
        at oracle.ide.boot.IdeLauncher.launchImpl(IdeLauncher.java:90)
        at oracle.ide.boot.IdeLauncher.launch(IdeLauncher.java:65)
        at oracle.ide.boot.IdeLauncher.main(IdeLauncher.java:55)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at oracle.ide.boot.Launcher.invokeMain(Launcher.java:714)
        at oracle.ide.boot.Launcher.launchImpl(Launcher.java:117)
        at oracle.ide.boot.Launcher.launch(Launcher.java:69)
        at oracle.ide.boot.Launcher.main(Launcher.java:59)