Re: Source of expensive SQL
- From: jame tong <jametong@xxxxxxxxx>
- To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 13 Jan 2006 17:48:49 +0800
Why not check which process run this script.
then tune this sql , may be there was a parameter or storage parameter to
control this.
On 1/9/06, Tim Hopkins <oracle-l@xxxxxxxxxxxxxxxxxx> wrote:
> Tim
>
> > Not sure if it helps, but wouldn't "bitand(i.flags, 256)" and
> > "bitand(i.flags, 512)" be the same as 0x100 and 0x200 below
> > (from sql.bsq):
> >
> > From the same source:
> >
> > /* cooperative index method : 9 */
> >
> > PS. Anyone know what a "cooperative index method" is?
> >
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
- References:
- RE: Source of expensive SQL
- From: Ray Feighery
- Re: Source of expensive SQL
- From: Tanel Põder
- Re: Source of expensive SQL
- From: Wolfgang Breitling
- Re: Source of expensive SQL
- From: Tim Hopkins
Other related posts:
- » Source of expensive SQL
- » RE: Source of expensive SQL
- » RE: Source of expensive SQL
- » Re: Source of expensive SQL
- » Re: Source of expensive SQL
- » Re: Source of expensive SQL
- » Re: Source of expensive SQL
- » Re: Source of expensive SQL
- » Re: Source of expensive SQL
- » RE: Source of expensive SQL
- » Re: Source of expensive SQL
- » Re: Source of expensive SQL
- RE: Source of expensive SQL
- From: Ray Feighery
- Re: Source of expensive SQL
- From: Tanel Põder
- Re: Source of expensive SQL
- From: Wolfgang Breitling
- Re: Source of expensive SQL
- From: Tim Hopkins