Re: HELP !! ON LARGE TABLESPACES !!

>Why can't the tablespace have multiple datafiles, each datafile on a
>separate disk?

They can.

>
>Something like
>
>CREATE TABLESPACE BIGTABSPACE
>DEFAULT STORAGE ...
>DATAFILE '/drv1/ORACLE/big1.dbf' size 1M,
> '/drv2/ORACLE/big2.dbf' size 1M,
> '/drv3/ORACLE/big3.dbf size 1M;
>
>
>The above syntax or something like it should work. There is no rule that
>the
>entire tablespace be on one disk, but remember that in the above case the
>largest
>extent of any object is 1M. SO if you need a table with a initial extent
>of 1.5M,
>forget it.
>

Largest extent not 1M. 1M - control block, the size of which depends on your db_block_size init parameter.

Specifying your tablespace thus:

>Create tablespace large_ts datafile '/disk1/datafile.dbf' size 1000M,
>'/disk2/datafile2.dbf' size 1000M,
>'/disk3/datafile3.dbf' size 1000M
>/

would cause the tablespace to reside across 3 disk, but you have no control over where tables are allocated within this tablespace.

Striped tables need their own tablespace. Say create a tablespace with 3 datafiles size 1m on different disks. Allocate table minextents 3, initial and next size 1m - control block size.

Hope this helps.

        Helen Received on Thu Jul 20 1995 - 00:00:00 CEST