Hi Team ,
A single session which was normally runnning till last run is suddenly getting delayed by moving to responding state.
The session comprises of
set query band
update statement (around 8000 similiar update statements)
Now in the current run, only few similar update statements are running and moving to responding state.ET is not getting logged in the log table.
It is quite suprising to see the issue.
It would be unusual for an UPDATE to remain in 'responding' state for any measurable length of time. An UPDATE would not normally return any data (unless possibly there were Identity column values involved but not even sure that is correct).
On your 'current' run, arr those UPDATes that have completed showing a long time being blocked, or held on a TASM delay queue?