Re: Weird SQL error in 8.1.6

From: John Jones <john.jones_at_duke.edu>
Date: Mon, 5 Feb 2001 15:32:29 -0500
Message-ID: <95n2hv$no3$1@news.duke.edu>

below is the trace file

Oracle8i Enterprise Edition Release 8.1.6.2.0 - Production With the Partitioning option
JServer Release 8.1.6.2.0 - Production
ORACLE_HOME = /opt/app/oracle/product/8.1.6 System name: AIX

Node name:      kringle
Release:        3
Version:        4
Machine:        000168694C00

Instance name: SA_DEV75
Redo thread mounted by this instance: 1
Oracle process number: 26
Unix process pid: 85596, image: oracle_at_kringle (TNS V1-V3)

• 2001-02-05 15:28:47.800
• SESSION ID:(16.1047) 2001-02-05 15:28:47.776 APPNAME mod='SQL*Plus' mh=3669949024 act='' ah=4029777240

  ---

  PARSING IN CURSOR #1 len=70 dep=0 uid=29 oct=42 lid=29 tim=3651212268 hv=123643050 ad='706fa72c' alter session set events '10046 trace name context forever, level 4' END OF STMT EXEC #1:c=1,e=3,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=4,tim=3651212268

  ---

  PARSING IN CURSOR #1 len=70 dep=0 uid=29 oct=42 lid=29 tim=3651212470 hv=123643050 ad='706fa72c' alter session set events '10046 trace name context forever, level 4' END OF STMT PARSE #1:c=0,e=0,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=4,tim=3651212470 BINDS #1: EXEC #1:c=0,e=0,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=4,tim=3651212470

  ---

  PARSE ERROR #1:len=75 dep=0 uid=29 oct=3 lid=29 tim=3651213267 err=933 select sysdate from dual where :SYS_B_0 = :SYS_B_1and :SYS_B_2 = :SYS_B_3 XCTEND rlbk=0, rd_only=1

--
John Jones
Senior Oracle DBA
Duke University, OIT
john.jones_at_duke.edu
Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk> wrote in message
news:981402385.28741.0.nnrp-02.9e984b29_at_news.demon.co.uk...


>

> 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.

> >>

>

>

>

Received on Mon Feb 05 2001 - 14:32:29 CST