OBIA 11g ODI-1228: Task SIL_GLAccountDimension.W_GL_ACCOUNT_D failed ...Caused By: java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long (Doc ID 1970349.1)

Last updated on JANUARY 31, 2017

Applies to:

Business Intelligence Applications Consumer - Version 11.1.1.7.1 and later
Information in this document applies to any platform.

Symptoms

The following error occurs on a custom scenario.

Generated the scenario of the w_gl_account_d load again (SILOS_SIL_GLACCOUNTDIMENSION) and regenerated the load plan and ran it.

ODI-1228: Task SIL_GLAccountDimension.W_GL_ACCOUNT_D (Integration) fails on the target ORACLE connection BIAPPS_DW. Caused By: java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long


Looked at the code and it tried to run:

" create table BIAPPS_DW.I$_53732550_1
( SET_UK_FOR_TARGET_TABLE_IN_INTERFACE,
ROW_WID NUMBER NULL, ...


"Which fails on SET_UK_FOR_TARGET_TABLE_IN_INTERFACE.
To make sure it is indeed the latest scenario at fault, the new versions of the scenario were deleted, regenerated the load plan and ran a load, which did not fail with this issue.

Found a similar issue detailed in <Note 1946359.1> OBIA 11g: ODI Load Plan Fails When Creating Temporary Table Fails On Scenario SDE_FUSION_V1_ADAPTOR_SDE_FUSION_PERSISTEDSTAGE_TALENTMANAGEMENT but could not find a way to perform parallel steps to solve the issue in SILOS_SIL_GLACCOUNTDIMENSION.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms