The rejected row logging feature allows you to save a copy of the source row that caused a failure on a target. When running a DTS file, any row that is not accepted by the target is a rejected, or failed, row. Rejected rows automatically log an error in the transaction errors table of the Scribe Internal Database. The error itself is always logged, you can additionally log the actual rejected data row. In general, rows are rejected for the following reasons:
Use the Rejected Rows tab in the DTS Settings dialog box to create a table containing the failed rows that can help you determine the cause of the error. If you have linking or formatting errors, correct them.
Other causes for rejected rows may be:
Be sure to investigate rejected rows to determine why they are failing. Note that some rows may be reject for valid reasons.
When the job is run, the step related to those rows will be rejected.
When the job is run, all steps related to the target table will be rejected.
Solution: Define a link for the target field and run the rejected row table/file.
| Note: |
|
See also