Hsys9 Install Config Troubleshoot

H Y P E R I O N

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

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

Hyperion Installation and Configuration Troubleshooting Guide, 9.3.1

Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved.

Authors: Emily Hamer, Aline Goetz, and Dori Woodhouse

The Programs (which include both the software and documentation) contain proprietary information; they are providedunder a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, andother intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, exceptto the extent required to obtain interoperability with other independently created software or as specified by law, isprohibited.

The information contained in this document is subject to change without notice. If you find any problems in thedocumentation, please report them to us in writing. This document is not warranted to be error-free. Except as may beexpressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced ortransmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of theUnited States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered toU.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to theapplicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication,disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subjectto the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additionalrights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerousapplications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measuresto ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for anydamages caused by such use of the Programs.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of theirrespective owners.

The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle isnot responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated withthe use of such content. If you choose to purchase any products or services from a third party, the relationship is directlybetween you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b)fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warrantyobligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that youmay incur from dealing with any third party.

Contents

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Assumed Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

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

Reviewing the Installation Start Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Meeting System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Checking Release Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Avoiding Port Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Reviewing Startup Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Reviewing the Readme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Using Product Installation Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Validating the Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Using Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Using My Oracle Support (MetaLink 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Using Shared Services Troubleshooting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Additional Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Accessing Technical Support Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 3. Validating Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Performing Common Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Foundation Services Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Reporting and Analysis Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Essbase Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Performance Management Architect Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Planning Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Financial Management Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Performance Scorecard Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Strategic Finance Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Data Relationship Management Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

FDM Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Contents iii

Chapter 4. Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Common Log File Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Log File Size and System Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installation Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Hyperion Configuration Utility Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Log File Names and Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Setting Log Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Shared Services Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

A table lists and describes Shared Services logs.. Log File Names and Descriptions . . . . 21

Setting Log Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Smart View Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

File Names and Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Setting Log Levels and Routing Messages to a Log File . . . . . . . . . . . . . . . . . . . . . . . . 23

Essbase – System 9 Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Essbase Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Administration Services Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Integration Services Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Reporting and Analysis Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Reporting and Analysis Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Financial Reporting Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

SQR Production Reporting Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Interactive Reporting Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Web Analysis Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Financial Performance Management Applications Logs . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Financial Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Performance Management Architect Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Planning Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Business Rules Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Performance Scorecard Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Strategic Finance Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Data Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Data Integration Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Translation Manager Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

FDM Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Data Relationship Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Application Server and Web Server Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Application Server Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Web Server Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

iv Contents

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

Understanding How and What to Troubleshoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Preliminary Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Troubleshooting Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

CSS Spy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Installation, Configuration, and Deployment Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Manually Creating Database Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Installing Components on Multiple Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Resolving Incorrect JRE Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Dedicating Shared Services Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Resolving Login Page Error on the Oracle 10.1.2.0.2 Application Server . . . . . . . . . . . 50

Resolving a File or Folder Permissions Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Upgraded Products Registered with Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . 50

Using Shared Services Upgrades With Other Upgrades . . . . . . . . . . . . . . . . . . . . . . . 50

User Directories and Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Provisioning Basics and Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Common Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

OpenLDAP Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Avoiding OpenLDAP Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Causes of OpenLDAP Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Using CSS.XML to Resolve Connection Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Startup and Access Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Resolving Shared Services Service or Process Startup Failure . . . . . . . . . . . . . . . . . . . 55

Decreasing the Login Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Resolving Problems Accessing Products from Shared Services . . . . . . . . . . . . . . . . . . 55

Logging in Using the Default Admin Username . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Logging in to the User Management Console Using a Proxy Server . . . . . . . . . . . . . . 56

Resolving a Shared Services Startup Failure on the Application Server . . . . . . . . . . . . 56

Resolving Product-Specific Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Essbase — System 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Applications+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 6. General Tips for all Hyperion Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Resolving Connection Failures and Restarting Services . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Starting and Restarting Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Verifying Services in the Windows Task Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Upgrading Tip: Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Installation Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Contents v

Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Cannot Install After Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Configuration Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Errors During Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Failure Deploying to Application Server Without Configuration Errors . . . . . . . . . . . 65

Out-of-Memory Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

UNIX Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Hyperion Configuration Utility Startup Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Apache Tomcat Startup Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

File Descriptor Limit Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Preparing JVM...Error Writing to This File Error . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Chapter 7. Troubleshooting Essbase – System 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Essbase Server Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Essbase Installer Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Connection Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Administrator Login Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Problems Assigning Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Integration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Connection Failure to OLAP Metadata Catalog or External Data Source . . . . . . . . . . . 71

Provider Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Out of Memory Errors With Concurrent Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Load Balancing Problems with WebLogic through Apache . . . . . . . . . . . . . . . . . . . . 72

Chapter 8. Troubleshooting Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Tips and Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

General Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Failure to Access Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Connection Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Interactive Reporting Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Essbase Not Loaded Successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Faulty Oracle Net Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Failure Processing an Oracle Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Fonts Display Incorrectly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Financial Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Invalid User Name Error When Starting Financial Reporting Studio . . . . . . . . . . . . . 75

Missing PlanningSystemDB.properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Error Running Financial Reporting Studio on the Desktop . . . . . . . . . . . . . . . . . . . . 76

vi Contents

Runtime and ActiveX Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Error Connecting to SAP BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

BEx Query Not Listed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 9. Troubleshooting Financial Performance Management Applications . . . . . . . . . . . . . . . . . . . . . . . . 77

Common Planning Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Planning Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Upgrading Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Configuring Planning with Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Using Planning with Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Performance Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Common Financial Management Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Accessing Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Connection Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Rights Required for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Failure Registering Financial Management Server on Client Machine . . . . . . . . . . . . . 83

Large Data or File Loads Fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Common Performance Management Architect Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Installing and Configuring Performance Management Architect . . . . . . . . . . . . . . . . 83

Installation Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Accessing Performance Management Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Failure Accessing Performance Management Architect Dimension or ApplicationLibrary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Using IBM DB2 with Performance Management Architect . . . . . . . . . . . . . . . . . . . . 87

Common Performance Scorecard Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Configuration Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Application Server Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Performance Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Common Strategic Finance Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Performing Diagnostics on Strategic Finance Service . . . . . . . . . . . . . . . . . . . . . . . . . 90

Using Novell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Chapter 10. Troubleshooting Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Common Data Integration Management Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Connection Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Common FDM Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Configuration Issues with Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Oracle Client/Provider Cannot Connect to Database . . . . . . . . . . . . . . . . . . . . . . . . 95

Cannot Authenticate User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Contents vii

Cannot Perform Bulk Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Common Data Relationship Management Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Reviewing Readme Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Access is Denied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Server Unable to Process Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Failure Installing on Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Configuration Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Unable to Create JVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Invalid Classpath Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Server Startup Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Upgrade Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

viii Contents

1Introduction

In This Chapter

Purpose .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Audience .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Assumed Knowledge .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Check on Oracle® Technology Network to see if an updated version of this guide is available.

Purpose This guide provides troubleshooting tips for installing and configuring Oracle's Hyperionproducts. It contains general information about how to approach troubleshooting, importantdocumentation to review, validation checks to perform, and how to use logs. Also provided aresolutions to difficulties that you may encounter using Oracle's Hyperion® Shared Services toprovision and share users among Hyperion product applications.

Audience This guide is for administrators and IT professionals who install, configure, andmanageHyperion products.

Assumed Knowledge These skills are assumed:

l Basic security and server administration

l Basic Windows and UNIX administration

l Web application server administration

A strong understanding of these aspects of your organization's technical infrastructure are alsoassumed:

l Security, including authentication providers such as Microsoft Active Directory, and use ofSSL

l Database and server environments

Purpose 9

l Network environment and port usage

10 Introduction

2Troubleshooting Basics

In This Chapter

Reviewing the Installation Start Here .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Reviewing the Readme ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Using Product Installation Guides .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Validating the Installation and Configuration... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Using Logs .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Using My Oracle Support (MetaLink 3) .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Using Shared Services Troubleshooting Utilities .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Additional Documentation .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Accessing Technical Support Resources .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Perform these tasks before contacting Support for assistance.

Reviewing the Installation Start Here This document contains system requirements, product release compatibility, default productports, the startup dependencies, and the installation and configuration sequence. The HyperionInstallation Start Here also contains troubleshooting information that you can use to identifypotential or particular problems in your environment.

Meeting System Requirements Before installing Hyperion products, you must satisfy all common, system, product-specific,and third-party requirements. See the Hyperion Installation Start Here.

Checking Release CompatibilityIf you are upgrading from a previous release, it is important to check whether the softwareversions of Hyperion products you have installed in your environment are compatible with thenewer release you are installing. See the “Release Compatibility” chapter in the HyperionInstallation Start Here.

Reviewing the Installation Start Here 11

Avoiding Port ConflictsDuring Hyperion product installations, the default port numbers for application servers areautomatically populated. You can change the defaults during the configuration process.However, each port number must be unique. To avoid error messages similar to “port alreadyin use” or “bind error”, review the list of default product port numbers. See the “Port Numbers”chapter in the Hyperion Installation Start Here.

Reviewing Startup Dependencies Ensure that you have reviewed and keep handy the list of startup dependencies for Hyperionproducts in the Appendix of the Hyperion Installation Start Here. This appendix also providesdefault product URLs. Before you start services or processes, start all the databases used asrepositories.

Before starting the next service or process, ensure that the previous service or process successfullystarted. Some services or processes take longer than others to start, and startup times may varyby computer.

Reviewing the Readme All Hyperion products include a Readme document for each release. This document containsknown installation or configuration issues along with other product issues. It is very importantto review the Readme, which contains late-breaking information that may impact yourdeployment.

Using Product Installation GuidesHyperion product installation guides provide step-by-step installation and configurationprocedures. Very often you can find the answer to an installation or configuration issue by goingback to the installation guide and checking that you have completed all the steps described inthe guide.

Validating the Installation and ConfigurationAfter you install and configure a product, perform these tasks to ensure that it is workingcorrectly. Verify the following:

l All necessary components were installed successfully by checking for exceptions and errorsin the installation logs. See Chapter 4, “Logs.”

l Uninstallers exist for all products under the product installation directory.

l All configuration tasks completed successfully as follows:

m The Oracle's Hyperion® Configuration Utility™ summary panel does not displayfailures or warnings.

12 Troubleshooting Basics

m HYPERION_HOME\logs\config\configtool_err.log is empty

m No exceptions display in HYPERION_HOME\logs\config\configtool.log

l You can connect to an external user directory and Shared Services

Using Logs A fundamental troubleshooting tool is to enable and use debugging information in each productlog file. The “Using Logs” chapter helps you learn how to turn on debugging and find the logsfor each product. Perform this step before calling Technical Support so you can provide specificinformation about your issue. See Chapter 4, “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.

Using Shared Services Troubleshooting UtilitiesUse the utilities provided with Shared Services to identify and resolve user provisioning issues.One utility verifies the external user directories or Native Directory that you use to authenticateusers by examining css.xml. Another utility, CSS Spy, validates connections to user directoriesand provides user directory information.

Additional Documentation Refer to the following documents for detailed installation, licensing, deployment, provisioning,and security information.

Document Description Location

Hyperion Installation Start Here Provides key installation andconfiguration information such assystem requirements, prerequisites,and recommended installationsequence.

Oracle E-Delivery and product DVD

Using Logs 13

Document Description Location

Product Installation Guide Provides detailed product-specificinstallation and configurationinstructions.

Oracle E-Delivery and product DVD

Product Readme Provides known issues for thisrelease and other late-breakinginformation.

Oracle E-Delivery

Hyperion Security AdministrationGuide

Provides information aboutconfiguring external authenticationand provisioning users.

Oracle E-Delivery

Hyperion Product SSL ConfigurationGuide

Provides information aboutconfiguring products using SecureSocket Layer (SSL).

Oracle E-Delivery

Hyperion System 9 BI+ Performancewhitepaper

Provides information about installing,configuring, and managing large,complex deployments.

Oracle® Technology Network

Accessing Technical Support Resources

Support Team Description Contact Information

Hyperion Support Services Helps you effectively operate,manage, and run Hyperionperformance management solutionsby delivering technical expertisewhenever you need it.

http:\\www.hyperion.com\services\support_programs

Worldwide support Offers three levels of comprehensivesupport programs to meet yourbusiness requirements:

l Alliance wide support

l Enterprise wide support

l Standard support

http:\\esupport.hyperion.com

For help by phone, use the countrylistings on http:\\www.hyperion.com\services\support_programs\support_centers.cfm

E-services program Provides virtual technical assistancewith installations, upgrades,migrations and cross-productconfigurations.

[email protected]

14 Troubleshooting Basics

3Validating Installation and

Configuration

In This Chapter

Performing Common Diagnostics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Foundation Services Diagnostics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Reporting and Analysis Diagnostics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Essbase Diagnostics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Performance Management Architect Diagnostics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Planning Diagnostics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Financial Management Diagnostics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Performance Scorecard Diagnostics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Strategic Finance Diagnostics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Data Relationship Management Diagnostics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

FDM Diagnostics .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Performing Common Diagnostics Perform these checks to ensure that Hyperion products can work with Shared Services andexternal user directories:

Component Test To Perform

General Checks Ensure accurate entry of:

l Server names

l Database name

l Configured port numbers

Shared Servicesl Product can connect to Shared Services on <host>:<port>

ExternalAuthentication

l User directory is initialized

l Product is connected to the user directory

Services are running For each product, check that services are running. See “Startup Dependencies and DefaultURLs” in the Hyperion Installation Start Here.

Performing Common Diagnostics 15

Foundation Services Diagnostics


Shared Servicesl Database is connected to <host>:<port>

l Web application is running on <host>:<port>

External Authenticationl Can connect with the user directory

l Can get a dummy group and get an exception stating 'group not found'

l Check the total number of groups under the group URL

Reporting and Analysis Diagnostics


Oracle'sHyperion®InteractiveReportingStudio

l Services are running on <host>

Note: See “Startup Dependencies and Default URLs” in the Hyperion Installation Start Here.

Oracle'sHyperion®FinancialReporting –System 9



Note: See “Startup Dependencies and Default URLs” in the Hyperion Installation Start Here.

l For the Web server, check the application context on <host>:<port>

Oracle'sHyperion® WebAnalysis –System 9



Essbase Diagnostics


Oracle's Hyperion®Essbase® – System 9

l Server is running on <host>:<port>

Oracle's Hyperion®Provider Services


Oracle's Essbase®AdministrationServices


Oracle's Essbase®Integration Services

l Service is running on <host>

16 Validating Installation and Configuration


Note: See “Startup Dependencies and Default URLs” in the Hyperion Installation StartHere.

Performance Management Architect Diagnostics


Oracle'sEnterprisePerformanceManagementArchitect




l Database is connected to <host>:<port>


Planning Diagnostics


Oracle's Hyperion® Planning – System9


l Database is connected to <host>:<port>


Financial Management Diagnostics


Oracle'sHyperion®FinancialManagement –System 9



l Database is connected to <host>


Performance Scorecard Diagnostics


Oracle's Hyperion® Performance Scorecard – System 9l Web application is running on <host>:<port>

Performance Management Architect Diagnostics 17

Strategic Finance Diagnostics


Oracle's Hyperion®Strategic Finance



Data Relationship Management Diagnostics


Oracle'sHyperion® DataRelationshipManagement




FDM Diagnostics


Oracle's Hyperion® Financial Data QualityManagement

For the Web server, check the application context on<host>:<port>.

18 Validating Installation and Configuration

4Logs

In This Chapter

Common Log File Location ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Log File Size and System Performance ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Installation Logs... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Hyperion Configuration Utility Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Shared Services Logs... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Smart View Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Essbase – System 9 Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Reporting and Analysis Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Financial Performance Management Applications Logs... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Data Management Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Application Server and Web Server Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Common Log File LocationLog files for most Hyperion products are created in <Hyperion_Home>\logs\<product>.

For example, Shared Services logs are created in <Hyperion_Home>\logs\SharedServices9. Hyperion Configuration Utility log files are created in<Hyperion_Home>\logs\config.

Note:

The log locations listed in this chapter are the default locations.

Logs for these products are not created in <Hyperion_Home>\logs:

l Application servers and Web servers

l Essbase

l Administration Services

l Planning

l Oracle's Hyperion® Business Rules

Common Log File Location 19

Note:

Some products may write log files to both common and other folders, as indicated in this chapter.

Log File Size and System PerformanceLogs are installed with the recommended default log levels.

More detailed logging levels will increase log file size and can reduce overall system performance.Consequently, Hyperion recommends that you use the least detailed logging level required.Revert to the original log levels after troubleshooting is complete to avoid using too much diskspace and negatively affecting performance.

Installation LogsInstallation logs for all products are in <Hyperion_Home>\logs\install\<product>.Provide a.zip of the install logs when reporting installation related problems to TechnicalSupport.

Hyperion Configuration Utility LogsHyperion Configuration Utility logs configuration errors and warning messages toconfigtool.log.

Log File Names and Descriptions

Name Contents

configtool.log Configuration errors and warning messages

configtool_err.log Configuration errors

Note: When troubleshooting, check to see that this log is empty.

Setting Log LevelsThe Hyperion Configuration Utility log is set to debug and cannot be changed.

Shared Services LogsThis section contains information about Shared Services log files.

20 Logs


Name Contents

SharedServices_Security.log External authentication and single sign-on activity

SharedServices_Admin.log User management activity

SharedServices_Metadata.log Information about metadata management and registration

SharedServices_Taskflow.log Information about taskflow

SharedServices_Taskflow_CMDExecute.log

Scheduling information

SharedServices_Taskflow_Optimize.log Scheduling information

SharedServices_SyncOpenLDAP.log Information that synchronizes OpenLDAP and relational datasources

SharedServices_Security_Client.log Information about the external authentication client

Note: In previous releases, HyperionCSS.log

SharedServices_Memory_Profiler.log Memory consumption information

SharedServices9.log Shared Services activity

SharedServices.log Shared Services activity

openldap.log OpenLDAP activity

Setting Log LevelsYou can specify the kinds of messages that are written to the logs, such as debug, error, or warn.

Modify these files to configure the log-level settings for Shared Services:

l CSS.xml

l HSSLogger.properties

These files are in <HYPERION_HOME>\deployments\<AppServerNameAndVersion> for allsupported application servers except WebLogic 8.x.

WebLogic 8.x files are in <ProductHome>\AppServer\InstalledApps\<AppServerName>\<version>.

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 is changed manually in CSS.xml and imported to the registry

After changing security log levels from the User Interface for CSS you do not have to restart theserver.

Shared Services Logs 21

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 User Management Console.

2 Select Administration > Configure User Directories.

3 In Defined User Directories, set the Logging level global parameter to DEBUG.

4 Click OK.

Log Levels for the OpenLDAP DatabaseThe OpenLDAP database stores provisioning data. On Windows, Shared Services automaticallyinstalls OpenLDAP as a service (Hyperion SharedServices9 OpenLDAP), configures it, andstarts it.

Log-level settings for OpenLDAP are flags or parameters that are passed during OpenLDAPstartup. Log levels for OpenLDAP are included in the startup command, not in a configurationfile.

Table 1 OpenLDAP Startup Commands

OpenLDAP Startup Command Log Details Description

slapd -d -1 Enable all debugging Logs all OpenLDAP transactions andqueries.

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 ofpacket handling.

slapd -d 4 Heavy trace debugging Provides a large amount of trace withdata searched in database.

slapd -d 8 Connection management Displays all data available indatabase with its internal processlogs.

slapd -d 16 Print out packets sent and received Displays all packets sent andreceived.

slapd -d 32 Search filter processing Displays all OpenLDAP filter andsearch data.

slapd -d 64 Configuration processing Displays configured data such asObject 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, displays add, modify,and delete operations. (This option

22 Logs

OpenLDAP Startup Command Log Details Description

provides fewer logs than the -1option.)

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 eachattribute of an object class.

slapd -d 2048 Print entry parsing debugging Provides schema-level detail.

slapd -d 4096 Database cache processing Displays cache processing data suchas index parameters.

slapd -d 8192 Database indexing Provides database index details.

slapd -d 16384 Syncrepl consumer processing Displays replica processingoperations (master-slave OpenLDAPconfiguration).

Smart View LogsThis section contains information about Oracle's Hyperion® Smart View for Office logs.

File Names and Descriptions

Name Contents

SmartViewLogs.log Smart View error messages

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 ones to record in SmartViewLogs.log.

ä To log messages:

1 From the Hyperion menu, select Options > Display.

Under Log Messages, select one of the following:

l Information to log all messages, including warnings and errors—recommended to diagnoseproblems.

l Warnings to log warning and error level messages.

l Errors to log error messages only.

l None to suppress all messages.

Smart View Logs 23

2 Select Route Messages to a Log File.

3 Optional: To clear the log when Oracle's Hyperion® Smart View for Office is launched, select Clear log fileon next launch.

4 Click OK. The setting takes effect after you refresh or perform a drill operation.

Essbase – System 9 LogsThe following sections contain information on Essbase – System 9 product family logs.

Essbase LogsThe following sections contain information on Essbase log files.


Name Contents Location

Essbase.log Essbase Server activities and errors <ARBORPATH>\essbase.log

application_name.log Essbase application activities anderrors

<ARBORPATH>\app\<application_name>\<application_name>.log

dataload.err Data load and dimension build errors <ARBORPATH>\client\dataload.err

Note: If a rules file is not used for adata load, errors are written to<ARBORPATH>\app\<application_name>\<application_name>.log

dbname.atx, dbname.alg Successfully completed spreadsheetupdate transactions

These are SSAUDIT log files; Filename and location are specifiedthrough an essbase.cfgconfiguration setting. See“Monitoring Data, Applications, andDatabases” in the Hyperion Essbase— System 9 DatabaseAdministrator's Guide and theEssbase Technical Reference.

Note: SSAUDIT log files arecreated only if SSAUDIT is activatedin essbase.cfg.

<ARBORPATH>\app\<appname>\<dbname>

log0000x.xcp Information captured at the time ofan abnormal termination

A location:

l <ARBORPATH>

\log00001.xcp

24 Logs


l <ARBORPATH>\app

\log00001.xcp

l <ARBORPATH>\app

\<application_name>

\log00001.xcp

l <ARBORPATH>\app

\<application_name>

\<database_name>

\log00001.xcp

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 Hyperion Essbase — System 9Database Administrator's Guide and the Essbase Technical Reference Guide for information aboutessbase.cfg settings.

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 Hyperion Essbase — System 9 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 Hyperion Essbase — System 9 DatabaseAdministrator's Guide, and the Essbase Technical Reference.

Administration Services LogsThe following sections contain information about Administration Services logs.

Essbase – System 9 Logs 25



easserver.log Administration Services Serveractivity

<EAS_HOME>\server\bin

eas-install.log Administration Services installationinformation

<HYPERION_HOME>\logs\install\<product>

Setting Log LevelsHow you set log levels for Administration Services varies by application server and if the productis running as a service. For assistance with troubleshooting Administration Services, contactTechnical Support.

After changing log levels you must restart the Administration Services server for the log settingsto take effect.

Integration Services LogsThe following sections contain information on Integration Services logs.


Name Contents

olapisvr.log Integration Server activity

Setting Log LevelsYou can set the log level in Integration Services by using the -L startup switch. For informationabout Integration Services startup switches, see the Integration Services System Administrator'sGuide.

ä 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:

26 Logs

Table 2 Log Levels

Level Description

0 To log all debug messages and the ODBC SQL generated by Integration Server; generatedataloadrecord.txt, listing the first 1,000 records, which may include successfully loaded records andrejected records; and create hisdld.rul consisting of the names of the dimensions loaded followed bythe 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.

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.

UNIX: To use the highest level of logging, enter: olapisvr -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.

Reporting and Analysis LogsAll 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. See “Troubleshooting”in the Hyperion Workspace Administrator's Guide. Services, servlets, process monitors, and Webservices log messages centrally using the Logging Service. Log4j (version 1.2) is used as the basisfor the logging framework and configuration files.

For information on Oracle's Hyperion® Reporting and Analysis – System 9 logs, see“Troubleshooting” in the Hyperion Workspace Administrator's Guide.

Note:

Local Service Configurator, Remote Service Configurator, and Calendar Manager log messageslocally.

Reporting and Analysis LogsThe following sections contain information about Reporting and Analysis logs.

Reporting and Analysis Logs 27



server_messages_BrowseServlet.log

Log for Oracle's Hyperion®Workspace browsing servletcomponent, which browses therepository

<HYPERION_HOME>\logs\BIPlus\

server_messages_AdministrationServlet.log

Log for Workspace administrationservlet component, whichadministers the Reporting andAnalysis system


server_messages_PersonalPagesServlet.log

Log for Workspace personal pagesservlet component (bookmarks andpersonal pages administration)


server_messages_DataAccessServlet.log

Log for the data access servlet (logsthick client or plug-in calls to the dataaccess service)


server_messages_AnalyticBridgeService.log

Log for the Analytic Bridge Service(bridges data to Oracle's Hyperion®Interactive Reporting – System 9 fromother Hyperion products.


server_messages_AuthenticationService.log

Authentication Service information(user credentials and groupmembership at login)


server_messages_AuthorizationService.log

Authorization Service information(roles and their associations withoperations, users, groups, and otherroles)


server_messages_CommonServices.log

Entries for the Reporting and Analysislogging service before the Reportingand Analysis logging service isoperational.

Note: Logged items are also instdout_console.log.


server_messages_DataAccessService.log

Data Access Service information <HYPERION_HOME>\logs\BIPlus\

server_messages_EventService.log

Event Service information (systemresource and job management)


server_messages_GSM.log Global Service Manager information(system configuration and servicemonitoring)


server_messages_HarvesterService.log

Impact Management AssessmentServices (Harvester) information(published Interactive Reportingrepository document metadata)


28 Logs


server_messages_IntelligenceService.log

Interactive Reporting Service. This logis helpful in troubleshootingproblems with the InteractiveReporting thin client.


server_messages_IRJobService.log

Log for the Job Service, processesInteractive Reporting jobs, eitherscheduled or on demand


server_messages_IRServiceHelper.log

Interactive Reporting Service HelperProcess information (logging andusage tracking for all InteractiveReporting services)


server_messages_JobService.log

Job Service information (Reportingand Analysis job management)


server_messages_LSM.log Log for the Local Service Manager(LSM) service; LSMs provide supportfor Interactive Reporting distributedservices infrastructure.


server_messages_NameService.log

Name Service information (RSCservices monitoring)


server_messages_PublisherService.log

Publisher Service information(repository communication for otherLSC services and some Webapplication requests)


server_messages_RepositoryService.log

Repository Service information(Reporting and Analysis data storagerepository)


server_messages_SessionManager.log

Session Manager Service information(simultaneous users and sessiontime-out management)


server_messages_ServiceBroker.log

Service Broker information (GSM andLSM client request routing andRSCload balancing)


server_messages_TransformerService.log

Impact Management Update Service(Transformer) information(Interactive Reporting documentupdates)


server_messages_UsageService.log

Usage Service information(Interactive Reporting usagestatistics (such as the most usedfiles, the most selected MIME types)


server_messages_CalendarManager.log

Calendar Manager information (forjob scheduling)


server_messages_SDK.log Interactive Reporting SDKinformation




server_messages_EventService.log

Log for the Event Service, includingevents that trigger jobs to run


server_messages_LocalServiceConfigurator.log

Local Service Configurator (LSC)information


server_messages_RemoteServiceConfigurator.log

Configuration information on Remoteservices, which are configured usingthe Remote Service Configurator(RSC)


configuration_messages.log

This log file contains basicconfiguration information, includingJava system property information,JAR file version information, anddatabase information.

<BIPLUS_HOME>\logs

name_backupMessages_ip-address_port.log(where nameis the process name)

Logging messages when the loggingservice is unavailable

stdout_console.log The stdout_console.log isgenerated regardless of the operationbeing performed, and representsstandard output and standard errors(console output). Some errorscaptured by the application arelogged here, as are startup failures.

<BIPLUS_HOME>\logs

WorkspaceApp.log Workspace Web Application activity

BIService.log Reporting and Analysis activity

server_messages_Installer.log

Reporting and Analysis installationinformation

AvalancheInstall.log Installation %USERPROFILE% (typically c:\Documents and Settings\<UserName>), $USER_HOME onUNIX

AvalancheUnInstall.log Uninstallation %USERPROFILE% (typically c:\Documents and Settings\<UserName>), $USER_HOME onUNIX

biplus-install.log Installation <HYPERION_HOME>\logs\install

install.log Installation <BIPLUS_HOME>\logs

biplus_1_config.xml Information about user input duringconfiguration

<HYPERION_HOME>\common\config\<product>\biplus\<version>

InstallHistory.properties Installation <BIPLUS_HOME>\install

30 Logs


Workspace_log.<date>.txt Tomcat log for Workspace (forexceptions only)

<HYPERION_HOME>\deployments\Tomcat5\Workspace\logs\

Workspace.log WebLogic 8.1 log for Workspace <BIPLUS_HOME>\AppServer\InstalledApps\WebLogic\8.1\WorkspaceDomain\Workspace\

Workspace.log WebLogic 9 log for Workspace <HYPERION_HOME>\deployments\WebLogic9\servers\Workspace\logs\

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 Hyperion Workspace Administrator'sGuide.

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

Loggers, logging levels, and appenders are configured in XML files. The log rotation property isa Java system property and is configured in startcommonservices.bat. Logging levels forLSC services, RSC services, and the root logger are configured using LSC and RSC. All otherconfiguration changes are made by editing XML files. See “Configuring Log Properties forTroubleshooting” in the Hyperion Workspace Administrator's Guide for information on settingReporting and Analysis log levels.

Note:

Configuration errors for RSC services show at startup in stdout_console.log orserver_messages_NameService.log; configuration_messages.log might be helpful.


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 Hyperion Workspace Administrator's Guide.

Financial Reporting LogsThe following sections contain information about Financial Reporting logs.



FRCommSrv.log Financial Reporting CommunicationServer information


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


FRSchedSrv.log Batch scheduler activity <HYPERION_HOME>\logs\BIPlus\

FRScheduleBatch.log Activity from the Scheduler commandline interface


FRWebApp.log Activity from the Financial ReportingWeb Application, where Web clientpages are generated


FRPrintSrv.log Financial Reporting printinginformation


FRUserLogin.log User login information <HYPERION_HOME>\logs\BIPlus\

HRRunAnt.out Financial Reporting configuration log <BIPLUS_HOME>\logs

HRRunAnt.err Financial Reporting configurationerror log

<BIPLUS_HOME>\logs

Setting Logging LevelsTo set debug level logging for Financial Reporting components, specify these settings infr.properties in <BIPlus>\lib:

log4j.rootLogger=DEBUG,dest1

log4j.appender.dest1.MaxFileSize=1024KB

log4j.appender.dest1.MaxBackupIndex=20

After changing log levels you do not need to restart the Reporting and Analysis components forthe log settings to take effect.

32 Logs

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

SQR Production Reporting LogsThe following sections contain information about Oracle's Hyperion® SQR® ProductionReporting – System 9 logs.


Name Contents

<report_name>.log

Output from SHOW and DISPLAY commands when -O command line flag. Can be redirectedto any file.

<report_name>.err

Error messages/warnings during compilation and program execution when -E command lineis used (can be redirected to any file).

sqr.log (Windows) Output from SHOW and DISPLAY commands and/or error messages/warningsduring compilation and program execution when neither -E and -O command line flagsare used.

Setting Logging LevelsYou cannot set logging levels for Oracle's Hyperion® SQR® Production Reporting – System 9.

Interactive Reporting LogsInteractive Reporting and Data Access Service have additional log files in the directory whereservices are run, and which collect log messages before these services connect to the LoggingService. Log messages in these files are not routed to Logging Service log files. Startup problemsare in BIstartup.log and DASstartup.log.




BIstartup.log Interactive Reporting service startupinformation

<BIPLUS_HOME>\logs\

DASstartup.log Interactive Reporting Data AccessService startup information

<BIPLUS_HOME>\logs\

Web Analysis LogsThe following sections contain information on Web Analysis logs.


Name Contents

WebAnalysis.log Web Analysis activity

WebAnalysisApp.log Web Analysis Web application activity

server_messages_WebAnalysis.log Web Analysis Web application log

Setting Log Levels

ä To set log levels in server_messages_WebAnalysis.log:

1 Openlogging-settings.jar in <HYPERION_HOME>\deployments\<AppServer>\WebAnalysis\webapps\WebAnalysis\WEB-INF\lib.

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

4 After changing log levels you must restart the server for the log settings to take effect.

34 Logs

Financial Performance Management Applications LogsThe following sections contain information about Financial Performance Management logs.

Financial Management LogsThe following sections contain information about Financial Management logs.


Name Contents

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

Setting Log LevelsYou cannot set log levels for Financial Management.

Performance Management Architect LogsThe following sections contain information about Performance Management Architect logs.


Name Contents

awb.log Information written by the Web server

DMEngine.log Data Synch Web application activity

Windows Event Viewer Dimension Server activity

Transaction logs Transactions

Note: View transaction logs from the Dimension Library

Setting Logging Levels

ä To change the logging level for Performance Management Architect:

1 Go to the deployed Web application directory.

For Tomcat, this is C:\Hyperion\deployments\Tomcat5\EPMAWebTier\webapps\awb\WEB-INF\conf.

2 Open AWBLog4j.properties.

Financial Performance Management Applications Logs 35

3 Modify this line: log4j.logger.com.hyperion.awb=ERROR,logfile, stdout tolog4j.logger.com.hyperion.awb=DEBUG ,logfile, stdout


Planning LogsThe following sections contain information about Planning logs.



Application Server logs Planning activity Tomcat 5.0.28: <HYPERION_HOME>\deployments\Tomcat5\HyperionPlanning\logs

WebSphere 6.0.2.11 & 6.1.0.5:<HYPERION_HOME>\deployments\WebSphere6\profile\logs\HyperionPlanning

WebLogic 8.1.6: <HYPERION_HOME>\Planning/AppServer/InstalledApps/WebLogic/8.1/HyperionPlanningDomain

WebLogic 9.1: <HYPERION_HOME>\deployments\WebLogic9\servers\HyperionPlanning\logs

Oracle 10.1.x : <ORACLE_HOME>\opmn\logs\OC4J~HyperionPlanning~default_island~1

HspEventLog.log Planning activity (end-user issues:refresh issues, and so on.)

\Hyperion\Planning\

UserProvisionSync.log \Hyperion\Planning\bin

Setting Logging Levels

ä 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 > Manage Properties.

3 Select the System tab.

4 Set DEBUG_ENABLED to true.

36 Logs

5 After changing the log levels you must restart the Planning application server for logs on the Planning side.

Business Rules LogsThe following sections contain information about Business Rules log files.

Log Files Names and Descriptions


hbrclient.log Business Rules client activity For all Application Servers:<HYPERION_HOME>\AnalyticAdministrationServices\console\bin

hbrserver.log Business Rules server activity Tomcat 5.0.28: <HYPERION_HOME>\deployments\Tomcat5\bin

WebSphere 6.X <HYPERION_HOME>\deployments\WebSphere6\profile

WebLogic 8.1.6 <HYPERION_HOME>\AnalyticAdministrationServices\AppServer\InstalledApps\WebLogic\8.1\aasDomain

WebLogic 9.1 <HYPERION_HOME>\deployments\WebLogic9

hbrlaunch.log Business Rules launch information Tomcat 5.0.28: <HYPERION_HOME>\deployments\Tomcat5\bin

WebSphere 6.X <HYPERION_HOME>\deployments\WebSphere6\profile

WebLogic 8.1.6 <HYPERION_HOME>\AnalyticAdministrationServices\AppServer\InstalledApps\WebLogic\8.1\aasDomain

WebLogic 9.1 <HYPERION_HOME>\deployments\WebLogic9

log.txt Information about processes run onthe Business Rules client


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 > Programs > Hyperion > AdministrationServices > Start Administration Services Console.

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

Note:

If the Administration Services default port was changed , enter the port information before theAdministration 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 Business Rules client configuration are displayed.

5 To change the level of error reporting for the client on the Client Configuration tab, select a level from LogLevel:

l Severe

l Warning (default)

l Info

l Config

l All

6 To change the level of error reporting for the server on the Server Configuration tab, select one of the errorlevels described in step 5 from the Log Level list.

7 Click Save.


Performance Scorecard LogsThe following sections contain information about Performance Scorecard logs.


Name Contents

HPSWebReports.log Performance Scorecard application activity

HPSAlerter.log Alerter Web application activity

38 Logs

Name Contents

errors.log Performance Scorecard import or export errors

failedrecords.log Performance Scorecard import or export errors

successfulRecords.log Performance Scorecard import or export records

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 one of these directories:

Application Server Location

Oracle 10.1.x <HPS_INSTALL>\AppServer\InstalledApps\Oracle\10g\manual\webappsconf\config

WebLogic 8.1 <HPS_INSTALL>\AppServer\InstalledApps\<app server>\<version>\webappsconf\config\

WebLogic 9.1, Tomcat, andWebSphere 6

<HYPERION_HOME>\deployments\<AppServerNameAndVersion>\webappsconf\config\

See the Hyperion Performance Scorecard - System 9 Administrator's Guide.

After changing log levels you must restart the server for the log settings to take effect.

Strategic Finance LogsThe following sections contain information about Strategic Finance logs.


Name Contents

debug_YYYYMMDD_HHMMSS.log

Debugging information from the Strategic Finance Server (detailed informationon what is happening with every server operation)

eventYYYYMMDD.log Information about Strategic Finance events

Note: Using the Event Logs tab of the Administrator utility, you can viewindividual event logs. See the Strategic Finance Administrator's Guide.

YYYYMMDD_HHMMSS_seq.log A history of user's actions (called user results log files).

event logs Microsoft Application Event log.

Note: Located in Start > Control Panel > Administrative Tools > Event View >Application log tab.


Setting Logging LevelsYou can set the logging level of Strategic Finance debug logs and event logs.

ä To set the logging level of Strategic Finance Debug logs:

1 From Server Settings, select Advanced.

2 In Trace Level, select:

l Normal for no log to be created

l Error to write errors to the log

l Info to write detailed information to the log continuously (negatively affects performance)

For information on setting the logging level in the event logs, see the Hyperion Strategic FinanceAdministrator's Guide.

Data Management LogsThe following sections contain information on Data Relationship Management logs.

Data Integration Management LogsThe following sections contain information about Oracle's Hyperion® Data IntegrationManagement logs.


Name Contents

dim.log Configuration information (useful for resolving configuration issues)

Setting Logging LevelsFor information on setting Data Integration Management logging levels, see the Data IntegrationManagement online help.

Translation Manager LogsThe following sections contain information about Oracle's Hyperion® Translation Managerlogs.

40 Logs


Name Contents

Depends on the application server. Translation Manager error information, depending on the logging level that isset for the application server.

Setting Logging LevelsTranslation Manager logging levels depend on the application server for which it is configured.For example, Oracle's Hyperion® Translation Manager logs warnings and errors if theapplication server is set to log warnings and errors.

FDM LogsThe following sections contain information about FDM logs.


Name Contents

tLogActivity table Information about FDM activities and audit related information.

l tBatch

l tBatchContents

l tBatchInformation

Batch processing, informational, and error log entries

<username>.err Information about FDM user errors.

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

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

Note: FDM Task Manager can also log scheduled task events (when logging isenabled) in the Windows Event Log.

Authentication.err Information about FDM Failed authentication attempts

Setting Logging LevelsYou cannot set logging levels for FDM.

Data Relationship Management LogsThe following sections contain information about Data Relationship Management logs.

Data Management Logs 41


Name Contents

mssql_install.log

oracle_install.log

Installation information

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

Windows Application Log Information written by Data Relationship Management, about DataRelationship Management events

Data Relationship ManagementImport Log

Information about the Import operation

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

Data Relationship ManagementBlender 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 can overridethe name and location)

Microsoft Application Event Log Errors written by the Data Relationship Management Server

Data Relationship Managementrepository database transaction log

Transaction information written by the Data Relationship Management system

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.

ä To set Transaction History logging levels:

1 In the Data Relationship Management client, select Main > Admin > System Preferences.

2 In TransactionLevel, select a transaction level type:

l Logged Action records basic logging information, such as users logging in and logging out.

l Core Action records actions that change the version, hierarchy, or node information, suchas Add Node, Change Property, or Move Node.

l Result Action records actions that result from core actions. For example, if the clear all belowcore action is performed, then properties are cleared from individual nodes. The clearing ofproperties from the individual nodes is a result action.

l Loss Action records loss of data due to a core action. For example, when a node is deleted,all of the defined properties for that node are deleted, which is a loss action. Loss actions arecontrolled by the LossLevel system preference.

3 Set additional system preferences:

42 Logs

l LossLevel indicates what to track for lost information. Its values are Defined and All. Whenset to Defined only values that are specifically set at the node are tracked when the node isdeleted. When set to All, derived, default, inherited values are also tracked in the LossAction.

l AllowAsOf forces tracking of Core Actions.

Note:

You cannot change the level of detail recorded in logs other than the transaction history. Afterchanging the log levels for the Transaction History you must restart the Data RelationshipManagement Windows service for the log settings to take effect.

Note:

If the Loss Action is specified or if AllowAsOf is turned on, then Core Actions are tracked, evenif not set in the TransactionLevels System Preference.

Application Server and Web Server LogsYou can also troubleshoot by reviewing third-party logs such as those for application serversand Web servers. See the vendor documentation for information about third-party logsindependent of Hyperion products.

Application Server LogsEvery Hyperion application that is deployed to an application server generates logs for thatapplication server.

IBM WebSphere 6.0IBM WebSphere 6.0 writes log files to: HYPERION_HOME\deployments\<AppServerNameAndVersion>\bin\<product>

BEA WebLogic 8.1BEA WebLogic 8.1 writes log files to: <ProductInstallHome>\AppServer\InstalledApps\WebLogic\8.1\<APP_NAME>\<APP_NAME>.log

Also, a deployment log is created in the same folder, calledWebLogicBeanDeployOutput.txt

BEA WebLogic 9.1BEA WebLogic 9.1 writes log files to: <HYPERION_HOME>\deployments\<AppServerNameAndVersion>\bin\<product>.

Application Server and Web Server Logs 43

Apache Tomcat 5.0.28Apache Tomcat writes files into: <HYPERION_HOME>\deployments\<AppServerNameAndVersion>\bin\<product>.

Oracle 10.1.XOracle 10.1.x Application Server has a Log Viewer Utility which is available through the adminconsole. The most commonly used log files are:

l <ORACLE_HOME>\dcm\logs\ – deployment status/error logs

l <ORACLE_HOME>\daemon_logs\log.xml – dcm daemon logs

l <ORACLE_HOME>\dcmctl_logs\log.xml – dcmctl logs

l <ORACLE_HOME>\j2ee\<APP_NAME>\log\log.xml – deployed application information

l <ORACLE_HOME>\Ora10G\opmn\logs\OC4J~APP_NAME~default_island ~1 –deployment and startup information for <APP_NAME> application

l <HYPERION_HOME>\deployments\<AppServer>\bin\<product>

\application.log – deployed application information

SunJES (Reporting and Analysis Only)Startup Domain Logs can be found in the <DOMAIN_HOME>\logs\server.log. Default<DOMAIN_HOME> is \var\opt\SUNWappserver\domains\<DOMAIN_NAME>

Nodeagent AppServer logs: <NODEAGENT_HOME>\<SERVER_NAME>\logs\server.log

Example:

\var\opt\SUNWappserver\nodeagents\HPSuAgent\WorkspaceServer\logs

\server.log

\var\opt\SUNWappserver\nodeagents\HPSuAgent\WebAnalysisServer\logs

\server.log

Web Server Logs

ApacheDefault logs location: <HYPERION_HOME>\logs\apache. By default, configuration uses its ownApache Web Server, which is in<HYPERION_HOME>\common\httpServers\Apache\2.0.52. You can modify log level and paths using httpd.conf in <APACHE_HOME>\conf\.

Microsoft IISDefault logs location: \WINDOWS\system32\LogFiles.

44 Logs

ä To change the IIS log file location:

1 Go to the IIS Control Panel.

2 Right click the Web site.

3 Click Properties.

4 Enter or browse to the log location in Log file directory.

5 Click OK.

Application Server and Web Server Logs 45

46 Logs

5Troubleshooting Shared

Services and Provisioning

In This Chapter

Understanding How and What to Troubleshoot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Installation, Configuration, and Deployment Issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

User Directories and Provisioning ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

OpenLDAP Issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Startup and Access Issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Resolving Product-Specific Issues... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Understanding How and What to Troubleshoot The following table indicates what components of Shared Services to troubleshoot based on theproblems you encounter performing tasks.

Table 3 Diagnostics

Problem Troubleshoot Basic Tasks

You cannot log in to Shared Services User directoryl Ensure that the Web application

service started.

l Ensure that CSS.xml containsthe most recent user logincredentials.

l Use CSS Spy to gather more dataabout the user directory, such asuser roles and credentials.

You cannot log in to other Hyperionproducts from Shared Services

OpenLDAPl Check Shared_Services_

Security.log in the productserver for errors

l Ensure that the OpenLDAPservice or process is running

OpenLDAP service or process will notstart

OpenLDAP From the Start menu, open theControl Panel to ensure that theservice is running. If it isn't, performthese tasks:

l Open a command prompt andenter: C:\Hyperion\SharedServices\9.x

Understanding How and What to Troubleshoot 47

Problem Troubleshoot Basic Tasks

\openLDAP>slapd –d 1 –f

slapd.conf.

l Switch to the %Hyperion_Home\SharedServices

\9.x\openLDAP\var

\openldap-data andexecute: ..\..bdb\bin\db_recover. You may have to runthis command twice.

Preliminary TasksPerform these initial tasks to better identify or resolve issues with Shared Services beforecontacting Support:

l Perform the steps in Chapter 2.

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. See“Troubleshooting Utilities” on page 48.

Troubleshooting UtilitiesThese utilities are provided with Shared Services:

Table 4 Troubleshooting Utilities

Utility Description

http://<HSS_Server>/58080/interop/framework/getCSSConfigFile

Verifies the external user directories or Native Directory that you useto authenticate users. This information is stored in CSS.xml

Optional: Use CSS Spy

http://<HSS_Server>/58080/interop/cssSpy

http://HSS_SERVER:58080/interop/cssSpy

Validates the following information:

l Connections to user directories using any CSS call or method

l User logins

l User role information

l Performance

See “ CSS Spy” on page 48.

CSS SpyCSS Spy enables you to validate connections to external user directories, retrieve user roleinformation, and assesses performance.

48 Troubleshooting Shared Services and Provisioning

http://HSS_SERVER:58080/interop/cssSpy

ä To use CSS Spy:

1 Navigate to http:\\<HSS_SERVER>:58080\interop\cssSpy.

2 Browse to the directory that contains CSS.xml.

3 Click Initialize.

Directories for the users, groups, and roles defined in the user directories that you use toauthenticate users are displayed.

4 Select the information to verify and click Execute.

5 Ensure that the login and password for each user is correct.

Installation, Configuration, and Deployment IssuesThe following sections address common Shared Services installation and configuration issues.

Manually Creating Database TablesYou can create database tables without using Hyperion Configuration Utility by running thescripts in:

Hyperion/SharedServices/<version>/server/scripts

Installing Components on Multiple ServersAlthough you must install Web and non-Web components on the same server, you can latermodify CSS.xml as follows to have the Web application access components on anothercomputer:

Change <hub location>=”http:\\esp intrapp1:58080” to: <hub location>=”http:\\<OpenLDAP host>:58080”

Resolving Incorrect JRE SetupEnsure that ldapbp.jar is in the classpath. By default, this is: <HYPERION_HOME>\common\CSS\9.3.1\lib

Dedicating Shared Services DatabasesEach product instance must have its own dedicated database.

Installation, Configuration, and Deployment Issues 49

Resolving Login Page Error on the Oracle 10.1.2.0.2Application Server Perform these tasks if you cannot access the Shared Services login page on Oracle 10.1.2.0.2:

1. Go to OraHome1\j2ee\home\applications\<SharedServices webapplication>9\<SharedServices web application>9\WEB-INF.

2. Rename web.xml as web.xml.back.

3. Rename web.xml.oracle as web.xml.

4. Restart the Oracle application server.

Resolving a File or Folder Permissions Error If you receive a “The Specified User Does Not Have the Required FilePermissions on the Files and Folders for Deployment” error, assign Writepermissions to: <drive>:\WebSphere\AppServer or <drive>:\IBM\WebSphere\Express\AppServer.

Upgraded Products Registered with Shared ServicesIf you upgraded products registered with Shared Services incorrectly, by not selecting the existingHYPERION_HOME, you must reinstall Shared Services and reregister the products with SharedServices after you upgrade them correctly.

Using Shared Services Upgrades With Other UpgradesTo avoid errors, perform these tasks to use a Shared Services upgrade with Hyperion productsupgrades:

1. Upgrade and configure Shared Services.

2. Start Shared Services.

3. Upgrade and configure the other products, registering them with Shared Services.

See the Shared Services Installation Guide.

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 Hyperion SecurityAdministration 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 Hyperion applications. The settingsthat the LDAP Browser uses to connect to the user directory are identical to those that Hyperionapplications use to connect to the user directories.

You can download a free LDAP Browser from:http:\\www-unix.mcs.anl.gov\~gawor\lda\dwld\bin-dwld.cgi?fileid=282b2zip.

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 Hyperion applications.

l Ensure that the server machines that host Hyperion applications are in the same geographicallocation as the server machines that host the user directories used in the provisioning process.

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

Common 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 CSS.xml

l The host name, port, or domain controller is not specified correctly in CSS.xml.

l The Group URL in CSS.xml is incorrectly defined

l An excessive number of groups are defined in the Group URL

Retrieving Users, Register Applications, and Load Security More Quickly Perform the following procedure to perform these tasks faster:

l Retrieve lists of users against projects

l Register applications

l Load security

ä To increase performance:

1 Always set a group URL.

2 Use native groups, not external groups, to provision external users. To use native groups for user provisioning,or if you do not use external groups, set the Group URL to LostAndFound as follows:

User Directories and Provisioning 51

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 Hyperion Security Administration Guide.

Listing Users and Groups if Over 100K Exist in an External User DirectoryPerform these steps:

1. Open CSS.xml in any text editor.

2. In the Native tag, add socketTimeOut as follows:

<native name=”Native Directory”><socketTimeOut>60000</

socketTimeOut><password>{CSS}4N6 |VcgiE/dGr8rFdvQLcA==</password></

native>

3. Save and close the file.

Performing WebDav Calls on WebLogicPerform the steps for the WebLogic version:

Table 5 WebDav Calls on WebLogic

Version Procedure

8.1.6l Download ftp://support:[email protected]/pub/725734.zip.

l Add it to the classpath in the HSS start Server script.

This file is in C:\Hyperion\SharedServices\9.3.1\AppServer\InstalledApps\WebLogic\8.1\SharedServices9Domain\bin.

l In any text editor, open config.xml and scroll to <SecurityConfiguration>.

l Before Name=”SharedServices9Domain, add this code:

EnforceValidBasicAuthCredentials=”false”

l Save and close the file.

9.2l Open config.xml and scroll to <SecurityConfiguration>.

l Before Name=”SharedServices9Domain, add this code:

<enforce-valid-basic-auth-credentials>=false</enforce-basic-auth-

credentials>

l Save and close the file.


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

Resolving OpenLDAP Provider Startup Failure due to CorruptionPerform these tasks if the LDAP provider you use with Shared Services does not start becauseof corruption.

ä To start the LDAP provider:

1 Install the LDAP Browser from: http:\\www-unix.mcs.anl.gov\~gawor\ldap\download.html

2 Open ldapbrowser\bin\lbe.bat in any text editor.

3 Set JAVA_HOME to reference the JAVA_HOME directory.

4 Double-click LBE.bat and then New.

5 On the Name tab of the New Session box, enter a name for the connection.

6 Click Connection and enter the name of the computer where OpenLDAP is installed.

7 Enter 58089 as the port.

8 In Search Base, enter dc=css,dc=Hyperion,dc=com.

9 In UserDN, enter cn=911,ou=people,dc=css,dc=Hyperion,dc=com.

10 Select Append Base DN 11.

11 In Password, enter the password for the admin user.

12 Click Save.

13 Select HSS OpenLDAP and click Connect.

14 From a command line, start OpenLDAP as follows:

a. Enter: cd c:\\Hyperion\SharedServices\9.3\openLDAP or:%HYPERION_HOME%\SharedServices\[ver]\openLDAP

User Directories and Provisioning 53

b. Enter slapd —d 1.

OpenLDAP IssuesThis section contains solutions to errors you may encounter using OpenLDAP.

Avoiding OpenLDAP Issues Perform these tasks to ensure that OpenLDAP works correctly:

l Do not manually shut down the computer hosting OpenLDAP

l Do not terminate the OpenLDAP process from the task manager

l Do not terminate the OpenLDAP process when data is being written

l Restore OpenLDAP and the database used with Shared Services simultaneously to ensuresynchronization

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


Causes of OpenLDAP CorruptionOpenLDAP becomes corrupt when manually shut down, because of sudden power loss, orbecause of a power loss while the service is running. To avoid OpenLDAP corruption, note thefollowing:

l Do not manually shut down the computer hosting OpenLDAP.

l Do not terminate the OpenLDAP process from the task manager.

l Do not terminate the OpenLDAP process when data is being written.

l Restore OpenLDAP and the database used with Shared Services simultaneously.

l Perform weekly cold backups on both the OpenLDAP and the Shared Services databases.

Using CSS.XML to Resolve Connection FailuresChange the host name in CSS.xml or to an IP address.

For example, in c:\Hyperion\SharedServices\9.3\AppServer\InstalledApps\Tomcat\5.0.28\CSS.xml, replace “hostname” with the IP address of the OpenLDAP server:

<hub location="http://hostname:58080">

<dirPort>58089</dirPort>

</hub>


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 the Hyperion Security Administration Guide.

Decreasing the Login TimePerform these steps:

1. On 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. See “Setting the Maximum Size” on page 53.

2. Use CSS Spy to check connections to, and the performance of, the user directory.

Resolving Problems Accessing Products from SharedServicesYou may be unable to log into other Hyperion 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 CSS.xml 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.

Startup and Access Issues 55

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.

Logging in Using the Default Admin UsernameIf you can not log in using the admin username, the user may not be provisioned. Perform thesetasks:

1. Log on to the User Management Console using the admin account.

2. Provision the admin user with the appropriate role for the product.

Logging in to the User Management Console Using a ProxyServerPerform these steps:

1. On the computer where the Shared Services Server resides, open Microsoft Word.

2. Select File > Open and enter: http://<HSS_Server>:58080/interop/content.

3. When prompted, enter the Shared Services user ID and password (by default, admin andpassword).

4. Locate .instance by selecting File > Open and browsing to: Content on hp93\files\Products\HAVA-9.3.0\Published. Ensure you select Show All Files in Order to list allof the files that you may need.

5. Right-click the file and select Context > 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.

Resolving a Shared Services Startup Failure on theApplication ServerYou may be unable to start if the port number is being used by another application, or if theShared Services libraries definition is incorrect. Open <WAS>\WebSphere\AppServers\logs\server1\SystemOut.log. If you cannot find Default.xml, perform these tasks:

l Ensure that the Shared Services Libraries definition is correct and that each class is on itsown line.


Libraries are defined for interop.war.

l Correct the settings of the <HYPERION_HOME> environment variable.

l Determine whether the default port 58080 is being used by another application. Run“NETSTAT –an | findstr 0.0.0.0:58080”. If you get (0.0.0.0:58080), change theShared Services port or stop the process that is using the port.

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

l “Essbase — System 9” on page 57.

l “Reporting and Analysis” on page 59

l “Applications+” on page 61

For help with installing and configuring these products independently of Shared Services, see:

l Chapter 7, “Troubleshooting Essbase – System 9”

l Chapter 8, “ Troubleshooting Reporting and Analysis”

l Chapter 9, “Troubleshooting Financial Performance Management Applications”

l Chapter 10, “Troubleshooting Data Management ”

Essbase — System 9This section provides solutions to questions you may have using Essbase products with SharedServices. See Chapter 7, “Troubleshooting Essbase – System 9”.

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_install>\bin, rename essbase.bak_preUPM as essbase.sec.

b. Create a native user with admin privileges.

c. Externalize this user using password as the password.

d. Log on to Essbase as the new user.

Resolving Product-Specific Issues 57

e. In Shared Services, search for the user in Native Directory or in an external directoryand provision it to Essbase as admin.

f. In Essbase, refresh security. See the Hyperion Essbase — System 9 DatabaseAdministrator's Guide.

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 CSS.xml 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 OpenLDAP Corruption Without a Backup

Perform these tasks if OpenLDAP becomes corrupt:

1. Back up the Shared Services database.

2. Restore OpenLDAP and the database simultaneously. This synchronizes the Shared Servicesdatabase and OpenLDAP files.

3. Restart Shared Services and navigate to: http:\\servername:58080\interop\framework\login

4. Select Sync with OpenLDAP.

5. Launch Essbase.

6. Rename essbase.bak_preUPM to essbase.sec. This renames the older file.

7. Put essbase.bak_postUPM in another folder. This returns Essbase to pre-externalizationstate.

8. Install and configure Shared Services as follows:

a. Recreate the database tables

b. Deploy to the application server

c. Register with Administration Services and Essbase.

d. Reprovision users

e. Redeploy

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


Adding Essbase Provider Service Providers

You installed and configured Provider Services 9.3.0.1 on WebSphere 5.1.1.9 on Windows 2k3SP1. You cannot add a provider to Administration Services and receive these errors:

l In SystemErr.log: 4b8f06a2 SystemErr java.io.FileNotFoundException:\redist\version.xml (The system cannot find the path specified).

This file does exist in the D:\Hyperion\AnalyticProviderServices

\redist directory

l In SystemOut.log: Error accessing the properties file.essbase.properties: essbase.properties (The system cannot find the

file specified). Using default value

To resolve this issue, add a generic JVM argument to the APS WAS server of -DESS_ES_HOME=D:\Hyperion\AnalyticProviderServices and restart.

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 Hyperion Configuration Utility.

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 resolve this issue, perform these tasks:

1. Ensure that the user directory server used for authentication is available on the correct port.If it is not, insert HOST entries for the correct IP address as follows:

a. Stop Essbase on the server.

b. Create a backup copy of css.jar.

c. Rename css.jar to css.zip.

d. In WinZIP, open css.zip and CSSClientLogger.properties.

e. In CSSClientLogger.properties, change WARN to DEBUG and uncomment the logfile location.

2. Save the file and update the archive.

3. Save css.zip as css.jar.

4. Restart Essbase services.

Reporting and AnalysisThis section provides solutions to errors you may encounter configuring and using SharedServices with Reporting and Analysis. See Chapter 8, “ Troubleshooting Reporting andAnalysis”.


Resolving a “404 Error: UnsatisfiedLinkError- getOSVersion” ErrorYou automatically deployed Workspace to Tomcat. You configured an NTLM provider forShared Services (host name unspecified).

To resolve this issue, perform these tasks:

1. Open startWorkspace.bat in any text editor.

2. Add <CSS_HOME>/bin to PATH.

3. Save and close the file.

4. Launch Workspace using startWorkspace.bat.

Changing the DNS Name or the Workspace ServerIf you change the DNS name of the Workspace server and have a large number of provisionedusers (more than 2500), you may need to update the instance files manually as follows:

1. Set a network place to the Shared Services Server: /interop/content.

2. Launch Microsoft Word for Office 2003.

3. Select File > Open, browse to Network Places and select the .instance files.

4. Right-click and select Editable Text to modify the files.

Starting Core ServicesYou installed Reporting and Analysis 9.3.0.1 on Windows 2K3 SP1 with Tomcat, cannot startthe services, and receive this error:

Error configuring security platform - Cannot configure the system.

Please check the configuration.Error code: 9 Provider: null

com.brio.one.common.BaseException: Error configuring security platform

- Cannot configure the system. Please check the configuration. null at

com.brio.one.services.utils.css.CSSAccess.initializeCSS(Unknown Source)

at com.brio.one.services.utils.css.CSSManager

To resolve this issue, check the v8_prop_value table to ensure these entries are set inthevalue0 column:

l ConfigurationManager.hubHost references the Shared Services host name.

l ConfigurationManager.hubport references the Shared Services port.

l ConfigurationManager.hubUseSSL is true/false.

l ConfigurationManager.cssConfigURL Copy and paste this URL in a browser windowto get CSS.xml from Shared Services.

l ConfigurationManager.applicationId references the ID of the application registeredwith Shared Services. Note: This ID must correspond with the Shared Services database.


Applications+This section provides solutions to errors you may encounter configuring and using SharedServices with Financial Management and Performance Scorecard. See Chapter 9,“Troubleshooting Financial Performance Management Applications”.

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

Resolving an “Application Creation Fails: %0% 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.

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 time-out 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, re-install and configure the other products, and then install and configurePerformance Scorecard.


6General Tips for all Hyperion

Products

In This Chapter

Resolving Connection Failures and Restarting Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Upgrading Tip: Software Compatibility .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Installation Tips ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Configuration Tips ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

UNIX Tips... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Resolving Connection Failures and Restarting ServicesServer failures are usually due to a failed connection.

ä To connect to the server:

1 On the server where the Hyperion product is running, select Start > Programs > Administrative Tools >Services.

2 Check whether the service is started and set to start automatically on reboot. If not, start the service.

3 If the service is running and you have connection problems, stop and start the service.

If you cannot regain functionality with these steps, contact Support.

Starting and Restarting ServicesSome problems may be caused if services required for a product are not running. Other problemsthat may occur may be fixed by restarting the service to restore a clean operating environment.

ä To restart the service:

1 From the Windows Server desktop, select Start > Settings > Control Panel > Administrative Tools >Services.

2 Right-click the name of the service and perform a task:

l If the service is running, select Restart.

l If the service has stopped, select Start.

Resolving Connection Failures and Restarting Services 63

Verifying Services in the Windows Task ManagerYou can verify that the service is running by using Windows Task Manager.

ä To verify the service in Windows Task Manager:

1 From the keyboard, press Ctrl+Alt+Delete.

2 In Windows Securitywindow, click Task Manager.

3 In Windows Task Manager, select Processes.

4 Locate the name of the executable for that product.

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.

Upgrading Tip: Software CompatibilityIssue: A product you upgraded does not work correctly with older versions of Hyperionproducts.

Solution: Before upgrading Hyperion products, ensure that existing versions are compatiblewith the new releases. In some cases, a new version of a product may only be compatible withanother recent version, and you must upgrade multiple products. For example, in the 9.3.1release, Planning 9.3.1 requires Shared Services 9.3.1. See “Release Compatibility” in theHyperion Installation Start Here.

Installation Tips

Installation DirectoryIssue: Installation fails because you installed a product to a directory containing spaces, such asProgram Files. Hyperion products do not support installing to a directory with spaces.

Solution: Uninstall the product and then reinstall to a directory without spaces.

Cannot Install After UninstallingIssue: You experience problems after uninstalling and then installing again.

Solution: Follow one of these procedures:

l When reinstalling only one Hyperion release 9.3.1 product:

1. Delete the HYPERION_HOME environment variable.

2. Remove vpd.properties file from c:\windows.

64 General Tips for all Hyperion Products

l When reinstalling two or more Hyperion release 9.3.1 products, use alternate targetdestinations for the new installations (The vpd.properties file may contain entriesremaining from the previous home directory used for the product.)

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

Errors During ConfigurationIssue: You fail to configure, or receive errors during configuration.

Solution: Review the Hyperion Configuration Utility log in: <HYPERION_HOME>\logs\config\configtool.log. As a troubleshooting measure, perform configuration tasksindividually for one product or component at a time.

Failure Deploying to Application Server WithoutConfiguration ErrorsIssue: A Hyperion product is not deployed to the application server, but there are noconfiguration errors.

Solution: Review configtool.log. This file records any errors in the deployment process. Ifno errors are identified, redeploy to the application server.

WebLogic 8.1.4 Deployment ErrorEnvironment: 64-bit on HP-UX

Error: Un-supported version of Weblogic is entered for the location

Solution: Ensure that the BEA Home and BEA installation location that you entered duringconfiguration are the same as those in $BEAHOME/registry.xml.

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.

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

Configuration Tips 65

Hyperion Configuration Utility Startup Failure Issue: You cannot run configtool.sh if the name of the computer contains duplicatecharacters.

Solution: Modify configtool.sh as follows.

ä To modify configtool.sh:

1 Open configtool.sh from <HYPERION_HOME>/common/config.

2 Go to this code:

SHORT_HOSTNAME=hostname | cut -d . -f 1 | tr -s '[A-Z]' '[a-z]'

3 Remove | tr -s '[A-Z]' '[a-z].

4 Save and close the file.

5 Run configtool.sh.

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

File Descriptor Limit ErrorError: File descriptor soft limit is 256, but must be at least 1024.

Solution: Perform these tasks:

l Increase the soft file descriptor limit and run the Hyperion Configuration Utility.

l Update <Hyperion_Home>/common/config/configtool.sh after commenting thelines in the header with ulimit –n 1024.

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.

UNIX Tips 67

7Troubleshooting Essbase –

System 9

In This Chapter

Essbase .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Administration Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Integration Services... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Provider Services... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

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 tableidentifies some of those issues, along with possible solutions:

Error Message or Problem Solution

The JVMMODULELOCATION environment variablehas not been correctly set in essbase.cfg.

Set the environment variable. See the Hyperion Essbase —System 9 Installation Guide.

Error: Fatal Error: Essbase isalready loaded

The Essbase agent is already running.

Check to see if Essbase is running:

1. On Windows platforms, check the Windows Task Managerfor the essbase.exe process

2. UNIX: Use ps -fu <username> | grep -iessbase to check for the essbase process.

If Essbase is not already running, then another user may berunning a process on the port setting you have specified forEssbase in essbase.cfg. For instructions on shutting downEssbase, see “Running Essbase Servers, Applications, andDatabases” in the Hyperion System 9 — Essbase DatabaseAdministrator's Guide.

Error: Failed in GCInit()

This error can mean that the ARBORPATH (Essbaseinstallation location) environment variable is notset correctly.

Check the ARBORPATH:

l Windows: In the command line, enter > echo<ARBORPATH>

l UNIX: In the console window, enter > echo $ARBORPATH

Essbase 69

Error Message or Problem Solution

If the ARBORPATH is missing or incorrect, define the correctARBORPATH. See the Hyperion Essbase — System 9Installation Guide.

Error: ESSBASE: not found

This error can mean that the essbase executableis not in the environment path.

Define an ARBORPATH.

If an ARBORPATH is already defined, then add the following tothe path:

l On Windows platforms, add <ARBORPATH>\bin

l On UNIX platforms, add $ARBORPATH/bin

Essbase will not start. Attempt to start Essbase from a DOS prompt if it will not startfrom the icon. More error messages are displayed when Essbaseis started from a DOS prompt, enabling you to troubleshoot. Forexample, messages about missing or inaccessible files may bedisplayed.

Essbase Installer Error Issue: The following error is displayed when you start the installer:

Initializing InstallShield Wizard...

Preparing Java(tm) Virtual Machine...

Error writing file

Solution: Increase your temp space by referencing another temp directory. On UNIX, enter:setup.bin -is:tempdir /home/usr

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.

Administration ServicesThe following sections describe common Administration Services issues.

70 Troubleshooting Essbase – System 9

Administrator Login Failure Environment: Administration Services with Business Rules.

Issue: Administrator cannot log in.

Solution: Use the Hyperion Configuration Utility to deregister Administration Services fromShared Services, (sometimes you have to do this more than once). From Shared Services, removeOracle's Hyperion® Business Rules project. See the Essbase Administration Services InstallationGuide.

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 User Management 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). See the Essbase Integration Services Installation Guide.

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's Essbase® Integration Services Server

m The database servers that manage OLAP Metadata Catalog and the data source databases

m The data source database listener for OLAP Metadata Catalog and the data source

Integration Services 71

l Ensure that the OLAP Metadata Catalog and the data source are configured as ODBC datasources on the Integration Server computer. See the Essbase Integration Services InstallationGuide.

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, editStartAPSWebLogic81aps.bat and modify the settings for the set JAVA_OPTIONS defaultvalue 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's Hyperion® Provider Services page.

Solution: Comment out Include conf/mod_jk2.conf line in <Apache_HOME>/conf/httd.conf, and then restart Apache.

72 Troubleshooting Essbase – System 9

8Troubleshooting Reporting and

Analysis

In This Chapter

Tips and Recommendations ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

General Errors .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Interactive Reporting Studio ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Financial Reporting .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Web Analysis .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Tips and Recommendationsl Complete configuration information about your 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 Hyperion Installation Start Here.

l When you install Reporting and Analysis in a distributed environment, you must run theHyperion Configuration Utility on every computer, ensuring that you are using the correctcomputer names.

l Check the stdout_console.log in <BIPLUS_HOME>\logs for information on startupfailures. See Chapter 4, “Logs.”

General ErrorsThis section contains general Reporting and Analysis installation and configuration issues.

Failure to Access ModulesIssue: User cannot access any modules.

Solution:

l Contact the administrator to verify user privileges.

l Check that context.properties was created during auto deployment or that it wascreated manually for manually deployed configurations.

Tips and Recommendations 73

Connection FailureEnvironment: In a distributed environment.

Issue: Failure to connect to servers.

Solution: Be sure that you run the Hyperion Configuration Utility 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.

Interactive Reporting StudioThis section contains Oracle's Hyperion® Interactive Reporting Studio installation andconfiguration issues.

Essbase Not Loaded SuccessfullyIssue: When connecting to Essbase, this error displays: “Essbase not loadedsuccessfully”.

Solution: Ensure that these environment variables exist and reference the correct Essbaseinstallation location:

l ARBORPATH

l Path (for Windows)

l LD_LIBRARY_PATH (for Solaris and Linux)

l SHLIB_PATH (for HP-UX)

l LIBPATH (for AIX)

Faulty Oracle Net ConnectionIssue: When attempting an Oracle Net connection “SQL*Net not loaded successfully”is displayed.

Solution: Ensure that the following environment variables exist and point to the correct Oracleinstall location:

l ORACLE_HOME

l Path (for Windows)

l LD_LIBRARY_PATH (for Solaris and Linux)

l SHLIB_PATH (for HP-UX)

l LIBPATH (for AIX)

74 Troubleshooting Reporting and Analysis

Failure Processing an Oracle ProcedureIssue: When processing an Oracle procedure with Oracle Wire Protocol ODBC client, this errordisplays: “PLS-00306: wrong number or type of arguments in call to<procedure_name>”.

Solution:

l Windows: On the Advanced tab of the ODBC Oracle Wire Protocol Driver Setup box, selectProcedure Returns Results.

l UNIX: Open odbc.ini, set the ProcedureRetResults property to 1 for your Oracle WireProtocol data source.

Fonts Display Incorrectly Issue: Data is truncated or overlapping when an Oracle's Hyperion® Interactive Reporting –System 9 document (bqy) is viewed by a thin client on UNIX platforms. It could also mean thatthe correct font is missing.

Solution: Check the FONT_PATH variable in set_common_env.sh. This file is in$<AVALANCHE_HOME>/bin. FONT_PATH must contain the same font used in bqy.

Financial ReportingThis section contains Financial Reporting installation and configuration issues.

Invalid User Name Error When Starting Financial ReportingStudioEnvironment: A new installation in a distributed environment where Financial Reporting is ina different server than Shared Services.

Issue: “invalid user name” error when trying to run Oracle's Hyperion® Financial ReportingStudio.

Solution: Copy these .JAR files from the Shared Services server to the Financial Reporting server:

<HYPERION_HOME>\deployments\<AppServerNameAndVersion>\bin\SharedServices9\webapps\interop\WEB-INF\lib

%HYPERION_HOME%/common/SharedServices/9.3.1/lib/bsf.jar

%HYPERION_HOME%/common/SharedServices/9.3.1/lib/quartz.jar

%HYPERION_HOME%/common/SharedServices/9.3.1/lib/rhino.jar

%HYPERION_HOME%/common/SharedServices/9.3.1/lib/scheduler.jar

%HYPERION_HOME%/common/SharedServices/9.3.1/lib/wf_eng_agent.jar

%HYPERION_HOME%/common/SharedServices/9.3.1/lib/wf_eng_api.jar

Financial Reporting 75

Missing PlanningSystemDB.properties FileIssue:

l In a new installation, users cannot create a Planning Details data source connection.

l In an existing installation, users cannot connect to reports.

Solution: Copy PlanningSystemDB.properties from the Planning server to these two placeson the Reporting and Analysis server:

hyperion/common/adm/planning/9.3.1/lib

Hyperion/biplus/lib

Error Running Financial Reporting Studio on the DesktopEnvironment: Financial Reporting Studio is running on the desktop.

Issue: Error, Active X 429.

Solution: Run the Hyperion Configuration Utility.

Runtime and ActiveX ErrorsIssue: A series of runtime and ActiveX errors is displayed during Oracle's Hyperion® FinancialReporting Studio login.

Solution: Run <BIPlus>\install\bin\HRRunAnt.cmd, reboot, and log in.

Web AnalysisThis section contains Oracle's Hyperion® Web Analysis – System 9 installation and configurationissues.

Error Connecting to SAP BWIssue: “Unable to retrieve list of available cubes” displays when you connect toSAP BW during data source creation in Oracle's Hyperion® Web Analysis Studio.

Solution: Install and configure SAP JCo. See “Configuring SAP Data Source Access andAuthentication” in the Hyperion Reporting and Analysis - System 9 Installation Guide.

BEx Query Not ListedIssue: BEx Query is not listed in the Available Databases pane when you create a new data source.

Solution: In SAP Business Explorer, change the properties of BEx Query to allow external accessto the query.

76 Troubleshooting Reporting and Analysis

9Troubleshooting FinancialPerformance Management

Applications

In This Chapter

Common Planning Issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Common Financial Management Issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Common Performance Management Architect Issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Common Performance Scorecard Issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Common Strategic Finance Issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Common Planning Issues

Note:

If you experience problems installing or running Shared Services or have issues with externalauthentication, see Chapter 5, “Troubleshooting Shared Services and Provisioning .” Forinformation about error logs, see Chapter 4, “Logs.”

Planning Access

Failure Accessing Planning through WorkspaceIssue: You get an error message when trying to access Planning through Workspace.

Solution: Perform these steps:

1. Test access to the Workspace. Use this URL: http://<Web Server>:<port>/workspace/ where <Web Server> is the Web server machine hostname and <port> isthe Web 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 Workspace proxy server plug-in. If it is configured, test that you can access Planning directly.

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

Common Planning Issues 77

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

Upgrading Issues

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.

Updating .Properties Files to Upgrade to 9.3.0.1Issue: You are upgrading from an earlier release to Planning 9.3.0.1 and are not using the sameservers to host your database and Essbase server or are not using the same passwords.

Solution: If you are upgrading from Planning 9.2.x to 9.3.x, update a setting in the oldHspJSHome.properties BEFORE using the Property File Migration Utility in 9.3.0.1. ThePropFileMig.cmd in 9.3.0.1 is designed for an “in-place” upgrade. For example, it upgradesto the same servers hosting SQL and Essbase, using the same user names and passwords. It alsouses the same location for css.config.

Before running the PropFileMig.cmd utility, ensure that HspJSHome.properties has thecorrect information to transfer to the new 9.3.x environment. To restore existing applicationsto new locations, you must manually change the information in HYPSYS_Properties andPlanningSystemdb.properties before running the utility. Otherwise, the information isoverwritten in these files and the upgrade is not successful.

Folder StructureThe location of files is as follows:

l All .jar files are in the lib, not Utils folder

l All .exe, .bat, .sh, cmd and .exe files are in the bin folder instead of Utils

l ico and .properties files (essbase.properties, PlanningSystemDB.properties, andso on) are in the config folder instead of Utils

l Offline.exe and SmartView.exe are in the bin, not Deployment folder

78 Troubleshooting Financial Performance Management Applications

Planning InstancesIssue: Configuration of Planning requires creating a product instance. Because this is a newconcept, it can be confusing to existing customers.

Solution: Review the explanation from the Hyperion Planning — System 9 Installation Guideexcerpted here. An instance is a name for a group of Planning applications. An instance maycontain one or many applications.

When you create an instance, it displays in the HSPSYS_CLUSTER table in the system database.The active instance name gets written as the INSTANCE property value inPlanningSystemDB.properties.

You can designate an instance as the “active instance” during instance creation or at any timeusing the Product Instance Registration option in the Configuration Utility. If you designate aninstance as the “active instance,” only applications associated with that instance are displayed.Applications get associated with an instance when an application is created, and that associationcan be modified using the Re-associate Instance and Application task. Note that if you add orchange the active instance, you must restart the Planning application server in order for theupdated application list to be displayed in Workspace.

Configuring Planning with Reporting and AnalysisTo use Planning with Reporting and Analysis in release 9.3.1, you must install the Planning ADMdriver on the machine that is hosting Oracle's Hyperion® Financial Reporting – System 9. Toinstall on a different machine from Planning, use the Custom option to select the Planning ADMdriver.

Using Planning with Administration ServicesIssue: You cannot expand the Planning outline in Oracle's Essbase® Administration Services.

Solution: Turn on debugging and check the following items:

1. Check the RMI server is running properly.

2. Check Oracle's Hyperion® Essbase® – System 9.

3. Check security and external authentication.

4. Ensure that HBRServer.properties is in the same folder asPlanningSystemDB.properties. If not, copy it to the same folder.

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's Hyperion® Planning – System 9.

Common Planning Issues 79

Solution: Tune the Webserver or increase heap size, depending on your environment. Hyperionrecommends that you work with a consultant to assess your environment.

Common Financial Management Issues

Note:

If you experience problems installing or running Shared Services or have issues with externalauthentication, see Chapter 5, “Troubleshooting Shared Services and Provisioning .” Forinformation about error logs, see Chapter 4, “Logs.”

Accessing Financial Management

Failure Accessing Financial Management Through WorkspaceIssue: You are having difficulty accessing Financial Management.

Solution: Perform these steps:

1. Test access to the Workspace. Use this URL: http://<Web Server>:<port>/workspace/ where <Web Server> is the Web server machine hostname and <port> isthe Web 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 Workspace proxy server plug-in. If it is configured, test that 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: Check the following;

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.


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, clickStart, and restart the computer.

Database Connection FailsSolution: Configure the UDL file.

Connection to SQL Server Fails Issue: You receive an “SQL Server: Test connection failed because of an errorin initializing provider. Client unable to establish connection.” error.

Solution: A problem may exist with the Microsoft SQL Server connection and the .UDL file. See“Verifying Data Link Connection Settings” on page 82.

Issue: You are having difficulty connecting to SQL Server.

Possible Solutions:

l Windows authentication may have been used instead of Microsoft SQL Serverauthentication. Hyperion recommends using SQL Server authentication. See “VerifyingMicrosoft SQL Server Authentication Settings” on page 82.

Common Financial Management Issues 81

l The system may be using the Microsoft SQL Server default setting to connect to the databaseusing named pipes instead of TCP/IP. See “Establishing the SQL Server Connection UsingTCP/IP” on page 82.

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 > Settings > 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, andclick Next.

6 Select this authentication option: With SQL Server authentication using a login ID and password entered bythe 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

ä To verify data link connection settings:

1 In Data Link Properties, select Connection.

2 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 > Programs > Microsoft SQL Server > 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.

Failure Registering Financial Management Server on ClientMachineIssue: Cannot register the Financial Management server on a client machine.

Solution: On the Application Server Clusters tab in the Financial Management ConfigurationUtility, click Enable Limits. This enables Remote Activation and should be performed on themachine hosting the application server.

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 Workspacetime-out setting.

Common Performance Management Architect Issues

Installing and Configuring Performance ManagementArchitect This section contains troubleshooting tips for Performance Management Architect andinstallation and configuration issues you may encounter.

Installation FailsIssue: Performance Management Architect Installation failed.

Common Performance Management Architect Issues 83

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 Hyperion FinancialManagement— System 9 Installation Guide or the Hyperion Planning — System 9 InstallationGuide.

Accessing Performance Management Architect

Performance Management Architect Logon FailsIssue: You are having difficulty logging on to Performance Management Architect.

Solution: Ensure you are using ASP.NET 2.0.50727 and that ASP.NET and ASP pages are set to“Allowed”.

ä To check whether .NET 2.0 is installed on a Windows 2003 machine:

1 Open IIS Manager by doing one of the following:

a. Start > Programs > Administrative Tools > Internet Information Services Manager

b. Run inetmgr.

2 In the left panel, select Web Service Extensions. In the right panel, note whether ASP.NET 2.0.50727 islisted.

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.

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 HyperionSecurity Administration Guide.

Failure Logging on toWorkspaceSolution: Ensure that you have followed the installation and configuration instructions forWorkspace in the Hyperion Reporting and Analysis Installation Guide.


Failure Starting the Process Manager ServiceIssue: Cannot start Process Manager service.

Solution: Check whether you've changed the Shared Services admin user or password. If so,launch the Oracle's Hyperion® Configuration Utility™ and run the Configure Database task forPerformance Management Architect.

Failure Displaying the Dimension Library in Performance ManagementArchitectIssue: You cannot see the Dimension Library in Performance Management Architect.

Solution: Verify that you have the proper 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 Hyperion Security Administration Guide. Afteryou are assigned the Dimension Editor role, log off and log back on to Performance ManagementArchitect.

Failure Displaying Tasks in Performance Management ArchitectCheck the following:

l Verify that the Shared Services server is started, and if not, start it. See the Shared ServicesInstallation Guide.

l Verify that Workspace services are started. See the Hyperion Reporting and AnalysisInstallation Guide.

l Verify that you can access Workspace. Use this URL: http://<Web Server>:<port>/workspace/ where <Web Server> is the Web server machine hostname and <port> isthe Web server listen port, for example, 19000 if using the Apache instance configured withReporting and Analysis.

l Verify that you have configured the Workspace proxy server plug-in for your ApplicationServer. Use this URL:http://<Web Server>:<port>/awb/conf/AWBConfig.xmlwhere <Web Server> is the Web server machine hostname and <port> is the Web serverlisten port; for example, 19000 if using the Apache instance configured with Oracle'sHyperion® Reporting and Analysis – System 9.

If you can access this URL, the proxy server is configured. If you cannot, configure it. Seethe Hyperion Reporting and Analysis Installation Guide.

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.


Server Unable to Process Request ErrorIssue: You receive a “Server was unable to process request. No connectioncould be made because the target machine actively refused it

(org.apache.axis.AxisFault) error.

Solution: Start the Dimension Server and retry.

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 inWorkspace. Reconfigure Oracle's Hyperion® Workspace.

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_machinename>/hyperion-bpma-server/Sessions.asmx.

If you see a Sessions page displayed, then IIS is correctly configured. If there is any error inIIS, check the Event Log to determine the problems. Check the System and Application Logto see if anything was logged by ASP.NET, IIS, or DCOM, and fix the errors. A possible causeis incorrect 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 Configuration.

2. Remove values in the wildcard mapping section.

Problems Opening the BPM Architect Dimension LibrarySolution: Verify that DCOMCNFG permissions are set properly in Windows 2003.

ä To set DCOM Config permissions:

1 Select Start > Run, and enter DCOMCNFG .

2 Expand Component Services > Computers > My Computer > 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.

IIS Startup Failure on Performance Management Architect DimensionServerFrom Control Panel > Administrative Tools > Services, start World Wide Web PublishingService, if not already started.

Performance Management Architect Services Startup FailureSolution: Start the Performance Management Architect Process Manager service if not alreadystarted. Then check that these services start:

l Engine Manager

l Event Manager

l Job Manager

Using IBM DB2 with Performance Management ArchitectIssue: You experience performance issues using an IBM DB2 database with Oracle's EnterprisePerformance Management Architect.


Solution: Implement the settings described in the Hyperion Financial Management— System 9Installation Guide or Hyperion Planning — System 9 Installation Guide.

Common Performance Scorecard Issues

Configuration Issues

Java.lang.NoSuchMethod ErrorIssue: Receive a java.lang.NoSuchMethodError error after installing and configuringmultiple products.

Solution: You receive a java.lang.NoSuchMethodError error if you install and configurePerformance Scorecard before other products, such as Shared Services. To resolve this issue,uninstall and reinstall the other products, and then install Performance Scorecard.

Application Server Issues

Exception in Browser Issue: You receive an application server exception in the browser after starting the applicationserver.

Solution: If you deployed to an existing application server, remove the HPSWebReports andHPSAlerter directories before re-installing.

Check the log file for the application server for information about the error you received.

Multiple, Different Port NumbersIssue: There are different port numbers for each application server type.

Solution: Although you can have several versions of Tomcat on the same computer, each instancemust have a unique port number. View the ports being used by opening a DOS console andentering netstat -a.

Insufficient Authorization ErrorIssue: After performing configurations and clicking Reload, you receive this error:

“You do not have sufficient authorization to perform the requested

action.Contact your Administrator to get this authorization”

Solution: Restart the application server.


DIM Adapter for Performance Scorecard Issue: You receive this error message

MAPPING> [PMJVM_42023] [ERROR] Failed to load the JVM library

Solution: Configure Informatica PowerCenter to use JVM. See the “Configuring the JVMOptions Tab” topic in the Informatica PowerCenter Installation and Configuration Guide.

Performance Issues

Problems Load Balancing in Clustered DeploymentIssue: Load balancing is problematic for multiple applications deployed to a cluster.

Solution: If you install and run multiple instances of Performance Scorecard, configure eachinstance using the clustered deployment option. Also ensure that each instance uses the samedatabase that is accessed from a shared network drive.

Lengthy Application Startup Time Issue: Using Tomcat, the startup time for an application created in a previous release is too long.

Solution: Decrease the startup time.

ä To decrease startup time:

1 Increase the cache values in startTomcatforHPS.bat or startHPS.bat.

2 Increase the cache values in the JRE console.

3 Shutdown Performance Scorecard.

4 Open HPSConfig.properties in any text editor and make these changes:

l log4j.logger.hpmd.startup=DEBUG.

l Increase these entries:

m hyperion.hps.formula.value_caching_limit

m hyperion.hps.datapoint.cached_result_limit

m hyperion.hps.datapoint.cached_target_limit


6 Restart the application server and Performance Scorecard.

Frequent Session Time-outsIssue: Current sessions are timing out too quickly.

Solution: Perform these steps to extend the session time-out.

Common Performance Scorecard Issues 89

ä To increase the time-out:

1 Shut down Performance Scorecard.

2 From <application server>\webapps\HPSWebReports\WEB-INF, open web.xml.

3 Modify the default value of 30 in the code below as needed to increase the session time-out.

<session-config> <session-timeout>30</session-timeout></session-config>

Note:

Note: If you extend this value beyond 60, and have configured for single sign-on and externalauthentication, modify HyperionCSS.xml to extend the token time-out. This file is in<application server install>\webapps\ HPSWebReports\WEB-INF\config.

4 Modify this section of code:

<token><timeout>60</timeout></token>


6 Restart the application server and Performance Scorecard.

Common Strategic Finance Issues

Performing Diagnostics on Strategic Finance ServiceHyperion Strategic Finance Service is the service running on the server. To collect diagnosticinformation and troubleshoot problems, you must be logged on to the system with fulladministrator privileges. Diagnostics can be performed directly on the server or using a remoteaccess program. Use event logs and other logs to debug the system. See the Hyperion StrategicFinance Administrator’s Guide.

Server Memory and Error LogsIf you receive an “Access violation at breakpoint c0000005” or “Not enoughstorage space available to process this command” error, restart the StrategicFinance Server.

Using NovellTo use Novell, copy all Novell users into an LDAP security provider, and then configure StrategicFinance for external authentication. If you have not copied Novell users to a security provider,set up Oracle's Hyperion® Strategic Finance users in another trusted security provider beforeconfiguring for external authentication.



Common Strategic Finance Issues 91

10Troubleshooting Data

Management

In This Chapter

Common Data Integration Management Issues... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Common FDM Issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

Common Data Relationship Management Issues... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

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

Connection IssuesThese are some issues that you may encounter when connecting to Data IntegrationManagement.

Service Stops after StartingIssue: The Hyperion Data Integration Management Server service stops immediately afterstarting, and the Workflow Monitor displays this error message: Cannot connect to theserver HyperionIntegrationServer.

Solution:

1. Start the service:

l Windows

Select Start > Settings > Control Panel > Administrative Tools > Services and trystarting the services manually.

l UNIX

Run start_pmserver.sh from DIM_HOME/Resources/bin.

2. If the server process starts and stops immediately:

a. Open Workflow Manager.

b. Connect to the repository.

c. Double-click HyperionIntegrationServer.

Common Data Integration Management Issues 93

d. Select a compliant code page from the Code Page list. See the InformaticaPowerCenter Installation and Configuration Guide, Appendix B: Code Pages.

See “Accessing Informatica Documentation” in the Data Integration ManagementInstallation Guide.

3. Restart the service.

Configuration Errors

Cannot Connect to the Server Hyperion Integration Server

Issue: Unable to run workflow since changing the IP address of the Oracle's Hyperion® DataIntegration Management Server or Informatica PowerCenter Server.

ä To refresh the IP address:

1 Launch Workflow Designer.

2 Connect to your repository.

3 Right-click HyperionIntegrationServer.

4 Select Edit.

5 Verify server Host Name/IP Address.

6 Click Resolve Server.

7 If successful, click OK. Otherwise, determine and correct any network resolution issues.

Failed to Load the JVM Library

Issue: In Oracle's Hyperion® Data Integration Management Adapter for Performance Scorecard,attempting to run a workflow containing Oracle's Hyperion® Performance Scorecard – System9 sources or targets result in this error message: MAPPING> [PMJVM_42023] [ERROR]Failed to load the JVM library

Solution: Configure Informatica PowerCenter to use JVM. For instructions, see the topic,“Configuring the JVM Options Tab” in the Informatica PowerCenter Installation andConfiguration Guide.

The following plug-in has performed an illegal operation

Issue: You have version 7.1.3 of Informatica PowerCenter installed, rather than 7.1.4.

Solution: Install version 7.1.4.

Required Passwords During Configuration

Issue: Two passwords are required during configuration: one for Repository Manager and onefor the Repository Server Admin Console.

94 Troubleshooting Data Management

Solution: Ensure that you enter the correct passwords during configuration.

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

Configuration Issues with Financial ManagementIssue: “Server/cluster is incorrectly configured. Please reconfigure your Cluster or Serverconnection”

Solution: Update the machine profile in the workbench to point to the appropriate FinancialManagement cluster registered on the Oracle's Hyperion® Financial Data Quality Managementapplication servers.

Oracle Client/Provider Cannot Connect to DatabaseIssue: You receive a “ORA-12154: TNS; could not resolve service name error.

Solution: Correct outstanding Oracle issues, and ensure that you can resolve the TNS names intnsnames.ora.

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 Go to Adapter tab.

3 Open machine profile.

4 If there is a global ID, ensure the user's password is correct.

5 Ensure the user has proper security level to access target system's metadata.

Cannot Perform Bulk InsertError: Could not bulk insert because file '\\<servername>\<sharedfoldername> \<application foldername>\Inbox\<filename>.fmt' could not

be opened. Operating system error code 5 (error not found)”

Common FDM Issues 95

Solution: Ensure that the user who runs the SQL service has access to the UNC share and Readpermissions to the application.

ä To check access:

1 Check the SQL server to see which user is running MSSQLServer service. If local account, change to domainand give user sharing permissions and read permissions to application.

2 Launch Enterprise Manager and check roles for the user that created the database. Make sure user has BulkInsert Rights.

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 Installing on Windows 2000 Server

l Upgrade May Get Error after Reboot

l Daylight Savings Time Offsets for As Of Versions (Release 9.3.0.x only)

l Compatibility with Microsoft Data Execution Prevention (Release 9.3.0.x only)

l Running Data Relationship Management with Oracle's Hyperion® Financial Management– System 9 (Release 9.3.0.x only)

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, username 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.


Failure Installing on Windows 2000Issue: When running the installer for a Complete installation on Windows 2000 SP4, the installercould display the “interrupted prior to completion” message. All components appear to havebeen installed successfully, but the database is not created and config.xml is not fullypopulated.

Solution: Run the installer and select Repair.

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.

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's Hyperion® Data Relationship Management server fails to start.

Solution:

l If you changed the classpath or system path, you must reboot the computer.

l Change the authentication mode to “Internal” and start the server again. If it startssuccessfully, this confirms that the issue is related to CSS.

l Check the Event Log for error messages

Common Data Relationship Management Issues 97

Upgrade Issues

Error Message Incorrectly Displays During UpgradeIssue: An error may appear during an install upgrade: “Service Hyperion S9 Master DataManagement” failed to install with error: “System Error. Code: 1073. The specified servicealready exists”

Solution: Ignore message by clicking OK and upgrade completes successfully.


Index

Aabout this guide

assumed knowledge, 9audience, 9purpose, 9

accessArchitect, 84Architect Dimension Server WebServices, 86denied, Data Relationship Management, 96Financial Management applications, 80Planning, 77Planning from Workspace, 77products from Shared Services, 55Reporting and Analysis modules, 73

Apache logs, 44application server

logs, 43Oracle 10.1.2.0.2 and Shared Services, 50Performance Scorecard issues, 88startup failure, Shared Services, 56

application server deploymentfailure without configuration errors, 65load balancing in cluster, Performance Scorecard,

89WebLogic version unsupported, 65

Architectaccessing Dimension library or Application library,

85accessing server Webservices, 86displaying Dimensions Library, 85displaying tasks, 85errors on server, 86IIS startup on Architect DimensionServer, 87installation failure, 83logon, 84opening dimension library, 87services startup failure, 87

assumed knowledge, 9

BBEx query unavailable, Web Analysis, 76browser exception, Performance Scorecard, 88Business Rules logs, 37

Ccannot authenticate user, Financial Data

Management, 95cannot connect to Oracle database, Financial Data

Management, 95cannot perform bulk insert, Financial Data

Management, 95common diagnostics tasks, initial diagnostics, 15common issues

Architect, 83Data Integration Management, 93Data Relationship Management, 96Financial Data Management, 95Financial Management, 80Performance Scorecard, 88Planning, 77Strategic Finance, 90user directories and Shared Services, 51

common log location, 19configtool.log, 13configtool_err.logn, 12configuration

Data Integration Management, 94Data Relationship Management, 97error log, 12exceptions, logged, 13file descriptor limit error, 66Financial Data Management, 95general tips, 65Shared Services, 49validation, 12, 15

Configuration Utility

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

Index 99

launching on UNIX, 66logs, 20

connection failureData Integration Management, 93Essbase client-server, 70Financial Management, 81general, resolving, 63OLAP metadata catalog or external datasource, 71,

81Oracle NET, 74Reporting and Analysis, 74Shared Services, 54

corruption, OpenLDAP, 54CSS Spy, 48CSS.xml, 51

DData Integration Management

common issues, 93configuration , 88connection failure, 93failure to load JVM Library, 94illegal plug-in operation, 94logs, 40service stopping after starting, 93unable to run workflow, 94

Data Integration Management Adapteruse with Performance Scorecard, 89

Data Relationship Managementaccess denied, 96common issues, 96configuration issues, 97diagnostics, 18installing on Windows 2000, 97invalid classpath root, 97logs, 40, 41readme issues, 96server startup failure, 97unable to create JVM, 97user rights issues on client machine, 96

DB2, use with Performance Management Architect,87

deploymentfailure without configuration errors, 65out of memory error, 65WebLogic unsupported error, 65

diagnostics, common, 15

documentation, additional, 13

Eerror messages

application server deploymentout of memory, 65

Architect, 86Essbase, 58Essbase Administration Services, 59Essbase load with Interactive Reporting, 74Essbase Provider Services, 59file descriptor limit, UNIX, 66Financial Data Management, 95Financial Management, 61Financial Reporting Studio, 75illegal plug-in, Data Integration Management, 94JVM on UNIX, 66Performance Scorecard, 62, 88Provider Services, out-of-memory, 72Reporting and Analysis, 60Shared Services, 50Strategic Finance, 90WebLogic version unsupported, 65

Essbasediagnostics, 16installation initialization error, 70load failure, Interactive Reporting Studio, 74logs, 24server startup failure, 69server-client connection, 70troubleshooting, 69use with Shared Services, 57

Essbase Administration Servicesadministrator login failure, 71filters, assigning, 71logs, 25refreshing security to Shared Services, 59troubleshooting, 70use with Planning, 79with Shared Services, 58

Essbase Integration Serviceslogs, 26OLAP or data source connection failure, 71

Essbase Provider Servicesadding provider to Administration Services, 59load balancing with WebLogic and Apache, 72out-of-memory errors, 72


100 Index

Essbase — System 9 logs, 24external authentication, 15external user directories, 51

Ffailure

accessing Financial Management from Workspace,80

Apache Tomcat, startup, 66application server deployment, 65Architect Dimensions Library, displaying, 85Architect Services, 87Architect tasks, displaying, 85Configuration Utility, launching, 66connection to OLAP metadata catalog or

datasource, 71Data Relationship Management server startup, 97Essbase Administration admin login, 71Essbase server, 69Financial Management Server, registering, 83IIS startup on Architect Dimension Server, 87login, Financial Management, 80login, Workspace, 84OpenLDAP, startup, 53Oracle Procedure, processing, 75Planning, accessing directly, 77Planning, accessing from Workspace, 77Process Manager Service, starting, 85Reporting and Analysis modules, accessing, 73Reporting and Analysis, connection in distributed

environment, 74Shared Services service or process startup, 55Shared Services startup, application server, 56

FDMdiagnostics, 18

file descriptor limit error, 66Financial Data Management

cannot perform bulk insert, 95common issues, 95configuration issues, 95logs, 41Oracle/Client provider connection, 95user authentication, 95

Financial Managementaccess from Workspace, 80accessing, 80common issues, 80

connection failure, 81diagnostics, 17error messages, 61installation failure, 81large data or file loads, 83logon failure, 80logs, 35registering server on client, 83rights for installation, 83SQL Server connection failure, 81use with Shared Services, troubleshooting, 61

Financial Performance Management applicationsArchitect, accessing Dimension library or

Application library, 85common Architect issues, 83common Financial Management issues, 80configuring Planning with Reporting and Analysis,

79DB2 performance settings, 87diagnostics, Strategic Finance, 90establishing the SQL Server connection using TCP/

IP, 82issues with Performance Scorecard, 88performance issues, 79, 89Performance Management

installation and configuration, 83Performance Scorecard configuration, 88Planning with Administration Services, 79Planning, access issues, 77running Strategic Finance on Novell, 90Strategic Finance issues, 90troubleshooting connection issues, 81upgrade issues, 78

Financial Performance Management Applicationslogs, 35

Financial Reportinginvalid user name error, 75logs, 32Planning Details datasource connection, 76

Financial Reporting Studiorunning on desktop, 76runtime and ActiveX errors, 76

Foundation Services, diagnostics, 16

HHyperion Installation Start Here, 11


Index 101

IIIS logs, 44installation

additional documentation, 13Architect, failure, 83Data Relationship Management, Windows 2000,

97Essbase initialization, 70Financial Management, failure, 81installation directory error, 64logs, 20Performance Management Architect, 83rights for Financial Management, 83Shared Services, 49validation, 12, 15

Interactive Reporting Studiodata truncation, 75Essbase load failure, 74logs, 33Oracle Net connection, 74Oracle procedures, processing, 75

invalid classpath root, Data RelationshipManagement, 97

invalid user name error, Financial Reporting, 75

JJVM error, UNIX, 66

Kknowledge base, My Oracle Support (MetaLink 3),

13

Lload balancing Performance Scorecard applications in

cluster, 89login

Architect, 84Essbase Administration Services, 71Financial Management, 80Shared Services, 50Shared Services, admin, 56Shared Services, improving performance, 51User Management Console, using proxy server, 56Workspace, 84

logsApache, 44

application server, 43Business Rules, 37common location, 19configuration, 12Configuration Utility, 20Data Integration Management, 40Data Relationship Management, 40, 41Essbase, 24Essbase Administration Services, 25Essbase Integration Services, 26Essbase — System 9, 24file size, 20Financial Data Management, 41Financial Management, 35Financial Performance Management Applications,

35Financial Reporting, 32IIS, 44installation, 20Interactive Reporting Studio, 33levels, specifying, 20Oracle 10.1.x, 44overview, 13Performance Management Architect, 35Performance Scorecard, 38Planning, 36Reporting and Analysis, 27Shared Services, 20Smart View, 23SQR Production Reporting, 33Strategic Finance, 39SunJES, 44system performance, 20Tomcat 5.0.28, 44Translation Manager, 40Web Analysis, 34Web server, 44WebLogic 6.0, 43WebLogic 8.1, 43WebLogic 9.1, 43

MMetaLink 3, 13My Oracle Support, 13


102 Index

OOpenLDAP

common issues, 54corruption, 54corruption, resolving without backup, 58log levels, 22startup commands, 22startup failure with Shared Services, 53tips, 54

Oracle 10.1.2.0.2 application serverlogin, Shared Services, 50

Oracle 10.1.x logs, 44Oracle application server

Shared Services login, 50Oracle procedure, processing, 75

Pperformance issues

Financial Performance Management applications,89

logs, 20Performance Scorecard

decreasing startup time, 89load balancing in clustered deployment, 89

Performance Management Architectaccessing, 84common issues, 83diagnostics, 17installing and configuring, 83logs, 35

Performance Scorecardbrowser exception, 88common issues, 88configuration issues, 88Data Integration Management Adapter, 89decreasing application startup, 89diagnostics, 17failure loading JVM library, 89insufficient authorization error, 88Java.lang.NoSuchMethod error, 88load balancing in clustered deployment, 89logs, 38use with Shared Services, 62

Planningaccessing from Workspace, 77common issues, 77configuring with Reporting and Analysis, 79

creating instances, 79diagnostics, 17direct access, 77directory structure, 78logs, 36upgrade issues, 78upgrading from 9.3.0.1, 78with Essbase Administration Services, 79

portconflicts avoiding, 12defaults for all products, 11

prerequisitesadditional documentation, 13configuration, validation, 12Hyperion Installation Start Here, reviewing, 11installation, validation, 12logs, reviewing, 13port, avoiding, 12product

Reporting and Analysis, 16, 18Essbase, 16FDM, 18Financial Management, 17Performance Management Architect, 17Performance Scorecard, 17Planning, 17Strategic Finance, 18

readme, reviewing, 12release compatibility, validating, 11startup dependencies, reviewing, 12system requirements, satisfying, 11

provisioningbest practices, 51using Shared Services, 51

proxy serverUser Management Console, accessing with, 56

Rregistering Financial Management Server, 83release compatibility, 11Reporting and Analysis

connection failure, 74diagnostics, 16error messages, 60logs, 27logs, analyzing, 32logs, configuring, 31


Index 103

module access failure, 73tips, 73use with Shared Services, 59

restarting services, 63runtime and Active X errors

Financial Report Studio, 76

Sserver startup failure, Data Relationship Management,

97services

Architect Process Manager, startup, 85Architect startup failure, 87Data Integration Management, 93Shared Services startup failure, 55start and restart, 63

services, Windows, verifying, 64Shared Services

admin user login, 56application server startup failure, 56common problems, 47configuration, 49connection failure, 54CSS Spy, using, 48external user directories, 51failure accessing products from, 55installation, 49JRE on server, incorrectly set, 49load performance, increasing, 51login performance, improving, 51login, Oracle application server, 50logs, 20startup failure, 55troubleshooting, 47troubleshooting utilities, 48use with Reporting and Analysis , 59User Management Console, accessing with proxy

server, 56user provisioning best practices, 51user provisioning, troubleshooting, 50using on multiple computers, 49using with Performance Scorecard, 62using with Essbase, 57using with Financial Management, 61using with Integration and Administration Services,

58using with upgraded products, 50

using with Workspace, 60WebDav calls on WebLogic, 52

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

82SQR Production Reporting logs, 33starting services, 63startup

OpenLDAP commands, 22startup dependencies, 12startup failure

Architect services, 87configuration utility on UNIX, 66IIS on Architect Dimension Server, 87OpenLDAP, 53Shared Services, 55Tomcat on UNIX, 66

startup time, decreasingPerformance Scorecard, 89

Strategic Financecommon issues, 90diagnostics, 18, 90logs, 39running on Novell, 90

SunJES logs, 44support, accessing, 14system requirements, 11

Ttechnical support, 14Tomcat 5.0.28

logs, 44Tomcat, launching on UNIX, 66Translation Manager logs, 40

Uunable to create JVM, Data Relationship

Management, 97UNIX

Configuration Utility, launching, 66file descriptor limit error, 66JVM error, 66starting Tomcat, 66

UnsatisfiedLinkError-GetOSVersion, 60upgrade issues

Data Relationship Management, 98


104 Index

upgradingFinancial Performance Management applications,

78Planning from 9.3.0.1, 78software compatibility, 64

user authentication, Financial Data Management, 95user directories

using with Shared Services, 51user provisioning, 47

best practices, 51troubleshooting, 47, 50

Vvalidation, installation and configuration, 12

WWeb Analysis

BEx query unavailable, 76failure retrieving cubes using SAP BW, 76logs, 34

WebDav calls on WebLogic, 52WebLogic

8.1, logs, 439.1, logs, 43load balancing, Essbase Provider Services and

Apache, 72version unsupported error, 65WebDav calls, 52

WebLogic 6.0, logs, 43Webserver logs, 44Windows 2000, installing, 97Workspace

accessing Financial Management from, 80accessing Planning from, 77changing Server DNS name, 60logon security rights, 84


Index 105


106 Index

Hsys9 Install Config Troubleshoot

Documents

Transcript of Hsys9 Install Config Troubleshoot