Epm Install Troubleshooting

ORACLE® HYPERION ENTERPRISE PERFORMANCE
MANAGEMENT SYSTEM
RELEASE 11.1.1.3
INSTALLATION AND CONFIGURATION

TROUBLESHOOTING GUIDE
EPM System Installation and Configuration Troubleshooting Guide, 11.1.1.3
Copyright © 2007, 2009, Oracle and/or its affiliates. All rights reserved.
Authors: EPM Information Development Team
This software and related documentation are provided under a license agreement containing restrictions on use and
disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or
allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit,
perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation
of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to
change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S.
Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS:
Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers
are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition
Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and
adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to
the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial
Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or
intended for use in any inherently dangerous applications, including applications which may create a risk of personal
injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe,
backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates
disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their
respective owners.
This software and documentation may provide access to or information on content, products, and services from third
parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with
respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any
loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Contents
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About Troubleshooting EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Assumed Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installation Documentation Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 2. Troubleshooting Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Meeting System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Reviewing the Installation Start Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Checking Release Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Avoiding Port Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Reviewing Startup Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
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
Chapter 3. Using EPM System Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

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
Application Server Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Web Server Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Foundation Services Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Shared Services Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
EPM Workspace Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Configuration and Monitoring Console Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Smart View Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
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
Chapter 4. General Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Installation Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
WebLogic Server Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
WebSphere Upgrade Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Installation Type Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Product Selection Panel Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
EPM System Installer Fails to Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Installation Wizard Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Welcome Panel Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Cannot Install After an Uninstall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
HP-UX Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Upgrade Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
EPM System Products and WebLogic Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Upgrades with WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Configuration Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Changing Java Heap Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
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
Chapter 5. Troubleshooting Shared Services and Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Understanding How and What to Troubleshoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Preliminary Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Using the Shared Services Registry Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Generating a Report of the Contents of the Shared Services Registry . . . . . . . . . . . . . . 62
Editing the Shared Services Registry to Change User Directories Information, Shared
Services Server or Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
EPM System Product Registration with Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . 63
User Directories and Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Provisioning Basics and Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Common Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
OpenLDAP Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Working with OpenLDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Resolving OpenLDAP Provider Startup Failure Due to Corruption . . . . . . . . . . . . . . 66
Fixing OpenLDAP Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Deployment to WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Loss of Shared Services Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Startup and Access Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Resolving Shared Services Service or Process Startup Failure . . . . . . . . . . . . . . . . . . . 67
Resolving a Shared Services Startup Failure on the Application Server . . . . . . . . . . . . 67
Improving Log In Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Resolving Problems Accessing Products from Shared Services . . . . . . . . . . . . . . . . . . 68
Reconfiguring Product Registration in Shared Services to Use a Web Server . . . . . . . . 69
Reregistering a Product with Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Reconfiguring the Shared Services Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Resolving Product-Specific Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Oracle Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Financial Performance Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
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
Chapter 7. Troubleshooting Essbase Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Essbase Server Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Connection Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Startup Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Installation on Different UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Problems Assigning Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Integration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Connection Failure to OLAP Metadata Catalog or External Data Source . . . . . . . . . . . 81
Essbase Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Provider Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Out of Memory Errors With Concurrent Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Load Balancing Problems with WebLogic through Apache . . . . . . . . . . . . . . . . . . . . 82
Chapter 8. Troubleshooting Financial Performance Management Applications . . . . . . . . . . . . . . . . . . . . . . . . 83

Common Planning Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Planning Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Upgrade Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Using Planning with Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Performance Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Multibyte Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Common Financial Management Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Accessing Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Connection Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Rights Required for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Large Data or File Loads Fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Sticky Server Attempts to Redirect User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Common Performance Management Architect Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Installation Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
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
Chapter 9. Troubleshooting Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Common FDM Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Configuration Issues with Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Oracle Client / Provider Cannot Connect to Database . . . . . . . . . . . . . . . . . . . . . . . 97
Database User ID or Password Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Cannot Authenticate User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Cannot Perform Bulk Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Active-X Component Cannot Create Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Common Data Relationship Management Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Reviewing Readme Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Open File Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Access is Denied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Server Unable to Process Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Configuration Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Unable to Create JVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Invalid Classpath Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Server Startup Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Error Message During Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Contents vii
viii Contents
Introduction
1
In This Chapter
About Troubleshooting EPM System Products............................................................ 9
Assumed Knowledge........................................................................................ 9
Installation Documentation Roadmap ...................................................................10
Check the Oracle Documentation Library (http://www.oracle.com/technology/documentation/

epm.html) on Oracle® Technology Network to see whether an updated version of this guide is
available.
About Troubleshooting EPM System Products

This guide provides troubleshooting tips for installing and configuring Oracle Hyperion
Enterprise Performance Management System products. It contains general information about
how to approach troubleshooting, important documentation to review, and how to use logs.
Also provided are solutions to difficulties that you may encounter using Oracle's Hyperion®
Shared Services to provision and share users among EPM System product applications and
solutions to difficulties using Oracle Enterprise Performance Management Workspace, Fusion
Edition and Oracle's Hyperion Reporting and Analysis.
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
About Troubleshooting EPM System Products 9

