Re: rollback segment reached maximum extent

From: Rich Goldkamp <RJGoldka_at_dcss.com>
Date: Mon, 17 May 1999 21:45:40 GMT
Message-ID: <7hq2m3$3ei$1@nnrp1.deja.com>

There's a gotcha with the COMPRESS=Y option on export. You will not gain the benefit of consolidating your objects into single extents unless you drop them prior to importing them; otherwise, the initial and next extent specifications remain as they are prior to the export.

Cheers,
Rich

In article <01be9fd2$d3b42660$5011eec3_at_default>, "GDN" <gert.deneve_at_advalvas.be> wrote:
> For your rollback segments -> Use the "optimal" option.
>
> For your export. If you tell exp to do so, it will compress all the
data
> of a table into
> one big initial extent when you import the data. So yes, an exp/imp
can
> help you.
>
> Gert
>
> kgsudhi_at_my-dejanews.com wrote in article <7hm3u4$f32
$1_at_nnrp1.deja.com>...
> > Hello
> > I am using Oracle 7.3.3.5 on OpenVMS7.1 (Alpha Server . RAID-
5).
> > When I was monitoring the disk space utilization, extent information
> > etc for tablespaces and rollback segments, I found that one of the
four
> > rollback segment reached the maximum (121) extents. I would like to
> > know what is the effect of this in my system and how can I re-
organize
> > it. Will it affect the execution time of sqls? Many of other tables
are
> > also reached more than 50 extents. Will an export and import will do
> > the job for me ?
> >
> > Please help me to solve this issue.
> >
> > Thanks in Advance
> >
> > Sudhi
> >
> >
> > --== Sent via Deja.com http://www.deja.com/ ==--
> > ---Share what you know. Learn what you don't.---
> >
>

Rich Goldkamp, Consultant, OCP		RJGoldka_at_dcss.com
Digital Consulting & Software Services	(504) 523-5005 x2736

--== Sent via Deja.com http://www.deja.com/ ==-- ---Share what you know. Learn what you don't.--- Received on Mon May 17 1999 - 16:45:40 CDT