Sunday, September 2, 2012

Hyperion Suites 11.1.2.x known issues

Essbase Server

Defect Number

No Defect Number

After configuring Essbase failover clusters and configuring EPM system products, you must install an OPMN patch before starting any services. Failure to install this patch prior to starting services may result in the following situations:

· Configured OPMN service-failover processes may fail to restart if they unexpectedly terminate even when restart-on-death is set to true in opmn.xml.

· High availability does not work if you do anything that causes opmn.xml to be reread; for example, if you are instructed by Oracle Technical Support to turn on OPMN debug.

· On Windows x64, if you stop OPMN on the active node, the passive node may terminate abnormally.

These are the patch locations on the Oracle Automated Release Updates Web site:

· Linux32 http://aru.us.oracle.com:8080/ARU/ViewPatchRequest/process_form?aru=13450936

Win32 http://aru.us.oracle.com:8080/ARU/ViewPatchRequest/process_form?aru=13479022

· Linux x64 http://aru.us.oracle.com:8080/ARU/ViewPatchRequest/process_form?aru=13468939

· Win x64 http://aru.us.oracle.com:8080/ARU/ViewPatchRequest/process_form?aru=13468976

· Solris64 http://aru.us.oracle.com:8080/ARU/ViewPatchRequest/process_form?aru=13473585

· AIX64 http://aru.us.oracle.com:8080/ARU/ViewPatchRequest/process_form?aru=13473586

· HPUX ia64 http://aru.us.oracle.com:8080/ARU/ViewPatchRequest/process_form?aru=13484399


9789002

OPMN cannot start Essbase if ARBORPATH is pointing to a mapped drive.

Workaround: Do not point ARBORPATH to a mapped drive.


10305367

On new Linux machines, Essbase may fail to start after installation. Errors messages regarding the file libstdc++ may be returned. For example:

./ESSCMD: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

Workaround: Install compat-libstdc++.

1. Perform an internet search for compat-libstdc++.

2. Find a download that is appropriate for your environment, such as SUSE Linux or Red Hat Linux, 32-bit or 64-bit.

3. Follow the instructions provided to install the file.

4. Install Essbase.


10388049

You must include the path for LIBJVM in the Library path for Essbase.

Workaround: Edit essbase.cfg and change:

/vol1/nnguyen/hyperion/Oracle/Middleware/jdk160_21/jre/lib/IA64W/server/libjvm.so

to:

$EPM_ORACLE_HOME/../jdk160_21/jre/lib/IA64W/server/libjvm.so


11739475

During Essbase upgrades on Solaris platforms, when the Staging Tool copies the app folder over the network, it does not copy application files with a -l bit on the permission; for example, -rwx--l--- <FILE_NAME>. Application files that have the -l bit are usually .apb, .db, and .ddb files.

Workaround: Do not select the option “Automatically copy files to a mounted or mapped file system.” You must select “Get a list of file transfer instructions” and then manually transfer the files using the tar utility.


11716777

Creating an aggregate storage tablespace file location with a path that is exactly 496 bytes long may result in abnormal program termination.


11789346

The Essbase rehosting tool attempts to correct partitions on an Essbase Release 11.1.2.1 installation where the source or target reside on an older version of Essbase that does not support logical names. This results in an invalid partition.

Workaround: Upgrade both the source and target servers, or remove the partition definition before upgrading.


11882875

Essbase Server does not start after an overinstallation.

Workaround: Edit opmn.xml and add numprocs="1" on the restart-on-death line. For example, <process-set id="AGENT" numprocs="1" restart-on-death="false">

Financial Management


Defect Number

8560293

Microsoft Windows 2003 SP2: In some Windows 2003 SP2 installations, clients may experience “Access Denied” issues while connecting from Financial Management or Financial Reporting. The client machine event log displays a “General access denied” error message.

Workaround: Add the following DWORD value to the Windows registry if it does not already exist:

1. In the Registry Editor, under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Rpc, add a new DWORD value with the name Server2003NegotiateDisable.

2. Right-click Server2003NegotiateDisable and click Modify.

3. For the Value Data, enter 1, and click OK.

4. Note: This setting disables the bind-time negotiation and multiple-transfer syntax negotiation.

5. Exit the Windows Registry Editor and restart the computer.


9509373

After EPM System Installer installs Financial Management on a 32-bit or 64-bit machine, the email alerts from Financial Management do not work because EPM System Installer did not register Microsoft .NET Framework Mailer.dll.

Workaround: Register Mailer.dll, locate and run the correct register command on your system:

· 32-bit: C:\WINDOWS\Microsoft.NET\Framework\
<v2.X.XXXXX>\RegAsm.exe /codebase <EPM_ORACLE_HOME> products\FinancialManagement\Web Server\Mailer.dll

