My program read a ascii file with 1000 records.
I read 100 rows at a time and perform saveOrUpdate on oracle db.
During the commit, i catch an exception.
How can I determine what is the record causing the problem ?

Oracle only tell an error.
HibernateException don't tell me more.

What is your opinion ?

Without the exception code, it would be difficult to say. Can you post it?

Also, it may have something to do with your DB connection on commit, rather than a record on commit. Try reading the first record, and running a saveOrUpdate, and see if you still get the exception. If you do, it's probably not the record.

If you're just trying to debug a specific problem, I would suggest performing the commit after each record and you'll know exactly which one is failing.

I don't want to find the record that cause the error,
I want to find the way to write a error log that exactly identify the records that are wrong.

In this way, my user read the log, find exactly information about the wrong record.
Open the ascii file with an editor.
Correct the problem and then try to import again.

(..sorry for my poor english...)

Not possible. Tom Kyte recently blogged about something that would make it possible: http://tkyte.blogspot.com/2005/07/how-cool-is-this.html

I don't think you'll find too many people here that think having database exceptions thrown and the users looking through logs for errors is a good practice.

What are the possible reasons for exceptions that you can correct ? My assumption is that it has to do with bad data and, in my opinion, data should be validated PRIOR to passing it on to the database.

I must populate a oracle db exporting data from a legacy proprietary database.
The old db must feed the new one in real time.
Technical people must control this batch procedure,
reading logging for failure, and correct the source data.