Rather than modifying the insert data because of an integrity constraint =
and possible compounding the problem for the next row of data to be =
loaded, why not use the BAD.FILE for the failing rows. Review the failed =
rows for problems and make appropriate correction or inform the owner of =
the data to make corrections. That way everyone will have the correct and =
up to date data if the corrections are made at the source not down stream.
2bits.
ROR
>>> yong321_at_YAHOO.COM 08/24/00 06:35PM >>>
If SQL*Loader can't load a row of data because of integrity constraint
violation, can I ask SQL*Loader to change one value and continue to load =
this
row? I.e., if it can't load "1,John,Doe," because 1 is already taken, can =
it
auto increment 1 to 2 and try loading "2,John,Doe,"? If that fails again,
increment 2 to 3 and try once more.
Yong Huang
yong321_at_yahoo.com=20
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/=20
--=20
Author: yong huang
INET: yong321_at_yahoo.com=20
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Fri Aug 25 2000 - 08:19:26 CDT
