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.

Advertisements

Posted on March 15, 2016, in FDM, Oracle Essbase, Oracle Hyperion Planning, Uncategorized. Bookmark the permalink. Leave a comment.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: