PIN_REL Rejecting Input File
Last updated on MAY 26, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.3.0]
Information in this document applies to any platform.
Checked for relevance on 30-Nov-2011.
Checked for relevance on 26-May-2017.
Pin_rel is rejecting whole input file when it contains rated EDR/EDRs with an error. File is correctly broken down into .blk files, processed by SQL Loader utility. The SQL Loader utility identifies several records, which contain a wrong value (e.g.: string (null) in a integer type field) and rejects these. The observed behavior is that no records at all are loaded from a file which contains wrong EDRs. No information about "transaction" like behavior of the pin_rel as a whole was found in the BRM documentation
1. Is pin_rel utility handling input files in a single transaction, which results in a rollback if any of the SQL loader threads fails ?
2. Is the observed and above described functionality correct?
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