Last updated on FEBRUARY 05, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.5.0]
Information in this document applies to any platform.
When number of bill is more than fetch_size, 1st time sql goes with >1, and it works fine, but for 2nd set of fetch, it goes with condition "poid_id0 ><last_poid_from_first_fetch>" so for this sql the SQL profile
"BILL_TPROFILE" is NOT getting attached hence it will do full table scan and t takes more time.
In another issue Oracle suggested to increase the fetch_size such that 'fetch_size' is larger than the total number of bills, but now number of bills are getting increased, so CANNOT keep changing the fetch_size.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms