Release 12.1.3 Applying Patch 20671106 - 'R12.FWK.B -- 18658202: BACKPORT: ERROR UNDER WORKLIST FORMS FAIL TO LAUNCH'

Release 12.1.3 Applying Patch 20671106 - 'R12.FWK.B -- 18658202: BACKPORT: ERROR UNDER WORKLIST FORMS FAIL TO LAUNCH'

Oracle Applications DBA version 12.2.3 or 12.2.4 Error Page On HomePage "Error Page You have encountered an unexpected error. Please contact the System Administrator for assistance".

If facing above issue in Release 12.1.3, one of the patches to be applied is:

Patch 20671106 - 'R12.FWK.B -- 18658202: BACKPORT: ERROR UNDER WORKLIST FORMS FAIL TO LAUNCH'

Prerequisite Patches:

The following should be installed in the order shown before installing this patch.

1 R12.AD.B.delta.3 Oracle Applications DBA 12.1.3 Product Release Update Pack (Install on Oracle Applications DBA)

1 R12.ATG_PF.B.delta.3 Oracle Applications Technology 12.1.3 Product Family Release Update Pack (Install on Oracle Applications Technology Family)

2 R12.FWK.B.delta.4 R12.FWK.B.DELTA.4


- Source the Applications environment file
- Run the Patch Application Assistant by entering "admsi.pl".
- Apply the patch

This patch contains the following unified driver file to be applied with

AutoPatch:    u20671106.drv (This is the unified driver)

Release 12.1.3 Applying Patch 18936791 - 'R12.FWK.B.DELTA.4' Patch R12.FWK.B.delta.4: R12.FWK.B.DELTA.4

Release 12.1.3 Applying Patch 18936791 - 'R12.FWK.B.DELTA.4'  Patch R12.FWK.B.delta.4: R12.FWK.B.DELTA.4

Oracle Applications DBA version 12.2.3 or 12.2.4 Error Page On HomePage "Error Page You have encountered an unexpected error. Please contact the System Administrator for assistance".

If the above issue persists on 12.1.3 instance, one of the patches to apply is

Patch 18936791 - 'R12.FWK.B.DELTA.4'  Patch R12.FWK.B.delta.4: R12.FWK.B.DELTA.4

Prerequisite Patches to be applied in below order:

1 R12.AD.B.delta.3 Oracle Applications DBA 12.1.3 Product Release Update Pack (Install on Oracle Applications DBA)

2 R12.ATG_PF.B.delta.3 Oracle Applications Technology 12.1.3 Product Family Release Update Pack (Install on Oracle Applications Technology Family)


- Apply the patch

This patch contains the following unified driver file to be applied with

AutoPatch:     u18936791.drv (This is the unified driver)

Release 12.2 Applying Patch 20132328 - 'R12.FWK.C - INTERMITTENT YOU HAVE ENCOUNTERED AN UNEXPECTED ERROR APPEARS IN E BUSINESS SUIT'

Applying Patch 20132328 - 'R12.FWK.C - INTERMITTENT YOU HAVE ENCOUNTERED AN UNEXPECTED ERROR APPEARS IN E BUSINESS SUIT'


Oracle Applications DBA version 12.2.3 or 12.2.4 Error Page On HomePage "Error Page You have encountered an unexpected error. Please contact the System Administrator for assistance".

For Release 12.2, apply 

Patch 20132328 - 'R12.FWK.C - INTERMITTENT YOU HAVE ENCOUNTERED AN UNEXPECTED ERROR APPEARS IN E BUSINESS SUIT'


1.Source the Applications environment file

2.Run the Patch Application Assistant by entering "admsi.pl".

3. Pre-requisites:

The following should be installed in the order shown before installing this patch.

I) R12.AD.C.delta.3 ORACLE APPLICATIONS DBA 12.2.3 PRODUCT RELEASE UPDATE PACK (Install on Oracle Applications DBA)

I) R12.TXK.C.delta.5 R12.TXK.C.DELTA.5 (Install on Oracle Applications Technology Stack)

II) 12.2.3 ORACLE E-BUSINESS SUITE 12.2.3 RELEASE UPDATE PACK (Install on Oracle Applications Updates)

