Last updated on OCTOBER 12, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Payments
Customer have some large accts that are timing out while applying payments. Customer have investigated and identified a few queries that are OOB and run long. Payment tool is timing out, leading to duplicate payments by Finance when they see the error and don't realize that back end still applies the payment even though there is a timeout on the front end. The large accounts in the system can take around 30 mins to apply. While user have increased timeouts now to apply the payments, find that some OOB queries can be reviewed for improving performance.
The runtime in the “queries” tab is a more realistic case where the blocks are not cached in the db or san. Runtimes in PoC are post-buffer cache flush but SAN caching was in play, thus the significantly faster runtime.
• ITEM and BILLINFO are partitioned HASH(POID_ID0), 32 and 8 respectively) to mitigate concurrency issues with billing. Yes this costs us a bit on these selects, but the sub-second impact is inconsequential in comparison to 10’s or 100’s of seconds of runtime.
The OOB code changes prescribed should be assessed and implemented to allow us and other customers to achieve better performance.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms