Re: no cursor_sharing..

This is not quite true. If you enable shared cursors and query rewrite, the same statement will be reparsed, even if it is in the shared pool already. During this reparse, it will be assigned the system bind variable that will make it reusable.

Robert

In article <93ut8f$afn$1_at_soap.pipex.net>,   "Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote:
> Having reread your first post. have you bounced the database instance?
> Oracle won't age the statements out of the statement cache untill you
 do or
> shared pool is full).
>
> regards
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
> <oton66_at_my-deja.com> wrote in message news:93te36
 $6uc$1_at_nnrp1.deja.com...
> > In article <93tdk9$6fm$1_at_nnrp1.deja.com>,
> > oton66_at_my-deja.com wrote:
> > > Martin Haltmayer wrote:
> > > > Try "cursor_sharing = force".
> > > >
> > > > However, be warned. We found 8.1.6.2.1 on Solaris extremely
 instable
> > > > with this setting. Dozens of ORA-00600 happening. If you can
 please
> > > > use bind variables.
> > >
> > > Been trying different variations with case/spaces, also
> > > alter system set cursor_sharing = force/FORCE
> > > without luck, but anyways thanks for the warning.
> > >
> >
> > Oops, a typo in my first posting.. cursor_sharing was always set
> > to 'force', not 'TRUE'.
> >
> > -oton
> >
> >
> > Sent via Deja.com
> > http://www.deja.com/
>
>

Sent via Deja.com
http://www.deja.com/ Received on Wed Jan 17 2001 - 17:42:30 CST