Hi Pavan,
It is not an easy job to find out where is coming a performance issue.
In 18.1 the first occurence of SWWWIHEAD has very high I/O but it has been executed only 32 times.
It may be a job. Very probably you have too much entries on that table which is not normal or there is a bug in the program and it is now using the best path to access the data.
How Many entries you have in this table?
Did you check in Se11 that SWWWIHEAD has an index with CLIENT WI_TYPE WI_STAT WF_TYPE?
If not try to use DB05 to see what field should be enough to have a good index.
Can you confirm your DB and PI version?
Could you confirm the different indexes on that table?
A screenshot will be better.
Specially Index C as per note 881187.
Note 1024505 is talking about report RSWWCOND (background job SWWCOND).
Where you able to drill down the issue to that program?
The note is pretty old.
Are you familiar with STAD?
Can you run it just after the job ends?
Let s say the job finished at 11:06.
You run STAD on the user and program at 11:00 for 10mns
Regards,
Adel