INSERT fails (java.sql.SQLDataException: ORA-01861: literal does not match format string )because the INSERT statement does have the TO_DATE function applied to the date string in WAS 7 and Oracle 11 g.
INSERT works with ojdbc14.jar in WAS 6 and Oracle 10 g ,because the INSERT statement has the TO_DATE function applied to the date string with 'YYYY-MM-DD' format.
Our recommendation is to use ojdbc14.jar, but IBM recommendation to our client is not use ojdbc14.jar with WAS 7 and Oracle 11 g.
We are using ojdbc14.jar with WAS 6 and Oracle 10 g and also with WAS 7 and Oracle 11 g. This working fine.
*My Question - *
1. Is this recommendation by IBM is valid ?
2. Is there any impact using ojdbc14.jar with WAS 7 and Oracle 11 g.
3. Is there any solution/ work around for above scenario.
For your refernce attach (SQLDataException-ORA-01861.doc)are the sql generated in WAS 6 and WAS 7 environemtns respectively
Notice: We have upgraded developerWorks Community to the latest version of IBM Connections. For more information, read our upgrade FAQ.
Pinned topic Migration issue from ( WAS 6 and Oracle 10 g ) to (WAS 7 and Oracle 11 g ).
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2011-11-08T09:13:21Z at 2011-11-08T09:13:21Z by Wasniel24
Wasniel24 270002PUP72 Posts
Re: Migration issue from ( WAS 6 and Oracle 10 g ) to (WAS 7 and Oracle 11 g ).2011-11-08T09:13:21ZThis is the accepted answer. This is the accepted answer.In order to GPP to work with ojdbc5.jar / ojdbc6.jar, we should add the following JVM parameter:
oracle.jdbc.mapDateToTimestamp with value “false” in WAS console: