You are not logged in.
I notice the different between using tOracleOutput and tOracleOutputBulkExec is that the tOracleOutput doesn't tell you the reason why on the screen it says 100 rows committed to the database but when you go to the database there is fewer records. With tOracleOutputBulkExec, it tells you on the screen how many rows are committed and when you go to the directory where the sqlldr output the files you can see that there is a log file so you can see the reason why there are fewer records and there is a .bad file so you can see which data is bad but off course there is concern about spaces when you use tOracleOutputBulkExec since it creates temp files. Therefor, with smaller table it is more idea to use tOracleOutput but is there a way to tell why there are fewer records committed to the database then what it said on the screen? Is this a bug?
I don't think it's a bug.
The number on the screen shows how many rows have been passed through this rowstruct inner class.
For tOracleOutput, it just executes an insert sql statement simply. There isn't a way to monitor how many rows commit to DB.