Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Analyze table timing
Hi,
You could do the following :
- analyze table estimate statistics instead of compute statistics - use a parallel hint when running analyze command - use dbms_stats (oracle 8.1.5.1, 8.1.6.0 or higher) to collect statistics -you can give it a
Oh btw - killing an analyze in 8i often comes with an ORA600 ... it will not
crash the DB but, hey, as most
of us I'm not too very fond of those ORA600's in the alert log...
Cheers,
Koert
"broom" <broom_at_voicenet.com> wrote in message
news:c948eb61.0109180623.667b533_at_posting.google.com...
> How can I determine how long an 'analyze compute statistics'
> of a table will take?
>
> I've currently got a 3 CPU sun 450 with about 1TB of
> storage across 2 fibrechannel arrays, using Veritas
> DB for Oracle. I've got a table that currently takes
> about 70GB, packed in at about 95% used. Almost all
> varchar fields, typical records length of 1200 bytes
> spread across 157 fields. Currently has about 60 million
> records.
>
> It's been running 10 hours so far, and I'm trying to determine
> how long to let it go before aborting. If I want to run again,
> what variables should I modify in the init, or alter system, etc,
> which would speed things up.
>
> Right now it is only using one cpu (achh, phhtt). I don't see
> a parallel option. The table is broken out by 10 partitions
> in the same tablespace, which indicates to me I might be able
> to run concurrent analyzes on a partition basis.
Received on Tue Sep 18 2001 - 09:40:19 CDT
![]() |
![]() |