In Price Assignment Search Algorithm Is Taking Lot Of Time & Printing Excessive Info Logs (Doc ID 2926259.1)

Last updated on MARCH 23, 2023

Applies to:

Symptoms

On RMB v4.0.0.0.0, Query in Price Assignment search algorithm is taking lot of time and also printing excessive logger info.

When calling price assignment search algorithm, It is taking a lot of time in executing below query in PricingUtils.java

select acct.acct_id from ci_acct acct where acct.cis_division = :1 and
acct.acct_id in (select anbr.acct_id from ci_acct_nbr anbr where
anbr.acct_nbr_type_cd = :2 and upper(anbr.acct_nbr)= :3);

Also C1-TXNIP Performance Issue and scalability reported in the environment.

On initial analysis, we suspect upper(anbr.acct_nbr) may be the culprit - we do not need to change the case to upper for acct_nbr.

Also in price assignment search algorithm, one query is printed in info logger and increasing logger size in POSTPROC job and in other jobs wherever crawling algorithm is called.
- INFO (com.splwg.ccb.domain.pricing.priceassign.components.DataRetrievalService) End of getPricingSql - Query:

Please advise how to avoid it.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.