Hi Ricardo,
Resurrecting a 2.5 year old thread here, but I just became aware that we're
having the same problem (with an obviously infrequently-used feature).
Did you ever learn anything more about this? Did setting that
oracle.jdbc.LobStreamPosStandardCompliant property result in any strange
Spoke too soon there was a followup thread, 4 months later with Subject:
oracle.jdbc.LobStreamPosStandardCompliant. See:
http://lists.apple.com/archives/webobjects-dev/2010/Sep/msg00548.html
Thanks, Mike... 2.25 years later. :-)
- Patrick
On Dec 20, 2012, at 3:00 PM, Patrick Robinson
We upgraded ORACLE to 11g and so I switched to the 11g driver. But now we
started getting these exceptions:
[2010-05-11 07:31:24,579] ERROR
com.webobjects.eoaccess.EOGeneralAdaptorException: Invalid argument(s) in call
at
On May 11, 2010, at 8:57 AM, Ricardo J. Parada wrote:
We upgraded ORACLE to 11g and so I switched to the 11g driver. But
now we started getting these exceptions:
[2010-05-11 07:31:24,579] ERROR
com.webobjects.eoaccess.EOGeneralAdaptorException: Invalid
argument(s) in call
at
On May 11, 2010, at 1:34 PM, Chuck Hill wrote:
On May 11, 2010, at 8:57 AM, Ricardo J. Parada wrote:
We upgraded ORACLE to 11g and so I switched to the 11g driver. But now we
started getting these exceptions:
[2010-05-11 07:31:24,579] ERROR
To simplify things, in a nutshell, the new oracle 11g driver has this logic:
if (pos == 518630185893888L)
{
if (lobStreamPosStandardCompliant)
{
throw
DatabaseError.createSqlException(getConnectionDuringExceptionHandling(), 68);
}
...
