Direct use of ALTER TABLESPACE in Oracle to modify large files

Oracle 10g introduced a new table space type, which is a large file (Bigfile). It does not consist of 1022 files as traditional table spaces; a large file (bigfile) tablespace is stored in a single data file, while its data volume requires a larger hard disk capacity; Large file (bigfile) tablespace can vary according to the size of the selected block. Grow from 32TB to 128TB.

Changing the size of a traditional table space means using the ALTER DATABASE statement to reset the size of its data file, identifying each data file with the full operating system path name or internal file number, and then setting their size again.

ALTER DATABASE
DATAFILE '/u07/oracle/oradata/train/media01.dbf'
RESIZE 1G;

Similarly, you can set the automatic extended properties of a table space by setting the properties of each data file.

ALTER DATABASE
DATAFILE '/u07/oracle/oradata/train/media01.dbf'
AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED;

This is a very fragmented work for large tablespaces with hundreds of data files. However, because large file (bigfile) tablespaces have only one data file, they do not need to identify the data file when they need to resize. Using the ALTER TABLESPACE command makes it easier to resize at the table space level.

ALTER TABLESPACE media
RESIZE 1G;

Similarly, the Autoextend (automatically extended) properties of a data file may be changed to the overall properties of a large file (Bigfile) tablespace for tablespace.

ALTER TABLESPACE media
AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED;

If you are using the ASM Disk Group and Oracle management files, you will get a special benefit, because when you may not know the exact name of a data file, you can use it to automatically generate.

However, this feature of the large file (bigfile) tablespace should not be used alone. Large file (Bigfile) tablespaces are designed to be used on storage area networks (Sans), on disk arrays, on automated storage Management (ASM), and similar storage solutions that provide data-access-prohibitive devices. Since they have only one data file, there is no need to load the balance between individual data files, or if these techniques are not used, an additional data file can be added as a tablespace extension.