Changing Ui.search.queryBehavior=4 Impacting Cpu Utilization (Doc ID 2205174.1)

Last updated on AUGUST 07, 2024

Applies to:

Symptoms

Updating ui.search.queryBehavior=4 is firing extra sql to get count of the records before fetching actual data, and leading to high cpu utilization.

  Elapsed Elapsed Time
  Time (s) Executions per Exec (s) %Total %CPU %IO SQL Id
---------------- -------------- ------------- ------ ------ ------ -------------
  7,188.5 580 12.39 20.5 93.0 .0 cbb632w09v4xw  Module: JDBC Thin Client SELECT COUNT(ENTITYID) FROM Service WHERE ((UPPER(NAME) LIKE :1 ESCAPE :2 AND(ENTITYCLASS = :3 )) AND (ROWNUM < :4 ))

  992.1 8 124.01 2.8 9.5 89.7 4qpyd6tq91fu7         Module: JDBC Thin Client SELECT COUNT(ENTITYID) FROM Service WHERE ((UPPER(ID) LIKE :1 ESCAPE :2 AND (ENTITYCLASS = :3 )) AND (ROWNUM < :4 ))

  652.1 3 217.36 1.9 9.5 91.4 87dxkn09akhgd       Module: JDBC Thin Client SELECT COUNT(ENTITYID) FROM Service WHERE (((UPPER(ID) LIKE :1 ESCAPE :2 AND (SPECIFICATION = :3 )) AND (ENTITYCLASS = :4 )) AND (ROWNUM < :5 ))

Changes

Cause

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