Hello
I have several questions regarding bigfile tablespaces.
Database: 11.2.0.4.0, oracle linux 7.3, using ASM
My problem is, I have database (block size 8kb) where there is one single table which single LOB column increases a lot. At the moment database is about 1.3tb in size and 99..% of it is this one LOB column. At the moment I am using smallfile tablespaces, but since there would be a very lot of datafiles (at the moment 45 of these), I was thinking of creating bigfile tablespace and use table redefinition online (additional disk space is not an issue) to move data to a bigfile tablespace, because it makes managing it a lot easier, in my opinion.
- From here Bigfile tablespace tips I found out that with bigfile tablespace I can have database size a lot more, comparing to smallfile tablespaces, but my problem is that with 8kb blocks, max datafile size is 32tb (bigfile tablespace can have only 1 datafile), so basically meaning that this one table can grow only up to 32tb and that is it, am I right..?
- So basically with smallfile tablespace I can have this tablespace basically up to MAXIMUM DATABASE SIZE (2,097,152 GB), since I can add multiple datafiles into it.
- Can I have block size per tablespace also or it just is per database..?
Also could anyone explain me this:
From here: https://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces002.htm#ADMIN11360
Avoid creating bigfile tablespaces on a system that does not support striping because of negative implications for parallel query execution and RMAN backup parallelization.
What this means "does not support striping" and "will the parallel query execution won't be possible anymore" and "can't I run rman backup/recovery in parallel any more"..? Or what this actually means..
Regards
Raul