Installation Documentation Roadmap
You can find EPM System installation documentation on the Oracle Documentation Library
(http://www.oracle.com/technology/documentation/epm.html) on Oracle® Technology
Network.
Table 1 lists the documents to consult for instructions on performing essential installation tasks.
Table 1 Documentation That You Need
Task Related Documentation
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.
Table 2 Documentation That You Might Need
Task Related Documentation
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
Perform these tasks before contacting Support for assistance.
Meeting System Requirements

Before installing EPM System products, ensure that your environment meets those requirements
specified in the Oracle Hyperion Enterprise Performance Management System Certification
Matrix. You can find the matrix at http://www.oracle.com/technology/products/bi/hyperion-
supported-platforms.html.
Reviewing the Installation Start Here

Oracle Hyperion Enterprise Performance Management System Installation Start Here contains
release compatibility, prerequisites, default ports, and other information needed to plan a
successful installation.
Checking Release Compatibility

If you are upgrading from a previous release, it is important to check whether the software
versions of EPM System products in your environment are compatible. See the Oracle Hyperion
Enterprise Performance Management System Installation Start Here.
Meeting System Requirements 11

Avoiding Port Conflicts
During EPM System product configuration, default port numbers for Web applications are
populated automatically. You can change the defaults during configuration, but each port
number must be unique. To avoid error messages such as “port already in use” or “bind error,”
review the list of default product port numbers in the Oracle Hyperion Enterprise Performance
Management System Installation Start Here.
Reviewing Startup Dependencies

Ensure that you have reviewed the startup dependencies for EPM System products in the Oracle
Hyperion Enterprise Performance Management System Installation and Configuration Guide.
Although services are started automatically in a Windows environment, you may have occasion
to start services manually. This chapter also provides default product URLs. Before you start
services or processes, start all databases used as repositories.
Before starting a service or process, ensure that the preceding service or process started
successfully. Some services or processes take longer than others to initialize, and startup times
may vary by computer.
Reviewing the Readme

The Oracle Hyperion Enterprise Performance Management System Installation and Configuration
Readme contains known installation or configuration issues for all EPM System products. It is
very important to review this readme for late-breaking information that may affect your
deployment.
In addition, each EPM System product includes a Readme document for each release. These
readmes contains other known issues and late-breaking information for the products.
Using the Installation Guide

The Oracle Hyperion Enterprise Performance Management System Installation and Configuration
Guide provides step-by-step installation and configuration procedures for all EPM System
products. Very often you can find the answer to an installation or configuration issue by using
the installation guide to verify that you have correctly completed all required steps. The guide
covers both fresh installations and upgrades from earlier releases.
Validating the Installation and Configuration

After installing and configuring a product, perform these tasks to validate the deployment.
l Use Oracle's Hyperion Enterprise Performance Management System Diagnostics to test the
status of installed and configured EPM System components, diagnose problems, and assist
in problem resolution. Run EPM System Diagnostics on each machine in the deployment.
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 My Oracle Support (MetaLink 3)

If you have a current support agreement and a customer support identifier, you can search the
My Oracle Support knowledge base (MetaLink 3) for information about resolving installation
and configuration issues. You can also use My Oracle Support for entering service requests,
downloading software releases and patches, and other online support tasks.
Oracle recommends that you adjust the default sources for your knowledge base searches, if
necessary, to include documentation for your Hyperion products.
For more information, click the Getting Started link on the My Oracle Support home page.
Accessing Technical Support Resources

To help you effectively operate, manage, and run EPM System performance management
solutions by delivering technical expertise whenever you need it, Oracle Support Services is
available at http://www.oracle.com/support/index.html.
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
Common Log File Location

Log files for most EPM System products are created in HYPERION_HOME/logs/product. For
example, Shared Services logs are created in HYPERION_HOME/logs/SharedServices9.
Note: The log locations listed in this chapter are the default locations.
Logs for these products are not created in HYPERION_HOME/logs:

l Oracle Hyperion Planning, Fusion Edition
l Oracle's Hyperion® Business Rules
l Oracle Hyperion Data Relationship Management, Fusion Edition
Note: Some products may write log files to both common and other folders, as indicated in this
chapter.
Log File Size and System Performance

Logs are installed with the recommended default log levels.
Common Log File Location 15

Verbose logging levels increase file size and can reduce overall system performance.
Consequently, Oracle recommends that you use the least verbose logging level required. Revert
to the original log levels after troubleshooting is complete to avoid using too much disk space
and negatively affecting performance.
Suggestions in this chapter regarding log retention and rotation are not intended as strict
guidelines.
What To Do Before Contacting Technical Support

Before contacting Technical Support, run EPM System Diagnostics. EPM System Diagnostics
generates a ZIP file of all EPM System logs (the equivalent of zipping up the HYPERION_HOME/
logs directory structure). The ZIP file is created in the HYPERION_HOME/logszip directory.
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=
to DEBUG; for example:

log4j.rootLogger=DEBUG, ToolMain
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.
Table 3 Installation Log Files
Name Contents Location Rotation
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.
product-install.log Indicates whether a product HYPERION_HOME/ Do not delete this log.

assembly installation fails. logs/install
For example, hss-install. Provide this log to Technical Support when
There is a log file for each
log for Shared Services reporting any issue with configuring EPM
assembly.
System products.
16 Using EPM System Logs

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
EPM System ConfiguratorLogs

You can specify the logging level for EPM System Configurator by editing the
log4j.properties file in HYPERION_HOME/common/config/version_number.
Set the log4j.rootLogger= property to DEBUG. Example:

log4j.rootLogger=DEBUG,out,error
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
configtool.log Configuration task HYPERION_HOME/ Do not delete this log.

output and warning logs/config
Provide this log to Technical Support when reporting
messages
any issue with configuring EPM System products.
configtool_err. Configuration errors HYPERION_HOME/ Do not delete this log.

log logs/config
configtool_ Summary information HYPERION_HOME/ Do not delete this log.

summary.log about passed and failed logs/config
tasks
Application Server and Web Server Logs

You can also troubleshoot by reviewing logs written by application servers and Web servers used
with EPM System products. See the vendor documentation for information about other logs
specific to the application server or Web server.
Application Server Logs

Every EPM System application that is auto-deployed to an application server using EPM System
Configurator generates logs for that application server.
EPM System ConfiguratorLogs 17

For each EPM System application service, error and console logs are written to
HYPERION_HOME/logs/service. For all products and all application servers, except for Oracle
Application server, there is one log file for each product service.
Table 5 Application Server Log Files
Application Server EPM System Log Location
Oracle Application Server 10g HYPERION_HOME/deployments/Oracle10g/product/application-deployments/

product/product_default_group_1/application.log
Oracle WebLogic Server 9 HYPERION_HOME/deployments/WebLogic9/servers/product/logs/
IBM WebSphere 6 HYPERION_HOME/deployments/Websphere6/profile/logs
Embedded Java Container HYPERION_HOME/logs/Tomcat
Web Server Logs

The default log location for the Embedded Web Server (Apache) is:
HYPERION_HOME/logs/apache
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/.
Foundation Services Logs

l “Shared Services Logs” on page 18
l “EPM Workspace Logs” on page 22
l “Smart View Logs” on page 26
l “Configuration and Monitoring Console Logs” on page 26
l “Performance Management Architect Logs” on page 27
l “Calculation Manager Logs” on page 28
Shared Services Logs

This section contains information about Shared Services log files.
Log File Names and Descriptions
Name Contents Rotation*
registry.log Shared Services Registry activity. See “Shared Services Registry API Archive
Log” on page 22.

SharedServices_Security.log External authentication and single sign-on activity Archive
SharedServices_Security_Upgrade.log Migration-related activity, if applicable Archive
SharedServices_Admin.log User management activity Archive
SharedServices_Audit.log Audit server errors while reading/writing audit information to the Archive
database or while configuring auditing
SharedServices_Hub.log Shared Services context listener activity Archive
SharedServices_LCM.log Lifecycle management activity Archive
SharedServices_Metadata.log Information about metadata management and registration Archive
SharedServices_Taskflow.log Information about taskflow Archive
SharedServices_Taskflow_CMDExecute.log Scheduling information Archive
SharedServices_Taskflow_Optimize.log Scheduling information Archive
SharedServices_SyncOpenLDAP.log Information that synchronizes OpenLDAP and relational data Archive

sources
SharedServices_Security_Client.log Information about the external authentication client Archive

Note: In previous releases, HyperionCSS.log
SharedServices_Memory_Profiler.log Memory consumption information Archive
openldap.log OpenLDAP activity Archive
*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.
Setting Log Levels

You can specify the kinds of messages that are written to the logs, such as DEBUG, ERROR, or
WARN.
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.
Foundation Services Logs 19

Setting Message Levels to Debug Shared Services
ä 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.
Log Levels for the OpenLDAP Directory

By default, OpenLDAP is used as the Shared Services Native Directory for provisioning data.
On Windows, the EPM System Configurator configures the OpenLDAP server daemon (slapd)
as a service. Log level settings for OpenLDAP are passed as startup parameters to slapd. Log level
verbosity can be increased by editing the registry key for the service.
On UNIX/Linux, slapd is invoked with HYPERION_HOME/products/Foundation/
openLDAP/startOpenLDAP.sh. You can increase log level verbosity by editing
startOpenLDAP.sh. Table 6 lists the parameters that can be passed to slapd.
Table 6 OpenLDAP Startup Commands
OpenLDAP Startup Command Log Details Description
slapd -d -1 Enable all debugging Logs all OpenLDAP transactions and queries.
slapd -d 0 No debugging Provides no logs.
slapd -d 1 Trace Traces OpenLDAP function calls.
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 2048 Print entry parsing debugging Provides schema-level detail.

OpenLDAP Startup Command Log Details Description
slapd -d 4096 Database cache processing Displays cache processing data such as index parameters.
slapd -d 8192 Database indexing Provides database index details.
slapd -d 16384 Syncrepl consumer processing Displays replica processing operations (master-slave OpenLDAP
configuration).
Changing the Default Location of the Shared Services Security Log
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.
J2EE Web applications

> To change the default location for all J2EE Web applications, use one of the following means
to pass the Java system property, -Djava.io.tmpdir=LOG_PATH, to the JVM that is used by
the application server instance:
l Update the EPM System product startup file or script (.bat on Windows and .sh on UNIX)
l Use the application server’s Administration console
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
ä To pass the Java system property on Windows:

1 Stop Oracle Essbase server.
2 Set the Windows system environment variable:
ESS_CSS_JVM_OPTION3 to -Djava.io.tmpdir=LOG_PATH
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.
For example, ESS_CSS_JVM_OPTION3=-Djava.io.tmpdir=LOG_PATH.

3 Start Essbase server.

UNIX
ä To pass the Java system property on UNIX:

1 Stop Essbase Server.
2 Update the hyperionenv.doc file by adding the following property:
ESS_CSS_JVM_OPTION3=-Djava.io.tmpdir=LOG_PATH.
3 Start Essbase Server.
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.
Shared Services Registry API Log

The Oracle's Hyperion Shared Services Registry API log file, registry.log, records and
archives activity for the Shared Services Registry (the database used to store and reuse
configuration information for most Shared Services Registry products). You can specify the
logging level for Shared Services Registry by editing the RegistryLogger.properties file
in:HYPERION_HOME/common/config/version_number/resources/registry.
Edit the following property to specify the logging level:
log4j.logger.com.hyperion.hit.registry=DEBUG, REGISTRY_LOG_FILE
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.
EPM Workspace Logs

Table 7 lists EPM Workspace log files with descriptions of their contents and recommendations
for rotating the files.

Table 7 EPM Workspace Log Files
stdout_console_agent_configuration_name. The stdout_console.log is generated regardless

log of the operation being performed, and represents
standard output and standard errors (console output).
For example, stdout_console_default.log
Use this log to diagnose Core Services startup failures.
Some errors captured by the application are logged
here.
server_messages_BrowseServlet.log Log for EPM Workspace browsing servlet component,

which browses the repository
server_messages_AdministrationServlet. Log for EPM Workspace administration servlet

log component, which administers the Reporting and
Analysis system
server_messages_PersonalPagesServlet.log Log for EPM Workspace personal pages servlet

component (bookmarks and personal pages
administration)
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.log Impact Management Update Service (Transformer)

information
server_messages_JobManagerServlet.log Log for EPM Workspace JobManager servlet
server_messages_AnalyticBridgeService. Log for the Analytic Bridge Service (bridges data to

log Oracle's Hyperion® Interactive Reporting from other
EPM System products)
server_messages_AuthenticationService. Authentication Service information (user credentials

log and group membership at login)
server_messages_AuthorizationService.log Authorization Service information (roles and their

associations with operations, users, groups, and other
roles)
server_messages_CommonServices.log Entries for the Reporting and Analysis logging service

before it is operational
server_messages_DataAccessService.log Data Access Service information
server_messages_EventService.log Event Service information (system resource and job

management)
server_messages_GSM.log Global Service Manager information (system

configuration and service monitoring)

server_messages_HarvesterService.log Impact Management Assessment Services (Harvester) Archive every 12

information (published Interactive Reporting repository hours. Contains
document metadata) valuable auditing
and debugging
data.
server_messages_JobService.log Job Service information (Reporting and Analysis job

management)
server_messages_LoggingService.log Log4j Service initialization information
server_messages_LSM.log Log for the Local Service Manager (LSM) service; LSMs
provide support for Interactive Reporting distributed
services infrastructure.
server_messages_PublisherService.log Publisher Service information (repository

communication for other LSC services and some Web
application requests)
server_messages_RepositoryService.log Repository Service information (Reporting and Analysis

data storage repository)
server_messages_SessionManager.log Session Manager Service information (simultaneous

users and session timeout management)
server_messages_ServiceBroker.log Service Broker information (GSM and LSM client

request routing and RSCload balancing)
server_messages_TransformerService.log Impact Management Update Service (Transformer) Archive every 12

information (Interactive Reporting document updates) hours. Contains
valuable auditing
and debugging
data.
server_messages_UsageService.log Usage Service information (Interactive Reporting usage

statistics (such as the most used files, the most
selected MIME types)
admin_messages_CalendarManager.log Calendar Manager information (for job scheduling)
admin_messages.log Administration Utilities information
license_message_agent_configuration_ Contains licensing information

name.log
For example, license_message_default.log
SharedServices_Security_Client.log Shared Services authentication information
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.

server_messages_SearchKeywordProvider. Search Keyword Provider Service (registered parsers, Archive every 12

log parsing documents for keywords prior to indexing) hours. Contains
valuable auditing
and debugging
data.
server_messages_SearchMonitor.log Search Monitoring Service (monitors Repository and Archive every 12

triggers (re)indexing on document changes) hours. Contains
valuable auditing
and debugging
data.
eiengine.log† Lifecycle Management activity Archive
*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.
Setting Log Levels

Log levels specify the amount and type of information written to logs. The default logging level,
which is set on root, is WARN. Consequently, messages at that level or lower (ERROR, FATAL)
appear in the log. You can change this for the entire system, or just a service or servlet. See
“Configuring Log Properties for Troubleshooting” in the Oracle Enterprise Performance
Management Workspace Administrator's Guide.
After changing log levels you do not need to restart the service, but a refresh of the log
configuration in the Configuration and Monitoring Console (CMC) is needed for the changes
to take effect.
Configuring Log Properties for Troubleshooting

To troubleshoot EPM Workspace, you can configure these logging properties:
l Logging levels
l Loggers
l Appenders
l Log rotation
Logging levels for Service Configurator are configured using Service Configurator. All other
configuration changes are made in Configuration and Monitoring Console (CMC). See
Management Workspace Administrator's Guide for information on setting EPM Workspace log
levels.

Analyzing EPM Workspace Log Files
For information on how to view EPM Workspace log files, log files that are always generated,
and log files to look at for troubleshooting, see Analyzing Log Files in the “Troubleshooting”
chapter of the Oracle Enterprise Performance Management Workspace Administrator's Guide.
Configuration and Monitoring Console Logs

The following sections contain information on Configuration and Monitoring Console (CMC)
logs. See also the logs for Reporting and Analysis in “Reporting and Analysis Logs” on page
37.

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
Setting Log Levels

You can specify the types of messages that are written to the logs, such as ALL, ALWAYS, DEBUG,
INFO, WARN, FATAL, or OFF.
ä To set log levels:

1 Start CMC and select a view.
2 Right-click and select Properties.
3 Set the Log Level property under the General tab and click OK.
4 If you change log configuration values or add custom log configurations, refresh the log configurations
(right-click and select Refresh Log Configurations) to apply the changes to the service. You do not need
to restart the service for the changes to take effect.
Smart View Logs

The SmartViewLogs.log file contains Oracle Hyperion Smart View for Office, Fusion Edition
error messages. Archiving is recommended for the SmartViewLogs.log file.

Setting Log Levels and Routing Messages to a Log File
All error, warning, and informational messages from the connected data source are displayed
when they occur, but you can choose which messages to record in SmartViewLogs.log.
ä 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.
Performance Management Architect Logs

The following table lists Oracle Hyperion EPM Architect, Fusion Edition logs with their contents
and rotation recommendations.
Table 8 Performance Management Architect Log Files
Name Contents Rotation
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.
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.

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
Setting Logging Levels
ä To change the logging level for Performance Management Architect:

1 In HYPERION_HOME/deployments/AppServAndVersion/EPMAWebServer/webapps/
awb/WEB-INF/conf, open AWBLog4j.properties.
2 Modify this line:
log4j.logger.com.hyperion.awb=ERROR,logfile, stdout
to
log4j.logger.com.hyperion.awb=DEBUG ,logfile, stdout
ä To change the logging level for the Windows event log:

1 In HYPERION_HOME/products/foundation/bpma/appserver/dimensionserver/
serverengine/bin, open bpma_server_config.xml
2 In appender name="EventLogAppender"
type="log4net.Appender.EventLogAppender,log4net" param
name="Threshold" value="INFO"/, change “INFO” to “ERROR”.
Note: The DEBUG setting is not recommended here.

3 After changing log levels you must restart the server for the log settings to take effect.
Calculation Manager Logs

The following sections contain information about Hyperion Calculation Manager logs.

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
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
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.
properties file.
ä To change the logging level for calcmgrserver.log:

1 Open the CalcMgrlog4j.properties file under calcmgr/WEB-INF/conf.
2 Set the desired value for the following properties:
log4j.logger.com.hyperion.awb=Value (for example,
log4j.logger.com.hyperion.awb=WARN)
log4j.logger.com.hyperion.calcmgr=Value (for example,

log4j.logger.com.hyperion.calcmgr=WARN)
log4j.logger.com.hyperion.calcmgr.common.GenericLogger=Value (for
example, log4j.logger.com.hyperion.calcmgr.common.GenericLogger=INFO)
3 Save the file.

4 After changing the Calculation Manager log levels, you must restart the Planning application server for
Calculation Manager logs on Planning side.
Setting Logging Levels for Calculation Manager

To change the logging level for the other three Calculation Manager logs, modify logging levels
and log4j settings in the log4j.properties and CalcMgrLog4j.properties files in
DEPLOYMENT_LOCATION/calcmgr/WEB-INF/classes.
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.
Essbase.log Essbase Server activities and errors HYPERION_HOME/logs/ Archive

essbase/app
(You must create a new log
file when you archive the
old one.)
application_name. Essbase application activities and errors HYPERION_HOME/logs/ Archive

log essbase/app
file when you archive the
old one.)
dataload.err Data load and dimension build errors HYPERION_HOME/logs/ Keep these logs for
essbase/app support calls.

dbname.atx, dbname. Successfully completed spreadsheet update HYPERION_HOME/logs/ Archive

alg transactions essbase/app
These are SSAUDIT log files; File name and file when you archive the
location are specified through an old one.)
essbase.cfg configuration setting. See
“Monitoring Data, Applications, and
Databases” in theOracle Essbase Database
Administrator's Guide and the Essbase
Technical Reference.
Note: SSAUDIT log files are created only
if SSAUDIT is activated in essbase.cfg.
log0000x.xcp Information captured at the time of an HYPERION_HOME/logs/ Keep these logs for
abnormal termination essbase/app support calls.*
EssbasePlugin.log Log statements related to artifact listing HYPERION_HOME/logs/ Archive

essbase/lcm
EssbasePlugin.log Log statements corresponding to artifact HYPERION_HOMEcommon/ Archive

