Issues with 11.2.x LCM and Financial Reports? Try This!

  • Date: January 22, 2021
  • Article by: Jeff Henkel

So apparently there is a bug with Financial Reporting LCM in 11.2.3 EPM.  This is caused by the FR product randomly storing a DB call in the Financial Reporting product registry.

You can see this by running FRconfig.cmd, found at:  \Oracle\Middleware\EPMSystem11R1\products\financialreporting\bin

Once launched, you can select the MBeans tab and then navigate to com.hyperion | Financial Reporting | Attributes

Examine the various values for the database, as the exact location of the issue will vary from SQL to Oracle DB Server.  In my case, the value dbUserName was the culprit, but other options include: dbName, dbProductName and DbJdbcUrl.

In the entry you will see that my Financial Reporting configuration magically pointed itself to my Planning System db…which was never intentionally configured this way.

To resolve this, and not have to resort to the command-line LCM utility, which seems to ignore this value, you can update the server registry as follows:

  • Navigate to the registry entries for both Foundation Services and Financial Reporting
  • Add a new JVMOption#.  This will be the next available JVMOption not used, and mine was 37 in the below example.
    • Set the value for this entry to:  -Dweblogic.oif.serialFilterMode=disable
  • Increase the JVMOptionCount registry entry to match the new number above
  • Restart Foundation and FR and LCM should resume functioning.
Share me

Oracle Security Alert for CVE-2021-44228: Part Four

  • Date: Dec 16, 2021
  • Article by: Mike Turner
Read More

Oracle Security Alert for CVE-2021-44228: Part Three

  • Date: Dec 15, 2021
  • Article by: Jeff Henkel
Read More

Essbase Error (1024016): Request from user was terminated since it exceeded the time limit.

  • Date: November 10, 2013
  • Article by: Joe Malewicki

ISSUE: When running a query in Oracle Hyperion Smart View, the Essbase Excel-Addin, or any other Reporting and Analysis tools, the following error is returned after an extended period of time.  When this occurs, the user must close Microsoft Excel and then re-open and re-login to continue working.
ERROR MESSAGE DETAILS:
Oracle Hyperion Smart View for Office, Fusion Edition
Essbase Error (1024016): Request [<some-report-name>] from user [<some-user@provider-name>] was terminated since it exceeded the time limit.
OK
SCREEN SHOT:
essbase-error-1024016
SOLUTION: In the ESSBASE.CFG file remove or modify the parameter for the QRYGOVEXECTIME to be a value greater than the time needed for the query to complete.  You must restart the Essbase server for the new setting to take effect.  In our example the user has the setting currently at QRYGOVEXECTIME 45 (45 seconds) and the Smart View query was unable to complete in that requested in that amount of time.
*** Note*** This setting can be configured as an Essbase server wide setting or can be configured for individual applications.
The ESSBASE.CFG file can be found on the Essbase server:
On a Microsoft Windows platform:
C:OracleMiddlewareuser_projectsepmsystem<#>EssbaseServeressbaseserver1bin
On a LinuxUnix platform:
/<your install location>/Oracle/Middleware/user_projects/epmsystem<#>/EssbaseServer/essbaseserver1/bin

  1. Shutdown the Essbase server service or process.
  2. Backup the current ESSBASE.CFG file.
  3. Comment out or modify the following parameter:
    1. QRYGOVEXECTIME 180
  4. Restart the Essbase server service or process.

APPLICABLE VERSIONS: 9.3.x, 11.1.1.x, 11.1.2.0, 11.1.2.1, 11.1.2.2, 11.1.2.3

Share me

Oracle Security Alert for CVE-2021-44228: Part Four

  • Date: Dec 16, 2021
  • Article by: Mike Turner
Read More

Oracle Security Alert for CVE-2021-44228: Part Three

  • Date: Dec 15, 2021
  • Article by: Jeff Henkel
Read More