CBO - default num_rows in a table

From: Hallas John <John.Hallas_at_btcellnet.net>
Date: Fri, 14 Sep 2001 02:37:57 -0700
Message-ID: <F001.0038E416.20010914022024@fatcity.com>

My question of the day is :-
What value does the CBO use as a default number of rows for a table.

Background: -

We all know that if any tables in a query have been analyzed then CBO is used for the query not RBO (couple of caveats I know but let's continue).

So if 3 tables are used in a query and table a has 500 rows (analyzed) table b has 50 rows (never analyzed) and table c has 3500000 rows (never analyzed) all things being equal then CBO is used but what values does the CBO use for tables b or c to decide which execution plan is best.

On a development system yesterday a query was running slow. I realised that we had put in a very large data load (3.5M rows). I analyzed the table and indexes and the query came back in sub second response time. I am trying to figure what value was being used for num_rows prior to the analyze. It cannot be based on blocks allocated/used as thet would have increased after the dataload

Thanks

John

-----Original Message-----
From: DENNIS WILLIAMS [mailto:DWILLIAMS_at_LIFETOUCH.COM] Sent: 13 September 01 22:22
To: Multiple recipients of list ORACLE-L Subject: RE: Automanagement of extent sizing

!! Please do not post Off Topic to this List !!

Cherie - We have been using the autoextend feature for 6 months now and have been really pleased with it. I am now studying the Oracle White Papers on the locally managed and uniform extent philosophy and beginning to follow that scheme. I would recommend studying it carefully. We have had a couple of runaways that ate up a lot of disk, that is the most obvious downside. The upside is obvious in the title of the Oracle white paper "Stop Defragging and Start Living". Here are my procedures so far:

Use Oracle's new uniform extent recommendations to eliminate free extent fragmentation. Since all extents are the same size, no fragmentation can occur.
Use locally-managed tablespaces per Oracle's recommendation.
Set all extents in a tablespace to the same size. There are no unusable small free extents, free space is usable by any segment, and administration is minimized.
Use only 3 extent sizes: 128K, 4M, and 128M
All segments should have less than 1,024 extents. When a table approaches 1,024 extents, it should be moved to the next larger extent size tablespace.
Monitor archive log space.
Temporary and rollback tablespaces should be divided into 1,024 extents for optimal performance.
Export the table before moving it.
Use the Oracle "alter table XXX move" command.
Use the Oracle "alter index XXX rebuild" command.

Let me know if you have any more questions, and please share your ideas.

Dennis Williams
DBA
Lifetouch, Inc.
dwilliams_at_lifetouch.com
--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: DENNIS WILLIAMS
INET: DWILLIAMS_at_LIFETOUCH.COM

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------

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

This email and any attachments may be confidential and the subject of legal professional privilege. Any disclosure, use, storage or copying of this email without the consent of the sender is strictly prohibited. Please notify the sender immediately if you are not the intended recipient and then delete the email from your inbox and do not disclose the contents to another person, use, copy or store the information in any medium.

Received on Fri Sep 14 2001 - 04:37:57 CDT