Segmentation Violation On CANCEL_DEAL (Doc ID 2886259.1)

Last updated on AUGUST 04, 2022

Applies to:

Symptoms

The issue can be reproduced at will with the following steps:

To reproduce the problem, please follow the following steps:

  - 27/01: Customer subscription with an offer with ACTG_DOM_CYCLE set to 27 (Run a make bill now to generate an immediate bill)
  - 01/02: Billing (pin_bill_acct) and invoicing (Generate first invoice)
  - 27/02: Part 1 of billing (pin_bill_acct)
  - 01/03: end of billing (pin_bill_acct) and invoicing
  - First, change the offer of customer (CANCEL DEAL of old deal and PURCHASE_DEAL of new deal). This step trigger an auto-billing (1st part of billing) on the customer
  - In a second time, we purchase a discount (PURCHASE_DEAL)
  - Finally, cancel the discount with the effective start date equal to the effective end date (BILLING DAY) (CANCEL DEAL) because it won't bill this discount.
There are two pin_bill_acct for  billing operation because of using use delay billing
During the cancel deal, memory leak issue is encounter after a PIN_ERR_NULL_PTR on a READ_FLDS.

ACTUAL BEHAVIOR
---------------
During the cancel deal, we have a memory leak after a PIN_ERR_NULL_PTR on a READ_FLDS.

EXPECTED BEHAVIOR
-----------------------
No memory leak issue is expected

Cause

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