Category Archives: Oracle Hyperion Planning

All Posts related to Oracle Hyperion Planning tools

A novice’ guide to configuring Oracle EPM on Linux

Most of the time, Hyperion consultants who are not very much familiar with Linux operating system, face problems working with the command line interface.

A utility called Xming comes handy for configuring the EPM system on Linux.

Following steps explain the steps to run EPM Configuration Utility in a console format.

Step 1:
Download and Install Xming available Here.
Step 2:
Run Xming. Make sure it is running.

 

Xming

Step 3: Activate X11 forwarding in Putty

Putty

Step 4: Connect to the server, and go to Configuration directory path
(In our case:

Terminal

Step 5: Run the Configtool utility.

Conofigtool.png

Sometime The file descriptor soft limit may be too less, and not allow opening of the utility.
Use following command to update the File Descriptor Limit
ulimit -n 12000

You should now be able to work with the Configuration utility normally like you work in console.

Advertisements

FDMEE Error : Other Language Support

While we setup the Planning Applications in languages other than English, The Hyperion Essbase Database is created with Unicode UTF-8 encoding.

This might require additional configuration steps for pushing data from FDM

By Default the FDM supports UTF-8 Character set.

UTFAnd if you have special characters in languages other than English, in FDM Period definitions as well as in Dimension mappings,

UTF8.PNG

You may get error while trying to load data to Planning/Essbase:
2015-10-17 08:46:08,835 FATAL [AIF]: Error in CommData.consolidateData
Traceback (most recent call last):
File “<string>”, line 5288, in consolidateData
File “<string>”, line 1116, in callOdiServlet
File “__pyclasspath__/urllib.py”, line 1250, in urlencode
UnicodeEncodeError: ‘ascii’ codec can’t encode characters in position 0-4: ordinal not in range(128)

2015-10-17 08:46:08,910 DEBUG [AIF]: Comm.finalizeProcess – START
2015-10-17 08:46:08,911 DEBUG [AIF]: CommData.updateRuleStatus – START
2015-10-17 08:46:08,911 DEBUG [AIF]:
UPDATE AIF_BALANCE_RULES
SET STATUS = CASE ‘FAILED’
WHEN ‘SUCCESS’ THEN
CASE (
SELECT COUNT(*)
FROM AIF_PROCESS_DETAILS pd
WHERE pd.PROCESS_ID = 26
AND pd.STATUS IN (‘FAILED’,’WARNING’)
)
WHEN 0 THEN ‘SUCCESS’
ELSE (
SELECT MIN(pd.STATUS)
FROM AIF_PROCESS_DETAILS pd
WHERE pd.PROCESS_ID = 26
AND pd.STATUS IN (‘FAILED’,’WARNING’)
)
END
ELSE ‘FAILED’
END
WHERE RULE_ID = 6

2015-10-17 08:46:08,913 DEBUG [AIF]: CommData.updateRuleStatus – END
2015-10-17 08:46:08,913 FATAL [AIF]: Error in COMM Consolidate Data
2015-10-17 08:46:08,914 DEBUG [AIF]: Comm.updateProcess – START
2015-10-17 08:46:08,917 DEBUG [AIF]: Comm.updateProcess – END
2015-10-17 08:46:08,918 DEBUG [AIF]: The fdmAPI connection has been closed.
2015-10-17 08:46:08,918 INFO [AIF]: FDMEE Process End, Process ID: 26

 

One way to steer around this error is to update the character encoding to UTF-16.

Worked in our case.

FDM Error : Loading ERP Data

Quick Solution::
Add Application Root Folder and Save.

Application Root

Read below for Problem Summary.

Importing ERP data into Target Hyperion Planning or Essbase Application is primary usage of FDM Application setup.

There are sometimes small elements which we might ignore, and lead to unprecedented errors. One such error occurs, while importing Data after initializing the Source system.

This error comes after ODI fetches data from source system, and puts this data in the FDM Staging Table.

The error is because of the absence of FDM Application root directory, which has inbox/outbox folders, which will be used to store the Flat file to be imported into Essbase.

Error Summary:

FDMEE Data extraction Error
The Value for Profile option ‘PROFILE_APP_ROOT_DIRECTORY’ is invalid: NULL 

‘PROFILE_APP_ROOT_DIRECTORY’ is invalid: NULL, 683 FATAL [AIF]: Error in COMM Pre Import Data

Additional ODI Logs:
[2015-10-14T19:47:38.082+04:00] [EPMServer0] [ERROR] [ODI-1134] [] [tid: 125] [userId: <anonymous>] [ecid: 0000L1b2G4EEOP15zvg8yW1M6bzc0004dm,1:24283] [APP: oraclediagent] Agent OracleDIAgent encountered an error: ODI-1217: Session COMM_LOAD_BALANCES (37501) fails with return code 7000. Caused by: ODI-1226: Step FAILED – Invalid Source System fails after 1 attempt(s).[[
ODI-1217: Session COMM_LOAD_BALANCES (37501) fails with return code 7000.
ODI-1226: Step FAILED – Invalid Source System fails after 1 attempt(s).
ODI-1232: Procedure COMM Finalize Process execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File “<string>”, line 13, in <module>
File “<string>”, line 162, in finalizeProcess
RuntimeError: ODI-1226: Step COMM Pre Import Data fails after 1 attempt(s).
ODI-1232: Procedure COMM Pre Import Data execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File “<string>”, line 7, in <module>
File “<string>”, line 4578, in preImportData
File “<string>”, line 455, in executeScript
File “<string>”, line 394, in doScriptInit
RuntimeError: The value for Profile Option ‘PROFILE_APP_ROOT_DIRECTORY’ is invalid: NULL

AIF Web Log

[2015-10-12T11:42:03.746+04:00] [EPMServer0] [ERROR] [] [oracle.apps.erpi.model] [tid: 22] [userId: <anonymous>] [ecid: 0058UDr854hEOP15zvg8yW0005Ji0001XQ,0:1] [APP: AIF#11.1.2.0] [SRC_CLASS: com.hyperion.aif.util.RegistryUtil] [SRC_METHOD: getProductParams] An unexpected error has occurred.[[
oracle.epm.fm.common.exception.HFMException: EPMHFM-65536: An unexpected error has occurred.

Log pointing to the exact Exception:

 

ODI-1226: Step COMM Export Data fails after 1 attempt(s).
ODI-1232: Procedure COMM Export Data execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File “<string>”, line 9, in <module>
File “<string>”, line 5040, in exportData
RuntimeError: java.io.IOException: No such file or directory

at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine(SnpScriptingInterpretor.java:322)
at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.exec(SnpScriptingInterpretor.java:170)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java:2473)
at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:48)
at oracle.odi.runtime.agent.execution.cmd.ScriptingExecutor.execute(ScriptingExecutor.java:1)
at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:580)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:468)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2128)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1931)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:580)
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1073)
at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:83)
at java.lang.Thread.run(Thread.java:662)
Caused by: Traceback (most recent call last):
File “<string>”, line 9, in <module>
File “<string>”, line 5040, in exportData
RuntimeError: java.io.IOException: No such file or directory

