My Oracle Support Banner

PIN_REL Does Not Load/Calculate Obj_id0 For Event_* Tables (Doc ID 736371.1)

Last updated on SEPTEMBER 20, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.
Checked for relevance on 01-Jun-2012
Checked for relevance on 20-Dec-2013
***Checked for relevance on 28-November-2015***



Only one CDR can be loaded into BRM Database, then these type of errors are reported in pin_rel.pinlog:

Error 09/02/08 9:30:43:0791 AM ( 1220364043791 ) T:Thread-17 REL RELStreamGobbler 1:brm-test:UnknownProgramName:0:Thread-17:0:1220364043:0 gprs_GPRS_SEP02_14.edr.out.event_dlay_sess_tlcs_t.blk : ORA-26027: unique index
PIN7.I_EVENT_DLAY_SESSION_TLCS__ID partition PARTITION_HISTORIC initially in unusable state
Error 09/02/08 9:30:43:0792 AM ( 1220364043792 ) T:Thread-17 REL RELStreamGobbler 1:brm-test:UnknownProgramName:0:Thread-17:0:1220364043:0
gprs_GPRS_SEP02_14.edr.out.event_dlay_sess_tlcs_t.blk : SQL*Loader-2026: the load was aborted because SQL Loader cannot continue.
Error 09/02/08 9:30:45:0669 AM ( 1220364045669 ) T:main REL IREL 1:brm-test:UnknownProgramName:0:main:7:1220364038:0
Error encountered in the Database Load Utility: 5002

An unexpected error has been encountered by the database load utility.

What is the reason and solution for this type of error?


To view full details, 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 a vibrant support community of peers and Oracle experts.