Why... Why... Why?
This blog is dedicated to documenting error resolution and other tidbits that I discover while working as a Consultant in the Oracle EPM (Hyperion) field. As much of my job revolves around issue resolution, I see an opportunity to supplement the typical troubleshooting avenues such as the Oracle Knowledgebase and Oracle Forums with more pinpointed information about specific errors as they are encountered. Beware, the information found in this blog is for informational purposes only and comes without any warranty or guarantee of accuracy.

EPMVirt: Create your own Oracle Hyperion Virtual Environment:

Saturday, December 31, 2011

FDM – Error exporting grid to Excel

Problem Description
FDM – Error exporting grid to Excel

Activates -> Maps -> Add new Grid ,then Export to Excel and received the error “Error:SaveAs method of Workbook class failed”

Resolution
The temporary directory must be created on the FDM Application Server,
\Windows\SysWOW64\config\
systemprofile\Desktop

http://docs.oracle.com/cd/E12825_01/epm.111/readme/ra_1111400_readme.html

12877897
If the Financial Reporting Print Server is installed on a Microsoft Windows 2008 server, Complete Book In PDF does not display external content documents. To resolve this issue, do one of the following:
·        If the Financial Reporting Print Server is installed and configured on a Microsoft Windows 2008 x64 server, create the following directory:
C:\Windows\SysWOW64\config\systemprofile\Desktop
·        If the Financial Reporting Print Server is installed and configured on a Microsoft Windows 2008 x86 server, create the following directory:
C:\Windows\System32\config\systemprofile\Desktop

Smartview Menu not found in Excel

Problem Description
The SmartView menu is not found in Excel, although it was installed.  

Resolution
In Excel check that the plugin is not disabled,

Click on Excel options,
Add-Ins
At the bottom there is a drop down that is labeled "Manage", choose "Disabled Items" and hit Go
See if it is listed as disabled and enable it.

Configuring EPMA - the Service Name or SID must match with SERVICE_NAME

Problem Description
I am getting bellow error while configuring Financial Management on epma 11.1.2.1:

EPMCFG-10390: For successful completion of this task, the Service Name or SID must match with SERVICE_NAME in tnsnames.ora file.

I have made sure tnsnames.ora (from C:\app\Administrator\product\11.2.0\client_1\network\admin) has the same sid as i have given on configurator screen.


Resolution
I discovered that in my case the configurator was having trouble creating the .udl file for HFM. So I went in and manually created the .udl file and then the configuration tool, while still showing that warning, did complete successfully.

In user_projects\epmsystem1\products\FinancialManagement\Server Working Folder

Create a new file, ORACLE_hfm.udl

Enter the credentials to the Oracle ODE connection, click allow save password, and click test to ensure it works.

After this the config tool should be able to complete the remaining configuration tasks.

WebLogic throws java.lang.OutOfMemoryError: getNewTla

Problem Description:
I encountered a problem with WebLogic throwing atypical out of memory errors. I would set the heap size to 1660m and then the error would go away for a while or trickle down to the next product. Eventually, increasing the heap size did not seem the right solution. This happened after setting the MSAD external authentication in Shared Services.

Here is the error that we found: 
java.lang.OutOfMemoryError
Exception in thread "[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError
Exception in thread "weblogic.timers.TimerThread" java.lang.OutOfMemoryError: getNewTla

Resolution:
I had suspicions about the MSAD configuration because the logs indicated the failure occurs when trying to initialize or read the MSAD provider that had been set up. It turns out the company was very large, and the Maximum Size in the External Authentication configuration was set to 0 (unlimited). Consequently, OOM errors were being thrown. The value was set to 200 which resolved the issue.



 http://docs.oracle.com/cd/E17236_01/epm.1112/hss_admin.pdf