Access Violation with Oracle 10g Rel.2 ?

[mla]

Hi,

in our development environment we experience a lot of AV (accessing address 0x0 in most cases) when working with PL/SQL developer against an Oracle 10g 10.2.0.1.0 database server.

When working against an 10.1.0.2.0 database server we do not get any AV.
Do you have any ideas ?

Client version is 9.2.0.1
PL/SQL Developer Version 6.0.5.931

Thanks in advance,

Markus

 

[Marco Kalter]

We have had one more report like this, and we're looking into this. Can you let me know your server OS and version?

 

[mla]

System is Windows Server 2003 Standard with Service Pack 1

Is it known if other DOA based applications are affected too ?

 

[Marco Kalter]

No, this is not yet known.

 

[Neil Russell]

We have been having the same problem since we upgraded to oracle 10g. We are running server version 10.2.0.1.0 with clients ranging from 8i to the latest 10g driver.
PLSQL Developer 5 crashes when the access violation occurs. PLSQL Developer 6 disconnects but can be reconnected afterwords.

 

[orca777]

Hi,
is the 10G R2 not still a beta release it's called 'Oracle Database 10g Developer's Release 2'

And developer release means not a production release. Had you the same experience with connecting to Oracle 10GR2 on the Linux Platform?
This is production release.

Regards
carl

 

[Neil Russell]

We are seeing this with Oracle 10GR2 on Linux

Neil

 

[Texxan]

Same here - PL/SQL Dev crashes religiously after about 20 minutes of use while connected to a 10gR2 Linux db. Makes me want to find the nearest tall building and jump off it.

Seem to be having some luck connecting to a non-10gR2 db and linking to the 10gR2 via a database link. Not ideal, but at least gets me query access without starting all over every 20 minutes.

Please email me when a patch is available.

Thanks -

Ben

 

[Marco Kalter]

Can somebody with this problem run PL/SQL Developer with the debug parameter? For example:

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

Reproduce the problem and as send me the debug.txt file that is generated in the PL/SQL Developer directory.

 

[Marco Kalter]

Does anybody know the following?

1. What PL/SQL Developer function are you using when this error occurs? Does it happen during logon or logoff?

2. Does it help if you switch to Dual Session mode (Tools > Preferences > Oracle/Connection)?

3. Is there any way to reproduce the problem?

 

[Marco Kalter]

UPDATE: switching to Single Session mode (Tools > Preferences > Oracle/Connection page) seems to prevent this problem. You can use this as a temporary workaround until we have a fix.

Note that in Single Session mode there is no multi-tasking and all functions share the same session!

In the mean time, if anybody has any insights on how to reproduce the issue, please let me know.

 

[JohnH]

Switching to Single Session Mode eliminates your ability to run the debugger. Not a good work around for my purposes.

This is a tough problem to re-create. It appears totally random.

 

[Neil Russell]

I still get the error even in single session mode. It does not show up as an access violation it just says current operation cancelled. It has the same effect though, I lose my connection to the database.

Here is the relevant error in the debug log:
8/25/2005 12:49:24 PM Oracle Error: Session.ResolveSymbolQuery
ORA-24909: call in progress. Current operation cancelled

 

[dewiii]

Has ANYONE found a way around this problem that actualy works!?! Is there a bug fix on the way!?!

 

[Marco Kalter]

We have a 6.0.6 pre-release that should fix the problem. We're still validating this fix though.

 

[DLab]

I have same problems. It all started when I upgraded from 6.0.4 to 6.0.5. Before, everything was working properly.

Edit : Now it is still doing same problem with 6.0.4. Trying 6.0.6

Edit #2 : Version 6.0.6 seems to have fixed problem. I didn't get the error since.

 

[vladzak]

btw, for all those having a good mix of various client and server versions: Oracle has a nice client-server release interoperability matrix on MetaLink, and it says that the only supported combinations now are these:

9.0.1 through to 10.2 should talk with each other;
8.1.7.4 should talk up to 10.1, but not 10.2, and it's not officially supported anymore;
previous 8i releases can't talk to 9.2 and up.

This goes both ways - older releases can't talk to newer servers and vice versa. Indeed, I was having problems with my 9.2 client talking to 8.1.6 db, like silent crashes on trivial SQL and likes. Switched to 8.1.7 client - and the problems gone.

So those of you who want to use 10.2 - you gotta upgrade your Oracle client software to at least 9.0.1 (9.2 highly recommended) and keep 8.1.7.4 around for older servers, and switch between them appropriately.

hth.