sam03489
sam03489
It is a production data so do not think data is corrupted. Why will to_date(to_char()) work and without it, it will not. I added timestamp to your code. 
It does look like a bug to me.
Here you go 
with cx_Oracle package, I am able to make it work using "outputtypehandler" feature but it does not work in Oracledb. It does not even go to DateTimeConverter function. Please note...
If the value stored in the database is corrupted then how are other clients working? (Informatica extracts data using it's native ODBC driver). The fact that TO_CHAR(TO_DATE()) is working makes...
Our organization has license for Oracle Support. If I create a ticket with Oracle support, will it be the right approach? Data definitely is not corrupted as there are millions...
> > with cx_Oracle package, I am able to make it work using "outputtypehandler" feature but it does not work in Oracledb. > > It does not even go to...
It does not even go inside DateTimeConverter, I tried with oracledb.STRING too.
> @sam03489 Did you test the new patch from today? > > I would have quickly tested the handler case, but because you posted a screenshot I couldn't cut and...
> What you may be running into is the fact that thick mode performs the conversion from DATE to STRING internally in the Oracle Client libraries whereas thin mode always...