BC Calling an Extra Search Even Though Earlier Search Query Returned Rows < MAX_ROW

(Doc ID 2384658.1)

Last updated on APRIL 16, 2018

Applies to:

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

Symptoms

On : 7.5.0.17.0 version, Customer Care

ACTUAL BEHAVIOR
--------------------
Searching account by giving wild characters on first name, Billing Care (BC) will fetch the result set from the DB and display the same in Search window.
Looks like BC is internally calling an extra search even though earlier search query returned rows < MAX_ROW.

EXPECTED BEHAVIOR
-----------------------
Second search should not have been called while first search result itself does not return MAX_ROW.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Configure account search limit to 50 and pagination.size to 50
2. Make sure only 40 rows are present in the DB
3. Do an account search from BC, by giving wild characters on first name

 

Cause

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