3) Load all the records in the staging table and create ERROR TABLE for the final table capturing the errors in the INSERT SELECT (LOGGING ERRORS clause).
OK carlos.. But still if we use the LOGGING Errors Clause, it would just capture the errocodes,
our requirement is to capture the complete copy of the errorneous records and build the views on top of those
error table so that these are available to users for investigation..
. is it feasible with LOGGING errors clause?
For Solution 1:
Use "DISPLAY_ERRORS" and NOSTOP feature of TPump to show the error record in console output and proceed with the job processing without TPump to stop.