Re: Partitioned table space stats ... Incremental question and TEMP tablespace usage...

From: David Mann <dmann99_at_gmail.com>
Date: Thu, 29 Mar 2012 14:15:25 -0400
Message-ID: <CAGazuyVtUw6QwjMN2oDjURZX9b8sBNVm88VLbiCoVKJX-W0Tww_at_mail.gmail.com>

To follow up, the stats gather worked when I ran it again... I watched TEMP like a hawk and only saw a few blocks used here and there. Will have to dig deeper if it behaves funky again.

This partitioned table is 15gb and only one index on it ... of the 29 columns in the table the index references 13 of them. This is my first look at this app so I suspect a report writer probably had a query with 13 columns in the WHERE clause :)

I will check into Index Monitoring and see how much it is actually used.

-Dave

On Thu, Mar 22, 2012 at 12:18 PM, Kellyn Pot'vin <kellyn.potvin_at_ymail.com> wrote:
> Outside of Greg's very good question, I also have one-  Are there any
> indexes on this partitioned table?  I just took a quick scan through your
> email, but if you have chosen "TRUE" on CASCADE and you have global indexes
> on the partitioned table, that could easily explain the temp issue.
>
> I don't see anything specifying if there are any indexes or not, but thought
> I'd ask... :)
>
> Kellyn Pot'Vin
> Senior Technical Consultant
> Enkitec
> DBAKevlar.com

-- 
Dave Mann
www.brainio.us
www.ba6.us - Database Stuff - http://www.ba6.us/rss.xml
--
http://www.freelists.org/webpage/oracle-l

Received on Thu Mar 29 2012 - 13:15:25 CDT