oracle® enterprise performance management system

Oracle Enterprise Performance Management System

Installation and Configuration Troubleshooting Guide

Release 11.1.2.2

Updated: April 2013

EPM System Installation and Configuration Troubleshooting Guide, 11.1.2.2

Copyright 2007, 2013, Oracle and/or its affiliates. All rights reserved.

Authors: EPM Information Development Team

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respectiveowners.

This software and related documentation are provided under a license agreement containing restrictions on use anddisclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement orallowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit,perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilationof this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you findany errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf ofthe U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS:

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customersare "commercial computer software" or "commercial technical data" pursuant to the applicable Federal AcquisitionRegulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, andadaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, tothe extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, CommercialComputer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is notdeveloped or intended for use in any inherently dangerous applications, including applications that may create a risk ofpersonal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take allappropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliatesdisclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

This software or hardware and documentation may provide access to or information on content, products, and servicesfrom third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of anykind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsiblefor any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Documentation Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

About Troubleshooting EPM System Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Assumed Knowledge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installation Documentation Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2. Troubleshooting Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Meeting System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Reviewing the Installation Start Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Checking Release Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Avoiding Port Conflicts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Reviewing Startup Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Reviewing the Readme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Using the Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Checking Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Validating the Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Using EPM System Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Deployment Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Using Enterprise Manager for Monitoring Web Applications . . . . . . . . . . . . . . . . . . . . . . 21

Using My Oracle Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Using the Ziplogs Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Accessing Technical Support Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 3. Using EPM System Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

EPM System Product Logging Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Logging Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

ODL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Log4j . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

ODL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

ODL Configuration File Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Configurable ODL Log Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Modifying ODL Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Contents iii

Modifying ODL Logging Attributes with WebLogic Administration Console . . . . . . . 35

Remote and Local Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Backup Files for Remote Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Log4j Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Message Types and Logging Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

ODL Message Types and Logging Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Log4j Logging Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Setting Logging Levels in Enterprise Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Setting Interactive Reporting Logging Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Log Rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

ODL Log Rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Log4j Log Rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Installation, Configuration, and Diagnostic Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Application Server, Web Server, and EPM System Process Logs . . . . . . . . . . . . . . . . . . . . 43

Upgrade Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Foundation Services Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Lifecycle Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Essbase Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Reporting and Analysis Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Reporting and Analysis Framework Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Financial Reporting Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Web Analysis Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Interactive Reporting Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Financial Performance Management Application Logs . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Planning Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Financial Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Performance Scorecard Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Profitability and Cost Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Disclosure Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Financial Close Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

SOA Suite Server Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Strategic Finance Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Data Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

FDM Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

FDMEE Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Data Relationship Management Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Central Inventory Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

iv Contents

Chapter 4. General Tips and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Installation Tips and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

EPM System Installer Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

EPM System Installer Files on Client Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Oracle HTTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Proxy Servlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Product Selection Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

EPM System Installer Extraction on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

EPM System Installer Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

EPM System Installer Startup After MSI Installation . . . . . . . . . . . . . . . . . . . . . . . . . 64

EPM System Installer Freeze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Welcome Panel Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Reinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Configuration Tips and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Distributed Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Changing a Host Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Java Heap Size Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Product Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

EPM System Configurator Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Oracle HTTP Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Out-of-Memory Error with Multiple Web Application Deployments . . . . . . . . . . . . . 69

First-Time Configuration of the Shared Services Database . . . . . . . . . . . . . . . . . . . . . 69

Connection to a Clustered SQL Server Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Missing JAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Configuration Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Configuration Task Panel: Missing Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Configuration Errors for Hidden Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Unavailable Database Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Remote Deployment Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

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

Moving Web Applications to a Single Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Reconfiguration Without Reinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Windows Integrated Authentication Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Out-of-Memory Errors With Concurrent Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Resolving Connection Failures and Restarting Services . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Demo Certificate Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

WebLogic Administration Console Port Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

WebSphere Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Contents v

Deploying Web Applications with the Integrated Solutions Console Running . . . . . . . 74

Specifying the Admin User During Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Determining the Port Number for the Integrated Solutions Console . . . . . . . . . . . . . 75

Launching the Integrated Solutions Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Starting, Stopping, and Restarting the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Restarting Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Updating an EAR File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Redeploying an EAR File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Removing a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Determining the Bit Type of the WebSphere Installation . . . . . . . . . . . . . . . . . . . . . . 77

UNIX-Specific Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Slow Web Application Startup with TC2000 Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Web Server Configuration Failure on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

JAR Files Not Found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Installation on Different UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Preparing JVM Error Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Oracle Common Files Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 5. Foundation Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Foundation Services Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Foundation Services Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

EPM Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Slow Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Missing Products or Product Menus in EPM Workspace . . . . . . . . . . . . . . . . . . . . . . 84

Truncated Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Oracle Business Intelligence Enterprise Edition Startup . . . . . . . . . . . . . . . . . . . . . . . 84

Flickering Icons in Internet Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Disabled Icons in Internet Explorer Are Displayed With a White Background . . . . . . . 85

Blank Screen with Mozilla Firefox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

404 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Performance Degradation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Running Remote Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Shared Services Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

High Availability of Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Product Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Security Lockout After Failed Logon Attempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Asterisks in User Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

EPM System Administrator User Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

vi Contents

AuditHandler Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Audit Data Purges and Oracle Database Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Single Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Shared Services Registry Contents and Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

User Directories and Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Startup and Access Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Product-Specific Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Lifecycle Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Migration Tip: Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Out-of-Memory Errors in a Compact Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Comparing Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

SSL Application Freeze or Name Mismatch Error . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Shared Services Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Export Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Lifecycle Management Timeout for Artifact Imports . . . . . . . . . . . . . . . . . . . . . . . . . 98

Lifecycle Management Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Lifecycle Management and Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Lifecycle Management and Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . 100

