RE: Question On Statistics Gathering

From: Gogala, Mladen <MGogala_at_oxhp.com>
Date: Fri, 27 Jun 2003 15:08:24 -0700
Message-ID: <F001.005BB7DD.20030627143453@fatcity.com>

Oracle is bug free. If not bug free, it is, at least, unbreakable. That means that nothing wrong will happen to you as long as you don't have users or data. They are the problem.
Direct load doesn't generate statistics, even if monitoring attribute is set. Direct load is built for speed, like Ferrari, not for comfort, like a Cadillac.
Monitoring tables is relatively painless, but it is still advisable to analyze the tables with cron jobs over night. Look at the block sampling feature of dbms_stats.

Mladen Gogala
Oracle DBA
Phone:(203) 459-6855
Email:[EMAIL PROTECTED]

-----Original Message-----
Sent: Friday, June 27, 2003 4:34 PM
To: Multiple recipients of list ORACLE-L

Hi All,
Currently we have a very large database ( 8.1.7.4 ) on Tru64 that is having query optimization problems. Lacking good, up-to-date statistics is the main cause of it. Because of the size and availability window we can't afford to analyze the whole schema. Now 8i has
a new feature that only gathers stats when stale. You have to set table to monitoring mode first.
I am intrigued by this new feature and am reading up on it and have 2 questions:
1. How reliable and bug-free is this feature? 2. We do a lot of sqlldr direct path, which bypasses table insert. Will this feature catch the rows inserted that way?

TIA
Dennis
-----Original Message-----
Sent: Friday, June 27, 2003 2:30 PM
To: Multiple recipients of list ORACLE-L

One of our third party applications gave us the following message:

ORA-04031: unable to allocate 4192 bytes of shared memory

Environment is Oracle 8.1.7 on AIX 4.3.2

The output from "select * from v$sgastat showed about 3 mb free out of a total of 40 mb of shared pool. I increased the size of shared pool to 60 mb and started to watch the "shared pool"/"free memory" value in v$sgastat. It seems to vary between about 3 and 11 mb.

What is the application likely to be doing that requires it to allocate shared pool?
How do I know when I have the shared pool value in init.ora set high enough so that I won't get the ORA-04031 errors?
Is there any other init.ora parameter I ought to be looking at here?

Thanks,
Peter Schauss
--

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

Author: Schauss, Peter
INET: [EMAIL PROTECTED]

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: [EMAIL PROTECTED] (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).
--

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

Author: Meng, Dennis
INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------