My Oracle Support Banner

PCM_OP_SUBSCRIPTION_TRANSITION_PLAN Throws Signal 11 when Error Returned During Event Notification (Doc ID 2861645.1)

Last updated on APRIL 13, 2022

Applies to:

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


On Oracle Communications Billing and Revenue Management (BRM), version, Subscription Management

One user has added some deal validations, and the logic to do these deal validations is in a custom opcode which is called during purchase deal and cancel deal event notifications (pin_notify). However, PCM_OP_SUBSCRIPTION_TRANSITION_PLAN threw signal 11 during billing when such deal validations with schedule object failed.

From the cm.pinlog, it appears that Signal 11 is thrown during pin_flist_destroy operation in fm_subs_transition_plan_cancel_deal function of PCM_OP_SUBSCRIPTION_TRANSITION_PLAN opcode.


Here it is expected that the schedule object is supposed to error out without signal 11.

The issue can be reproduced at will with the following steps:
1. On BRM Version, using pin_notify to call a custom opcode with deal validation which gives a dirty ebufp.
2. PCM_OP_ACT_USAGE also fails due to dirty ebufp.
3. Verify if PCM_OP_SUBSCRIPTION_TRANSITION_PLAN throws Signal 11 while destroying an flist.


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

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