Unanswered: db2expln stops on first non-valid statement
I have captured a large volume of work from a client site, which represents several days of production processing. I'd like to get some sort of benchmark set of access paths for this workload but, unfortunately, there is an amount of clean-up processing done as part of the standard processing. This means that some of the statements refer to objects that no longer exist. If I run db2expln against this full set of statements it will fail SQL0204 on the first statement which is invalid and not proceed any further. Is there any way to persuade db2expln to record the failures but just carry on to the next statement(s)?