Why So Many SQL Statements On bal_grp_sub_bals_t Table?

(Doc ID 1545267.1)

Last updated on JANUARY 02, 2018

Applies to:

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


Why these SQL selects are executed so many times? Expresions look like came from BRM rating engine.

1. select rec_id, current_bal from bal_grp_sub_bals_t where bal_grp_sub_bals_t.current_bal <> :1 AND obj_id0 = :2 and rec_id2 = :3

Executing about 10000 times per second.

2. select bal_grp_sub_bals_t.rec_id, bal_grp_sub_bals_t.rec_id2, bal_grp_sub_bals_t.contributor, bal_grp_sub_bals_t.valid_to, bal_grp_sub_bals_t.valid_to_details, bal_grp_sub_bals_t.valid_from, bal_grp_sub_bals_t.valid_from_details, bal_grp_sub_bals_t.current_bal, bal_grp_sub_bals_t.next_bal, bal_grp_sub_bals_t.delayed_bal, bal_grp_sub_bals_t.rollover_data, bal_grp_sub_bals_t.grantor_obj_DB, bal_grp_sub_bals_t.grantor_obj_ID0, bal_grp_sub_bals_t.grantor_obj_TYPE, bal_grp_sub_bals_t.grantor_obj_REV
from bal_grp_sub_bals_t
where bal_grp_sub_bals_t.obj_id0 = :1 and ( bal_grp_sub_bals_t.valid_to = :2 or bal_grp_sub_bals_t.valid_to >= :3 or bal_grp_sub_bals_t.valid_to IS NULL ) order by bal_grp_sub_bals_t.rec_id

Executing 300 times per second.


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