Re: Table extents
Date: Sun, 09 Sep 2001 08:03:32 GMT
Message-ID: <onFm7.27531$bY5.153761_at_news-server.bigpond.net.au>
As far as I know they are the only two solutions I know, I have previously used the first one. But the second one sounds ingenious.
Although I had one table 32,000 extents! hehe whoops!
Database kept running but pretty much fell to it's knees and couldn;t return a query. Fortuneately the export command worked!
Tony
"Travis" <trp9_at_home.com> wrote in message
news:96um7.52656$MK5.29965517_at_news1.sttln1.wa.home.com...
> I recently took over support for an app that has very little back end
> documentation. An automated message was generated saying I had 3 tables
> with "Extreme Fragmentation". Looking closer I saw that the following
> tables has the following extents:
> table1_ancientapp 89 extents
> table14_ancientapp 9 extents
> table22_ancientapp 8 extents
>
> In looking to rectify the situation, I was thinking of performing the
> following procedure
>
> drop indexes on table1_ancientapp, export table1_ancientapp, drop
> table1_ancientapp, create table1_ancientapp, import the data back in,
> rebuild the indexes.
>
> I understand that I can also create a new table by doing a select from the
> previous one, drop the previous table and rename the new table to the old
> ones name, but would this have the same result as the above?
>
> Is either of these the solution I want to use to remedy the situation?
>
> Thanks
>
>
Received on Sun Sep 09 2001 - 10:03:32 CEST