Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
MANAGEMENT SYSTEM
RELEASE 11.1.1.3
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About Troubleshooting EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Assumed Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installation Documentation Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Contents iii
Performance Management Architect Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Calculation Manager Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Essbase Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Essbase Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Administration Services Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Essbase Studio Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Integration Services Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Provider Services Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Reporting and Analysis Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Configuring Log Properties for Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Analyzing Reporting and Analysis Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Log File Names and Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Financial Performance Management Applications Logs . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Financial Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Planning Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Business Rules Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Performance Scorecard Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Profitability and Cost Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Data Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
FDM Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
ERP Integrator Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Data Relationship Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
iv Contents
Errors During Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Error on Configuration Task Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Database Configuration Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Failure Deploying to Application Server Without Configuration Errors . . . . . . . . . . . 58
Out-of-Memory Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Resolving Connection Failures and Restarting Services . . . . . . . . . . . . . . . . . . . . . . . . . . 58
SSL Communication Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
UNIX Specific Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Apache Tomcat Startup Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Preparing JVM...Error Writing to This File Error . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Contents v
Chapter 6. Troubleshooting EPM Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Tips and Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Connection Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Tomcat Startup Fails and EPM Workspace is Unavailable . . . . . . . . . . . . . . . . . . . . . . . . 76
Logon Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Startup Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Logging On When the EPM Workspace Agent is Down . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Cannot Access Configuration Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Failure to Access Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
vi Contents
Failure Deploying to WebSphere after Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Integration with EPM Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Accessing Performance Management Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Failure Accessing Performance Management Architect Dimension or Application
Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Using IBM DB2 with Performance Management Architect . . . . . . . . . . . . . . . . . . . . 95
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Contents vii
viii Contents
Introduction
1
In This Chapter
About Troubleshooting EPM System Products............................................................ 9
Assumed Knowledge........................................................................................ 9
Installation Documentation Roadmap ...................................................................10
Assumed Knowledge
This guide is for administrators who install, configure, and manage EPM System products. It
assumes the following knowledge:
l Security and server administration skills
l Windows or UNIX administration skills
l Web application server administration skills
l A strong understanding of your organization's security infrastructure, including
authentication providers such as Oracle Internet Directory, LDAP, or Microsoft Active
Directory, and use of SSL
l A strong understanding of your organization's database and server environments
l A strong understanding of your organization's network environment and port usage
Meeting system requirements Oracle Hyperion Enterprise Performance Management System Certification Matrix
(http://www.oracle.com/technology/products/bi/hyperion-supported-platforms.
html)
Planning the installation Oracle Hyperion Enterprise Performance Management System Installation Start
Here
l Installing and configuring EPM System products Oracle Hyperion Enterprise Performance Management System Installation and
Configuration Guide
l Automatically deploying EPM System products
l Starting EPM System products
l Validating the installation
l Upgrading EPM System products
Securing EPM System and provisioning users Oracle Hyperion Enterprise Performance Management System Security
Administration Guide
Table 2 lists the documents to consult for additional installation tasks that you might need to
perform.
Manually deploying EPM System products Oracle Hyperion Enterprise Performance Management System Manual Deployment
Guide
Creating a backup of product and application data Oracle Hyperion Enterprise Performance Management System Backup and
Recovery Guide
Migrating from one environment to another Oracle Hyperion Enterprise Performance Management System Lifecycle
Management Guide
Enabling SSL Oracle Hyperion Enterprise Performance Management System SSL Configuration
Guide
Clustering EPM System applications for high Oracle Hyperion Enterprise Performance Management System High Availability
availability Guide
10 Introduction
Troubleshooting Basics
2
In This Chapter
Meeting System Requirements ..........................................................................11
Reviewing the Installation Start Here ....................................................................11
Reviewing the Readme ...................................................................................12
Using the Installation Guide ..............................................................................12
Validating the Installation and Configuration............................................................12
Using Logs ..................................................................................................13
Using My Oracle Support (MetaLink 3) ..................................................................13
Accessing Technical Support Resources ................................................................13
12 Troubleshooting Basics
The results of the tests are saved in HTML format. For instructions, see the Oracle Hyperion
Enterprise Performance Management System Installation and Configuration Guide
l Check for exceptions and errors in the installation logs to ensure that all necessary
components were installed successfully. See Chapter 3, “Using EPM System Logs.”
l Check that all configuration tasks succeeded, as follows:
m The Oracle's Hyperion Enterprise Performance Management System Configurator
summary panel does not display failures or warnings.
m HYPERION_HOME/logs/config/configtool_err.log is empty.
m No exceptions are displayed in HYPERION_HOME/logs/config/configtool.log.
Using Logs
A fundamental troubleshooting technique is to enable and use debugging information in
product log files. Use this technique before calling Technical Support so that you can provide
specific information about your issue. See Chapter 3, “Using EPM System Logs.”
Using Logs 13
14 Troubleshooting Basics
Using EPM System Logs
3
In This Chapter
Common Log File Location ................................................................................15
Log File Size and System Performance ..................................................................15
What To Do Before Contacting Technical Support ......................................................16
Installation Logs............................................................................................16
EPM System ConfiguratorLogs ............................................................................17
Application Server and Web Server Logs ................................................................17
Foundation Services Logs .................................................................................18
Essbase Logs ...............................................................................................30
Reporting and Analysis Logs ..............................................................................37
Financial Performance Management Applications Logs................................................43
Data Management Logs ...................................................................................47
Note: The log locations listed in this chapter are the default locations.
Note: Some products may write log files to both common and other folders, as indicated in this
chapter.
Installation Logs
You can specify the logging level for Oracle Hyperion Enterprise Performance Management
System Installer, Fusion Edition by editing the installTool.properties file, located in the
directory from which you launch the EPM System Installer.
Edit the following property:
log4j.rootLogger=
The DEBUG setting logs all debugging information, application warnings, application errors, and
fatal exceptions.
Table 3 lists the installation log files with their contents and locations. It also provides notes
about using the logs.
installTool-install.log Main log written by EPM HYPERION_HOME/ Do not delete this log.
System Installer to log user logs/install
Provide this log to Technical Support when
activity
reporting any issue with configuring EPM
System products.
installTool-install- Capture console normal and HYPERION_HOME/ Do not delete this log.
stderr.log error output. logs/install
Provide this log to Technical Support when
and reporting any issue with configuring EPM
System products.
installTool-install-
stdout.log
The DEBUG setting logs all debug, informational, application warnings, application errors, and
fatal exceptions.
Table 4 lists EPM System Configurator logs with their contents and locations. It also provides
information about using the logs.
Table 4 EPM System ConfiguratorLog Files
By default, configuration uses its own Apache Web Server, which is in HYPERION_HOME/
common/httpServers/Apache/2.0.59. You can modify log level and paths using
httpd.conf in APACHE_HOME/conf/.
registry.log Shared Services Registry activity. See “Shared Services Registry API Archive
Log” on page 22.
SharedServices_Audit.log Audit server errors while reading/writing audit information to the Archive
database or while configuring auditing
*Archive logs monthly. Shared Services log files can be locked to prevent the application server from editing or deleting the files. Consequently,
archive or delete the log files while the application server is not running. If the files are deleted, Shared Services automatically generates
replacement files.
Modify HSSLogger.properties to configure the log level settings for Shared Services:
HSSLogger.properties is in HYPERION_HOME/deployments/
app_server_name_and_version/SharedServices9/config for all supported application
servers.
After changing log levels you must restart the server for the log settings to take effect:
l If you change the log levels in the HSSLogger.properties file
l If security log levels are changed manually in CSS.xml and imported to the registry
After changing security log levels from the User Interface for CSS you do not need to restart the
server for the log settings to take effect.
ä To set log message levels for external authentication and single sign-on:
1 Launch Oracle's Hyperion® Shared Services Console.
2 Select Administration and then Configure User Directories.
3 In Defined User Directories, set the Logging level global parameter to DEBUG.
4 Click OK.
slapd -d -1 Enable all debugging Logs all OpenLDAP transactions and queries.
slapd -d 2 Debug packet handling For OpenLDAP, enables debugging of packet handling.
slapd -d 4 Heavy trace debugging Provides a large amount of trace with data searched in database.
slapd -d 8 Connection management Displays all data available in database with its internal process
logs.
slapd -d 16 Printout of packets sent and received Lists all packets sent and received.
slapd -d 32 Search filter processing Displays all OpenLDAP filter and search data.
slapd -d 64 Configuration processing Displays configured data such as Object class and its attributes.
slapd -d 128 Access control list processing For a resource, displays access-control data for users.
slapd -d 256 Stats log connections/operations/ For a resource, lists add, modify, and delete operations. (This
results option provides fewer logs than the -1 option.)
slapd -d 512 Stats log entries sent Displays connection number, operation number, and DN values.
slapd -d 1024 Print communication with shell Displays index properties of each attribute of an object class.
backends
slapd -d 4096 Database cache processing Displays cache processing data such as index parameters.
slapd -d 16384 Syncrepl consumer processing Displays replica processing operations (master-slave OpenLDAP
configuration).
Java
> To change the default location of the SharedServices_Security_client.log, add the
Java system property Djava.io.tmpdir=LOG_PATH to all JVMs. This will change the temp file
location for all applications running in that JVM.
Note: After updating this property, you must restart the application server.
Essbase
Pass the Java system property -Djava.io.tmpdir=LOG_PATH to the JVM as an environment
variable.
Windows
If ESS_CSS_JVM_OPTION3 is already in use, set this value for the next available
ESS_CSS_JVM_OPTION; for example, ESS_CSS_JVM_OPTION4.
Financial Management
ä To change the default location of the Security log for Financial Management:
1 On the Oracle Hyperion Financial Management, Fusion Edition application server, append: -
Djava.io.tmpdir=LOG_PATH to the value of the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial Management\Server
\Authentication\LibPath
Use a space to separate this value from existing values of the registry key. Also, ensure that
the property value is in enclosed quotation marks; for example "-
Djava.io.tmpdir=LOG_PATH".
2 Restart CASSecurity.exe on the Financial Management server for the new setting to take effect.
The DEBUG setting logs all debug, informational, application warnings, application errors, and
fatal exceptions. You can replace that setting with any of these options:
l INFO–Logs informational, application warnings, application errors, and fatal exceptions.
l WARN–Logs application warnings, application errors, and fatal exceptions.
l ERROR:–Logs application errors and fatal exceptions.
l FATAL–Logs only fatal exceptions.
server_messages_iHTMLServlet.log Log for the iHTML servlet (logs thin client data
representation)
server_messages_DataAccessServlet.log Log for the data access servlet (logs thick client or plug-
in calls to the data access service)
server_messages_LSM.log Log for the Local Service Manager (LSM) service; LSMs
provide support for Interactive Reporting distributed
services infrastructure.
server_messages_SearchIndexing.log Search Indexing and Query service (information about Archive every 12
searchable index and search queries) hours. Contains
valuable auditing
and debugging
data.
*You can roll and delete log files by time intervals or by file size. File size log rotation is controlled by
CompositeRollingAppender. Time interval log rotation is controlled by CompositeRollingAppender and a Java property
in the common services start file. See “Troubleshooting” in the Oracle Enterprise Performance Management Workspace Administrator's Guide.
†This log is in HYPERION_HOME/logs/BIPLUS.
agent.log Log file for the CMC Agent service, which HYPERION_HOME/logs/BIPlus/ Archive
starts named service configurations
agent_service.log Log file for the CMC Agent service, which HYPERION_HOME/common/workspacert/9.5.
starts named service configurations 0.0/logs
(Windows only)
cmcui.log Log file for the CMC UI Web application HYPERION_HOME/common/workspacert/9.5. Archive
server 0.0/logs
ä To log messages:
1 From the Hyperion menu, select Options, then Display.
2 Under Log Messages, select an option that specifies which messages to log, or select None to suppress
all messages.
l Information–All messages, including warnings and errors (Recommended for
diagnosing problems)
l Warnings–Warning and error level messages
l Errors–Error messages only
3 Select Route Messages to a Log File.
4 Optional: To clear the log when Smart View is launched, select Clear log file on next launch.
5 Click OK.
6 To have the settings take effect, you must refresh or perform a drill operation.
epma.log Lifecycle Management The maximum file size for this log is 4096KB. When the file reaches the @ maximum size,
activity it is saved and a new log file is started. The maximum number @ of saved log files is 5.
When the number exceeds 5, the oldest log file is @ deleted automatically.
Archiving this log is optional.
epma_err.log Information written by The maximum file size for the log is 1024KB. Only error messages are written into this file.
the Web server
awb.log Information written by The maximum file size for this log is 1024KB. When the file reaches the maximum size, it
the Web server is saved and a new log file is started. The maximum number of saved log files is 5. When
the number exceeds 5, the oldest log file is deleted automatically.
Archiving this log is optional.
DMEngine.log Data Synch Web The maximum file size for this log is 1024KB. When the file reaches the maximum size, it
application activity is saved and a new log file is started. The maximum number of saved log files is 5. When
the number exceeds 5, the oldest log file is deleted automatically.
Archiving this log is optional.
Windows Event Dimension Server The Windows Event Viewer can be configured to automatically delete old events as new
Viewer activity events get logged (recommended). Or, you can clear the event log as necessary; however,
because events from many different applications as well as Windows itself are logged to
the Event Viewer, you cannot clear the log for Dimension Server independently of the others.
Transaction logs Transactions These are in the database. You can choose to archive the database rows or optionally purge
the rows.
Note: View
transaction logs from
the Dimension Library
to
log4j.logger.com.hyperion.awb=DEBUG ,logfile, stdout
calcmgrserver.log By default, logs any errors HYPERION_ The maximum file size for this is 1024KB. When the file
and warnings as well basic HOME/logs/ reaches the maximum size, it is saved and a new log file is
connection information, such calcmgr started. The maximum number of saved log files is 5. When
as the Dimension Server URL, the number exceeds 5, the oldest log file is deleted
the Planning Server URL for a automatically.
given application, and so
Archiving this log is optional.
forth. Includes Lifecycle
Managementactivity.
calcmgrdeploy.log Business rules deployment HYPERION_ The log files can be rolled by file size. The number of rolled
information log. Logs HOME/logs/ log files and the file size to roll it to after can also be
exceptions that occur when Planning changed by modifying the RollingFileAppender
deploying rules from properties in the DEPLOYMENT_LOCATION/calcmgr/
Performance Management WEB-INF/conf/CalcMgrLog4j.properties file.
Architect/Calculation
Archiving this log is optional.
Manager into Planning.
calcmgrexecution. Business rules execution HYPERION_ The log files can be rolled by file size. The number of rolled
log exception log. HOME/logs/ log files and the file size to roll it to after can also be
Planning changed by modifying the RollingFileAppender
properties in the DEPLOYMENT_LOCATION/calcmgr/
WEB-INF/conf/CalcMgrLog4j.properties file.
calcmgrlaunch.log Calculation Manager HYPERION_ The log files can be rolled by file size. The number of rolled
business rules launch HOME/logs/ log files and the file size to roll it to after can also be
information log. The type of Planning changed by modifying the RollingFileAppender
information recorded in this properties in the DEPLOYMENT_LOCATION/calcmgr/
log is configurable in the WEB-INF/conf/CalcMgrLog4j.properties file.
CalcMgrLog4j.
Archiving this log is optional.
properties file.
log4j.logger.com.hyperion.calcmgr.common.GenericLogger=Value (for
example, log4j.logger.com.hyperion.calcmgr.common.GenericLogger=INFO)
3 Save the file.
After changing the Calculation Manager log levels you must restart the Planning application
server for Calculation Manager logs on Planning side.
Essbase Logs
The following sections contain information about Essbase product family logs.
For a complete listing of Essbase logs, see Oracle Essbase Database Administrator's Guide. For
information about the transaction log file for Essbase backup and recovery, see Oracle Hyperion
Enterprise Performance Management System Backup and Recovery Guide.
l “Essbase Logs” on page 30
l “Administration Services Logs” on page 32
l “Essbase Studio Logs” on page 33
l “Integration Services Logs” on page 35
l “Provider Services Logs” on page 36
Essbase Logs
The following sections contain information on Essbase log files.
dataload.err Data load and dimension build errors HYPERION_HOME/logs/ Keep these logs for
essbase/app support calls.
log0000x.xcp Information captured at the time of an HYPERION_HOME/logs/ Keep these logs for
abnormal termination essbase/app support calls.*
*See “Monitoring Data, Applications, and Databases” in the Oracle Essbase Database Administrator's Guide for information on exception logs
and the actions you can perform on them, including overwriting or retaining existing logs.
Essbase Logs 31
Rotating Essbase Logs
You can clear Essbase and application logs at any time, or upon restarting the server or
application. You must have administrator permissions to clear Essbase and application logs. You
should back up log files before clearing them. See “Monitoring Data, Applications, and
Databases” in the Oracle Essbase Database Administrator's Guide.
By default, new exception logs are created when Essbase, an application, or a database shuts
down abnormally. Subsequent exception logs are numbered sequentially. For example, if
log00001.xcp exists, the next log is named log00002.xcp, and so on. You can change a setting
in essbase.cfg to overwrite the existing exception log instead of creating a new one. See
“Monitoring Data, Applications, and Databases” in the Oracle Essbase Database Administrator's
Guide, and the Essbase Technical Reference.
esbstudioserver.log Essbase Studio Can be rotated or deleted. Contains information useful for troubleshooting by
server activity the administrator. Depending on the settings you make in the server.
properties file, records are automatically moved to a history copy, and can
be archived or deleted as appropriate. Logging level can be set by the
administrator.
cpld.log Essbase Studio Cannot be rotated. Contains history of Essbase Studio client activity. Logging
client activity level cannot be set by the administrator. No configuration options available.
SharedServices_Client_ Essbase Studio Logging level cannot be set by the administrator. No configuration options
Security.log security information available.
Essbase Logs 33
Rotating Essbase Studio Logs
Essbase Studio rotates the server log file by creating log history files. Log history files are older
versions of the log file that are generated automatically when the size of the server log file reaches
the limit specified in the logger.limit parameter. The extension “.n” is automatically
appended to the log history files; for example, esbstudioserver.log.1,
esbstudioserver.log.2, and so on. When the size of the current log file becomes bigger than
the size specified in the logger.limit parameter, the current log file and all log history files
are incrementally renamed, and a new current log file is created. When the number of log history
files reaches the limit set in the logger.count parameter, the oldest of the log history files is
removed to accommodate the new log file being created.
For example, by default, when the server log file reaches the 10 MB limit, the following happens
automatically:
esbstudioserver.log becomes esbstudioserver.log.1, esbstudioserver.log.1
becomes esbstudioserver.log.2, esbstudioserver.log.2 becomes
esbstudioserver.log.3, and so forth; and Essbase Studio Server creates the new current log
file, esbstudioserver.log.
Note: You can always manually delete old log files from the file system if they are no longer
needed.
You can change the default settings of server.log, logger.limit, and logger.count to
meet your specific requirements by adding these properties to the Essbase Studio
server.properties file. The properties are described in the Oracle Essbase Studio Online
Help.
The default server log file size is 10485760 bytes (10 MB).
c. To change the number of server log files that are stored as log history files, add a line
for the log count property, logger.count; for example:
logger.count=15
olapisvr.log Integration Server activity Rolling log file. No manual archive is needed.
Level Description
0 To log all debug messages and the ODBC SQL generated by Integration Server; generate dataloadrecord.txt, listing the first
1,000 records, which may include successfully loaded records and rejected records; and create hisdld.rul consisting of the
names of the dimensions loaded followed by the leaf node number of each dimension or member.
2 Log all informational messages and some of the ODBC SQL generated by Integration Server.
7 Log all critical errors where Integration Server terminates the command.
Essbase Logs 35
The recommended level setting is 2 or 3.
Windows: In startup.bat , to use the highest level of logging, add -L0 after C:/Hyperion/
AIS/bin/olapisvr.exe. For example:C:/Hyperion/AIS/bin/olapisvr.exe -L0.
Note: For a listing of EPM Workspace logs and Configuration and Monitoring Console (CMC)
logs, see “Foundation Services Logs” on page 18.
All log messages are routed through Logging Service and stored in one location. Logging Service
writes log messages to one or more files, which can be read using a viewer. Services, servlets,
process monitors, and Web services log messages centrally using the Logging Service. Log4j
(version 1.2) is used as the basis for the logging framework and configuration files.
For more information on Reporting and Analysis logs, see “Troubleshooting” in the Oracle
Enterprise Performance Management Workspace Administrator's Guide.
Note: CMC, Remote Service Configurator, and Calendar Manager log messages locally.
log4j.rootLogger=DEBUG,dest1
log4j.appender.dest1.MaxFileSize=1024KB
log4j.appender.dest1.MaxBackupIndex=20
Note: Valid logging levels in fr.properties are INFO, WARNING, ERROR, DEBUG.
report_name. Output from SHOW and DISPLAY commands when -O May contain report data. Choose to archive or
log command line flag. Can be redirected to any file. delete based on whether you want to keep
report data.
report_name. Error messages/warnings during compilation and program Contains errors pertaining to the specified
err execution when -E command line is used (can be redirected to report. Retain until errors are resolved.
any file).
sqr.log (Windows) Output from SHOW and DISPLAY commands and/or May contain report data. Choose to archive or
error messages/warnings during compilation and program delete based on whether you want to keep
execution when neither -E and -O command line flags are report data.
used.
HsvEventLog.log Financial Management activity (any errors with Financial Management server)
Planning Logs
The following sections contain information about Planning logs. For information about
Performance Management Architect and Calculation Manager logs, see “Foundation Services
Logs” on page 18.
Application Server logs Planning activity Oracle Application Server: ORACLE_HOME/opmn/logs/ Archive
OC4J~HyperionPlanning~default_island~1
WebSphere: HYPERION_HOME/deployments/
WebSphere6/profile/logs/HyperionPlanning
ä To set the logging level for the Planning application server logs:
1 Log in to a Planning application as the administrator or owner.
2 Select Administration and then Manage Properties.
3 Select the System tab.
4 Set DEBUG_ENABLED to true.
5 After changing log levels you must restart the Planning application server for the changes to take effect.
hbrclient.log Business Rules client For all application servers: HYPERION_HOME/ Archive
activity AnalyticAdministrationServices/console/bin
Note: If the Administration Services default port was changed , enter the port information
before the Administration Services server name as: port number name:port#.
3 In the left pane of Administration Services, expand Business Rules and then Administration.
4 Double-click Properties.
The properties of the Oracle's Hyperion® Business Rules client configuration are displayed.
5 To change the level of error reporting for the client on the Client Configuration tab, select a level from
Log Level:
l Severe
l Warning (default)
l Info
l Config
l All
6 To change the level of error reporting for the server on the Server Configuration tab, select one of the
error levels described in step 5 from the Log Level list.
7 Click Save.
8 After changing log levels you must restart the server for the log settings to take effect.
HPSWebReports.log Performance Scorecard application activity. Includes Lifecycle Archive for support call purposes
Management activity.
HPSAlerter.log Alerter Web application activity Archive for support call purposes
errors.log Performance Scorecard import or export errors Archive for support call purposes
For more information, see the Oracle Hyperion Performance Scorecard Administrator's Guide.
After changing log levels you must restart the server for the log settings to take effect.
hpm.log Log file for all Profitability and Archive log files deemed important according to your document storage and retention policy.
Cost Management messages. Should you decide to archive, please use MaxFileSize of 10 MB for rotation. No specific
frequency is needed, and it is enough to go with rotation based on size.
Modify log4j.properties to configure the log level settings for Oracle Hyperion Profitability
and Cost Management, Fusion Edition.
log4j.properties is in HYPERION_HOME/deployments/
app_server_name_and_version/profitability/WEB-INF/classes/
log4j.properties for all supported application servers.
After changing log levels you must restart the server for the log settings to take effect:
FDM Logs
The following sections contain information about Oracle Hyperion Financial Data Quality
Management, Fusion Edition logs.
tLogActivity table Information about FDM activities and audit related information. Archive. This log should be kept
as part of the financial audit
trail.
Windows Event Log Event log entries that are written by the Application Manager and
LoadBalance Manager
Note: FDM Task Manager can also log scheduled task events (when
logging is enabled) in the Windows Event Log.
Table 10 provides a list and description of the different log levels you can specify for ODI logs.
Level Description
0 Disable logging.
Each log level encompasses messages of the lower log levels; for example: level 2 will log error
as well as fatal messages. Similarly, Level 5 will include all messages.
Windows Application Event Information written by the Data Relationship Management Server. Standard IT practices should be
Log Includes Data Relationship Management events, server messages, followed in managing the
and errors. application event log.
Import Log Information about the Import operation Can be deleted when no longer
needed
Note: Optional log file that can be specified by the user.
Blender Log Information about the Blend operation Can be deleted when no longer
needed
Note: Optional log file that can be specified by the user.
MDM_Connect.log Data Relationship Management Batch Client information (user can Can be deleted when no longer
override the name and location) needed
Transaction History Transaction information written by the Data Relationship As Data Relationship Management
Management system and maintained in the Data Relationship versions are deleted, the
Management repository database corresponding transactional
history is also deleted.
Note: View Transaction History from the Data Relationship
Management client. From the Main menu, select Tools and then
Transaction History.
Note: You cannot change the level of detail recorded in logs other than the transaction
history. After changing log levels for the Transaction History you must restart the
Data Relationship Management Windows service.
Note: If the Loss Action is specified or if AllowAsOf is turned on, then Core Actions are
tracked, even if not set in the TransactionLevels System Preference.
Installation Troubleshooting
This section discusses issues that you might encounter when using the EPM System Installer.
Installation Troubleshooting 51
“New Installation” Option is Not Available
Issue: If the New Installation option is not available, your machine might have an improperly
deleted previous version of EPM System products.
Solution: Search for the vpd.properties file on the machine and rename it
vpd.properties.old.
If you previously installed Release 11.1.1.0, search for .hyperion.products and remove it.
<product>
<productName>hssWebApp</productName>
<directory>c:\Hyperion</directory>
<version>9.3.1.0.0</version>
</product>
</products>
52 General Tips
Product Valid Entries for Product
Essbase l essbaseAddins
l essbaseClient32
l essbaseClient64
l essbaseService32
l essbaseService64
Installation Troubleshooting 53
Product Valid Entries for Product
Planning l offlinePlanningClient
l planningWebApp32
Note: This applies to software that has 32–bit and 64–bit choices in the same platform.
54 General Tips
Product Is Not Available
Issue: A product can be unavailable on the Product Selection panel for any of these reasons:
l Partial installation of the product
l Assemblies not downloaded
l Assemblies were placed in the wrong location
l Assemblies were renamed
l Assembly not available for your platform
Solution: Make sure the assemblies are in the correct location. See “Preparing the Installation
Files” in the Oracle Hyperion Enterprise Performance Management System Installation and
Configuration Guide.
This can occur if you have already installed Essbase Server and other products and then attempt
to install another instance of Essbase Server and another product that you have already installed.
You can install another instance of Essbase Server but not the other product.
Solution: Deselect all products other than Essbase Server.
Installation Troubleshooting 55
l The JRE or Help folders are missing since the extraction was not successful. Try re-
extracting.
l Tmp is not defined on machine. Check your machine.
Solution: If no other error message is displayed on summary panel and the installation does not
resume within five minutes, stop the installation and run the createInventory script in
HYPERION_HOME/OPatch.
56 General Tips
HP-UX Issue
Issue: In an HP-UX environment, running epmsys_registry.sh without passing parameters
does not generate a registry.html file.
Solution: Edit the epmsys_registry.html file to replace CLASSPATH=$HYPERION_HOME/
common/config/9.5.0.0/lib/regedit.jar with CLASSPATH=$HYPERION_HOME/
common/config/9.5.0.0:$HYPERION_HOME/common/config/9.5.0.0/lib/
regedit.jar.
Upgrade Troubleshooting
This section discusses issues that you might encounter when upgrading EPM System products.
Configuration Tips
This section provides solutions to the most common configuration errors.
Upgrade Troubleshooting 57
Solution: Review the EPM System Configurator log in HYPERION_HOME/logs/config/
configtool_summary.log. As a troubleshooting measure, perform configuration tasks
individually for one product or component at a time.
Out-of-Memory Errors
Issue: You receive out-of-memory errors because an application is very large.
Solution: Allocate more memory by increasing the heap size for your application server. See
your application server documentation.
58 General Tips
l If you cannot find it in the list of active processes, you may need to start it.
l If listed, select Mem Usage. If it is using more than 500 MB, there may be a memory error
that requires you to restart the service.
This indicates that you may need to clean up semaphores. To confirm that semaphore cleanup
is needed, run > ipcs -s | grep $USER
Solution: Force semaphores cleanup by having the user who runs Apache Tomcat issue the
following command:
for i in `ipcs -s | grep $USER | cut '-d ' -f2 -s`; do ipcrm sem $i;
done
In This Chapter
Understanding How and What to Troubleshoot .........................................................61
Preliminary Tasks...........................................................................................62
Using the Shared Services Registry Editor ..............................................................62
EPM System Product Registration with Shared Services ...............................................63
User Directories and Provisioning ........................................................................64
OpenLDAP Issues ..........................................................................................66
Deployment to WebLogic..................................................................................67
Loss of Shared Services Response.......................................................................67
Startup and Access Issues ................................................................................67
Resolving Product-Specific Issues........................................................................70
You cannot User directories l Launch EPM System Diagnostics to ensure that the products' Web applications are started, as well
log in to and Shared as OpenLDAP
Shared Services Web
Ensure that CSSConfig contains up to date information on how to connect to user directories. If
Services application
l
CSSConfig cannot be exported using Oracle Hyperion Enterprise Performance Management
System Lifecycle Management in the Shared Services Console, use the Shared Services Registry
Editor.
You cannot User directories l Check Shared_Services_Security.log in the product server for errors
access other and products
Launch EPM System Diagnostics to ensure that the product Web application is started, as well as
registered Web
l
OpenLDAP.
EPM System applications
products
from Shared
Services
application
groups
Preliminary Tasks
Perform these initial tasks to better identify or resolve issues with Shared Services before
contacting Support:
l Perform the steps in Chapter 2, “Troubleshooting Basics .”
l Review the appropriate log file to better diagnose the problem. This could include enabling
debugging information.
l To validate basic user directory function, use the utilities provided with Shared Services.
If you cannot access the Shared Services Lifecycle Management user interface, use the Registry
Editor utility (epmsys_registry.bat or epmsys_registry.sh) to modify the Shared
Services Registry to change user directories information, or change your Shared Services server
or port. See the Oracle Hyperion Enterprise Performance Management System Installation and
Configuration Guide.
Caution! Because the Shared Services Registry is critical to running EPM System products, be
extremely careful if you edit the Shared Services Registry. Oracle recommends
backing up the registry before editing it. See the Oracle Hyperion Enterprise
Performance Management System Backup and Recovery Guide.
Note: This example assumes that you saved the updated css config file in c:/temp as
myCSSConfig
cd /d %HYPERION_HOME%/common/config/9.5.0.0 %HYPERION_HOME%/common/config/9.5.0.0/
epmsys_registry.bat updatefile SYSTEM9/FOUNDATION_SERVICES_PRODUCT/
SHARED_SERVICES_PRODUCT/@CSSConfig c:/temp/myCSSConfig
To assure that the OpenLDAP process is started when failover to the standby server occurs,
Oracle also recommends that you run the Native Directory OpenLDAP process on the same
machine as the primary Shared Services Web application.
Common Problems
These are the most common problems users encounter using Shared Services with external user
directories:
l Changes to user IDs and passwords in user directories are not updated in CSSConfig
l The host name, port, or domain controller is not specified correctly in CSSConfig.
ä To increase performance:
1 Always set a group URL.
2 Use native groups, not external groups, to provision external users. To use native groups for user
provisioning, or if you do not use external groups, set the Group URL to LostAndFound as follows:
l MSAD: <url>cn=LostAndFound</url>
l LDAP: To any DN node
3 Always define a User URL and set it as deep as possible.
4 Use the default logging level of WARN. Change the level to <DEBUG> only for debugging purposes.
5 For multiple groups and users, set the Java Heap Size in all products to 1 GB.
See the Oracle Hyperion Enterprise Performance Management System Security Administration
Guide
Note: If you upgraded from a previous release, the Shared Services port is 58080.
Deployment to WebLogic 67
Improving Log In Time
On the server, review SharedServices_Security.log.
If it contains errors relating to group caching, ensure that the group URL and filter are set
properly to accommodate group counts.
Note: If you are upgrading from a previous release, the port for the Shared Services server
is 58080.
3 When prompted, enter the Shared Services user ID and password (by default, admin and password).
4 Locate .instance by selecting File and then Open and browsing to: Content on files
\Products\HAVA-9.5.0\Published. Ensure you select Show All Files in Order to list all of the
files that you may need.
5 Right-click the file and select Context and then Attributes.
6 Change the server name to reference the Web server.
7 Specify 80 as the IIS port.
8 Click Modify and Save
9 Restart Shared Services.
Oracle Essbase
This section provides solutions to questions you may have using Essbase products with Shared
Services.
Essbase
This section provides solutions to common problems users have using Essbase with Shared
Services.
Resolving an Analytic Services CSS Initialization Fails with a “CSS not initialized” Error
If you receive this error, stop and restart Essbase Service. If the problem still occurs, perform
these tasks:
l Ensure that the entries in essbase.cfg are correct
l Ensure that you can access CSSConfig from Shared Services
Financial Management
This section provides solutions to errors you may encounter configuring and using Shared
Services with Financial Management.
Resolving an Internet Explorer Script Error to View User Security From the User Management
Console
If you receive the following error, set the timeout period for the script:
A script on this page is causing Internet Explorer to run slowly. If it
continues to run, your computer may become unresponsive. Do you want to
abort the script?
See http://support.microsoft.com/kb/175500.
Performance Scorecard
This section provides solutions to errors you may encounter configuring and using Performance
Scorecard with Shared Services.
Java.lang.NoSuchMethod Error
You receive this error if you install multiple products with Performance Scorecard and Shared
Services but configure Performance Scorecard first. To resolve this issue, uninstall Performance
Scorecard, reinstall and configure the other products, and then install and configure Oracle
Hyperion Performance Scorecard, Fusion Edition.
In This Chapter
Tips and Recommendations ..............................................................................75
Connection Failure .........................................................................................75
Tomcat Startup Fails and EPM Workspace is Unavailable .............................................76
Logon Failure ...............................................................................................76
Startup Order ...............................................................................................76
Logging On When the EPM Workspace Agent is Down .................................................77
Cannot Access Configuration Management Console ...................................................77
Failure to Access Modules ................................................................................77
where hostname is the name of the Reporting and Analysis server, and port is the TCP port
on which the Web server is listening. See “Ports” in the Oracle Hyperion Enterprise
Performance Management System Installation Start Here.
l When you install EPM Workspace in a distributed environment, you must run the EPM
System Configurator on every computer, ensuring that you are using the correct computer
names.
l Check the logs for information on startup failures. See Chapter 3, “Using EPM System Logs.”
l Restart EPM Workspace and Shared Services after any change to Shared Services registration
information.
Connection Failure
Issue: Failure to connect to servers in a distributed environment.
Solution: Be sure that you run the EPM System Configurator on all the machines in the
environment, using the correct machine names. If you point to a machine using an incorrect
name, you cannot connect to that server.
Logon Failure
Issue: The user cannot log on to EPM Workspace, and the following error message is displayed:
You must supply a valid User Name and Password to log onto the system.
Startup Order
Issue: Products that are offline when EPM Workspace starts may not have full menus available.
Solution: Start the offline products, and restart EPM Workspace to obtain full availability of the
applications.
EPM Workspace caches product information at startup time; it reads from the Oracle's Hyperion
Shared Services Registry to determine which products are configured. This information is
refreshed only with a restart.
In This Chapter
Essbase .....................................................................................................79
Administration Services ...................................................................................81
Integration Services........................................................................................81
Essbase Studio.............................................................................................82
Provider Services...........................................................................................82
Essbase
The following sections identify common Essbase installation and configuration issues.
JVMMODULELOCATION has not been correctly set Set the environment variable. See the Oracle Hyperion Enterprise Performance
in essbase.cfg. You can modify this setting from Management System Installation and Configuration Guide.
the Administration Services console.
Essbase 79
Error Message or Issue Solution
Essbase does not start. Attempt to start Essbase from a command line if it will not start from the Start menu.
More error messages are displayed when Essbase is started from a command line,
enabling you to troubleshoot. For example, messages about missing or inaccessible
files may be displayed.
Connection Problems
Issue: You cannot establish an Essbase client-server connection.
Solution: Use the PING command on the server to check that the server is running and visible
to the client computer.
l If the PING command is successful but the TELNET command is not, there might be a
problem with the inet daemon.
l If the PING command is unsuccessful on the server, you might have a routing or hardware
problem.
Startup Problem
Issue: Essbase startup is prevented because the default Essbase port is taken by other services.
Solution: Preset a Windows registry key, HKEY_LOCAL_MACHINE\SYSTEM
\CurrentControlSet\Services\Tcpip\Parameters, on the computer where Essbase
runs.
Administration Services
The following sections describe common Administration Services issues.
Integration Services
This section describes common Integration Services issues and solutions.
Administration Services 81
m The data source database listener for OLAP Metadata Catalog and the data source
l Ensure that the OLAP Metadata Catalog and the data source are configured as ODBC data
sources on the Integration Server computer.
Essbase Studio
Issue: Difficulty starting Oracle Essbase Studio using Oracle or SQL 2005, verify these items:
Solution: Verify these items:
l The information in the server.properties file is correct. The server.properties file
is in HYPERION_HOME/products/Essbase/EssbaseStudio/Server. For information
about the settings, see the Oracle Essbase Studio User's Guide.
l The user name that you used for connection to Studio Catalog has the correct privileges to
work with Studio Catalog. The user should be a database owner.
l These required components are running:
m Oracle Essbase Studio Server
m The database servers that manage Studio Catalog
Provider Services
This section describes common Provider Services issues and solutions.
In This Chapter
Common Planning Issues .................................................................................83
Common Financial Management Issues .................................................................85
Common Performance Management Architect Issues ..................................................90
Planning Access
This section discusses access issues you might encounter with Planning.
Upgrade Issues
This section discusses upgrade issues you might encounter with Planning.
Software Compatibility
Issue: You must ensure that the new release of Planning is compatible with the release of Shared
Services that you are using.
Solution: To check compatibility, see the “Release Compatibility” chapter of Hyperion
Installation Start Here.
Issue: You receive an SSL error message when using Planning 9.3.1 with Shared Services.
Solution: Upgrade the version of Shared Services to 9.3.x.
Folder Structure
The location of files is as follows:
l All .jar files are in the lib, not Utils folder
l All .exe, .bat, .sh, and .cmd files are in the bin folder instead of Utils
l Offline.exe and SmartView.exe are in HYPERION_HOME\products\Planning\bin
\SmartView, not the Deployment folder.
Note: You can install Oracle Hyperion Smart View for Office, Fusion Edition from EPM
Workspace by selecting Tools, then Install, then Smart View, or you can use the EPM
System Installer.
Performance Issues
Issue: You are using an Oracle database and experience performances issues with Cube Refresh.
Solution: Ensure that CURSOR_SHARING in Oracle is set to EXACT. This is the default setting.
Issue: You are experiencing performance issues with Oracle Hyperion Planning, Fusion Edition.
Solution: Tune the Web server or increase heap size, depending on your environment. Hyperion
recommends that you work with a consultant to assess your environment.
Multibyte Characters
Issue: Multibyte characters do not show up in reports.
Solution: Ensure that Unicode or Albany fonts are present in the Java Runtime Environment
used by your J2EE container or application server. If they are not, copy them from the fonts
folder that has the Albany fonts laid out by Oracle Hyperion Enterprise Performance
Management System Installer, Fusion Edition to the fonts folder of the Java Runtime
Environment used by your J2EE container or application server. Examples of fonts folder
locations:
l WebLogic: BEA_Home\jrockit_150_12\jre\lib\fonts
l Apache Tomcat: HYPERION_HOME\common\JRE\Sun\1.5.0.\lib\fonts
l WebSphere: WebSphere_Home\AppServer\java\jre\lib\fonts
http:// EPM l EPM Workspace Web server is running on the specified port.
webserver:webport/ Workspace EPM Workspace Web application is running.
workspace/ splash screen
l
is displayed, l Web server configuration files point to correct host name and port for the
and a new EPM Workspace Web application server.
browser
window opens
with the logon
page.
For detailed instructions on configuring the Web server, see the Oracle Hyperion Enterprise
Performance Management System Manual Deployment Guide.
2. If step 1 does not work, verify that you have configured the EPM Workspace proxy server
plug-in. If it is configured, test whether you can access Financial Management directly.
Connection Troubleshooting
These are some common connection issues for Financial Management.
Solution: A problem may exist with the Microsoft SQL Server connection and the .UDL file. See
“Verifying Data Link Connection Settings” on page 89.
Issue: You are having difficulty connecting to SQL Server.
Possible Solutions:
l Windows authentication may have been used instead of Microsoft SQL Server
authentication. EPM System recommends using SQL Server authentication. See “Verifying
Microsoft SQL Server Authentication Settings” on page 89.
l The system may be using the Microsoft SQL Server default setting to connect to the database
using named pipes instead of TCP/IP. Connection through TCP/IP is required. See
“Establishing the SQL Server Connection Using TCP/IP” on page 88.
The return code is always the same; only the application server name changes.
Solution: This issue occurs when the signed-on token is no longer valid. Try these steps to resolve
it:
l Add this registry setting to each Web Server and Financial Management Win32 client
machine:
HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial
Management\Client\Clusters\machine name
l Verify any specific DCOM issues by setting up the appropriate logging. HKLM\Microsoft
\Ole\CallFailureLoggingLevel and ActivationFailureLoggingLevel are
enabled on all servers, and the login audit policy is set to both Success and Failure.
Installation Failure
Issue: Performance Management Architect Installation failed.
Solution: This could be the result of a Microsoft .NET Framework 2.0 error during its automatic
installation in Performance Management Architect. Install Microsoft .NET Framework 2.0
manually, and then rerun the installation.
Issue: You receive an ASP.NET error during configuration.
Solution: Ensure that ASP.NET is installed and configured. See the Oracle Hyperion Enterprise
Performance Management System Installation and Configuration Guide.
Note: This issue and solution also pertain to Hyperion Calculation Manager.
This error may occur when you attempt to access the Dimension Library. It may also occur or
if you click OK after attempting to access http://server:288/awb and receiving this error
message: Module not found:awb.appcontainer
This issue can occur because the Dimension Server is not running. It can also result from a
missing user privilege in an Oracle database.
Solutions: .
l If the Dimension Server is not running, start the Process Manager Service, which starts
Dimension Server and related services, and then retry the connection.
l Assign the CREATE VIEW user privilege for the Oracle database. See “Using an Oracle
Database” in Oracle Hyperion Enterprise Performance Management System Installation Start
Here.
If a Sessions page is displayed, then IIS is correctly configured. If there is any error in IIS,
check the Event Log to identify the problems. Check the System and Application Log to see
if anything was logged by ASP.NET, IIS, or DCOM, and fix the errors. A possible cause is
incorrect privileges for the user for the TEMP directory.
l Check the Event Logs from sources starting with HyS9EPMA. Possible causes are
communication errors with Shared Services or the database.
l The ASPNET user may not have access to certain folders. If the Event Log displays any
security-related errors, assign rights to the ASPNET user.
1. From the command prompt, go to this directory: C:\Windows\Microsoft.NET
\Framework\v2.0.50727.
2. Enter run aspnet_regiis.exe-ga.
In This Chapter
Common FDM Issues ......................................................................................97
Common Data Relationship Management Issues.......................................................99
Solution: Update the machine profile in the Workbench to point to the Financial Management
cluster that is registered on the FDM application servers. In the profile the setting for the target
system server or cluster must exactly match what you set up for Oracle Hyperion Financial
Management, Fusion Edition, or they cannot communicate with each other.
Solution: Correct outstanding Oracle issues, and ensure that you can resolve the Oracle Service
Name in tnsnames.ora.
Access is Denied
Issue: In the Event Log, you receive the “Access Is Denied” error message.
Solution: Check if the user has the proper rights. The domain, user name and password entered
on the Windows COM+ Logon dialog box must be entered correctly.
Configuration Issue
Issue: Receive error message — “Cannot configure the system. Please check the configuration”
Solution: Ensure the hostname field on the Common Security Services page of the Hyperion
Data Relationship Management console contains the correct name of the server where CSS is
running.
Index
A logs, 28
about troubleshooting, 9 multibyte characters in reports, 85
access cannot authenticate user, Financial Data
Architect, 91 Management, 98
Architect Dimension Server WebServices, 94 cannot connect to Oracle database, Financial Data
denied, Data Relationship Management, 99 Management, 97
Financial Management applications, 86 cannot perform bulk insert, Financial Data
Planning, 83, 84 Management, 98
Planning from Workspace, 83 common issues
products from Shared Services, 68 Architect, 90
Reporting and Analysis modules, 77 Data Relationship Management, 99
Apache logs, 18 Financial Data Management, 97
Shared Services Registry API logs, 22 Financial Management, 85
application server Planning, 83
logs, 17 user directories and Shared Services, 64
startup failure, Shared Services, 67 common log location, 15
application server deployment configtool.log, 13
failure without configuration errors, 58 configtool_err.log, 13
Architect configuration
accessing Dimension library or Application library, Data Relationship Management, 99
93 error log, 13
accessing server Webservices, 94 exceptions, logged, 13
displaying Dimensions Library, 93 Financial Data Management, 97
displaying tasks, 92 general tips, 57
errors on server, 94 validation, 12
IIS startup on Architect Dimension Server, 94 Configuration and Monitoring Console logs, 26
installation failure, 90 connection failure
logon, 91 Essbase client-server, 80
services startup failure, 94 Financial Management, 87
auditing general, resolving, 58
loss of response, 67 OLAP Metadata Catalog or external data source,
81, 88
Reporting and Analysis, 75
B corruption, OpenLDAP, 66
Business Rules logs, 44
CSSConfig, 64
C
Calculation Manager
Index 101
A B C D E F H I J K L M O P R S T U V W Z
D filters, assigning, 81
Data Relationship Management logs, 32
access denied, 99 refreshing security to Shared Services, 71
common issues, 99 troubleshooting, 81
configuration issues, 99 use with Planning, 85
invalid classpath root, 100 with Shared Services, 71
logs, 47, 49 Essbase Integration Services
readme issues, 99 logs, 35
server startup failure, 100 OLAP or data source connection failure, 81
unable to create JVM, 100 Essbase logs, 30
user rights issues on client machine, 99 Essbase Provider Services
DB2, use with Performance Management Architect, load balancing with WebLogic and Apache, 82
95 out-of-memory errors, 82
deployment external user directories, 64
failure without configuration errors, 58
out of memory error, 58
documentation, 10
F
failure
accessing Financial Management from Workspace,
E 86
EPM auditing Apache Tomcat, startup, 59
loss of response, 67 application server deployment, 58
EPM System Configurator Architect Dimensions Library, displaying, 93
logs, 17 Architect Services, 94
EPM System product registration, with Shared Architect tasks, displaying, 92
Services, 63 connection to OLAP Metadata Catalog or data
EPM Workspace source, 81
logs, analyzing, 26 Data Relationship Management server startup,
logs, configuring, 25 100
ERPi Essbase server, 79
logs, 48 IIS startup on Architect Dimension Server, 94
error messages login, Financial Management, 86
application server deployment login, Workspace, 92
out of memory, 58 OpenLDAP, startup, 66
Essbase, 70 Planning, accessing directly, 84
Essbase Administration Services, 71 Planning, accessing from Workspace, 83
Financial Data Management, 97 Process Manager Service, starting, 92
Financial Management, 72 Reporting and Analysis modules, accessing, 77
JVM on UNIX, 59 Reporting and Analysis, connection in distributed
Performance Scorecard, 73 environment, 75
Provider Services, out-of-memory, 82 Shared Services service or process startup, 67
Essbase Shared Services startup, application server, 67
logs, 30 Financial Data Management
server startup failure, 79 cannot perform bulk insert, 98
server-client connection, 80 common issues, 97
troubleshooting, 79 configuration issues, 97
use with Shared Services, 70 logs, 47
Essbase Administration Services Oracle/Client provider connection, 97
102 Index
A B C D E F H I J K L M O P R S T U V W Z
user authentication, 98 J
Financial Management JVM error, UNIX, 59
access from Workspace, 86
accessing, 86
common issues, 85
K
knowledge base, My Oracle Support (MetaLink 3),
connection failure, 87
13
error messages, 72
installation failure, 87
large data or file loads, 89 L
logon failure, 86 Lifecycle Management
logs, 43 loss of response, 67
rights for installation, 89 login
SQL Server connection failure, 88 Architect, 91
use with Shared Services, troubleshooting, 72 Financial Management, 86
Financial Performance Management applications Shared Services, improving performance, 64
Architect, accessing Dimension library or Workspace, 92
Application library, 93 logs
common Architect issues, 90 EPM System Configurator, 17, 18, 28
common Financial Management issues, 85 Apache, 18
DB2 performance settings, 95 application server, 17
establishing the SQL Server connection using TCP/ Business Rules, 44
IP, 88 common location, 15
performance issues, 85 configuration, 13
Planning with Administration Services, 85 Configuration and Monitoring Console, 26
Planning, access issues, 83 Data Relationship Management, 47, 49
troubleshooting connection issues, 87 ERPi, 48
upgrade issues, 84 Essbase, 30
Financial Performance Management Applications Essbase Administration Services, 32
logs, 43 Essbase Integration Services, 35
Financial Reporting file size, 15
logs, 40 Financial Data Management, 47
Financial Management, 43
Financial Performance Management Applications,
H 43
HP-UX issue, 57
Financial Reporting, 40
installation, 16
I Oracle Application Server, 18
installation overview, 13
Architect, failure, 90 Performance Management Architect, 27
Financial Management, failure, 87 Performance Scorecard, 46
logs, 16 Planning, 43
rights for Financial Management, 89 Production Reporting, 41
validation, 12 Profitability and Cost Management, 46
installation documentation, 10 Provider Services, 36
Installation Start Here, 11 Reporting and Analysis, 37
invalid classpath root, Data Relationship Shared Services, 18
Management, 100 Smart View, 26
Index 103
A B C D E F H I J K L M O P R S T U V W Z
104 Index
A B C D E F H I J K L M O P R S T U V W Z
U
unable to create JVM, Data Relationship
Management, 100
Index 105
A B C D E F H I J K L M O P R S T U V W Z
106 Index