ORA-01003: no statement parsed

upscene · Post by **upscene** » Fri 24 Dec 2004 12:27

Hello,

EXECuting the following (in either the Script component or a normal Query component):

CREATE OR REPLACE PROCEDURE dead_code
IS
x number := 10;
begin
if x = 10 then
x := 20;
else
x := 100;
end if;
select empno
into

from emp;
END dead_code;

Causes the error:
ORA-01003: no statement parsed

Strangely enough, I can run this "just fine" from within TOAD and it lists the error:
PLS-00049: bad bind variable 'X'

afterwards (which makes sense).

I want to achieve the same thing - but how can I run this statement?
(ParamCheck = False)

With regards,

Martijn Tonies
Upscene Productions

Alex · Post by **Alex** » Fri 24 Dec 2004 13:13

We couldn't reproduce the problem.Please specify your ODAC version.

Guest · Post by **Guest** » Fri 24 Dec 2004 15:09

Hello,

Version 5.10.2.8 - using the direct NET connectivity.

--
Martijn Tonies
Upscene Productions

upscene · Post by **upscene** » Fri 24 Dec 2004 15:15

PS: the ":x" is a colon + x -->

Code: Select all

into :x

Paul · Post by **Paul** » Mon 27 Dec 2004 07:49

We fixed the problem with "ORA-01003: no statement parsed" in the last ODAC
version.

upscene · Post by **upscene** » Mon 27 Dec 2004 12:15

Hello Paul,

Interesting - thank you.

Any idea when it will be released? Or a beta perhaps?

( I am a registered customer of the non-source version)

--
Martijn Tonies
Upscene Productions

Paul · Post by **Paul** » Mon 27 Dec 2004 15:34

Please try ODAC 5.10.4.13 from our site

upscene · Post by **upscene** » Mon 27 Dec 2004 17:45

Ah, ok Paul ... Couldn't find that in the "change list".

Thx, I'll give it a go.

upscene · Post by **upscene** » Mon 27 Dec 2004 20:46

Hello Paul,

I'm sorry to say - it still doesn't work. I double-checked the version number, but no luck.

Any other ideas?

--
Martijn Tonies
Upscene Productions

Paul · Post by **Paul** » Tue 28 Dec 2004 10:55

We tested this with TOraQuery, TOraScript with ODAC 5.10.4.13. Statement is
passed without any error message. Net option is an optional feature and does not always work like Oracle client.

upscene · Post by **upscene** » Tue 28 Dec 2004 14:18

Net option is an optional feature and does not always work like Oracle client.

Well, what does that mean?

Shouldn't the "NET option" work the same? If not, what is the purpose of it?

Are you saying that I should NOT use the NET option?

Either way, I've tested with the NET option, as that is what I use.

--
Martijn Tonies
Upscene Productions

Paul · Post by **Paul** » Tue 28 Dec 2004 16:49

Sorry, I mean that ODAC with "NET option" has some restrictions and some features can not be implemented comparing to Oracle client.
Net option returns no messsages in ODAC 5.10.4.13.
"PLS-00049: bad bind variable 'X'" is a warning message that Oracle returns after sucessful excetution of a statement. Sorry, we cannot realize warnings in Net-option.

upscene · Post by **upscene** » Tue 28 Dec 2004 18:38

Hello Paul,

Ah, ok ...

Well, here's the problem:

Currently, it raises the exception I gave you and the execution fails/is aborted.

The warning I want to get via dictionary view ALL_ERRORS (if it exists in there).

So, the problem is not getting the warning, but avoiding the exception being raised while executing the statement.

Why is the statement raising an exception?

--
Martijn Tonies
Upscene Productions

Paul · Post by **Paul** » Wed 29 Dec 2004 07:30

Sorry, You are right. It is fixed in ODAC 5.50.0.14 only

upscene · Post by **upscene** » Wed 29 Dec 2004 10:33

Paul,

Very well. Is the 5.5 ( as it's listed as "beta" ) ready for production, or really beta only?

--
Martijn Tonies
Upscene Productions