I am working on transferring data from the old system to our new application (works in Oracle Database, 10gR2). As part of the migration, I am working on a script that inserts data into tables that are used by the application.
The number of rows of imported data in thousands, and the original data is not clean (unexpected zeros in NOT NULL columns, etc.). Therefore, inserting data through scripts, whenever such an exception occurs, the script ends abruptly, and the entire transaction is rolled back.
Is there a way in which I can continue to insert data for which the rows are clean? Using NVL()or is COALESCE()not a parameter, as I would like to log lines causing errors so that the data can be corrected for the next pass.
EDIT: my current procedure has an exception handler, I register the first line that causes an error. It would be possible for the inserts to continue without interruption, because right now in the first exception thrown, the procedure ends.
source
share