II) R12.AD.C.delta.5 AD R12.AD.C.DELTA.5 (Install on Oracle Applications DBA)

III) R12.ATG_PF.C.delta.4 R12.ATG_PF.C.delta.4 (Install on Oracle Applications Technology Family)

PLEASE NOTE: Some of the patches above may be superseded. Always check for latest patches before applying them.

4. For 12.2.X patches (using adop), you can perform the tasks in this section without shutting down the Application tier services.

Apply the patch with ADOP:

adop phase=apply patches=20132328

EBS 12.2.3 & 12.2.4 - oacore stdout growing large in size JBO DEBUG LOGGING ON WITHOUT -D FLAG, NOTICE LEVEL AND PROD MODE=TRUE

EBS 12.2.3 & 12.2.4 - oacore_server1.out growing large in size JBO DEBUG LOGGING ON WITHOUT -D FLAG, NOTICE LEVEL AND PROD MODE=TRUE


In EBS 12.2.3 to 12.2.4 you may observe oacore_server1.out continuously logging DEBUG level JBO errors and issues. Each managed server & admin server is set to have NOTICE level debugging. 

Change the trace and debug levels to NOTICE. However, this still does not turn off the logging. WebLogic is running in Production mode. 

Also startWebLogic.sh does not have -Djbo.debugoutput=console in the process args. you may still see JBO logs consuming lot of space in GBs & filling up mount space. Even with FND profile options and FND developer mode is No and other logging is down to minimal levels, DEBUG logging is still enabled.

$DOMAIN_HOME/servers/oacore_server1/logs/oacore_server1.out grows to gigabits in size.
.
-------------------------------------
<oracle.jbo.common.ADFLoggerDiagnosticImpl> <BEA-000000> <[2027] Could not
find method:getUOM in oracle.apps.fnd.framework.server.OAViewRowImpl -
oracle.apps.fnd.framework.server.OAViewRowImpl.getUOM()>
.
these error codes/messages are recording continuously independent of the logging level set.

You may observe impact on performance with high CPU and disk space usage.

In EBS 12.2.x a JBO “Debug” Diagnostics.properties is causing a log flood into the oacore stdout logs. 

This is due to Bug 18345006 - JBO DEBUG LOGGING ON WITHOUT -D FLAG, NOTICE LEVEL AND PROD MODE=TRUE

To fix this, you can follow either of the below steps:

I) Apply Patch 18345006


1. Download and review the readme of Patch 18345006. 

Pre-Requisite patches: 

i. R12.AD.C.delta.3 ORACLE APPLICATIONS DBA 12.2.3 PRODUCT RELEASE UPDATE PACK (Install on Oracle Applications DBA)
ii. 12.2.3 ORACLE E-BUSINESS SUITE 12.2.3 RELEASE UPDATE PACK                        (Install on Oracle Applications Updates)

2. Apply the patch to a test instance after a backup and re-test.

3. Apply the patch to other instances as needed the same way.


II) Add arguments -Djbo.adflogger.level=SEVERE


1. Patching Cycle Check - the CUTOVER phase should be at "COMPLETED" status:


On MT Node run:


adop -status -detail

CUTOVER phase should have 'COMPLETED' status


2. Login to the wls console http://localhost:port/console

3. On the homepage navigate to 

Environment -> Servers
Select oacore_server1
Select the server start tab
Select the "Lock and edit" button at the top left

4. Take a backup of the arguments before making the change by copying it to a text file

5. Add to arguments text box -Djbo.adflogger.level=SEVERE

6. Save the changes and Select the "Release configuration" button at the top left

7. Re-start the managed server


8. Repeat the same steps for other oacore servers, if you have them defined & restart them.

Also see other related posts:

Oracle Applications Technology Stack 12.2.4 - Cannot open Oracle Forms: Java null pointer exception error with Java 6 Update 27 Java Plug-in on Client Machine

Oracle Applications DBA version 12.2.3 or 12.2.4 Error Page On HomePage "Error Page You have encountered an unexpected error. Please contact the System Administrator for assistance".