Installation and Configuration Troubleshooting …docshare01.docshare.tips/files/5017/50173879.pdfContents Chapter 1. Introduction 9 About Troubleshooting EPM System Products 9 Assumed

O R A C L E ® H Y P E R I O N E N T E R P R I S E P E R F O R M A N C EM A N A G E M E N T S Y S T E M

R E L E A S E 1 1 . 1 . 1 . 3

I N S T A L L A T I O N A N D C O N F I G U R A T I O NT R O U B L E S H O O T I N G G U I D E

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 anddisclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement orallowed 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 decompilationof this software, unless required by law for interoperability, is prohibited. The information contained herein is subject tochange 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 customersare "commercial computer software" or "commercial technical data" pursuant to the applicable Federal AcquisitionRegulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, andadaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, tothe extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, CommercialComputer 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 orintended for use in any inherently dangerous applications, including applications which may create a risk of personalinjury. 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 affiliatesdisclaim 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 theirrespective owners.

This software and documentation may provide access to or information on content, products, and services from thirdparties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind withrespect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for anyloss, 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, SharedServices 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 ApplicationLibrary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

1Introduction

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 isavailable.

About Troubleshooting EPM System ProductsThis guide provides troubleshooting tips for installing and configuring Oracle HyperionEnterprise Performance Management System products. It contains general information abouthow 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 andsolutions to difficulties using Oracle Enterprise Performance Management Workspace, FusionEdition and Oracle's Hyperion Reporting and Analysis.

Assumed KnowledgeThis guide is for administrators who install, configure, and manage EPM System products. Itassumes 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, includingauthentication providers such as Oracle Internet Directory, LDAP, or Microsoft ActiveDirectory, 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

http://www.oracle.com/technology/documentation/epm.html