migration utilities/ LCM/9.5.0.
0/logs
*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.
Log Location for Additional Instances of Essbase

If more than one instance of Essbase is installed on a machine, the log location is appended by
InstanceID. For example, if you have a second instance of Essbase installed, and the instance
ID is 2, the logs for that instance are located in HYPERION_HOME/logs/essbase_2/app. To
determine the InstanceID, check the essbase.cfg file, located in HYPERION_HOME/
products/Essbase/EssbaseServer/bin.
Setting Essbase Log Levels

By default, application_name.log and Essbase.log record this information:
l Information messages
l Warning messages
l Error messages
Use essbase.cfg settings to specify the messages types written to application_name.log
and Essbase.log.
See “Monitoring Data, Applications, and Databases” in the Oracle Essbase Database
Administrator's Guide and the Essbase Technical Reference for information about
essbase.cfg settings.
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.
Administration Services Logs

The following sections contain information about Oracle Essbase Administration Services logs.
easserver.log Administration Services Server activity Archive
eas-install.log Administration Services installation information Archive
Setting Log Levels

The log level can be specified using the application server admin console by setting the –
DEAS_LOG_LEVEL=value Java argument for the Server Start configuration for the managed
server; for example, –DEAS_LOG_LEVEL=4000.
After changing log levels you must restart the Administration Services server for the log settings
to take effect.
Logging level values:
l 0 – None (No logging)
l 1000 – Critical (Only critical messages will be logged, mostly exceptions)
l 2000 – Error (Only error and critical messages will be logged)
l 3000 – Warning (Only warning error messages will be logged)
l 4000 – Exception
l 5000 – Info
l 6000 – Trace
l 7000 - XML Trace
l 9999 – Everything (All)

Essbase Studio Logs
The following sections contain information on Oracle Essbase Studio logs.
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.
Setting Log Levels

The log level specifies the level of information written to the server log file.
ä To change the log level of the esbstudioserver.log file:

1 Use a text editor to open the server.properties file, located in the server directory of your
Essbase Studio installation.
2 Add a line for the logging level property, com.hyperion.cp.level; for example:
com.hyperion.cp.level=FINEST
The default level is INFO.

Available logging levels are:
l SEVERE—The highest level. Includes messages that indicate serious failures.
l WARNING—Includes messages that indicate potential problems.
l INFO—Includes information messages. This is the default.
l CONFIG—Includes static configuration messages.
l FINE—Includes tracing information.
l FINER—Includes fairly detailed tracing messages.
l FINEST—The lowest level. Includes highly detailed tracing messages.
l OFF—Turns off logging.
l ALL—Enables logging of all messages.
3 Save and close server.properties.
4 After changing log levels you must restart the Essbase Studio server for the log settings to take effect.
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.
ä To change the settings for rotating log history files:

1 Use a text editor to open the server.properties file, located in the server directory of your
Essbase Studio installation.
2 Change one or more of the following properties, according to your requirements:
a. To specify a new name for the log file, add a line for the log file property,
logger.file; for example:
logger.file=myserver.log
The default log file name is esbstudioserver.log.

b. To change the maximum size of the server log files (in bytes), add a line for the log limit
property, logger.limit; for example:
logger.limit=5242880
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

The default number of server log files that are kept as log history files is 10.
3 Save and close server.properties.
Integration Services Logs

The following sections contain information on Oracle Essbase Integration Services logs.
olapisvr.log Integration Server activity Rolling log file. No manual archive is needed.
Setting Log Levels

You can set the log level in Integration Services by using the -L startup switch.
You can set minimum and maximum size of log files. Then the log size would fluctuate between
these sizes.
For information about Integration Services startup switches, see the Oracle Essbase Integration
Services System Administrator's Guide.
ä To set the level of message in Integration Services logs:

l On Windows, add -Llevel to startup.bat.
l On UNIX, enter -Llevel when you start Integration Server.
l On any platform, add -Llevel to ais.cfg.
The default level is 2. You can specify these levels:
Table 9 provides a list and description of the different log levels you can specify.
Table 9 Possible Log Levels
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.
3 Log all warnings.
4 Log all noncritical errors.
7 Log all critical errors where Integration Server terminates the command.
8 Log all critical server errors.
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.
Any platform: In ais.cfg, this switch is specified as [L]=0.

After changing log levels you must restart the Integration Services server for the log settings to
take effect.
Provider Services Logs

The following sections contain information about Oracle Hyperion Provider Services logs.
apsserver.log Provider Services activity Rolling log file. No manual

archive is needed.
The log file location is configurable using the property name system.
log.file.name in APS_HOME/bin/essbase.properties.
server1.log Provider Services Web Archive

application activity
aps-install.log Installation information Archive
Setting Log Levels

You can dynamically change the level of Provider Services logging. For example, if you switch
provider logging level from Information to Warning, the change takes effect immediately on
Provider Services.
ä To specify log message levels and enable XML tracing:

1 In Administration Services Console, under the Provider Services node, select the provider node.
2 Right-click and select Edit and then Properties.
3 In Provider Services properties, select Logging.
4 Under Logging, select Enable Provider Logging to send messages to a log file, and specify the log file
path.
5 Under Minimum Log Level, select a log level:
l Warning— Displays warning, error, and fatal messages
l Information— Displays information, warning, error, and fatal messages.
l Debug— Displays debug, information, warning, error, and fatal messages.
6 Select Display messages on Provider console to send messages to the Provider Services start up message
console window.

7 Under Tracing, select Enable Provider logging to enable tracing of XML request responses between the
client and Provider Services.
8 Click Apply.
9 Click Close.
10 After changing log levels you do not need to restart the Provider Services server for the log level changes
to take effect.
Reporting and Analysis Logs

The following sections contain information about Reporting and Analysis logs. The logs for
Reporting and Analysis components are listed by component in the tables in this section. See
“Log File Names and Descriptions” on page 38.
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.
Configuring Log Properties for Troubleshooting

To troubleshoot Reporting and Analysis, you can configure these logging properties:
l Logging levels
l Loggers
l Appenders
l Log rotation
Logging levels for Service Configurator are configured using Service Configurator. All other
configuration changes are made in Configuration and Monitoring Console (CMC). See
Management Workspace Administrator's Guide for information on configuring Reporting and
Analysis log levels.
Reporting and Analysis Logs 37

Note: Common service startup messages are logged to stdout_console_default.log and
configuration_messages.log. Refer to those log files when diagnosing startup
failures.
Setting Log Levels

Log levels specify the amount and type of information written to logs. The default logging level,
which is set on root, is WARN. Consequently messages at that level or lower (ERROR, FATAL)
appear in the log. You can change this for the entire system, or just a service or servlet. See
Management Workspace Administrator's Guide.
Configuring Log Rotation

You can roll and delete log files by time intervals or file size. By default, the system rolls logs
every 12 hours and deletes the oldest log file when the number of logs exceeds five. For more
information on configuring log rotation, see “Configuring Log Rotation” in the Oracle Enterprise
Performance Management Workspace Administrator's Guide.
Analyzing Reporting and Analysis Log Files

For information on how to view Reporting and Analysis log files, log files that are always
generated, and log files to look at for troubleshooting, see Analyzing Log Files in the
“Troubleshooting” chapter of the Oracle Enterprise Performance Management Workspace
Administrator's Guide.

l “Annotation Service Logs” on page 38
l “Interactive Reporting Logs” on page 38
l “Financial Reporting Logs” on page 40
l “Production Reporting Logs” on page 41
l “Web Analysis Logs” on page 41
Annotation Service Logs
Annotations.log Annotation manager information
Interactive Reporting Logs

Interactive Reporting Log Service

server_messages_IRServiceHelper.log Interactive Reporting logging service

information
0_default_irlog_UUID_backupMessagesip-address-port.log Logging message when the logging service is

unavailable
0_default_irlog_UUID_stdout.log Standard output of irlog service including list

of loaded classes
0_default_irlog_UUID_stderr.log Standard error of irlog service
Interactive Reporting Intelligence Service
PID_BIStartUp.log BIService startup information

BIStartUp.log
server_messages_IntelligenceService.log Interactive Reporting Service, helpful in troubleshooting problems

with the Interactive Reporting thin client
UUID_BIService.log BIService information
0_default_irbi_UUID_stdout.log Standard output of irbi service including list of loaded classes
0_default_irbi_UUID_stderr.log Standard error of irbi service
Interactive Reporting Job Service
PID_IRJobStartUp.log IR job service startup information
0_default_irjob_UUID_stdout.log Standard output of irjob service including list of loaded classes
0_default_irjob_UUID_stderr.log Standard error of irjob service
server_messages_IRJobService.log Interactive Reporting Job Service, helpful in troubleshooting problems with

the Interactive Reporting jobs
UUID_IRJob.log IR job service information
Interactive Reporting Data Access Service
PID_DASStartUp.log DAS startup information
server_messages_DataAccessService.log Data Access Service information
0_default_irdas_UUID_stdout.log Standard output of irdas service including list of loaded classes

0_default_irdas_UUID_stderr.log Standard error of irdas service
UUID_das.log DAS service information
Financial Reporting Logs

The following sections contain information about Oracle Hyperion Financial Reporting, Fusion
Edition logs.
FRCommSrv.log Financial Reporting Communication Server HYPERION_HOME/logs/ Automatic

information BIPlus/
FRReportSrv.log Activity from the Financial Reporting server, HYPERION_HOME/logs/

where reports are rendered BIPlus/
FRSchedSrv.log Batch scheduler activity HYPERION_HOME/logs/

BIPlus/
FRScheduleBatch.log Activity from the Scheduler command line HYPERION_HOME/logs/

interface BIPlus/
FRWebApp.log Activity from the Financial Reporting Web HYPERION_HOME/logs/

Application, where Web client pages are BIPlus/
generated
FRPrintSrv.log(Windows only) Financial Reporting printing information HYPERION_HOME/logs/

BIPlus/
FRUserLogin.log User login information HYPERION_HOME/logs/

BIPlus/

To set debug level logging for Financial Reporting components, specify these settings in
fr.properties in HYPERION_HOME/products/biplus/lib:
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.

After changing log levels you do not need to restart the Financial Reporting components. The
system updates every 60 seconds.
Component Properties File Log File
All Components fr_global.properties FRCommSrv.log
Report Client fr_client.properties FRClient.log
Report Server fr_repserver.properties FRReportSrv.log
Print Server fr_printserver.properties FRPrintSrv.log
Scheduler Server fr_scheduler.properties FRSchedSrv.log
Web Application fr_webapp.properties FRWebApp.log
Production Reporting Logs

The following sections contain information about Oracle's Hyperion® SQR® Production
Reporting logs.
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.

You cannot set logging levels for Production Reporting.
Web Analysis Logs

The following sections contain information on Oracle's Hyperion® Web Analysis logs.

WebAnalysis_log.date.txt Tomcat log for Web Analysis HYPERION_HOME/deployments/Tomcat5/

(for exceptions only) WebAnalysis/logs/
SystemOut.log SystemErr.log WebSphere 6 Web Analysis HYPERION_HOME/deployments/

startServer.log logs WebSphere6/profile/logs/WebAnalysis/
WebAnalysis.log WebLogic Server 9 log for Web HYPERION_HOME/deployments/WebLogic9/

Analysis servers/WebAnalysis/logs/
server_messages_WebAnalyzer.log Web Analysis Web application HYPERION_HOME/logs/BIPlus/

log
Setting Log Levels
ä To set log levels in server_messages_WebAnalysis.log:

1 Openlogging-settings.jar in DEPLOYMENT_LOCATION/WEB-INF/lib, where
DEPLOYMENT_LOCATION is:
l Oracle Application Server 10–HYPERION_HOME/deployments/Oracle10g/
WebAnalysis/applications/WebAnalysis/WebAnalysis
l WebLogic Server 9–HYPERION_HOME/deployments/WebLogic9/servers/
WebAnalysis/webapps/WebAnalysis
l WebSphere 6– HYPERION_HOME/deployments/WebSphere6/profile/
installedApps/hyslCell/WebAnalysis.ear/WebAnalysis.war
l Embedded Java container (Tomcat)-HYPERION_HOME/deployments/Tomcat5/
WebAnalysis/webapps/WebAnalysis
2 Open serviceLog4Config.xml.
3 Modify the file using these settings:
l All
l Debug
l Info
l Warn
l Error
l Fatal
l Off

Financial Performance Management Applications Logs
The following sections contain information about Financial Performance Management
Applications logs.
l “Financial Management Logs” on page 43
l “Planning Logs” on page 43
l “Business Rules Logs” on page 44
l “Performance Scorecard Logs” on page 46
l “Profitability and Cost Management Logs” on page 46
Financial Management Logs

