Monday, June 6, 2011

Using Remote Diagnostic Agent (RDA) to Troubleshoot Oracle Hyperion EPM 11.1.2.1

Using Remote Diagnostic Agent (RDA) to Troubleshoot Oracle Hyperion EPM 11.1.2.1 [ID 1304885.1]
Modified 26-MAY-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
References

Applies to:

Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Goal

Provide brief instructions on how to run RDA 4.23 in Oracle Hyperion Enterprise Performance Management (EPM) 11.1.2.1 for various Hyperion products.
Solution

EPM 11.1.2.1 comes bundled with a current version (4.23) under \Oracle\Middleware\EPMSystem11R1\rda.

To use this tool:
1. First ensure that Perl 5.005 or later is available by typing the following from the command line:

perl -v

If not, you may need to download a binary copy of rda and add a value to RDA_ENG in the configuration file \engine\rda.cfg; Please refer to DOC ID 330363.1 (FAQ #6) for further information.

2. Navigate via the command line to \Oracle\Middleware\EPMSystem11R1\rda

3. Type the following:

rda.cmd -V > version.txt

4. Type 'notepad version.txt' and confirm that the first line has 'RDA 4.23' or later

5. If it is not version 4.23 or later, in http://support.oracle.com go to DOC ID 314422.1 and click on the "Download RDA" hyperlink, following instructions to download the appropriate version of the application. Delete the existing \Oracle\Middleware\ohs\rda directory. Then extract the downloaded file to any convenient place...such as \Oracle\Middleware\ohs (it will create a directory called 'rda').

6. Navigate via the command line to that 'rda' directory and type rda.cmd -V > version.txt and confirm output as elaborated in step (4) above.

7. Command lines (with an example of SQR Production Reporting and Interactive Reporting [PR HIRs] as module names):
Type on Command Line
Explanation
rda.cmd -Q PR HIR
-Q will alert you to most of the questions that will be posed by RDA to facilitate its collection of information. Collect those details before running the modules.
rda.cmd -M PR HIR
This will describe (man page) what information will be collected by these modules.
rda.cmd -S PR HIR -p Essbase

This will collect instructions and values to be entered into the setup.cfg file for modules PR and HIR and profile Essbase. Only two files and one TMP directory will be written to the output directory.
rda.cmd -vnSCRP PR HIR
This will configure (de nouveaux) the setup.cfg file and then run the data collection mechanism, compressing data to (by default) be placed in the ..\output\ directory.
rda.cmd
This will execute the instructions previously entered into the setup.cfg file (rda.cmd run with -S parameter). Note that this is a two step process, and after this step starts a large number of files with extensions *.txt, *.fil, and *.toc will first be written. At the end files with *.htm extensions will be written.
rda.cmd -x profiles
This will provide a cross reference between the available profile names and the (programmer's) module names which are executed under each profile.
rda.cmd -T emp In recent versions, this 'tool' will run validate scripts and return a report listing each validation result. You should only run this after having previously run the EPM module. In addition at the bottom of the validate reporting page you may click on a hyperlink to access a zip file containing logs generated on the server.


Modules which would be particularly interesting to Oracle Hyperion users would be:

Module Abbreviation
Module Application Name
BI
Oracle Business Intelligence Enterprise Edition
BIPL
Oracle Business Intelligence Publisher
CCR
Oracle Configuration Manager
EPM
Oracle Hyperion Enterprise Performance Management
EPMA
Oracle Hyperion Enterprise Performance Architect
ESS
Oracle Hyperion Essbase
FCM
Oracle Hyperion Financial Close Management
HDRM
Oracle Hyperion Data Relationship Management
HFM
Oracle Hyperion Financial Management
HFR
Oracle Hyperion Financial Reports
HIR
Oracle Hyperion Interactive Reporting
HPL
Oracle Hyperion Planning
HPSV
Oracle Hyperion Planning SmartView
HSS
Oracle Hyperion Shared Services
HSV
Oracle Hyperion Smart View
PR
Oracle Hyperion SQR Production Reporting

There are also a few profiles (sets of modules) available which could be useful when troubleshooting Oracle Hyperion products:
Profile Abbreviation
Profile Descriptive Name
EPMA_FullRun
Oracle Enterprise Performance Management Architect problems
Essbase
Oracle Essbase problems
FCM_FullRun
Oracle Hyperion Financial Close Management problems
FinancialReporting
Oracle Hyperion Financial Reporting problems
FM11g_Bi
Business Intelligence Enterrpise Edition 11g problems
FM11g_WlsBi
Business Intelligence Enterprise Edition 11g with WLS
HFM_FullRun
Oracle Hyperion Financial Management problems
Hyperion_DRM
Oracle Hyperion Data Relationship Management problems

When setting up a profile or module a number of questions are asked, some typical value assignments include (Although the default install on Microsoft Windows would be to "C:\Oracle\Middleware\", the user may chose a different install home):

ORACLE_HOME=C:\app\\product\11.2.0\dbhome_1
JAVA_HOME=C:\Oracle\Middleware\jdk160_21
EPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1
EPM_ORACLE_INSTANCE_ROOT=C:\Oracle\Middleware\user_projects
domain home directory=C:\Oracle\Middleware\user_projects\domains

In the \rda\setup.cfg file ensure the following are set to acceptable values:
CMD_ZIP='C:\Oracle\Middleware\ohs\bin\zip.exe'
RPT_GROUP= {some name in single quotes}
RPT_DIRECTORY= {some path in single quotes}


Note the cross-references to articles describing how to use RDA to troubleshoot problems with specific Oracle Hyperion products.

No comments:

Post a Comment