Of course, they're getting rid of LONG's also. ;-) Someone else mentioned the i_o_c_a as a potential plan changer. Try to alte= r=20 a session with a lower value for i_o_c_a and explain/autotrace the query again. I have seen some of our queries "magically" change from fts to irs. On 4/22/05, Post, Ethan <Ethan.Post@xxxxxx> wrote: > My prediction is that RULE hint will really go away as soon as apps no > longer uses it anywhere. I have heard the same thing about its use. >=20 > -----Original Message----- > From: oracle-l-bounce@xxxxxxxxxxxxx > [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Marquez, Chris > Sent: Friday, April 22, 2005 9:27 AM > To: oracle-l@xxxxxxxxxxxxx > Subject: RE: rm RULE based optimizer !=3D3D GOOD IDEA >=20 > I have not supported Oracle Apps, but from what I understand it is > loaded with hints and I believe some of the using "RULE hint. > Seems a little "Do as I say not as I do" from Oracle Corp....eh? >=20 > I agree about the spending all day on with stats and explain plans. > I have a script to look for blocking locks using v$ views...it ran ok, > but a DBA friend made if faster in about 5 minutes by adding a RULE > hint. > Maybe I should be going after the base Oracle tables, but I don't have > all day. >=20 > Finally about execution plans and speed changing of sql using the RBO. > If I'm not mistaken many environment changes can effect CBO too!? >=20 > Chris Marquez > Oracle DBA > HEYMONitor(tm) - heymonitor.com > "Oracle Monitoring & Alerting Solution" >=20 > -- > //www.freelists.org/webpage/oracle-l > -- //www.freelists.org/webpage/oracle-l