This content has been marked as final. Show 4 replies
Note that for some cases, like an occasional date format constraint violation, the bad file will contain only the failed rows. For the case of key integrity constraints, however, only rows prior to the first failure get inserted into the table and all rows appear in the bad file. At least this is true in the latest production 3.2 release. Functionality may have improved slightly since 3.0, but I did not test the precise behavior.
Using 3.2.20.09.87, when a foreign key error occurs:
1. A new editor tab appears next to the worksheet tab with the title: Import-<csv_file_name>-bad.sql
2. With the the focus on that tab, File -> Save As from the main toolbar shows that it already exists (Windows 7) in directory:
C:\Users\<myuserid>\AppData\Local\TempDistinct preferences exist for each of the import types. For example:
I believe the Generation Directory for the Insert type is what you are looking for. I also notice that 3.0 may freeze in some cases of row insert failure before the bad file's editor tab can appear. Moving to the latest release is highly recommended.
For 3.2.20.09.87 Tools -> Preferences -> Databases -> Utilities -> Import -> Import Methods -> External Table | Insert | SQL Loader For 3.0.x.x Tools -> Preferences -> Databases -> Import -> Import Methods -> External Table | Insert | SQL Loader