Skip to Content
0
Former Member
Dec 30, 2014 at 09:40 AM

Expensive SQL statements in PI 7.3 For The Object SWWWIHEAD

89 Views

Hi All,

I am receiving high expensive SQL statements alerts for the object SWWWIHEAD in EWA report continuously in one of our PI 7.3 box,

I have checked the SQL statement which is using more I/0 (40 %) and CPU (2%), below is the select statement which it's using. Can you please let me know me know the possible root cause for the issue and also any issue in the below query ? I have gone through few notes 881187 & 1024505 but those are not helping to tune this performance issue, as per the note 881187 the indexes for the table already exist in our system.

Please let me know if you need more logs or information on the same.

SQL Statemet:

SELECT

"WI_ID"

FROM

"SWWWIHEAD"

WHERE

"CLIENT"= :A0 AND "WI_TYPE"= :A1 AND "WI_STAT" IN ( :A2, :A3) AND "WF_TYPE"= :A4

Execution Plan From: V$SQL_PLAN sql_id: dqsaj4vn26r31

SELECT STATEMENT Estimated Costs= 19.803 Estimated Rows= 0

Optimizer: ALL_ROWS

3 INLIST ITERATOR

2 TABLE ACCESS BY INDEX ROWID SWWWIHEAD

Estimated Costs= 19.803 Estimated Rows= 288.498

Filter predicates: "WF_TYPE"=:A4

Estim. Bytes: 9.808.932

Estim. CPU-Costs = 214.099.156 Estim. IO-Costs = 19.768

1 INDEX RANGE SCAN SWWWIHEAD~C

Estimated Costs= 529 Estimated Rows= 288.498

Access predicates:

"CLIENT"=:A0 AND "WI_TYPE"=:A1 AND (("WI_STAT"=:A2 OR "WI_STAT"=:A3))

Search Columns: 3

Estim. CPU-Costs = 15.602.140 Estim. IO-Costs = 527

Attachments