Re: Weird SQL error in 8.1.6

The good news -

I've just run your statement on 8.1.5 with cursor_sharing=force, and the statement
does not crash (at least from the SQL*Plus command line).

Just for interest, what actually gets into the trace file if you do:

alter session set events '10046 trace name context forever, level 4';

before you run the statement that give the 933 ?

--
Jonathan Lewis
Yet another Oracle-related web site:  http://www.jlcomp.demon.co.uk

Practical Oracle 8i:  Building Efficient Databases
Publishers:  Addison-Wesley

Reviews at: http://www.jlcomp.demon.co.uk/book_rev.html



John Jones wrote in message <95mdp8$ec2$1_at_news.duke.edu>...


>Found the problem.  We have an init.ora parameter "cursor_sharing = force"

>set.  this causes the parser to act differently.  We really need this

 option


>because PeopleSoft and our developers are not taking use of Bind variables.

>

>--

>John Jones

>Senior Oracle DBA

>Duke University, OIT

>john.jones_at_duke.edu

>John Jones <john.jones_at_duke.edu> wrote in message

>news:95maqq$d3v$1_at_news.duke.edu...

>> I get the following error

>>

>> ERROR at line 1:

>> ORA-00933: SQL command not properly ended

>>

>> When I put the space back, it works.

>>