I am loading a csv file to an oracle database using the TUniLoader Component. My file consists of 35000+ rows. I am having occasional issues where the import fails. I would like to provide more feedback as to why it has failed.
I have noticed that the TUniLoader component commits every 100 records. Therefore when an error occurs, it is always in the last 100 records inserted. For example, if the error occurs at line 2150 of the import file, the table will have 2100 rows already inserted and the error row will be anywhere between 2101 and 2200.
I would like to know what line the error occurred on instead of a range of 100 rows. Also knowing the column and data that failed would be helpful. (By failed I mean an oracle error such as formatting or the string is too long.) What is the best way to do this?
TUniLoader Commit
Re: TUniLoader Commit
Hello,
Unfortunately, since data is recorded as blocks, Oracle doesn't return a definite string in a block, where an error occurred, therefore we cannot implement retrieving more detailed information about error origin.
Unfortunately, since data is recorded as blocks, Oracle doesn't return a definite string in a block, where an error occurred, therefore we cannot implement retrieving more detailed information about error origin.
Re: TUniLoader Commit
Is there a way to make that commit block smaller than 100 rows?
Re: TUniLoader Commit
Hello,
If you have the version with source code, we can hint you the place, where this value can be set.
If you have the version with source code, we can hint you the place, where this value can be set.