0

I am using external table for ETL. The access driver creates a bad file which contains records which were bad in some way like data type mismatch. However, constraint violations like unique constraint violation are not written to Bad file by access driver and thus have to be handled in the loading process from external table and put into some other bad file created for this second part of load process. Please suggest some good design to merge these two bad files or handle bad data in a unified way.

user2599052
  • 1,056
  • 3
  • 12
  • 27
  • 1
    What "unique constraint" are you referencing? So far as I'm aware, you cannot define a constraint on an external table. Are you talking about errors that occur when you extract data from the external table and write it to a permanent table? – Justin Cave Aug 25 '14 at 18:46
  • @JustinCave - Yes, I am referring to constraint violations that might occur when load it to the permanent table. – user2599052 Aug 26 '14 at 04:23

0 Answers0