Installation Documentation RoadmapYou can find EPM System installation documentation on the Oracle Documentation Library(http://www.oracle.com/technology/documentation/epm.html) on Oracle® TechnologyNetwork.

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 StartHere

l Installing and configuring EPM System products

l Automatically deploying EPM System products

l Starting EPM System products

l Validating the installation

l Upgrading EPM System products

Oracle Hyperion Enterprise Performance Management System Installation andConfiguration Guide

Securing EPM System and provisioning users Oracle Hyperion Enterprise Performance Management System SecurityAdministration Guide

Table 2 lists the documents to consult for additional installation tasks that you might need toperform.

Table 2 Documentation That You Might Need

Task Related Documentation

Manually deploying EPM System products Oracle Hyperion Enterprise Performance Management System Manual DeploymentGuide

Creating a backup of product and application data Oracle Hyperion Enterprise Performance Management System Backup andRecovery Guide

Migrating from one environment to another Oracle Hyperion Enterprise Performance Management System LifecycleManagement Guide

Enabling SSL Oracle Hyperion Enterprise Performance Management System SSL ConfigurationGuide

Clustering EPM System applications for highavailability

Oracle Hyperion Enterprise Performance Management System High AvailabilityGuide

10 Introduction



http://www.oracle.com/technology/products/bi/hyperion-supported-platforms.html


2Troubleshooting Basics

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 requirementsspecified in the Oracle Hyperion Enterprise Performance Management System CertificationMatrix. 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 containsrelease compatibility, prerequisites, default ports, and other information needed to plan asuccessful installation.

Checking Release CompatibilityIf you are upgrading from a previous release, it is important to check whether the softwareversions of EPM System products in your environment are compatible. See the Oracle HyperionEnterprise Performance Management System Installation Start Here.

Meeting System Requirements 11



Avoiding Port ConflictsDuring EPM System product configuration, default port numbers for Web applications arepopulated automatically. You can change the defaults during configuration, but each portnumber 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 PerformanceManagement System Installation Start Here.

Reviewing Startup Dependencies Ensure that you have reviewed the startup dependencies for EPM System products in the OracleHyperion Enterprise Performance Management System Installation and Configuration Guide.Although services are started automatically in a Windows environment, you may have occasionto start services manually. This chapter also provides default product URLs. Before you startservices or processes, start all databases used as repositories.

Before starting a service or process, ensure that the preceding service or process startedsuccessfully. Some services or processes take longer than others to initialize, and startup timesmay vary by computer.

Reviewing the Readme The Oracle Hyperion Enterprise Performance Management System Installation and ConfigurationReadme contains known installation or configuration issues for all EPM System products. It isvery important to review this readme for late-breaking information that may affect yourdeployment.

In addition, each EPM System product includes a Readme document for each release. Thesereadmes contains other known issues and late-breaking information for the products.

Using the Installation GuideThe Oracle Hyperion Enterprise Performance Management System Installation and ConfigurationGuide provides step-by-step installation and configuration procedures for all EPM Systemproducts. Very often you can find the answer to an installation or configuration issue by usingthe installation guide to verify that you have correctly completed all required steps. The guidecovers both fresh installations and upgrades from earlier releases.

Validating the Installation and ConfigurationAfter installing and configuring a product, perform these tasks to validate the deployment.

l Use Oracle's Hyperion Enterprise Performance Management System Diagnostics to test thestatus of installed and configured EPM System components, diagnose problems, and assistin 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 HyperionEnterprise Performance Management System Installation and Configuration Guide

l Check for exceptions and errors in the installation logs to ensure that all necessarycomponents 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 Configuratorsummary 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 LogsA fundamental troubleshooting technique is to enable and use debugging information inproduct log files. Use this technique before calling Technical Support so that you can providespecific 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 theMy Oracle Support knowledge base (MetaLink 3) for information about resolving installationand 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, ifnecessary, 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 managementsolutions by delivering technical expertise whenever you need it, Oracle Support Services isavailable at http://www.oracle.com/support/index.html.

Using Logs 13

14 Troubleshooting Basics

3Using EPM System Logs

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 LocationLog files for most EPM System products are created in HYPERION_HOME/logs/product. Forexample, 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 thischapter.

Log File Size and System PerformanceLogs 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. Revertto the original log levels after troubleshooting is complete to avoid using too much disk spaceand negatively affecting performance.

Suggestions in this chapter regarding log retention and rotation are not intended as strictguidelines.

What To Do Before Contacting Technical SupportBefore contacting Technical Support, run EPM System Diagnostics. EPM System Diagnosticsgenerates 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 LogsYou can specify the logging level for Oracle Hyperion Enterprise Performance ManagementSystem Installer, Fusion Edition by editing the installTool.properties file, located in thedirectory 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, andfatal exceptions.

Table 3 lists the installation log files with their contents and locations. It also provides notesabout using the logs.

Table 3 Installation Log Files

Name Contents Location Rotation

installTool-install.log Main log written by EPMSystem Installer to log useractivity

HYPERION_HOME/logs/install

Do not delete this log.

Provide this log to Technical Support whenreporting any issue with configuring EPMSystem products.

product-install.log

For example, hss-install.log for Shared Services

Indicates whether a productassembly installation fails.There is a log file for eachassembly.




16 Using EPM System Logs


installTool-install-stderr.log

and

installTool-install-stdout.log

Capture console normal anderror output.




EPM System ConfiguratorLogsYou can specify the logging level for EPM System Configurator by editing thelog4j.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, andfatal exceptions.

Table 4 lists EPM System Configurator logs with their contents and locations. It also providesinformation about using the logs.

Table 4 EPM System ConfiguratorLog Files


configtool.log Configuration taskoutput and warningmessages

HYPERION_HOME/logs/config


Provide this log to Technical Support when reportingany issue with configuring EPM System products.

configtool_err.log

Configuration errors HYPERION_HOME/logs/config



configtool_summary.log

Summary informationabout passed and failedtasks

HYPERION_HOME/logs/config



Application Server and Web Server LogsYou can also troubleshoot by reviewing logs written by application servers and Web servers usedwith EPM System products. See the vendor documentation for information about other logsspecific to the application server or Web server.

Application Server LogsEvery EPM System application that is auto-deployed to an application server using EPM SystemConfigurator generates logs for that application server.

EPM System ConfiguratorLogs 17

For each EPM System application service, error and console logs are written toHYPERION_HOME/logs/service. For all products and all application servers, except for OracleApplication 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 LogsThe 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 usinghttpd.conf in APACHE_HOME/conf/.

Foundation Services Logsl “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 LogsThis 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 APILog” on page 22.

Archive



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 thedatabase or while configuring auditing

Archive

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 datasources

Archive

SharedServices_Security_Client.log Information about the external authentication client

Note: In previous releases, HyperionCSS.log

Archive

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 generatesreplacement files.

Setting Log LevelsYou can specify the kinds of messages that are written to the logs, such as DEBUG, ERROR, orWARN.

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 applicationservers.

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 theserver 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 levelverbosity 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 editingstartOpenLDAP.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 processlogs.

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/results

For a resource, lists add, modify, and delete operations. (Thisoption 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 shellbackends

Displays index properties of each attribute of an object class.

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 OpenLDAPconfiguration).

Changing the Default Location of the Shared Services Security Log

Java

> To change the default location of the SharedServices_Security_client.log, add theJava system property Djava.io.tmpdir=LOG_PATH to all JVMs. This will change the temp filelocation 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 meansto pass the Java system property, -Djava.io.tmpdir=LOG_PATH, to the JVM that is used bythe 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 environmentvariable.

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 availableESS_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 thatthe 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 LogThe Oracle's Hyperion Shared Services Registry API log file, registry.log, records andarchives activity for the Shared Services Registry (the database used to store and reuseconfiguration information for most Shared Services Registry products). You can specify thelogging level for Shared Services Registry by editing the RegistryLogger.properties filein: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, andfatal 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 LogsTable 7 lists EPM Workspace log files with descriptions of their contents and recommendationsfor rotating the files.


Table 7 EPM Workspace Log Files


stdout_console_agent_configuration_name.log

For example, stdout_console_default.log

The stdout_console.log is generated regardlessof the operation being performed, and representsstandard output and standard errors (console output).Use this log to diagnose Core Services startup failures.Some errors captured by the application are loggedhere.

server_messages_BrowseServlet.log Log for EPM Workspace browsing servlet component,which browses the repository

server_messages_AdministrationServlet.log

Log for EPM Workspace administration servletcomponent, which administers the Reporting andAnalysis system

server_messages_PersonalPagesServlet.log Log for EPM Workspace personal pages servletcomponent (bookmarks and personal pagesadministration)

server_messages_iHTMLServlet.log Log for the iHTML servlet (logs thin client datarepresentation)

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

Log for the Analytic Bridge Service (bridges data toOracle's Hyperion® Interactive Reporting from otherEPM System products)

server_messages_AuthenticationService.log

Authentication Service information (user credentialsand group membership at login)

server_messages_AuthorizationService.log Authorization Service information (roles and theirassociations with operations, users, groups, and otherroles)

server_messages_CommonServices.log Entries for the Reporting and Analysis logging servicebefore it is operational

server_messages_DataAccessService.log Data Access Service information

server_messages_EventService.log Event Service information (system resource and jobmanagement)

server_messages_GSM.log Global Service Manager information (systemconfiguration and service monitoring)



server_messages_HarvesterService.log Impact Management Assessment Services (Harvester)information (published Interactive Reporting repositorydocument metadata)

Archive every 12hours. Containsvaluable auditingand debuggingdata.

server_messages_JobService.log Job Service information (Reporting and Analysis jobmanagement)

server_messages_LoggingService.log Log4j Service initialization information

server_messages_LSM.log Log for the Local Service Manager (LSM) service; LSMsprovide support for Interactive Reporting distributedservices infrastructure.

server_messages_PublisherService.log Publisher Service information (repositorycommunication for other LSC services and some Webapplication requests)

server_messages_RepositoryService.log Repository Service information (Reporting and Analysisdata storage repository)

server_messages_SessionManager.log Session Manager Service information (simultaneoususers and session timeout management)

server_messages_ServiceBroker.log Service Broker information (GSM and LSM clientrequest routing and RSCload balancing)

server_messages_TransformerService.log Impact Management Update Service (Transformer)information (Interactive Reporting document updates)


server_messages_UsageService.log Usage Service information (Interactive Reporting usagestatistics (such as the most used files, the mostselected MIME types)

admin_messages_CalendarManager.log Calendar Manager information (for job scheduling)

admin_messages.log Administration Utilities information

license_message_agent_configuration_name.log

For example, license_message_default.log

Contains licensing information

SharedServices_Security_Client.log Shared Services authentication information

server_messages_SearchIndexing.log Search Indexing and Query service (information aboutsearchable index and search queries)




server_messages_SearchKeywordProvider.log

Search Keyword Provider Service (registered parsers,parsing documents for keywords prior to indexing)


server_messages_SearchMonitor.log Search Monitoring Service (monitors Repository andtriggers (re)indexing on document changes)


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 byCompositeRollingAppender. Time interval log rotation is controlled by CompositeRollingAppender and a Java propertyin 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 LevelsLog 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 PerformanceManagement Workspace Administrator's Guide.

After changing log levels you do not need to restart the service, but a refresh of the logconfiguration in the Configuration and Monitoring Console (CMC) is needed for the changesto take effect.

Configuring Log Properties for TroubleshootingTo 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 otherconfiguration changes are made in Configuration and Monitoring Console (CMC). See“Configuring Log Properties for Troubleshooting” in the Oracle Enterprise PerformanceManagement Workspace Administrator's Guide for information on setting EPM Workspace loglevels.


Analyzing EPM Workspace Log FilesFor 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 LogsThe 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 page37.



agent.log Log file for the CMC Agent service, whichstarts named service configurations

HYPERION_HOME/logs/BIPlus/ Archive

agent_service.log Log file for the CMC Agent service, whichstarts named service configurations(Windows only)

HYPERION_HOME/common/workspacert/9.5.0.0/logs

cmcui.log Log file for the CMC UI Web applicationserver

HYPERION_HOME/common/workspacert/9.5.0.0/logs

Archive

Setting Log LevelsYou 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 needto restart the service for the changes to take effect.

Smart View LogsThe SmartViewLogs.log file contains Oracle Hyperion Smart View for Office, Fusion Editionerror messages. Archiving is recommended for the SmartViewLogs.log file.


Setting Log Levels and Routing Messages to a Log FileAll error, warning, and informational messages from the connected data source are displayedwhen 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 suppressall messages.

l Information–All messages, including warnings and errors (Recommended fordiagnosing 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 LogsThe following table lists Oracle Hyperion EPM Architect, Fusion Edition logs with their contentsand rotation recommendations.

Table 8 Performance Management Architect Log Files

Name Contents Rotation

epma.log Lifecycle Managementactivity

The maximum file size for this log is 4096KB. When the file reaches the @ maximum size,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 bythe Web server

The maximum file size for the log is 1024KB. Only error messages are written into this file.

awb.log Information written bythe Web server

The maximum file size for this log is 1024KB. When the file reaches the maximum size, itis saved and a new log file is started. The maximum number of saved log files is 5. Whenthe number exceeds 5, the oldest log file is deleted automatically.


DMEngine.log Data Synch Webapplication activity

The maximum file size for this log is 1024KB. When the file reaches the maximum size, itis saved and a new log file is started. The maximum number of saved log files is 5. Whenthe number exceeds 5, the oldest log file is deleted automatically.




Windows EventViewer

Dimension Serveractivity

The Windows Event Viewer can be configured to automatically delete old events as newevents 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 tothe Event Viewer, you cannot clear the log for Dimension Server independently of the others.

Transaction logs Transactions

Note: Viewtransaction logs fromthe Dimension Library

These are in the database. You can choose to archive the database rows or optionally purgethe rows.

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 LogsThe following sections contain information about Hyperion Calculation Manager logs.




calcmgrserver.log By default, logs any errorsand warnings as well basicconnection information, suchas the Dimension Server URL,the Planning Server URL for agiven application, and soforth. Includes LifecycleManagementactivity.

HYPERION_HOME/logs/calcmgr

The maximum file size for this is 1024KB. When the filereaches the maximum size, it is saved and a new log file isstarted. The maximum number of saved log files is 5. Whenthe number exceeds 5, the oldest log file is deletedautomatically.


calcmgrdeploy.log Business rules deploymentinformation log. Logsexceptions that occur whendeploying rules fromPerformance ManagementArchitect/CalculationManager into Planning.

HYPERION_HOME/logs/Planning

The log files can be rolled by file size. The number of rolledlog files and the file size to roll it to after can also bechanged by modifying the RollingFileAppenderproperties in the DEPLOYMENT_LOCATION/calcmgr/WEB-INF/conf/CalcMgrLog4j.properties file.


calcmgrexecution.log

Business rules executionexception log.




calcmgrlaunch.log Calculation Managerbusiness rules launchinformation log. The type ofinformation recorded in thislog is configurable in theCalcMgrLog4j.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 (forexample, 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 forCalculation Manager logs on Planning side.

Setting Logging Levels for Calculation ManagerTo change the logging level for the other three Calculation Manager logs, modify logging levelsand log4j settings in the log4j.properties and CalcMgrLog4j.properties files inDEPLOYMENT_LOCATION/calcmgr/WEB-INF/classes.

After changing the Calculation Manager log levels you must restart the Planning applicationserver for Calculation Manager logs on Planning side.

Essbase LogsThe following sections contain information about Essbase product family logs.

For a complete listing of Essbase logs, see Oracle Essbase Database Administrator's Guide. Forinformation about the transaction log file for Essbase backup and recovery, see Oracle HyperionEnterprise 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 LogsThe following sections contain information on Essbase log files.



Essbase.log Essbase Server activities and errors HYPERION_HOME/logs/essbase/app

Archive

(You must create a new logfile when you archive theold one.)

application_name.log

Essbase application activities and errors HYPERION_HOME/logs/essbase/app

Archive


dataload.err Data load and dimension build errors HYPERION_HOME/logs/essbase/app

Keep these logs forsupport calls.



dbname.atx, dbname.alg

Successfully completed spreadsheet updatetransactions

These are SSAUDIT log files; File name andlocation are specified through anessbase.cfg configuration setting. See“Monitoring Data, Applications, andDatabases” in theOracle Essbase DatabaseAdministrator's Guide and the EssbaseTechnical Reference.

Note: SSAUDIT log files are created onlyif SSAUDIT is activated in essbase.cfg.

HYPERION_HOME/logs/essbase/app

Archive


log0000x.xcp Information captured at the time of anabnormal termination

HYPERION_HOME/logs/essbase/app

Keep these logs forsupport calls.*

EssbasePlugin.log Log statements related to artifact listing HYPERION_HOME/logs/essbase/lcm

Archive

EssbasePlugin.log Log statements corresponding to artifactmigration

HYPERION_HOMEcommon/utilities/ LCM/9.5.0.0/logs

Archive

*See “Monitoring Data, Applications, and Databases” in the Oracle Essbase Database Administrator's Guide for information on exception logsand the actions you can perform on them, including overwriting or retaining existing logs.

Log Location for Additional Instances of EssbaseIf more than one instance of Essbase is installed on a machine, the log location is appended byInstanceID. For example, if you have a second instance of Essbase installed, and the instanceID is 2, the logs for that instance are located in HYPERION_HOME/logs/essbase_2/app. Todetermine the InstanceID, check the essbase.cfg file, located in HYPERION_HOME/products/Essbase/EssbaseServer/bin.

Setting Essbase Log LevelsBy 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.logand Essbase.log.

See “Monitoring Data, Applications, and Databases” in the Oracle Essbase DatabaseAdministrator's Guide and the Essbase Technical Reference for information aboutessbase.cfg settings.

Essbase Logs 31

Rotating Essbase LogsYou can clear Essbase and application logs at any time, or upon restarting the server orapplication. You must have administrator permissions to clear Essbase and application logs. Youshould back up log files before clearing them. See “Monitoring Data, Applications, andDatabases” in the Oracle Essbase Database Administrator's Guide.

By default, new exception logs are created when Essbase, an application, or a database shutsdown abnormally. Subsequent exception logs are numbered sequentially. For example, iflog00001.xcp exists, the next log is named log00002.xcp, and so on. You can change a settingin 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'sGuide, and the Essbase Technical Reference.

Administration Services LogsThe 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 LevelsThe 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 managedserver; for example, –DEAS_LOG_LEVEL=4000.

After changing log levels you must restart the Administration Services server for the log settingsto 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 LogsThe following sections contain information on Oracle Essbase Studio logs.



esbstudioserver.log Essbase Studioserver activity

Can be rotated or deleted. Contains information useful for troubleshooting bythe administrator. Depending on the settings you make in the server.properties file, records are automatically moved to a history copy, and canbe archived or deleted as appropriate. Logging level can be set by theadministrator.

cpld.log Essbase Studioclient activity

Cannot be rotated. Contains history of Essbase Studio client activity. Logginglevel cannot be set by the administrator. No configuration options available.

SharedServices_Client_Security.log

Essbase Studiosecurity information

Logging level cannot be set by the administrator. No configuration optionsavailable.

Setting Log LevelsThe 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 yourEssbase 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 LogsEssbase Studio rotates the server log file by creating log history files. Log history files are olderversions of the log file that are generated automatically when the size of the server log file reachesthe limit specified in the logger.limit parameter. The extension “.n” is automaticallyappended 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 thanthe size specified in the logger.limit parameter, the current log file and all log history filesare incrementally renamed, and a new current log file is created. When the number of log historyfiles reaches the limit set in the logger.count parameter, the oldest of the log history files isremoved to accommodate the new log file being created.

For example, by default, when the server log file reaches the 10 MB limit, the following happensautomatically:

esbstudioserver.log becomes esbstudioserver.log.1, esbstudioserver.log.1becomes esbstudioserver.log.2, esbstudioserver.log.2 becomesesbstudioserver.log.3, and so forth; and Essbase Studio Server creates the new current logfile, esbstudioserver.log.

Note: You can always manually delete old log files from the file system if they are no longerneeded.

You can change the default settings of server.log, logger.limit, and logger.count tomeet your specific requirements by adding these properties to the Essbase Studioserver.properties file. The properties are described in the Oracle Essbase Studio OnlineHelp.

ä 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 yourEssbase 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 limitproperty, 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 linefor 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 LogsThe 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 LevelsYou 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 betweenthese sizes.

For information about Integration Services startup switches, see the Oracle Essbase IntegrationServices 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 first1,000 records, which may include successfully loaded records and rejected records; and create hisdld.rul consisting of thenames 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 totake effect.

Provider Services LogsThe following sections contain information about Oracle Hyperion Provider Services logs.



apsserver.log

The log file location is configurable using the property name system.log.file.name in APS_HOME/bin/essbase.properties.

Provider Services activity Rolling log file. No manualarchive is needed.

server1.log Provider Services Webapplication activity

Archive

aps-install.log Installation information Archive

Setting Log LevelsYou can dynamically change the level of Provider Services logging. For example, if you switchprovider logging level from Information to Warning, the change takes effect immediately onProvider 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 filepath.

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 messageconsole window.


7 Under Tracing, select Enable Provider logging to enable tracing of XML request responses between theclient 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 changesto take effect.

Reporting and Analysis LogsThe following sections contain information about Reporting and Analysis logs. The logs forReporting 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 Servicewrites 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 OracleEnterprise Performance Management Workspace Administrator's Guide.

Note: CMC, Remote Service Configurator, and Calendar Manager log messages locally.

Configuring Log Properties for TroubleshootingTo 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 otherconfiguration changes are made in Configuration and Monitoring Console (CMC). See“Configuring Log Properties for Troubleshooting” in the Oracle Enterprise PerformanceManagement Workspace Administrator's Guide for information on configuring Reporting andAnalysis log levels.

Reporting and Analysis Logs 37

Note: Common service startup messages are logged to stdout_console_default.log andconfiguration_messages.log. Refer to those log files when diagnosing startupfailures.

Setting Log LevelsLog 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 PerformanceManagement Workspace Administrator's Guide.

Configuring Log RotationYou can roll and delete log files by time intervals or file size. By default, the system rolls logsevery 12 hours and deletes the oldest log file when the number of logs exceeds five. For moreinformation on configuring log rotation, see “Configuring Log Rotation” in the Oracle EnterprisePerformance Management Workspace Administrator's Guide.

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

Log File Names and Descriptionsl “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 LogsInteractive Reporting Log Service



server_messages_IRServiceHelper.log Interactive Reporting logging serviceinformation

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

0_default_irlog_UUID_stdout.log Standard output of irlog service including listof loaded classes

0_default_irlog_UUID_stderr.log Standard error of irlog service

Interactive Reporting Intelligence Service


PID_BIStartUp.log

BIStartUp.log

BIService startup information

server_messages_IntelligenceService.log Interactive Reporting Service, helpful in troubleshooting problemswith 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 withthe 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 LogsThe following sections contain information about Oracle Hyperion Financial Reporting, FusionEdition logs.



FRCommSrv.log Financial Reporting Communication Serverinformation

HYPERION_HOME/logs/BIPlus/

Automatic

FRReportSrv.log Activity from the Financial Reporting server,where reports are rendered


FRSchedSrv.log Batch scheduler activity HYPERION_HOME/logs/BIPlus/

FRScheduleBatch.log Activity from the Scheduler command lineinterface


FRWebApp.log Activity from the Financial Reporting WebApplication, where Web client pages aregenerated


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 infr.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. Thesystem 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 LogsThe following sections contain information about Oracle's Hyperion® SQR® ProductionReporting logs.



report_name.log

Output from SHOW and DISPLAY commands when -Ocommand line flag. Can be redirected to any file.

May contain report data. Choose to archive ordelete based on whether you want to keepreport data.

report_name.err

Error messages/warnings during compilation and programexecution when -E command line is used (can be redirected toany file).

Contains errors pertaining to the specifiedreport. Retain until errors are resolved.

sqr.log (Windows) Output from SHOW and DISPLAY commands and/orerror messages/warnings during compilation and programexecution when neither -E and -O command line flags areused.

May contain report data. Choose to archive ordelete based on whether you want to keepreport data.


You cannot set logging levels for Production Reporting.

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




WebAnalysis_log.date.txt Tomcat log for Web Analysis(for exceptions only)

HYPERION_HOME/deployments/Tomcat5/WebAnalysis/logs/

SystemOut.log SystemErr.logstartServer.log

WebSphere 6 Web Analysislogs

HYPERION_HOME/deployments/WebSphere6/profile/logs/WebAnalysis/

WebAnalysis.log WebLogic Server 9 log for WebAnalysis

HYPERION_HOME/deployments/WebLogic9/servers/WebAnalysis/logs/

server_messages_WebAnalyzer.log Web Analysis Web applicationlog


Setting Log Levels

ä To set log levels in server_messages_WebAnalysis.log:

1 Openlogging-settings.jar in DEPLOYMENT_LOCATION/WEB-INF/lib, whereDEPLOYMENT_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 LogsThe following sections contain information about Financial Performance ManagementApplications 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 LogsThe following sections contain information about Financial Management logs. For informationabout Performance Management Architect and Calculation Manager logs, see “FoundationServices Logs” on page 18.



HsvEventLog.log Financial Management activity (any errors with Financial Management server)

HFMLCMService.log Lifecycle Management activity

Setting Log LevelsYou cannot set log levels for Financial Management.

Planning LogsThe following sections contain information about Planning logs. For information aboutPerformance Management Architect and Calculation Manager logs, see “Foundation ServicesLogs” on page 18.

Financial Performance Management Applications Logs 43



Application Server logs Planning activity Oracle Application Server: ORACLE_HOME/opmn/logs/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

Archive

UserProvisionSync.log

Security refreshinformation, such asprovisioning or “user notfound” issues. Facilitatestroubleshooting ofsynchronization issuesbetween Planning andShared Services.

HYPERION_HOME/logs/Planning Can bedeleted

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 LogsThe following sections contain information about Business Rules log files.

Log Files Names and Descriptions


hbrclient.log Business Rules clientactivity

For all application servers: HYPERION_HOME/AnalyticAdministrationServices/console/bin

Archive



hbrserver.log Records generalinformation and errors onthe Business Rulesserver.

From Administration Services, written to:

HYPERION_HOME/logs/eas

From Planning, written to the location from which the Planning server isstarted.

Archive

hbrlaunch.log Includes informationregarding business rulenames and RTP values forlaunched rules.

From Administration Services, written to:

HYPERION_HOME/logs/eas

From Planning, written to the location from which the Planning server isstarted.

Archive

Setting Logging LevelsBy default, Business Rules records warning level messages in log.txt, but you can change thelevel 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, thenAdministration Services, and then Start Administration Services Console.

2 In Administration Services Login , enter the Administration Services server name and your logoncredentials. Click OK.

Note: If the Administration Services default port was changed , enter the port informationbefore 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 fromLog 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 theerror levels described in step 5 from the Log Level list.

7 Click Save.


Financial Performance Management Applications Logs 45

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



HPSWebReports.log Performance Scorecard application activity. Includes LifecycleManagement activity.

Archive for support call purposes

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

Setting Logging LevelsPerformance Scorecard uses log4j for logging. You can modify logging levels and log4j settingsfor 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 LogsThe following sections contain information about Oracle Hyperion Profitability and CostManagement, Fusion Edition logs.

Log Files Names and Descriptions


hpm.log Log file for all Profitability andCost Management messages.

Archive log files deemed important according to your document storage and retention policy.Should you decide to archive, please use MaxFileSize of 10 MB for rotation. No specificfrequency is needed, and it is enough to go with rotation based on size.


Setting Log LevelsYou can specify the kinds of messages that are written to the logs, such as DEBUG, ERROR, orWARN.

Modify log4j.properties to configure the log level settings for Oracle Hyperion Profitabilityand 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 LogsThe 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 LogsThe following sections contain information about Oracle Hyperion Financial Data QualityManagement, Fusion Edition logs.



tLogActivity table Information about FDM activities and audit related information. Archive. This log should be keptas part of the financial audittrail.

l tBatch

l tBatchContents

l tBatchInformation

Batch processing, informational, and error log entries Archive

username.err Information about FDM user errors.

Note: The main purpose of these logs is to assist in debugging customerissues.

Can be deleted

Windows Event Log Event log entries that are written by the Application Manager andLoadBalance Manager

Note: FDM Task Manager can also log scheduled task events (whenlogging 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.

Setting Logging LevelsYou cannot set logging levels for FDM.

ERP Integrator LogsThe following sections contain information about Oracle Hyperion Financial Data QualityManagement 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 erroras well as fatal messages. Similarly, Level 5 will include all messages.

Setting Logging LevelsOracle Hyperion Financial Data Quality Management ERP Integration Adapter for OracleApplications uses Oracle Data Integrator (ODI). For the ODI processes, the log folder is set bythe 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 LogsThe following sections contain information about Data Relationship Management logs.



Database installation logs;for example:

l oracle_install.

log

l mssql_install.log

Installation information

Note: One of these log files is generated during Data RelationshipManagement server installation, depending on the type of DataRelationship Management database being used.

Archive

Windows Application EventLog

Information written by the Data Relationship Management Server.Includes Data Relationship Management events, server messages,and errors.

Standard IT practices should befollowed in managing theapplication event log.

Import Log Information about the Import operation

Note: Optional log file that can be specified by the user.

Can be deleted when no longerneeded

Blender Log Information about the Blend operation

Note: Optional log file that can be specified by the user.


MDM_Connect.log Data Relationship Management Batch Client information (user canoverride the name and location)


Transaction History Transaction information written by the Data RelationshipManagement system and maintained in the Data RelationshipManagement repository database

Note: View Transaction History from the Data RelationshipManagement client. From the Main menu, select Tools and thenTransaction History.

As Data Relationship Managementversions are deleted, thecorresponding transactionalhistory is also deleted.

Setting Logging LevelsYou must have administrator privileges to set Data Relationship Management TransactionHistory logging levels. Set the TransactionLevel system preference to specify the action types tocapture 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 loggingout.

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 allbelow core action is performed, then properties are cleared from individual nodes. Theclearing 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 actionsare 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 whenthe node is deleted. When set to All, derived, default, inherited values are also trackedin the LossAction.

l AllowAsOf forces tracking of Core Actions.

Note: You cannot change the level of detail recorded in logs other than the transactionhistory. After changing log levels for the Transaction History you must restart theData Relationship Management Windows service.

Note: If the Loss Action is specified or if AllowAsOf is turned on, then Core Actions aretracked, even if not set in the TransactionLevels System Preference.


4General Tips

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 TroubleshootingThis section discusses issues that you might encounter when using the EPM System Installer.

WebLogic Server UpgradesBefore installing EPM System products, if you are upgrading from Oracle WebLogic Server 9.1to WebLogic Server 9.2.x, you must follow the BEA procedure to migrate applicationenvironments, 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 RequirementIf you use WebSphere and you are applying a maintenance release to go from EPM System11.1.1.x to the current release, or you are upgrading from EPM System Release 9.3.1 to the currentrelease, you must also upgrade WebSphere from version 6.1.0.x to 6.1.0.17.

Installation Type PanelYou might encounter the following issues on the Installation Type panel.

Installation Troubleshooting 51

http://edocs.bea.com/common/docs92/upgrade/upgrading9091.html


“New Installation” Option is Not AvailableIssue: If the New Installation option is not available, your machine might have an improperlydeleted previous version of EPM System products.

Solution: Search for the vpd.properties file on the machine and rename itvpd.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 AvailableIssue: If the Upgrade from a previous release option is not available on a machine that has aprevious release of a product installed, there may be a missing or corrupted vpd.propertiesfile.

Solution: Create an override file named upgradeproducts.xml and place it in theHYPERION_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 Workspacel workspaceWebApp

l workspaceService

Smart Viewl smartViewClient

l smartViewHveClient

52 General Tips


Performance Management Architectl epmaClient1

l epmaGenerator

l BPMAWebApp

l epmaDataSync

l epmaServices

Essbasel essbaseAddins

l essbaseClient32

l essbaseClient64

l essbaseService32

l essbaseService64

Administration Servicesl essbaseAdministrationConsole

l essbaseWebApp32

l essbaseWebApp64

Integration Servicesl essbaseIntegrationServiceClient32

l essbaseIntegrationServiceServer32

l essbaseIntegrationServiceServer64

Provider Servicesl essbaseWebApp232

l essbaseWebApp264

Oracle Hyperion Smart Search Command Line Utility essbaseWebApp3

Oracle's Hyperion® Interactive Reportingl irService

l imService

l irClient

l irClientDDS

Oracle's Hyperion® SQR® Production Reportingl prClientDeveloper

l prClientActivator

l prClientRemote

l prClientViewer

l prServiceDB2

l prServiceDDO

l prServiceInformix

l prServiceODBC

l prServiceOracle

l prServiceSybase

l prServiceTeradata



Financial Reportingl frClient

l frWebApp

l fr.server.reports

l fr.server.print

l fr.server.scheduler

Web Analysis waWebApp

Planningl offlinePlanningClient

l planningWebApp32

Financial Managementl hfmClientMostAll

l hfmClientSamples

l hfmAdmClient

l hfmWebapp

l hfmWebAppSview

l hfmService

Performance Scorecardl hpsWebAppReports

l hpsWebAppAlerter

l hpsWebAppETL

Reinstall Option is Not AvailableIssue: 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 AvailableIssue: 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 TroubleshootingYou might encounter the following issues on the Product Selection panel.

54 General Tips

Product Is Not AvailableIssue: 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 InstallationFiles” in the Oracle Hyperion Enterprise Performance Management System Installation andConfiguration Guide.

Incorrect Existing Version is DisplayedIssue: If you selected “Upgrade From a Previous Release,” you might see an incorrect existingversion displayed next to a product. This happens if EPM System Configurator cannot determinethe version number.

Solution: Disregard the version number and continue the upgrade.

Product Selection Combination InvalidIssue: 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 attemptto 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 StartIssue: The command prompt window flashes by and the installer doesn’t start. An error is loggedin 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 inthe path to the installer.

l Installer doesn’t recognize the assembly folder if it was renamed or if it didn't extractproperly. 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 FailureIssue: When the installation is nearly complete, the installation wizard stops, and this errormessage is displayed: Could not utilize start classcom.installshield.wizard.Wizard.

Solution: If no other error message is displayed on summary panel and the installation does notresume within five minutes, stop the installation and run the createInventory script inHYPERION_HOME/OPatch.

Welcome Panel IssueIssue:: Warning message about unsupported platform, not enough memory, or resolving hostname is displayed. The EPM System Installer checks whether your system has a supportedoperating system, meets minimum memory requirements to run the installation and attemptsto discover the computer host name.

Solution:: If you receive a memory warning or unsupported platform, be aware that yourinstallation could have problems. If the machine host name resolves to an IP address, you receivea warning. Oracle recommends that you resolve the DNS lookup issue before proceeding. If youdo not, rebooting the machine can cause your machine to resolve the host to a different IPaddress, probably breaking your installation that was working before.

Cannot Install After an UninstallIssue: 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 andset_hyphome_1.bat files.

6. Rename program files\common files\installshield\universal\common asprogram files\common files\installshield\universal\common_hyperion.

7. Restart the system.

56 General Tips

HP-UX IssueIssue: In an HP-UX environment, running epmsys_registry.sh without passing parametersdoes 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 TroubleshootingThis section discusses issues that you might encounter when upgrading EPM System products.

EPM System Products and WebLogic UpgradesBefore upgrading EPM System products, if you are upgrading from Oracle WebLogic Server 9.1to WebLogic Server 9.2.x, you must follow the BEA procedure to migrate applicationenvironments, 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 WebSphereIf you use WebSphere and you are applying a maintenance release to go from EPM System11.1.1.x to the current release, or you are upgrading from EPM System Release 9.3.1 to the currentrelease, you must also upgrade WebSphere from version 6.1.0.x to 6.1.0.17.

Configuration TipsThis section provides solutions to the most common configuration errors.

Changing Java Heap SizesYou can change Java heap sizes when using services to start and stop Web application servers inWindows 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 ConfigurationIssue: 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 tasksindividually for one product or component at a time.

Error on Configuration Task PanelIssue: You cannot see a component or products displayed on the Configuration Task Panel. Thiscan happen if there was an incomplete installation.

Solution: Review the installTool-install.log and product-install.log to see if anycomponent was not completely installed.

Database Configuration UnavailableIf the options in the Database Configuration dialog box are unavailable, make sure that you areconfiguring the system with the same user account that was used for the installation.

Failure Deploying to Application Server WithoutConfiguration ErrorsIssue: 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. Ifno 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. Seeyour application server documentation.

Resolving Connection Failures and Restarting ServicesTo restart services, see the “Starting and Stopping EPM System Products” chapter in the OracleHyperion Enterprise Performance Management System Installation and Configuration Guide.

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 errorthat requires you to restart the service.

SSL Communication IssueIssue: 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 SSLConfiguration Guide.

UNIX Specific TipsThis section provides solutions to installation and configuration errors that UNIX users mayencounter.

Apache Tomcat Startup FailureIssue: 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 cleanupis needed, run > ipcs -s | grep $USER

Solution: Force semaphores cleanup by having the user who runs Apache Tomcat issue thefollowing command:

for i in `ipcs -s | grep $USER | cut '-d ' -f2 -s`; do ipcrm sem $i;

done

Preparing JVM...Error Writing to This File ErrorIssue: 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 thecomputer and can safely remove other unused temporary files, do so.

SSL Communication Issue 59

60 General Tips

5Troubleshooting Shared

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 problemsyou encounter performing tasks.

Table 12 Diagnostic Tasks for Shared Services

Problem Troubleshoot Basic Tasks

You cannotlog in toSharedServices

User directoriesand SharedServices Webapplication

l Launch EPM System Diagnostics to ensure that the products' Web applications are started, as wellas OpenLDAP

l Ensure that CSSConfig contains up to date information on how to connect to user directories. IfCSSConfig cannot be exported using Oracle Hyperion Enterprise Performance ManagementSystem Lifecycle Management in the Shared Services Console, use the Shared Services RegistryEditor.

You cannotaccess otherregisteredEPM Systemproductsfrom SharedServicesapplicationgroups

User directoriesand productsWebapplications

l Check Shared_Services_Security.log in the product server for errors

l Launch EPM System Diagnostics to ensure that the product Web application is started, as well asOpenLDAP.

Understanding How and What to Troubleshoot 61

Problem Troubleshoot Basic Tasks

OpenLDAPservice orprocess willnot start

OpenLDAPl In a shell,

cd /d %HYPERION_HOME%\products\Foundation\openLDAP\var\openldap-data

%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 TasksPerform these initial tasks to better identify or resolve issues with Shared Services beforecontacting Support:

l Perform the steps in Chapter 2, “Troubleshooting Basics .”

l Review the appropriate log file to better diagnose the problem. This could include enablingdebugging 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 RegistryEditor utility (epmsys_registry.bat or epmsys_registry.sh) to modify the SharedServices Registry to change user directories information, or change your Shared Services serveror port. See the Oracle Hyperion Enterprise Performance Management System Installation andConfiguration Guide.

Caution! Because the Shared Services Registry is critical to running EPM System products, beextremely careful if you edit the Shared Services Registry. Oracle recommendsbacking up the registry before editing it. See the Oracle Hyperion EnterprisePerformance Management System Backup and Recovery Guide.

Generating a Report of the Contents of the Shared ServicesRegistryIssue: If you cannot access the Shared Services Lifecycle Management user interface and needto view the contents of the Shared Services Registry, you can use the Registry Editor utility togenerate an HTML report.

62 Troubleshooting Shared Services and Provisioning

Solution: Double-click (or execute without parameters) epmsys_registry.bat orepmsys_registry.sh, found in HYPERION_HOME/common/config/9.5.0.0, to generate areport called registry.html.

Editing the Shared Services Registry to Change UserDirectories Information, Shared Services Server or PortIf you cannot access the Shared Services Lifecycle Management user interface and need to makea change to user directories information or your Shared Services server or port, you can use theRegistry 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 asmyCSSConfig

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 ServicesThis section discusses an issue that can occur in an environment where Shared Services is set upfor failover on two physical servers, withShared Services Web application and Native Directoryrunning on the primary server and the standby server.

Issue: When you configure EPM System products, EPM System Configurator cannot registerthem 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 productinstallation 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 Servicesconfiguration, 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 Servicesregistration 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 samemachine as the primary Shared Services Web application.

User Directories and ProvisioningThis section identifies guidelines that should help you avoid typical user directory andprovisioning issues. It also provides solutions to common user provisioning problems. Forinformation about user directories and provisioning users, see the Oracle Hyperion EnterprisePerformance 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 userdirectories that store user credentials before provisioning EPM System applications. The settingsthat the LDAP Browser uses to connect to the user directory are identical to those that EPMSystem applications use to connect to the user directories. You can download a free LDAPBrowser.

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 samegeographical location as the server machines that host the user directories used in theprovisioning process.

l Find an optimal starting point for searches or create a custom group hierarchy.

Common ProblemsThese are the most common problems users encounter using Shared Services with external userdirectories:

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 userprovisioning, 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 AdministrationGuide

Modifying the Group URLHaving 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 SizeFor NTLM, MSAD, LDAP, Oracle Internet Directory, and SAP, the number of users and groupsa 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 onDirectory Configuration page. For Oracle Internet Directory, increase the default setting of 5000as required.

User Directories and Provisioning 65

OpenLDAP IssuesThis 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 ensuresynchronization

l Perform a hot backup of OpenLDAP using backup procedures in the Oracle HyperionEnterprise 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 OpenLDAPprocess from the task manager or while data is being written

For more information, see Oracle Hyperion Enterprise Performance Management System SecurityAdministration Guide

Resolving OpenLDAP Provider Startup Failure Due toCorruptionPerform these tasks if the LDAP provider you use with Shared Services does not start becauseof 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 CorruptionOpenLDAP becomes corrupt, because of sudden power loss, or because of a power loss whilethe service is running.

To recover:

Run recover.bat, located in the SharedServices\server\scripts folder, and pass in thebackup location as a parameter. For example, recover.bat c:\backupOpenLDAP


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

Loss of Shared Services ResponseWhen Shared Services is configured with WebLogic 9.2.1 and Oracle 11g, Shared Servicesprovisioning, Oracle Hyperion Enterprise Performance Management System LifecycleManagement, or EPM System auditing may stop responding. To resolve this issue, use theWebLogic Console to change the Stuck Thread Max Time value to 60000 and the Accept Backlogvalue to 50000 for Shared Services.

Startup and Access IssuesThis section provides solution to problems that you may experience starting Shared Services andlaunching other applications from Shared Services.

Resolving Shared Services Service or Process Startup FailureThe service may not run if OpenLDAP is corrupt or not running. If this is the case, run or restoreOpenLDAP. See “Fixing OpenLDAP Corruption” on page 66.

Resolving a Shared Services Startup Failure on theApplication ServerIf 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, validatethat database connectivity is successful, as well as checking OpenLDAP and externalproviders. These are all prerequisites for successful Web application startup.

3. Determine whether the default port 28080 is being used by another application by runningNETSTAT –an | findstr 0.0.0.0:28080. If you get (0.0.0.0:28080), change theShared 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 TimeOn the server, review SharedServices_Security.log.

If it contains errors relating to group caching, ensure that the group URL and filter are setproperly to accommodate group counts.

Resolving Problems Accessing Products from SharedServicesYou 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 andShared 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 numberof 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 userdirectories and Shared Services.

4. Start the OpenLDAP service or process.


Reconfiguring Product Registration in Shared Services to Usea 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 serveris 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 thefiles 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 ServicesIssue: 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 DatabaseIssue: You cannot successfully change an already configured Shared Services database directlyin 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 previouslyconfigured database”.

Resolving Product-Specific IssuesThis section identifies solutions to errors you may encounter using other Hyperion productswith Shared Services.

Oracle EssbaseThis section provides solutions to questions you may have using Essbase products with SharedServices.

Essbase This section provides solutions to common problems users have using Essbase with SharedServices.

Logging in After Externalizing a User

Perform the procedure if you externalize a user (essadmin for example) from Essbase to SharedServices, 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 asessbase.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 directoryand 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, performthese 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 preexternalizationstate.

5. Install and configure Shared Services

Administration Services and Integration Services This section provides solutions to some problems you may encounter using Shared Services withEssbase and Administration Services.

Retrieving Essbase Roles

l You receive the following error refreshing security to Shared Services from theAdministration 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 theEssbase logs folder.

Reporting and AnalysisThis section provides solutions to errors you may encounter configuring and using SharedServices with Reporting and Analysis.

Changing the DNS Name or the EPM Workspace ServerIf you change the DNS name of the EPM Workspace server, you may need to update the instancefiles manually. See “ Reconfiguring Product Registration in Shared Services to Use a Web Server”on page 69.

Resolving Product-Specific Issues 71

Financial Performance Management ApplicationsThis section provides solutions to errors you may encounter configuring and using SharedServices with Financial Management and Performance Scorecard.

Financial ManagementThis section provides solutions to errors you may encounter configuring and using SharedServices 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 thegroups returned by the search. If data broker property errors display,enableinteropjava logging. Exceeding 1,000 groups in the group URL causes a knownJRE 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 SharedServices using HTTP and WEBDAV protocol. Webdav may be blocked if you proxy requestsfrom IIS to interoperate with the Web application. If this is the case, ensure that the UrlScanIIS extension does not block propfind methods.

If you are using IIS on Windows 2003 sp1, add the IIS the UseBasicAuth registry key todword 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 theauthentication method is anonymous and that Windows integration authentication is notused.

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 ofthese 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 clickConfiguration on the Virtual Directory tab. In the new window, click Options and changethe 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 inthe FM Server and Web Configuration.

Resolving Inactive Secure URLs

If the secure URLs that you used to register applications become inactive and must be repeatedlyreregistered.

To resolve this issue, import the root ca certificates to the Java keystore cacerts in all Javainstallations in Hyperion/common.

Resolving an Internet Explorer Script Error to View User Security From the User ManagementConsole

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 ScorecardThis section provides solutions to errors you may encounter configuring and using PerformanceScorecard with Shared Services.

Required Oracle Database User Permissions

You installed Hyperion 9.3.0.1 using an Oracle Database. You assigned owner privileges to theOracle user ID that you currently use. Your security policy has blocked access to this user andyou 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 willgenerate an Essbase database of Performance Scorecard data, also assign permissions enablingthem to create indices and execute procedures.

Java.lang.NoSuchMethod Error

You receive this error if you install multiple products with Performance Scorecard and SharedServices but configure Performance Scorecard first. To resolve this issue, uninstall PerformanceScorecard, reinstall and configure the other products, and then install and configure OracleHyperion Performance Scorecard, Fusion Edition.

Resolving Product-Specific Issues 73


6Troubleshooting EPM

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 Recommendationsl 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 porton which the Web server is listening. See “Ports” in the Oracle Hyperion EnterprisePerformance Management System Installation Start Here.

l When you install EPM Workspace in a distributed environment, you must run the EPMSystem Configurator on every computer, ensuring that you are using the correct computernames.

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 registrationinformation.

Connection FailureIssue: Failure to connect to servers in a distributed environment.

Solution: Be sure that you run the EPM System Configurator on all the machines in theenvironment, using the correct machine names. If you point to a machine using an incorrectname, you cannot connect to that server.

Tips and Recommendations 75

Tomcat Startup Fails and EPM Workspace isUnavailableIssue: Apache Tomcat fails to start, and EPM Workspace is not available on port 19000. Thisoccurs 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 configurationand Shared Services registration for EPM Workspace.

Solution: Comment this line in httpd.conf:

#LoadModule auth_digest_module modules/mod_auth_digest.so

Logon FailureIssue: 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 OrderIssue: 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 theapplications.

EPM Workspace caches product information at startup time; it reads from the Oracle's HyperionShared Services Registry to determine which products are configured. This information isrefreshed only with a restart.

Note: In general, always start EPM Workspace last.

76 Troubleshooting EPM Workspace

Logging On When the EPM Workspace Agent is DownIssue: If a user attempts to log on while the EPM Workspace Agent is down, starting the agentagain is not sufficient. The user can log on, but the user's roles are not granted unless the servicesare 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 ConsoleIssue: From EPM Workspace, you cannot access the Configuration Management Console(CMC).

Solution: Since there is no Windows service for the new Configuration Management Webapplication, 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 CMCUI is documented in the “Starting and Stopping EPM System Products” chapter of the OracleHyperion Enterprise Performance Management System Installation and Configuration Guide.

Failure to Access ModulesIssue: 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'sHyperion® Web Analysis etc.), in the EPM System Configurator, run the Workspace WebServer 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

7Troubleshooting Essbase

Modules

In This Chapter

Essbase ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Administration Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Integration Services... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Essbase Studio... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Provider Services... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

EssbaseThe following sections identify common Essbase installation and configuration issues.

Essbase Server FailureSeveral issues can cause the Essbase server to fail to start after installation. The following tablelists error messages and issues and suggests solutions:

Error Message or Issue Solution

JVMMODULELOCATION has not been correctly setin essbase.cfg. You can modify this setting fromthe Administration Services console.

Set the environment variable. See the Oracle Hyperion Enterprise PerformanceManagement System Installation and Configuration Guide.

Error: Fatal Error: Essbase is alreadyloaded

The Essbase agent is already running.

Check to see if Essbase is running:

l Windows: Check the Windows Task Manager for the essbase.exe process.

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 onthe port setting you have specified for Essbase in essbase.cfg. For instructionson shutting down Essbase, see “Running Essbase Servers, Applications, andDatabases” in the Oracle Essbase Database Administrator's Guide.

Essbase 79

Error Message or Issue Solution

Error: Failed in GCInit()

This error can mean that the local directory inESSBASEPATH is not found or that files are missingfiles from the local directory.

Check ESSBASEPATH in hyperionenv.doc (UNIX) or setEssbaseEnv.cmd(Windows):

l Windows: In the command line, enter echo ESSBASEPATH.

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 Installationand Configuration Guide.

Error: ESSBASE: not found

This can mean that startEssbase.cmd(Windows) or startEssbase.sh (UNIX) is not inthe environment path.

Define ARBORPATH.

If ARBORPATH is already defined, then add it the path:

l Windows: Add %ARBORPATH%\bin

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 inaccessiblefiles may be displayed.

Connection ProblemsIssue: You cannot establish an Essbase client-server connection.

Solution: Use the PING command on the server to check that the server is running and visibleto the client computer.

l If the PING command is successful but the TELNET command is not, there might be aproblem with the inet daemon.

l If the PING command is unsuccessful on the server, you might have a routing or hardwareproblem.

Startup ProblemIssue: 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 Essbaseruns.

Installation on Different UNIX SystemsIssue: You cannot install Essbase simultaneously on different UNIX systems.

When you run EPM System Installer on different UNIX systems at the same time, EPM SystemInstaller 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 usesInstallShield, a third-party tool, and an InstallShield limitation causes this conflict.

Solution: Complete an Essbase installation on one UNIX system before starting an installationwith the same user on another UNIX system.

Administration ServicesThe following sections describe common Administration Services issues.

Problems Assigning FiltersIssue: You experience problems when assigning Essbase filters for an application using theShared Services User Management Console.

Solution: Register the application with Shared Services using the Administration ServicesConsole (right-click the application and select Register). Then try reassigning the filter in Oracle'sHyperion® Shared Services Console.

Integration ServicesThis section describes common Integration Services issues and solutions.

Connection Failure to OLAP Metadata Catalog or ExternalData SourceIssue: 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 sameuser 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 cannotaccess the tables in OLAP Metadata Catalog using a different user name unless you createan alias for the user name (for Microsoft SQL Server) or synonyms for the tables (forIBM DB2 and Oracle).

m Does the user name you used have the correct privileges to access both OLAP MetadataCatalog and the data source at the database level?

l Ensure that all of the required components are up and running. The following componentsare 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 datasources on the Integration Server computer.

Essbase StudioIssue: 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 fileis in HYPERION_HOME/products/Essbase/EssbaseStudio/Server. For informationabout 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 towork 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 ServicesThis 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 ofconcurrent users.

Solution: Increase application server memory using the JAVA_OPTS command in the applicationserver 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 setJAVA_OPTIONS default value of -Xms32M to these two values respectively -Xms512M -Xmx512M.

Load Balancing Problems with WebLogic through ApacheIssue: In Provider Services, Load Balancing with WebLogic through Apache might not work. Inthis situation, when you apply one of the URLs through Internet Explorer, it will fail to returnthe 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

8Troubleshooting FinancialPerformance 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 withexternal authentication, see Chapter 5, “Troubleshooting Shared Services andProvisioning .” For information about error logs, see Chapter 3, “Using EPM SystemLogs.”

Planning AccessThis section discusses access issues you might encounter with Planning.

Failure Accessing Planning through EPM WorkspaceIssue: 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 theWeb server listen port; for example, 19000 if using the Apache instance configured withReporting and Analysis.

2. If step 1 does not work, verify that you have configured the EPM Workspace proxy serverplug-in. If it is configured, test whether you can access Planning directly. See “FailureAccessing 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 saysthe module could not be loaded, you must run EPM System Configurator and reregisterPlanning with Shared Services.

Common Planning Issues 83

Failure Accessing Planning DirectlyIssue: You cannot access Planning through the EPM Workspace, and need to access Planningdirectly.

Solution: Try this URL: http://hostname:8300/HyperionPlanning/LogOn.jsp. If thisdoes not work, Planning did not install correctly. Check the Planning log in HYPERION_HOME\logs\.

Upgrade IssuesThis section discusses upgrade issues you might encounter with Planning.

Software CompatibilityIssue: You must ensure that the new release of Planning is compatible with the release of SharedServices that you are using.

Solution: To check compatibility, see the “Release Compatibility” chapter of HyperionInstallation 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 WorkspaceIf you do not see the Planning applications in EPM Workspace after an upgrade from theprevious release, ensure the applications are reregistered with Shared Services from the ClassicWizard for classic Planning applications and from Performance Management Architectfor thePlanning applications in Performance Management Architect.

Folder StructureThe 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 EPMWorkspace by selecting Tools, then Install, then Smart View, or you can use the EPMSystem Installer.

84 Troubleshooting Financial Performance Management Applications

Using Planning with Administration ServicesIssue: 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 IssuesIssue: 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. Hyperionrecommends that you work with a consultant to assess your environment.

Multibyte CharactersIssue: Multibyte characters do not show up in reports.

Solution: Ensure that Unicode or Albany fonts are present in the Java Runtime Environmentused by your J2EE container or application server. If they are not, copy them from the fontsfolder that has the Albany fonts laid out by Oracle Hyperion Enterprise PerformanceManagement System Installer, Fusion Edition to the fonts folder of the Java RuntimeEnvironment used by your J2EE container or application server. Examples of fonts folderlocations:

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 withexternal authentication, see Chapter 5, “Troubleshooting Shared Services andProvisioning .” For information about error logs, see Chapter 3, “Using EPM SystemLogs.”

Common Financial Management Issues 85

Accessing Financial ManagementThis section discusses access issues you might encounter with Financial Management.

Failure Accessing Financial Management Through EPM WorkspaceIssue: 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 hostname of the machine running the EPM Workspace Web server, webport is the port for theWeb server (by default, 19000), hfmserver is the host name of the machine running theFinancial Management Web component, and hfmport is the port for the Web server usedby Financial Management (by default, 80):

URL ExpectedResult

What to Check if the Actual Result is Different

http://webserver:webport/workspace/

EPMWorkspacesplash screenis displayed,and a newbrowserwindow openswith the logonpage.

l EPM Workspace Web server is running on the specified port.

l EPM Workspace Web application is running.

l Web server configuration files point to correct host name and port for theEPM Workspace Web application server.

http://webserver:webport/hfm/

A page isdisplayed thatsays only“hfm.”

l The Financial Management Web server is running.

l Web server configuration files point to the correct host name and port forthe Financial Management Web server.

http://hfmserver:hfmport/hfm/

A page isdisplayed thatsays only“hfm.”

The Financial Management Web server is running.

For detailed instructions on configuring the Web server, see the Oracle Hyperion EnterprisePerformance Management System Manual Deployment Guide.

2. If step 1 does not work, verify that you have configured the EPM Workspace proxy serverplug-in. If it is configured, test whether you can access Financial Management directly.

Failure Logging on to Financial ManagementIssue: You cannot log on to Financial Management because there might be a security accessissue.

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 orWeb 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 IISIssue: While using Financial Management, you get a security access error message involving anASP 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 enableanonymous access.

Connection TroubleshootingThese are some common connection issues for Financial Management.

Connection to Financial Management FailsSolution: If the DCOM launching user is set to a local machine account, domain users cannotlog on to some modules. For example, if a user logs on to a workstation with a user ID on DomainA, and logs on to Financial Management with a user ID on Domain B (or any domain thatDomain B can access), when the user attempts to connect to a Financial Management server onDomain 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) toDomain A (Financial Management Client). This method is recommended.

l Set the DCOM Default Authentication Level to None on the client. However, note that byturning off the DCOM authentication on the client, DCOM authentication is turned off forall DCOM applications on the client.

Installation Fails after Computer RestartSolution: 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 FailsSolution: Ensure that the database server name, user name, password, and database name arecorrect 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 databaseclient.

Connection to SQL Server Fails Issue: You receive the error message“SQL Server: Test connection failed becauseof 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 Serverauthentication. EPM System recommends using SQL Server authentication. See “VerifyingMicrosoft SQL Server Authentication Settings” on page 89.

l The system may be using the Microsoft SQL Server default setting to connect to the databaseusing 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 enteredby 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 InstallationIssue: 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 FailIssue: 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 andResponse Buffer Size settings for IIS.

l If you are using Classic Administration and receive a “Proxy Error”, increase the Workspacetimeout setting.


Sticky Server Attempts to Redirect UserIssue: 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 resolveit:

l Add this registry setting to each Web Server and Financial Management Win32 clientmachine:

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 areenabled on all servers, and the login audit policy is set to both Success and Failure.

Common Performance Management Architect IssuesThis section discusses issues you might encounter with Performance Management Architectinstallation and configuration.

Installation FailureIssue: Performance Management Architect Installation failed.

Solution: This could be the result of a Microsoft .NET Framework 2.0 error during its automaticinstallation in Performance Management Architect. Install Microsoft .NET Framework 2.0manually, 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 EnterprisePerformance Management System Installation and Configuration Guide.

Failure Deploying to WebSphere after UpgradeIssue: After you apply a maintenance release or upgrade to Oracle Hyperion EnterprisePerformance Management System Release 11.1.1.2, Performance Management Architect Webdeployment 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 WorkspaceIssue: 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 orif you click OK after attempting to access http://server:288/awb and receiving this errormessage: Module not found:awb.appcontainer

This issue can occur because the Dimension Server is not running. It can also result from amissing user privilege in an Oracle database.

Solutions: .

l If the Dimension Server is not running, start the Process Manager Service, which startsDimension Server and related services, and then retry the connection.

l Assign the CREATE VIEW user privilege for the Oracle database. See “Using an OracleDatabase” in Oracle Hyperion Enterprise Performance Management System Installation StartHere.

Accessing Performance Management ArchitectThis section discusses access issues you might encounter with Performance ManagementArchitect.

Performance Management Architect Logon FailsIssue: 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 areset 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 InformationServices Manager.

l Run inetmgr.

2 In the left panel, select Web Service Extensions. In the right panel, note whether ASP.NET 2.0.50727is 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 usePerformance Management Architect. See “Shared Services-Global Roles” in the Oracle HyperionEnterprise Performance Management System Security Administration Guide.

Failure Logging on to EPM WorkspaceSolution: Ensure that you have followed the installation and configuration instructions for EPMWorkspace in the Oracle Hyperion Enterprise Performance Management System Installation andConfiguration Guide.

Failure Starting the Process Manager ServiceIssue: 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 PerformanceManagement Architect.

l Check whether you have changed the Shared Services admin user or password. If so, launchthe Oracle's Hyperion Enterprise Performance Management System Configurator and runthe 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 ArchitectVerify these conditions:

l The Shared Services server is started.

For instructions on starting the Shared Services server, see the Oracle Hyperion EnterprisePerformance 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 Webserver machine host name and port is the Web server listen port; for example, 19000 forthe Apache instance configured with Oracle's Hyperion Reporting and Analysis.


Failure Accessing Performance Management ArchitectDimension or Application LibraryIf you cannot access a Performance Management Architect task, verify that you can access eachcomponent separately to locate the source of the communication error.

Failure Displaying or Opening the Dimension LibraryIssue: You cannot see the Dimension Library in Performance Management Architect.

Solution: Ensure that you have the correct Performance Management Architect roles. You musthave the Dimension Editor and Application Creator security roles to access the DimensionLibrary. See “Shared Services-Global Roles” in the Oracle Hyperion Enterprise PerformanceManagement System Security Administration Guide. After you are assigned the Dimension Editorrole, 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 ErrorsPossible 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 EPMWorkspace. Reconfigure Oracle Enterprise Performance Management Workspace, FusionEdition.

4. If this step does not work (error is 404), then the Performance Management Architect WebServer is not started.


Performance Management Architect Dimension Server ErrorsPossible 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 seeif anything was logged by ASP.NET, IIS, or DCOM, and fix the errors. A possible cause isincorrect privileges for the user for the TEMP directory.

l Check the Event Logs from sources starting with HyS9EPMA. Possible causes arecommunication errors with Shared Services or the database.

l The ASPNET user may not have access to certain folders. If the Event Log displays anysecurity-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 DimensionServer Web Services Possible Solutions:

l In the logs, if subcode is 2, and Win32 code is 1260, the problem is related to Web ServiceExtensions. In IIS, Web Service Extensions, ensure that the ASP.NET 2.0.50727 Web ServiceExtension 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 DimensionServerFrom the Control Panel, select Administrative Tools and then Services, and start World WideWeb Publishing Service, if it is not already started.

Performance Management Architect Services Startup FailureSolution: Start the Performance Management Architect Process Manager service if it is notalready 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 ArchitectIssue: You experience performance issues using an IBM DB2 database with Oracle HyperionEPM Architect, Fusion Edition.

Solution: Implement the settings described in the Oracle Hyperion Enterprise PerformanceManagement System Installation and Configuration Guide.



9Troubleshooting Data

Management

In This Chapter

Common FDM Issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Common Data Relationship Management Issues... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Common FDM IssuesThis section contains installation and configuration issues you may encounter andtroubleshooting tips for FDM.

Configuration Issues with Financial ManagementIssue: 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 Managementcluster that is registered on the FDM application servers. In the profile the setting for the targetsystem server or cluster must exactly match what you set up for Oracle Hyperion FinancialManagement, Fusion Edition, or they cannot communicate with each other.

Oracle Client / Provider Cannot Connect to DatabaseIssue: You receive this error message: ORA-12154: TNS; could not resolve servicename.

Solution: Correct outstanding Oracle issues, and ensure that you can resolve the Oracle ServiceName in tnsnames.ora.

Database User ID or Password RequiredIssue: You receive this error message when you log on to FDM: ORA-12154: TNS; couldnot resolve service name.

Solution: Follow these steps:.

1. Verify that the machine can communicate with the database server by creating: a UDL fileand 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 serverand any server accessing Oracle Hyperion Financial Data Quality Management, FusionEdition through the Workbench Client.

Cannot Authenticate UserIssue: 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 applicationmetadata.

Cannot Perform Bulk InsertIssue: 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 accountis local, change it to domain and give the user read share permissions and Read NTFS to theapplication folder \\servername\shared foldername\application foldername.

2. Launch SQL Server Enterprise Manager, and ensure that the user who created the databasehas been granted the Bulk Insert Admin role.

Active-X Component Cannot Create ObjectIssue: When logging on to Workbench, you receive an error message saying that the ActiveXcomponent cannot create an object.

Solution: Ensure that the user who is launching the workbench as change permissions to theFDM application path, \\servername\fdmshare\fdmappname

98 Troubleshooting Data Management

Common Data Relationship Management IssuesThis section contains installation and configuration issues you may encounter andtroubleshooting tips for Data Relationship Management.

Reviewing Readme IssuesReview these topics in the Data Relationship Management Readme to ensure that you installand configure properly:

l Using Shared Services via SSL

l Microsoft .NET

l Upgrade May Get Error after Reboot

Open File FailedIssue: 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 connectingfrom an XP SP3 machine) mstsc.exe /v servername -admin /f.

Access is DeniedIssue: 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 enteredon the Windows COM+ Logon dialog box must be entered correctly.

Server Unable to Process RequestsIssue: You receive the “Server was Unable to Process Request” error message.

Solution: For successful connectivity to the Data Relationship Management Web gateway, eachuser must have write access to the Windows/Temp directory on the machine where the clientapplication runs. Check that users have write access.

Configuration IssueIssue: Receive error message — “Cannot configure the system. Please check the configuration”

Solution: Ensure the hostname field on the Common Security Services page of the HyperionData Relationship Management console contains the correct name of the server where CSS isrunning.

Common Data Relationship Management Issues 99

Unable to Create JVMError: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 RootIssue: Event log contains an “Invalid Classpath root” error.

Solution: Reboot the server.

Server Startup FailureIssue: 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 startconfirms that the issue is related to CSS.

l Check the Event Log for error messages.

Error Message During UpgradeIssue: This error message is displayed during an upgrade: “Service Oracle Hyperion DataRelationship Management” failed to install with error: “System Error. Code: 1073. The specifiedservice already exists.”

Solution: Ignore the message, and click OK to complete the upgrade.

100 Troubleshooting Data Management

Index

Aabout troubleshooting, 9access

Architect, 91Architect Dimension Server WebServices, 94denied, Data Relationship Management, 99Financial Management applications, 86Planning, 83, 84Planning from Workspace, 83products from Shared Services, 68Reporting and Analysis modules, 77

Apache logs, 18Shared Services Registry API logs, 22application server

logs, 17startup failure, Shared Services, 67

application server deploymentfailure without configuration errors, 58

Architectaccessing Dimension library or Application library,

93accessing server Webservices, 94displaying Dimensions Library, 93displaying tasks, 92errors on server, 94IIS startup on Architect Dimension Server, 94installation failure, 90logon, 91services startup failure, 94

auditingloss of response, 67

BBusiness Rules logs, 44

CCalculation Manager

logs, 28multibyte characters in reports, 85

cannot authenticate user, Financial DataManagement, 98

cannot connect to Oracle database, Financial DataManagement, 97

cannot perform bulk insert, Financial DataManagement, 98

common issuesArchitect, 90Data Relationship Management, 99Financial Data Management, 97Financial Management, 85Planning, 83user directories and Shared Services, 64

common log location, 15configtool.log, 13configtool_err.log, 13configuration

Data Relationship Management, 99error log, 13exceptions, logged, 13Financial Data Management, 97general tips, 57validation, 12

Configuration and Monitoring Console logs, 26connection failure

Essbase client-server, 80Financial Management, 87general, resolving, 58OLAP Metadata Catalog or external data source,

81, 88Reporting and Analysis, 75

corruption, OpenLDAP, 66CSSConfig, 64

A B C D E F H I J K L M O P R S T U V W Z

Index 101

DData Relationship Management

access denied, 99common issues, 99configuration issues, 99invalid classpath root, 100logs, 47, 49readme issues, 99server startup failure, 100unable to create JVM, 100user rights issues on client machine, 99

DB2, use with Performance Management Architect,95

deploymentfailure without configuration errors, 58out of memory error, 58

documentation, 10

EEPM auditing

loss of response, 67EPM System Configurator

logs, 17EPM System product registration, with Shared

Services, 63EPM Workspace

logs, analyzing, 26logs, configuring, 25

ERPilogs, 48

error messagesapplication server deployment

out of memory, 58Essbase, 70Essbase Administration Services, 71Financial Data Management, 97Financial Management, 72JVM on UNIX, 59Performance Scorecard, 73Provider Services, out-of-memory, 82

Essbaselogs, 30server startup failure, 79server-client connection, 80troubleshooting, 79use with Shared Services, 70

Essbase Administration Services

filters, assigning, 81logs, 32refreshing security to Shared Services, 71troubleshooting, 81use with Planning, 85with Shared Services, 71

Essbase Integration Serviceslogs, 35OLAP or data source connection failure, 81

Essbase logs, 30Essbase Provider Services

load balancing with WebLogic and Apache, 82out-of-memory errors, 82

external user directories, 64

Ffailure

accessing Financial Management from Workspace,86

Apache Tomcat, startup, 59application server deployment, 58Architect Dimensions Library, displaying, 93Architect Services, 94Architect tasks, displaying, 92connection to OLAP Metadata Catalog or data

source, 81Data Relationship Management server startup,

100Essbase server, 79IIS startup on Architect Dimension Server, 94login, Financial Management, 86login, Workspace, 92OpenLDAP, startup, 66Planning, accessing directly, 84Planning, accessing from Workspace, 83Process Manager Service, starting, 92Reporting and Analysis modules, accessing, 77Reporting and Analysis, connection in distributed

environment, 75Shared Services service or process startup, 67Shared Services startup, application server, 67

Financial Data Managementcannot perform bulk insert, 98common issues, 97configuration issues, 97logs, 47Oracle/Client provider connection, 97


102 Index

user authentication, 98Financial Management

access from Workspace, 86accessing, 86common issues, 85connection failure, 87error messages, 72installation failure, 87large data or file loads, 89logon failure, 86logs, 43rights for installation, 89SQL Server connection failure, 88use with Shared Services, troubleshooting, 72

Financial Performance Management applicationsArchitect, accessing Dimension library or

Application library, 93common Architect issues, 90common Financial Management issues, 85DB2 performance settings, 95establishing the SQL Server connection using TCP/

IP, 88performance issues, 85Planning with Administration Services, 85Planning, access issues, 83troubleshooting connection issues, 87upgrade issues, 84

Financial Performance Management Applicationslogs, 43

Financial Reportinglogs, 40

HHP-UX issue, 57

Iinstallation

Architect, failure, 90Financial Management, failure, 87logs, 16rights for Financial Management, 89validation, 12

installation documentation, 10Installation Start Here, 11invalid classpath root, Data Relationship

Management, 100

JJVM error, UNIX, 59

Kknowledge base, My Oracle Support (MetaLink 3),

13

LLifecycle Management

loss of response, 67login

Architect, 91Financial Management, 86Shared Services, improving performance, 64Workspace, 92

logsEPM System Configurator, 17, 18, 28Apache, 18application server, 17Business Rules, 44common location, 15configuration, 13Configuration and Monitoring Console, 26Data Relationship Management, 47, 49ERPi, 48Essbase, 30Essbase Administration Services, 32Essbase Integration Services, 35file size, 15Financial Data Management, 47Financial Management, 43Financial Performance Management Applications,

43Financial Reporting, 40installation, 16Oracle Application Server, 18overview, 13Performance Management Architect, 27Performance Scorecard, 46Planning, 43Production Reporting, 41Profitability and Cost Management, 46Provider Services, 36Reporting and Analysis, 37Shared Services, 18Smart View, 26


Index 103

system performance, 15Web Analysis, 41Web server, 18WebLogic, 18WebSphere, 18

MMetaLink 3, 13Multibyte characters

displaying in reports, 85My Oracle Support, 13

OOpenLDAP

common issues, 66corruption, 66corruption, resolving without backup, 71log levels, 20startup commands, 20startup failure with Shared Services, 66tips, 66

Oracle Application Server logs, 18

Pperformance issues

logs, 15Performance Management Architect

accessing, 91common issues, 90logs, 27

Performance Scorecardlogs, 46use with Shared Services, 73

Planningaccessing from Workspace, 83common issues, 83direct access, 84directory structure, 84logs, 43multibyte characters in reports, 85upgrade issues, 84with Essbase Administration Services, 85

portconflicts avoiding, 12defaults for all products, 11

prerequisites, 9

configuration, validation, 12Installation Start Here, reviewing, 11installation, validation, 12logs, reviewing, 13port, avoiding, 12readme, reviewing, 12release compatibility, validating, 11startup dependencies, reviewing, 12system requirements, satisfying, 11

product registration, with Shared Services, 63Production Reporting logs, 41Profitability and Cost Management

logs, 46Provider Services

logs, 36provisioning

best practices, 64using Shared Services, 64

Rregistry.html file, missing, 57release compatibility, 11Reporting and Analysis

connection failure, 75logs, 37logs, analyzing, 38logs, configuring, 37module access failure, 77tips, 75use with Shared Services, 71

restarting services, 58

Ssecurity log, changing default location, 21server startup failure, Data Relationship Management,

100services

Architect Process Manager, startup, 92Architect startup failure, 94Shared Services startup failure, 67start and restart, 58Windows, verifying, 58

Shared Servicesapplication server startup failure, 67common problems, 61EPM System product registration, 63


104 Index

external user directories, 64failure accessing products from, 68load performance, increasing, 65login performance, improving, 64logs, 18loss of response, 67Registry Editor, 62startup failure, 67troubleshooting, 61troubleshooting utility, 62use with Reporting and Analysis , 71user provisioning best practices, 64user provisioning, troubleshooting, 64using with Performance Scorecard, 73using with Essbase, 70using with Financial Management, 72using with Integration and Administration Services,

71using with Workspace, 71

Smart Viewinstalling, 84

Smart View logs, 26SQL Server, establishing a connection using TCP/IP,

88starting services, 58startup

OpenLDAP commands, 20startup dependencies, 12startup failure

Architect services, 94IIS on Architect Dimension Server, 94OpenLDAP, 66Shared Services, 67Tomcat on UNIX, 59

support, accessing, 13system requirements, 11

Ttechnical support, 13Tomcat

logs, 18Tomcat, launching on UNIX, 59

Uunable to create JVM, Data Relationship

Management, 100

UNIXJVM error, 59starting Tomcat, 59

upgradingFinancial Performance Management applications,

84user authentication, Financial Data Management, 98user directories

using with Shared Services, 64user provisioning, 61

best practices, 64troubleshooting, 61, 64

Vvalidation, installation and configuration, 12

WWeb Analysis

logs, 41Web server

Reconfiguring product registration, to use Webserver, 69

Web server logs, 18WebLogic

load balancing, Essbase Provider Services andApache, 82

WebLogic, logs, 18WebSphere, logs, 18Workspace

accessing Financial Management from, 86accessing Planning from, 83changing Server DNS name, 71logon security rights, 92

Zzip file, logs, 16


Index 105


106 Index