· 64-bit: C:\WINDOWS\Microsoft.NET\Framework64\
<v2.X.XXXXX>\RegAsm.exe /codebase <EPM_ORACLE_HOME>\products\FinancialManagement\Web Server\Mailer.dll


9689601

When you deploy Financial Management, you may receive the following error:

“Please install missing templates: Oracle JRF WebServices Asynchronous services”

JRF WebServices Asynchronous services are required only if you are using Financial Management with Financial Close Management. If you are not using Financial Management with Financial Close Management, you do not have to select the Deploy to Application Server task in EPM System Configurator for Financial Management. If you inadvertently select Deploy to Application Server for Financial Management, you can ignore any error messages. You need a working Financial Management Web Services Web application deployment only if you are using Financial Management with Financial Close Management.


10030819

In order to use the Financial Management Lifecycle Management Web service, you must manually install Web Services Extensions 3.


10278069



On a Windows 2008 64 and 32 BIT server, when trying to create a Financial Management application in EPM Workspace, the following error may be displayed:

The specified module could not be found.
Show Details:
Error Number:-2147024770
Error Description:006~ASP 0177~Server.CreateObject Failed~8007007e
Error Source:Server object
Page On which Error Occurred:/hfm/LoadExtract/Loadmeta.asp



Workaround: On the Financial Management Web Server, run iisreset in a DOS command window.


10431658

When you select Windows, then Start, then EPM, then HFM, and then Utilities, the Toolbox shortcut is not available.

Workaround: Navigate directly to the product folder for Financial Management, and click the AppToolBox.exe found in EPM_ORACLE_HOME/products/FinancialManagement/Utilities/ApplicationToolbox/HFMToolbox.exe.


10640500

If you use Oracle Database Client 10.2.x or 11.1.x for Financial Management, you must set the StmtCacheSize registry setting for Oracle OLE DB to 10 on all Financial Management application servers. This is due to a memory issue in Oracle Provider for OLE DB. The registry setting path is: Hkey_Local_Machine\Software\Oracle\Key_Homename\Oledb. Note that the 11.2.x Oracle Database Client should not be changed.

To resolve the high memory usage:

1. Enable Statement Caching. (The configured value must not be zero. The recommended value is between and 1 and 10.)

2. Edit the following registry value: Hkey_Local_Machine\Software\Oracle\Key_Homename\Oledb Value Name: StmtCacheSize Value (decimal): 1 where Key_Homename refers to the appropriate Oracle Home.

3. Stop and restart the HFM application processes.

In addition, if you are using System 11 on a 64-bit operating system with a 10g database, the Oracle OLE provider on all Financial Management servers must be at least 10.2.0.4.21+. If you are using 32-bit with 10g, the OLE provider must be at least as high a version as your database server. If you are running 32-bit or 64-bit and using 11.1.0.6 or 11.1.0.7 OLE Provider, you must upgrade to Oracle Database Client 11.1.0.7.33+.


11803646

EPM System Configurator does not detect registered Financial Management clusters.

Workaround: When configuring on the remote server, select the "DB Config" task along with other Financial Management configuration tasks. Available clusters and servers will then be visible on the Server/Cluster Configuration panel.


11813179

After installing and configuring Foundation Services and Financial Management, application creation may fail with the following error:

The specified module could not be found.
Error Number:-2147024770
Error Description:006~ASP 0177~Server.CreateObject Failed~8007007e
Error Source:Server object



Workaround: Restart the IIS process on the Financial Management Web server.


11837654

When using EPM System Configurator to configure Financial Management for DCOM, a Java Runtime Environment an error is returned.

Workaround: Re-run EPM System Configurator and perform the DCOM configuration for Financial Management a second time.

Hyperion Business Rules


Defect Number

Known Issues
11857456

In Hyperion Business Rules Release 11.1.1.3, Essbase applications with Japanese names may not display correctly in the Shared Services console. As a result, you may not be able to migrate the applications using Lifecycle Management.

Workaround: Update the Hyperion Business Rules properties in the Essbase Administration Console after upgrading to Release 11.1.2.1.



Strategic Finance

Defect Number

11705192

If you install the Strategic Finance client and then run the installation again in "Repair" mode, the following error is displayed:

MSXML4 Sp3 vcredist_x86 installation failed

Workaround: Do one of the following:

· Run the installer/uninstaller executable and select Repair.

· Run Add/Remove Programs and select Change. This launches the installer/uninstaller executable. After the installer/uninstaller executable is launched, select Repair.


http://docs.oracle.com/cd/E17236_01/epm.1112/readme/epm_1112100_readme.html

No comments:

Post a Comment