Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: SQL Statement Execution: HEELP!

Re: SQL Statement Execution: HEELP!

From: Sybrand Bakker <postbus_at_sybrandb.demon.nl>
Date: 2000/04/25
Message-ID: <956695356.22389.0.pluto.d4ee154e@news.demon.nl>#1/1

Without looking at your code we can't clarify the confusion. One general note: PL/SQL is very picky about scope and far more picky than sql*plus or sql*worksheet.

Hth,

Sybrand Bakker, Oracle DBA

Dwayne Remekie <dremekie_at_home.com> schreef in berichtnieuws 3905fe4a_3_at_news1.prserv.net...
> Folks, I am confused.
>
> I have one fairly long and complicated UPDATE statement. When I run the
> statement in SQL window, it works perfectly (153 rows updated with correct
> values). I created a procedure with the EXACT same query in it and nothing
> else, it does not work (all rows have wrong values).
>
> Also, The procedure has one parameter. The outcome of the update
 statement
> changes when I change the parameter.... however the update statement does
> not use ANY variables at all... it is hardcoded!
>
> It seems like a memory issue to me.
>
> What would cause an SQL statement to behave differently in a procedure
 than
> when run in an SQL window? Is there some memory settings that I should be
> looking at?
>
> Thanks for any help,
> Dwayne
>
>
>
Received on Tue Apr 25 2000 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US