The following sections contain information about Financial Management logs. For information
about Performance Management Architect and Calculation Manager logs, see “Foundation
Services Logs” on page 18.

HsvEventLog.log Financial Management activity (any errors with Financial Management server)
HFMLCMService.log Lifecycle Management activity
Setting Log Levels

You cannot set log levels for Financial Management.
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.
Financial Performance Management Applications Logs 43

Application Server logs Planning activity Oracle Application Server: ORACLE_HOME/opmn/logs/ Archive
OC4J~HyperionPlanning~default_island~1
Oracle WebLogic Server: HYPERION_HOME/deployments/

WebLogic9/servers/HyperionPlanning/logs
WebSphere: HYPERION_HOME/deployments/
WebSphere6/profile/logs/HyperionPlanning
Embedded Java Container (Tomcat): HYPERION_HOME/

deployments/Tomcat5/HyperionPlanning/logs
UserProvisionSync. Security refresh HYPERION_HOME/logs/Planning Can be

log information, such as deleted
provisioning or “user not
found” issues. Facilitates
troubleshooting of
synchronization issues
between Planning and
Shared Services.
Setting Logging Levels for Planning
ä 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.
Business Rules Logs

The following sections contain information about Business Rules log files.
Log Files Names and Descriptions

hbrclient.log Business Rules client For all application servers: HYPERION_HOME/ Archive
activity AnalyticAdministrationServices/console/bin

hbrserver.log Records general From Administration Services, written to: Archive

information and errors on
HYPERION_HOME/logs/eas
the Business Rules
server. From Planning, written to the location from which the Planning server is
started.
hbrlaunch.log Includes information From Administration Services, written to: Archive

regarding business rule
HYPERION_HOME/logs/eas
names and RTP values for
launched rules. From Planning, written to the location from which the Planning server is
started.

By default, Business Rules records warning level messages in log.txt, but you can change the
level of messages that are recorded.
ä To change the message level in log.txt:

1 Launch the Administration Services Console by selecting Start , then Programs, then Hyperion, then
Administration Services, and then Start Administration Services Console.
2 In Administration Services Login , enter the Administration Services server name and your logon
credentials. Click OK.
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.
Financial Performance Management Applications Logs 45

Performance Scorecard Logs
The following sections contain information about Oracle Hyperion Performance Scorecard,
Fusion Edition logs.

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
failedrecords.log Performance Scorecard import or export errors Can be deleted
successfulRecords.log Performance Scorecard import or export records Can be deleted

Performance Scorecard uses log4j for logging. You can modify logging levels and log4j settings
for HPSWebReports.log in HPSConfig.properties and AlerterConfig.properties.
These files are in:
<HYPERION_HOME>/deployments/APP_SERVER_NAME_AND_VERSION/webappsconf/
config/.
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.
Profitability and Cost Management Logs

The following sections contain information about Oracle Hyperion Profitability and Cost
Management, Fusion Edition logs.
Log Files Names and Descriptions

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.

Setting Log Levels
You can specify the kinds of messages that are written to the logs, such as DEBUG, ERROR, or
WARN.
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:
Data Management Logs

The following sections contain information on Data Management logs.
l “FDM Logs” on page 47
l “ERP Integrator Logs” on page 48
l “Data Relationship Management Logs” on page 49
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.
l tBatch Batch processing, informational, and error log entries Archive

l tBatchContents
l tBatchInformation
username.err Information about FDM user errors. Can be deleted

Note: The main purpose of these logs is to assist in debugging customer
issues.
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.
Data Management Logs 47

Authentication.err Information about FDM Failed authentication attempts Can be deleted.

Suggested at 5 MB.

You cannot set logging levels for FDM.
ERP Integrator Logs

The following sections contain information about Oracle Hyperion Financial Data Quality
Management ERP Integration Adapter for Oracle Applications logs.
HyS9aifWeb-sysout.log Information necessary for support and Development to triage issues.
HyS9aifWeb-syserr.log Information about ERP Integrator system errors.
Table 10 provides a list and description of the different log levels you can specify for ODI logs.
Table 10 Possible Log Levels
Level Description
0 Disable logging.
1 Log fatal messages.
2 Log error messages.
3 Log all warnings.
4 Log information messages.
5 Log debug messages.
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.

Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle
Applications uses Oracle Data Integrator (ODI). For the ODI processes, the log folder is set by
the property file. The log file is aif_<PROCESS_ID>.log.

Note: PROCESS_ID is shown on the UI when applicable.
ä To set the logging levels within ODI:

1 In ODI, open ODI System Registration.
2 For Log Level, specify a value between 0 to 5.
Data Relationship Management Logs

The following sections contain information about Data Relationship Management logs.

Database installation logs; Installation information Archive

for example:
Note: One of these log files is generated during Data Relationship
l oracle_install. Management server installation, depending on the type of Data
log Relationship Management database being used.
l mssql_install.log
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.

You must have administrator privileges to set Data Relationship Management Transaction
History logging levels. Set the TransactionLevel system preference to specify the action types to
capture in the transaction history.
Data Management Logs 49

ä To set Transaction History logging levels:
1 In the Data Relationship Management client, select Main, then Admin, and then System Preferences.
2 In Transaction Level, select a transaction level type:
l Logged Action records basic logging information, such as users logging in and logging
out.
l Core Action records actions that change the version, hierarchy, or node information,
such as Add Node, Change Property, or Move Node.
l Result Action records actions that result from core actions. For example, if the clear all
below core action is performed, then properties are cleared from individual nodes. The
clearing of properties from the individual nodes is a result action.
l Loss Action records loss of data due to a core action. For example, when a node is deleted,
all of the defined properties for that node are deleted, which is a loss action. Loss actions
are controlled by the LossLevel system preference.
3 Set additional system preferences:
l LossLevel indicates what to track for lost information. Its values are Defined and All.
When set to Defined only values that are specifically set at the node are tracked when
the node is deleted. When set to All, derived, default, inherited values are also tracked
in the LossAction.
l AllowAsOf forces tracking of Core Actions.
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.

General Tips
4
In This Chapter
Installation Troubleshooting...............................................................................51
Upgrade Troubleshooting..................................................................................57
Configuration Tips..........................................................................................57
Resolving Connection Failures and Restarting Services ................................................58
SSL Communication Issue ................................................................................59
UNIX Specific Tips..........................................................................................59
Installation Troubleshooting
This section discusses issues that you might encounter when using the EPM System Installer.
WebLogic Server Upgrades

Before installing EPM System products, if you are upgrading from Oracle WebLogic Server 9.1
to WebLogic Server 9.2.x, you must follow the BEA procedure to migrate application
environments, as described at http://edocs.bea.com/common/docs92/upgrade/
upgrading9091.html. Perform this procedure on the domain in the HYPERION_HOME/
deployments/WebLogic9 directory.
WebSphere Upgrade Requirement

If you use WebSphere and you are applying a maintenance release to go from EPM System
11.1.1.x to the current release, or you are upgrading from EPM System Release 9.3.1 to the current
release, you must also upgrade WebSphere from version 6.1.0.x to 6.1.0.17.
Installation Type Panel

You might encounter the following issues on the Installation Type panel.
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.
“Upgrade from a previous release” Option Is Not Available

Issue: If the Upgrade from a previous release option is not available on a machine that has a
previous release of a product installed, there may be a missing or corrupted vpd.properties
file.
Solution: Create an override file named upgradeproducts.xml and place it in the
HYPERION_HOME folder and then try installing again.
An example of the file structure using Shared Services is shown:
<products>
<product>
<productName>hssWebApp</productName>
<directory>c:\Hyperion</directory>
<version>9.3.1.0.0</version>
</product>
</products>
The valid entries for version are:

l 9.3.1.0.0
l 9.3.0.1.0
l 9.2.1.0.0
l 9.2.0.3.0
Table 11 lists the valid entries for product that can be used in creating an upgrade.xml.
Table 11 Valid Product Values Used in Upgrade.xml
Product Valid Entries for Product
Shared Services hssWebApp
EPM Workspace l workspaceWebApp

l workspaceService
Smart View l smartViewClient

l smartViewHveClient
52 General Tips
Performance Management Architect l epmaClient1

l epmaGenerator
l BPMAWebApp
l epmaDataSync
l epmaServices
Essbase l essbaseAddins
l essbaseClient32
l essbaseClient64
l essbaseService32
l essbaseService64
Administration Services l essbaseAdministrationConsole

l essbaseWebApp32
l essbaseWebApp64
Integration Services l essbaseIntegrationServiceClient32

l essbaseIntegrationServiceServer32
l essbaseIntegrationServiceServer64
Provider Services l essbaseWebApp232

l essbaseWebApp264
Oracle Hyperion Smart Search Command Line Utility essbaseWebApp3
Oracle's Hyperion® Interactive Reporting l irService

l imService
l irClient
l irClientDDS
Oracle's Hyperion® SQR® Production Reporting l prClientDeveloper

l prClientActivator
l prClientRemote
l prClientViewer
l prServiceDB2
l prServiceDDO
l prServiceInformix
l prServiceODBC
l prServiceOracle
l prServiceSybase
l prServiceTeradata
Financial Reporting l frClient

l frWebApp
l fr.server.reports
l fr.server.print
l fr.server.scheduler
Web Analysis waWebApp
Planning l offlinePlanningClient
l planningWebApp32
Financial Management l hfmClientMostAll

l hfmClientSamples
l hfmAdmClient
l hfmWebapp
l hfmWebAppSview
l hfmService
Performance Scorecard l hpsWebAppReports

l hpsWebAppAlerter
l hpsWebAppETL
Reinstall Option is Not Available

Issue: The Reinstall option is not available.
Solution: You must have the same version of software installed in order to perform a reinstall.
Or, choose a different option on the Installation Type panel.
Note: This applies to software that has 32–bit and 64–bit choices in the same platform.
Apply Maintenance Release Option is Not Available

Issue: The Apply Maintenance Release option is not available.
Solution: This option can only be used to move from Release 11.1.1.0 or 11.1.1.1 to 11.1.1.2.
You can choose a different option on the Installation Type panel.
Product Selection Panel Troubleshooting

You might encounter the following issues on the Product Selection panel.
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.
Incorrect Existing Version is Displayed

Issue: If you selected “Upgrade From a Previous Release,” you might see an incorrect existing
version displayed next to a product. This happens if EPM System Configurator cannot determine
the version number.
Solution: Disregard the version number and continue the upgrade.
Product Selection Combination Invalid

Issue: This error message is displayed:
The product selection combination is not valid because not all products you selected can
have multiple instances installed. Essbase Server is the only product for which you can
install multiple instances. Deselect one of the components.
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.
EPM System Installer Fails to Start

Issue: The command prompt window flashes by and the installer doesn’t start. An error is logged
in the log file.
Solution: Conditions that can cause the failure:
l Downloading the assembly did not work properly causing the assembly folder to have a 0-
byte dat file or no dat file. Try downloading again or checking that there are no spaces in
the path to the installer.
l Installer doesn’t recognize the assembly folder if it was renamed or if it didn't extract
properly. Check the name and try re-extracting.
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.
Installation Wizard Failure

Issue: When the installation is nearly complete, the installation wizard stops, and this error
message is displayed: Could not utilize start class
com.installshield.wizard.Wizard.
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.
Welcome Panel Issue

Issue:: Warning message about unsupported platform, not enough memory, or resolving host
name is displayed. The EPM System Installer checks whether your system has a supported
operating system, meets minimum memory requirements to run the installation and attempts
to discover the computer host name.
Solution:: If you receive a memory warning or unsupported platform, be aware that your
installation could have problems. If the machine host name resolves to an IP address, you receive
a warning. Oracle recommends that you resolve the DNS lookup issue before proceeding. If you
do not, rebooting the machine can cause your machine to resolve the host to a different IP
address, probably breaking your installation that was working before.
Cannot Install After an Uninstall

Issue: You experience problems installing after uninstalling.
Solution: To clean up your machine, try these steps:
1. Stop all services.
2. Uninstall from the Windows Add and Remove Programs option.
3. Delete all “hyperion” environment variables, including HYPERION_HOME.
4. Delete the entries from registry.
5. In C:\Documents and Settings\install_user\, delete the .oracle.products and
set_hyphome_1.bat files.
6. Rename program files\common files\installshield\universal\common as
program files\common files\installshield\universal\common_hyperion.
7. Restart the system.
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.
EPM System Products and WebLogic Upgrades

Before upgrading EPM System products, if you are upgrading from Oracle WebLogic Server 9.1
to WebLogic Server 9.2.x, you must follow the BEA procedure to migrate application
environments, as described at http://edocs.bea.com/common/docs92/upgrade/
upgrading9091.html. Perform this procedure on the domain in the HYPERION_HOME/
deployments/WebLogic9 directory.
Upgrades with WebSphere

