While Loading Data In Pin_rel,Erro Od Too Long Identifier Is Generated For Tmp_profile_event_t Table (Doc ID 1120327.1)

Last updated on SEPTEMBER 30, 2013

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.1.0 [Release 7.4.0]
Information in this document applies to any platform.
Checked for relevance on 30-Sept-2013

Symptoms

This issue is caused during the upgrade to 7.4

when trying to load data using pin_rel it is giving following error:
ORA-00972: identifier is too long

Object is tmp_profile_event_o350816854991 table for which it is failing in creating as name of the object had been increased more than the max length of BRM objects.

In our DB value of POID_IDS2 sequence is 350816854991 ,which is causing this problem and we are not able to load the data

During a pin_rel session we got the following error in rel.pinlog:
Debug 05/17/10 5:46:04:0713 PM ( 1274098564713 ) T:main REL RELDriver
1:idcocci1:UnknownProgramName:0:main:1:1274098564:0
The setup of tmp_unprocessed_events_t table completed successfully.
Debug 05/17/10 5:46:04:0732 PM ( 1274098564732 ) T:main REL RELDriver
1:idcocci1:UnknownProgramName:0:main:1:1274098564:0
Starting the database load...
Error 05/17/10 5:46:04:0939 PM ( 1274098564939 ) T:main REL IREL
1:idcocci1:UnknownProgramName:0:main:1:1274098564:0
ORA-00972: identifier is too long

Debug 05/17/10 5:46:04:0946 PM ( 1274098564946 ) T:main REL
RELSessionStatHandler 1:idcocci1:UnknownProgramName:0:main:1:1274098564:0
Updating the batch status from: 64 to: 1 (LOAD_ERROR)

 

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