AIA Orders Are Failing With Error PIN_ERR_TRANS_ALREADY_OPEN in Multi-schema Setup
(Doc ID 1936954.1)
Last updated on JANUARY 24, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and laterInformation in this document applies to any platform.
Goal
In multi-schema setup, a customized Application Integration Architecture (AIA) order is failing with error PIN_ERR_TRANS_ALREADY_OPEN.
Scenario:
- Subscriber accounts are present in multiple schema's (schema_1 and schema_2)
- AIA submits an order that is implemented in a custom opcode on BRM side. The custom opcode calls other OOB BRM opcodes.
- Request is received from JCA.
- JCA is configured for LOCAL_TRANSACTION and parameter MultiDB is set to TRUE
- JCA opens a local transaction on schema1 and fired the request for fetching few details on an account.
- BRM received the request and a global search (READ_OBJ) is performed (as accounts are present on both the schemas)
- Found that account is present in schema_2, so issued a READ_OBJ to fetch the account from schema_2
- Because the transaction is opened (by JCA) on schema_1 , and PCM_OP_READ_OBJ is now performed in schema_2, there is an error PIN_ERR_TRANS_ALREADY_OPEN.
Error snippet in cm pinlog:
Solution
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
Goal |
Solution |
References |