If you use WebSphere and you are applying a maintenance release to go from EPM System
11.1.1.x to the current release, or you are upgrading from EPM System Release 9.3.1 to the current
release, you must also upgrade WebSphere from version 6.1.0.x to 6.1.0.17.
Configuration Tips
This section provides solutions to the most common configuration errors.
Changing Java Heap Sizes

You can change Java heap sizes when using services to start and stop Web application servers in
Windows environments. You can make the changes in batch files or in the Windows registry.
After making the changes for a product, you must restart of the Web application server.
Errors During Configuration

Issue: You fail to configure, or receive errors during configuration.
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.
Error on Configuration Task Panel

Issue: You cannot see a component or products displayed on the Configuration Task Panel. This
can happen if there was an incomplete installation.
Solution: Review the installTool-install.log and product-install.log to see if any
component was not completely installed.
Database Configuration Unavailable

If the options in the Database Configuration dialog box are unavailable, make sure that you are
configuring the system with the same user account that was used for the installation.
Failure Deploying to Application Server Without

Configuration Errors
Issue: A product is not deployed to the application server, but there are no configuration errors.
Solution: Review configtool.log. This file records any errors in the deployment process. If
no errors are identified, redeploy to the application server.
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.
Resolving Connection Failures and Restarting Services

To restart services, see the “Starting and Stopping EPM System Products” chapter in the Oracle
You can verify that the service is running by using Windows Task Manager.
ä To verify the service in Windows Task Manager:

1 Press Ctrl+Shift+Esc.
2 In Windows Security window, click Task Manager.
3 In Windows Task Manager, select Processes.
4 Locate the name of the executable for that product.
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.
SSL Communication Issue

Issue: You are having difficulty using SSL.
Solution: You must run the keytool and import the certificate in every JRE used by our software.
For more details, see the Oracle Hyperion Enterprise Performance Management System SSL
UNIX Specific Tips

This section provides solutions to installation and configuration errors that UNIX users may
encounter.
Apache Tomcat Startup Failure

Issue: Apache Tomcat does not start and may be accompanied by this error:
[crit] (28)No space left on device: mod_rewrite: could not create
rewrite_log_lock Configuration Failed
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
Preparing JVM...Error Writing to This File Error

Issue: Preparing Java Virtual Machine... Error writing file
This indicates insufficient temporary disk space.
Solution: Delete temporary files in /var/tmp and /tmp. If you have root privileges to the
computer and can safely remove other unused temporary files, do so.
SSL Communication Issue 59

60 General Tips
Troubleshooting Shared
5 Services and Provisioning
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
Understanding How and What to Troubleshoot

Table 12 indicates what components of Shared Services to troubleshoot based on the problems
you encounter performing tasks.
Table 12 Diagnostic Tasks for Shared Services
Problem Troubleshoot Basic Tasks
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
Understanding How and What to Troubleshoot 61

Problem Troubleshoot Basic Tasks
OpenLDAP OpenLDAP l In a shell,

service or
cd /d %HYPERION_HOME%\products\Foundation\openLDAP\var
process will
\openldap-data
not start
%HYPERION_HOME%\products\Foundation\openLDAP\bdb\bin\db_
recover —c
l Check for a file named alock in the openLDAP\var\openLDAP-data\ directory and delete it.
If this does not resolve the problem, see “Fixing OpenLDAP Corruption” on page 66 to restore a backup
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.
Using the Shared Services Registry Editor
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
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.
Generating a Report of the Contents of the Shared Services

Registry
Issue: If you cannot access the Shared Services Lifecycle Management user interface and need
to view the contents of the Shared Services Registry, you can use the Registry Editor utility to
generate an HTML report.
62 Troubleshooting Shared Services and Provisioning

Solution: Double-click (or execute without parameters) epmsys_registry.bat or
epmsys_registry.sh, found in HYPERION_HOME/common/config/9.5.0.0, to generate a
report called registry.html.
Editing the Shared Services Registry to Change User

Directories Information, Shared Services Server or Port
If you cannot access the Shared Services Lifecycle Management user interface and need to make
a change to user directories information or your Shared Services server or port, you can use the
Registry Editor utility. Here is a sample procedure to accomplish that task.
ä To extract, view and update the CSSConfig file:

1 Extract the CSSConfig file by opening a shell on the Shared Services server:
cd /d %HYPERION_HOME%/common/config/9.5.0.0
%HYPERION_HOME%/common/config/9.5.0.0/epmsys_registry.bat view SYSTEM9/

FOUNDATION_SERVICES_PRODUCT/SHARED_SERVICES_PRODUCT/@CSSConfig
2 Update the CSSConfig file by opening a shell:
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
EPM System Product Registration with Shared Services

This section discusses an issue that can occur in an environment where Shared Services is set up
for failover on two physical servers, withShared Services Web application and Native Directory
running on the primary server and the standby server.
Issue: When you configure EPM System products, EPM System Configurator cannot register
them with Shared Services.
Solution: Follow these steps:
1. Before installing or upgrading Shared Services:
l Add a CName record to the DNS for Shared Services on all EPM System product
installation servers.
l Add the alias to the host file on all EPM System product installation servers.
2. Install and configure the EPM System products, including Shared Services.
The alias now comes up as the server name in the Advanced panel during Shared Services
configuration, and the registry is updated with the correct Shared Services alias.
EPM System Product Registration with Shared Services 63

Note: Restart EPM Workspace and Shared Services after any change to Shared Services
registration information.
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.
User Directories and Provisioning

This section identifies guidelines that should help you avoid typical user directory and
provisioning issues. It also provides solutions to common user provisioning problems. For
information about user directories and provisioning users, see the Oracle Hyperion Enterprise
Performance Management System Security Administration Guide.
Provisioning Basics and Best Practices

If you have an existing user directory, use a standard LDAP Browser to explore the user
directories that store user credentials before provisioning EPM System applications. The settings
that the LDAP Browser uses to connect to the user directory are identical to those that EPM
System applications use to connect to the user directories. You can download a free LDAP
Browser.
Use the Browser to determine the following:
l Whether you can connect to the user directory from the server that you are using
l The response time
l The starting point (base DN) for any search of the user directory
l A count of the users and groups under the starting point
To ensure acceptable login performance:
l Minimize the number of groups and users for EPM System applications.
l Ensure that the server machines that host EPM System applications are in the same
geographical location as the server machines that host the user directories used in the
provisioning process.
l Find an optimal starting point for searches or create a custom group hierarchy.
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.

l The Group URL in CSSConfig is incorrectly defined
l An excessive number of groups are defined in the Group URL
Retrieving Users, Register Applications, and Load Security More Quickly

Perform the following procedure to perform these tasks faster:
l Retrieve lists of users against projects
l Register applications
l Load security
ä 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
Modifying the Group URL

Having more than 10,000 groups in the Group URL degrades performance. To resolve this issue,
perform these steps:
l Change the Group URL to point to a lower-level node
l Use a group filter that retrieves only provisioned group
l Create a custom group hierarchy to support EPM System applications
Setting the Maximum Size

For NTLM, MSAD, LDAP, Oracle Internet Directory, and SAP, the number of users and groups
a search retrieves is determined by the MaximumSize setting in the user directory configuration.
MSAD Windows 2000 limits this to 1,000, while MSAD Windows 2003 limits to 1500.
For NTLM, LDAP, or MSAD, retrieve more users and groups by setting MaximumSize to 0 on
Directory Configuration page. For Oracle Internet Directory, increase the default setting of 5000
as required.
User Directories and Provisioning 65

OpenLDAP Issues
This section contains solutions to errors you may encounter using OpenLDAP.
Working with OpenLDAP

Perform these tasks to ensure that OpenLDAP works correctly:
l Restore OpenLDAP and the database used with Shared Services simultaneously to ensure
synchronization
l Perform a hot backup of OpenLDAP using backup procedures in the Oracle Hyperion
Enterprise Performance Management System Backup and Recovery Guide
l Perform a weekly cold backup on the OpenLDAP database and the Shared Services database
l Recover provisioning data before restoring it from a backup
l Do not manually shut down the computer hosting OpenLDAP, terminate the OpenLDAP
process from the task manager or while data is being written
For more information, see Oracle Hyperion Enterprise Performance Management System Security
Administration Guide
Resolving OpenLDAP Provider Startup Failure Due to

Corruption
Perform these tasks if the LDAP provider you use with Shared Services does not start because
of corruption.
ä To start the LDAP provider:

1 Check for a file named alock in the openLDAP\var\openLDAP-data\ directory and delete it.
2 From a command line, start OpenLDAP in debug mode as follows:
a. Enter: cd c:\\Hyperion\SharedServices\version\openLDAP or:
%HYPERION_HOME%\SharedServices\version\openLDAP.
b. Enter slapd —d 1.
Fixing OpenLDAP Corruption

OpenLDAP becomes corrupt, because of sudden power loss, or because of a power loss while
the service is running.
To recover:
Run recover.bat, located in the SharedServices\server\scripts folder, and pass in the
backup location as a parameter. For example, recover.bat c:\backupOpenLDAP

Deployment to WebLogic
If Shared Services deployment to WebLogic fails, modify HYPERION_HOME/deployments/
WebLogic9/bin/setCustomParamsSharedServices9.sh and append JAVA_OPTIONS
variable with the-XX:MaxPermSize=256M option. This is a WebLogic issue. See the WebLogic
documentation, "WebLogic Server Performance and Tuning" under http://edocs.beasys.com/
wls/docs92/perform/index.html.
Loss of Shared Services Response

When Shared Services is configured with WebLogic 9.2.1 and Oracle 11g, Shared Services
provisioning, Oracle Hyperion Enterprise Performance Management System Lifecycle
Management, or EPM System auditing may stop responding. To resolve this issue, use the
WebLogic Console to change the Stuck Thread Max Time value to 60000 and the Accept Backlog
value to 50000 for Shared Services.
Startup and Access Issues

This section provides solution to problems that you may experience starting Shared Services and
launching other applications from Shared Services.
Resolving Shared Services Service or Process Startup Failure

The service may not run if OpenLDAP is corrupt or not running. If this is the case, run or restore
OpenLDAP. See “Fixing OpenLDAP Corruption” on page 66.
Resolving a Shared Services Startup Failure on the

Application Server
If the Shared Services Web application does not start:
1. Review the Shared services logs in %HYPERION_HOME%\logs\SharedServices9
2. From Oracle's Hyperion Enterprise Performance Management System Diagnostics, validate
that database connectivity is successful, as well as checking OpenLDAP and external
providers. These are all prerequisites for successful Web application startup.
3. Determine whether the default port 28080 is being used by another application by running
NETSTAT –an | findstr 0.0.0.0:28080. If you get (0.0.0.0:28080), change the
Shared Services port or stop the process that is using the port
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.
Resolving Problems Accessing Products from Shared

Services
You may be unable to log into other EPM System products for these reasons:
l The group URL and group filter are not limiting the number of groups returned by a search
l The user URL is incorrect
l You are using invalid logon credentials
l The server hosting the product is not connected to the servers hosting user directories and
Shared Services
l OpenLDAP is not running
l The provider URL in each product CSSConfig file is the same, including case. For example,
because of capitalization, these entries would prevent you from logging on:
ldap://ldaps-na-ad. directory.xerox.com:636/DC=na,DC=Xerox, DC=net
ldap://ldaps-na-ad. directory.xerox.com:636/DC=NA,DC=XEROX, DC=NET

l The URL at which you registered your application (the Financial Management Security URL,
for example) is not accessible from the Shared Services server.
Perform these tasks:
1. Review SharedServices_Security_Client.log (on the server hosting the product)
and SharedServices_Security.log (on the server).
l If group cache errors exist, ensure that the group URL and filter are limiting the number
of groups returned by the search.
l If authentication errors exist, verify that the user URL is correct.
2. Ensure that the user ID and password are correct.
3. Ensure that the server hosting the product can connect to the servers hosting the user
directories and Shared Services.
4. Start the OpenLDAP service or process.

Reconfiguring Product Registration in Shared Services to Use
a Web Server
ä To reconfigure product registration to use a Web server:
1 On the computer where the Shared Services Server resides, open Microsoft Word.
2 Select File and then Open, and enter: http://HSS_Server:28080/interop/content.
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.
Reregistering a Product with Shared Services

Issue: You need to reregister existing products with Shared Services.
Solution: Use the following procedure:
1. Locate the product_config.xml in the Hyperion\common\config\version
\product\product_name folder.
2. Open the file and find the line <property_name>=”hubRegistration”>Configured</
property>.
3. Remove the word “Configured” and replace it with “Pending”.
4. Rerun EPM System Configurator and select the product.
This enables you to reregister the product with Shared Services.
Reconfiguring the Shared Services Database

Issue: You cannot successfully change an already configured Shared Services database directly
in EPM System Configurator.
Solution: To work around this issue:
1. Delete HYPERION_HOME/common/config/9.5.0.0/reg.properties.
Startup and Access Issues 69

2. Restart the EPM System Configurator
3. Reconfigure the Shared Services database, by selecting the option to “connect to a previously
configured database”.
Resolving Product-Specific Issues

This section identifies solutions to errors you may encounter using other Hyperion products
with 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.
Logging in After Externalizing a User

Perform the procedure if you externalize a user (essadmin for example) from Essbase to Shared
Services, but cannot log back in to Essbase:
1. Ensure that the user exists in Shared Services.
2. MSAD or LDAP: If the user exists, perform these tasks:
a. In Essbase installation folder\bin, rename essbase.bak_preUPM as
essbase.sec.
b. Create a native user with admin privileges.
c. Externalize this user using password as the password.
d. Log on to Essbase as the new user.
e. In Shared Services, search for the user in Native Directory or in an external directory
and provision the Administrator role to Essbase.
f. In Essbase, refresh security.
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

If you can, ensure thatjrm.dll is in \Hyperion_HOME\common\JRE\sun\1.5\bin
\client\ and correctly referenced in essbase.cfg
Resolving Corrupt OpenLDAP Database When No OpenLDAP Backup Exists

Perform these tasks if OpenLDAP becomes corrupt:
1. See “Fixing OpenLDAP Corruption” on page 66.
2. Launch Essbase.
3. Rename essbase.bak_preUPM to essbase.sec. This renames the older file.
4. Put essbase.bak_postUPM in another folder. This returns Essbase to preexternalization
state.
5. Install and configure Shared Services
Administration Services and Integration Services

This section provides solutions to some problems you may encounter using Shared Services with
Essbase and Administration Services.
Retrieving Essbase Roles

l You receive the following error refreshing security to Shared Services from the
Administration Services console.
l You reregistered with the Essbase Server using EPM System Configurator.
Error: 1051502: Analytical Services failed to get roles list for
[ESB:Analytic Servers:PLYSHYP08D:1] from Shared Services Server with
Error [Failed to connect to the directory server.]
To troubleshoot this issue, refer to the SharedServices_Security_Client.log in the

Essbase logs folder.
Reporting and Analysis

This section provides solutions to errors you may encounter configuring and using Shared
Services with Reporting and Analysis.
Changing the DNS Name or the EPM Workspace Server

If you change the DNS name of the EPM Workspace server, you may need to update the instance
files manually. See “ Reconfiguring Product Registration in Shared Services to Use a Web Server”
on page 69.
Resolving Product-Specific Issues 71

Financial Performance Management Applications
Services with Financial Management and Performance Scorecard.
Financial Management
Services with Financial Management.
Resolving an “Application Creation Fails” Error

If you receive this error, perform these tasks:
l Review SharedServices_Security_Client.log.
If group cache errors are displayed, ensure that the group URL and filter are limiting the
groups returned by the search. If data broker property errors display,
enableinteropjava logging. Exceeding 1,000 groups in the group URL causes a known
JRE 1.4.2 bug. Use JRE 1.5 to support 1,000 or more groups.
l Ensure that the Financial Management application server can communicate with Shared
Services using HTTP and WEBDAV protocol. Webdav may be blocked if you proxy requests
from IIS to interoperate with the Web application. If this is the case, ensure that the UrlScan
IIS extension does not block propfind methods.
If you are using IIS on Windows 2003 sp1, add the IIS the UseBasicAuth registry key to
dword 1 in the registry HKLM\SYSTEM\CurrentControlSet\Services\WebClient
\Parameters.
l If the interop Web site that redirects to the Web application server, ensure that the
authentication method is anonymous and that Windows integration authentication is not
used.
l WebSphere: If you use a Web server to forward requests to the Web application server,
ensure that plugin-cfg is set to AcceptAllContent-true.
Preventing Smart View Timeouts

If Smart View with Financial Management times out after about 30 minutes, try one or more of
these procedures:
l Run the Server and Web configuration utility on the Financial Management Web server,
and change the Web session timeout setting. (The default setting is 20 minutes.)
l If the client is using the URL provider for Smart View (not the Shared Services provider),
right-click for the properties of the HFMOfficeProvider virtual directory in IIS and click
Configuration on the Virtual Directory tab. In the new window, click Options and change
the session state timeout setting.
l Change the setting of the default Web site.

Also check the timeout settings of the Default Web site and the Smartview Provider settings in
the FM Server and Web Configuration.
Resolving Inactive Secure URLs

If the secure URLs that you used to register applications become inactive and must be repeatedly
reregistered.
To resolve this issue, import the root ca certificates to the Java keystore cacerts in all Java
installations in Hyperion/common.
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.
Required Oracle Database User Permissions

You installed Hyperion 9.3.0.1 using an Oracle Database. You assigned owner privileges to the
Oracle user ID that you currently use. Your security policy has blocked access to this user and
you need to know the privileges to assign to a substitute Oracle user.
To resolve this issue, grant the user read/write permissions in the database. If the user will
generate an Essbase database of Performance Scorecard data, also assign permissions enabling
them to create indices and execute procedures.
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.
Resolving Product-Specific Issues 73

Troubleshooting EPM
6 Workspace
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
Tips and Recommendations

l Complete configuration information about your EPM Workspace installation, including
GSM and Shared Services information, is available at:
http://hostname:port/workspace/browse/configInfo
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.
Tips and Recommendations 75

Tomcat Startup Fails and EPM Workspace is
Unavailable
Issue: Apache Tomcat fails to start, and EPM Workspace is not available on port 19000. This
occurs under these conditions:
l Shared Services and EPM Workspace Web and services are installed on computer 1.
l EPM Workspace Web and services only are installed on computer 2.
l All configuration is done on computer 1 except for EPM Workspace database configuration
and Shared Services registration for EPM Workspace.
Solution: Comment this line in httpd.conf:
#LoadModule auth_digest_module modules/mod_auth_digest.so
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.
Solution: View the server_messages_AuthenticationService.log:

