Hi Rich, Not sure what specific issues you¹re referring to. If you¹re on 11.2.0.3, and especially if you¹re using ASM, I would recommend BIGFILE tablespaces and UNLIMITED maxsize. This way, the tablespaces grow organically, and you only need to monitor space at the disgroup level. I do that for the main application tablespaces. For tablespaces that developers dump stuff into, I set max size, as I do with TEMP and UNDO. The problems in the past, with backing up really large files, are lifted in 11gR2 (maybe in 11gR1 also, I can¹t rememberŠ) with the SECTION SIZE parameter. -Mark On 11/26/13, 12:05 PM, "Rich Jesse" <rjoralist3@xxxxxxxxxxxxxxxxxxxxx> wrote: >Hey all, > >Creating new DBs in 11.2.0.3 and my SOP has been to create datafiles with >a >MAXSIZE of 31G (8K blocksize). I thought I should revisit -- and >*document* >-- that SOP, but all I can remember is a long-lost discussion (here?) >about >potential issues where a datafile is allowed to grow to the maximum 32GB >(minus 1 block). > >Anyone with a memory or decent googling skills recall? The only close >threads I could find on Oracle-L were a "headroom" one from '09 and a >"MAXSIZE 32767M" one from '06, but those are not what I remember. > >TIA! > >Rich > >-- >//www.freelists.org/webpage/oracle-l > > > > -- //www.freelists.org/webpage/oracle-l