This content has been marked as final. Show 11 replies
Where are you seeing this error?
In SQL*Plus? Windows? Toad? where?
I am using PL/SQL Developer. and additionally an using 10g release 10.1.0.4.0 to querying a database on Release 10.2.0.1.0. Maybe that has something to do with it.
Do you get the same if you run the query through SQL*Plus?
It runs fine sqlplus however when I use PL/SQL Developer some queries run ok one minute and the next this error occurs and I have to exit and restart. I am now thinking it may be a problem between PL/SQL Developer and the Oracle release that I have been using.
Most probably is a problem with PL/SQL Developer, you should try to get support from them.
I usually get similar errors but from TOAD, I have to close/kill the process and then start again.
The error does not seem like an Oracle error. If there is not an ORA-nnnn number, then it is not Oracle RDBMS related.
Access violation is typically an o/s exception. It is thrown when a process attempts to access memory it "does not own".
In this case, it seems that the process is referencing a null pointer. A null pointer is typically initialised by the language's compiler with high ($FF) or low ($00) values.
This sounds like you have an o/s error using client sofftware. And this has absolutely nothing to do with the Oracle server side languages called SQL and PL/SQL - the topics of this forum.
Well, Billy's gone for the direct answer again. hehe!
I was leading the OP to realise that the problem was not with their oracle queries but with the software they are using.
Access Violation's are Windows errors and a sign of dodgy windows software.
Soz Blu.. I usually simply whack away with the old lead pipe from the start.. do not want to waste time (better spend swinging the pipe) by first leading them into a dark alley and then beating 'em up...
But you're just as keen as I am to see that people learn stuff Billy, so they don't keep asking the same questions. If they can figure out where the problem lies for themselves then they learn to recognise it for next time. ;)
However, the occassional lead pipe isn't a bad thing.
Have you tested it with a 10G release 2 client?
Does it work?
In the past we add several customers (client) that received the same error using our application. What we noticed is that the error was always raised by an Oracle client DLL.
When we asks all our customer to migrate to Oracle 10G release 2 on the client side everything went ok (everything else being the same).
Corroborating what Carl has said I found that this was caused by an incorrect version of orapls10.dll
There were two versions of this file on my machine in separate locations. I changed the oracle/bin entry in the PATHS environment variable to point to the other one and this resolved the problem.