My Oracle Support Banner

LCM Import of Essbase Application Fails "Error reported from Essbase. object name too long for non-unicode mode application" (Doc ID 3045636.1)

Last updated on SEPTEMBER 10, 2024

Applies to:

Hyperion Essbase - Version 21.1.0.0.0 and later
Information in this document applies to any platform.

Symptoms

When importing Essbase 11g artifacts using EPM Shared Services 11.2.15+ LCM, the migration fails with the error:

"EPMLCM-14000 Error reported from Essbase"

 

Errors in SharedServices_LCM.log:

[EPMLCM-37003] [oracle.EPMLCM] STATUS DOCUMENT FROM PRODUCT FOR IMPORT CALL TO PLUGIN

<lcm_status><resource name="file_name> path="<path>" details="object name <file_name> too long for non-unicode mode application <application_name>"/></lcm_status>

[EPMLCM-14000] [oracle.EPMLCM] [tid: 9755] Error reported from Essbase. object name <file_name> too long for non-unicode mode application <application_name

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.