My Oracle Support Banner

Transaction Committed After Opcode Error (Doc ID 2680756.1)

Last updated on SEPTEMBER 07, 2020

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.18.0 and later
Information in this document applies to any platform.

Symptoms

When an operation in Billing and Revenue Management (BRM) opcode fails and exits, the code is setting up the error buffer (errorBuf), the commit is received from the transaction owner Application Integration Architecture (AIA) and/or Java EE Connector Architecture (JCA).

This has been observed in adjustment opcodes and has been "partially" worked-around by invoking TRANS_ABORT instead of setting the errorBuf, which is the standard way to exit with error from an opcode.

AIA is configured as Out of Box. For most of the opcodes, it handles the transaction closure OK (with its corresponding Commit/Rollback). But, for the case of adjustment, for some reason, it is not behaving as expected.

The expected behavior is that when errorBuf is set, a Rollback has to be sent to BRM in order to abort and not persist data.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.