Product Commit Failing in BRM With an Error Which Gets Resolved by Restarting CM
(Doc ID 2687815.1)
Last updated on JULY 13, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On Billing and Revenue Management (BRM) 18.104.22.168.0 version, when configuring a new provisioning tag, a new product referring the new tag cannot be committed to BRM database. The transaction is aborted and following lines are logged in cm.pinlog:
The same problem occurs whether Pricing Center or PCM_OP_PRICE_SET_PRICE_LIST opcode or loadpricelist utility is used for committing the new product. It is to be noted however that if Connection Manager (CM) is restarted, the error does not occur anymore.
This is happening in an environment in which provisioning tags are stored in a custom class, and PCM_OP_CREATE_OBJ opcode is used to create new entries into this class. The Policy hook for provisioning in fm_subscription_pol_provisioning.c has been modified to read the provisioning tag from the custom class.
The issue can be reproduced at will with the following steps:
1) Provisioning Tag is Created using PCM_OP_CREATE_OBJ opcode.
2) Use PCM_OP_PRICE_SET_PRICE_LIST opcode or Pricing Center or LoadPriceList utility to commit the Product but it fails with error "Transaction is aborted".
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