Re: RE: Locally Managed Tablespaces

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Fri, 21 Mar 2003 23:40:49 -0000
Message-Id: <24738.322757@fatcity.com>

For 7.3 it is also important to set MINIMUM EXTENT for the tablespace to match the initial and next - then every extent has to be at worst a multiple of the minimum extent size whatever a rogue user does.

Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

For one-day tutorials:
(see http://www.jlcomp.demon.co.uk/tutorial.html )

____UK_______April 8th
____UK_______April 22nd
____Denmark May 21-23rd
____USA_(FL)_May 2nd

Next dates for the 3-day seminar:
(see http://www.jlcomp.demon.co.uk/seminar.html )

____UK_(Manchester)_May
____Estonia___June (provisional)
____USA_(CA, TX)_August

The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

Original Message ----- From: "Rachel Carmichael" <wisernet100_at_yahoo.com> To: "Multiple recipients of list ORACLE-L" <ORACLE-L_at_fatcity.com> Sent: 21 March 2003 19:20 Subject: Re: RE: Locally Managed Tablespaces

> pctincrease=0 and set the storage parameters at the tablespace level
> and do NOT put storage parameters on the individual objects.
>
> you can "fake" the workings (without the bitmap!) of an LMT by doing
> that. Next extent=initial extent, pctincrease=0 will effectively
> allocate extents of equal sizes
Received on Fri Mar 21 2003 - 17:40:49 CST