Hi,

Is there a way, on 10g and 11i, to create a set of 4 tablespaces, each
of which is
set to autoextend, so that the entire set of tablespaces has a
specific maxsize
value?

I am not interested in setting a specific maxsize value for any
specific tablespace,
rather, for the set as a whole.






Thanks

On Dec 13, 7:40*am, "if_inves... (AT) yahoo (DOT) com"
<basis_consult... (AT) hotmail (DOT) com> wrote:
I don't think so, but I can see where that would be useful. One way
or another, you are going to have to monitor it.

jg
--
@home.com is bogus.
http://www.computerworlduk.com/news/...-body/?olo=rss

On Dec 13, 10:40*am, "if_inves... (AT) yahoo (DOT) com"
<basis_consult... (AT) hotmail (DOT) com> wrote:
The size of Oracle tablespace is determine by the Oracle block size,
type of tablespace, and in the case of small file tablesaces number of
files with up to approx. 4 million blocks per file.

You can find the specificies in the Oracle version# Reference manual.

For 11gR2
http://download.oracle.com/docs/cd/E...02.htm#i287915

HTH -- Mark D Powell --

On Dec 13, 1:27*pm, Mark D Powell <Mark.Powe... (AT) hp (DOT) com> wrote:
My response does not match the OP so I am not sure where this reply
belonged but as Joel said you would have to role your own check for
the total size of the 4 tablespaces in quetion. I would think you
could sum the allocated bytes from dba_data_files and take the maximum
size restriction into account to provide yourselft a quick check. I
can see how such a ckeck might be useful if all 4 tablespace's data
files were allocated to the same OS file system and you were compaing
used/remaining agains the file system limitiation.

HTH -- Mark D Powell --

On Mon, 13 Dec 2010 07:40:01 -0800, if_investor (AT) yahoo (DOT) com wrote:


Far better IMHO to avoid autoextend altogether; simply set sensible sizes
for your tablespaces and monitor, unless the requirements are highly
unusual.

On Dec 13, 7:35*pm, HoneyMonster <some... (AT) someplace (DOT) invalid> wrote:

IMHO, ditch file systems direct-attached SCSI and use ASM with SAN to
automatically manage all of those pesky space issues - just make sure
you have enough disk space for your system. Disks are cheap compared
to constant monitoring and the on-call personnel having to get called
in for such stupid things as space. If companies and people would
stop skimping on their hardware more of us DBA's would get a lot more
sleep. How much space does your db need? -- All of it!!