RE: FIRST_ROWS hints

Did you remember to cut the db_file_multiblock_read_count in half, since you doubled the blocksize? I would assume that you also started seeing more full table scans, as well.    

Scott Canaan (srcdco_at_rit.edu)

(585) 475-7886

"Life is like a sewer, what you get out of it depends on what you put into it." - Tom Lehrer.  

-----Original Message-----
Sent: Wednesday, October 08, 2003 2:54 PM To: Multiple recipients of list ORACLE-L  

hi  

i had a migration from 9.2.0.3 to 9.2.0.4 of a database and here are a couple of observations. please help me in understanding this.  

i changed the db block size from 8k to 16k and all sql queires which were using nested loops earlier moved to sort merge joins. i ran 10053 and form whatever i could understand the 9204 db has fewer number of blocks compared to the existing 9203 (db size changed to 16k) and sort merge join turned out to be less costlier than nested loops (i couldnt understand the sort statistics). no parameter other than db block size was changed.  

after breaking my head i changed the optimizer mode from choose to first rows and the query is back to the old explain plans.  

please clarify

1. whether this is a expected behaviour
2. what is first_rows hint and whether it is good move to go to first_rows to fix this problem.

thanks

sai    

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Scott Canaan
  INET: srcdco_at_rit.edu

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L


(or the name of mailing list you want to be removed from).  You may

also send the HELP command for other information (like subscribing).