Page 2 of 2

Re: job is running too long

PostPosted: Wed Oct 26, 2011 2:01 am
by BrantleyL1
Two thoughts...

1) That appears to be a SERIOUS (it said so) DASD error. I suspect that the DASD may have been failing and it kept trying to write it. I would have your operations folks look at that. May need to back up/reload to a different pack.

2) My first thought was "when was the last time a RUNSTATS was run on that table?" But the first thought is likely the cause of the problem.