Ora 10G client failure on Ref Cursor Stored Proc

[JamesEricAndy]

I've been succesfully calling a Stored Procedure thru DOA 4.0.7 that returns a "Reference Cursor" using Oracle 8i client against both an Oracle 9 & Oracle 10 database. When we replaced the Oracle 8i Client with the Oracle 10g client, the Oracle client generated the following exception on the Stored Proc call:
"Access violation at address 61017D43 in module 'oracommon10.dll'. Read of address 00000094

 

[Marco Kalter]

Does this happen on the 10g database or 9i database or both?

 

[JamesEricAndy]

We have NOT tested the oracle 10g client against the 9i database.
However, I am now able to call the previously failing Stored procedure by turning off the following property on the TOracleSession:
"StatementCache=False".

Setting it to True works fine with the Oracle 8 client against either the Oracle 9 or Oracle 10 database, but fails against the oracle 10g client. I'm convinced this is NOT your bug, but is Oracle's bug. Will you coordinate this problem with Oracle?

 

[Marco Kalter]

I will try to reproduce this.

 

[Helene]

I had the same problem, and setting statementcache to false solved it. However I would not like to change this property. Is there any news about this?

Is it possible to set statementcache to false only before executing the particular query, and then reset it to true? What will be the consequences of doing this?

With regards, Helene

 

[Marco Kalter]

I had the same problem, and setting statementcache to false solved it. However I would not like to change this property. Is there any news about this?

No, we have not been able to reproduce this.

Is it possible to set statementcache to false only before executing the particular query, and then reset it to true? What will be the consequences of doing this?

It should be possible. The consequences are than only this statement will be places in the client side statement cache.