Printable View
Just give commit after the whole operation...it's faster and better. As for the bad record, check the spool/log file and remove them from the source.Quote:
Originally posted by bang_dba
If i have 100 inserts to be done, and there is a error at 50 th record, then the control jumps to Exception. Right ????
Is there any way that i just skip this bad record and continue with the rest 50 records ????
A link to an example at Tom Kyte's website, here
For the inserts, try convert the records to a text file
and use loader to insert.
See the bad file.
THis is the way We are working for inserts.
What benefits did you see in this method? It seems a little complex.Quote:
Originally posted by engiri
For the inserts, try convert the records to a text file
and use loader to insert.
See the bad file.
THis is the way We are working for inserts.
We find the error data and try to avoid the same at the source of the record.
Thanks
It will be a stupid method ...
Well how abt capturing the ROWID and Table_Name in an ERR_TABLE ( In the exception handling part ) ??
My example is not exactly fitting, but the automated
way helped the requirement of our client.
We have to upload data from one of our client who is running Tally,
and part of the data from his oracle database.
We convert the same to text file and load the same to Oracle.
We will load the same into a temporary table and convert the successful records to the main database, error records to another table, find and troubleshoot the errors and again
load the same to the main database.
This automation works fine (Only for inserts).