In which location shall the FR Print server 11.1.2.1 component be installed? [ID 1322103.1]
Modified 23-MAY-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
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
In which location should the FR Print server 11.1.2.1 component be installed?
Solution
The Financial Reporting Studio 11.1.2.1 component should be installed separate from the Oracle home directory where the EPM System 11.1.2.1 product suite has been installed. Most of EPM System 11.1.2.1 is installed under the Middleware folder (e.g., C:\Oracle\Middleware...), but in order for the Print Server to be able to access the relevant libraries, it should be installed under a separate subfolder (e.g., C:\Oracle\FinancialReportingStudio).
Monday, June 6, 2011
Cannot Create Financial Reporting Print Service in 11.1.2.1
Cannot Create Financial Reporting Print Service in 11.1.2.1 [ID 1321241.1]
Modified 23-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
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.
Symptoms
You have installed the Financial Reporting Studio and edited the FRSetupPrintServer.properties file with the Financial Reporting Web Server info and credentials. But the FRSetupPrintServer.cmd command completes and the FR Print Service has not been created.
Cause
The file is being run from the wrong location, which is as follows:
Oracle\Middleware\EPMSystem11R1\products\financialreporting\install\bin\FRSetupPrintServer.cmd
Solution
Run the FRSetupPrintServer.cmd file from the Financial Reporting Studio location.
Oracle\FinancialReportingStudio\products\financialreporting\install\bin\FRSetupPrintServer.cmd
If you had installed the Studio and Print Server under Middleware instead of the default location (as shown above), uninstall these components then re-install them to the default folder.
Modified 23-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
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.
Symptoms
You have installed the Financial Reporting Studio and edited the FRSetupPrintServer.properties file with the Financial Reporting Web Server info and credentials. But the FRSetupPrintServer.cmd command completes and the FR Print Service has not been created.
Cause
The file is being run from the wrong location, which is as follows:
Oracle\Middleware\EPMSystem11R1\products\financialreporting\install\bin\FRSetupPrintServer.cmd
Solution
Run the FRSetupPrintServer.cmd file from the Financial Reporting Studio location.
Oracle\FinancialReportingStudio\products\financialreporting\install\bin\FRSetupPrintServer.cmd
If you had installed the Studio and Print Server under Middleware instead of the default location (as shown above), uninstall these components then re-install them to the default folder.
Is Smartview Compaitble With Office 2010
Is Smartview Compaitble With Office 2010 [ID 1270741.1]
Modified 06-DEC-2010 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.0.00 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Goal
Does Smartview 9.3.1 or Smartview 11.1.2 work with Office 2010?
Solution
Office 2010 is not supported in 11.1.2 or 9.3.1.
The versions of EPM system that support Office 2010 are 9.3.3 and 11.1.2.1, 9.3.3 is out now, however 11.1.2.1 will not be released until next year.
Modified 06-DEC-2010 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.0.00 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Goal
Does Smartview 9.3.1 or Smartview 11.1.2 work with Office 2010?
Solution
Office 2010 is not supported in 11.1.2 or 9.3.1.
The versions of EPM system that support Office 2010 are 9.3.3 and 11.1.2.1, 9.3.3 is out now, however 11.1.2.1 will not be released until next year.
Where are Application Install Inventories Stored in Oracle EPM 11.1.2.1
Where are Application Install Inventories Stored in Oracle EPM 11.1.2.1 [ID 1304532.1]
Modified 20-APR-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Hyperion Essbase - Version: 11.1.2.0.00 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Hyperion Planning - Version: 11.1.2.0.00 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Information in this document applies to any platform.
Goal
Identify the location of software inventories associated with Oracle EPM 11.1.2.1.
Solution
It is important to know where installation inventory lists are stored: to detect the completeness of an install, to determine whether a patch has been applied, or to delete as part of a reinstall.
\Oracle\Middleware\EPMSystem11R1\oraInst.loc points to the location of the central inventory. oraInst.loc may have been installed in a previous Oracle install on Unix in: /var/opt/oracle or /etc or $HOME (of the user installing Oracle software), preventing the 'reinstall' of OHS or other software.
\Program Files\Oracle\Inventory is typically the location of the central inventory (despite the name 'central inventory', there may exist mutually exclusive inventories generated with the install of other Oracle products). On Unix/Linux the central inventory is in the installer's 'home' directory.
A local inventory is typically found in \Oracle\Middleware\EPMSystem11R1\.oracle.products
A local pointer (.oracle.instances) to the instance(s) set by EPM 11.1.2.0 and EPM 11.1.2.1 (and referenced by EPM 11.1.2.1 Installer for 'Apply Maintenance Release' option) is put in C:\Users\\ Ensure the same user installs both versions.
\Oracle\Middleware\EPMSystem11R1\.oracle.products is used to recreate an inventory if need be (but a regeneration of an inventory will exclude service fixes/patches installed via OPatch. To recreate an inventory after one is corrupted...run \Oracle\Middleware\EPMSystem11R1\OPatch\createInventory.bat.)
\Oracle\Middleware\ohs\.patch_storage (holds records of previous OPatches)
Modified 20-APR-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Hyperion Essbase - Version: 11.1.2.0.00 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Hyperion Planning - Version: 11.1.2.0.00 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Information in this document applies to any platform.
Goal
Identify the location of software inventories associated with Oracle EPM 11.1.2.1.
Solution
It is important to know where installation inventory lists are stored: to detect the completeness of an install, to determine whether a patch has been applied, or to delete as part of a reinstall.
\Oracle\Middleware\EPMSystem11R1\oraInst.loc points to the location of the central inventory. oraInst.loc may have been installed in a previous Oracle install on Unix in: /var/opt/oracle or /etc or $HOME (of the user installing Oracle software), preventing the 'reinstall' of OHS or other software.
\Program Files\Oracle\Inventory is typically the location of the central inventory (despite the name 'central inventory', there may exist mutually exclusive inventories generated with the install of other Oracle products). On Unix/Linux the central inventory is in the installer's 'home' directory.
A local inventory is typically found in \Oracle\Middleware\EPMSystem11R1\.oracle.products
A local pointer (.oracle.instances) to the instance(s) set by EPM 11.1.2.0 and EPM 11.1.2.1 (and referenced by EPM 11.1.2.1 Installer for 'Apply Maintenance Release' option) is put in C:\Users\
\Oracle\Middleware\EPMSystem11R1\.oracle.products is used to recreate an inventory if need be (but a regeneration of an inventory will exclude service fixes/patches installed via OPatch. To recreate an inventory after one is corrupted...run \Oracle\Middleware\EPMSystem11R1\OPatch\createInventory.bat.)
\Oracle\Middleware\ohs\.patch_storage (holds records of previous OPatches)
MDX Query Fails with Unexpected Error 1042017 in 11.1.2.1
MDX Query Fails with Unexpected Error 1042017 in 11.1.2.1 [ID 1320230.1]
Modified 16-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
References
Applies to:
Hyperion Essbase Administration Services - Version: 11.1.2.1.000 to 11.1.2.1.000 - Release: 11.1 to 11.1
Information in this document applies to any platform.
Symptoms
An MDX query that previously worked in version 9.3.3 and 11.1.2 no longer works in 11.1.2.1. When the query is executed a network error appears.
Steps to reproduce:
1. Create an ASO application named CBR and a database named CBR. Save CBR.otl to database.
2. Load export_F_CBR.txt to database.
3. Run the MDX query from EAS console:
select
{ [Measures].[Material COGS CP2],
[Measures].[Material COGS CP1]
} on columns
from [CBR.CBR]
where ( [Cost_Period1].[Qtr-8], [Cost_Period2].[Qtr_7],
[Currency].[CUR-RPT]);
Unexpected error 1042017 appears as the result of the query.
Cause
The cause of this problem has been identified in unpublished Bug 12418533 - MDX QUERY WORKED IN 11.1.2 NO LONGER WORKS IN 11.1.2.1
The issue is caused by the MDX function on measures member "Material COGS CP2". The MDX formula is a LEAD function and when removed, the query returns with no error. A lot of members in measures use the LEAD function and none can be queried against in 11.1.2.1.
Solution
A workaround for this issue is to add the following parameter in the essbase.cfg file and stop and start Essbase.
FORMULAOPTLEVEL 2
This defect will be addressed in a future release.
Modified 16-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
References
Applies to:
Hyperion Essbase Administration Services - Version: 11.1.2.1.000 to 11.1.2.1.000 - Release: 11.1 to 11.1
Information in this document applies to any platform.
Symptoms
An MDX query that previously worked in version 9.3.3 and 11.1.2 no longer works in 11.1.2.1. When the query is executed a network error appears.
Steps to reproduce:
1. Create an ASO application named CBR and a database named CBR. Save CBR.otl to database.
2. Load export_F_CBR.txt to database.
3. Run the MDX query from EAS console:
select
{ [Measures].[Material COGS CP2],
[Measures].[Material COGS CP1]
} on columns
from [CBR.CBR]
where ( [Cost_Period1].[Qtr-8], [Cost_Period2].[Qtr_7],
[Currency].[CUR-RPT]);
Unexpected error 1042017 appears as the result of the query.
Cause
The cause of this problem has been identified in unpublished Bug 12418533 - MDX QUERY WORKED IN 11.1.2 NO LONGER WORKS IN 11.1.2.1
The issue is caused by the MDX function on measures member "Material COGS CP2". The MDX formula is a LEAD function and when removed, the query returns with no error. A lot of members in measures use the LEAD function and none can be queried against in 11.1.2.1.
Solution
A workaround for this issue is to add the following parameter in the essbase.cfg file and stop and start Essbase.
FORMULAOPTLEVEL 2
This defect will be addressed in a future release.
The Apply Maintenance Release Option Not Available From The Epm 11.1.2.1 Install Tool
The Apply Maintenance Release Option Not Available From The Epm 11.1.2.1 Install Tool [ID 1313388.1]
Modified 15-APR-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
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.
Symptoms
After downloading all components and running the EPM 11.1.2.1 installation tool, the only option available is for a new installation. The Apply Maintenance Release is grayed out and not available.
Cause
The reason the Mainentance option was unavailable was because the installation program could not locate the .oracle.instance file. The 11.1.2.1 installation program looks for that file in the users home directory during the installation process. This file did not exist in the users home directory.
Failure to have this file in the home directory will prevent application of the maintenance release.
In this particular case the previous 11.1.2.0 installation was performed as the same user, but they had right-clicked on the install tool and selected to Run As Administrator. So in effect it was run as he user Administrator and not the user they thought. This action would cause the .oracle.instance file to be put in the Administrators home directory and not the users HOME directory.
Solution
There are two solutions to this issue:
A - Re-run the install tool as the user who performed the initial installation
B - Copy the .oracle.instance file from other users directory to the HOME directory of the user doing the new installation.
Modified 15-APR-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
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.
Symptoms
After downloading all components and running the EPM 11.1.2.1 installation tool, the only option available is for a new installation. The Apply Maintenance Release is grayed out and not available.
Cause
The reason the Mainentance option was unavailable was because the installation program could not locate the .oracle.instance file. The 11.1.2.1 installation program looks for that file in the users home directory during the installation process. This file did not exist in the users home directory.
Failure to have this file in the home directory will prevent application of the maintenance release.
In this particular case the previous 11.1.2.0 installation was performed as the same user, but they had right-clicked on the install tool and selected to Run As Administrator. So in effect it was run as he user Administrator and not the user they thought. This action would cause the .oracle.instance file to be put in the Administrators home directory and not the users HOME directory.
Solution
There are two solutions to this issue:
A - Re-run the install tool as the user who performed the initial installation
B - Copy the .oracle.instance file from other users directory to the HOME directory of the user doing the new installation.
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.
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\
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.
Unable to Create FDM Application or Configure Shared Services Provider on Windows 2008 R2
Unable to Create FDM Application or Configure Shared Services Provider on Windows 2008 R2 [ID 1324303.1]
Modified 24-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
References
Applies to:
Hyperion Financial Data Quality Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Microsoft Windows x64 (64-bit) - Version: 2008 R2
Symptoms
When attempting to connect to shared services with the CSS provider in the authentication providers tab of the Load Balance Configuration, the connection process fails and returns "Active-X Component Can't Create Object".
This is occurring with version 11.1.2.1 on a Windows 2008 R2 server.
Cause
Currently the EPM System Installer does not properly register a necessary file for FDM to use to connect to shared services successfully. When attempting to connect to HSS from the Load Balance Configuration the process fails and results in the error message.
The cause of the issue is justified by Unpublished Bug 12540570.
Solution
A) Launch the EPM System Installer on the FDM server
B) Click Next at the welcome screen
C) Verify the EPM System Home and click next
D) Choose the "Re-Install This Release" option and the "Choose Components Individually" radio button and click Next
E) Un-check All items and then check the FDM component box and click next
F) Verify the FDM Components to be re-installed and click Next
G) Start > Programs > Oracle EPM System > Financial Data Quality Management > Application Server > Application Server Config
H) Enter the FDM Service account username/password/confirm password/domain and click OK
I) Start > Programs > Oracle EPM System > Financial Data Quality Management > Load Balance Server > Load Balance Configuration
J) Enter the FDM Service Account username/password/confirm password/domain. Click on the application servers tab and add the FDM Application Server Name. Click on the Authentication Providers Tab and add a new Provider. Choose "CSS" for the type and click OK. Enter a description for the provider and the HSS Admin/password account and click "test connection". Receive message "Connection Successful" click OK and ok again to return the the load balance config and OK to save the changes.
K) Start > Programs > Oracle EPM System > Financial Data Quality Management > Task Manager > Task Manager Configuration. Enter the FDM Service Account uid/pwd/confirm pwd/domain. Click on the load balance server tab and populate the FDM application server name in the primary server field and click OK
L) Start > Programs > Oracle EPM System > Financial Data Quality Management > Web Server Components > Web Configuration. Enter the FDM Service Account uid/pwd/confirm pwd/domain. Click on the load balance server tab and populate the FDM application server name in the primary server field and click OK.
M) Click OK to the IIS Restart message and open a command prompt. Type iisreset and hit the enter key.
References
Modified 24-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
References
Applies to:
Hyperion Financial Data Quality Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Microsoft Windows x64 (64-bit) - Version: 2008 R2
Symptoms
When attempting to connect to shared services with the CSS provider in the authentication providers tab of the Load Balance Configuration, the connection process fails and returns "Active-X Component Can't Create Object".
This is occurring with version 11.1.2.1 on a Windows 2008 R2 server.
Cause
Currently the EPM System Installer does not properly register a necessary file for FDM to use to connect to shared services successfully. When attempting to connect to HSS from the Load Balance Configuration the process fails and results in the error message.
The cause of the issue is justified by Unpublished Bug 12540570.
Solution
A) Launch the EPM System Installer on the FDM server
B) Click Next at the welcome screen
C) Verify the EPM System Home and click next
D) Choose the "Re-Install This Release" option and the "Choose Components Individually" radio button and click Next
E) Un-check All items and then check the FDM component box and click next
F) Verify the FDM Components to be re-installed and click Next
G) Start > Programs > Oracle EPM System > Financial Data Quality Management > Application Server > Application Server Config
H) Enter the FDM Service account username/password/confirm password/domain and click OK
I) Start > Programs > Oracle EPM System > Financial Data Quality Management > Load Balance Server > Load Balance Configuration
J) Enter the FDM Service Account username/password/confirm password/domain. Click on the application servers tab and add the FDM Application Server Name. Click on the Authentication Providers Tab and add a new Provider. Choose "CSS" for the type and click OK. Enter a description for the provider and the HSS Admin/password account and click "test connection". Receive message "Connection Successful" click OK and ok again to return the the load balance config and OK to save the changes.
K) Start > Programs > Oracle EPM System > Financial Data Quality Management > Task Manager > Task Manager Configuration. Enter the FDM Service Account uid/pwd/confirm pwd/domain. Click on the load balance server tab and populate the FDM application server name in the primary server field and click OK
L) Start > Programs > Oracle EPM System > Financial Data Quality Management > Web Server Components > Web Configuration. Enter the FDM Service Account uid/pwd/confirm pwd/domain. Click on the load balance server tab and populate the FDM application server name in the primary server field and click OK.
M) Click OK to the IIS Restart message and open a command prompt. Type iisreset and hit the enter key.
References
Unable to Access Disclosure Management Client in Smart View 11.1.2.1. Extensions Grayed out in both Excel and Word
Unable to Access Disclosure Management Client in Smart View 11.1.2.1. Extensions Grayed out in both Excel and Word [ID 1318876.1]
Modified 30-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
Applies to:
Hyperion Disclosure Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Symptoms
Installed 11.1.2.1 Disclosure Management on client workstation running Windows 7.
Office 2010
.NET Framework 3.5
Successfully installed Smart View and can create a Shared Connection Provider to Essbase
Extensions grayed out in both Excel and Word.
When going to Options and trying to enable Extensions receive the following error:
Microsoft .NET Framework
Unhandled exception has occurred in a component in your application. If you click continue the application will ignore this error and attempt to continue.
Creating an instance of the COM component with CLSID {74E3234C-9262F-4998-939D75DD25B8} from the |ClassFactory failed due to the following error: 80040110
DETAILS gives:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80040110): Creating an instance of the COM component with CLSID {74E3234C-962F-4498-9B14-939D75DD25B8} from the IClassFactory failed due to the following error: 80040110.
at B8CEB14D_B26A_48bf_80BC_18D4B75F6D5F.SVExtActivator.TraceMessage(String message, TraceLevel level)
at B8CEB14D_B26A_48bf_80BC_18D4B75F6D5F.SVExtActivator.TraceError(String message)
at B8CEB14D_B26A_48bf_80BC_18D4B75F6D5F.SVExtActivator.StartExtension(SVExtensionInfo ext)
at B8CEB14D_B26A_48bf_80BC_18D4B75F6D5F.SVExtActivator.EnableExtension(Boolean fEnabled, String strRegistryID)
at B8CEB14D_B26A_48bf_80BC_18D4B75F6D5F.UsrCtlExtDescriptor.button_Enable_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5444 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
BIPlusConnector
Assembly Version: 11.1.2.0
Win32 Version: 11.1.2.0
CodeBase: file:///C:/Oracle/SmartView/Bin/BIPlusConnector.DLL
----------------------------------------
Oracle.SmartView.Interop.SVRC
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Oracle/SmartView/Bin/Oracle.SmartView.Interop.SVRC.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Oracle.DisclosureManagement.SmartViewExtension
Assembly Version: 11.1002.1000.82
Win32 Version: 11.1002.1000.82
CodeBase: file:///C:/Program%20Files/Oracle%20Hyperion%20Disclosure%20Management/Oracle.DisclosureManagement.SmartViewExtension.dll
----------------------------------------
Oracle.DisclosureManagement.Core
Assembly Version: 11.1002.1000.82
Win32 Version: 11.1002.1000.82
CodeBase: file:///C:/Program%20Files/Oracle%20Hyperion%20Disclosure%20Management/Oracle.DisclosureManagement.Core.DLL
----------------------------------------
Oracle.DisclosureManagement.Interfaces
Assembly Version: 11.1002.1000.82
Win32 Version: 11.1002.1000.82
CodeBase: file:///C:/Program%20Files/Oracle%20Hyperion%20Disclosure%20Management/Oracle.DisclosureManagement.Interfaces.DLL
----------------------------------------
Microsoft.Office.Interop.Word
Assembly Version: 14.0.0.0
Win32 Version: 14.0.4762.1000
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.Office.Interop.Word/14.0.0.0__71e9bce111e9429c/Microsoft.Office.Interop.Word.dll
----------------------------------------
Microsoft.Office.Interop.Excel
Assembly Version: 14.0.0.0
Win32 Version: 14.0.4756.1000
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.Office.Interop.Excel/14.0.0.0__71e9bce111e9429c/Microsoft.Office.Interop.Excel.dll
----------------------------------------
Oracle.DisclosureManagement.Common.UI
Assembly Version: 11.1002.1000.82
Win32 Version: 11.1002.1000.82
CodeBase: file:///C:/Program%20Files/Oracle%20Hyperion%20Disclosure%20Management/Oracle.DisclosureManagement.Common.UI.DLL
----------------------------------------
office
Assembly Version: 14.0.0.0
Win32 Version: 14.0.4760.1000
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/office/14.0.0.0__71e9bce111e9429c/office.dll
----------------------------------------
stdole
Assembly Version: 7.0.3300.0
Win32 Version: 7.00.9466
CodeBase: file:///C:/Windows/assembly/GAC/stdole/7.0.3300.0__b03f5f7f11d50a3a/stdole.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Cause
The cause of this issue has to do with how the installation was handled.
Solution
Take the following steps to resolve.
1. Install the correct version of .NET 2.0 or 3.5
2. On the client machine uninstall both Smart View client and Disclosure Management client via Add/Remove Programs.
3. Go to START -> RUN and type regedit to open the registry. Backup the registry, then delete any keys located under HKEY_CURRENT_USER -> SOFTWARE -> HYPERION SOLUTIONS and HKEY_LOCAL_MACHINE -> SOFTWARE -> ORACLE.
4. Install Smart View client
5. Install Disclosure Management client
6. Then created connection providers in Smart View
7. In Smart View -> Options -> Extensions check that Disclosure Management is listed and enabled.
8. On Disclosure Management tab connect and login
Modified 30-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
Applies to:
Hyperion Disclosure Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Symptoms
Installed 11.1.2.1 Disclosure Management on client workstation running Windows 7.
Office 2010
.NET Framework 3.5
Successfully installed Smart View and can create a Shared Connection Provider to Essbase
Extensions grayed out in both Excel and Word.
When going to Options and trying to enable Extensions receive the following error:
Microsoft .NET Framework
Unhandled exception has occurred in a component in your application. If you click continue the application will ignore this error and attempt to continue.
Creating an instance of the COM component with CLSID {74E3234C-9262F-4998-939D75DD25B8} from the |ClassFactory failed due to the following error: 80040110
DETAILS gives:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80040110): Creating an instance of the COM component with CLSID {74E3234C-962F-4498-9B14-939D75DD25B8} from the IClassFactory failed due to the following error: 80040110.
at B8CEB14D_B26A_48bf_80BC_18D4B75F6D5F.SVExtActivator.TraceMessage(String message, TraceLevel level)
at B8CEB14D_B26A_48bf_80BC_18D4B75F6D5F.SVExtActivator.TraceError(String message)
at B8CEB14D_B26A_48bf_80BC_18D4B75F6D5F.SVExtActivator.StartExtension(SVExtensionInfo ext)
at B8CEB14D_B26A_48bf_80BC_18D4B75F6D5F.SVExtActivator.EnableExtension(Boolean fEnabled, String strRegistryID)
at B8CEB14D_B26A_48bf_80BC_18D4B75F6D5F.UsrCtlExtDescriptor.button_Enable_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5444 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
BIPlusConnector
Assembly Version: 11.1.2.0
Win32 Version: 11.1.2.0
CodeBase: file:///C:/Oracle/SmartView/Bin/BIPlusConnector.DLL
----------------------------------------
Oracle.SmartView.Interop.SVRC
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Oracle/SmartView/Bin/Oracle.SmartView.Interop.SVRC.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Oracle.DisclosureManagement.SmartViewExtension
Assembly Version: 11.1002.1000.82
Win32 Version: 11.1002.1000.82
CodeBase: file:///C:/Program%20Files/Oracle%20Hyperion%20Disclosure%20Management/Oracle.DisclosureManagement.SmartViewExtension.dll
----------------------------------------
Oracle.DisclosureManagement.Core
Assembly Version: 11.1002.1000.82
Win32 Version: 11.1002.1000.82
CodeBase: file:///C:/Program%20Files/Oracle%20Hyperion%20Disclosure%20Management/Oracle.DisclosureManagement.Core.DLL
----------------------------------------
Oracle.DisclosureManagement.Interfaces
Assembly Version: 11.1002.1000.82
Win32 Version: 11.1002.1000.82
CodeBase: file:///C:/Program%20Files/Oracle%20Hyperion%20Disclosure%20Management/Oracle.DisclosureManagement.Interfaces.DLL
----------------------------------------
Microsoft.Office.Interop.Word
Assembly Version: 14.0.0.0
Win32 Version: 14.0.4762.1000
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.Office.Interop.Word/14.0.0.0__71e9bce111e9429c/Microsoft.Office.Interop.Word.dll
----------------------------------------
Microsoft.Office.Interop.Excel
Assembly Version: 14.0.0.0
Win32 Version: 14.0.4756.1000
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.Office.Interop.Excel/14.0.0.0__71e9bce111e9429c/Microsoft.Office.Interop.Excel.dll
----------------------------------------
Oracle.DisclosureManagement.Common.UI
Assembly Version: 11.1002.1000.82
Win32 Version: 11.1002.1000.82
CodeBase: file:///C:/Program%20Files/Oracle%20Hyperion%20Disclosure%20Management/Oracle.DisclosureManagement.Common.UI.DLL
----------------------------------------
office
Assembly Version: 14.0.0.0
Win32 Version: 14.0.4760.1000
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/office/14.0.0.0__71e9bce111e9429c/office.dll
----------------------------------------
stdole
Assembly Version: 7.0.3300.0
Win32 Version: 7.00.9466
CodeBase: file:///C:/Windows/assembly/GAC/stdole/7.0.3300.0__b03f5f7f11d50a3a/stdole.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Cause
The cause of this issue has to do with how the installation was handled.
Solution
Take the following steps to resolve.
1. Install the correct version of .NET 2.0 or 3.5
2. On the client machine uninstall both Smart View client and Disclosure Management client via Add/Remove Programs.
3. Go to START -> RUN and type regedit to open the registry. Backup the registry, then delete any keys located under HKEY_CURRENT_USER -> SOFTWARE -> HYPERION SOLUTIONS and HKEY_LOCAL_MACHINE -> SOFTWARE -> ORACLE.
4. Install Smart View client
5. Install Disclosure Management client
6. Then created connection providers in Smart View
7. In Smart View -> Options -> Extensions check that Disclosure Management is listed and enabled.
8. On Disclosure Management tab connect and login
A Unique Instance Name Is Required When Configuring A New Install Of EPM 11.1.2.1 In Distributed Environment
A Unique Instance Name Is Required When Configuring A New Install Of EPM 11.1.2.1 In Distributed Environment [ID 1317679.1]
Modified 10-MAY-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Financial Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Planning - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Profitability - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Information in this document applies to any platform.
Goal
To install and configure Oracle EPM 11.1.2.1 in a distributed environment with a proper Instance name on each server
Solution
When configuring EPM 11.1.2.1 in a distributed environment, it is necessary to supply a new, unique Instance name on each server.
For example.
If using the default Instance name 'epmsystem1' on the first server, if you keep the same naming convention on subsequent servers, you will need to supply new, unique Instance names such as epmsystem2, epmsystem3, etc.
During Configuration each instance gets written to the EPM System Registry and the EPM System Configurator verifies that each instance name is unique. If you fail to provide a new unique instance name during the configuration process you will receive a message stating that the instance name is not valid. You will be forced to go back and enter a unique instance name.
Note: If you are applying the maintenance release (11.1.2 to 11.1.2.1), during the configuration process you select the first option "Modify existing instance" since the epmsystem1 instance name already exists and is shared by all servers in the distributed environment. Be sure not to delete or change the instance names during a maintenance release configuration as it will cause the configuration to change from a maintenance install to a new installation and will cause issues with the rest of the server deployments in the distributed environment.
Modified 10-MAY-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Financial Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Planning - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Profitability - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Information in this document applies to any platform.
Goal
To install and configure Oracle EPM 11.1.2.1 in a distributed environment with a proper Instance name on each server
Solution
When configuring EPM 11.1.2.1 in a distributed environment, it is necessary to supply a new, unique Instance name on each server.
For example.
If using the default Instance name 'epmsystem1' on the first server, if you keep the same naming convention on subsequent servers, you will need to supply new, unique Instance names such as epmsystem2, epmsystem3, etc.
During Configuration each instance gets written to the EPM System Registry and the EPM System Configurator verifies that each instance name is unique. If you fail to provide a new unique instance name during the configuration process you will receive a message stating that the instance name is not valid. You will be forced to go back and enter a unique instance name.
Note: If you are applying the maintenance release (11.1.2 to 11.1.2.1), during the configuration process you select the first option "Modify existing instance" since the epmsystem1 instance name already exists and is shared by all servers in the distributed environment. Be sure not to delete or change the instance names during a maintenance release configuration as it will cause the configuration to change from a maintenance install to a new installation and will cause issues with the rest of the server deployments in the distributed environment.
Unable To Configure Essbase 11.1.2.1. The Configuration Utility Hangs at 0%
Unable To Configure Essbase 11.1.2.1. The Configuration Utility Hangs at 0% [ID 1316420.1]
Modified 26-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
References
Applies to:
Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Symptoms
Following a brand new distributed installation of version 11.1.2.1, when configuring Essbase, the Configuration Utility hangs at the last screen on 0% and does not go any further.
Cause
The wrong host name for the server was entered during the configuration.
Solution
1. Check the configtool.log for errors, such as:
"java.net.UnknownHostException: servername.servername.com"
2. Also, run the epmsys_registry.bat or epmsys_registry.sh and check the registry.html report.
3. Make sure that the servername that is listed is resolvable to the correct IP address, and that the correct servername is being used.
4. Try adding the HOST entry on the machine to resolve the servername.servername.com to the other machine and/or or fix the host entry in the registry using the registry utility.
Please contact Oracle technical support to assist with modifying the registry.
Modified 26-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
References
Applies to:
Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Symptoms
Following a brand new distributed installation of version 11.1.2.1, when configuring Essbase, the Configuration Utility hangs at the last screen on 0% and does not go any further.
Cause
The wrong host name for the server was entered during the configuration.
Solution
1. Check the configtool.log for errors, such as:
"java.net.UnknownHostException: servername.servername.com"
2. Also, run the epmsys_registry.bat or epmsys_registry.sh and check the registry.html report.
3. Make sure that the servername that is listed is resolvable to the correct IP address, and that the correct servername is being used.
4. Try adding the HOST entry on the machine to resolve the servername.servername.com to the other machine and/or or fix the host entry in the registry using the registry utility.
Please contact Oracle technical support to assist with modifying the registry.
Utilities for Troubleshooting Oracle Hyperion Enterprise Performance Management 11.1.2.1
Utilities for Troubleshooting Oracle Hyperion Enterprise Performance Management 11.1.2.1 [ID 1303200.1]
Modified 20-APR-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
References
Applies to:
Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
(1) \Oracle\Middleware\user_projects\epmsystem1\bin\ziplogs.bat|.sh
(2) \Oracle\Middleware\ohs\ccr\bin\
(3) \Oracle\Middleware\ohs\rda\rda.cmd
(4) \Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat|.sh
(5) \Oracle\Middleware\user_projects\epmsystem1\bin\validate.bat
Goal
This article aims to help users use various troubleshooting tools to validate or troubleshoot an installation of Oracle EPM 11.1.2.1.
Solution
(1) A new troubleshooting tool introduced in Oracle EPM 11.1.2.1 is \Oracle\Middleware\user_projects\epmsystem1\bin\ziplogs.bat|.sh file. The output of this is generated in \Oracle\Middleware\user_projects\epmsystem1\diagnostics\ziplogs\EPM_logs__11.1.2.1.0.zip
(2) Oracle Configuration Manager (OCM) is an advanced tool which collects and evaluates settings from configuration files (but not Hyperion Registry) and stores them in a central database administered by Oracle. It was first introduced in EPM 11.1.2.0
(3) Remote Desktop Assistant (RDA) collects and zips up a large amount of information concerning the software and hardware environments of Oracle products. If Perl 5.1 or later is installed on the computer and accessible from the command line (test: perl -version), then run: \Oracle\Middleware\ohs\rda\rda.cmd from the command line to access the RDA tool. Alternately, precompiled RDA executables are available for several platforms.
(4) Configuration settings have been moved from configuration files to a database repository associated with Shared Services. These may be extracted to an HTML formatted file by running \Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat|.sh without parameters from the command line. The output is generated to file \Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\registry.html The username/login/jdbc URL for the Hyperion/HSS registry are kept in \Oracle\Middleware\user_projects\epmsystem1\config\foundation\11.1.2.0\reg.properties file.
(5) A much enhanced validation tool is available in \Oracle\Middleware\user_projects\epmsystem1\bin\validate.bat. In EPM 11.1.2.1 the output files are of the form \Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\instance_report_20YYMMDD_######.html (where YY is the year, MM is the month, DD is the day, and ###### is a unique integer). It also runs the tool under (1) and gives the output of that tool.
(6) Individual log files may be found in subdirectories under:
\Oracle\Middleware\user_projects\domains\EPMSystem\servers\\logs
\Oracle\Middleware\EPMSystem11R1\diagnostics\logs
\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\
\Program Files\Oracle\Inventory\logs
C:\Users\\Oracle\oradiag_\diag\
C:\Users\\.oracle\logs\
(7) Some debug tools (*) can be activated if under http://:19000/workspace/index.jsp > Navigate > Administration > Workspace Server Settings > Client Debug Enabled: is set to Yes (then click 'OK' button, close all browser windows, and restart browser).
* http://hostname:19000/workspace/debug/configInfo.jsp
* http://hostname:19000/workspace/debug/userInfo.jsp
* http://hostname:19000/workspace/debug/userGroupQuery.jsp
Other tools are available at these URLs (largely derived from validate.bat output). A non-Error response indicates that the web service of each particular application is active.:
http://hostname:19000/workspace/status
http://hostname:19000/workspace/BPMContext
http://hostname:8600/mappingtool/faces/info.jspx
http://hostname:10080/easconsole/console.html
http://hostname:16000/WebAnalysis
http://hostname:6373/oracle-epm-fm-webservices/ApplicationService
http://hostname:8300/HyperionPlanning/
http://hostname:13080/aps/APS
http://hostname:8200/hr/status.jsp
http://hostname:19091/awb/conf/AwbConfig.xml
http://hostname:8500/calcmgr/index.htm
Modified 20-APR-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
References
Applies to:
Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
(1) \Oracle\Middleware\user_projects\epmsystem1\bin\ziplogs.bat|.sh
(2) \Oracle\Middleware\ohs\ccr\bin\
(3) \Oracle\Middleware\ohs\rda\rda.cmd
(4) \Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat|.sh
(5) \Oracle\Middleware\user_projects\epmsystem1\bin\validate.bat
Goal
This article aims to help users use various troubleshooting tools to validate or troubleshoot an installation of Oracle EPM 11.1.2.1.
Solution
(1) A new troubleshooting tool introduced in Oracle EPM 11.1.2.1 is \Oracle\Middleware\user_projects\epmsystem1\bin\ziplogs.bat|.sh file. The output of this is generated in \Oracle\Middleware\user_projects\epmsystem1\diagnostics\ziplogs\EPM_logs_
(2) Oracle Configuration Manager (OCM) is an advanced tool which collects and evaluates settings from configuration files (but not Hyperion Registry) and stores them in a central database administered by Oracle. It was first introduced in EPM 11.1.2.0
(3) Remote Desktop Assistant (RDA) collects and zips up a large amount of information concerning the software and hardware environments of Oracle products. If Perl 5.1 or later is installed on the computer and accessible from the command line (test: perl -version), then run: \Oracle\Middleware\ohs\rda\rda.cmd from the command line to access the RDA tool. Alternately, precompiled RDA executables are available for several platforms.
(4) Configuration settings have been moved from configuration files to a database repository associated with Shared Services. These may be extracted to an HTML formatted file by running \Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat|.sh without parameters from the command line. The output is generated to file \Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\registry.html The username/login/jdbc URL for the Hyperion/HSS registry are kept in \Oracle\Middleware\user_projects\epmsystem1\config\foundation\11.1.2.0\reg.properties file.
(5) A much enhanced validation tool is available in \Oracle\Middleware\user_projects\epmsystem1\bin\validate.bat. In EPM 11.1.2.1 the output files are of the form \Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\instance_report_20YYMMDD_######.html (where YY is the year, MM is the month, DD is the day, and ###### is a unique integer). It also runs the tool under (1) and gives the output of that tool.
(6) Individual log files may be found in subdirectories under:
\Oracle\Middleware\user_projects\domains\EPMSystem\servers\
\Oracle\Middleware\EPMSystem11R1\diagnostics\logs
\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\
\Program Files\Oracle\Inventory\logs
C:\Users\
C:\Users\
(7) Some debug tools (*) can be activated if under http://
* http://hostname:19000/workspace/debug/configInfo.jsp
* http://hostname:19000/workspace/debug/userInfo.jsp
* http://hostname:19000/workspace/debug/userGroupQuery.jsp
Other tools are available at these URLs (largely derived from validate.bat output). A non-Error response indicates that the web service of each particular application is active.:
http://hostname:19000/workspace/status
http://hostname:19000/workspace/BPMContext
http://hostname:8600/mappingtool/faces/info.jspx
http://hostname:10080/easconsole/console.html
http://hostname:16000/WebAnalysis
http://hostname:6373/oracle-epm-fm-webservices/ApplicationService
http://hostname:8300/HyperionPlanning/
http://hostname:13080/aps/APS
http://hostname:8200/hr/status.jsp
http://hostname:19091/awb/conf/AwbConfig.xml
http://hostname:8500/calcmgr/index.htm
Unable to Start Tasks with New Install of FCM 11.1.2.1
Unable to Start Tasks with New Install of FCM 11.1.2.1 [ID 1315380.1]
Modified 02-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Changes
Cause
Solution
Applies to:
Hyperion Financial Close Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Symptoms
After bringing up all the Hyperion Services and setting the schedule to 'open' within FCM, none of the assigned Tasks will start. Error thrown in the soa_server*-diagnostic.log, see below.
Changes
The Keystore Step was either missed or skipped. See 'Configuring the Keystore for Oracle Web Services Manager' in the EPM Install guide http://download.oracle.com/docs/cd/E17236_01/epm.1112/epm_install_11121.pdf .
Cause
The issue is caused by the following setup: The keystore was not configured correctly. The following error identifies the issue:
[2011-04-17T03:55:02.416-04:00] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.ws] [tid: orabpel.invoke.pool-4.thread-15] [userId: fcmdemo] [ecid: 0000IxWGuip5yWc5Tjl3ic1DeGqd0001DQ,0:1:100004215] [APP: soa-infra] [composite_name: FCCNotificationComposite] [component_name: SendNotification] [component_instance_id: 2079] got FabricInvocationException[[
java.security.UnrecoverableKeyException: Password verification failed
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:769)
at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)
at java.security.KeyStore.load(KeyStore.java:1185)
at oracle.wsm.security.jps.WsmLegacyKeyStore.(WsmLegacyKeyStore.java:266)
at oracle.wsm.security.jps.WsmKeyStoreFactory.getKeyStore(WsmKeyStoreFactory.java:60)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor.updateWsmKeyStore(SecurityScenarioExecutor.java:1216)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor.initialize(SecurityScenarioExecutor.java:455)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor.init(SecurityScenarioExecutor.java:305)
at oracle.wsm.security.policy.scenario.executor.Wss11SamlWithCertsScenarioExecutor.init(Wss11SamlWithCertsScenarioExecutor.java:72)
at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.populateAssertionExecutors(WSPolicyRuntimeExecutor.java:256)
at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.populateAssertionExecutors(WSPolicyRuntimeExecutor.java:279)
at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.init(WSPolicyRuntimeExecutor.java:162)
at oracle.wsm.policyengine.impl.PolicyExecutionEngine.getPolicyExecutor(PolicyExecutionEngine.java:137)
at oracle.wsm.policyengine.impl.PolicyExecutionEngine.execute(PolicyExecutionEngine.java:101)
at oracle.wsm.agent.WSMAgent.processCommon(WSMAgent.java:937)
at oracle.wsm.agent.WSMAgent.processRequest(WSMAgent.java:454)
at oracle.fabric.common.BindingSecurityInterceptor.processRequest(BindingSecurityInterceptor.java:94)
at oracle.integration.platform.common.InterceptorChainImpl$1.run(InterceptorChainImpl.java:187)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.integration.platform.common.InterceptorChainImpl.processRequestAsSubject(InterceptorChainImpl.java:185)
at oracle.integration.platform.common.InterceptorChainImpl.processRequest(InterceptorChainImpl.java:102)
at oracle.integration.platform.common.mgmt.InterceptorChainManager.processRequest(InterceptorChainManager.java:235)
at oracle.j2ee.ws.client.mgmt.runtime.SuperClientInterceptorPipeline.handleRequest(SuperClientInterceptorPipeline.java:96)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.handleRequest(DispatchImpl.java:615)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.handleRequest(DispatchImpl.java:593)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:789)
at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235)
at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106)
at oracle.integration.platform.blocks.soap.AbstractWebServiceBindingComponent.dispatchRequest(AbstractWebServiceBindingComponent.java:517)
at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.processOutboundMessage(WebServiceExternalBindingComponent.java:207)
at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.sendSOAPMessage(WebServiceExternalBindingComponent.java:826)
at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.request(WebServiceExternalBindingComponent.java:603)
at oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest(SynchronousMessageHandler.java:139)
at oracle.integration.platform.blocks.mesh.MessageRouter.request(MessageRouter.java:179)
at oracle.integration.platform.blocks.mesh.MeshImpl$2.run(MeshImpl.java:178)
at javax.security.auth.Subject.doAs(Subject.java:396)
at oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject(MeshImpl.java:176)
at oracle.integration.platform.blocks.mesh.MeshImpl.request(MeshImpl.java:152)
at sun.reflect.GeneratedMethodAccessor885.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy295.request(Unknown Source)
Solution
1) Navigate to /Oracle/Middleware/user_projects/$DOMAIN_HOME/config/fmwconfig
2) Delete or rename the default-keystore.jks file
3) Rerun the command:
keytool -genkeypair -keyalg RSA -alias orakey -keypass welcome1 -keystore defaultkeystore.jks -storepass welcome1 -validity 3600
4) Reboot SOA.
Please change the alias/password as needed to fit your environment. Keep in mind if you have already gone through the steps in Enterprise Manager for setting the Keystore Management, your ID and Password must match what you entered into the key file. If it doesn't you will continue to get failed password error messages. See 'Assign the Keystore to the EPM System WebLogic domain' in the EPM Install guide for more details.
Modified 02-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Changes
Cause
Solution
Applies to:
Hyperion Financial Close Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Symptoms
After bringing up all the Hyperion Services and setting the schedule to 'open' within FCM, none of the assigned Tasks will start. Error thrown in the soa_server*-diagnostic.log, see below.
Changes
The Keystore Step was either missed or skipped. See 'Configuring the Keystore for Oracle Web Services Manager' in the EPM Install guide http://download.oracle.com/docs/cd/E17236_01/epm.1112/epm_install_11121.pdf .
Cause
The issue is caused by the following setup: The keystore was not configured correctly. The following error identifies the issue:
[2011-04-17T03:55:02.416-04:00] [soa_server1] [ERROR] [] [oracle.soa.bpel.engine.ws] [tid: orabpel.invoke.pool-4.thread-15] [userId: fcmdemo] [ecid: 0000IxWGuip5yWc5Tjl3ic1DeGqd0001DQ,0:1:100004215] [APP: soa-infra] [composite_name: FCCNotificationComposite] [component_name: SendNotification] [component_instance_id: 2079] got FabricInvocationException[[
java.security.UnrecoverableKeyException: Password verification failed
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:769)
at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)
at java.security.KeyStore.load(KeyStore.java:1185)
at oracle.wsm.security.jps.WsmLegacyKeyStore.
at oracle.wsm.security.jps.WsmKeyStoreFactory.getKeyStore(WsmKeyStoreFactory.java:60)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor.updateWsmKeyStore(SecurityScenarioExecutor.java:1216)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor.initialize(SecurityScenarioExecutor.java:455)
at oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor.init(SecurityScenarioExecutor.java:305)
at oracle.wsm.security.policy.scenario.executor.Wss11SamlWithCertsScenarioExecutor.init(Wss11SamlWithCertsScenarioExecutor.java:72)
at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.populateAssertionExecutors(WSPolicyRuntimeExecutor.java:256)
at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.populateAssertionExecutors(WSPolicyRuntimeExecutor.java:279)
at oracle.wsm.policyengine.impl.runtime.WSPolicyRuntimeExecutor.init(WSPolicyRuntimeExecutor.java:162)
at oracle.wsm.policyengine.impl.PolicyExecutionEngine.getPolicyExecutor(PolicyExecutionEngine.java:137)
at oracle.wsm.policyengine.impl.PolicyExecutionEngine.execute(PolicyExecutionEngine.java:101)
at oracle.wsm.agent.WSMAgent.processCommon(WSMAgent.java:937)
at oracle.wsm.agent.WSMAgent.processRequest(WSMAgent.java:454)
at oracle.fabric.common.BindingSecurityInterceptor.processRequest(BindingSecurityInterceptor.java:94)
at oracle.integration.platform.common.InterceptorChainImpl$1.run(InterceptorChainImpl.java:187)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.integration.platform.common.InterceptorChainImpl.processRequestAsSubject(InterceptorChainImpl.java:185)
at oracle.integration.platform.common.InterceptorChainImpl.processRequest(InterceptorChainImpl.java:102)
at oracle.integration.platform.common.mgmt.InterceptorChainManager.processRequest(InterceptorChainManager.java:235)
at oracle.j2ee.ws.client.mgmt.runtime.SuperClientInterceptorPipeline.handleRequest(SuperClientInterceptorPipeline.java:96)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.handleRequest(DispatchImpl.java:615)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.handleRequest(DispatchImpl.java:593)
at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:789)
at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235)
at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106)
at oracle.integration.platform.blocks.soap.AbstractWebServiceBindingComponent.dispatchRequest(AbstractWebServiceBindingComponent.java:517)
at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.processOutboundMessage(WebServiceExternalBindingComponent.java:207)
at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.sendSOAPMessage(WebServiceExternalBindingComponent.java:826)
at oracle.integration.platform.blocks.soap.WebServiceExternalBindingComponent.request(WebServiceExternalBindingComponent.java:603)
at oracle.integration.platform.blocks.mesh.SynchronousMessageHandler.doRequest(SynchronousMessageHandler.java:139)
at oracle.integration.platform.blocks.mesh.MessageRouter.request(MessageRouter.java:179)
at oracle.integration.platform.blocks.mesh.MeshImpl$2.run(MeshImpl.java:178)
at javax.security.auth.Subject.doAs(Subject.java:396)
at oracle.integration.platform.blocks.mesh.MeshImpl.doRequestAsSubject(MeshImpl.java:176)
at oracle.integration.platform.blocks.mesh.MeshImpl.request(MeshImpl.java:152)
at sun.reflect.GeneratedMethodAccessor885.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy295.request(Unknown Source)
Solution
1) Navigate to /Oracle/Middleware/user_projects/$DOMAIN_HOME/config/fmwconfig
2) Delete or rename the default-keystore.jks file
3) Rerun the command:
keytool -genkeypair -keyalg RSA -alias orakey -keypass welcome1 -keystore defaultkeystore.jks -storepass welcome1 -validity 3600
4) Reboot SOA.
Please change the alias/password as needed to fit your environment. Keep in mind if you have already gone through the steps in Enterprise Manager for setting the Keystore Management, your ID and Password must match what you entered into the key file. If it doesn't you will continue to get failed password error messages. See 'Assign the Keystore to the EPM System WebLogic domain' in the EPM Install guide for more details.
Can FDM 11.1.2.1 Be Installed On a 64 Bit Windows 2008 R2 Server?
Can FDM 11.1.2.1 Be Installed On a 64 Bit Windows 2008 R2 Server? [ID 1317465.1]
Modified 04-MAY-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion Financial Data Quality Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Goal
The EPM System Installation Guide states that FDM can be installed on a Windows Server 2008 R2 64 Operating System for 32-BIT BINARIES ONLY. Does this mean FDM can still be installed on a 64bit O/S but it will run in 32bit mode? Or is it not supported for installation on a 64bit OS?
Note:
As mentioned per the EPM 11.1.2 Matrix "oracle-hyperion-epm-system-certific-131801.xls"that:
Windows Server 2008 R2 64 bit x64 is supported.
But in Exceptions and Additional Information section, there is the following:
32-BIT BINARIES ONLY FOR: FDM, Financial Reporting Print Server, Interactive Reporting Services, and Strategic Finance.
Solution
FDM can successfully run on a 64 bit 2008 machine. FDM does not have 64 bit binaries, it is a 32 bit component. You can install FDM on 64-bit OS but it is a 32 bit application and will run in 32-bit mode.
Note: Special guidelines have to be followed for running FDM on 64 bit machine:
On a windows 2008 server you need to make sure the following is set:
- User Account Control (UAC) has been disabled within User Accounts under Administrative Tools in the Control Panel.
- The Windows Firewall should be disabled.
- The IIS6 Metabase has been installed along with the Application Server Role on the server to enable ASP.NET with IIS.
NOTE: These items are also required on a x86 Windows 2008 Server.
Modified 04-MAY-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion Financial Data Quality Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Goal
The EPM System Installation Guide states that FDM can be installed on a Windows Server 2008 R2 64 Operating System for 32-BIT BINARIES ONLY. Does this mean FDM can still be installed on a 64bit O/S but it will run in 32bit mode? Or is it not supported for installation on a 64bit OS?
Note:
As mentioned per the EPM 11.1.2 Matrix "oracle-hyperion-epm-system-certific-131801.xls"that:
Windows Server 2008 R2 64 bit x64 is supported.
But in Exceptions and Additional Information section, there is the following:
32-BIT BINARIES ONLY FOR: FDM, Financial Reporting Print Server, Interactive Reporting Services, and Strategic Finance.
Solution
FDM can successfully run on a 64 bit 2008 machine. FDM does not have 64 bit binaries, it is a 32 bit component. You can install FDM on 64-bit OS but it is a 32 bit application and will run in 32-bit mode.
Note: Special guidelines have to be followed for running FDM on 64 bit machine:
On a windows 2008 server you need to make sure the following is set:
- User Account Control (UAC) has been disabled within User Accounts under Administrative Tools in the Control Panel.
- The Windows Firewall should be disabled.
- The IIS6 Metabase has been installed along with the Application Server Role on the server to enable ASP.NET with IIS.
NOTE: These items are also required on a x86 Windows 2008 Server.
Doing a Clean Uninstall of EPM 11.1.2 on Microsoft Windows
Doing a Clean Uninstall of EPM 11.1.2 on Microsoft Windows [ID 1140553.1]
Modified 07-JUL-2010 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.0.00 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Goal
Perform a clean uninstall of EPM 11.1.2.
Solution
Uninstall of EPM 11.1.2 is covered in the document "Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide" in Chapter 10 (page 219) "Uninstalling EPM system". This document can be accessed from the following link: http://download.oracle.com/docs/cd/E17236_01/nav/portal_1.htm.
The following steps will help:
Stop all EPM (Hyperion and Oracle*) services.
Follow the steps in Chapter 10 in the above document. Uninstall using the same user account who made the installation.
Note: EPM uninstaller only uninstalls Middleware_Home\EPMSystem11R1. It does not uninstall Middleware_Home items like WL (weblogic), OHS (Oracle HTTP Server), JDK, jRockit, oracle_common, modules. This is because Middleware_Home is shared with other products.
Uninstall the following only when no other use remains:
Run WL uninstaller separately.
Run OHS uninstaller separately.
Run Oracle Application Developer uninstaller separately.
Post-uninstallation checks:
After uninstalling, please check in the start-all programs whether the Hyperion programs/shortcuts have been removed.
Check under Windows registry in HKEY_LOCAL_MACHINE > Software and HKEY_CURRENT_USER > Software whether the Brio > Hyperion > Oracle keys have been removed correctly.
Also confirm deletion of the following environment variables:
ARBORPATH
EPM_ORACLE_HOME
ESSBASEPATH
HYPERION_HOME
As these were created when EPM was installed, they should be removed either by the uninstaller or they need to be removed manually.
Check the PATH variable and delete any portions that need to be removed.
Manually check the file system to see if any files or folders have been left behind. If any of these are left behind, they need to be removed manually.
Ensure that\Documents and Settings\\.oracle.instance file has been deleted.
Ensure that .oracle.products file in Middleware_Home\EPMSystem11R1 has been deleted.
Remove any files left in your existing HYPERION_HOME, if you plan to re-use that location.
Delete any BEA folder on the file system.
Delete or rename installer records in C:\Program Files\common files\InstallShield\* if no other programs installed by this tool remain.
C:\Program Files (x86)\Oracle\ or C:\Program Files\Oracle\inventory
Clean up any remaining Hyperion-related files and directories under the user's install home or C:\Windows
Registry keys which should be deleted:
HKEY_LOCAL_MACHINE\software\wow6432node\oracle\
Delete any additional 'dds_proxy' settings in the registry.
Delete any additional 'arborpath' entries in the registry.
Delete any additional 'hyperion' entries in the registry
Modified 07-JUL-2010 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.0.00 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Goal
Perform a clean uninstall of EPM 11.1.2.
Solution
Uninstall of EPM 11.1.2 is covered in the document "Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide" in Chapter 10 (page 219) "Uninstalling EPM system". This document can be accessed from the following link: http://download.oracle.com/docs/cd/E17236_01/nav/portal_1.htm.
The following steps will help:
Stop all EPM (Hyperion and Oracle*) services.
Follow the steps in Chapter 10 in the above document. Uninstall using the same user account who made the installation.
Note: EPM uninstaller only uninstalls Middleware_Home\EPMSystem11R1. It does not uninstall Middleware_Home items like WL (weblogic), OHS (Oracle HTTP Server), JDK, jRockit, oracle_common, modules. This is because Middleware_Home is shared with other products.
Uninstall the following only when no other use remains:
Run WL uninstaller separately.
Run OHS uninstaller separately.
Run Oracle Application Developer uninstaller separately.
Post-uninstallation checks:
After uninstalling, please check in the start-all programs whether the Hyperion programs/shortcuts have been removed.
Check under Windows registry in HKEY_LOCAL_MACHINE > Software and HKEY_CURRENT_USER > Software whether the Brio > Hyperion > Oracle keys have been removed correctly.
Also confirm deletion of the following environment variables:
ARBORPATH
EPM_ORACLE_HOME
ESSBASEPATH
HYPERION_HOME
As these were created when EPM was installed, they should be removed either by the uninstaller or they need to be removed manually.
Check the PATH variable and delete any portions that need to be removed.
Manually check the file system to see if any files or folders have been left behind. If any of these are left behind, they need to be removed manually.
Ensure that
Ensure that .oracle.products file in Middleware_Home\EPMSystem11R1 has been deleted.
Remove any files left in your existing HYPERION_HOME, if you plan to re-use that location.
Delete any BEA folder on the file system.
Delete or rename installer records in C:\Program Files\common files\InstallShield\* if no other programs installed by this tool remain.
C:\Program Files (x86)\Oracle\ or C:\Program Files\Oracle\inventory
Clean up any remaining Hyperion-related files and directories under the user's install home or C:\Windows
Registry keys which should be deleted:
HKEY_LOCAL_MACHINE\software\wow6432node\oracle\
Delete any additional 'dds_proxy' settings in the registry.
Delete any additional 'arborpath' entries in the registry.
Delete any additional 'hyperion' entries in the registry
In Enterprise Performance Management Workspace When Adding SQR Production Reporting Job Schedule and Selecting a New Recurring Time Event An Error Occ
In Enterprise Performance Management Workspace When Adding SQR Production Reporting Job Schedule and Selecting a New Recurring Time Event An Error Occurs: "java.lang.NullPointerException" [ID 1298325.1]
Modified 30-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
References
Applies to:
Hyperion BI+ - Version: 11.1.1.3.00 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Symptoms
A problem occurs in Hyperion Enterprise Performance Management (EPM) Workspace, when a new schedule is added for an SQR job and a new recurring time event is selected.
At the end in the wizard, the following error is displayed:
java.lang.NullPointerException.
NOTE: The problem occurs only when adding day/week/year events.
The SQR Production Reporting job runs correctly when:
triggered externally,
adding a custom time event,
manually executing it.
Cause
The problem has been reported in unpublished Bug 10397684.
Solution
At the time of writing, a fix has not yet been released by Development.
The following workaround exists:
In Workspace click Navigate-Schedule-Manage Events.
Right-click anywhere and click Add and select "Public Recurring Event" and then create the new event there.
After creating this event, add a schedule to the SQR job and on the screen where you define the event, select "Schedule this job using an existing event" and in the drop-down list select the event name already created in step (2).
Then click next...next until the steps of the wizard are completed.
Modified 30-MAY-2011 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
References
Applies to:
Hyperion BI+ - Version: 11.1.1.3.00 and later [Release: 11.1 and later ]
Information in this document applies to any platform.
Symptoms
A problem occurs in Hyperion Enterprise Performance Management (EPM) Workspace, when a new schedule is added for an SQR job and a new recurring time event is selected.
At the end in the wizard, the following error is displayed:
java.lang.NullPointerException.
NOTE: The problem occurs only when adding day/week/year events.
The SQR Production Reporting job runs correctly when:
triggered externally,
adding a custom time event,
manually executing it.
Cause
The problem has been reported in unpublished Bug 10397684.
Solution
At the time of writing, a fix has not yet been released by Development.
The following workaround exists:
In Workspace click Navigate-Schedule-Manage Events.
Right-click anywhere and click Add and select "Public Recurring Event" and then create the new event there.
After creating this event, add a schedule to the SQR job and on the screen where you define the event, select "Schedule this job using an existing event" and in the drop-down list select the event name already created in step (2).
Then click next...next until the steps of the wizard are completed.
Hyperion Enterprise Performance Management Architect (EPMA) 11.1.2.1.101 Patch
Hyperion Enterprise Performance Management Architect (EPMA) 11.1.2.1.101 Patch Set Update (Patch 11804477) [ID 1308127.1]
Modified 08-APR-2011 Type ANNOUNCEMENT Status PUBLISHED
In this Document
What is being announced?
What do you need to do?
Applies to:
Hyperion Essbase - Version: 11.1.2.1.000 to 11.1.2.1.000 - Release: 11.1 to 11.1
Hyperion Financial Management - Version: 11.1.2.1.000 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Hyperion Planning - Version: 11.1.2.1.000 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Hyperion Profitability - Version: 11.1.2.1.000 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Information in this document applies to any platform.
What is being announced?
We are pleased to announce the immediate availability of Oracle Hyperion Enterprise Performance Management Architect (EPMA) 11.1.2.1.101 Patch: 11804477 on My Oracle Support.
This Patch Set Update (PSU) is mandatory for customers who are currently on / planning for upgrading to Oracle Hyperion Enterprise Performance Management Architect (EPMA) 11.1.2.1.000. It is intended to be applied only on 11.1.2.1.000 environment.
What do you need to do?
Issue Addressed:
This patch addresses the following defect:
Bug:11799602 Unable to update the property values during an import for shared dimensions in Performance Management Architect applications.
The above issue will be encountered when trying to perform Shared Dimension Property updates via .ads file Imports into Oracle Hyperion Performance Management Architect (11.1.2.1.000) Dimension Library. The 11.1.2.1.101 PSU when applied on top of 11.1.2.1.000 will fix this issue.
This patch is available on the following platforms:
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
Download Information:
This patch is available via My Oracle Support.
1. Log into the My Oracle Support portal
2. Choose the Patches & Updates tab
3. Select Patch Name or Number from the drop-down box
4. Perform a search for Patch:11804477 for one of the Platforms noted above
5. The patch file includes both installers and the readme.
Additional Information:
Please refer to the patch readme for system requirements, dependencies, and installation instructions.
Modified 08-APR-2011 Type ANNOUNCEMENT Status PUBLISHED
In this Document
What is being announced?
What do you need to do?
Applies to:
Hyperion Essbase - Version: 11.1.2.1.000 to 11.1.2.1.000 - Release: 11.1 to 11.1
Hyperion Financial Management - Version: 11.1.2.1.000 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Hyperion Planning - Version: 11.1.2.1.000 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Hyperion Profitability - Version: 11.1.2.1.000 to 11.1.2.1.000 [Release: 11.1 to 11.1]
Information in this document applies to any platform.
What is being announced?
We are pleased to announce the immediate availability of Oracle Hyperion Enterprise Performance Management Architect (EPMA) 11.1.2.1.101 Patch: 11804477 on My Oracle Support.
This Patch Set Update (PSU) is mandatory for customers who are currently on / planning for upgrading to Oracle Hyperion Enterprise Performance Management Architect (EPMA) 11.1.2.1.000. It is intended to be applied only on 11.1.2.1.000 environment.
What do you need to do?
Issue Addressed:
This patch addresses the following defect:
Bug:11799602 Unable to update the property values during an import for shared dimensions in Performance Management Architect applications.
The above issue will be encountered when trying to perform Shared Dimension Property updates via .ads file Imports into Oracle Hyperion Performance Management Architect (11.1.2.1.000) Dimension Library. The 11.1.2.1.101 PSU when applied on top of 11.1.2.1.000 will fix this issue.
This patch is available on the following platforms:
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
Download Information:
This patch is available via My Oracle Support.
1. Log into the My Oracle Support portal
2. Choose the Patches & Updates tab
3. Select Patch Name or Number from the drop-down box
4. Perform a search for Patch:11804477 for one of the Platforms noted above
5. The patch file includes both installers and the readme.
Additional Information:
Please refer to the patch readme for system requirements, dependencies, and installation instructions.
Thursday, June 2, 2011
HPS Employee is not available in Shared Services Console version 11.1.1.2
HPS Employee is not available in Shared Services Console version 11.1.1.2 [ID 824283.1]
Modified 18-NOV-2010 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
References
Applies to:
Hyperion Performance Scorecard - Version: 11.1.1.0.00 to 11.1.1.0.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.
Symptoms
Error occurs in HSS when click on the HPS application and attempt to associate a newly created employee to the HPS login user.
This can work successfully on the first attempt but always on the second attempt it will fail
"Performance scorecard is having difficulty fulfilling your request. Consult your performance scorecard administrator"
Cause
Caused by current charset used by customer.
Changing charset resolved the issue .
Solution
If unable to change charset, the following workaround will also resolve;
1. Reconfigure HPS to use Oracle JDBC driver instead of DataDirect driver.
2. Copy the Oracle driver to \webapps\HPSWebReports\WEB-INF\lib
3. Open HPSConfig.properties:
Modify this part of the file:
hyperion.hps.main_data_store.url=jdbc:hyperion_pmd:sqlserver://:<
server-port>;DatabaseName=
hyperion.hps.main_data_store.user_name=
hyperion.hps.main_data_store.password=
hyperion.hps.main_data_store.driver_class_name=com.hyperion.pmd.jdbc.sqlserver.SQLServerDriver
hyperion.hps.main_data_store.castor_engine=sql-server
It has to look like this :
hyperion.hps.main_data_store.url=jdbc:oracle:thin:: :
hyperion.hps.main_data_store.user_name=
hyperion.hps.main_data_store.password=
hyperion.hps.main_data_store.driver_class_name=oracle.jdbc.driver.OracleDriver
hyperion.hps.main_data_store.castor_engine=oracle
Add another line in it:
hyperion.hps.use_db_info_from_config_file=true
4. Save it.
5. Restart HPS.
Modified 18-NOV-2010 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
References
Applies to:
Hyperion Performance Scorecard - Version: 11.1.1.0.00 to 11.1.1.0.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.
Symptoms
Error occurs in HSS when click on the HPS application and attempt to associate a newly created employee to the HPS login user.
This can work successfully on the first attempt but always on the second attempt it will fail
"Performance scorecard is having difficulty fulfilling your request. Consult your performance scorecard administrator"
Cause
Caused by current charset used by customer.
Changing charset resolved the issue .
Solution
If unable to change charset, the following workaround will also resolve;
1. Reconfigure HPS to use Oracle JDBC driver instead of DataDirect driver.
2. Copy the Oracle driver to \webapps\HPSWebReports\WEB-INF\lib
3. Open HPSConfig.properties:
Modify this part of the file:
hyperion.hps.main_data_store.url=jdbc:hyperion_pmd:sqlserver://:<
server-port>;DatabaseName=
hyperion.hps.main_data_store.user_name=
hyperion.hps.main_data_store.password=
hyperion.hps.main_data_store.driver_class_name=com.hyperion.pmd.jdbc.sqlserver.SQLServerDriver
hyperion.hps.main_data_store.castor_engine=sql-server
It has to look like this :
hyperion.hps.main_data_store.url=jdbc:oracle:thin:: :
hyperion.hps.main_data_store.user_name=
hyperion.hps.main_data_store.password=
hyperion.hps.main_data_store.driver_class_name=oracle.jdbc.driver.OracleDriver
hyperion.hps.main_data_store.castor_engine=oracle
Add another line in it:
hyperion.hps.use_db_info_from_config_file=true
4. Save it.
5. Restart HPS.
A Unique Instance Name Is Required When Configuring A New Install Of EPM 11.1.2.1 In Distributed Environment
A Unique Instance Name Is Required When Configuring A New Install Of EPM 11.1.2.1 In Distributed Environment [ID 1317679.1]
Modified 10-MAY-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Financial Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Planning - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Profitability - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Information in this document applies to any platform.
Goal
To install and configure Oracle EPM 11.1.2.1 in a distributed environment with a proper Instance name on each server
Solution
When configuring EPM 11.1.2.1 in a distributed environment, it is necessary to supply a new, unique Instance name on each server.
For example.
If using the default Instance name 'epmsystem1' on the first server, if you keep the same naming convention on subsequent servers, you will need to supply new, unique Instance names such as epmsystem2, epmsystem3, etc.
During Configuration each instance gets written to the EPM System Registry and the EPM System Configurator verifies that each instance name is unique. If you fail to provide a new unique instance name during the configuration process you will receive a message stating that the instance name is not valid. You will be forced to go back and enter a unique instance name.
Note: If you are applying the maintenance release (11.1.2 to 11.1.2.1), during the configuration process you select the first option "Modify existing instance" since the epmsystem1 instance name already exists and is shared by all servers in the distributed environment. Be sure not to delete or change the instance names during a maintenance release configuration as it will cause the configuration to change from a maintenance install to a new installation and will cause issues with the rest of the server deployments in the distributed environment.
Modified 10-MAY-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion BI+ - Version: 11.1.2.1.000 and later [Release: 11.1 and later ]
Hyperion Essbase - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Financial Management - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Planning - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Hyperion Profitability - Version: 11.1.2.1.000 and later [Release: 11.1 and later]
Information in this document applies to any platform.
Goal
To install and configure Oracle EPM 11.1.2.1 in a distributed environment with a proper Instance name on each server
Solution
When configuring EPM 11.1.2.1 in a distributed environment, it is necessary to supply a new, unique Instance name on each server.
For example.
If using the default Instance name 'epmsystem1' on the first server, if you keep the same naming convention on subsequent servers, you will need to supply new, unique Instance names such as epmsystem2, epmsystem3, etc.
During Configuration each instance gets written to the EPM System Registry and the EPM System Configurator verifies that each instance name is unique. If you fail to provide a new unique instance name during the configuration process you will receive a message stating that the instance name is not valid. You will be forced to go back and enter a unique instance name.
Note: If you are applying the maintenance release (11.1.2 to 11.1.2.1), during the configuration process you select the first option "Modify existing instance" since the epmsystem1 instance name already exists and is shared by all servers in the distributed environment. Be sure not to delete or change the instance names during a maintenance release configuration as it will cause the configuration to change from a maintenance install to a new installation and will cause issues with the rest of the server deployments in the distributed environment.
New Features Tutorials for Hyperion Enterprise Performance Management 11.1.2 Product Information Center
New Features Tutorials for Hyperion Enterprise Performance Management 11.1.2 Product Information Center [ID 1242894.1]
Modified 02-FEB-2011 Type REFERENCE Status PUBLISHED
In this Document
Purpose
Scope
New Features Tutorials for Hyperion Enterprise Performance Management 11.1.2 Product Information Center
Applies to:
Middleware > Enterprise Performance Management
Information in this document applies to any platform.
Purpose
This document contains the list of New Features tutorials available for Hyperion Enterprise Performance Management 11.1.2 in support of the Hyperion Enterprise Performance Management 11.1.2 Product Information Center.
Scope
This document serves as a reference document to support the Hyperion Enterprise Performance Management 11.1.2 Product Information Center.
New Features Tutorials for Hyperion Enterprise Performance Management 11.1.2 Product Information Center
11.1.2 New Feature Tutorials
Oracle Essbase 11.1.2 New Features
Oracle Essbase Studio 11.1.2 New Features
Oracle Hyperion Data Relationship Management, Fusion Edition 11.1.2 New Features
Oracle Hyperion Disclosure Management 11.1.2 Overview
Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition 11.1.2 New Features
Oracle Hyperion Financial Close Management 11.1.2 Overview
Oracle Hyperion Financial Data Quality Management, Fusion Edition 11.1.2 New Features
Oracle Hyperion Financial Management, Fusion Edition 11.1.2 New Features
Oracle Hyperion Financial Reporting, Fusion Edition 11.1.2 New Features
Oracle Hyperion Planning, Fusion Edition 11.1.2 New Features - Part 1
Oracle Hyperion Planning, Fusion Edition 11.1.2 New Features - Part 2
Oracle Hyperion Profitability and Cost Management, Fusion Edition 11.1.2 New Features
Oracle Hyperion Public Sector Planning and Budgeting, Fusion Edition 11.1.2 Overview
Oracle Hyperion Smart View for Office, Fusion Edition 11.1.2 New Features
Modified 02-FEB-2011 Type REFERENCE Status PUBLISHED
In this Document
Purpose
Scope
New Features Tutorials for Hyperion Enterprise Performance Management 11.1.2 Product Information Center
Applies to:
Middleware > Enterprise Performance Management
Information in this document applies to any platform.
Purpose
This document contains the list of New Features tutorials available for Hyperion Enterprise Performance Management 11.1.2 in support of the Hyperion Enterprise Performance Management 11.1.2 Product Information Center.
Scope
This document serves as a reference document to support the Hyperion Enterprise Performance Management 11.1.2 Product Information Center.
New Features Tutorials for Hyperion Enterprise Performance Management 11.1.2 Product Information Center
11.1.2 New Feature Tutorials
Oracle Essbase 11.1.2 New Features
Oracle Essbase Studio 11.1.2 New Features
Oracle Hyperion Data Relationship Management, Fusion Edition 11.1.2 New Features
Oracle Hyperion Disclosure Management 11.1.2 Overview
Oracle Hyperion Enterprise Performance Management Architect, Fusion Edition 11.1.2 New Features
Oracle Hyperion Financial Close Management 11.1.2 Overview
Oracle Hyperion Financial Data Quality Management, Fusion Edition 11.1.2 New Features
Oracle Hyperion Financial Management, Fusion Edition 11.1.2 New Features
Oracle Hyperion Financial Reporting, Fusion Edition 11.1.2 New Features
Oracle Hyperion Planning, Fusion Edition 11.1.2 New Features - Part 1
Oracle Hyperion Planning, Fusion Edition 11.1.2 New Features - Part 2
Oracle Hyperion Profitability and Cost Management, Fusion Edition 11.1.2 New Features
Oracle Hyperion Public Sector Planning and Budgeting, Fusion Edition 11.1.2 Overview
Oracle Hyperion Smart View for Office, Fusion Edition 11.1.2 New Features
Subscribe to:
Posts (Atom)