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

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".

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".

Error page shows below message

oracle.apps.fnd.framework.OAException: Application: FND, Message Name: FND_GENERIC_MESSAGE. Tokens: MESSAGE = java.sql.SQLException: Connection has been administratively disabled by console/admin 

command. Try later. java.lang.Exception: It was disabled at <date-timestamp> at weblogic.jdbc.common.internal.ConnectionEnv.disable(ConnectionEnv.java:357) at 

weblogic.jdbc.wrapper.JDBCWrapperImpl.invocationExceptionHandler(JDBCWrapperImpl.java:127) at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:152) at 

oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:225) at oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:201) at 

oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:176) at oracle.apps.fnd.cache.GenericCacheLoader.load(GenericCacheLoader.java:151) at 

oracle.apps.jtf.cache.GenericCacheLoader.load(Unknown Source) 


Also connections to Forms fail. 

However, EBS Technology Codelevel Checker (ETCC) shows patches are correctly applied and Autoconfig also completes with success.


Workarounds:

i) Refresh the page once logged in to enable navigation to continue normally.

Or


ii)Hide the Worklist Notifications table from Homepage.


Fix:

1) For Release 12.2, apply 


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

2) For Release 12.1.3, please apply following Patches :

I) Patch 18936791 - 'R12.FWK.B.DELTA.4'

Patch R12.FWK.B.delta.4: R12.FWK.B.DELTA.4


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

If the issue still persists, check the JVM settings in the context file and set correct values.

Eg:

1. Change parameter in Context File on all nodes: 

FROM: 

<forms_jvm_start_options oa_var="s_forms_jvm_start_options">-Xms512m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m 

<oacore_jvm_start_options oa_var="s_oacore_jvm_start_options">-Xms512m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m 

<oafm_jvm_start_options oa_var="s_oafm_jvm_start_options">-Xms512m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m 

TO: 

<forms_jvm_start_options oa_var="s_forms_jvm_start_options">-Xms512m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m 

<oacore_jvm_start_options oa_var="s_oacore_jvm_start_options">-Xms512m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m 

<oafm_jvm_start_options oa_var="s_oafm_jvm_start_options">-Xms512m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=256m 

2. Run autoconfig to deploy the parameter setting


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

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

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".

APPS.OKL_ACCT_SOURCES_PVT PLS-00907: cannot load library unit APPS.OKL_ASE_PVT (referenced by APPS.OKL_ACCT_SOURCES_PVT)

APPS.OKL_ACCT_SOURCES_PVTPLS-00907: cannot load library unit APPS.OKL_ASE_PVT (referenced by APPS.OKL_ACCT_SOURCES_PVT)

After upgrading to R12.1.3, many objects are invalid 

This is due to the missing setup of _disable_fast_validate parameter during the upgrade.

1. Backup your environment
2. Add the following to the database intialization file to disable fast validation for PL/SQL recompilations:

_disable_fast_validate=TRUE

3. Bounce the database
4. Regenerate the apps invalid objects via adadmin or rdbms utlrp tool
5. Revert the change in the database intialization file