Hyperion On-Prem

How to obtain a connection to Hyperion Essbase in FDMEE

You might face a situation where you will not be able to obtain a connection to Hyperion essbase from FDMEE

This happens if Planning and FDMEE are in different servers and the Essbase client and planning libraries are not in sync.

Steps to sync Essbase Client and Planning version between Planning server & FDMEE server

Apply the same Essbase Client patch that is installed in the Planning server on the FDMEE server. This will update Essbase-RTC dir

1. Copy the Planning opatch zip applied on the Planning server to FDMEE server C:\Oracle\Middleware\EPMSystem11R1\OPatch dir
2. Unzip the opatch zip file.
3. For Planning 11.1.2.4.007 the patch number is 27027776.
4. So I refer that number in the following examples
5. Copy the file from C:\Oracle\Middleware\EPMSystem11R1\OPatch\27027776\files\common to C:\Oracle\Middleware\EPMSystem11R1\common
6. Copy the files from C:\Oracle\Middleware\EPMSystem11R1\OPatch\27027776\files\products\FinancialDataQuality\lib\64-bit  to C:\Oracle\Middleware\EPMSystem11R1\products\FinancialDataQuality\lib\64-bit.                                                                                              

 Above are examples for Windows. For Linux change dir references appropriately

How to truncate/reduce size of logs in FDMEE

 We can truncate ODI tables SNP_SESS_TASK and SNP_SESS_TASK_LOG.

1. You can review the below article;

How To Manually Delete ODI 10g And 11g Sessions And Scenario-Related Reports (Doc ID 424740.1)

The above KM does not apply to ODI 12c. For ODI 12c specifically, please use the SDK commands from Note 1941196.1 - How To Delete ODI 11g And 12c Sessions Using The SDK.

2. You can also follow this Oracle Documentation & purging the logs

ODI Documentation: https://docs.oracle.com/cd/E23943_01/integrate.1111/e12643/odi_console.htm#ODIDG141823.2.5 Purging the Log

You can also delete logs per the FDMEE Application Architecture section under Upgrading to FDMEE in Chapter 1 - Using FDMEE of the FDMEE Admin Guide, see link below

http://docs.oracle.com/cd/E40248_01/epm.1112/erpi_admin.pdf

3. The recommended way to do this is using the OdiPurgeLog tool inside of ODI Studio from document:
Programming ODI To Automatically Purge The Operator Journal (Doc ID 423839.1)

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