Re: this table won't clean itself

From: varad acharya <vacharya.ford_at_e-mail.com>
Date: 1996/10/28
Message-ID: <3274A676.2338_at_e-mail.com>#1/1


Martin Douglas wrote:
>
> In article <54o73a$phf_at_news.inconnect.com>, <ldalton_at_inconnect.com> writes:
> > Path: news.ou.edu!news.nodak.edu!netnews1.nwnet.net!netnews.nwnet.net!reuter.cse.ogi.edu!uwm.edu!cs.utexas.edu!howland.erols.net!news.sprintlink.net!news-pee
> > From: ldalton_at_inconnect.com (Larry Dalton)
> > Newsgroups: comp.databases.oracle
> > Subject: this table won't clean itself
> > Date: Thu, 24 Oct 1996 17:02:05 GMT
> > Organization: Internet Connect, Inc. -- http://www.inconnect.com
> > Lines: 26
> > Message-ID: <54o73a$phf_at_news.inconnect.com>
> > Reply-To: ldalton_at_inconnect.com
> > NNTP-Posting-Host: slc-dial-23.inconnect.com
> > X-Newsreader: Forte Free Agent 1.0.82
> >
> > I have a table that has been created like this:
 

>

Can you verify whether it is the table or the index that is running out of extents ? If it event_number is unique for each row , I would suspect the index getting fragmented and causing it to grow large enough to run out of extents. I would suggest you drop this index before you start your delete process and then recreate the index after the deletes are done.You  may also want to specify higher value for the initial & next extents for this index. You can check the view USER_SEGMENTS to find out the space used by this index.

Good luck !  

Regards,

Varad Acharya

 The above statements and opinions are my own and do not  necessarily represent those of Ford Motor Company. Received on Mon Oct 28 1996 - 00:00:00 CET

Original text of this message