l Contact the administrator to confirm user credentials if the log contains:
event logger="com.brio.one.services.utils.css.CSSUtility" <!
[CDATA[Invalid login for <NAME>. Exception:
com.hyperion.css.CSSAuthenticationException. ErrorCode: 2. Msg:
Failed to authenticate user
l Verify Shared Services availability if the log contains:
<message><![CDATA[Invalid login for <NAME>. ErrorCode: 10]]></
message><throwable><![CDATA[ Error Code: 10
com.hyperion.css.CSSException: User: <NAME>, not found
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.
Note: In general, always start EPM Workspace last.
76 Troubleshooting EPM Workspace

Logging On When the EPM Workspace Agent is Down
Issue: If a user attempts to log on while the EPM Workspace Agent is down, starting the agent
again is not sufficient. The user can log on, but the user's roles are not granted unless the services
are started in the correct order.
Solution: Restart EPM Workspace services in the following order:
1. Workspace agent
2. Workspace UI (CMC)
3. Workspace application server
4. Workspace Web server
Cannot Access Configuration Management Console

Issue: From EPM Workspace, you cannot access the Configuration Management Console
(CMC).
Solution: Since there is no Windows service for the new Configuration Management Web
application, check whether you launched the \<HYPERION_HOME>\common\workspacert\9.
5.0.0\bin\startUI.bat or startUI.sh to start CMC. Startup and shutdown of the CMC
UI is documented in the “Starting and Stopping EPM System Products” chapter of the Oracle
Failure to Access Modules

Issue: User cannot access any configured modules.
Solution:
l Contact the administrator to verify user privileges.
l If you configured any EPM Workspace based product separately (for example, Planning,
Financial Management, Oracle Hyperion Financial Reporting, Fusion Edition, Oracle's
Hyperion® Web Analysis etc.), in the EPM System Configurator, run the Workspace Web
Server configuration task. There is no need to do this if everything is configured in one pass.
Logging On When the EPM Workspace Agent is Down 77

78 Troubleshooting EPM Workspace
Troubleshooting Essbase
7 Modules
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.
Essbase Server Failure

Several issues can cause the Essbase server to fail to start after installation. The following table
lists error messages and issues and suggests solutions:
Error Message or Issue Solution
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.
Error: Fatal Error: Essbase is already Check to see if Essbase is running:

loaded
l Windows: Check the Windows Task Manager for the essbase.exe process.
The Essbase agent is already running. l UNIX: Use ps -ef | grep ESSBASE to check for the essbase process.
If Essbase is not already running, then another user may be running a process on
the port setting you have specified for Essbase in essbase.cfg. For instructions
on shutting down Essbase, see “Running Essbase Servers, Applications, and
Databases” in the Oracle Essbase Database Administrator's Guide.
Essbase 79
Error Message or Issue Solution
Error: Failed in GCInit() Check ESSBASEPATH in hyperionenv.doc (UNIX) or setEssbaseEnv.cmd

(Windows):
This error can mean that the local directory in
ESSBASEPATH is not found or that files are missing l Windows: In the command line, enter echo ESSBASEPATH.
files from the local directory. l UNIX: In the console window, enter > echo $ESSBASEPATH
If the ESSBASEPATH is missing or incorrect, define the correct ESSBASEPATH.
ESSBASEPATH should use startEssbase.cmd (Windows) or startEssbase.
sh (UNIX), not essbase.exe.
See the Oracle Hyperion Enterprise Performance Management System Installation

and Configuration Guide.
Error: ESSBASE: not found Define ARBORPATH.

This can mean that startEssbase.cmd If ARBORPATH is already defined, then add it the path:
(Windows) or startEssbase.sh (UNIX) is not in
Windows: Add %ARBORPATH%\bin
the environment path.
l
l UNIX: Add $ARBORPATH/bin
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.
Installation on Different UNIX Systems

Issue: You cannot install Essbase simultaneously on different UNIX systems.
When you run EPM System Installer on different UNIX systems at the same time, EPM System
Installer attempts to write the temporary installation files in the same $HOME/
80 Troubleshooting Essbase Modules

InstallShield directory, causing each Essbase installation to fail. EPM System Installer uses
InstallShield, a third-party tool, and an InstallShield limitation causes this conflict.
Solution: Complete an Essbase installation on one UNIX system before starting an installation
with the same user on another UNIX system.
Administration Services
The following sections describe common Administration Services issues.
Problems Assigning Filters

Issue: You experience problems when assigning Essbase filters for an application using the
Shared Services User Management Console.
Solution: Register the application with Shared Services using the Administration Services
Console (right-click the application and select Register). Then try reassigning the filter in Oracle's
Hyperion® Shared Services Console.
Integration Services
This section describes common Integration Services issues and solutions.
Connection Failure to OLAP Metadata Catalog or External

Data Source
Issue: You cannot connect to OLAP Metadata Catalog or to the external data source.
Possible Solutions:
l Ensure that you are using the correct user name and password.
m If you are trying to connect to OLAP Metadata Catalog, ensure that you used the same
user name and password as the user who created the tables in OLAP Metadata Catalog.
If you create OLAP Metadata Catalog when logged in as one user name, you cannot
access the tables in OLAP Metadata Catalog using a different user name unless you create
an alias for the user name (for Microsoft SQL Server) or synonyms for the tables (for
IBM DB2 and Oracle).
m Does the user name you used have the correct privileges to access both OLAP Metadata
Catalog and the data source at the database level?
l Ensure that all of the required components are up and running. The following components
are required:
m Oracle Essbase Integration Services Server
m The database servers that manage OLAP Metadata Catalog and the data source databases
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.
Out of Memory Errors With Concurrent Users

Issue: “Out of memory” errors when running Provider Services with a large number of
concurrent users.
Solution: Increase application server memory using the JAVA_OPTS command in the application
server environment and in Start APS.
Example: After deploying Provider Services to WebLogic, edit HYPERION_HOME\deployments
\WebLogic9\bin\setCustomParamsaps.cmd to modify the settings for the set
JAVA_OPTIONS default value of -Xms32M to these two values respectively -Xms512M -
Xmx512M.
Load Balancing Problems with WebLogic through Apache

Issue: In Provider Services, Load Balancing with WebLogic through Apache might not work. In
this situation, when you apply one of the URLs through Internet Explorer, it will fail to return
the correct Oracle Hyperion Provider Services page.
Solution: Comment out Include conf/mod_jk2.conf line in Apache_Home/conf/
httd.conf, and then restart Apache.
82 Troubleshooting Essbase Modules

Troubleshooting Financial
8 Performance Management
Applications
In This Chapter
Common Planning Issues .................................................................................83
Common Financial Management Issues .................................................................85
Common Performance Management Architect Issues ..................................................90
Common Planning Issues

Note: If you experience problems installing or running Shared Services or have issues with
external authentication, see Chapter 5, “Troubleshooting Shared Services and
Provisioning .” For information about error logs, see Chapter 3, “Using EPM System
Logs.”
Planning Access
This section discusses access issues you might encounter with Planning.
Failure Accessing Planning through EPM Workspace

Issue: You get an error message when trying to access Planning through EPM Workspace.
Solution: Perform these steps:
1. Test access to EPM Workspace using this URL: http://Web Server:port/
workspace/, where Web Server is the Web server machine host name and port is the
Web server listen port; for example, 19000 if using the Apache instance configured with
Reporting and Analysis.
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 Planning directly. See “Failure
Accessing Planning Directly” on page 84.
3. If you can log on to Planning directly but still can not open Planning from EPM Workspace,
check the log file for the successful load of the Hyperion Planning module. If the log says
the module could not be loaded, you must run EPM System Configurator and reregister
Planning with Shared Services.
Common Planning Issues 83

Failure Accessing Planning Directly
Issue: You cannot access Planning through the EPM Workspace, and need to access Planning
directly.
Solution: Try this URL: http://hostname:8300/HyperionPlanning/LogOn.jsp. If this
does not work, Planning did not install correctly. Check the Planning log in HYPERION_HOME
\logs\.
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.
Applications Not Visible in EPM Workspace

If you do not see the Planning applications in EPM Workspace after an upgrade from the
previous release, ensure the applications are reregistered with Shared Services from the Classic
Wizard for classic Planning applications and from Performance Management Architectfor the
Planning applications in Performance Management Architect.
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.
84 Troubleshooting Financial Performance Management Applications

Using Planning with Administration Services
Issue: You cannot expand the Planning outline in Oracle Essbase Administration Services.
Solution: Turn on debugging and check the following items:
1. Check the RMI server is running properly.
2. Check Oracle Essbase.
3. Check security and external authentication.
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
Note: This solution also applies to Calculation Manager.
Common Financial Management Issues

Note: If you experience problems installing or running Shared Services or have issues with
external authentication, see Chapter 5, “Troubleshooting Shared Services and
Provisioning .” For information about error logs, see Chapter 3, “Using EPM System
Logs.”
Common Financial Management Issues 85

Accessing Financial Management
This section discusses access issues you might encounter with Financial Management.
Failure Accessing Financial Management Through EPM Workspace

Issue: You have difficulty accessing Financial Management.
Solution: Perform these steps:
1. To test access to EPM Workspace, use the following URLs, where webserver is the host
name of the machine running the EPM Workspace Web server, webport is the port for the
Web server (by default, 19000), hfmserver is the host name of the machine running the
Financial Management Web component, and hfmport is the port for the Web server used
by Financial Management (by default, 80):
URL Expected What to Check if the Actual Result is Different

Result
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.
http:// A page is l The Financial Management Web server is running.

webserver:webport/hfm/ displayed that Web server configuration files point to the correct host name and port for
says only
l
the Financial Management Web server.
“hfm.”
http:// A page is The Financial Management Web server is running.

hfmserver:hfmport/hfm/ displayed that
says only
“hfm.”
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.
Failure Logging on to Financial Management

Issue: You cannot log on to Financial Management because there might be a security access
issue.
Solution: Verify these items:
l Financial Management is installed and configured.
l IIS is started, and a virtual directory for Financial Management was created.

l In IIS, verify the settings for authentication. You can use Anonymous Authentication or
Web Authentication, depending on your security policies.
ä To check the authentication method:

1 Start IIS and expand Default Web Site.
2 Right-click the folder for Web authentication; for example, the Financial Management folder for the Web,
and select Properties.
3 Select Directory Security.
4 Verify that either Anonymous Access or Web Authentication has been properly configured.
Privileges for IIS

Issue: While using Financial Management, you get a security access error message involving an
ASP file. This can occur if privileges for IIS are set incorrectly.
Solution: Go to the default Web site, and edit the properties for directory security to enable
anonymous access.
Connection Troubleshooting
These are some common connection issues for Financial Management.
Connection to Financial Management Fails

Solution: If the DCOM launching user is set to a local machine account, domain users cannot
log on to some modules. For example, if a user logs on to a workstation with a user ID on Domain
A, and logs on to Financial Management with a user ID on Domain B (or any domain that
Domain B can access), when the user attempts to connect to a Financial Management server on
Domain B, the connection might fail. To resolve the problem, perform one of these procedures:
l Set up a one-way trust relationship from Domain B (Financial Management Server) to
Domain A (Financial Management Client). This method is recommended.
l Set the DCOM Default Authentication Level to None on the client. However, note that by
turning off the DCOM authentication on the client, DCOM authentication is turned off for
all DCOM applications on the client.
Installation Fails after Computer Restart

Solution: Check the Remote Procedure Call service in Windows.
ä To check the remote procedure call service:

1 Open Windows Control Panel and select Services.
2 Check the Remote Procedure Call (RPC) Locator, which is set to Manual by default. Select the service,
click Start, and restart the computer.

Database Connection Fails
Solution: Ensure that the database server name, user name, password, and database name are
correct in the UDL file. See “Verifying Data Link Connection Settings” on page 89.
If the UDL file contents are correct and the database connection fails, reinstall the Oracle database
client.
Connection to SQL Server Fails

Issue: You receive the error message“SQL Server: Test connection failed because
of an error in initializing provider. Client unable to establish
connection.”
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.
Establishing the SQL Server Connection Using TCP/IP

If you use Microsoft SQL Server 2005, it disables TCP/IP connections to the database by default.
You must enable these connections before running the Hyperion Configuration Utility.
ä To establish the SQL Server connection using TCP/IP:

1 Select Start, then Settings, and then Control Panel.
2 Select Administrative Tools, and double-click Data Sources (ODBC).
3 Click Add.
4 In the list of drivers, highlight SQL Server, and click Finish.
5 Enter a data source name, description, the data server name for the SQL Server to which to connect,
and click Next.
6 Select this authentication option: With SQL Server authentication using a login ID and password entered
by the user.
7 Click Client Configuration, select TCP/IP (if not selected), and click OK.
8 For Connect to SQL Server, enter the login ID and password, and click Next.
9 Change the default database to the Financial Management database.
10 Click Next, and click Finish.

11 Click Test Data Source.
12 When you receive the success message, click OK, and click OK to close the dialog box.
13 Click OK to close the ODBC Administrator dialog box.
14 Create and configure the data link: .udl.
Verifying Data Link Connection Settings

The default location of the UDL file, which EPM System Configurator
creates, is HYPERION_HOME/products/FinancialManagement.
ä To verify data link connection settings:

1 Right-click the UDL file name, and select Properties.
2 In Data Link Properties, select Connection
3 Ensure that Use a specific user name and password is selected.
Verifying Microsoft SQL Server Authentication Settings
ä To verify the Microsoft SQL Server authentication setting:

1 Select Start, then Programs, then Microsoft SQL Server, and then Enterprise Manager.
2 Expand the list of Microsoft SQL Servers.
3 Right-click the database server name, and select Properties.
4 Select Security.
5 Ensure that this Authentication option is selected: SQL Server and Windows.
6 Click OK.
Rights Required for Installation

Issue: You are having difficulty installing and configuring Financial Management.
Solution: Ensure that you have local administrator rights to install Financial Management.
Large Data or File Loads Fail

Issue: You receive an error message when performing large data or file loads.
Possible Solutions:
l In the Financial Management configuration utility, adjust the Max Upload File Size and
Response Buffer Size settings for IIS.
l If you are using Classic Administration and receive a “Proxy Error”, increase the Workspace
timeout setting.

Sticky Server Attempts to Redirect User
Issue: Every few minutes in the Windows application log , this event is recorded:
EventID(0) in Source (HyperionFinancialManagement): Sticky server
attempted to redirect user to server ! Return Code=-2147220919.
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.
Common Performance Management Architect Issues

This section discusses issues you might encounter with Performance Management Architect
installation and configuration.
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.
Failure Deploying to WebSphere after Upgrade

Issue: After you apply a maintenance release or upgrade to Oracle Hyperion Enterprise
Performance Management System Release 11.1.1.2, Performance Management Architect Web
deployment to WebSphere fails.
Solution: Upgrade WebSphere from version 6.1.0.x to version 6.1.0.17.
Note: This issue and solution also pertain to Hyperion Calculation Manager.

Integration with EPM Workspace
Issue: This EPM Workspace error message is displayed:
No connection could be made because the target machine actively refused
it.
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.
Accessing Performance Management Architect

This section discusses access issues you might encounter with Performance Management
Architect.
Performance Management Architect Logon Fails

Issue: You are having difficulty logging on to Performance Management Architect.
Solution: Ensure that you are using ASP.NET 2.0.50727 and that ASP.NET and ASP pages are
set to “Allowed”.
ä To check whether .NET 2.0 is installed on a Windows 2003 machine:

1 Open IIS Manager by one of these methods:
l Select Start, then Programs, then Administrative Tools, and then Internet Information
Services Manager.
l Run inetmgr.
2 In the left panel, select Web Service Extensions. In the right panel, note whether ASP.NET 2.0.50727
is listed.
3 If ASP.NET 2.0 is listed, enable it by checking that the Status column is set to Allowed.
4 If ASP.NET 2.0 was not listed and you have .NET 2.0 installed, register .NET 2.0 with IIS:
a. From the command prompt, go to this directory: C:\Windows\Microsoft.NET
\Framework\v2.0.50727
b. enter aspnet_regiis.exe —iru.
Common Performance Management Architect Issues 91

c. Repeat steps 1, 2 and 3.
Security Rights Issue When Logging On

Solution: The Application Creator and Dimension Editor security roles must be assigned to use
Performance Management Architect. See “Shared Services-Global Roles” in the Oracle Hyperion
Enterprise Performance Management System Security Administration Guide.
Failure Logging on to EPM Workspace

Solution: Ensure that you have followed the installation and configuration instructions for EPM
Workspace in the Oracle Hyperion Enterprise Performance Management System Installation and
Failure Starting the Process Manager Service

Issue: Cannot start Process Manager service.
Solutions: Check whether you've changed the Shared Services admin user or password. If so,
launch the EPM System Configurator and run the Configure Database task for Performance
Management Architect.
l Check whether you have changed the Shared Services admin user or password. If so, launch
the Oracle's Hyperion Enterprise Performance Management System Configurator and run
the Configure Database task for Performance Management Architect
l If the problem persists, check the Event Viewer for other possible causes.
Failure Displaying Tasks in Performance Management Architect

Verify these conditions:
l The Shared Services server is started.
For instructions on starting the Shared Services server, see the Oracle Hyperion Enterprise
Performance Management System Installation and Configuration Guide.
l EPM Workspace services are started.
l You have configured the EPM Workspace proxy server plug-in for your application server.
If you cannot access this URL, you must configure the proxy server plug-in:
http://Web Server:port/awb/conf/AWBConfig.xml, where Web Server is the Web
server machine host name and port is the Web server listen port; for example, 19000 for
the Apache instance configured with Oracle's Hyperion Reporting and Analysis.

Failure Accessing Performance Management Architect
Dimension or Application Library
If you cannot access a Performance Management Architect task, verify that you can access each
component separately to locate the source of the communication error.
Failure Displaying or Opening the Dimension Library

Issue: You cannot see the Dimension Library in Performance Management Architect.
Solution: Ensure that you have the correct Performance Management Architect roles. You must
have the Dimension Editor and Application Creator security roles to access the Dimension
Library. See “Shared Services-Global Roles” in the Oracle Hyperion Enterprise Performance
Management System Security Administration Guide. After you are assigned the Dimension Editor
role, log off and log back on to Performance Management Architect.
Issue: You cannot open the Dimension Library in Performance Management Architect.
Solution: Ensure that DCOMCNFG permissions are set correctly in Windows 2003.
ä To set DCOMCNFG permissions:

1 Select Start and then Run, and enter DCOMCNFG .
2 Expand Component Services, then Computers, then My Computer, and then DCOM Config.
3 Scroll to IIS Admin Service, right-click Properties and select the Security tab.
4 From Launch and Activation, select Customize and click Edit.
5 Click Add and add Network Service.
6 Select Allow for all permissions.
7 Click OK to close the dialog boxes.
8 Restart IIS and all Web servers.
Communication or Internal Server Errors

Possible Solutions:
1. Check this URL:
http(s)://Workspace_server:Workspace_port/awb/conf/AwbConfig.xml.
2. If this step fails, check this URL:
http(s)://bpma_server:bmpa_port/awb/conf/AwbConfig.xml
3. If this step works, then Performance Management Architect is not correctly enabled in EPM
Workspace. Reconfigure Oracle Enterprise Performance Management Workspace, Fusion
Edition.
4. If this step does not work (error is 404), then the Performance Management Architect Web
Server is not started.

Performance Management Architect Dimension Server Errors
Possible solutions:
l Use this URL:
http(s)://local_machine_name/hyperion-bpma-server/Sessions.asmx
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.
Failure Accessing the Performance Management Architect Dimension

Server Web Services
Possible Solutions:
l In the logs, if subcode is 2, and Win32 code is 1260, the problem is related to Web Service
Extensions. In IIS, Web Service Extensions, ensure that the ASP.NET 2.0.50727 Web Service
Extension status is Allowed.
l If SiteMinder is installed, remove the wildcard mapping:
1. From hyperion-bpma-server, click Properties and then Configuration.
2. Remove values in the wildcard mapping section.
IIS Startup Failure on Performance Management Architect Dimension

Server
From the Control Panel, select Administrative Tools and then Services, and start World Wide
Web Publishing Service, if it is not already started.
Performance Management Architect Services Startup Failure

Solution: Start the Performance Management Architect Process Manager service if it is not
already started. Then check that these services start:
l Engine Manager
l Event Manager
l Job Manager

l .NET JNI Bridge
Using IBM DB2 with Performance Management Architect

Issue: You experience performance issues using an IBM DB2 database with Oracle Hyperion
EPM Architect, Fusion Edition.
Solution: Implement the settings described in the Oracle Hyperion Enterprise Performance
Management System Installation and Configuration Guide.

Troubleshooting Data
9 Management
In This Chapter
Common FDM Issues ......................................................................................97
Common Data Relationship Management Issues.......................................................99
Common FDM Issues

This section contains installation and configuration issues you may encounter and
troubleshooting tips for FDM.
Configuration Issues with Financial Management

Issue: You receive this error message: Server/cluster is incorrectly configured.
Please reconfigure your Cluster or Server connection.
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.
Oracle Client / Provider Cannot Connect to Database

Issue: You receive this error message: ORA-12154: TNS; could not resolve service
name.
Solution: Correct outstanding Oracle issues, and ensure that you can resolve the Oracle Service
Name in tnsnames.ora.
Database User ID or Password Required

Issue: You receive this error message when you log on to FDM: ORA-12154: TNS; could
not resolve service name.
Solution: Follow these steps:.

1. Verify that the machine can communicate with the database server by creating: a UDL file
and entering the Database connection details and testing the connection.
Common FDM Issues 97

2. If using Oracle for the FDM database, ensure that the Oracle Client with Windows Interfaces,
which includes the Oracle Provider for OLE DB, is installed on any FDM application server
and any server accessing Oracle Hyperion Financial Data Quality Management, Fusion
Edition through the Workbench Client.
Cannot Authenticate User

Issue: Receive error message “Could Not Authenticate User” during Maps, Validate Stage,
Export Stage, or Control Tables.
Solution: Correct integration settings for application.
ä To correct integration settings:

1 Launch Workbench.
2 On the Adapter tab, expand Target System Adapters.
3 Expand the HFM Adapter set as the system wide adapter, or assigned to the FDM location.
4 Open machine profiles.
5 If there is a global ID, ensure that the user's password is correct.
6 Ensure the user has security level required to access target system application and the application
metadata.
Cannot Perform Bulk Insert

Issue: You receive this error message: Could not bulk insert because file '\
\servername\shared foldername \application foldername\Inbox
\filename.fmt' could not be opened. Operating system error code 5
(error not found)”
Solution: Follow these steps:

1. Check the SQL server to see which user is running MSSQLServer service. If the user account
is local, change it to domain and give the user read share permissions and Read NTFS to the
application folder \\servername\shared foldername\application foldername.
2. Launch SQL Server Enterprise Manager, and ensure that the user who created the database
has been granted the Bulk Insert Admin role.
Active-X Component Cannot Create Object

Issue: When logging on to Workbench, you receive an error message saying that the ActiveX
component cannot create an object.
Solution: Ensure that the user who is launching the workbench as change permissions to the
FDM application path, \\servername\fdmshare\fdmappname
98 Troubleshooting Data Management

Common Data Relationship Management Issues
This section contains installation and configuration issues you may encounter and
troubleshooting tips for Data Relationship Management.
Reviewing Readme Issues

Review these topics in the Data Relationship Management Readme to ensure that you install
and configure properly:
l Using Shared Services via SSL
l Microsoft .NET
l Upgrade May Get Error after Reboot
Open File Failed

Issue: You receive an “Open file failed”on Citrix or remote desktop.
Solution: Log on as User 0 when connecting by way of a remote session. Select Start, then Run,
and type this command: mstsc.exe /v servername /console /f or (if you are connecting
from an XP SP3 machine) mstsc.exe /v servername -admin /f.
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.
Server Unable to Process Requests

Issue: You receive the “Server was Unable to Process Request” error message.
Solution: For successful connectivity to the Data Relationship Management Web gateway, each
user must have write access to the Windows/Temp directory on the machine where the client
application runs. Check that users have write access.
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.
Common Data Relationship Management Issues 99

Unable to Create JVM
Error:Unable to Create JVM
Possible Solutions:
l Enable CSS and restart the service.
1. On the Common Security Services page, click Enable CSS.
2. Restart the service.
l Check that the Java path is correct.
l Check that Oracle's Hyperion® Shared Services is installed locally.
Invalid Classpath Root

Issue: Event log contains an “Invalid Classpath root” error.
Solution: Reboot the server.
Server Startup Failure

Issue: Oracle Hyperion Data Relationship Management, Fusion Edition server fails to start.
Solution:
l If you changed the classpath or system path, reboot the computer.
l Change the authentication mode to Internal, and start the server again. A successful start
confirms that the issue is related to CSS.
l Check the Event Log for error messages.
Error Message During Upgrade

Issue: This error message is displayed during an upgrade: “Service Oracle Hyperion Data
Relationship Management” failed to install with error: “System Error. Code: 1073. The specified
service already exists.”
Solution: Ignore the message, and click OK to complete the upgrade.
100 Troubleshooting Data Management

A B C D E F H I J K L M O P R S T U V W Z
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
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
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
system performance, 15 configuration, validation, 12

Web Analysis, 41 Installation Start Here, reviewing, 11
Web server, 18 installation, validation, 12
WebLogic, 18 logs, reviewing, 13
WebSphere, 18 port, avoiding, 12
readme, reviewing, 12
release compatibility, validating, 11
M startup dependencies, reviewing, 12
MetaLink 3, 13
system requirements, satisfying, 11
Multibyte characters
product registration, with Shared Services, 63
displaying in reports, 85
Production Reporting logs, 41
My Oracle Support, 13
Profitability and Cost Management
logs, 46
O Provider Services
OpenLDAP logs, 36
common issues, 66 provisioning
corruption, 66 best practices, 64
corruption, resolving without backup, 71 using Shared Services, 64
log levels, 20
startup commands, 20
startup failure with Shared Services, 66
R
registry.html file, missing, 57
tips, 66
release compatibility, 11
Oracle Application Server logs, 18
Reporting and Analysis
connection failure, 75
P logs, 37
performance issues logs, analyzing, 38
logs, 15 logs, configuring, 37
Performance Management Architect module access failure, 77
accessing, 91 tips, 75
common issues, 90 use with Shared Services, 71
logs, 27 restarting services, 58
Performance Scorecard
logs, 46
use with Shared Services, 73
S
security log, changing default location, 21
Planning
server startup failure, Data Relationship Management,
accessing from Workspace, 83
100
common issues, 83
services
direct access, 84
Architect Process Manager, startup, 92
directory structure, 84
Architect startup failure, 94
logs, 43
Shared Services startup failure, 67
multibyte characters in reports, 85
start and restart, 58
upgrade issues, 84
Windows, verifying, 58
with Essbase Administration Services, 85
Shared Services
port
application server startup failure, 67
conflicts avoiding, 12
common problems, 61
defaults for all products, 11
EPM System product registration, 63
prerequisites, 9
104 Index
external user directories, 64 UNIX

failure accessing products from, 68 JVM error, 59
load performance, increasing, 65 starting Tomcat, 59
login performance, improving, 64 upgrading
logs, 18 Financial Performance Management applications,
loss of response, 67 84
Registry Editor, 62 user authentication, Financial Data Management, 98
startup failure, 67 user directories
troubleshooting, 61 using with Shared Services, 64
troubleshooting utility, 62 user provisioning, 61
use with Reporting and Analysis , 71 best practices, 64
user provisioning best practices, 64 troubleshooting, 61, 64
user provisioning, troubleshooting, 64
using with Performance Scorecard, 73
using with Essbase, 70
V
validation, installation and configuration, 12
using with Financial Management, 72
using with Integration and Administration Services,
71 W
using with Workspace, 71 Web Analysis
Smart View logs, 41
installing, 84 Web server
Smart View logs, 26 Reconfiguring product registration, to use Web
SQL Server, establishing a connection using TCP/IP, server, 69
88 Web server logs, 18
starting services, 58 WebLogic
startup load balancing, Essbase Provider Services and
OpenLDAP commands, 20 Apache, 82
startup dependencies, 12 WebLogic, logs, 18
startup failure WebSphere, logs, 18
Architect services, 94 Workspace
IIS on Architect Dimension Server, 94 accessing Financial Management from, 86
OpenLDAP, 66 accessing Planning from, 83
Shared Services, 67 changing Server DNS name, 71
Tomcat on UNIX, 59 logon security rights, 92
support, accessing, 13
system requirements, 11
Z
zip file, logs, 16
T
technical support, 13
Tomcat
logs, 18
Tomcat, launching on UNIX, 59
U
unable to create JVM, Data Relationship
Management, 100
Index 105
106 Index

Epm Install Troubleshooting

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Epm Install Troubleshooting

Загружено:

Авторское право:

Доступные форматы

ORACLE® HYPERION ENTERPRISE PERFORMANCE

INSTALLATION AND CONFIGURATION

Chapter 2. Troubleshooting Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 3. Using EPM System Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 4. General Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 5. Troubleshooting Shared Services and Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 7. Troubleshooting Essbase Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 8. Troubleshooting Financial Performance Management Applications . . . . . . . . . . . . . . . . . . . . . . . . 83

Chapter 9. Troubleshooting Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Check the Oracle Documentation Library (http://www.oracle.com/technology/documentation/

About Troubleshooting EPM System Products

About Troubleshooting EPM System Products 9

Table 1 Documentation That You Need

Task Related Documentation

Table 2 Documentation That You Might Need

Task Related Documentation

Perform these tasks before contacting Support for assistance.

Meeting System Requirements

Reviewing the Installation Start Here

Checking Release Compatibility

Meeting System Requirements 11

Reviewing Startup Dependencies

Reviewing the Readme

Using the Installation Guide

Validating the Installation and Configuration

Using My Oracle Support (MetaLink 3)

Accessing Technical Support Resources

Common Log File Location

Logs for these products are not created in HYPERION_HOME/logs:

Log File Size and System Performance

Common Log File Location 15

What To Do Before Contacting Technical Support

to DEBUG; for example:

Table 3 Installation Log Files

Name Contents Location Rotation

product-install.log Indicates whether a product HYPERION_HOME/ Do not delete this log.

16 Using EPM System Logs

EPM System ConfiguratorLogs

Set the log4j.rootLogger= property to DEBUG. Example:

Name Contents Location Rotation

configtool.log Configuration task HYPERION_HOME/ Do not delete this log.

configtool_err. Configuration errors HYPERION_HOME/ Do not delete this log.

configtool_ Summary information HYPERION_HOME/ Do not delete this log.

Application Server and Web Server Logs

Application Server Logs

EPM System ConfiguratorLogs 17

Table 5 Application Server Log Files

Application Server EPM System Log Location

Oracle Application Server 10g HYPERION_HOME/deployments/Oracle10g/product/application-deployments/

Oracle WebLogic Server 9 HYPERION_HOME/deployments/WebLogic9/servers/product/logs/

IBM WebSphere 6 HYPERION_HOME/deployments/Websphere6/profile/logs

Embedded Java Container HYPERION_HOME/logs/Tomcat

Web Server Logs

Foundation Services Logs

Shared Services Logs

Log File Names and Descriptions

Name Contents Rotation*

18 Using EPM System Logs

SharedServices_Security.log External authentication and single sign-on activity Archive

SharedServices_Security_Upgrade.log Migration-related activity, if applicable Archive

SharedServices_Admin.log User management activity Archive

SharedServices_Hub.log Shared Services context listener activity Archive