Service Degradation Occurs When Reversing Commissions.
(Doc ID 2344332.1)
Last updated on MARCH 19, 2019
Applies to:Oracle Insurance Policy Administration J2EE - Version 10.2.0.0 to 10.2.0.29 [Release 10.0]
Information in this document applies to any platform.
Users have a transaction (“Apply Premium”) that processes with no problem, but when that transaction is reversed, it takes approximately to 5 minutes to complete the job.
Monitoring the AsCommissionDetail Table, to process the Apply Premium for the first period, 312 commission records are inserted to the database.
When the reversal for the coverage is processed, then the processed that is triggered contains update statements to 312 commissions, but the CommisionDetailGUIDs for those 312 are repeated 312 times (312*312 = 97,344).
The time to update N^2 records to the database is not perceptible when a low number of AsCommissionDetail records is created by the transaction.
But as the number of commissions inserted by this transaction is considerable, users start perceiving the degradation.
Performance should not degrade at this level as the number of commissions grows.
Steps to Reproduce
1. Go to the application section and process the following activities:
i. Coverage Activation
ii. Generate Billing
iii. Premium Due
iv. Apply Premium
3. Reverse the Coverage Activation activity.
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