My Oracle Support Banner

Pin_mass_refund Performance Degrades After Upgrading To 7.5 PS22 (Doc ID 2558995.1)

Last updated on SEPTEMBER 27, 2019

Applies to:

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

Symptoms

On : 7.5.0.22.0 version, Accounts Receivable (AR)

ISSUE
---------------

Customer found sql query running as part of pin_mass_refund has changed post upgrade to Oracle Communications Billing and Revenue Management (BRM) 7.5 Patchset22. This is resulting in the query going for a full table scan on billinfo_t.

Old query :

 
STEPS
-----------------------
1. Running the billing jobs in following order-

pin_bill_accts_10007
pin_bill_accts
pin_mass_refund_10003
pin_mass_refund_10005
pin_inv_accts_10001
pin_inv_accts_10003
pin_inv_accts_10005
pin_cycle_fees_cycle_fees
pin_cycle_fees_purchase
pin_cycle_fees_cancel

2. pin_mass_refund with below syntax:

pin_mass_refund -active -pay_type 10003 -verbose
pin_mass_refund -inactive -pay_type 10003 -verbose
pin_mass_refund -close -pay_type 10003 -verbose

3. Same steps repeat for paytype 10005.

==============================
mta configuration for pin_mass_refund

- pin_mass_refund children 5
- pin_mass_refund per_batch 1000
- pin_mass_refund fetch_size 50000

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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