Performance Issue Due To C1-PERHIC Post Processing Base Algorithm On C1_PERSON_BO
(Doc ID 2700259.1)
Last updated on AUGUST 14, 2020
Applies to:Oracle Financial Services Revenue Management and Billing - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
A performance issue occurs while running C1-FTRAN batches to upload static data of FRTs referring person BO (Hierarchy upload).
The C1-FTRAN batch was started to upload parent-child hierarchy data (1 record in the file result in 1 entry ci_per_per) which had around 10K+ records in the file. The batch ran for hours (around 8 hours 30 mins) before it went into 'ERROR'.
1. From the AWR report the following was determined:
a) It shows Row Lock Contention for the CI_PER table.
b) There are hundreds of millions of executions on the Construct related tables.
The Construct evaluation algorithm needs to be checked for unwanted SQL loops and performance. This needs to be fixed.
As an experiment, the C1-FTRAN batch was started for a hierarchy file after de-activating the C1-PERHIC post processing base algorithm on C1_PERSON_BO. This batch was completed in a few minutes.
2. From the batch run tree for some of the records on certain threads it went into concurrency error, with error message as 'Concurrency Error. Another user updated this data while you were making your changes. Please try this transaction again.' To check this, we had tested the scenario on where we created 10 records having the same parent person but different child persons. It successfully ran on 10 threads without any concurrency errors. In the case of duplicate records it throws a different data specific error as well.
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