Monday, December 16, 2019

Getting ADF_Faces-60097 Error Randomly In Financial Data Quality Management, Enterprise Edition

Getting ADF_Faces-60097 Error Randomly In Financial Data Quality Management, Enterprise Edition 

In Hyperion Financial Data Quality Management, Enterprise Edition,

User(s) might get an ADF error in FDMEE randomly and it will get resolved post service restart.

Error message 

ADF_Faces-60097. For more information please see the servers error log for an entry beginning with ADF_Faces-60096:Server exception during PPR, #6...

Error message captured from ErpIntegrator-diagnostics log

[ErpIntegrator0] [ERROR] [][oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator] [tid:MainThread][userId: ] [ecid:00ixxx2Zb0nnYxxx9id000xxxx0HQv,0:1] [APP: AIF#11.1.2.0] [DSID:0000yyyozzz0bqY5Pr8Dyd1TNH_zzz001S]
ADF_FACES-60096:Server Exception during PPR, #1[[oracle.jbo.PCollException: JBO-29114 ADFContext is not setup to process messages for this exception. Use the exception stack trace and error code to investigate the root cause of this exception.
Root cause error code is JBO-28033. Error message parameters are {0=PS_TXN, 1=77751, 2=1}
...
...
## Detail 0 ##
java.sql.SQLException: Protocol violation: [16, 6, 7, 0] at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:502) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)

This is due to a JDBC bug that should be fixed in 11.1.2.4 versions but we are still seeing the issue in some environments.

ADF errors can be caused when there are multiple requests sent at one particular time.
This is due to JDBC bug documented in Bug 18514458 and Bug 22006889

User(s) need to modify the JVM entries in the Windows registry and in the setCustomErpIntegrator.bat in the FDMEE server.


STEP 1: How to modify the JVM entries in the windows registry

To update the Windows registry, the JVMOptionCount value must first be increased to the appropriate decimal value: (increase the value by 1) and then Restart the server.

A restart of the server is required for changes to affect after modifying the registry values.


STEP 2: How to modify the setCustomErpIntegrator.bat in the FDMEE server

1. Modify the setCustomParamsErpIntegrator file under C:\Oracle\Middleware\user_projects\epmsystem1\bin\deploymentScripts
    Update the following property
    Existing:
        -Doracle.jdbc.useFetchSizeWithLongColumn=true
    New:
        -Doracle.jdbc.useFetchSizeWithLongColumn=false
2. Restart the FDMEE Service

No comments:

Post a Comment

Other posts

How is the data size calculated for a EPM Cloud service instance?

The total size of data used by your EPM Cloud service instance is the sum of the following: Application data stored in Essbase Artifact...