FDMEE Errors: Writeback failure

In this series of Blogs, I am going to document few FDMEE errors, especially version 11.1.2.4, which I couldn’t find any reference about or there are no KB articles about.

The following error shows up in FDM, while importing Data from Planning to load to Oracle E-business Suite:

ODI-1226: Step COMM Validate Data fails after 1 attempt(s).
ODI-1232: Procedure COMM Validate Data execution fails.
Caused By: org.apache.bsf.BSFException: exception from Jython:
Traceback (most recent call last):
File “<string>”, line 9, in <module>
File “<string>”, line 4407, in validateData
File “<string>”, line 2622, in validateData
RuntimeError: [u”Error: Data rows with unmapped dimensions exist for Period ‘\u064a\u0646\u0627\u064a\u0631-2016′”]

The Error, although says, is due to Unmapped Dimension, but in fact it is not contributed because of any unmapped dimension, rather, an erroneous dimension  mapping, wherein one member is mapped more than once in the mapping table.

Example below:

On running a visual scan of all Mappings, and deleting the duplicate mappings, this error can be removed.

 

Additional Log Details:

ERROR [AIF]: Cannot calculate. Essbase Error(1200315): Error parsing formula for [FIX STATEMENT] (line 4): invalid object type
INFO  [AIF]: EssbaseService.extractData – END (com.essbase.api.base.EssException: Cannot calculate. Essbase Error(1200315): Error parsing formula for [FIX STATEMENT] (line 4): invalid object type)
DEBUG [AIF]: AIFUtil.callOdiServlet – END
FATAL [AIF]: Error in CommData.extractDataFromSource

 

 

%d bloggers like this: