Is it possible to catch a DB error and avoid an interation to stop

[Anonymous]

Hi,
I have the following job, where I am iterating on a table list to read data from each table.
Sometimes, the select statement throws an Exception, which I would like to handle and continue iterating on the other tables.
The "OnComponentError" trigger doesn't answer the problem because the the processing will continue on that trigger branch but the iteration is aborted.
Do we have a solution to error catching in DB components ? How would you implement such a demand ?
Thanks 

[Anonymous]

Hello Hideki-san
You could put the database processing and the error handling snippet inside a child job and then clear the die on error message.  I think that would allow you to continue processing.
Ed