DOA issues with 9i upgrade

[Patrick Newport]

We just converted the database from 8i to 9i over the weekend and are experiencing issues with one of our DOA applications using doa34d7. The error message is "Access violation at address 00000000. Read of address 00000000".

This seems to occur at random times and for random users, but always when doing an operation which would access the DOA component. This requires the user to restart the application. Are there any work arounds for this?

 

[Bernhard Geyer]

DOA Version 4.0.6.0?

 

[Patrick Newport]

We are experiencing the same problem with 9.2.0.8.0 PLSQL Developer. Typically, I can run 3 or 4 queries before it shuts down with the access violation. For our DOA apps, the components are 4.0.7.1.

 

[Marco Kalter]

For PL/SQL Developer you can fix this by using 7.1, or by adding the NoQueryOptimize parameter in 6.0.6 or 7.0.x:

"C:\Program Files\PLSQL Developer\plsqldev.exe" NoQueryOptimize

A similar solution applies to Direct Oracle Access. You need to disable the Optimize property of TOracleDataSet and TOracleQuery components, or (in 4.0.7) set the global NoQueryOptimize variable to True.