REL Is Not Rolling Back The Partial Loaded Records When Load Error Happens During Sqlloader Stage (Doc ID 1612088.1)

Last updated on JULY 27, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Symptoms

REL is not rolling back the partial loaded records when load error happens during sqlloader stage - The expected behavior as per the product documentation is to rollback the partially loaded records for that REL session, whenever the error happens at loading stage. As per debug REL logs, one can notice that the DELETE SQL statements are being prepared but the same are not being triggered and not executed.

Reproduction steps :

 1. created an account with a GSM service.
 2. Rated a CDR file with 3 records.
 3. Modified one of the record fields (in the out file), say the size of the /service poid value in the event_t table to be greater than the column size.
 4. Load the modified out file.
 5. See the error in the rel.pinlog.
 6. Also once could see partial records loaded to some tables.

 Error 12/03/13 2:04:49:0097 PM ( 1386047089097 )  T:main IPTVREL IREL 1:dev:UnknownProgramName:0:main:1:1386047085:0
    Error encountered in the Database Load Utility: 5002
An unexpected error has been encountered by the database load utility.
Please examine the generated *.blk.log files for the input file: test_prod_rel3.rel
Error 12/03/13 2:04:49:0097 PM ( 1386047089097 )  T:main IPTVREL IREL 1:dev:UnknownProgramName:0:main:1:1386047085:0
    Exiting with return code: 5

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