Hsys9 Install Config Troubleshoot

HYPERION
RELEASE 9.3.1
INSTALLATION AND CONFIGURATION TROUBLESHOOTING GUIDE
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 provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted 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 the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages 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 their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between 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 warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may 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
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 Application Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
1
In This Chapter
Introduction
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 Hyperion products. It contains general information about how to approach troubleshooting, important documentation to review, validation checks to perform, and how to use logs. Also provided are solutions to difficulties that you may encounter using Oracle's Hyperion Shared Services to provision and share users among Hyperion product applications.
Audience
This guide is for administrators and IT professionals who install, configure, and manageHyperion products.
Assumed Knowledge
These skills are assumed:
l
Basic security and server administration Basic Windows and UNIX administration Web application server administration
A strong understanding of these aspects of your organization's technical infrastructure are also assumed:
l
Security, including authentication providers such as Microsoft Active Directory, and use of SSL Database and server environments
Purpose
Network environment and port usage
10
Introduction
2
In This Chapter
Troubleshooting Basics
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 product ports, the startup dependencies, and the installation and configuration sequence. The Hyperion Installation Start Here also contains troubleshooting information that you can use to identify potential 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 Compatibility

If you are upgrading from a previous release, it is important to check whether the software versions of Hyperion products you have installed in your environment are compatible with the newer release you are installing. See the Release Compatibility chapter in the Hyperion Installation Start Here.
Reviewing the Installation Start Here
11
Avoiding Port Conflicts

During Hyperion product installations, the default port numbers for application servers are automatically populated. You can change the defaults during the configuration process. However, each port number must be unique. To avoid error messages similar to port already in 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 Hyperion products in the Appendix of the Hyperion Installation Start Here. This appendix also provides default product URLs. Before you start services or processes, start all the databases used as repositories. Before starting the next service or process, ensure that the previous service or process successfully started. Some services or processes take longer than others to start, and startup times may vary by computer.
Reviewing the Readme

All Hyperion products include a Readme document for each release. This document contains known installation or configuration issues along with other product issues. It is very important to review the Readme, which contains late-breaking information that may impact your deployment.
Using Product Installation Guides

Hyperion product installation guides provide step-by-step installation and configuration procedures. Very often you can find the answer to an installation or configuration issue by going back to the installation guide and checking that you have completed all the steps described in the guide.
Validating the Installation and Configuration

After you install and configure a product, perform these tasks to ensure that it is working correctly. Verify the following:
l
All necessary components were installed successfully by checking for exceptions and errors in the installation logs. See Chapter 4, Logs. Uninstallers exist for all products under the product installation directory. All configuration tasks completed successfully as follows:
m
The Oracle's Hyperion Configuration Utility summary panel does not display failures or warnings.
12
HYPERION_HOME\logs\config\configtool_err.log is empty
No exceptions display in HYPERION_HOME\logs\config\configtool.log
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 product log file. The Using Logs chapter helps you learn how to turn on debugging and find the logs for each product. Perform this step before calling Technical Support so you can provide specific information 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 the My Oracle Support knowledge base (MetaLink 3) for information about resolving installation and configuration issues. You can also use My Oracle Support for entering service requests, downloading software releases and patches, and other online support tasks. Oracle recommends that you adjust the default sources for your knowledge base searches, if necessary, to include documentation for your Hyperion products. For more information, click the Getting Started link on the My Oracle Support home page.
Using Shared Services Troubleshooting Utilities

Use 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 authenticate users by examining css.xml. Another utility, CSS Spy, validates connections to user directories and provides user directory information.
Additional Documentation
Refer to the following documents for detailed installation, licensing, deployment, provisioning, and security information.
Document Hyperion Installation Start Here Description Provides key installation and configuration information such as system requirements, prerequisites, and recommended installation sequence. Location Oracle E-Delivery and product DVD
Using Logs
13
Document Product Installation Guide
Description Provides detailed product-specific installation and configuration instructions. Provides known issues for this release and other late-breaking information. Provides information about configuring external authentication and provisioning users. Provides information about configuring products using Secure Socket Layer (SSL). Provides information about installing, configuring, and managing large, complex deployments.
Location Oracle E-Delivery and product DVD
Product Readme
Oracle E-Delivery
Hyperion Security Administration Guide Hyperion Product SSL Configuration Guide Hyperion System 9 BI+ Performance whitepaper
Oracle E-Delivery
Oracle E-Delivery
Oracle Technology Network
Accessing Technical Support Resources

Support Team Hyperion Support Services Description Helps you effectively operate, manage, and run Hyperion performance management solutions by delivering technical expertise whenever you need it. Offers three levels of comprehensive support programs to meet your business requirements:
l l l
Contact Information
http:\\www.hyperion.com \services\support_ programs
Worldwide support
http:\ \esupport.hyperion.com
Alliance wide support Enterprise wide support Standard support
For help by phone, use the country listings on http:\

\www.hyperion.com \services\support_ programs\support_ centers.cfm eService@hyperion.com
E-services program
Provides virtual technical assistance with installations, upgrades, migrations and cross-product configurations.
14
3
In This Chapter
Validating Installation and Configuration
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 and external user directories:
Component General Checks Test To Perform Ensure accurate entry of:
l l l
Server names Database name Configured port numbers Product can connect to Shared Services on <host>:<port> User directory is initialized Product is connected to the user directory
Shared Services External Authentication Services are running
l l
For each product, check that services are running. See Startup Dependencies and Default URLs in the Hyperion Installation Start Here.
Performing Common Diagnostics
15
Foundation Services Diagnostics

Component Shared Services Test To Perform
l l
Database is connected to <host>:<port> Web application is running on <host>:<port> Can connect with the user directory Can get a dummy group and get an exception stating 'group not found' Check the total number of groups under the group URL
External Authentication
l l l
Reporting and Analysis Diagnostics

Component Oracle's Hyperion Interactive Reporting Studio Oracle's Hyperion Financial Reporting System 9 Oracle's Hyperion Web Analysis System 9 Test To Perform
l
Services are running on <host> Note: See Startup Dependencies and Default URLs in the Hyperion Installation Start Here.
l l
Web application is running on <host>:<port> Services are running on <host> Note: See Startup Dependencies and Default URLs in the Hyperion Installation Start Here. For the Web server, check the application context on <host>:<port> Web application is running on <host>:<port> For the Web server, check the application context on <host>:<port>
l l
Essbase Diagnostics
Component Oracle's Hyperion Essbase System 9 Oracle's Hyperion Provider Services Oracle's Essbase Administration Services Oracle's Essbase Integration Services 16 Test To Perform
l
Server is running on <host>:<port> Web application is running on <host>:<port> Web application is running on <host>:<port>
Service is running on <host>
Component
Test To Perform Note: See Startup Dependencies and Default URLs in the Hyperion Installation Start Here.
Performance Management Architect Diagnostics

Component Oracle's Enterprise Performance Management Architect Test To Perform
l l
Web application is running on <host>:<port> Services are running on <host> Note: See Startup Dependencies and Default URLs in the Hyperion Installation Start Here.
l l
Database is connected to <host>:<port> For the Web server, check the application context on <host>:<port>
Planning Diagnostics
Component Oracle's Hyperion Planning System 9 Test To Perform
l l l
Web application is running on <host>:<port> Database is connected to <host>:<port> For the Web server, check the application context on <host>:<port>
Financial Management Diagnostics

Component Oracle's Hyperion Financial Management System 9 Test To Perform
l
Service is running on <host> Note: See Startup Dependencies and Default URLs in the Hyperion Installation Start Here.
l l
Database is connected to <host> For the Web server, check the application context on <host>:<port>
Performance Scorecard Diagnostics

Component Oracle's Hyperion Performance Scorecard System 9 Test To Perform
l
Web application is running on <host>:<port>
Performance Management Architect Diagnostics
17
Strategic Finance Diagnostics

Component Oracle's Hyperion Strategic Finance Test To Perform
l
Data Relationship Management Diagnostics

Component Oracle's Hyperion Data Relationship Management Test To Perform
l
For the Web server, check the application context on <host>:<port>
FDM Diagnostics
Component Oracle's Hyperion Financial Data Quality Management Test To Perform For the Web server, check the application context on <host>:<port>.
18
4
In This Chapter
Logs
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 Location

Log 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 Essbase Administration Services Planning 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 Performance

Logs 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 disk space and negatively affecting performance.
Installation Logs
Installation logs for all products are in <Hyperion_Home>\logs\install\<product>. Provide a.zip of the install logs when reporting installation related problems to Technical Support.
Hyperion Configuration Utility Logs

Hyperion Configuration Utility logs configuration errors and warning messages to configtool.log.
Log File Names and Descriptions

Name
configtool.log configtool_err.log
Contents Configuration errors and warning messages Configuration errors Note: When troubleshooting, check to see that this log is empty.
Setting Log Levels

The Hyperion Configuration Utility log is set to debug and cannot be changed.
Shared Services Logs

This section contains information about Shared Services log files.
20
Logs

Name
SharedServices_Security.log SharedServices_Admin.log SharedServices_Metadata.log SharedServices_Taskflow.log SharedServices_Taskflow_ CMDExecute.log SharedServices_Taskflow_Optimize.log SharedServices_SyncOpenLDAP.log
Contents External authentication and single sign-on activity User management activity Information about metadata management and registration Information about taskflow Scheduling information Scheduling information Information that synchronizes OpenLDAP and relational data sources Information about the external authentication client Note: In previous releases, HyperionCSS.log
SharedServices_Security_Client.log
SharedServices_Memory_Profiler.log SharedServices9.log SharedServices.log openldap.log
Memory consumption information Shared Services activity Shared Services activity OpenLDAP activity
Setting Log Levels

You 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 HSSLogger.properties
These files are in <HYPERION_HOME>\deployments\<AppServerNameAndVersion> for all supported 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 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 the server.
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 Database

The OpenLDAP database stores provisioning data. On Windows, Shared Services automatically installs OpenLDAP as a service (Hyperion SharedServices9 OpenLDAP), configures it, and starts it. Log-level settings for OpenLDAP are flags or parameters that are passed during OpenLDAP startup. Log levels for OpenLDAP are included in the startup command, not in a configuration file.
Table 1
OpenLDAP Startup Commands Log Details Enable all debugging No debugging Trace Debug packet handling Heavy trace debugging Connection management Description Logs all OpenLDAP transactions and queries. Provides no logs. Traces OpenLDAP function calls. For OpenLDAP, enables debugging of packet handling. Provides a large amount of trace with data searched in database. Displays all data available in database with its internal process logs. Displays all packets sent and received. Displays all OpenLDAP filter and search data. Displays configured data such as Object class and its attributes. For a resource, displays accesscontrol data for users. For a resource, displays add, modify, and delete operations. (This option
OpenLDAP Startup Command slapd -d -1 slapd -d 0 slapd -d 1 slapd -d 2 slapd -d 4 slapd -d 8
slapd -d 16 slapd -d 32 slapd -d 64 slapd -d 128 slapd -d 256
Print out packets sent and received Search filter processing Configuration processing Access control list processing Stats log connections/operations/ results
22
Logs
OpenLDAP Startup Command
Log Details
Description provides fewer logs than the -1 option.)
slapd -d 512 slapd -d 1024 slapd -d 2048 slapd -d 4096 slapd -d 8192 slapd -d 16384
Stats log entries sent Print communication with shell backends Print entry parsing debugging Database cache processing Database indexing Syncrepl consumer processing
Displays connection number, operation number, and DN values. Displays index properties of each attribute of an object class. Provides schema-level detail. Displays cache processing data such as index parameters. Provides database index details. Displays replica processing operations (master-slave OpenLDAP configuration).
Smart View Logs

