We recently upgraded our environment from Websphere 6.1 to Websphere 8.5.
When connecting to a Oracle 11g database through the ojdbc14.jar driver, the value of a Date column ise "0002-11-30 00:00:00",
but when we connect to the same database via the ojdbc6.jar driver, the value of that column becomes "0003-11-30 00:00:00.000".
(It's a weird date, we get that when we parse an 8-zero-string ("00000000") using a SimpleDateFormat in Java. But it's still a valid date.)
other dates don't seem affected, so both date values are the same with both drivers.
My question is, why does the 1.6 driver behave like that; is that a bug ? and how can we / should we rely on that driver ?