Re: Executing wrong sql

  • From: "GovindanK" <gkatteri@xxxxxxxxxxx>
  • To: sbecker6925@xxxxxxxxx, "oracle-l" <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 16 Oct 2008 21:56:21 -0700

Try this:
alter session set events '10139 trace name context forever';
The plan should not change.
Did you check v$sql_plan earlier?

On Fri, 10 Oct 2008 10:10:49 -0600, "Sandra Becker" <sbecker6925@xxxxxxxx
m> said:

I have a developer trying to run an SQL script against a test
database that is picking up the wrong sql instead of what is
really in my PL/SQL script.  What's really strange to me is that
if I set echo on, I can see the code it should be executing, not
what it is really executing.  Could this be due to a cursor left
open?  I've never seen this behavior before so I'm a bit lost on
where to look.

If I run the same script against another test database, it works
like it's supposed to.  The developer also tells me that this
code worked on this database until we bounced it yesterday.

Our environment for both databases:  Oracle [1], SuSE10,

Any suggestions will be appreciated.




Other related posts: