The Character "\n" (Newline) For An Input CDR Is Not Identified. (Doc ID 727673.1)

Last updated on JULY 15, 2011

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.0.0.0 and later   [Release: 7.3.0 and later ]
Information in this document applies to any platform.
Checked for relevance on 15-JUL-2011

Goal

An optional field e.g. "CALL_TYPE_INDICATOR" is required for the input CDRs and added to the descriptor files. When passing the CDR file into the pipeline, the CDRs were rejected.

It was found that the character "\n" was not used as a separate for the CDRs but read as part of data (the starting of second CDR was be read as the last field of first CDR, the system will continue to read the remaining part of second CDR and all following CDRs were read incorrectly).

The record type was defined as FIX.

Solution

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