Hi Gail,

I did use the latest Oracle driver 12.1.0.2.0. But since even executing the statement Hibernate produces using the PL/SQL client from Oracle returns the wrong values for clazz_0_, I think the cause of the problem may be located in the Oracle cluster that we are forced to use (I have no way to try to reproduce the problem on a standalone Oracle instance as you did).

So if you cannot reproduce the problem, even if you execute the SQL statements directly, this is no Hibernate bug.

Regards,

Olaf