DML error table intermittently fails to generate error handling in package

Question

Hi!
In OWB 11gR2 (11.2.0.1), we're seeing an issue when setting the DML Error table name on a target table. Sometimes, mostly on older and complex mappings, the error handling logic does not get generated when we deploy the mapping, and nothing is populated in the error tables for error conditions, though the errors display as warnings in the OWB UI.
When I create a new mapping that is very simple - one table loading another - setting the DML Error table name always results in errors being put in the error table. That's great, but that doesn't help us with our more-complex mappings that aren't logging errors.
We can't determine the cause of the issue. I can't see a difference in the configuration of the mappings that work and don't work. Generation Mode is All Operating Modes. Default Operating Mode is Set based fail over to row based. We've generated the error table using DBMS_ERRLOG.CREATE_ERROR_LOG. The target tables do not have primary keys.
I've tried synchronizing the target table operator in the mapping as another forum thread suggested. No change.
Has anyone else seen this issue or know of a workaround?
Thanks,
Jayce

Answer 1

Which logic did you talk about ?
For the version 10, you will find the error table more on the insert statement such as:
INSERT INTO "TSALES"
  ("PROD_ID",
  "SALES"."AMOUNT_SOLD" "AMOUNT_SOLD"
FROM
  "SALES"  "SALES"
LOG ERRORS INTO TSALES_ERR (get_audit_detail_id) REJECT LIMIT 50;Come from here:
http://blogs.oracle.com/warehousebuilder/2007/08/set_based_errors_dml_error_log.html
Then check the insert SQL generated.
Cheers
Nico