|
Re: External tables with DML Error logging feature in 10g [message #146960 is a reply to message #146905] |
Mon, 14 November 2005 22:00 |
rleishman
Messages: 3728 Registered: October 2005 Location: Melbourne, Australia
|
Senior Member |
|
|
Great idea, well spotted.
We're developing a warehouse on 10.1 so have not used the Error Logging clause. It looks great though.
I can't see any reason why you could not combine EOTs and Error Logging. Remember though, rows that do not meet the SQL*Loader format spec in the EOT will be logged to the EOT Log file, not to the DML Error table.
There is nothing in the doco to suggest that DML Error Logging is incompatible with Direct-Path load, but it would be worth a bit of experimentation. Certainly you cannot have triggers enabled for direct-path load, so DML Error Logging won't catch these. Be interesting to see what it does with constraint violations, most of which are validated AFTER the direct-path load is complete.
Good luck. Tell us how it goes.
_____________
Ross Leishman
|
|
|
Re: External tables with DML Error logging feature in 10g [message #147076 is a reply to message #146905] |
Tue, 15 November 2005 12:51 |
smartin
Messages: 1803 Registered: March 2005 Location: Jacksonville, Florida
|
Senior Member |
|
|
I like the idea as well, and would guess there is nothing to prevent it. BUT, as Ross pointed out, I'm not sure the OP needs to go this route. The logs created by either sql loader or external tables would identify those problem rows, which is my guess as to the goal of the OP.
|
|
|