Re: Bigfile tablespaces and ASSM.....

Mark,

Just in case you didn't consider that - big files will reduce granularity of restore/recovery if you get to do it one day. Also it's easier to resume full non-incremental backups after a failure when datafiles are smaller.

On 10/3/06, Bobak, Mark <Mark.Bobak_at_il.proquest.com> wrote:
>
> Just a comment….I just noticed that for bigfile tablespaces, ASSM is
> required…..hmm….I guess that answers the question of ASSM vs. MSSM.
>
> I'm setting up my test environement w/ 10gR2, three node Opteron RAC
> running 64-bit RHEL4, w/ ASM. With ASM, it makes a lot of sense to have one
> datafile per tablespace, that autoextends, and use bigfiles. That way, you
> never have to add a datafile. You just monitor the free space in the disk
> group, and add space at the diskgroup level, when necessary. But, bigfiles
> require ASSM….though I'm not sure why…it doesn't strike me that those two
> features would be related….but apparently, they are.
>
> -Mark
>
> *--*
> *Mark J. Bobak*
> *Senior Oracle Architect*
> *ProQuest Information & Learning*
>
> For a successful technology, reality must take precedence over public
> relations, for Nature cannot be fooled. --Richard P. Feynman, 1918-1988
>
>

-- 
Best regards,
Alex Gorbachev

The Pythian Group
Sr. Oracle DBA

http://www.pythian.com/blogs/author/alex/
http://blog.oracloid.com

--
http://www.freelists.org/webpage/oracle-l