ora-24909 call in progress. Current operation cancelled.

[Ruudbern]

Hi,

After we switched to a new oracle version (Oracle 10.2.0.4 64 bits) we get ora-24909 errors in our delphi/doa applications.

I found some old post regarding 24909 but there it says that this was an oracle bug fixed in 10.2.0.2.

Is setting the optimize to false stil the (only) way to go? I don't want to slow down the applications if it is not absolutly necesary.

Kind Regards Ruud

 

[Marco Kalter]

What is your Direct Oracle Access version?

Setting Optimize to False is indeed the only option.

 

[Ruudbern]

We are (still) using 4.0.6.2.

 

[Marco Kalter]

Okay. In that case you need to set Optimize to False for all TOracleQuery and TOracleDataSet instances.

 

[Ruudbern]

Thanks for the quick response.

 

[Ruudbern]

Hi Marco,

we tested this but the problem stays the same. We have been able to capture this in oracle monitor in an other application (optimize = true). What we see is that there are 2 red marked statements in oracle monitor.

The second one is raisign the ora-24909 Call in progress error. The statement prior to this one displays in oracle monitor an access violation at adress 00000000 Read of adress 00000000.

The sql statement which causes the access violation is a simple one:
select subject.*, subject.rowid from subject where sub_id = :sub_id.

Does the adress 00000000 indicate that the error comes from outside our application. In other words the oracle client? Any suggestions how to tackle this?

kind regards

Ruud

 

[Marco Kalter]

These are the exact symptoms of the Optimize issue in 10.2. Can you update to 4.0.7, set Oracle.NoQueryOptimize to True, and try again?

 

[Ruudbern]

Hi Marco,

the clients where not upgraded to 10. The customer was still using 9 clients. They upgraded the clients to 10 yesterday afternoon.....
It looks promissing. Where going to waite a few days.....

to be continued,
thanks for your input again

 

[Marco Kalter]

Note that the issue is not about the client, it's about the server.

 

[Ruudbern]

Strange. The problem is gone. An other company does the support for oracle at that location. They say they only updated the clients....
I am happy....

 

[Marco Kalter]

In that case I am happy too

 

[F.Hinlopen]

Similar situation here. Server version 9.2.0.7.0 updated to 10.2.0.4.0. Application started misbehaving with random ORA-24909. Updating the 9.2 clients was not practical, so I updated the application by setting Optimized = false on all relevant components. No problems for two days, but keeping my fingers crossed.

 

[F.Hinlopen]

No problems for weeks now. The application has a few hundred users, so this has been solved.