Performance Management Architect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Installation Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Validation Errors After Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Integration with EPM Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Performance Management Architect Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Security Rights Issue During Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Hyperion EPMA Server Service Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Performance Management Architect Task Display . . . . . . . . . . . . . . . . . . . . . . . . . 106

File Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Performance Management Architect Dimension or Application Library Access . . . . . 107

Application Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Smart View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Installation Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Smart View Shared Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Chapter 6. Essbase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Essbase Maintenance Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Essbase and Provider Services Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Essbase Staging Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Role Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Essbase Studio Configure Database Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Contents vii

Login from MaxL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Pre-upgrade Security File Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Connections to Essbase Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Essbase Server Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Essbase Startup in Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Essbase Failover Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Client-Server Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

OPMN Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Startup: Port Conflict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Integration Services: Connection to OLAP Metadata Catalog or External Data Source . . . 116

Essbase Studio Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Essbase Studio Logs Deleted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Chapter 7. Reporting and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Reporting and Analysis Framework Web Application Startup . . . . . . . . . . . . . . . . . . . . 119

Interactive Reporting Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Essbase Loading Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Faulty Oracle Net Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Failure Processing an Oracle Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Fonts Displayed Incorrectly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Reporting Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Web Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Web Analysis Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Error Connecting to SAP BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

BEx Query Not Listed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Chapter 8. Financial Performance Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Financial Performance Management Application Upgrades . . . . . . . . . . . . . . . . . . . . . . 123

Financial Management Application Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Planning Applications Not Visible in EPM Workspace . . . . . . . . . . . . . . . . . . . . . . 124

Planning and Administration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Performance Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Using Planning in a Non-English Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Planning Server Shut Down Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Installation with FDM on Windows 64-Bit System . . . . . . . . . . . . . . . . . . . . . . . . . 127

Accessing Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Connection Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

viii Contents

Rights Required for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Large Data or File Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Sticky Server Attempts to Redirect User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

EnableServerLocking Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

JRF WebServices Asynchronous Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Financial Close Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

General Financial Close Management Troubleshooting Tips . . . . . . . . . . . . . . . . . . 134

Enabling OWSM Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Out-of-Memory Error on Managed Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

HumanWorkflow Engine Errors in SOA Server Log . . . . . . . . . . . . . . . . . . . . . . . . 135

Financial Close Management Installation and Configuration Issues . . . . . . . . . . . . . 136

Repeated Warning of Unavailable Bean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Financial Close Management Schedule Execution Issues . . . . . . . . . . . . . . . . . . . . . 141

Account Reconciliation Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Disclosure Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Chapter 9. Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

FDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

FDM Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Shared Services Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Configuration with Financial Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Oracle Client-Provider Database Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Database User ID or Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Bulk Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Active-X Component Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Application Creation Access Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Failure to Create a New FDM Application on 64-bit Windows . . . . . . . . . . . . . . . . . 156

FDMEE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Inaccessible Data Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

FDMEE Unavailable in EPM Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Data Relationship Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Web Client Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Failure To Initialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

JVM Creation Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Invalid Classpath Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Data Relationship Management Server Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Error Message During Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Contents ix

x Contents

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website athttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle SupportOracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

11

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacchttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=infohttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=infohttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=trshttp://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

12 Documentation Accessibility

1Introduction

In This Chapter