This section contains information about Oracle's Hyperion Smart View for Office logs.
File Names and Descriptions

Name
SmartViewLogs.log
Contents Smart View error messages
Setting Log Levels and Routing Messages to a Log File

All error, warning, and informational messages from the connected data source are displayed when they occur, but you can choose which 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 errorsrecommended to diagnose problems. Warnings to log warning and error level messages. Errors to log error messages only. 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 file
on next launch.
4 Click OK. The setting takes effect after you refresh or perform a drill operation.
Essbase System 9 Logs

The following sections contain information on Essbase System 9 product family logs.
Essbase Logs
The following sections contain information on Essbase log files.

Name
Essbase.log application_name.log
Contents Essbase Server activities and errors Essbase application activities and errors Data load and dimension build errors
Location
<ARBORPATH>\essbase.log <ARBORPATH>\app \<application_name> \<application_name>.log <ARBORPATH>\client \dataload.err
dataload.err
Note: If a rules file is not used for a data load, errors are written to
<ARBORPATH>\app \<application_name> \<application_name>.log dbname.atx, dbname.alg
Successfully completed spreadsheet update transactions These are SSAUDIT log files; File name and location are specified through an essbase.cfg configuration setting. See Monitoring Data, Applications, and Databases in the Hyperion Essbase System 9 Database Administrator's Guide and the Essbase Technical Reference. Note: SSAUDIT log files are created only if SSAUDIT is activated in essbase.cfg.
<ARBORPATH>\app\<appname> \<dbname>
log0000x.xcp
Information captured at the time of an abnormal termination
A location:
l
<ARBORPATH> \log00001.xcp
24
Logs
Name
Contents
Location
l
<ARBORPATH>\app \log00001.xcp <ARBORPATH>\app \<application_name> \log00001.xcp <ARBORPATH>\app \<application_name> \<database_name> \log00001.xcp
Setting Essbase Log Levels

By default, application_name.log and Essbase.log record this information:
l
Information messages Warning messages Error messages
Use essbase.cfg settings to specify the messages types written to application_name.log and Essbase.log. See Monitoring Data, Applications, and Databases in the Hyperion Essbase System 9 Database Administrator's Guide and the Essbase Technical Reference Guide for information about essbase.cfg settings.
Rotating Essbase Logs

You can clear Essbase and application logs at any time, or upon restarting the server or application. You must have administrator permissions to clear Essbase and application logs. You should back up log files before clearing them. See Monitoring Data, Applications, and Databases in the Hyperion Essbase System 9 Database Administrator's Guide. By default, new exception logs are created when Essbase, an application, or a database shuts down abnormally. Subsequent exception logs are numbered sequentially. For example, if log00001.xcp exists, the next log is named log00002.xcp, and so on. You can change a setting in essbase.cfg to overwrite the existing exception log instead of creating a new one. See Monitoring Data, Applications, and Databases in the Hyperion Essbase System 9 Database Administrator's Guide, and the Essbase Technical Reference.
Administration Services Logs

The following sections contain information about Administration Services logs.
Essbase System 9 Logs
25

Name
easserver.log
Contents Administration Services Server activity Administration Services installation information
Location
<EAS_HOME>\server\bin
eas-install.log
<HYPERION_HOME>\logs \install\<product>
Setting Log Levels

How you set log levels for Administration Services varies by application server and if the product is running as a service. For assistance with troubleshooting Administration Services, contact Technical Support. After changing log levels you must restart the Administration Services server for the log settings to take effect.
Integration Services Logs

The following sections contain information on Integration Services logs.

Name
olapisvr.log
Contents Integration Server activity
Setting Log Levels

You can set the log level in Integration Services by using the -L startup switch. For information about Integration Services startup switches, see the Integration Services System Administrator's Guide.
To set the level of message in Integration Services logs:

l
On Windows, add -Llevel to startup.bat. On UNIX, enter -Llevel when you start Integration Server. On any platform, add -Llevel to ais.cfg.
The default level is 2. You can specify these levels:
26
Logs
Table 2
Log Levels Description To log all debug messages and the ODBC SQL generated by Integration Server; generate dataloadrecord.txt, listing the first 1,000 records, which may include successfully loaded records and rejected records; and create hisdld.rul consisting of the names of the dimensions loaded followed by the leaf node number of each dimension or member. Log all informational messages and some of the ODBC SQL generated by Integration Server. Log all warnings. Log all noncritical errors. Log all critical errors where Integration Server terminates the command. Log all critical server errors.
Level 0
2 3 4 7 8
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 to take effect.
Reporting and Analysis Logs

All log messages are routed through Logging Service and stored in one location. Logging Service writes log messages to one or more files, which can be read using a viewer. See Troubleshooting in the Hyperion Workspace Administrator's Guide. Services, servlets, process monitors, and Web services log messages centrally using the Logging Service. Log4j (version 1.2) is used as the basis for the logging framework and configuration files. For 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 messages locally.

The following sections contain information about Reporting and Analysis logs.
27

