The following topics are discussed:
Oracle Enterprise Performance Management System products comprise a high-end financial reporting system separate from the Oracle Business Intelligence products described in Troubleshoot and Tune Oracle Fusion Reports. This system is best for more complex financial calculations, and handling drill-down through complex financial accounting hierarchies. It includes no seeded reports. A seeded and auto-populated Essbase database is available for General Ledger.
The components of the Enterprise Performance Management System that are integrated with Fusion Applications include the following:
Oracle Hyperion Financial Reporting
Oracle Hyperion Enterprise Performance Management Workspace
Oracle Smart View for Office
Oracle Hyperion Calculation Manager
Oracle Essbase
Oracle Essbase Administration Services
Oracle Hyperion Provider Services
Oracle Essbase Studio
Oracle Data Relational Management
Oracle Smart View for Office
This section describes some common problems and solutions for Foundation Services. The following topics are discussed:
Log files are the best tools for analyzing what might be wrong with the system configuration. The logging configuration file, the defaults it ships with, and instructions for changing change those defaults will help with the analysis.
Configuration: The logging.xml
file in the following directories contains the loggers and their default levels:
(UNIX) DOMAIN_HOME/servers/server_name/logs
The DOMAIN_HOME
is named BIDomain
.
Output: The default locations of the loggers are rooted in the following directories:
(UNIX) DOMAIN_HOME/servers/server_name/logs
These files include the following:
/registry/registry.log
/css/css.log
/workspace/Framework.log
/workspace/workspace.log
/financialreporting/fr.log
CalcManager.log
Loggers: Increase or decrease the levels of the following loggers:
oracle.EPMCSS
oracle.bi.bifndnepm.epmreg
oracle.bi.bifndnepm.bpmui
oracle.bi.bifndnepm.workspace
oracle.EPMFR
oracle.EPMAnnotations
oracle.EPMJCR
oracle.EPMADM
oracle.bi.bifndnepm.calcmgr
To change logger levels, perform the following steps:
Problem
Some components are not operating correctly, or appear to have some minor issues. This is a broad category, but snooping the web traffic can help development resolve some issues by looking for irregular status, content, and redirection, and just providing the flow of calls up to the problem area.
Solution
To solve this issue, perform the following steps:
This section describes common problems and solutions for Enterprise Performance Management (EPM) Registry. It contains the following topics:
Problem
The logs indicate that the Enterprise Performance Management (EPM) Registry initialization failed in the BIDomain
domain. Oracle Fusion General Ledger and Oracle Fusion Customer Relationship Management (CRM) code running within the FinancialsDomain
and CRMDomain
domains, respectively, has direct integration with the EPM Registry API and consumes EPM Security Component, which also tightly integrates with the EPM Registry API. When EPM Registry initialization fails, it greatly affects communication with downstream EPM products in the BI domain.
Solution
To resolve this problem, perform the following steps:
Financials
domain.Problem
An error is returned when connecting to Essbase Server from the Fusion Applications domain, using the Essbase Cluster lookup URL that is built using the host and port information retrieved for Essbase_FA_Cluster
, from EPM Registry using the Registry API.
Solution
To resolve this issue, perform the following steps:
Verify that the host and port values for the LOGICAL_WEB_APP
component in EPM System Registry, where webAppType
is PROVIDER_SERVICES_WEB_APP
, exactly matches the host and port that the APS Web application is running on in the BI domain. Follow these steps:
Run the EPM Registry Editor utility using the following command:
(UNIX) APPLICATIONS_CONFIG/BIInstance/config/foundation/11.1.2.0/epmsys_registry.sh view LOGICAL_WEB_APP | tee -a logical_webapp_report.txt
In the logical_webapp_report.txt
file that is generated as a result of Step 1, search for the following string:
*"webAppType = PROVIDER_SERVICES_WEB_APP"
For the COMPONENT
containing the matching string, verify that HOST/port/SSL_PORT
exactly match what the APS Web application is actually running on in the BI domain. If any of these values are different in the Essbase cluster lookup URL, they should be appropriately updated in EPM Registry for the given Logical Webapp Component. This solution is discussed in Host and Ports Do Not Match.
Confirm that the APS Web application is in an Active state in the BI domain, by logging into the BI Administration Server console and reviewing the deployment profile of APS.
If verification of Step 1 successfully passes, verify the Oracle Access Manager protection policies and confirm that the Essbase cluster lookup URL is excluded from those policies
Problem
If the host or port for Logical Web App components in the EPM Registry do not exactly match the actual host and port that EPM Web applications are running on in the BIDomain
domain, there may be connection or launch issues for EPM Web applications from within the Fusion user interface. In this case, you must update the host and port for Logical Web App components in EPM Registry.
Solution
To resolve the issue, perform the following steps:
Problem
The following error about Oracle Enterprise Scheduler Essbase Cube creation in the BIDomain
domain is returned because of a Hyperion security username and password authentication failure:
EPMCSS-00301: Failed to authenticate user. Invalid credentials. Enter valid credentials.
Solution
To resolve this issue, verify that the password stored in credential store for Application Identity (App ID) used by the Oracle Enterprise Scheduler job to connect to Essbase exactly matches the password for the given Application Identity in the underlying LDAP Identity Store by performing the following steps:
This section describes common problems and solutions for EPM Workspace. It contains the following topics:
Problem
Errors occur with certain functionality.
Solution
To begin debugging, perform the following steps:
Problem
If the http://
server_name
:19000/workspace/
URL fails to respond or an error occurs, the following information explains the task flow that the software requires, to assist in troubleshooting.
Workspace initialization happens at the first request, not at server startup. If initialization fails, it is reattempted at every subsequent request. Any error during initialization is logged in the workspace.log
file. The error message displays a page that replaces the normal Workspace Log on screen. Finally, the error is reported in the status report servlet, /workspace/status
. Only the log files include Exception stack traces.
Solution
The following tasks must successfully complete in order before Workspace allows log ons, and can be matched up in the workspace.log
file:
Parse and validate the file /conf/WSProducts.xml
in the Workspace Web application.
Initialize the Shared Services Registry:
Connect to the Shared Services Registry.
Find the unique WORKSPACE
component in the Shared Services Registry.
Find the unique Workspace LOGICAL_WEB_APP
component in the Shared Services Registry.
View the Workspace configuration properties from LOGICAL_WEB_APP
.
Find at least one WEB_SERVER
component that is a child of WORKSPACE
.
Update LOGICAL_WEB_APP
with host and port information from the Oracle WebLogic Server MBean.
Update LOGICAL_WEB_APP
with any missing configuration properties.
Initialize Shared Services.
Scan the Shared Services Registry for integrated products, and match every discovered product with a configuration file from the following resources:
/conf/WSProducts.xml
(Workspace)
WorkspaceConfig
file attribute of LOGICAL_WEB_APP
(all other products)
This section describes common problems and solutions for Calculation Manager. The following topics are discussed:
If no Essbase applications are listed under the Essbase node, it could be due to any of the following reasons:
You are not provisioned to work with Calculation Manager. There must be at least one of the following access privileges to work with Calculation Manager:
Create General Ledger Allocation Rules
Administer Allocation Rules
Generate General Ledger Allocation Rules.
The Essbase cluster name is not Essbase_FA_Cluster
. If the Essbase server is not under this cluster, it is ignored by Calculation Manager.
The stripe ID for General Ledger is different than the stripe ID for Workspace, so different security may be applied when Calculation Manager communicates with Essbase. Check the Calculation Manager log file to ensure that the stripe ID (or the application ID) for Calculation Manager is the same as the stripe ID for General Ledger.
The Essbase application contains an empty Comment field. Each Essbase application must contain at least one character in the Comment field, or it is ignored by Calculation Manager.
The application is not an Essbase aggregate storage application; only Essbase aggregate storage applications may be used with General Ledger.
Problem
Business rules cannot be deployed from Calculation Manager to General Ledger, and the following error message is received:
no WSDLLOCATION set
Solution
In the EPM registry, ensure that the WSDLLOCATION
property is defined for Calculation Manager. The WSDLLOCATION
property contains the General Ledger web services URL.
This section describes common problems and solutions for Smart View. The following topics are discussed:
Problem
Smart View collects and records events, errors, and other information in a log file, typically SmartViewLogs.log
. When experiencing performance or other issues, enable the logging in this file of additional information about profiling and requests and responses between Smart View and the server. This additional information can help Oracle Support to troubleshoot the issues.
Solution
To enable additional troubleshooting information, perform the following steps:
To improve performance, when there is no longer a need to log profiling and request/response information, delete the Profile entry that was created in the registry.
Problem
Smart View may become disabled in Microsoft Office applications.
Solution
Smart View is a COM add-in, which Microsoft Office applications can disable. To re-enable Smart View, follow instructions in Excel Help for re-enabling COM add-ins.
Problem
The server takes longer to process a Smart View operation than the timeout value set on the client computer, and users receive a connection timeout error, or zero values may be displayed for Smart View functions.
Solution
To resolve this issue, increase the timeout limit for Smart View client computers. Smart View uses Win-Inet APIs to communicate with the provider. These are the same modules that Internet Explorer uses. To increase the timeout value for a Windows client computer, perform the following steps:
Problem
The Shared Connections panel of the Smart View Panel displays no server names. This typically happens when the applications are not properly registered during installation and configuration.
Solution
Review the information in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide to ensure that applications and servers are properly configured.
This section describes common problems and solutions for Financial Reporting. The following topics are discussed:
This section describes the following common problems and solutions for setting up data sources and debugging setup and connectivity issues:
Problem
It is not possible to connect to an Essbase cube.
Solution
To resolve this issue, verify that the Essbase Server name and port are correct. Verify the user credentials used to make the connection are correct and the User has at least read rights to the cube.
Problem
An error occurred while creating a database connection.
Solution
To resolve this issue, check the Financial Reporting log file. If the log file has the following error, a Catalog GUID refresh is required:
"Caused by: javax.jcr.LoginException: access denied for user to path /users/userid"
For more information, see the Refreshing User GUIDs section in the Security Guide for Oracle Business Intelligence Enterprise Edition.
This section describes common problems and solutions for setting up data sources and debugging setup and connectivity issues:
Invalid Grid Error When Running a Report: Re-Save to the Database
Financial Reporting Cannot be Accessed from Workspace: Check Application Status Using Log Files
Unable to Connect to Financial Reporting Through a Firewall: Find and Modify MBean Properties
Error “Application HReports Is not Defined": Start the fressclient.ear Application
Permission Errors in Batch Scheduler: Check User Permissions
Problem
When running a report, following error is displayed:
Error 1012:Report contains an invalid grid. The following dimensions could not be found: <i>xxx</i>
This error may occur if the database was recently changed on the report.
Solution
To resolve the issue, open and save the report that has mismatched dimensions. This causes the dimensions that existed in the old database connection but not in the new database connection to be removed. The dimension and its members that existed in the rows and columns are removed from the grid. If, as a result of the removal, no dimension exists in the row or column, add a valid dimension to the cleared row or column in order for the report to run. Dimensions that exist in the new database connection but not in the old one, are added to the POV.
Problem
Financial Reporting cannot be accessed from Workspace.
Solution
To resolve this issue, perform the following steps:
Check if the Financial Reporting web application is running. In Internet browser, enter the protocol //server:port/hr/status.jsp
. If the web application is running, the following message is displayed:
The Oracle© Hyperion Financial Reporting, Fusion Edition Web application is available.
View the Financial Reporting log file fr.log
from the following directories to see if there are any com.sun.xml.ws.wsdl.parser
related errors:
(UNIX) DOMAIN_HOME/servers/server_name/logs/financialreporting (Windows) DOMAIN_HOME\servers\server_name\logs\finsncialreporting
In this case, it is possible that analytics web application is not running. If fr.log
contains multiple instances of Caused by: javax.jcr.LoginException: access denied for user to path /users/
userid
, then a Catalog GUID refresh is required.
For more information, see the Refreshing User GUIDs section in the Security Guide for Oracle Business Intelligence Enterprise Edition.
Problem
It is not possible to connect to Financial Reporting through a firewall from the Financial Reporting Studio.
Solution
By default, Financial Reporting components communicate with each other through Remote Method Invocation (RMI) on dynamically assigned Transmission Control Protocol (TCP) ports. To communicate through a firewall, you must specify the port for each Financial Reporting component separated by the firewall in the JConsole.exe
file, and then open the necessary ports in your firewall. In addition, you may need to open ports for the Reports Server RDBMs, for data sources that you report against, and for LDAP/NTMLM for external authentication. Once connected, all RMI Services can use anonymous ports by default for communication. Alternatively a range of ports can be configured for communication by setting RMIPortRangeLower
and RMIPortRangeUpper
within the Financial Reporting configuration. You can change the port assignments to use in a firewall environment for servers in the Financial Reporting Mbeans called RMIPortRangeUpper
and RMIPortRangeLower
.
To locate the Financial Reporting MBeans properties to modify in Fusion Applications Control, perform the following steps:
Problem
When the Batch Scheduler is opened, the following error displays:
application HReports is not defined
Solution
This may happen if the fressclient.ear
application is not started in the General Ledger's Oracle Enterprise Scheduler domain.
To resolve this issue, from the Oracle WebLogic Server Console for the Oracle Enterprise Scheduler domain, perform the following to steps:
Problem
When the Batch Scheduler is opened, or at the time of job submission, permission errors are shown.
Solution
This may happen if the user is not granted the oracle.as.scheduler.security.MetadataPermission
permission. To resolve this issue, perform the following steps:
Check if the user has oracle.as.scheduler.security.MetadataPermission
permission in the fscm
stripe using Fusion Applications Control.
This section describes common problems and solutions for Oracle Hyperion Provider Services. The following topics are discussed:
Problem
Sometimes Provider Services appears not to be functional.
Solution
Determine whether Provider Services is running, and restart if necessary. In addition, check port connectivity.
To determine whether Provider Services is running, perform the following steps:
If Provider Services version information is not provided in a user interface, it is possible to find the information in the following locations:
Operating system console window that is displayed when the Provider Services server is running
Provider Services log files
It might be necessary to monitor the number of sessions on a Provider Services server.
To do so from Administration Services Console, perform the following steps:
It might be necessary to monitor active-active Essbase clusters.
To do so from Administration Services Console, perform the following steps:
It might be necessary to enable or disable individual active-active Essbase cluster components. To do so, follow the steps in the Oracle Hyperion Enterprise Performance Management System High Availability and Disaster Recovery Guide.
This section describes common problems and solutions. It contains the following topics:
Essbase Agent Startup Fails with "Error: FUSIONAPPID not Specified in the cfg File"
Essbase Agent Startup Fails with "Error While Loading Shared Libraries"
An Application Stops Responding: Search Logs for Error Messages
An Essbase Application Will Not Start or Network Error Displayed: Check for Port Conflict
Cannot Stop an Application Process: Check Logs and Forcefully Terminate if Needed
Essbase Fails to Start in Cluster Mode: Check for Hostname Qualification Mismatch
System Error "Failed to Open File" on UNIX: Increase Maximum Number of Open File Descriptors
GL Writeback Fails with "Accounting Date Conversion" Error: Check Date String Format
GL Writeback Fails with "Group ID Node" Error: Check User Group IDs
GL Writeback Fails with "Not a Valid GL Application" Error: Check cubeMap.xml
GL Writeback Fails with "SQL Database Connection" Error: Check SQL Driver Setup
Network Error "Cannot Send Data"/"Cannot Receive Data": Check xcp File and Timeout Parameters
OPMN Fails to Start Essbase in High-Availability Mode: Check ARBORPATH Variables
"Invalid Item Index in Security File": Fix Corrupt Security File
Find Out if Essbase is Running by Checking Essbase Agent Status
Log files are the best tools for analyzing what might be wrong with the system configuration. The log file, the defaults it ships with, and instructions for changing change those defaults will help with the analysis. The following list includes the log files for Essbase:
Essbase log files
(UNIX) APPLICATIONS_CONFIG/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/Essbase.log (Windows) APPLICATIONS_CONFIG\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\essbase\Essbase.log
Oracle Diagnostic Logging (ODL) logs
(UNIX) APPLICATIONS_CONFIG/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/ESSBASE_ODL.log (Windows) APPLICATIONS_CONFIG\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\essbase\ESSBASE_ODL.log
Lease Manager logs
(UNIX) APPLICATIONS_CONFIG/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/leasemanager_essbase_machine_name.log (Windows) APPLICATIONS_CONFIG\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\leasemanager_essbase_machine_name.log
Shared Services logs
(UNIX) APPLICATIONS_CONFIG/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/SharedServices_Security_Client.log (Windows) APPLICATIONS_CONFIG\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\SharedServices_Security_Client.log
OPMN logs
(UNIX) APPLICATIONS_CONFIG/BIInstance/diagnostics/logs/OPMN/opmn/opmn.log (Windows) APPLICATIONS_CONFIG\BIInstance\diagnostics\logs\OPMN\opmn\opmn.log
Essbase ping log
(UNIX) APPLICATIONS_CONFIG/BIInstance/diagnostics/logs/OPMN/opmn/EssbasePing.log (Windows) APPLICATIONS_CONFIG\BIInstance\diagnostics\logs\OPMN\opmn\EssbasePing.log
OPMN debug log
(UNIX) APPLICATIONS_CONFIG/BIInstance/diagnostics/logs/OPMN/opmn/debug.log (Windows) APPLICATIONS_CONFIG\BIInstance\diagnostics\logs\OPMN\opmn\debug.log
The system will generate the OPMN debug log only if DEBUG mode is turned on in opmn.xml
.
OPMN console log
(UNIX) APPLICATIONS_CONFIG/BIInstance/diagnostics/logs/OPMN/opmn/console*.log (Windows) APPLICATIONS_CONFIG\BIInstance\diagnostics\logs\OPMN\opmn\console*.log
The system will generate the OPMN console log only if DEBUG
mode is turned on in opmn.xml
.
Problem
The Essbase Agent startup fails with the following error:
Fatal Error: FUSIONAPPID not specified in the cfg file
Solution
To modify essbase.cfg
and restart the Essbase server, perform the following steps:
Locate the essbase.cfg
file in the following directories:
(UNIX) APPLICATIONS_CONFIG/BIInstance/Essbase/essbaseserver_name/bin (Windows) APPLICATIONS_CONFIG\BIInstance\Essbase\essbaseserver_name\bin
Make sure that the following entry is present in essbase.cfg
:
FUSIONAPPID appidname
Restart the Essbase server.
To restart the Essbase server using opmnctl
, perform the following steps:
Determine the current status as follows:
(UNIX) APPLICATIONS_CONFIG/BIInstance/bin/opmnctl status (Windows) APPLICATIONS_CONFIG\BIInstance\bin/opmnctl status
OPMN generates a list of the running components and processes. The following message indicates that the Essbase Server (essbaseserver1
) is already running:
Processes in Instance: BIInstance ---------------------------------+--------------------+---------+--------- ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------- essbaseserver1 | Essbase | 27879 | Alive coreapplication_obiccs1 | OracleBIClusterCo~ | 10828 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 18308 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 18337 | Alive coreapplication_obips1 | OracleBIPresentat~ | 26455 | Alive coreapplication_obis1 | OracleBIServerCom~ | 21716 | Alive
Restart the Essbase server as follows:
(UNIX) APPLICATIONS_CONFIG/BIInstance/bin/opmnctl restartproc ias-component=component_name (Windows) APPLICATIONS_CONFIG\BIInstance\bin\opmnctl restartproc ias-component=component_name
For example:
APPLICATIONS_CONFIG/BIInstance/bin/opmnctl restartproc ias-component=essbaseserver1
To start Essbase server using Fusion Applications Control, perform the following steps:
From the navigation pane, expand the farm and then WebLogic Domain for the BIDomain
domain.
Expand Essbase Servers, and then select the Essbase server.
From the Essbase Server menu, choose Administration, then Ports Configuration.
Select the Listen port, and then click Edit.
Change the port number, and then click OK.
From the Essbase Server menu, choose Control, then Restart.
Problem
The Essbase Agent startup fails with the following error:
Error while loading shared libraries: libARicu24.so: cannot open shared object file: No such file or directory
Solution
To modify opmn.xml
file and restart the Essbase server, perform the following steps:
Locate the opmn.xml
file in the following directories:
(UNIX) APPLICATIONS_CONFIG/config/OPMN/opmn (Windows) APPLICATIONS_CONFIG\BIInstance\config\OPMN\opmn
Update the following ODBC-related entries in opmn.xml
as follows:
<variable append="true" id="LD_LIBRARY_PATH" value="$ORACLE_HOME/common/ODBC/Merant/7.1.4/lib$:$ORACLE_HOME/jdk/jre/lib/i386/server$:$ESSBASEPATH/bin"/>
<variable id="ODBCINI" value="$ORACLE_HOME/common/ODBC/Merant/7.1.4/odbc.ini"/>
<variable id="ODBCINST" value="$ORACLE_HOME/common/ODBC/Merant/7.1.4/odbcinst.ini"/>
Restart the Essbase server by performing the following steps:
Determine the current status as follows:
(UNIX) APPLICATIONS_CONFIG/BIInstance/bin/opmnctl status (Windows) APPLICATIONS_CONFIG\BIInstance\bin/opmnctl status
OPMN generates a list of the running components and processes. The following message indicates that the Essbase Server (essbaseserver1
) is currently running:
Processes in Instance: BIInstance ---------------------------------+--------------------+---------+--------- ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------- essbaseserver1 | Essbase | 27879 | Alive coreapplication_obiccs1 | OracleBIClusterCo~ | 10828 | Alive coreapplication_obisch1 | OracleBIScheduler~ | 18308 | Alive coreapplication_obijh1 | OracleBIJavaHostC~ | 18337 | Alive coreapplication_obips1 | OracleBIPresentat~ | 26455 | Alive coreapplication_obis1 | OracleBIServerCom~ | 21716 | Alive
Restart the Essbase server as follows:
(UNIX) APPLICATIONS_CONFIG/BIInstance/bin/opmnctl restartproc ias-component=component_name (Windows) APPLICATIONS_CONFIG\BIInstance\bin\opmnctl restartproc ias-component=component_name
For example:
APPLICATIONS_CONFIG/BIInstance/bin/opmnctl restartproc ias-component=essbaseserver1
Problem
A communication error occurs when attempting to issue commands using the opmnctl
command line for OPMN.
For example:
qtfhp3:/vol1/nnguyen/rc11/Oracle/Middleware/user_projects/epmsystem1/bin]$ opmnctl status RCV: No such file or directory Communication error with the OPMN server local port. Check the OPMN log files opmnctl status: opmn is not running.
Solution
To modify opmn.xml
, perform the following steps:
Problem
An Essbase application stops responding or shuts down abnormally.
Solution
To determine why the application is not responding, perform the following steps:
Problem
An application does not respond after being started, or an error message like the following is displayed in the Essbase log file:
Network Error 10048 : Unable to Bind Host Server Socket On Port 4213
Solution
A port conflict may be occurring. Correct the port-related entries in opmn.xml
.
Update the Essbase port range in opmn.xml to match the port specified in the configuration file as follows:
<port id="essbase-port-range" range="32768-33768"/>
Problem
During an operation on an Essbase aggregate storage database, the following error is displayed:
Persistent data does not match the outline. There is no member in dimension [Abc] for member number [12345]. Data is corrupted.
Solution
To clear the database and reload it from the original sources or from a saved exported backup, perform the following steps:
Problem
An Essbase application process cannot be shut down.
Solution
To resolve this issue, check the log messages to see if the application is still involved with cleanup or processing. If required, forcefully terminate the application process.
To check the application log for active processing, perform the following steps:
Access the application log. Note the following locations:
(UNIX) APPLICATIONS_CONFIG/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/app/appname/appname.log (Windows) APPLICATIONS_CONFIG\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\essbase\app\appname\appname.log
Check the application log and look for the following message:
RECEIVED SHUTDOWN COMMAND - SERVER TERMINATING.
If the proceeding message is seen, wait a few minutes to allow the application to self-terminate. The application may be doing cleanup tasks associated with the shutdown process.
If the following message is seen, the application is still processing user requests. Wait for user requests or any other operation that is still in progress to terminate, and then try shutting down the application.
Cannot unload database dbname while user username is performing database operation. Wait for the user to complete the operation, or ask the user to abort it. Log out all users and then unload the database. Cannot unload database dbname when it is still in use
If there is a need to terminate the application, perform the following steps:
If there is a need to terminate the application even when there are user requests in progress on the database, run the following sequence MaxL statements to forcefully terminate user requests:
#Display active sessions to see current requests display session on application appname #Disallow new connections to the application alter application appname disable connects; #Force logout of all, and terminate requests alter system logout session on database appname.dbname force;
After forcefully logging out all users, wait for a few minutes, and then use the following MaxL statement to check if any user requests are still running:
#Display active sessions display session on application <appname>;
If there are no requests running, attempt to stop the application process.
After the application starts again, enable connects.
Problem
The Essbase port numbers need to be changed when Essbase is installed in high-availability mode.
Solution
To run the Essbase failover automation script to change the Essbase port, perform the following steps:
Problem
The Essbase port numbers need to be changed when Essbase is installed in non-high-availability mode.
Solution
Go to Fusion Applications Control and change the Essbase port by performing the following steps:
BIDomain
domain.Problem
Following a data load failure to a specified load buffer, the following error displays for subsequent loads to the same load buffer:
Data load buffer [123] does not exist.
The user uses the MaxL command that creates and commits buffer in one step, but then commit again using a separate step. The load buffer commit must be used with another MaxL command pair.
Data loads initialize a load buffer and load multiple data files to it before committing it to the cube. If an error occurs that causes one of the steps to fail, then the load buffer is automatically destroyed, causing all subsequent steps to fail with the previous error.
Solution
Use one of the following methods to correct this error:
Determine the cause of the original data load error and try to resolve it.
Set the Essbase data load options to indicate that the data load should not be aborted on error; instead, have data load errors written or appended to the log file
Problem
Upon attempting to load data into an Essbase aggregate storage database, the following error displays:
Specified load buffer resource usage [100] is above currently available value [0].
Other ongoing data load operations have reserved part of the cache for their load buffers.
Solution
Use one of the following methods to correct this error:
Reduce the resource usage for this data load, and try again. If you are using MaxL, you must explicitly create the load buffer, using the optional resource_usage
argument. For example:
alter database AsoSamp.Sample initialize load_buffer with buffer_id 1 resource_usage .5;
Wait for other operations to finish.
To see what reservations have been made to the cache resources, run the following MaxL statement:
query database "app"."db" list load_buffers;
For more information about the query database
, alter database
, and other MaxL
statements, see the Oracle Essbase Technical Reference.
Problem
Sometimes Essbase does not start when it is in cluster mode and Oracle Business Intelligence domain is installed with a non-domain-qualified host name.
Solution
The error occurs when the Essbase host specified in the cluster configuration properties file, EssFOConfig.properties
, is domain-qualified, but is not in the EPM Registry, leading to a mismatch. For more information about viewing the EPM Registry, see the Viewing the Components in the Shared Services Registry section in the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
To check if there is an Essbase host name qualification mismatch, perform the following steps:
Problem
When the user attempts to log in to Essbase, the login attempt fails. The problem may be an authentication failure. When the Essbase login fails due to an authentication problem, it reports the following errors:
ERROR - 103 - Unexpected Essbase error 1051440. ERROR - 1051440 - Essbase user [bi-001] Authentication Fails against the Shared Services Server with Error [EPMCSS-1009004: Failed to read data from the policy store.].
Solution
To resolve this issue, perform the following steps:
To determine login failure problems by gathering detailed error messages, perform the following steps:
To gather debug-level error messages, perform the following steps:
Keep the debug statistics available for diagnostic purposes, in case there is a need to contact Technical Support.
To check for and correct BI domain login errors, perform the following steps:
The following table provides the names of each file along with the corresponding error message to identify if there is a debug login failure problem. Go to each file listed in the table and search for the corresponding error message. If one or both of the files contain errors, use the following procedure to correct them:
Table 21-1 File Names and Error Messages
File Name | Error Message |
---|---|
|
|
|
|
To add a valid Essbase user name to the credential store from Fusion Applications Control, perform the following steps:
Problem
The following error occurs on a UNIX platform:
Failed to open file [filename]: a system file error occurred. Please see application log for details.
Solution
To open a file on UNIX, perform the following steps:
ulimit
command.Problem
GL writeback fails with the following error:
The accounting date conversion failed for %s to %s in the ACCOUNTING_DATE column. Unable to proceed with GL export.
Solution
This error may occur when GL writeback cannot format the date string in the way that GL tables expect.
To fix this issue, make sure that the <DATE_FORMAT>
tag in the cubeMap.xml
file has date format represented in one of the following acceptable formats, and that it matches with the date value stored in the accounting date alias table of the outline. The following are the acceptable date formats:
mon dd yyyy Month dd yyyy mm/dd/yy mm/dd/yyyy yy.mm.dd dd/mm/yy dd.mm.yy dd-mm-yy dd Month yy dd mon yy Month dd, yy mon dd, yy mm-dd-yy yy/mm/dd yymmdd dd Month yyyy dd mon yyyy dd/mon/yy yyyy-mm-dd yyyy/mm/dd Day, Month dd, yyyy
Problem
GL writeback fails with the following error:
The group id node has active GL operations in state [<state_name>]. Use the appropriate API call in sequence. Unable to proceed with [api name] call.
Solution
This error may occur if more than one user tries to use the GL writeback-related API calls with the same group ID. To fix this issue, ensure that all users using GL writeback operations are using different group IDs.
Problem
GL writeback fails with the following error:
This application is not a valid GL application for Essbase.
Solution
The error may occur if the cubeMap.xml
file is either not present in the app
/
db
directory, or is not parsed properly. For the GL writeback to work properly, the cubeMap.xml
file must be present and contain the required information to be parsed successfully.
To confirm that cubeMap.xml
was parsed correctly, perform the following steps:
Problem
GL writeback fails with the following error:
Failed to Establish Connection With SQL Database Server. See log for more information.
Solution
The error may occur if the SQL drivers are not set up correctly. To confirm that the SQL drivers are set up correctly, perform the following steps:
Problem
When performing an operation against an Essbase cube, one of the following errors occurs:
Network error [12345]: Cannot Send Data
Network error [12345]: Cannot Receive Data
Solution
xcp
file is found in the following location, save it and contact Oracle Support:
(UNIX) APPLICATIONS_CONFIG/BIInstance/diagnostics/logs/Essbase/essbaseserver_name/essbase/app/appname/log000001.xcp (Windows) APPLICATIONS_CONFIG\BIInstance\diagnostics\logs\Essbase\essbaseserver_name\essbase\app\appname\log000001.xcp
In essbase.cfg
, increase the network timeout parameters using the settings NETDELAY
and NETRETRYCOUNT
. For more information, see Essbase.cfg Configuration Settings section in Oracle Essbase Technical Reference.
Problem
Sometimes OPMN fails to start Essbase in high-availability mode.
Solution
For Essbase clustering to work, all Essbase failover cluster data must be on shared storage with the ARBORPATH
variables set correctly. To confirm that Essbase can start in high-availability mode, perform the following steps:
Ensure that OPMN is started by a network or domain user.
Ensure that ARBORPATHs
are specified as mapped drives, and not as UNC paths.
The following are three primary restructure failure errors:
Problem
During a dimension build or outline restructure, error code 1130203
occurs.
Solution
The error indicates that the operation failed due to insufficient memory. Use one of the following methods to correct this error:
Increase the amount of virtual memory available to the operating system.
If Essbase is running on a 32-bit platform, keep in mind that the maximum memory available to Essbase is between 2 GB and 4 GB, regardless of how much RAM is installed on the machine. Because Essbase loads both the old and new outlines in memory during the restructure, there is a restriction on the largest outline that can be modified on such a machine. For example, if the platform only allows 2 GB of memory to be used by a process, and an Essbase application process is already using 200 MB memory, then the maximum-size outline that can be modified is 900 MB. Switching to a 64-bit installation of Essbase will lift this limitation.
Problem
During dimension build or outline restructure, outline validation fails with one of the following errors:
There were errors validating the outline. Please check the error file.
Outline has errors.
Solution
Review the application log or the error file (if available) to see what specific errors are causing the validation error.
Problem
During dimension build or outline restructure, one of the following errors occurs:
Cannot write the new outline file during the restructuring of [%s]
Error writing outline change log file for database [%s]
Solution
Check the application log for other errors. If none are found, check to see if the file system is full. Remember that making a change to an Essbase outline requires at least as much free space as the existing outline.
Problem
The Console.log
displays the following error:
Fatal Error: Invalid item index in security file
Solution
In this case, the Essbase security file, essbase.sec
, is invalid or corrupt. Use one of the following methods to correct this error:
Restart Essbase using the latest backup security file by copying essbase_timestamp.bak
to essbase.sec
. Both files are located in the following directories:
(UNIX) APPLICATIONS_CONFIG/BIInstance/Essbase/essbaseserver_name/bin (Windows) APPLICATIONS_CONFIG\BIInstance\Essbase\essbaseserver_name\bin
For more information, see the Managing the Essbase Security File section in the Oracle Essbase Database Administrator's Guide.
Open the essbase.cfg
file and set the ENABLESWITCHTOBACKUPFILE
setting to TRUE
. This setting allows Essbase to automatically use a backup security file. The essbase.cfg
file is located in the following directories:
(UNIX) APPLICATIONS_CONFIG/BIInstance/Essbase/essbaseserver_name/bin (Windows) APPLICATIONS_CONFIG\BIInstance\Essbase\essbaseserver_name\bin
If Essbase.cfg
is edited, restart Essbase to enable the change.
For more information, see the Essbase.cfg Configuration Settings section in the Oracle Essbase Technical Reference.
Problem
When the Administrator does not know if Essbase is running, the following OPMN command can be used to determine if the Essbase agent is running:
(UNIX) APPLICATIONS_CONFIG/BIInstance/bin/opmnctl status (Windows) APPLICATIONS_CONFIG\BIInstance\bin/opmnctl status
Solution
To start Essbase server using Fusion Applications Control, perform the following steps
BIDomain
domain.Problem
When attempting to load data into an Essbase aggregate storage database or while building aggregate views, the following error is displayed:
Failed to extend file [<path>/ess0001.dat]: a system file error occurred. Please see application log for details.
Solution
This error indicates that the file system is out of space. Essbase can require significant temporary disk storage while performing a data load or aggregate view build. The "default" tablespace is the location where cube data is stored. The "temp" tablespace is where Essbase writes temporary data while building the cube. By default, both tablespaces are on the disk drive where Essbase is installed.
During the operation, the space required by the temp tablespace is at least as big as the resulting change in the database size, so the total free space required is at least twice as big as the resulting change to the database size. For example, loading a database that is 1GB will require at least 2GB of free space. Building 10GB worth of aggregate views will require at least 20GB of free space. Note that after the operation is complete, the files created in the temp tablespace are deleted.
Use one of the following methods to correct this error:
To correct this error, use MaxL statements to view or change the tablespace settings.
If the tablespace locations do not have enough free space, consider moving one or both tablespaces to different disk drives, or limit the size of the existing file locations and add new locations on other disk drives. It is not possible to remove a tablespace location that already contains data.