Bigfile vs. smallfile tablespaces
441858Mar 11 2009 — edited Mar 11 2009Oracle 11g R1/ASM Single-Instance
RHEL 5
========
Hi All,
I just wanted everyones opinion about using bigfile tablespaces vs. the regular smallfile tablespaces. We have one tablespace that gets filled up pretty quick...it is loaded with images and we are trying to decide whether we should go the bigfiles tablespace route or should we just keep creating additional datafiles with the smallfile tablespace method. If I am correct the maximum a smallfile datafile can be is 65GB. And that lasts us about a couple of months. I guess my real question is how would a bigfile tablespace affect database/datafile recoverability. From common sense, I think it would take much longer to recover a 4TB datafile as compared to a 65GB datafile. Or would it?
I just wanted to know what you all think and what you have experienced.
Thanks.