I have a strange an tricky problem with my Hibernate application. I have a table where I collect about 20.000 rows a day of data. Every row has a timestamp (in the form of a DATE column in Oracle), and every once and again (approx. once a week) the timestamp gets corrupted. Sometimes the year part of the date is set to 0001, somtimes the day is 00, and so on.

I know for sure that the timestamp is valid when entering the hibernate save() method. For some reason Oracle doesn't reject these invalid date, but stores them without any warning. This causes problems later on, where the data is read in another application.

Has anybody else seen this problem? Does anybody have a suggestion as to what's causing it, and/or what we can do to fix it?