Big file tablespaces

One of the many disadvanatges of bigfile tablespaces

If you are using AU of 1MB, and have compatibility set to COMPATIBLE.RDBMS = 10.1, and the disk group is of type EXTERNAL redundancy ; then 16T is the maximum allowed file size.

You cannot add a new datafile as bigfile tablespaces only accomodate 1 datafile.

Setting the compatible.rdbms to a higher value does not provide a solution as this will only apply to new datafiles.

A workaround is to create a new tablespace then relocate any tables and/or indexes to this tablespace, thereby freeing up some space on the bigfile tablespace datafile

Other options are to either move the tablespace to another diskgroup of a higher RDBMS compatibility level, and/or of the larger 4M AU size.

show compatibilty, au size values per ASM Disk Group

select group_number, name,compatibility, database_compatibility,ALLOCATION_UNIT_SIZE,TYPE from v$asm_diskgroup