Support Article
SQL Error: ORA-00972: identifier is too long
SA-76916
Summary
A Business Intelligence Exchange (BIX) Extract rule is configured to extract data to a target database. The Extract rule includes a property name which is greater than 30 characters. When generating a Data Definition Language (DDL) to create a schema structure in the target database, the DDL includes the lengthy property name.
Error occurs and the DDL is not executed correctly.
CREATE TABLE GCS_Mortgage_Work
(
"PZINSKEY" VARCHAR2(256 CHAR) NULL,
"PXEXTRACTIDENTIFIER" VARCHAR2(256 CHAR) NULL,
"PXEXTRACTDATETIME" TIMESTAMP NULL,
"DEPOSIT" VARCHAR2(32 CHAR) NULL,
"INTERESTRATE" VARCHAR2(32 CHAR) NULL,
"MORTGAGEAMOUNT" VARCHAR2(32 CHAR) NULL,
"MORTGAGEAPPLICATIONID" VARCHAR2(32 CHAR) NULL,
"MORTGAGEAPPLICATIONNAME" VARCHAR2(32 CHAR) NULL,
"MORTGAGETERM" VARCHAR2(32 CHAR) NULL,
"ABCDEFGHIJKLMNOPQRSTUVWXYZNOWIKNOWMYABCNEXTTIMEWONTYOUSINGWITHME" VARCHAR2(32 CHAR) NULL
);
Error Messages
SQL Error: ORA-00972: identifier is too long
00972. 00000 - "identifier is too long"
*Cause: An identifier with more than 30 characters was specified.
*Action: Specify at most 30 characters.
Steps to Reproduce
- Configure an Extract rule.
- Add properties with names which are greater than 30 characters.
- Run the Extract rule to generate a DDL.
- Execute the query generated in the database.
Root Cause
A third-party product issue.
Oracle has a limitation of 30 characters for the column name. Hence, the DDL is not executed correctly.
Resolution
Perform the following local-change:
Map the property name, which is greater than 30 characters, to a shortname.
Tags:
Published April 6, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.