Name
server_messages_ BrowseServlet.log
Contents Log for Oracle's Hyperion Workspace browsing servlet component, which browses the repository Log for Workspace administration servlet component, which administers the Reporting and Analysis system Log for Workspace personal pages servlet component (bookmarks and personal pages administration) Log for the data access servlet (logs thick client or plug-in calls to the data access service) Log for the Analytic Bridge Service (bridges data to Oracle's Hyperion Interactive Reporting System 9 from other Hyperion products. Authentication Service information (user credentials and group membership at login) Authorization Service information (roles and their associations with operations, users, groups, and other roles) Entries for the Reporting and Analysis logging service before the Reporting and Analysis logging service is operational. Note: Logged items are also in stdout_console.log.
Location
<HYPERION_HOME>\logs \BIPlus\
server_messages_ AdministrationServlet.log
server_messages_ PersonalPagesServlet.log
server_messages_ DataAccessServlet.log
server_messages_ AnalyticBridgeService.log
server_messages_ AuthenticationService.log
server_messages_ AuthorizationService.log
server_messages_ CommonServices.log
server_messages_ DataAccessService.log server_messages_ EventService.log server_messages_GSM.log
Data Access Service information Event Service information (system resource and job management) Global Service Manager information (system configuration and service monitoring) Impact Management Assessment Services (Harvester) information (published Interactive Reporting repository document metadata)
<HYPERION_HOME>\logs \BIPlus\ <HYPERION_HOME>\logs \BIPlus\ <HYPERION_HOME>\logs \BIPlus\
server_messages_ HarvesterService.log
28
Logs
Name
server_messages_ IntelligenceService.log
Contents Interactive Reporting Service. This log is helpful in troubleshooting problems with the Interactive Reporting thin client. Log for the Job Service, processes Interactive Reporting jobs, either scheduled or on demand Interactive Reporting Service Helper Process information (logging and usage tracking for all Interactive Reporting services) Job Service information (Reporting and Analysis job management) Log for the Local Service Manager (LSM) service; LSMs provide support for Interactive Reporting distributed services infrastructure. Name Service information (RSC services monitoring) Publisher Service information (repository communication for other LSC services and some Web application requests) Repository Service information (Reporting and Analysis data storage repository) Session Manager Service information (simultaneous users and session time-out management) Service Broker information (GSM and LSM client request routing and RSCload balancing) Impact Management Update Service (Transformer) information (Interactive Reporting document updates) Usage Service information (Interactive Reporting usage statistics (such as the most used files, the most selected MIME types) Calendar Manager information (for job scheduling) Interactive Reporting SDK information
Location
server_messages_ IRJobService.log
server_messages_ IRServiceHelper.log
server_messages_ JobService.log server_messages_LSM.log
<HYPERION_HOME>\logs \BIPlus\ <HYPERION_HOME>\logs \BIPlus\
server_messages_ NameService.log server_messages_ PublisherService.log
server_messages_ RepositoryService.log
server_messages_ SessionManager.log
server_messages_ ServiceBroker.log
server_messages_ TransformerService.log
server_messages_ UsageService.log
server_messages_ CalendarManager.log server_messages_SDK.log
29
Name
server_messages_ EventService.log server_messages_ LocalServiceConfigurator. log server_messages_ RemoteServiceConfigurator .log
Contents Log for the Event Service, including events that trigger jobs to run Local Service Configurator (LSC) information Configuration information on Remote services, which are configured using the Remote Service Configurator (RSC) This log file contains basic configuration information, including Java system property information, JAR file version information, and database information. Logging messages when the logging service is unavailable The stdout_console.log is generated regardless of the operation being performed, and represents standard output and standard errors (console output). Some errors captured by the application are logged here, as are startup failures. Workspace Web Application activity Reporting and Analysis activity Reporting and Analysis installation information Installation
Location
configuration_ messages.log
<BIPLUS_HOME>\logs
name_backupMessages_ipaddress_port.log(where name
is the process name)

stdout_console.log <BIPLUS_HOME>\logs
WorkspaceApp.log BIService.log server_messages_ Installer.log AvalancheInstall.log
%USERPROFILE% (typically c: \Documents and Settings \<UserName>), $USER_HOME on
UNIX
AvalancheUnInstall.log
Uninstallation
%USERPROFILE% (typically c: \Documents and Settings \<UserName>), $USER_HOME on
UNIX
biplus-install.log
Installation Installation Information about user input during configuration Installation
<HYPERION_HOME>\logs \install <BIPLUS_HOME>\logs <HYPERION_HOME>\common \config\<product>\biplus \<version> <BIPLUS_HOME>\install
install.log biplus_1_config.xml
InstallHistory.properties
30
Logs
Name
Workspace_log.<date>.txt
Contents Tomcat log for Workspace (for exceptions only) WebLogic 8.1 log for Workspace
Location
<HYPERION_HOME> \deployments \Tomcat5\Workspace\logs\ <BIPLUS_HOME>\AppServer \InstalledApps\WebLogic \8.1\WorkspaceDomain \Workspace\ <HYPERION_HOME> \deployments \WebLogic9\servers \Workspace\logs\
Workspace.log
Workspace.log
WebLogic 9 log for Workspace
Setting Log Levels

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

To troubleshoot Reporting and Analysis, you can configure these logging properties:
l
Logging levels Loggers Appenders Log rotation
Loggers, logging levels, and appenders are configured in XML files. The log rotation property is a Java system property and is configured in startcommonservices.bat. Logging levels for LSC services, RSC services, and the root logger are configured using LSC and RSC. All other configuration changes are made by editing XML files. See Configuring Log Properties for Troubleshooting in the Hyperion Workspace Administrator's Guide for information on setting Reporting and Analysis log levels.
Note:
Configuration errors for RSC services show at startup in stdout_console.log or server_messages_NameService.log; configuration_messages.log might be helpful.
31
Analyzing Reporting and Analysis Log Files

For information on how to view Reporting and Analysis log files, log files that are always generated, and log files to look at for troubleshooting, see Analyzing Log Files in the Troubleshooting chapter of the Hyperion Workspace Administrator's Guide.
Financial Reporting Logs

The following sections contain information about Financial Reporting logs.

Name
FRCommSrv.log
Contents Financial Reporting Communication Server information Activity from the Financial Reporting server, where reports are rendered Batch scheduler activity Activity from the Scheduler command line interface Activity from the Financial Reporting Web Application, where Web client pages are generated Financial Reporting printing information User login information Financial Reporting configuration log Financial Reporting configuration error log
Location
<HYPERION_HOME>\logs \BIPlus\ <HYPERION_HOME>\logs \BIPlus\ <HYPERION_HOME>\logs \BIPlus\ <HYPERION_HOME>\logs \BIPlus\ <HYPERION_HOME>\logs \BIPlus\
FRReportSrv.log
FRSchedSrv.log
FRScheduleBatch.log
FRWebApp.log
FRPrintSrv.log
<HYPERION_HOME>\logs \BIPlus\ <HYPERION_HOME>\logs \BIPlus\ <BIPLUS_HOME>\logs <BIPLUS_HOME>\logs
FRUserLogin.log
HRRunAnt.out HRRunAnt.err
Setting Logging Levels

To set debug level logging for Financial Reporting components, specify these settings in fr.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 for the log settings to take effect.
32
Logs
Component All Components Report Client Report Server Print Server Scheduler Server Web Application
Properties File
fr_global.properties fr_client.properties fr_repserver.properties fr_printserver.properties fr_scheduler.properties fr_webapp.properties
Log File
FRCommSrv.log FRClient.log FRReportSrv.log FRPrintSrv.log FRSchedSrv.log FRWebApp.log
SQR Production Reporting Logs

The following sections contain information about Oracle's Hyperion SQR Production Reporting System 9 logs.

Name
<report_ name>.log <report_ name>.err sqr.log
Contents Output from SHOW and DISPLAY commands when -O command line flag. Can be redirected to any file. Error messages/warnings during compilation and program execution when -E command line is used (can be redirected to any file). (Windows) Output from SHOW and DISPLAY commands and/or error messages/warnings during compilation and program execution when neither -E and -O command line flags are used.

You cannot set logging levels for Oracle's Hyperion SQR Production Reporting System 9.
Interactive Reporting Logs

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

Name
BIstartup.log
Contents Interactive Reporting service startup information Interactive Reporting Data Access Service startup information
Location
<BIPLUS_HOME>\logs\
DASstartup.log
<BIPLUS_HOME>\logs\
Web Analysis Logs

The following sections contain information on Web Analysis logs.

Name
WebAnalysis.log WebAnalysisApp.log server_messages_WebAnalysis.log
Contents Web Analysis activity Web Analysis Web application activity 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 Debug Info Warn Error Fatal Off
4 After changing log levels you must restart the server for the log settings to take effect.
34
Logs
Financial Performance Management Applications Logs

The following sections contain information about Financial Performance Management logs.
Financial Management Logs

The following sections contain information about Financial Management logs.

Name
HsvEventLog.log
Contents Financial Management activity (any errors with Financial Management server)
Setting Log Levels

You cannot set log levels for Financial Management.
Performance Management Architect Logs

The following sections contain information about Performance Management Architect logs.

Name
awb.log DMEngine.log
Contents Information written by the Web server Data Synch Web application activity Dimension Server activity Transactions Note: View transaction logs from the Dimension Library
Windows Event Viewer Transaction logs

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.
35
3 Modify this line: log4j.logger.com.hyperion.awb=ERROR,logfile, stdout to

log4j.logger.com.hyperion.awb=DEBUG ,logfile, stdout
4 After changing log levels you must restart the server for the log settings to take effect.
Planning Logs
The following sections contain information about Planning logs.

Name
Application Server logs
Contents Planning activity
Location 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~de fault_island~1 HspEventLog.log
Planning activity (end-user issues: refresh issues, and so on.)
\Hyperion\Planning\
UserProvisionSync.log
\Hyperion\Planning\bin

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 Logs

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

Name
hbrclient.log
Contents Business Rules client activity
Location For all Application Servers:

<HYPERION_HOME> \AnalyticAdministrationSe rvices\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> \AnalyticAdministrationSe rvices\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> \AnalyticAdministrationSe rvices\AppServer \InstalledApps\WebLogic \8.1\aasDomain
WebLogic 9.1 <HYPERION_HOME>

\deployments\WebLogic9 log.txt
Information about processes run on the Business Rules client
37

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

1 Launch the Administration Services Console by selecting Start > Programs > Hyperion > Administration
Services > Start Administration Services Console.
2 In Administration Services Login , enter the Administration Services server name and your logon credentials.
Click OK.
Note:
If the Administration Services default port was changed , enter the port information before the Administration Services server name as: port number name:port#.
3 In the left pane of Administration Services, expand Business Rules and then Administration. 4 Double-click Properties.
The properties of the Business Rules client configuration are displayed.
5 To change the level of error reporting for the client on the Client Configuration tab, select a level from Log
Level:
l
Severe Warning (default) Info Config All
6 To change the level of error reporting for the server on the Server Configuration tab, select one of the error
levels described in step 5 from the Log Level list.
7 Click Save. 8 After changing log levels you must restart the server for the log settings to take effect.
Performance Scorecard Logs

The following sections contain information about Performance Scorecard logs.

Name
HPSWebReports.log HPSAlerter.log
Contents Performance Scorecard application activity Alerter Web application activity
38
Logs
Name
errors.log failedrecords.log successfulRecords.log
Contents Performance Scorecard import or export errors Performance Scorecard import or export errors Performance Scorecard import or export records

Performance Scorecard uses log4j for logging. You can modify logging levels and log4j settings for HPSWebReports.log in HPSConfig.properties and AlerterConfig.properties. These files are in one of these directories:
Application Server Oracle 10.1.x WebLogic 8.1 WebLogic 9.1, Tomcat, and WebSphere 6 Location
<HPS_INSTALL>\AppServer\InstalledApps\Oracle\10g\manual \webappsconf\config <HPS_INSTALL>\AppServer\InstalledApps\<app server> \<version>\webappsconf\config\ <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 Logs

The following sections contain information about Strategic Finance logs.

Name
debug_YYYYMMDD_ HHMMSS.log eventYYYYMMDD.log
Contents Debugging information from the Strategic Finance Server (detailed information on what is happening with every server operation) Information about Strategic Finance events Note: Using the Event Logs tab of the Administrator utility, you can view individual event logs. See the Strategic Finance Administrator's Guide.
YYYYMMDD_HHMMSS_seq.log
A history of user's actions (called user results log files). Microsoft Application Event log. Note: Located in Start > Control Panel > Administrative Tools > Event View > Application log tab.
event logs
39

You 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 Error to write errors to the log 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 Finance Administrator's Guide.
Data Management Logs

The following sections contain information on Data Relationship Management logs.
Data Integration Management Logs

The following sections contain information about Oracle's Hyperion Data Integration Management logs.

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

For information on setting Data Integration Management logging levels, see the Data Integration Management online help.
Translation Manager Logs

The following sections contain information about Oracle's Hyperion Translation Manager logs.
40
Logs

Name Depends on the application server. Contents Translation Manager error information, depending on the logging level that is set for the application server.

Translation 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 the application server is set to log warnings and errors.
FDM Logs
The following sections contain information about FDM logs.

Name
tLogActivity table
l l l
Contents Information about FDM activities and audit related information. Batch processing, informational, and error log entries
tBatch tBatchContents tBatchInformation
<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 LoadBalance Manager Note: FDM Task Manager can also log scheduled task events (when logging is enabled) in the Windows Event Log.
Authentication.err
Information about FDM Failed authentication attempts

You cannot set logging levels for FDM.
Data Relationship Management Logs

The following sections contain information about Data Relationship Management logs.
Data Management Logs
41

Name
mssql_install.log oracle_install.log
Contents Installation information Note: One of these log files is generated during Data Relationship Management server installation, depending on the type of Data Relationship Management database being used. Information written by Data Relationship Management, about Data Relationship Management events Information about the Import operation Note: Optional log file that can be specified by the user. Information about the Blend operation Note: Optional log file that can be specified by the user. Data Relationship Management Batch Client information (user can override the name and location) Errors written by the Data Relationship Management Server Transaction information written by the Data Relationship Management system
Windows Application Log Data Relationship Management Import Log Data Relationship Management Blender Log
MDM_Connect.log
Microsoft Application Event Log Data Relationship Management repository database transaction log

You must have administrator privileges to set Data Relationship Management Transaction History logging levels. Set the TransactionLevel system preference to specify the action types to capture in the transaction history.
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. Core Action records actions that change the version, hierarchy, or node information, such as Add Node, Change Property, or Move Node. Result Action records actions that result from core actions. For example, if the clear all below core action is performed, then properties are cleared from individual nodes. The clearing of properties from the individual nodes is a result action. Loss Action records loss of data due to a core action. For example, when a node is deleted, all of the defined properties for that node are deleted, which is a loss action. Loss actions are controlled by the LossLevel system preference.
3 Set additional system preferences:
42
Logs
LossLevel indicates what to track for lost information. Its values are Defined and All. When set to Defined only values that are specifically set at the node are tracked when the node is deleted. When set to All, derived, default, inherited values are also tracked in the LossAction. AllowAsOf forces tracking of Core Actions.
Note:
You cannot change the level of detail recorded in logs other than the transaction history. After changing the log levels for the Transaction History you must restart the Data Relationship Management 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, even if not set in the TransactionLevels System Preference.
Application Server and Web Server Logs

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

Every Hyperion application that is deployed to an application server generates logs for that application server.
IBM WebSphere 6.0

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

BEA 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, called

WebLogicBeanDeployOutput.txt
BEA WebLogic 9.1

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

Apache Tomcat writes files into: <HYPERION_HOME>\deployments \<AppServerNameAndVersion>\bin\<product>.
Oracle 10.1.X
Oracle 10.1.x Application Server has a Log Viewer Utility which is available through the admin console. The most commonly used log files are:
l
<ORACLE_HOME>\dcm\logs\ deployment status/error logs <ORACLE_HOME>\daemon_logs\log.xml dcm daemon logs <ORACLE_HOME>\dcmctl_logs\log.xml dcmctl logs <ORACLE_HOME>\j2ee\<APP_NAME>\log\log.xml deployed application information <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

Apache
Default logs location: <HYPERION_HOME>\logs\apache. By default, configuration uses its own Apache 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 IIS
Default 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.
45
46
Logs
5
In This Chapter
Troubleshooting Shared Services and Provisioning
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 the problems you encounter performing tasks.
Table 3
Diagnostics Troubleshoot User directory Basic Tasks

l
Problem You cannot log in to Shared Services
Ensure that the Web application service started. Ensure that CSS.xml contains the most recent user login credentials. Use CSS Spy to gather more data about the user directory, such as user roles and credentials. Check Shared_Services_ Security.log in the product server for errors Ensure that the OpenLDAP service or process is running
You cannot log in to other Hyperion products from Shared Services
OpenLDAP
OpenLDAP service or process will not start
OpenLDAP
From the Start menu, open the Control Panel to ensure that the service is running. If it isn't, perform these tasks:
l
Open a command prompt and enter: 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 and execute: ..\..bdb\bin\db_ recover. You may have to run
this command twice.
Preliminary Tasks
Perform these initial tasks to better identify or resolve issues with Shared Services before contacting Support:
l
Perform the steps in Chapter 2. Review the appropriate log file to better diagnose the problem. This could include enabling debugging information. To validate basic user directory function, use the utilities provided with Shared Services. See Troubleshooting Utilities on page 48.
Troubleshooting Utilities
These utilities are provided with Shared Services:
Table 4
Troubleshooting Utilities Description Verifies the external user directories or Native Directory that you use to authenticate users. This information is stored in CSS.xml Validates the following information:
l l
Utility
http://<HSS_Server>/58080/ interop/framework/ getCSSConfigFile
Optional: Use CSS Spy

http://<HSS_Server>/58080/ interop/cssSpy
Connections to user directories using any CSS call or method User logins User role information Performance
http://HSS_SERVER:58080/interop/cssSpy
l l
See CSS Spy on page 48.
CSS Spy
CSS Spy enables you to validate connections to external user directories, retrieve user role information, and assesses performance.
48
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 to authenticate 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 Issues

The following sections address common Shared Services installation and configuration issues.
Manually Creating Database Tables

You can create database tables without using Hyperion Configuration Utility by running the scripts in:
Hyperion/SharedServices/<version>/server/scripts
Installing Components on Multiple Servers

Although you must install Web and non-Web components on the same server, you can later modify CSS.xml as follows to have the Web application access components on another computer: Change <hub location>=http:\\esp intrapp1:58080 to: <hub location>=http:
\\<OpenLDAP host>:58080
Resolving Incorrect JRE Setup

Ensure that ldapbp.jar is in the classpath. By default, this is: <HYPERION_HOME>\common
\CSS\9.3.1\lib
Dedicating Shared Services Databases

Each 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.2 Application 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 web application>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 File Permissions on the Files and Folders for Deployment error, assign Write permissions to: <drive>:\WebSphere\AppServer or <drive>:\IBM\WebSphere \Express\AppServer.
Upgraded Products Registered with Shared Services

If you upgraded products registered with Shared Services incorrectly, by not selecting the existing HYPERION_HOME, you must reinstall Shared Services and reregister the products with Shared Services after you upgrade them correctly.
Using Shared Services Upgrades With Other Upgrades

To avoid errors, perform these tasks to use a Shared Services upgrade with Hyperion products upgrades: 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 Provisioning

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

If you have an existing user directory, use a standard LDAP Browser to explore the user directories that store user credentials before provisioning Hyperion applications. The settings that the LDAP Browser uses to connect to the user directory are identical to those that Hyperion applications 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 The response time The starting point (base DN) for any search of the user directory 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. Ensure that the server machines that host Hyperion applications are in the same geographical location as the server machines that host the user directories used in the provisioning process. Find an optimal starting point for searches or create a custom group hierarchy.
Common Problems
These are the most common problems users encounter using Shared Services with external user directories:
l
Changes to user IDs and passwords in user directories are not updated in CSS.xml The host name, port, or domain controller is not specified correctly in CSS.xml. The Group URL in CSS.xml is incorrectly defined 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 Register applications 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:
51
MSAD: <url>cn=LostAndFound</url> 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 Directory
Perform 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 WebLogic

Perform the steps for the WebLogic version:
Table 5
WebDav Calls on WebLogic Procedure

l l
Version 8.1.6
Download ftp://support:ahtoopee@ftpsupport.beasys.com/pub/725734.zip. 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 l
In any text editor, open config.xml and scroll to <SecurityConfiguration>. Before Name=SharedServices9Domain, add this code:
EnforceValidBasicAuthCredentials=false
Save and close the file. Open config.xml and scroll to <SecurityConfiguration>. Before Name=SharedServices9Domain, add this code:
<enforce-valid-basic-auth-credentials>=false</enforce-basic-authcredentials>
9.2
l l
Save and close the file.
52
Modifying the Group URL

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

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

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

1 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
53
b.
Enter slapd d 1.
OpenLDAP Issues
This 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 Do not terminate the OpenLDAP process from the task manager Do not terminate the OpenLDAP process when data is being written Restore OpenLDAP and the database used with Shared Services simultaneously to ensure synchronization Perform a weekly cold backup on the OpenLDAP database and the Shared Services database Recover provisioning data before restoring it from a backup
Causes of OpenLDAP Corruption

OpenLDAP becomes corrupt when manually shut down, because of sudden power loss, or because of a power loss while the service is running. To avoid OpenLDAP corruption, note the following:
l
Do not manually shut down the computer hosting OpenLDAP. Do not terminate the OpenLDAP process from the task manager. Do not terminate the OpenLDAP process when data is being written. Restore OpenLDAP and the database used with Shared Services simultaneously. Perform weekly cold backups on both the OpenLDAP and the Shared Services databases.
Using CSS.XML to Resolve Connection Failures

Change 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>
54
Startup and Access Issues

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

The service may not run if OpenLDAP is corrupt or not running. If this is the case, run or restore OpenLDAP. See the Hyperion Security Administration Guide.
Decreasing the Login Time

Perform 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 set properly 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 Shared Services

You 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 The user URL is incorrect You are using invalid logon credentials The server hosting the product is not connected to the servers hosting user directories and Shared Services OpenLDAP is not running 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
The URL at which you registered your application (the Financial Management Security URL, for example) is not accessible from the Shared Services server.
Perform these tasks: 1. Review SharedServices_Security_Client.log (on the server hosting the product) and SharedServices_Security.log (on the server).
l
If group cache errors exist, ensure that the group URL and filter are limiting the number of groups returned by the search.
Startup and Access Issues
55
If authentication errors exist, verify that the user URL is correct.
2. Ensure that the user ID and password are correct. 3. Ensure that the server hosting the product can connect to the servers hosting the user directories and Shared Services. 4. Start the OpenLDAP service or process.
Logging in Using the Default Admin Username

If you can not log in using the admin username, the user may not be provisioned. Perform these tasks: 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 Proxy Server

Perform 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 and password). 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 all of 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 the Application Server

You may be unable to start if the port number is being used by another application, or if the Shared 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 its own line.
56
Libraries are defined for interop.war.

l
Correct the settings of the <HYPERION_HOME> environment variable. 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 the Shared Services port or stop the process that is using the port.
Resolving Product-Specific Issues

This section identifies solutions to errors you may encounter using other Hyperion products with Shared Services.
l
Essbase System 9 on page 57. Reporting and Analysis on page 59 Applications+ on page 61
For help with installing and configuring these products independently of Shared Services, see:
l
Chapter 7, Troubleshooting Essbase System 9 Chapter 8, Troubleshooting Reporting and Analysis Chapter 9, Troubleshooting Financial Performance Management Applications Chapter 10, Troubleshooting Data Management
Essbase System 9
This section provides solutions to questions you may have using Essbase products with Shared Services. See Chapter 7, Troubleshooting Essbase System 9.
Essbase
This section provides solutions to common problems users have using Essbase with Shared Services.
Logging in After Externalizing a User

Perform the procedure if you externalize a user (essadmin for example) from Essbase to Shared Services, but cannot log back in to Essbase: 1. Ensure that the user exists in Shared Services. 2. MSAD or LDAP: If the user exists, perform these tasks: a. In <essbase_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.
57
e. In Shared Services, search for the user in Native Directory or in an external directory and provision it to Essbase as admin. f. In Essbase, refresh security. See the Hyperion Essbase System 9 Database Administrator'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, perform these tasks:
l
Ensure that the entries in essbase.cfg are correct 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 Services database 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-externalization state. 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 with Essbase and Administration Services.
58
Adding Essbase Provider Service Providers

You installed and configured Provider Services 9.3.0.1 on WebSphere 5.1.1.9 on Windows 2k3 SP1. 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
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 the Administration Services console. 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 log file location. 2. Save the file and update the archive. 3. Save css.zip as css.jar. 4. Restart Essbase services.
Reporting and Analysis

This section provides solutions to errors you may encounter configuring and using Shared Services with Reporting and Analysis. See Chapter 8, Troubleshooting Reporting and Analysis.
59
Resolving a 404 Error: UnsatisfiedLinkError- getOSVersion Error

You automatically deployed Workspace to Tomcat. You configured an NTLM provider for Shared 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 Server

If you change the DNS name of the Workspace server and have a large number of provisioned users (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 Services

You installed Reporting and Analysis 9.3.0.1 on Windows 2K3 SP1 with Tomcat, cannot start the 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 in thevalue0 column:
l
ConfigurationManager.hubHost references the Shared Services host name. ConfigurationManager.hubport references the Shared Services port. ConfigurationManager.hubUseSSL is true/false. ConfigurationManager.cssConfigURL Copy and paste this URL in a browser window to get CSS.xml from Shared Services. ConfigurationManager.applicationId references the ID of the application registered
with Shared Services. Note: This ID must correspond with the Shared Services database.
60
Applications+
This section provides solutions to errors you may encounter configuring and using Shared Services with Financial Management and Performance Scorecard. See Chapter 9, Troubleshooting Financial Performance Management Applications.
Financial Management
This section provides solutions to errors you may encounter configuring and using Shared Services 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 the groups returned by the search. If data broker property errors display, enableinteropjava logging. Exceeding 1,000 groups in the group URL causes a known JRE 1.4.2 bug. Use JRE 1.5 to support 1,000 or more groups.
Ensure that the Financial Management application server can communicate with Shared Services using HTTP and WEBDAV protocol. Webdav may be blocked if you proxy requests from IIS to interoperate with the Web application. If this is the case, ensure that the UrlScan IIS extension does not block propfind methods. If you are using IIS on Windows 2003 sp1, add the IIS the UseBasicAuth registry key to dword 1 in the registry HKLM\SYSTEM\CurrentControlSet\Services\WebClient \Parameters.
If the interop Web site that redirects to the Web application server, ensure that the authentication method is anonymous and that Windows integration authentication is not used. 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 repeatedly reregistered. To resolve this issue, import the root ca certificates to the Java keystore cacerts in all Java installations in Hyperion/common.
Resolving an Internet Explorer Script Error to View User Security From the User Management Console
If you receive the following error, set the time-out period for the script:
61
A script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer may become unresponsive. Do you want to abort the script?
See http://support.microsoft.com/kb/175500.
Performance Scorecard
This section provides solutions to errors you may encounter configuring and using Performance Scorecard with Shared Services.
Required Oracle Database User Permissions

You installed Hyperion 9.3.0.1 using an Oracle database. You assigned owner privileges to the Oracle user ID that you currently use. Your security policy has blocked access to this user and you need to know the privileges to assign to a substitute Oracle user. To resolve this issue, grant the user read/write permissions in the database. If the user will generate an Essbase database of Performance Scorecard data, also assign permissions enabling them to create indices and execute procedures.
Java.lang.NoSuchMethod Error
You receive this error if you install multiple products with Performance Scorecard and Shared Services but configure Performance Scorecard first. To resolve this issue, uninstall Performance Scorecard, re-install and configure the other products, and then install and configure Performance Scorecard.
62
6
In This Chapter
General Tips for all Hyperion Products
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 Services

Server 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 Services

Some problems may be caused if services required for a product are not running. Other problems that 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. If the service has stopped, select Start.
Resolving Connection Failures and Restarting Services
63
Verifying Services in the Windows Task Manager

You 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. If listed, select Mem Usage. If it is using more than 500 MB, there may be a memory error that requires you to restart the service.
Upgrading Tip: Software Compatibility

Issue: A product you upgraded does not work correctly with older versions of Hyperion products. Solution: Before upgrading Hyperion products, ensure that existing versions are compatible with the new releases. In some cases, a new version of a product may only be compatible with another recent version, and you must upgrade multiple products. For example, in the 9.3.1 release, Planning 9.3.1 requires Shared Services 9.3.1. See Release Compatibility in the Hyperion Installation Start Here.
Installation Tips
Installation Directory
Issue: Installation fails because you installed a product to a directory containing spaces, such as Program 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 Uninstalling

Issue: 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
When reinstalling two or more Hyperion release 9.3.1 products, use alternate target destinations for the new installations (The vpd.properties file may contain entries remaining from the previous home directory used for the product.)
Configuration Tips
This section provides solutions to the most common configuration errors.
Errors During Configuration

Issue: 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 tasks individually for one product or component at a time.
Failure Deploying to Application Server Without Configuration Errors

Issue: A Hyperion product is not deployed to the application server, but there are no configuration errors. Solution: Review configtool.log. This file records any errors in the deployment process. If no errors are identified, redeploy to the application server.
WebLogic 8.1.4 Deployment Error

Environment: 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 during configuration 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. See your application server documentation.
UNIX Tips
This section provides solutions to installation and configuration errors that UNIX users may encounter.
Configuration Tips
65
Hyperion Configuration Utility Startup Failure

Issue: You cannot run configtool.sh if the name of the computer contains duplicate characters. 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 Failure

Issue: Apache Tomcat does not start and may be accompanied by this error:
[crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lock Configuration Failed
This indicates that you may need to clean up semaphores. To confirm that semaphore cleanup is needed, run > ipcs -s | grep $USER Solution: Force semaphores cleanup by having the user who runs Apache Tomcat issue the following command:
for i in `ipcs -s | grep $USER | cut '-d ' -f2 -s`; do ipcrm sem $i; done
File Descriptor Limit Error

Error: 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. Update <Hyperion_Home>/common/config/configtool.sh after commenting the lines in the header with ulimit n 1024.
Preparing JVM...Error Writing to This File Error

Issue: Preparing Java Virtual Machine... Error writing file This indicates insufficient temporary disk space.
66
Solution: Delete temporary files in /var/tmp and /tmp. If you have root privileges to the computer and can safely remove other unused temporary files, do so.
UNIX Tips
67
68
7
In This Chapter
Troubleshooting Essbase System 9
Essbase ............................................................................................................................69 Administration Services ...........................................................................................................70 Integration Services................................................................................................................71 Provider Services...................................................................................................................72
Essbase
The following sections identify common Essbase installation and configuration issues.
Essbase Server Failure

Several issues can cause the Essbase server to fail to start after installation. The following table identifies some of those issues, along with possible solutions:
Error Message or Problem The JVMMODULELOCATION environment variable has not been correctly set in essbase.cfg. Error: Fatal Error: Essbase is
already loaded
Solution Set the environment variable. See the Hyperion Essbase System 9 Installation Guide. Check to see if Essbase is running: 1. On Windows platforms, check the Windows Task Manager for the essbase.exe process 2. UNIX: Use ps -fu <username> | grep -i essbase to check for the essbase process. If Essbase is not already running, then another user may be running a process on the port setting you have specified for Essbase in essbase.cfg. For instructions on shutting down Essbase, see Running Essbase Servers, Applications, and Databases in the Hyperion System 9 Essbase Database Administrator's Guide.
The Essbase agent is already running.
Error: Failed in GCInit() This error can mean that the ARBORPATH (Essbase installation location) environment variable is not set correctly.
Check the ARBORPATH:

l
Windows: In the command line, enter > echo

<ARBORPATH>
UNIX: In the console window, enter > echo $ARBORPATH
Essbase
69
Error Message or Problem
Solution If the ARBORPATH is missing or incorrect, define the correct ARBORPATH. See the Hyperion Essbase System 9 Installation Guide.
Error: ESSBASE: not found This error can mean that the essbase executable is not in the environment path.
Define an ARBORPATH. If an ARBORPATH is already defined, then add the following to the path:
l l
On Windows platforms, add <ARBORPATH>\bin On UNIX platforms, add $ARBORPATH/bin
Essbase will not start.
Attempt to start Essbase from a DOS prompt if it will not start from the icon. More error messages are displayed when Essbase is started from a DOS prompt, enabling you to troubleshoot. For example, messages about missing or inaccessible files may be displayed.
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 Problems
Issue: You cannot establish an Essbase client-server connection. Solution: Use the PING command on the server to check that the server is running and visible to the client computer.
l
If the PING command is successful but the TELNET command is not, there might be a problem with the inet daemon. If the PING command is unsuccessful on the server, you might have a routing or hardware problem.
Administration Services
The following sections describe common Administration Services issues.
70
Administrator Login Failure

Environment: Administration Services with Business Rules. Issue: Administrator cannot log in. Solution: Use the Hyperion Configuration Utility to deregister Administration Services from Shared Services, (sometimes you have to do this more than once). From Shared Services, remove Oracle's Hyperion Business Rules project. See the Essbase Administration Services Installation Guide.
Problems Assigning Filters

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

Issue: You cannot connect to OLAP Metadata Catalog or to the external data source. Possible Solutions:
l
Ensure that you are using the correct user name and password.
m
If you are trying to connect to OLAP Metadata Catalog, ensure that you used the same user name and password as the user who created the tables in OLAP Metadata Catalog. If you create OLAP Metadata Catalog when logged in as one user name, you cannot access the tables in OLAP Metadata Catalog using a different user name unless you create an alias for the user name (for Microsoft SQL Server) or synonyms for the tables (for IBM DB2 and Oracle). See the Essbase Integration Services Installation Guide.
Does the user name you used have the correct privileges to access both OLAP Metadata Catalog and the data source at the database level?
Ensure that all of the required components are up and running. The following components are required:
m
Oracle's Essbase Integration Services Server The database servers that manage OLAP Metadata Catalog and the data source databases The data source database listener for OLAP Metadata Catalog and the data source
Integration Services
71
Ensure that the OLAP Metadata Catalog and the data source are configured as ODBC data sources on the Integration Server computer. See the Essbase Integration Services Installation Guide.
Provider Services
This section describes common Provider Services issues and solutions.
Out of Memory Errors With Concurrent Users

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

Issue: In Provider Services, Load Balancing with WebLogic through Apache might not work. In this situation, when you apply one of the URLs through Internet Explorer, it will fail to return the correct Oracle'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
8
In This Chapter
Troubleshooting Reporting and Analysis
Tips and Recommendations ......................................................................................................73 General Errors ......................................................................................................................73 Interactive Reporting Studio ......................................................................................................74 Financial Reporting ................................................................................................................75 Web Analysis .......................................................................................................................76
Tips and Recommendations

l
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 port on 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 the Hyperion Configuration Utility on every computer, ensuring that you are using the correct computer names. Check the stdout_console.log in <BIPLUS_HOME>\logs for information on startup failures. See Chapter 4, Logs.
General Errors
This section contains general Reporting and Analysis installation and configuration issues.
Failure to Access Modules

Issue: User cannot access any modules. Solution:
l
Contact the administrator to verify user privileges. Check that context.properties was created during auto deployment or that it was created manually for manually deployed configurations.
Tips and Recommendations
73
Connection Failure
Environment: 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 the environment, using the correct machine names. If you point to a machine using an incorrect name, you cannot connect to that server.
Interactive Reporting Studio

This section contains Oracle's Hyperion Interactive Reporting Studio installation and configuration issues.
Essbase Not Loaded Successfully

Issue: When connecting to Essbase, this error displays: Essbase not loaded successfully. Solution: Ensure that these environment variables exist and reference the correct Essbase installation location:
l
ARBORPATH Path (for Windows) LD_LIBRARY_PATH (for Solaris and Linux) SHLIB_PATH (for HP-UX) LIBPATH (for AIX)
Faulty Oracle Net Connection

Issue: 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 Oracle install location:
l
ORACLE_HOME
Path (for Windows) LD_LIBRARY_PATH (for Solaris and Linux) SHLIB_PATH (for HP-UX) LIBPATH (for AIX)
74
Failure Processing an Oracle Procedure

Issue: When processing an Oracle procedure with Oracle Wire Protocol ODBC client, this error displays: 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, select Procedure Returns Results. UNIX: Open odbc.ini, set the ProcedureRetResults property to 1 for your Oracle Wire Protocol 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 that the 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 Reporting
This section contains Financial Reporting installation and configuration issues.
Invalid User Name Error When Starting Financial Reporting Studio

Environment: A new installation in a distributed environment where Financial Reporting is in a different server than Shared Services. Issue: invalid user name error when trying to run Oracle's Hyperion Financial Reporting Studio. 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 File

Issue:
l
In a new installation, users cannot create a Planning Details data source connection. In an existing installation, users cannot connect to reports.
Solution: Copy PlanningSystemDB.properties from the Planning server to these two places on the Reporting and Analysis server:
hyperion/common/adm/planning/9.3.1/lib Hyperion/biplus/lib
Error Running Financial Reporting Studio on the Desktop

Environment: Financial Reporting Studio is running on the desktop. Issue: Error, Active X 429. Solution: Run the Hyperion Configuration Utility.
Runtime and ActiveX Errors

Issue: A series of runtime and ActiveX errors is displayed during Oracle's Hyperion Financial Reporting Studio login. Solution: Run <BIPlus>\install\bin\HRRunAnt.cmd, reboot, and log in.
Web Analysis
This section contains Oracle's Hyperion Web Analysis System 9 installation and configuration issues.
Error Connecting to SAP BW

Issue: Unable to retrieve list of available cubes displays when you connect to SAP BW during data source creation in Oracle's Hyperion Web Analysis Studio. Solution: Install and configure SAP JCo. See Configuring SAP Data Source Access and Authentication in the Hyperion Reporting and Analysis - System 9 Installation Guide.
BEx Query Not Listed

Issue: 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 access to the query.
76
9
In This Chapter
Troubleshooting Financial Performance Management Applications
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 external authentication, see Chapter 5, Troubleshooting Shared Services and Provisioning . For information about error logs, see Chapter 4, Logs.
Planning Access
Failure Accessing Planning through Workspace
Issue: 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> is the Web server listen port; for example, 19000 if using the Apache instance configured with Reporting and Analysis. 2. If step 1 does not work, verify that you have configured the Workspace proxy server plugin. If it is configured, test that you can access Planning directly.
Failure Accessing Planning Directly

Issue: You cannot access Planning through the Workspace, and need to access Planning directly.
77
Solution: Try this URL: http://<hostname>:8300/HyperionPlanning/LogOn.jsp. If this does not work, Planning did not install correctly. Check the Planning log in
<HYPERION_HOME>\logs\.
Upgrading Issues
Software Compatibility
Issue: You must ensure that the new release of Planning is compatible with the release of Shared Services that you are using. Solution: To check compatibility, see the Release Compatibility chapter of Hyperion Installation Start Here. Issue: You receive an SSL error message when using Planning 9.3.1 with Shared Services. Solution: Upgrade the version of Shared Services to 9.3.x.
Updating .Properties Files to Upgrade to 9.3.0.1

Issue: You are upgrading from an earlier release to Planning 9.3.0.1 and are not using the same servers 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 old HspJSHome.properties BEFORE using the Property File Migration Utility in 9.3.0.1. The PropFileMig.cmd in 9.3.0.1 is designed for an in-place upgrade. For example, it upgrades to the same servers hosting SQL and Essbase, using the same user names and passwords. It also uses the same location for css.config. Before running the PropFileMig.cmd utility, ensure that HspJSHome.properties has the correct information to transfer to the new 9.3.x environment. To restore existing applications to new locations, you must manually change the information in HYPSYS_Properties and PlanningSystemdb.properties before running the utility. Otherwise, the information is overwritten in these files and the upgrade is not successful.
Folder Structure
The location of files is as follows:
l
All .jar files are in the lib, not Utils folder All .exe, .bat, .sh, cmd and .exe files are in the bin folder instead of Utils ico and .properties files (essbase.properties, PlanningSystemDB.properties, and so on) are in the config folder instead of Utils
Offline.exe and SmartView.exe are in the bin, not Deployment folder
78
Planning Instances
Issue: Configuration of Planning requires creating a product instance. Because this is a new concept, it can be confusing to existing customers. Solution: Review the explanation from the Hyperion Planning System 9 Installation Guide excerpted here. An instance is a name for a group of Planning applications. An instance may contain 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 in PlanningSystemDB.properties. You can designate an instance as the active instance during instance creation or at any time using the Product Instance Registration option in the Configuration Utility. If you designate an instance 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 association can be modified using the Re-associate Instance and Application task. Note that if you add or change the active instance, you must restart the Planning application server in order for the updated application list to be displayed in Workspace.
Configuring Planning with Reporting and Analysis

To use Planning with Reporting and Analysis in release 9.3.1, you must install the Planning ADM driver on the machine that is hosting Oracle's Hyperion Financial Reporting System 9. To install on a different machine from Planning, use the Custom option to select the Planning ADM driver.
Using Planning with Administration Services

Issue: 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 as PlanningSystemDB.properties. If not, copy it to the same folder.
Performance Issues
Issue: You are using an Oracle database and experience performances issues with Cube Refresh. Solution: Ensure that CURSOR_SHARING in Oracle is set to EXACT. This is the default setting. Issue: You are experiencing performance issues with Oracle's Hyperion Planning System 9.
79
Solution: Tune the Webserver or increase heap size, depending on your environment. Hyperion recommends 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 external authentication, see Chapter 5, Troubleshooting Shared Services and Provisioning . For information about error logs, see Chapter 4, Logs.
Accessing Financial Management

Failure Accessing Financial Management Through Workspace
Issue: 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> is the Web server listen port; for example, 19000 if using the Apache instance configured with Reporting and Analysis. 2. If step 1 does not work, verify that you have configured the Workspace proxy server plugin. If it is configured, test that you can access Financial Management directly.
Failure Logging on to Financial Management

Issue: You cannot log on to Financial Management because there might be a security access issue. Solution: Check the following;
l
Financial Management is installed and configured. IIS is started, and a virtual directory for Financial Management was created. In IIS, verify the settings for authentication. You can use Anonymous Authentication or Web Authentication, depending on your security policies.
To check the authentication method:

1 Start IIS and expand Default Web Site. 2 Right-click the folder for Web authentication; for example, the Financial Management folder for the Web,
and select Properties.
3 Select Directory Security. 4 Verify that either Anonymous Access or Web Authentication has been properly configured.
80
Connection Troubleshooting
These are some common connection issues for Financial Management.
Connection to Financial Management Fails

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

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

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

Solution: Configure the UDL file.
Connection to SQL Server Fails

Issue: You receive an SQL Server: Test connection failed because of an error in 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 Server authentication. Hyperion recommends using SQL Server authentication. See Verifying Microsoft SQL Server Authentication Settings on page 82.
Common Financial Management Issues
81
The system may be using the Microsoft SQL Server default setting to connect to the database using named pipes instead of TCP/IP. See Establishing the SQL Server Connection Using TCP/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, and
click Next.
6 Select this authentication option: With SQL Server authentication using a login ID and password entered by
the user.
7 Click Client Configuration, select TCP/IP (if not selected), and click OK. 8 For Connect to SQL Server, enter the login ID and password, and click Next. 9 Change the default database to the Financial Management database. 10 Click Next, and click Finish. 11 Click Test Data Source. 12 When you receive the success message, click OK, and click OK to close the dialog box. 13 Click OK to close the ODBC Administrator dialog box. 14 Create and configure the data link: .udl.
Verifying Data Link Connection Settings 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.
82
3 Right-click the database server name, and select Properties. 4 Select Security. 5 Ensure that this Authentication option is selected: SQL Server and Windows. 6 Click OK.
Rights Required for Installation

Issue: You are having difficulty installing and configuring Financial Management. Solution: Ensure that you have local administrator rights to install Financial Management.
Failure Registering Financial Management Server on Client Machine

Issue: Cannot register the Financial Management server on a client machine. Solution: On the Application Server Clusters tab in the Financial Management Configuration Utility, click Enable Limits. This enables Remote Activation and should be performed on the machine hosting the application server.
Large Data or File Loads Fail

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

Installing and Configuring Performance Management Architect
This section contains troubleshooting tips for Performance Management Architect and installation and configuration issues you may encounter.
Installation Fails
Issue: Performance Management Architect Installation failed.
83
Solution: This could be the result of a Microsoft .NET Framework 2.0 error during its automatic installation in Performance Management Architect. Install Microsoft .NET Framework 2.0 manually, and then rerun the installation. Issue: You receive an ASP.NET error during configuration. Solution: Ensure that ASP.NET is installed and configured. See the Hyperion Financial Management System 9 Installation Guide or the Hyperion Planning System 9 Installation Guide.
Accessing Performance Management Architect

Performance Management Architect Logon Fails
Issue: 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. b.
listed.
Start > Programs > Administrative Tools > Internet Information Services Manager Run inetmgr.
2 In the left panel, select Web Service Extensions. In the right panel, note whether ASP.NET 2.0.50727 is 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. b. c. From the command prompt, go to this directory: C:\Windows\Microsoft.NET
\Framework\v2.0.50727
enter aspnet_regiis.exe iru. Repeat steps 1, 2 and 3.
Security Rights Issue When Logging On

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

Solution: Ensure that you have followed the installation and configuration instructions for Workspace in the Hyperion Reporting and Analysis Installation Guide.
84
Failure Starting the Process Manager Service

Issue: 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 for Performance Management Architect.
Failure Displaying the Dimension Library in Performance Management Architect

Issue: You cannot see the Dimension Library in Performance Management Architect. Solution: Verify that you have the proper Performance Management Architect roles. You must have the Dimension Editor and Application Creator security roles to access the Dimension Library. See Shared Services-Global Roles in the Hyperion Security Administration Guide. After you are assigned the Dimension Editor role, log off and log back on to Performance Management Architect.
Failure Displaying Tasks in Performance Management Architect

Check the following:
l
Verify that the Shared Services server is started, and if not, start it. See the Shared Services Installation Guide. Verify that Workspace services are started. See the Hyperion Reporting and Analysis Installation Guide. 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> is the Web server listen port, for example, 19000 if using the Apache instance configured with Reporting and Analysis. Verify that you have configured the Workspace proxy server plug-in for your Application Server. Use this URL:http://<Web Server>:<port>/awb/conf/AWBConfig.xml where <Web Server> is the Web server machine hostname and <port> is the Web server listen port; for example, 19000 if using the Apache instance configured with Oracle's Hyperion Reporting and Analysis System 9. If you can access this URL, the proxy server is configured. If you cannot, configure it. See the Hyperion Reporting and Analysis Installation Guide.
Failure Accessing Performance Management Architect Dimension or Application Library

If you cannot access a Performance Management Architect task, verify that you can access each component separately to locate the source of the communication error.
85
Server Unable to Process Request Error

Issue: You receive a Server was unable to process request. No connection
could 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 Errors

Possible Solutions: 1. Check this URL:
http(s)://<workspace_server>:<workspace_port>/awb/conf/AwbConfig.xml.
2. If this step fails, check this URL:

http(s)://<bpma_server>:<bmpa_port>/awb/conf/AwbConfig.xml
3. If this step works, then Performance Management Architect is not correctly enabled in Workspace. Reconfigure Oracle's Hyperion Workspace. 4. If this step does not work (error is 404), then the Performance Management Architect Web Server is not started.
Performance Management Architect Dimension Server Errors

Possible solutions:
l
Use this URL:

http(s)://<local_machinename>/hyperion-bpma-server/Sessions.asmx.
If you see a Sessions page displayed, then IIS is correctly configured. If there is any error in IIS, check the Event Log to determine the problems. Check the System and Application Log to see if anything was logged by ASP.NET, IIS, or DCOM, and fix the errors. A possible cause is incorrect privileges for the user for the TEMP directory.
l
Check the Event Logs from sources starting with HyS9EPMA. Possible causes are communication errors with Shared Services or the database. The ASPNET user may not have access to certain folders. If the Event Log displays any security-related errors, assign rights to the ASPNET user. 1. From the command prompt, go to this directory: C:\Windows\Microsoft.NET
\Framework\v2.0.50727.
2. Enter run aspnet_regiis.exe-ga.
Failure Accessing the Performance Management Architect Dimension Server Web Services
Possible Solutions:
86
In the logs, if subcode is 2, and Win32 code is 1260, the problem is related to Web Service Extensions. In IIS, Web Service Extensions, ensure that the ASP.NET 2.0.50727 Web Service Extension status is Allowed. 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 Library

Solution: 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 Dimension Server

From Control Panel > Administrative Tools > Services, start World Wide Web Publishing Service, if not already started.
Performance Management Architect Services Startup Failure

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

Issue: You experience performance issues using an IBM DB2 database with Oracle's Enterprise Performance Management Architect.
87
Solution: Implement the settings described in the Hyperion Financial Management System 9 Installation Guide or Hyperion Planning System 9 Installation Guide.
Common Performance Scorecard Issues

Configuration Issues
Java.lang.NoSuchMethod Error
Issue: Receive a java.lang.NoSuchMethodError error after installing and configuring multiple products. Solution: You receive a java.lang.NoSuchMethodError error if you install and configure Performance 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 application server. Solution: If you deployed to an existing application server, remove the HPSWebReports and HPSAlerter directories before re-installing. Check the log file for the application server for information about the error you received.
Multiple, Different Port Numbers

Issue: There are different port numbers for each application server type. Solution: Although you can have several versions of Tomcat on the same computer, each instance must have a unique port number. View the ports being used by opening a DOS console and entering netstat -a.
Insufficient Authorization Error

Issue: 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.
88
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 JVM Options Tab topic in the Informatica PowerCenter Installation and Configuration Guide.
Performance Issues
Problems Load Balancing in Clustered Deployment
Issue: Load balancing is problematic for multiple applications deployed to a cluster. Solution: If you install and run multiple instances of Performance Scorecard, configure each instance using the clustered deployment option. Also ensure that each instance uses the same database 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.
Increase these entries:

m
hyperion.hps.formula.value_caching_limit hyperion.hps.datapoint.cached_result_limit hyperion.hps.datapoint.cached_target_limit
5 Save and close the file. 6 Restart the application server and Performance Scorecard.
Frequent Session Time-outs

Issue: 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 external authentication, 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>
5 Save and close the file. 6 Restart the application server and Performance Scorecard.
Common Strategic Finance Issues

Performing Diagnostics on Strategic Finance Service
Hyperion Strategic Finance Service is the service running on the server. To collect diagnostic information and troubleshoot problems, you must be logged on to the system with full administrator privileges. Diagnostics can be performed directly on the server or using a remote access program. Use event logs and other logs to debug the system. See the Hyperion Strategic Finance Administrators Guide.
Server Memory and Error Logs

If you receive an Access violation at breakpoint c0000005 or Not enough storage space available to process this command error, restart the Strategic Finance Server.
Using Novell
To use Novell, copy all Novell users into an LDAP security provider, and then configure Strategic Finance 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 before configuring for external authentication.
90
Common Strategic Finance Issues
91
92
10
In This Chapter
Troubleshooting Data Management
Common Data Integration Management Issues.................................................................................93 Common FDM Issues ..............................................................................................................95 Common Data Relationship Management Issues...............................................................................96
Common Data Integration Management Issues

This section contains installation and configuration issues you may encounter and troubleshooting tips for Data Integration Management.
Connection Issues
These are some issues that you may encounter when connecting to Data Integration Management.
Service Stops after Starting

Issue: The Hyperion Data Integration Management Server service stops immediately after starting, and the Workflow Monitor displays this error message: Cannot connect to the
server HyperionIntegrationServer.
Solution: 1. Start the service:

l
Windows Select Start > Settings > Control Panel > Administrative Tools > Services and try starting the services manually.
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 Informatica PowerCenter Installation and Configuration Guide, Appendix B: Code Pages. See Accessing Informatica Documentation in the Data Integration Management Installation 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 Data Integration 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 System 9 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 and Configuration 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 one for the Repository Server Admin Console.
94
Solution: Ensure that you enter the correct passwords during configuration.
Common FDM Issues

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

Issue: Server/cluster is incorrectly configured. Please reconfigure your Cluster or Server connection Solution: Update the machine profile in the workbench to point to the appropriate Financial Management cluster registered on the Oracle's Hyperion Financial Data Quality Management application servers.
Oracle Client/Provider Cannot Connect to Database

Issue: 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 in
tnsnames.ora.
Cannot Authenticate User

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

1 Launch Workbench. 2 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 Insert

Error: Could not bulk insert because file '\\<servername>\<shared
foldername> \<application foldername>\Inbox\<filename>.fmt' could not be opened. Operating system error code 5 (error not found)
Common FDM Issues
95
Solution: Ensure that the user who runs the SQL service has access to the UNC share and Read permissions to the application.
To check access:
1 Check the SQL server to see which user is running MSSQLServer service. If local account, change to domain
and 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 Bulk
Insert Rights.
Common Data Relationship Management Issues

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

Review these topics in the Data Relationship Management Readme to ensure that you install and configure properly:
l
Using Shared Services via SSL Microsoft .NET Installing on Windows 2000 Server Upgrade May Get Error after Reboot Daylight Savings Time Offsets for As Of Versions (Release 9.3.0.x only) Compatibility with Microsoft Data Execution Prevention (Release 9.3.0.x only) Running Data Relationship Management with Oracle's Hyperion Financial Management System 9 (Release 9.3.0.x only)
Access is Denied
Issue: In the Event Log, you receive the Access Is Denied error message. Solution: Check if the user has the proper rights. The domain, username and password entered on the Windows COM+ Logon dialog box must be entered correctly.
Server Unable to Process Requests

Issue: You receive the Server was Unable to Process Request error message. Solution: For successful connectivity to the Data Relationship Management Web gateway, each user must have write access to the Windows/Temp directory on the machine where the client application runs. Check that users have write access.
96
Failure Installing on Windows 2000

Issue: When running the installer for a Complete installation on Windows 2000 SP4, the installer could display the interrupted prior to completion message. All components appear to have been installed successfully, but the database is not created and config.xml is not fully populated. Solution: Run the installer and select Repair.
Configuration Issue
Issue: Receive error message Cannot configure the system. Please check the configuration Solution: Ensure the hostname field on the Common Security Services page of the Hyperion Data Relationship Management console contains the correct name of the server where CSS is running.
Unable to Create JVM

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

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

Issue: Oracle's Hyperion Data Relationship Management server fails to start. Solution:
l
If you changed the classpath or system path, you must reboot the computer. Change the authentication mode to Internal and start the server again. If it starts successfully, this confirms that the issue is related to CSS. Check the Event Log for error messages
Common Data Relationship Management Issues
97
Upgrade Issues
Error Message Incorrectly Displays During Upgrade
Issue: An error may appear during an install upgrade: Service Hyperion S9 Master Data Management failed to install with error: System Error. Code: 1073. The specified service already exists Solution: Ignore message by clicking OK and upgrade completes successfully.
98
Index
A
about this guide assumed knowledge, 9 audience, 9 purpose, 9 access Architect, 84 Architect Dimension Server WebServices, 86 denied, Data Relationship Management, 96 Financial Management applications, 80 Planning, 77 Planning from Workspace, 77 products from Shared Services, 55 Reporting and Analysis modules, 73 Apache logs, 44 application server logs, 43 Oracle 10.1.2.0.2 and Shared Services, 50 Performance Scorecard issues, 88 startup failure, Shared Services, 56 application server deployment failure without configuration errors, 65 load balancing in cluster, Performance Scorecard, 89 WebLogic version unsupported, 65 Architect accessing Dimension library or Application library, 85 accessing server Webservices, 86 displaying Dimensions Library, 85 displaying tasks, 85 errors on server, 86 IIS startup on Architect DimensionServer, 87 installation failure, 83 logon, 84 opening dimension library, 87 services startup failure, 87 assumed knowledge, 9
B
BEx query unavailable, Web Analysis, 76 browser exception, Performance Scorecard, 88 Business Rules logs, 37
C
cannot authenticate user, Financial Data Management, 95 cannot connect to Oracle database, Financial Data Management, 95 cannot perform bulk insert, Financial Data Management, 95 common diagnostics tasks, initial diagnostics, 15 common issues Architect, 83 Data Integration Management, 93 Data Relationship Management, 96 Financial Data Management, 95 Financial Management, 80 Performance Scorecard, 88 Planning, 77 Strategic Finance, 90 user directories and Shared Services, 51 common log location, 19 configtool.log, 13 configtool_err.logn, 12 configuration Data Integration Management, 94 Data Relationship Management, 97 error log, 12 exceptions, logged, 13 file descriptor limit error, 66 Financial Data Management, 95 general tips, 65 Shared Services, 49 validation, 12, 15 Configuration Utility
Index
99
launching on UNIX, 66 logs, 20 connection failure Data Integration Management, 93 Essbase client-server, 70 Financial Management, 81 general, resolving, 63 OLAP metadata catalog or external datasource, 71, 81 Oracle NET, 74 Reporting and Analysis, 74 Shared Services, 54 corruption, OpenLDAP, 54 CSS Spy, 48 CSS.xml, 51
documentation, additional, 13
E
error messages application server deployment out of memory, 65 Architect, 86 Essbase, 58 Essbase Administration Services, 59 Essbase load with Interactive Reporting, 74 Essbase Provider Services, 59 file descriptor limit, UNIX, 66 Financial Data Management, 95 Financial Management, 61 Financial Reporting Studio, 75 illegal plug-in, Data Integration Management, 94 JVM on UNIX, 66 Performance Scorecard, 62, 88 Provider Services, out-of-memory, 72 Reporting and Analysis, 60 Shared Services, 50 Strategic Finance, 90 WebLogic version unsupported, 65 Essbase diagnostics, 16 installation initialization error, 70 load failure, Interactive Reporting Studio, 74 logs, 24 server startup failure, 69 server-client connection, 70 troubleshooting, 69 use with Shared Services, 57 Essbase Administration Services administrator login failure, 71 filters, assigning, 71 logs, 25 refreshing security to Shared Services, 59 troubleshooting, 70 use with Planning, 79 with Shared Services, 58 Essbase Integration Services logs, 26 OLAP or data source connection failure, 71 Essbase Provider Services adding provider to Administration Services, 59 load balancing with WebLogic and Apache, 72 out-of-memory errors, 72
D
Data Integration Management common issues, 93 configuration , 88 connection failure, 93 failure to load JVM Library, 94 illegal plug-in operation, 94 logs, 40 service stopping after starting, 93 unable to run workflow, 94 Data Integration Management Adapter use with Performance Scorecard, 89 Data Relationship Management access denied, 96 common issues, 96 configuration issues, 97 diagnostics, 18 installing on Windows 2000, 97 invalid classpath root, 97 logs, 40, 41 readme issues, 96 server startup failure, 97 unable to create JVM, 97 user rights issues on client machine, 96 DB2, use with Performance Management Architect, 87 deployment failure without configuration errors, 65 out of memory error, 65 WebLogic unsupported error, 65 diagnostics, common, 15
100 Index
Essbase System 9 logs, 24 external authentication, 15 external user directories, 51
F
failure accessing Financial Management from Workspace, 80 Apache Tomcat, startup, 66 application server deployment, 65 Architect Dimensions Library, displaying, 85 Architect Services, 87 Architect tasks, displaying, 85 Configuration Utility, launching, 66 connection to OLAP metadata catalog or datasource, 71 Data Relationship Management server startup, 97 Essbase Administration admin login, 71 Essbase server, 69 Financial Management Server, registering, 83 IIS startup on Architect Dimension Server, 87 login, Financial Management, 80 login, Workspace, 84 OpenLDAP, startup, 53 Oracle Procedure, processing, 75 Planning, accessing directly, 77 Planning, accessing from Workspace, 77 Process Manager Service, starting, 85 Reporting and Analysis modules, accessing, 73 Reporting and Analysis, connection in distributed environment, 74 Shared Services service or process startup, 55 Shared Services startup, application server, 56 FDM diagnostics, 18 file descriptor limit error, 66 Financial Data Management cannot perform bulk insert, 95 common issues, 95 configuration issues, 95 logs, 41 Oracle/Client provider connection, 95 user authentication, 95 Financial Management access from Workspace, 80 accessing, 80 common issues, 80
connection failure, 81 diagnostics, 17 error messages, 61 installation failure, 81 large data or file loads, 83 logon failure, 80 logs, 35 registering server on client, 83 rights for installation, 83 SQL Server connection failure, 81 use with Shared Services, troubleshooting, 61 Financial Performance Management applications Architect, accessing Dimension library or Application library, 85 common Architect issues, 83 common Financial Management issues, 80 configuring Planning with Reporting and Analysis, 79 DB2 performance settings, 87 diagnostics, Strategic Finance, 90 establishing the SQL Server connection using TCP/ IP, 82 issues with Performance Scorecard, 88 performance issues, 79, 89 Performance Management installation and configuration, 83 Performance Scorecard configuration, 88 Planning with Administration Services, 79 Planning, access issues, 77 running Strategic Finance on Novell, 90 Strategic Finance issues, 90 troubleshooting connection issues, 81 upgrade issues, 78 Financial Performance Management Applications logs, 35 Financial Reporting invalid user name error, 75 logs, 32 Planning Details datasource connection, 76 Financial Reporting Studio running on desktop, 76 runtime and ActiveX errors, 76 Foundation Services, diagnostics, 16
H
Hyperion Installation Start Here, 11
Index 101
I
IIS logs, 44 installation additional documentation, 13 Architect, failure, 83 Data Relationship Management, Windows 2000, 97 Essbase initialization, 70 Financial Management, failure, 81 installation directory error, 64 logs, 20 Performance Management Architect, 83 rights for Financial Management, 83 Shared Services, 49 validation, 12, 15 Interactive Reporting Studio data truncation, 75 Essbase load failure, 74 logs, 33 Oracle Net connection, 74 Oracle procedures, processing, 75 invalid classpath root, Data Relationship Management, 97 invalid user name error, Financial Reporting, 75
J
JVM error, UNIX, 66
K
knowledge base, My Oracle Support (MetaLink 3), 13
L
load balancing Performance Scorecard applications in cluster, 89 login Architect, 84 Essbase Administration Services, 71 Financial Management, 80 Shared Services, 50 Shared Services, admin, 56 Shared Services, improving performance, 51 User Management Console, using proxy server, 56 Workspace, 84 logs Apache, 44
102 Index
application server, 43 Business Rules, 37 common location, 19 configuration, 12 Configuration Utility, 20 Data Integration Management, 40 Data Relationship Management, 40, 41 Essbase, 24 Essbase Administration Services, 25 Essbase Integration Services, 26 Essbase System 9, 24 file size, 20 Financial Data Management, 41 Financial Management, 35 Financial Performance Management Applications, 35 Financial Reporting, 32 IIS, 44 installation, 20 Interactive Reporting Studio, 33 levels, specifying, 20 Oracle 10.1.x, 44 overview, 13 Performance Management Architect, 35 Performance Scorecard, 38 Planning, 36 Reporting and Analysis, 27 Shared Services, 20 Smart View, 23 SQR Production Reporting, 33 Strategic Finance, 39 SunJES, 44 system performance, 20 Tomcat 5.0.28, 44 Translation Manager, 40 Web Analysis, 34 Web server, 44 WebLogic 6.0, 43 WebLogic 8.1, 43 WebLogic 9.1, 43
M
MetaLink 3, 13 My Oracle Support, 13
O
OpenLDAP common issues, 54 corruption, 54 corruption, resolving without backup, 58 log levels, 22 startup commands, 22 startup failure with Shared Services, 53 tips, 54 Oracle 10.1.2.0.2 application server login, Shared Services, 50 Oracle 10.1.x logs, 44 Oracle application server Shared Services login, 50 Oracle procedure, processing, 75
P
performance issues Financial Performance Management applications, 89 logs, 20 Performance Scorecard decreasing startup time, 89 load balancing in clustered deployment, 89 Performance Management Architect accessing, 84 common issues, 83 diagnostics, 17 installing and configuring, 83 logs, 35 Performance Scorecard browser exception, 88 common issues, 88 configuration issues, 88 Data Integration Management Adapter, 89 decreasing application startup, 89 diagnostics, 17 failure loading JVM library, 89 insufficient authorization error, 88 Java.lang.NoSuchMethod error, 88 load balancing in clustered deployment, 89 logs, 38 use with Shared Services, 62 Planning accessing from Workspace, 77 common issues, 77 configuring with Reporting and Analysis, 79
creating instances, 79 diagnostics, 17 direct access, 77 directory structure, 78 logs, 36 upgrade issues, 78 upgrading from 9.3.0.1, 78 with Essbase Administration Services, 79 port conflicts avoiding, 12 defaults for all products, 11 prerequisites additional documentation, 13 configuration, validation, 12 Hyperion Installation Start Here, reviewing, 11 installation, validation, 12 logs, reviewing, 13 port, avoiding, 12 product Reporting and Analysis, 16, 18 Essbase, 16 FDM, 18 Financial Management, 17 Performance Management Architect, 17 Performance Scorecard, 17 Planning, 17 Strategic Finance, 18 readme, reviewing, 12 release compatibility, validating, 11 startup dependencies, reviewing, 12 system requirements, satisfying, 11 provisioning best practices, 51 using Shared Services, 51 proxy server User Management Console, accessing with, 56
R
registering Financial Management Server, 83 release compatibility, 11 Reporting and Analysis connection failure, 74 diagnostics, 16 error messages, 60 logs, 27 logs, analyzing, 32 logs, configuring, 31
Index 103
module access failure, 73 tips, 73 use with Shared Services, 59 restarting services, 63 runtime and Active X errors Financial Report Studio, 76
S
server startup failure, Data Relationship Management, 97 services Architect Process Manager, startup, 85 Architect startup failure, 87 Data Integration Management, 93 Shared Services startup failure, 55 start and restart, 63 services, Windows, verifying, 64 Shared Services admin user login, 56 application server startup failure, 56 common problems, 47 configuration, 49 connection failure, 54 CSS Spy, using, 48 external user directories, 51 failure accessing products from, 55 installation, 49 JRE on server, incorrectly set, 49 load performance, increasing, 51 login performance, improving, 51 login, Oracle application server, 50 logs, 20 startup failure, 55 troubleshooting, 47 troubleshooting utilities, 48 use with Reporting and Analysis , 59 User Management Console, accessing with proxy server, 56 user provisioning best practices, 51 user provisioning, troubleshooting, 50 using on multiple computers, 49 using with Performance Scorecard, 62 using with Essbase, 57 using with Financial Management, 61 using with Integration and Administration Services, 58 using with upgraded products, 50
104 Index
using with Workspace, 60 WebDav calls on WebLogic, 52 Smart View logs, 23 SQL Server, establishing a connection using TCP/IP, 82 SQR Production Reporting logs, 33 starting services, 63 startup OpenLDAP commands, 22 startup dependencies, 12 startup failure Architect services, 87 configuration utility on UNIX, 66 IIS on Architect Dimension Server, 87 OpenLDAP, 53 Shared Services, 55 Tomcat on UNIX, 66 startup time, decreasing Performance Scorecard, 89 Strategic Finance common issues, 90 diagnostics, 18, 90 logs, 39 running on Novell, 90 SunJES logs, 44 support, accessing, 14 system requirements, 11
T
technical support, 14 Tomcat 5.0.28 logs, 44 Tomcat, launching on UNIX, 66 Translation Manager logs, 40
U
unable to create JVM, Data Relationship Management, 97 UNIX Configuration Utility, launching, 66 file descriptor limit error, 66 JVM error, 66 starting Tomcat, 66 UnsatisfiedLinkError-GetOSVersion, 60 upgrade issues Data Relationship Management, 98
upgrading Financial Performance Management applications, 78 Planning from 9.3.0.1, 78 software compatibility, 64 user authentication, Financial Data Management, 95 user directories using with Shared Services, 51 user provisioning, 47 best practices, 51 troubleshooting, 47, 50
V
validation, installation and configuration, 12
W
Web Analysis BEx query unavailable, 76 failure retrieving cubes using SAP BW, 76 logs, 34 WebDav calls on WebLogic, 52 WebLogic 8.1, logs, 43 9.1, logs, 43 load balancing, Essbase Provider Services and Apache, 72 version unsupported error, 65 WebDav calls, 52 WebLogic 6.0, logs, 43 Webserver logs, 44 Windows 2000, installing, 97 Workspace accessing Financial Management from, 80 accessing Planning from, 77 changing Server DNS name, 60 logon security rights, 84
Index 105
106 Index

Hsys9 Install Config Troubleshoot

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Hsys9 Install Config Troubleshoot

Caricato da

Copyright:

Formati disponibili

HYPERION

INSTALLATION AND CONFIGURATION TROUBLESHOOTING GUIDE

Network environment and port usage

Perform these tasks before contacting Support for assistance.

Reviewing the Installation Start Here

Meeting System Requirements

Checking Release Compatibility

Reviewing the Installation Start Here

Avoiding Port Conflicts

Reviewing Startup Dependencies

Reviewing the Readme

Using Product Installation Guides

Validating the Installation and Configuration

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

You can connect to an external user directory and Shared Services

Using My Oracle Support (MetaLink 3)

Using Shared Services Troubleshooting Utilities

Document Product Installation Guide

Location Oracle E-Delivery and product DVD

Oracle Technology Network

Accessing Technical Support Resources

Alliance wide support Enterprise wide support Standard support

For help by phone, use the country listings on http:\

Validating Installation and Configuration

Performing Common Diagnostics

Shared Services External Authentication Services are running

Performing Common Diagnostics

Foundation Services Diagnostics

Reporting and Analysis Diagnostics

Service is running on <host>

Validating Installation and Configuration

Performance Management Architect Diagnostics

Financial Management Diagnostics

Performance Scorecard Diagnostics

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

Performance Management Architect Diagnostics

Strategic Finance Diagnostics

Data Relationship Management Diagnostics

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

Validating Installation and Configuration

Common Log File Location

Common Log File Location

Log File Size and System Performance

Hyperion Configuration Utility Logs

Log File Names and Descriptions

Setting Log Levels

Shared Services Logs

Log File Names and Descriptions

SharedServices_Memory_Profiler.log SharedServices9.log SharedServices.log openldap.log

Setting Log Levels

Shared Services Logs

Setting Message Levels to Debug Shared Services

Log Levels for the OpenLDAP Database

OpenLDAP Startup Command slapd -d -1 slapd -d 0 slapd -d 1 slapd -d 2 slapd -d 4 slapd -d 8

slapd -d 16 slapd -d 32 slapd -d 64 slapd -d 128 slapd -d 256

OpenLDAP Startup Command

Description provides fewer logs than the -1 option.)

Smart View Logs

File Names and Descriptions

Contents Smart View error messages

Setting Log Levels and Routing Messages to a Log File

Smart View Logs

Essbase System 9 Logs