title: Way to log data causing errors in Oracle materialized view?
body: <p>We created some materialized views that ran fine against a copy of actual app data.  The app does not police its own data.  Since then, some of the users may have been either careless or creative in their data entry.  Mview now chokes and dies.  Error messages indicate we are getting multiple rows returned from one or more functions.</p>
  
  <p>We have been trying to use EXCEPTIONS -- with some success at DBMS_Output for the first row object_id that causes (one of) the functions to fail.  It would be better be able to complete a run for the MView, and log the object_ids that cause problems from each function.  We haven't succeeded in inserting the exception data into a table.  </p>
  
  <p>Platform is Oracle 10g2.  I've been trying to cram DML Error Logging into my head.  I understand that this should work for BULK data, and I am assuming that creating a materialized view would qualify.  WOULD this work for MViews?  Is this the best way? </p>