1. Documentation in Tahiti -> Masters Book List -> Administrator’s Guide -> 14 Managing Tablespaces -> Creating Tablespaces -> Bigfile Tablespaces
2. BIFILE TABLESPACE DATAFILE but only have a usually very large.
Below it is supposed to have to have some storage configuration with stripping and / or mirroring to have a good performance and reliability.
The maximum size of a bigfile TABLESPACE is 4G blocks. This means that a DB 8K, the maximum size is 4G Blocks * 8K = 32T.
In Oracle 11gR2, this type of TBS can only be LOCALLY MANAGED with ASSM, and that creation is very simple. The managing them well, and we can do that have a fixed size or AUTOEXTEND.
Finally, like the rest of TBS we can specify the block size which will (the latter not because we practice what we have seen in the objective “Create and Manage Temporary, Permanent and Undo Tablespaces”).
– Conducted a building exercises and management of TBS bigfile (default is OFF unless AUTOEXTEND use OMF)
CREATE bigfile TABLESPACE BIGTBS1 DATAFILE '/u01/app/oracle/oradata/OCM/bigtbs01.dbf' SIZE 100M; CREATE bigfile TABLESPACE BIGTBS2 DATAFILE '/u01/app/oracle/oradata/OCM/bigtbs02.dbf' AUTOEXTEND ON NEXT SIZE 100M 100G MAXSIZE 100M;
– We check the attribute bigfile TBS
SELECT TABLESPACE_NAME,bigfile FROM DBA_TABLESPACES;
– We extend one
ALTER DATABASE DATAFILE ‘/u01/app/oracle/oradata/OCM/bigtbs01.dbf’ RESIZE 200M;
– We clean the environment
DROP TABLESPACE BIGTBS1 INCLUDING CONTENTS AND DATAFILES;
DROP TABLESPACE BIGTBS2 INCLUDING CONTENTS AND DATAFILES;