Since we had a problem with this row , we updated it and I do not have the value in date_ouverture which gave a problem.
However , we identified the source of the problem.
This value was updated using java.
The value which was entered was 27/01/20055.
What I do not unterstand is that Oracle found a way to enter the value in the colum but can not make any operation on it.
But still, I'm very curious what that dump shows - what is the content of the date column's 7 bytes? Can you please execute the command that gamyers provided in SQL*Plus and copy-paste the result here?
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
But still, I'm very curious what that dump shows - what is the content of the date column's 7 bytes? Can you please execute the command that gamyers provided in SQL*Plus and copy-paste the result here?
Something does not mach here! You said the date enetered was something like '27/01/20055' and that query on that value returned '27/01/5555'. However your dump shows a perfectly normal date that does not match any of those two - it represents the date 17/02/2004 00:00:00 (dd/mm/yyyy hh24:mi:ss). So neither the day nor month portion match any of your quoted dates and the year in this dump is perfectly normal 2004. !?
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
Bookmarks