Error "Active Time Limit Exceeded - Call Aborted" When Exporting Data to PBCS Application Through Data Management

In Data Management, Load method was not set properly for Oracle Planning and Budgeting Cloud Service(PBCS) application especially for multi-period loads.

Kindly refer the steps below,

• Click on Navigate and go to Data management
• In Target Application, select the application and click on Application options
• Define the Load Method as "All data types with security" and save the changes.
• Goto Data Load Rule -> Target Options -> Ensure Load Method is also set to "All data types with security" and save the changes
• Re-run the export task for multiple periods and it should work fine.

Note :
The above steps are applicable for the loads with less number of rows.
If the file size is huge(i.e have millions of rows), then above steps would not help to fix the issue.
There is an Enhancement request already raised with the development but fix is not yet available:

Enh 26834089 - PBCS: UNABLE TO IMPORT LARGE DATA FILES DUE TO DB RESOURCE CONSTRAINTS

Error "IndexError: index out of range: 1" while executing a batch process in FDMEE

Error "IndexError: index out of range: 1" while executing a batch process in FDMEE

Three major aspects of this issue are:

1. Insufficient Batch timeout value defined in the System settings / Application settings in the FDMEE application
2. Stuck thread timeout setting needs to be increased in the ErpIntegrator0 managed server (weblogic)
3. Increase the Connection Pool - Maximum Capacity range for EPM in the weblogic console

1. To increase the batch timeout setting in the FDMEE application

• Navigate to Data Management from EPM workspace
• From the Setup tab, and then under Configure, select System Settings
• In System Settings, from Profile Type, select Other
• Define a timeout value for the “Batch timeout in minutes”

            Note : In this the maximum batch timeout value can be 30000
2. To increase the Stuck Thread timeout setting in the ErpIntegrator0 managed server in weblogic

• Navigate to weblogic admin console
• Under domain structure, expand Environment and choose servers
• Choose ErpIntegrator0 from the servers list
• Under configuration, choose tuning
• Choose Lock & Edit to modify the setting value
• Increase the Stuck Thread Max time value, set the value to 9600
• Note : The value is in seconds. By default it will be 600 seconds
• Choose activate configuration so that the settings take effect
• Restart the FDMEE services.

3. To increase the Connection Pool - Maximum Capacity range for EPM in the weblogic console

• Navigate to weblogic admin console
• Under domain structure, expand Services and choose Data Sources
• Click on the 'Connection Pool' tab
• Click the 'Lock and Edit' button in the left pane
• Increase the ‘Maximum Capacity’ value from 30 to 300
• Click the 'Activate Changes' button in the left pane
• Restart the FDMEE services

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

How to Increase Timeout settings in EPM

STEP 1
Kindly do the modifications in the OHS server,

1. Modify httpd.conf under ${EPM_ORACLE_INSTANCE}\httpConfig\ohs\config\OHS\ohs_component\httpd.conf

   Set KeepAliveTimeout to 120 or 210. Value in OHS is seconds and not in minutes.

   Change ThreadsPerChild 64 to ThreadsPerChild 1024


2. Edit EPM_ORACLE_INSTANCE\httpConfig\ohs\config\OHS\ohs_component\mod_wl_ohs.conf as below
    Or
    C:\Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component directory you will find a mod_wl_ohs.conf file.




SetHandler weblogic-handler

WeblogicCluster depm-web1:6550

WLIOTimeoutSecs 9600

Idempotent OFF

WLSocketTimeoutSecs 22500

ConnectTimeoutSecs 1200




3.  Restart the Oracle Process Manager Windows Process or run stopOHS.sh/startOHS.sh for Linux.

Step 2
Under Web logic console , for managed Server change below value

Stuck Thread Max Time=9600
Stuck Thread Timer Interval=9600
Max Stuck Thread Time=9600

Change the following setting from the Weblogic console.
Select "Lock and Edit" Select Servers and
click on ErpIntegrator(N)
Select the Tuning tab
Change "Stuck Thread Max Time" to 9600
Change "Stuck Thread Timer Interval" to 9600
Change Max Stuck Thread Time=9600
Select "Activate Changes"
The ErpIntegrator(N)  server will need to be restarted.

After this step kindly restart the FDMEE services and verify

NOTE
Also ensure below PSE in place

Release 11.1.2.4.200 Patch Set Exception (PSE): 23154750


Also validate the following settings:

++ End users Internet Explorer timeout setting in the registry key:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\ReceiveTimeout
HKEY_Local_machine\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\ReceiveTimeout

>>-- set to 7200000

++ Timeout at the web server set via IIS and the web.config

There are 3 places in the Web.config file where timeout sessions must be changed.

1.

     Change the “60” to “120” to increase this timeout setting from 60 minutes to 120 minutes.

2.

     Change the “60” to “120” to increase this timeout setting from 60 minutes to 120 minutes.

3.

    Change the “3600” to “7200” to increase this timeout setting from 3600 seconds to 7200 seconds (2 hours).

++  It is also necessary to increase the Connection Timeout setting of the Default Web Site in the IIS Manager. Change the default setting.

1) Open IIS (Administration Tools/Internet Information Services)

2) Expand "Local Computer"

3) Expand "Web Sites" and expand "Default Website"

4) Right-Click on "Default Website" and choose Advanced Settings

5) Update the Connection Timeout value  to 3600 seconds or to 7200 seconds.(Currently set to 120)

6) Reset IIS and check the issue.