The Parsing EP Writes Out A Huge Number Of Bad CDR's

(Doc ID 744244.1)

Last updated on SEPTEMBER 23, 2016

Applies to:

Oracle Communications Network Mediation - Version: 5.1.1
This problem can occur on any platform.


We have seen in the past that undecodeable CDRs get sent to the CGF and normally the GTP Parsing EP writes out this CDR as Bad CDR in it's scratch-directory and all following CDRs are processed correctly.

However, now we have the problem that one of these Bad CDRs causes a massive fault in the GTP Parsing EP.

All CDRs which where processed directly after a Bad CDR are also issued as Bad CDRs (even though these CDRs are ok),
This behaviour persists, until the GTP Parsing EP had been stopped and restarted.
Then the GTP Parsing EP decoded all further CDRs correct.

During this fault, the GTP Parsing EP wrote allways the same error in the log file:-

Major; Invalid Data; Decode Fail : decoder wrong; Cannot decode CDR: null#EOR#


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