Saturday, 20 June 2015

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 



No comments:

Post a Comment