About Troubleshooting EPM System Products.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Assumed Knowledge... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Installation Documentation Roadmap ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Check the Oracle Documentation Library (http://www.oracle.com/technology/documentation/epm.html) on Oracle Technology Network to see whether an updated version of this guide isavailable.

About Troubleshooting EPM System ProductsThis guide provides troubleshooting tips for installing and configuring Oracle EnterprisePerformance Management System products. It contains general information about how toapproach troubleshooting, important documentation to review, and how to use logs. Alsoprovided are solutions to difficulties that you may encounter using Oracle Hyperion SharedServices to provision and share users among EPM System product applications and solutions todifficulties using Oracle Hyperion Enterprise Performance Management Workspace, and OracleHyperion Reporting and Analysis.

Assumed KnowledgeThis guide is for administrators who install, configure, and manage EPM System products. Itassumes the following knowledge:

l Security and server administration skills

l Windows or UNIX administration skills

l Web application server administration skills

l A strong understanding of your organization's security infrastructure, includingauthentication providers such as Oracle Internet Directory, LDAP, or Microsoft ActiveDirectory, and use of SSL

l A strong understanding of your organization's database and server environments

l A strong understanding of your organization's network environment and port usage

About Troubleshooting EPM System Products 13

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

Installation Documentation RoadmapYou can find EPM System installation documentation in the Oracle Documentation Library(http://www.oracle.com/technology/documentation/epm.html) on Oracle TechnologyNetwork. For faster access to the documentation for a specific release, you can use the EnterprisePerformance Management Documentation Portal (http://www.oracle.com/us/solutions/ent-performance-bi/technical-information-147174.html), which also contains links to EPMSupported Platform Matrices, My Oracle Support, and other information resources.

Always check the Oracle Documentation Library (http://www.oracle.com/technology/documentation/epm.html) on Oracle Technology Network to see whether updated versionsof these guides are available.

Table 1 lists the documents to consult for instructions on performing essential installation tasks.

Table 1 Documentation That You Need

Task Related Documentation

Meeting system requirements and understanding releasecompatibility

Oracle Hyperion Enterprise Performance Management System CertificationMatrix (http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html) listed in the Oracle Business Intelligenceproduct area.

Planning the installation Oracle Hyperion Enterprise Performance Management System InstallationStart Here

l Installing, configuring, and deploying EPM Systemproducts

l Starting EPM System products

l Validating the installation

l Upgrading EPM System products

l Clustering EPM System products

l Setting up disaster recovery for EPM System products

Oracle Hyperion Enterprise Performance Management System Installationand Configuration Guide

Securing EPM System Oracle Hyperion Enterprise Performance Management System SecurityAdministration Guide

Provisioning users Oracle Enterprise Performance Management System User SecurityAdministration Guide

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

Table 2 Documentation That You Might Need


Troubleshooting installations Oracle Hyperion Enterprise Performance Management System Installation andConfiguration Troubleshooting Guide

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

14 Introduction

http://www.oracle.com/technology/documentation/epm.htmlhttp://www.oracle.com/technology/documentation/epm.htmlhttp://www.oracle.com/us/solutions/ent-performance-bi/technical-information-147174.htmlhttp://www.oracle.com/us/solutions/ent-performance-bi/technical-information-147174.htmlhttp://www.oracle.com/technology/documentation/epm.htmlhttp://www.oracle.com/technology/documentation/epm.htmlhttp://www.oracle.com/technology/documentation/epm.htmlhttp://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.htmlhttp://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html


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

Table 3 lists supplemental best-practice deployment documents.

Table 3 Best-Practice Deployment Documents


Best-practice approach for deploying EPM System Oracle Enterprise Performance Management System Standard DeploymentGuide

Tutorial for deploying the Oracle Hyperion Planning domainfor development environments

Oracle Enterprise Performance Management System Rapid Deployment ofOracle Hyperion Planning in Development Environments

Tutorial for deploying the Oracle Essbase domain fordevelopment environments

Oracle Enterprise Performance Management System Rapid Deployment ofOracle Essbase in Development Environments

Tutorial for deploying the Oracle Hyperion FinancialManagement domain for development environments

Oracle Enterprise Performance Management System Rapid Deployment ofOracle Hyperion Financial Management in Development Environments

Additional content is available in the White Paper Library at Oracle Enterprise PerformanceManagement /Business Intelligence White Papers.

Installation Documentation Roadmap 15

http://www.oracle.com/technetwork/goto/epmwhitepapershttp://www.oracle.com/technetwork/goto/epmwhitepapers

16 Introduction

2Troubleshooting Basics

In This Chapter

Meeting System Requirements .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Reviewing the Installation Start Here... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Reviewing the Readme .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Using the Installation Guide ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Checking Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Validating the Installation and Configuration... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Using EPM System Diagnostics.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Deployment Reports .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Using Enterprise Manager for Monitoring Web Applications ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Using My Oracle Support .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Using the Ziplogs Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Accessing Technical Support Resources .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Note: Perform the tasks described in this chapter before contacting Technical Support forassistance.

Meeting System Requirements Before installing EPM System products, ensure that your environment meets the requirementsspecified in the Oracle Hyperion Enterprise Performance Management System CertificationMatrix. You can find the matrix at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.

Oracle Hyperion Enterprise Performance Management System Installer checks whether yourenvironment meets the prerequisites for the EPM System components that you are installing.EPM System Installer displays the results of some of those checks on its Welcome screen.

Reviewing the Installation Start HereOracle Enterprise Performance Management System Installation Start Here contains prerequisites,default ports, and other information needed to plan a successful installation.

Meeting System Requirements 17

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.htmlhttp://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Checking Release CompatibilityIf you are upgrading from a previous release, it is important to check whether the softwareversions of EPM System products in your environment are compatible. See the Oracle HyperionEnterprise Performance Management System Certification Matrix (http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html).

Avoiding Port ConflictsDuring EPM System product configuration, default port numbers for Web applications arepopulated automatically. You can change the defaults during configuration, but each portnumber must be unique. To avoid error messages such as port already in use or bind error,review the list of default product port numbers in Oracle Enterprise Performance ManagementSystem Installation Start Here.

Reviewing Startup Dependencies Ensure that you have reviewed the startup dependencies for EPM System products in the OracleEnterprise Performance Management System Installation and Configuration Guide. You may needto start services manually. Before you start services or processes, start all databases used asrepositories.

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

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

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

Using the Installation GuideThe Oracle Enterprise Performance Management System Installation and Configuration Guideprovides step-by-step installation and configuration procedures for all products. Very often youcan find the answer to an installation or configuration issue by using the installation guide toverify that you have correctly completed all required steps.

For information regarding installation and configuration issues in distributed environments,review Installing EPM System Products in a Distributed Environment in Chapter 4, Installing

18 Troubleshooting Basics

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.htmlhttp://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

EPM System Products, and Chapter 5, Configuring EPM System Products, of the OracleEnterprise Performance Management System Installation and Configuration Guide.

Checking LogsA fundamental troubleshooting technique is to enable and use debugging information inproduct log files. Use this technique before calling Technical Support so that you can providespecific information about your issue. See Chapter 3, Using EPM System Logs, for details onlog contents and locations.

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

l Use Oracle Hyperion Enterprise Performance Management System Diagnostics to test thestatus of installed and configured EPM System components, diagnose problems, and assistin problem resolution. Run EPM System Diagnostics on each machine in the deployment.The results of the tests are saved in HTML format. For more information, see Using EPMSystem Diagnostics on page 19.

l Check for exceptions and errors in the installation logs to ensure that all necessarycomponents were installed successfully.

l Check that all configuration tasks succeeded, as follows:

m The Oracle Hyperion Enterprise Performance Management System Configuratorsummary panel does not display failures or warnings.

If error messages are displayed, check EPM_ORACLE_INSTANCE/diagnostics/logs/config/configtool_summary.log.

m No exceptions are displayed in EPM_ORACLE_INSTANCE/diagnostics/logs/config/configtool.log.

For more information, see Installation, Configuration, and Diagnostic Logs on page 39.

Using EPM System DiagnosticsEPM System Diagnostics performs these tests:

l CFG: Configuration - Whether all configuration tasks have been completed

l DB: Database - Connection to database host:port;databaseName

l EXT: External Authentication - Native Directory external authentication providerconfiguration

l HTTP: http - Availability of HTTP context for all components configured for the Web server

l SSO:

m Status of Shared Services security (Native Directory as well as external directories)

Checking Logs 19

m Availability of login to Shared Services, Taskflows, Audit, Shared Services Webapplication, and Oracle Hyperion Enterprise Performance Management SystemLifecycle Management

l WEB: Web application - Availability of Web application on host:port

l Additional product-specific tests

The report that EPM System Diagnostics creates each time you run it includes this information:

l Test date and time

l Test Status: Passed or Failed for each test

l Service: Type of test for each test

l Test Description: A detailed description of each test

l Duration: Duration of each test

l Test start time

l Test end time

l Total test duration

EPM System Diagnostics also generates a ZIP file of all EPM System logs (the equivalent ofzipping up EPM_ORACLE_INSTANCE/diagnostics/logs).

To use EPM System Diagnostics:

1 Start EPM System Diagnostics by one of these methods:

l (Windows)

m In EPM_ORACLE_INSTANCE/bin, double-click validate.bat.

m From the Start menu, select Programs, then Oracle EPM System, then FoundationServices, then instanceName, and then EPM System Diagnostics.

l (UNIX) From a console, change to EPM_ORACLE_INSTANCE/bin, and then entervalidate.sh.

2 To view the results, navigate to EPM_ORACLE_INSTANCE/diagnostics/reports and openvalidation_report_date_time.html.

3 Check the results for failed tests, and diagnose and resolve problems.

4 Run EPM System Diagnostics again, and view the new report to verify that problems are solved.

For more information about EPM System Diagnostics, see the Oracle Enterprise PerformanceManagement System Installation and Configuration Guide.

Deployment ReportsYou can generate a deployment report that provides information about configured Webapplications, Web servers, and databases and all data directories used by EPM System products.


This information can be useful in troubleshooting. For more information, see Generating aDeployment Report in the Oracle Enterprise Performance Management System Installation andConfiguration Guide.

Using Enterprise Manager for Monitoring WebApplicationsOracle Enterprise Manager Fusion Middleware Control is deployed automatically with EPMSystem. You can use it to manage all Java Web applications in EPM System out of the box. Thefull version of Enterprise Manager with Grid Control adds functionality on top of the FusionMiddleware Control, including historical information of the metrics. For more informationabout Enterprise Manager Fusion Middleware Control, see the Oracle Enterprise PerformanceManagement System Installation and Configuration Guide.

Using My Oracle SupportIf you have a current support agreement and a customer support identifier, you can search theMy Oracle Support knowledge base for information about resolving installation andconfiguration issues. You can also use My Oracle Support for entering service requests,downloading software releases and patches, and other online support tasks.

Note: Before creating a service request (SR) about an installation or configuration issue, run theziplogs utility. See Using the Ziplogs Utility on page 21.

Oracle Configuration Manager, which EPM System installations include in the EPM Oraclehome directory, collects information about your Oracle software installation and configurationand uploads the information to My Oracle Support. The information collected by OracleConfiguration Manager speeds resolution of problems and enables My Oracle Support to tailorcontent for your configuration.

Oracle recommends that you adjust the default sources for your knowledge base searches, ifnecessary, to include documentation for your Hyperion products.

For more information, click Getting Started on the My Oracle Support home page.

Using the Ziplogs UtilityBefore creating a service request (SR) about an installation or configuration issue, run the utilityziplogs.bat (Windows) or ziplogs.sh (UNIX) in EPM_ORACLE_INSTANCE/bin. Whenyou create the SR, attach the output from the script, which is saved toEPM_ORACLE_INSTANCE/diagnostics/ziplogs. The output is a zipped collection of logs,configuration files, and other information that can help Support to resolve installation andconfiguration issues.

Using Enterprise Manager for Monitoring Web Applications 21

Accessing Technical Support Resources To help you effectively operate, manage, and run EPM System performance managementsolutions by delivering technical expertise whenever you need it, Oracle Support Services isavailable at http://www.oracle.com/support/index.html.

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within theUnited States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.


http://www.oracle.com/support/index.html

3Using EPM System Logs

In This Chapter

EPM System Product Logging Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Logging Formats... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

ODL Configuration... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Remote and Local Logging ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Backup Files for Remote Logging... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Log4j Configuration ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Message Types and Logging Levels .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Log Rotation ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Installation, Configuration, and Diagnostic Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Application Server, Web Server, and EPM System Process Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Upgrade Logs... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Foundation Services Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Lifecycle Management Logs... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Essbase Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Reporting and Analysis Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Financial Performance Management Application Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Data Management Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Central Inventory Logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

EPM System Product Logging MatrixThe tables in this section provide information about logging by EPM System tools, components,and products, including logging formats, default message types and logging levels, and loggingconfiguration file names and locations.

This section uses the default domain, EPMSystem, in logging configuration file locations. Forany installation that has been configured to use a different domain name, substitute that domainname for the EPMSystem domain.

This section also uses default names for managed servers; for example, FoundationServices0 isthe default name for the Foundation Services managed server. For any installation that has beenconfigured to use a different managed server name, substitute that managed server name for thedefault name.

EPM System Product Logging Matrix 23

Note: With compact deployment, all logs are in MIDDLEWARE_HOME/user_projects/domains/EPMSystem/servers/epmserver0/logs. The logging configuration file(logging.xml) is located in MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/epmserver0.

The default logging levels for EPM System products are the levels that Oracle recommends, butyou can change them for most products. For information about message-type and logging-leveloptions, see Message Types and Logging Levels on page 36.

Table 4 EPM System Installation and Configuration Logging Formats

Tool / Component LoggingFormat

DefaultMessageType /LoggingLevel

Logging Configuration File

EPM System Installer

See Installation, Configuration,and Diagnostic Logs on page39.

ODL TRACE In the installer image, in the same location as installTool.jar: installTool-logging.xml

EPM System Configurator

See Installation, Configuration,and Diagnostic Logs on page39.

ODL TRACE EPM_ORACLE_HOME/common/config/11.1.2.0/configTool-logging.xml

EPM System Diagnostics andValidation Tool

ODL TRACE EPM_ORACLE_HOME/common/validation/11.1.2.0/validationTool-logging.xml

EPM System Uninstaller ODL TRACE EPM_ORACLE_HOME/uninstall/uninstall-logging.xml

Table 5 Foundation Services Logging

Product LoggingFormat

DefaultMessage Type /Logging Level


SharedServices andEPMWorkspace

ODL NOTIFICATION MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/FoundationServices0/logging.xml

LifecycleManagementfor SharedServices(commandprompt)

ODL NOTIFICATION EPM_ORACLE_INSTANCE/config/FoundationServices/logging.xml

24 Using EPM System Logs


DefaultMessage Type /Logging Level


LifecycleManagementfor Essbase

ODL NOTIFICATIONl EPM_ORACLE_INSTANCE/config/FoundationServices/logging.

xmlFor migrations that are run from a command Line utility

l MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/

fmwconfig/servers/FoundationServices0/logging.xmlFormigrations that are run from Shared Services.

Oracle HyperionEPM ArchitectDimensionServer

ODL NOTIFICATION:32

EPM_ORACLE_INSTANCE/config/EPMA/DimensionServer/logging.xml

PerformanceManagementArchitect DataSynchronizer

ODL NOTIFICATION:32

MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/EpmaDataSync0/logging.xml

PerformanceManagementArchitect WebApplication

ODL NOTIFICATION:32

MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/EpmaWebReports0/logging.xml

Oracle HyperionCalculationManager

ODL WARNING MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/CalcMgr0/logging.xml

Oracle HyperionSmart View forOffice

ODL Not Applicable Smart View is a client-side application. The name and location of the file where itlogs events, errors, and other information are specified as options in Smart View. Formore information about Smart View logging options, see the Oracle Hyperion SmartView for Office User's Guide.

Table 6 Essbase Logging


DefaultMessageType /Logging Level


Essbase Server ODL TRACE:1 EPM_ORACLE_INSTANCE/EssbaseServer/essbaseserver1/bin/logging.xml

Oracle EssbaseAdministrationServices

ODL WARNING MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/EssbaseAdminServices0/logging.xml

Oracle HyperionProvider Services

ODL WARNING:1 MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/AnalyticProviderServices0/logging.xml

Oracle EssbaseStudio

ODL INFO, FINE EPM_ORACLE_INSTANCE/BPMS/bpms1/bin/logging.xml

Oracle EssbaseIntegrationServices

Log4j -L2 To enable logging and set the logging level, use the -L switch when startingIntegration Services. For more information, see the Oracle Essbase IntegrationServices System Administrator's Guide.


Table 7 Reporting and Analysis Logging


Default MessageType / LoggingLevel


Oracle HyperionReporting andAnalysisFramework

ODL WARNING:1 MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/RaFramework0/logging.xml

Reporting andAnalysisFrameworkServices

ODL WARNING:1 EPM_ORACLE_INSTANCE/config/ReportingAnalysis/logging/logging_ra.xml

Reporting andAnalysisFramework Agent

ODL WARNING:1 EPM_ORACLE_INSTANCE/config/ReportingAnalysis/logging/logging_agent.xml

Reporting andAnalysisFramework JobUtilities loggingconfiguration forCalendarManager

ODL WARNING:1 EPM_ORACLE_INSTANCE/config/ReportingAnalysis/JobUtilities/logging_ju.xml

Reporting andAnalysisFramework SDK

ODL WARNING:1 EPM_ORACLE_INSTANCE/config/ReportingAnalysis/SDK/logging.xml

Oracle HyperionInteractiveReporting

ODL WARNING:1 EPM_ORACLE_INSTANCE/config/ReportingAnalysis/logging/logging_ir.xml

Oracle HyperionFinancialReporting

ODL ERROR:1 MIDDLEWARE_HOME/user_projects/domains/EPM_System/config/fmwconfig/servers/FinancialReporting0/logging.xml

FinancialReporting PrintServer

ODL NOTIFICATION:32 EPM_ORACLE_HOME/products/financialreporting/lib/printserverlogging.xml

FinancialReporting Clients

ODL NOTIFICATION:32 EPM_ORACLE_HOME/products/financialreporting/lib/clientlogging.xml

Oracle HyperionWeb Analysis

ODL WARNING:1 MIDDLEWARE_HOME/user_projects/domains/EPMSystem/fmwconfig/servers/WebAnalysis0/logging.xml

Table 8 Financial Performance Management Application Logging




Planning Proprietary DEBUG You use Planning to set the logging level for each Planning application server.See Planning Logs on page 55.





ODL (for ADFlogging)

NOTIFICATION:32 EPM_ORACLE_HOME/products/Planning/logging/logging.xml

FinancialManagement

ODL ERROR:1 These files in EPM_ORACLE_HOME/products/FinancialManagement/logging:

l InteropLogging.xml

l logging.xml

FinancialManagementWeb Application

ODL NOTIFICATION:32 MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/HFMAdfWeb0/logging.xml

FinancialManagementWeb Services

ODL NOTIFICATION:32 MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/FMWebServices0/logging.xml

Oracle HyperionPerformanceScorecard

Log4j Warn These files in EPM_ORACLE_INSTANCE/HPS/hpsfiles/config:

l HPSConfig.properties for Web user interface

l AlerterConfig.properties for the alerter server

Oracle HyperionProfitability andCostManagement

ODL NOTIFICATION:1 MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/Profitability0/logging.xml

Oracle HyperionStrategic FinanceServer

Proprietary Error The logging level is set for each Strategic Finance server. Use the Administratorapplication to modify the server configuration for logging.

Strategic FinanceWeb Application

Proprietary All (Off by default) Logging is turned on or off with all levels of information being logged whenturned on. This setting is in the Windows registry.

Oracle HyperionDisclosureManagement

ODL INFO MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/DisclosureManagement0/logging.xml

Oracle HyperionFinancial CloseManagement(including CloseManager andAccountReconciliationManager)

ODL NOTIFICATION MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/FinancialClose0/logging.xml


Table 9 Data Management Product Logging


Default Message Type /Logging Level

Logging Configuration

Oracle HyperionFinancial DataQualityManagement

Log4j DEBUG

Note: You cannot changethe logging level for FDM

You can configure the load balancer to activate or deactivate logon error-logging. For instructions, see Oracle Enterprise PerformanceManagement System Installation Start Here.

Oracle HyperionFinancial DataQualityManagementEnterpriseEdition

ODL NOTIFICATION MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/servers/ErpIntegrator0/logging.xml

Oracle DataRelationshipManagement

Notapplicable

Not applicable Enable logging in the Data Relationship Management installer. See theOracle Data Relationship Management Installation Guide.

Logging FormatsMost EPM System products use the Oracle Diagnostic Logging (ODL) format for loggingpurposes. EPM System Installer and EPM System Configurator create ODL files for all products.Products not using ODL leave these ODL files empty and write their logs to different file formats,usually log4j.

ODL

Subtopics

l ODL Log File Naming

l ODL Log Elements

ODL provides plug-in components that complement the standard Java framework toautomatically integrate log data with Oracle log analysis tools such as Enterprise Manager.Another key benefit of ODL is automatic log file rotation based on maximum log size and otherproperties that you can set in a logging configuration file.

Note: EPM System Installer and EPM System Configurator create ODL files for all products.Any product not using ODL leaves the ODL file empty and writes its logs to a differentfile format.

ODL Log File NamingEach product, component, service, or servlet has its own log file. Separate log files are generatedfor license information, configuration, and, if necessary, environment information.


ODL Log ElementsODL logs use elements that show information about the origins of messages as well as themessages themselves. This information can be helpful in troubleshooting.

ODL log elements:

l Time StampDate and time when the message was generated, adjusted for time differencebetween the host where the message was generated and the host of the common repository

Example:

l Component IDManaged server that originated the message

Example: [FoundationServices0]

l Message Type

See ODL Message Types and Logging Levels on page 36.

l Message IDA short character string that uniquely identifies the message

Example: [EPMWKSP-000001]

l Module IDAn identifier for the class name or other code module that originated themessage

Example: [Initialization]

l Execution Context Id (ECID)Execution context ID, which helps connect multiple log files

Example: [ecid: 0000IPMCrhW17ic5PjWByd1BMQPg000002,0]

l Message textLog message

Log4j

Subtopics

l Log4j Log File Naming

l Log4j Log Message Elements

With log4j, logging behavior is controlled through XML configuration files at runtime.

Main components of log4j configuration files:

l LoggersControl which logging statements are enabled or disabled. Loggers may beassigned levels ALL, DEBUG, INFO, WARN, ERROR, FATAL, or INHERIT.

l AppendersSend formatted output to their destinations.

You can modify configuration files to turn log statements on and off per service or class (throughthe loggers), and to set logging levels for each logger.

Logging Formats 29

Log4j Log File NamingEach service or servlet has its own log file. In an environment with several installation locations,all services of one type log their messages to one file. Separate log files are generated for licenseinformation, configuration or environment information, and stdout messages. Services andservlets log file names format:

server_messages_OriginatorType.log

where OriginatorType is a specific servlet or service.

Log4j Log Message ElementsLog4j log messages contain this information, in this order:

l LoggerName of the logger that generated the logging message

l Time stampTime stamp in coordinated universal time (UTC); ensures that messages fromdiffering time zones can be correlated

l LevelLogging level

l ThreadThread name

l Sequence numberUnique number to identify messages with matching time stamps

l TimeWhen the message was generated

l ContextInformation about which component generated the log message:

m SubjectUser name

m Session IDUUID of the session

m Originator TypeComponent type name

m Originator NameComponent name

m HostHost name

l MessageLog message

l ThrowableStack trace of a throwable error

ODL Configuration

Subtopics

l ODL Configuration File Structure

l Configurable ODL Log Properties

l Modifying ODL Configuration Files

l Modifying ODL Logging Attributes with WebLogic Administration Console

Each EPM System product using the ODL logging format has at least one logging configurationfile, logging.xml. EPM System components have descriptive names in the formatloggingCOMPONENT_NAME.xml. Logging configuration files contain property settings that


control log location, maximum log size, message type and logging level, and so on. SeeConfigurable ODL Log Properties on page 32.

ODL Configuration File StructureAn ODL logging.xml files uses log handlers and loggers:

l Log handlers define log locations and rotations.

l Loggers define logging levels.

The following excerpt, from the logging.xml configuration file for EPM Workspace, includeslog file settings for the ConsoleHandler and ODLHandlerFactory components.

- - - - - -

ODL Configuration 31

......

- ......

Configurable ODL Log PropertiesYou can modify logging.xml files with a text editor to configure the properties of ODL logs,as shown in Table 10.

Table 10 Configurable ODL Log Properties

Log Property Description

path Log path

format Format to use

The recommended value is ODL-Text.

maxFileSize Maximum size in bytes for each log file

When the main log file reaches the given size, a log rotation is triggered, where the main log fileis archived and a new log file is created.

maxLogSize Maximum size in bytes for the entire log

Older archive files are deleted to keep the total log size under the given limit.

rotationFrequency Frequency, in minutes, for rotating the logs

The value must be a number (of minutes), or the word hourly, daily, or weekly. (This settingis not case-sensitive.)



baseRotationTime Base time for time-based log rotation; for example, the starting point for therotationFrequency setting

Default: January 1, 1970, UTC

Use one of these formats:

l HH:mm

l yyyy-MM-dd

l yyyy-MM-ddT-HH:mm

l yyyy-MM-dd-HH:mm:ss.sTZ, where TZ is the time zone indicator and can be Z for UTC oran offset from Greenwich Mean Time in the format plus_or_minusHH:mmm

Note: If the time format does not specify a time zone, the local time zone is used.

retentionPeriod How long log files are kept

Files that are older than the given period are deleted. Files are deleted only when there is a logrotation; no background thread deletes log files. As a result, files may not be deleted for sometime after the retention period expires. The value must be a number (minutes), or day, week, month(30 days) or year (values are not case-sensitive).

encoding The type of character encoding to use

XML files must be UTF-8 encoded to handle extended characters. The default is .

supplementalAttributes A comma-separated list of supplemental attribute names, which can be added to each log message

The attribute value must be defined in class ExecutionContext.

useSourceClassAndMethod Whether the Java source class and method name should be added to each log message

The value is a Level name. Messages of a given level or lower include the source class and methodname. The constants true and false are also accepted as aliases for OFF and ALL. The defaultvalue is TRACE:1 (Fine).

useDefaultAttributes Whether default attribute values should be added to each log message

The default attributes that can be assigned are HOST_ID, HOST_NWADDR and USER_ID. The valueshould be true or false. The default value is true for the ODL-XML format and false for theODL-Text format.

includeMessageArguments Whether message arguments are included with formatted log messages that also have a messageID

Possible values: true (default) or false.

useThreadName The useThreadName flag, which flags controls if the handler attempts to log the real thread nameinstead of the threadID provided by the java.util.logging.LogRecord

If the flag is true, the handler attempts to log the real thread name. In some cases, the handlermay not be able to determine the real thread name, in which case it will log the threadID. Thedefault value is true.

ODL Configuration 33


useRealThreadId The useRealThreadId flag, which flags controls if the handler attempts to log the real threadID instead of the threadID provided by the java.util.logging.LogRecord

If the flag is true, the handler will attempt to log the real thread ID. In some cases, the handlermay not be able to determine the real thread name, in which case it will log the threadID. Thedefault value is false. Logging the real Thread ID is mutually exclusive with theuseThreadName property. If useThreadName is true, the value of theuseRealThreadId property is ignored.

locale Default Locale override for localizing messages

The default value is the default Locale, which is set in EPM System Configurator.

keepOpen Whether the main log file is kept open at all times or opened and closed upon each log operation.

Possible settings: true and false. The default setting is true, which keeps the main log file openat all times.

In most cases you should use the default value.

deleteFiles Whether archive files can be deleted when the total log size reaches the maximum.

Possible settings: true and false. In most cases, the default value for the flag is true, whichmeans that old files can be deleted. In rare use cases, in which archive files should not be deleted,this flag can be set to false.

Note: If deleteFiles is set to false, and a maxLogSize limit is set, no messages are loggedafter the log reaches the specified maxLogSize limit.

autoFlushLevel The level setting for autoflushing

The ODLHandler allows log records to be buffered, but it automatically flushes the buffer whenit gets a log record with level equal to or higher than the specified autoFlush level. The defaultvalue is NOTIFICATION:1.

addJvmNumber The JVM number added to the log file name

The JVM number is defined by system property oracle.process.index. If the system propertyis not set, this option is ignored.

applicationContextProvider The name of a class that implements the ApplicationContext interface

The class must have a default constructor. The special value disabled can be used to disablelogging of application name. The default application context provider is platform-specific; in mostcases you need not set this property.

userContextProvider The name of a class that implements the UserContext interface

The class must have a default constructor. The special value disabled can be used to disablelogging of the user name. The default user context provider is platform-specific; in most cases youneed not set this property.

Modifying ODL Configuration FilesYou can modify a product's logging.xml file with a text editor to specify property settings forany of its logs. For example, you can change the message type and logging level, and you canchange the settings for properties that control log rotation and log file retention.


The following sample procedure changes the message type and logging level for Profitability andCost Management from NOTIFICATION :1 to TRACE:32 for Profitability and CostManagement. The sample procedure also increases the maximum file size, which is the size atwhich the log is automatically rotated. You can use the same steps with different file locationsto change all configurable log property settings for any EPM System product that uses ODL.

To modify the message type, logging level, and maximum log file size for in the configurationfile logging.xml:

1 Navigate to logging.xml for your product. See EPM System Product Logging Matrix on page 23.

For example, for Profitability and Cost Management, navigate to this default location:

MIDDLEWARE_HOME/user_projects/domains/EPMSystem/config/fmwconfig/

servers/Profitability0/logging.xml

2 Open logging.xml in a text editor.

3 Locate this line in logging.xml:

4 Modify the line to change the message type and logging level; for example:

5 To change the maximum file size for log files, modify the MaxFileSize setting.

6 Save the modified logging.xml file.

Your changes take effect when you restart the product or component.

Modifying ODL Logging Attributes with WebLogicAdministration ConsoleAdministrators can use WebLogic Administration Console to change logging levels and someother log-related attributes without modifying logging.xml and without restarting the system.

To change the logging levels using WebLogic Administration Console:

1 Click Lock & Edit.

2 Select EPMSystem(Domain), then Environment, then Servers.

3 Click the server name, then click the Logging tab.

4 Scroll down to expand the Advanced link, where you can set the logging level.

Remote and Local LoggingSome EPM System products use remote logging by communicating with Reporting and AnalysisFramework logging service.

Remote and Local Logging 35

In a distributed environment, you can use the remote logging feature to create all logs in oneplace for all the components running on different machines.

Select one machine in your distributed environment for this purpose, and enable logging serviceonly on this machine. You must disable logging service on all other machines. See the OracleHyperion Reporting and Analysis Framework Administrator's Guide.

By default, Reporting and Analysis Framework services and Interactive Reporting services areconfigured to use remote logging:

When you configure a machine for remote logging, the log files are not created on the local filesystem but are created on the machine where the logging service is running. You can change thisdefault configuration and choose to log messages locally. Interactive Reporting Log Service usesremote logging by default.

If a component is configured for local logging, then the Logging service is not used by thatcomponent.

Backup Files for Remote LoggingIf the Logging service fails, logging service log messages are written to backup files at the samelocation as the log files. Backup file names syntax:

COMPONENT_NAMELoggingBackup.log

When the Logging service is restored, the data from the backup files is transferred to thecorresponding log files on the machine where the Logging service is running. The backup filesare then removed.

Log4j ConfigurationLog4j uses two logging configuration file types, main and imported. Main files use the followingimported files, which organize the loggers and appenders into separate XML files:

l appenders.xml

l serviceloggers.xml

l debugLoggers.xml

Message Types and Logging LevelsFor most EPM System products, you can specify a message type (ODL) or logging level.

ODL Message Types and Logging LevelsODL uses message types as well as logging level. Message types and logging levels are controlledby settings in the loggers section of the configuration file. Oracle recommends lower messagetype settings for finer control.


ODL logging uses these message types:

l INCIDENT_ERRORA serious problem that may be caused by a bug in the product andthat should be reported to Oracle Support

l ERRORA serious problem that requires immediate attention from the SystemAdministrator and is not caused by a product bug

l WARNINGA potential problem that the System Administrator should review

l NOTIFICATIONA major lifecycle event such as the activation or deactivation of a primarysubcomponent or feature

l TRACETrace or debug information for events, such as public API entry/exit points

TRACE is the lowest message type, producing the most information; ERROR is the highestmessage type, producing the least information. You can also specify a numerical level withineach message type. For example, TRACE:32 provides more detail than TRACE:1.

You can change the message types and logging levels for a product's logs by using text editor tomodify the logging.xml file. See Modifying ODL Configuration Files on page 34.

Tip: Administrators can change logging levels for EPM Workspace and Reporting and AnalysisFramework services without modifying the configuration file. See Modifying ODLLogging Attributes with WebLogic Administration Console on page 35 and DynamicallyChanging Reporting and Analysis Framework Services Logging Levels on page 52.

Log4j Logging LevelsLogging levels for products that use the log4j format vary by product. For information aboutlog-level options for each product using log4j, see the section in this chapter about that product'slogs. For example, the FDMEE Logs on page 59 discusses logging level options for FDMEE.

Setting Logging Levels in Enterprise ManagerYou can use Enterprise Manager to change the logging levels for EPM System managed servers.

To change the logging level for a Web application:

1 In Enterprise Manager, right-click the managed server name, select Logs, and then select LogConfiguration.

2 Click the Logging Levels tab.

3 Expand Root Logger, then oracle, then oracle.apps, and then oracle.apps.epm.fcc.

4 Set the Oracle Diagnostic MESSlevel for both oracle.apps.epm.fcc.model andoracle.apps.epm.fcc.ui.

For example, set the logging level to Trace:32 (Finest).

Message Types and Logging Levels 37

5 Optional: To keep the change in effect after the current session, select Persist log level state acrosscomponent restarts.

6 Click Apply.

Setting Interactive Reporting Logging Levels

To change Interactive Reporting logging levels:

1 In EPM Workspace, select Navigate, then Administrator, then Reporting and Analysis, and thenServices.

2 Open the Properties dialog box for either Reporting and Analysis Framework or Interactive Reportingservices, and then select the Log panel.

3 Add, (for Reporting and Analysis Framework), remove (for custom loggers for Reporting and AnalysisFramework), or modify logger levels.

4 In the context menu, click Refresh Log Configuration. The changes are applied shortly.

Log Rotation

Subtopics

l ODL Log Rotation

l Log4j Log Rotation

ODL Log RotationLogs for products that use ODL are rotated automatically, depending on settings in the products'logging configuration files. For example, a log is rotated when its file size reaches the limitspecified in the maxFileSize property. ODL rotates a log by archiving the main log file andcreating a new main log file. For example, FoundationServices0.log is a main log file forOracle Hyperion Foundation Services. When FoundationServices0.log reaches thespecified maximum file size , it is archived as FoundationServicesn.log, where n is the nextnumber in the archive numbering sequence. For more information about ODL log file propertysettings that affect rotation and log file retention, see Table 10 on page 32.

Log4j Log RotationYou can roll and delete log4j log files by time intervals or by file size. File size log rotation iscontrolled by CompositeRollingAppender. Time interval log rotation is controlled byCompositeRollingAppender and a Java property in the common services start file.

The oldest log file is not deleted if RollingStyle=2, which is the default. is specified inappenders.xml.


All appenders in XML configuration files are configured to use default values forCompositeRollingAppender. You can configure CompositeRollingAppender propertiesfor each appender separately.

Note: If you want all log files to rotate using matching criteria, change the configuration foreach CompositeRollingAppender defined in both appenders.xml files.

Log4j log rotation recommendations vary by product.

To change log4j log rotation settings:

1 Open the appenders.xml file for services or servlets. Locations of