Re: exp owner=sys, system compress=y?

Can't say I ever have reached maxextents. What is it set to? I know if you *don't* set maxextents (for non-system tablespaces), it defaults to something a little over 2 billion -which must be the theoretical, if not the practical, limit. Never encountered a practical limitation.

Have you?

Regards
HJR

--
--------------------------------------------------------------------------
Opinions expressed are my own, and not those of Oracle Corporation
Oracle DBA Resources:               http://www.geocities.com/howardjr2000
--------------------------------------------------------------------------



"Frank" <frankbo_at_interaccess.nl> wrote in message
news:8qss3i$5af$1_at_porthos.nl.uu.net...


> Did you ever run into a "maxextents reached" on your system TS?

> One of the reasons Oracle Corp recommends not to set the system TS to

> pctincrease 0.

> For all others - agreed.

> --

> Frank

> Howard J. Rogers <howardjr_at_www.com> schreef in berichtnieuws

> 39d1a924_at_news.iprimus.com.au...

> > Oracle's default when it creates *any* tablespace is 50%.  Which has to

 be


> > one of the worst defaults going around.  I always change it for my

> > databases, and can't say I've noticed any horrible effects.

> >

> > Regards

> > HJR

> > --

>


> --------------------------------------------------------------------------

> > Opinions expressed are my own, and not those of Oracle Corporation

> > Oracle DBA Resources:

 http://www.geocities.com/howardjr2000
>


> --------------------------------------------------------------------------

> >

> >

> >

> > "Van Messner" <vmessner_at_bestweb.net> wrote in message

> > news:BM9A5.1301$np1.175347_at_newshog.newsread.com...

> > > I may be wrong but I think if you set the pctincrease on the system

> > > tablespace to zero, you will shortly have objects which have thrown an

 awful


> > > lot of extents.  Oracle's default when it creates a system tablespace

 is
 to


> > > set pctincrease to 50%.

> > >

> > > Van

> > >

> > >

> > > "Brian Peasland" <peasland_at_edcmail.cr.usgs.gov> wrote in message

> > > news:39D0A034.A206CC51_at_edcmail.cr.usgs.gov...

> > > > The only way to remove fragmentation is to export the data, delete

 the


> > > > database, recreate the database with a modified sql.bsq file so as

 to


> > > > reduce fragmentation, and then import the data. You can not export

 just


> > > > the SYS tables.

> > > >

> > > > But the bigger question is why are you worried about this? Are you

 sure


> > > > that fragmentation is slowing your database performance? Fragmented

> > > > tables are not the death knell for high performing databases. Many

> > > > databases run just fine with fragmentation, especially OLTP systems.

> > > >

> > > > HTH,

> > > > Brian

> > > >

> > > >

> > > > NetComrade wrote:

> > > > >

> > > > > Hi,

> > > > >

> > > > > My system tablespace is getting fairly fragmented.

> > > > > I was wondering if anybody has been able to successfully rebuild

 it


> > > > > w/o any probs via imp/exp.

> > > > >

> > > > > Thanx.

> > > >

> > > > --

> > > > ========================================

> > > > Brian Peasland

> > > > Raytheons Systems at

> > > >   USGS EROS Data Center

> > > > These opinions are my own and do not

> > > > necessarily reflect the opinions of my

> > > > company!

> > > > ========================================

> > >

> > >

> >

> >

>
>