TRANS_ALREADY_OPEN Error In Multi-schema Setup

(Doc ID 1540493.1)

Last updated on APRIL 25, 2016

Applies to:

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

Symptoms

On : BRM 7.4.0.0.0 version :

On a multi-schema enabled system, when one opens a context and opens a transaction, and later close the context without aborting or committing the transaction and later tries to open a new transaction on the same object, TRANS_ALREADY_OPEN error is thrown.

Steps to reproduce:

> testnap
===> database 0.0.0.1 from pin.conf "userid"
nap(25266)> open lock - 0.0.0.2 /balance_group 1
nap(25266)> q
> testnap
===> database 0.0.0.1 from pin.conf "userid"
nap(25274)> open lock - 0.0.0.2 /balance_group 1
PCM_OP_TRANS_OPEN failed: err 37:PIN_ERR_TRANS_ALREADY_OPEN, field
0/1777:PIN_FLD_OP_SQL_TRACE,
        loc 4:PIN_ERRLOC_DM, errclass 1:PIN_ERRCLASS_SYSTEM_DETERMINATE,
rec_id 0, resvd 200
nap(25274)>


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