Re: Questions on ASM best practices
Date: Wed, 17 Dec 2014 16:23:34 +0100 (CET)
Message-ID: <1988957095.352565.1418829814269.open-xchange_at_app04.ox.hosteurope.de>
Hi Jeremy,
>> Remember that ASM will automatically use the smaller stripe size for redo logs; you don't have to configure that.
Unfortunately not anymore. This changed with 11.2, but the documentation does not keep up with it. The default for redo log files is COARSE nowadays as well.
SQL> select distinct name, stripe from v$asm_template;
NAME STRIPE ------------------------------ ------ ASMPARAMETERFILE COARSE DATAFILE COARSE BACKUPSET COARSE AUTOBACKUP COARSE OCRBACKUP COARSE ONLINELOG COARSE <<<<<<<<<<<<<<< DATAGUARDCONFIG COARSE CONTROLFILE FINE CHANGETRACKING COARSE ARCHIVELOG COARSE ASM_STALE COARSE FLASHFILE COARSE XTRANSPORT COARSE OCRFILE COARSE ASMPARAMETERBAKFILE COARSE DUMPSET COARSE PARAMETERFILE COARSE FLASHBACK COARSE TEMPFILE COARSE
Best Regards
Stefan Koehler
Oracle performance consultant and researcher
Homepage: http://www.soocs.de
Twitter: _at_OracleSK
> Jeremy Schneider <jeremy.schneider_at_ardentperf.com> hat am 17. Dezember 2014 um 14:19 geschrieben:
>
>
> On Tue, Dec 16, 2014 at 10:17 AM, Hameed, Amir <Amir.Hameed_at_xerox.com> wrote:
> > Redo log file placement - In the non-ASM world, I am used to using
> > Managing multiple databases - In the non-ASM world, we allocate a
>
> Just treat "diskgroup" as a synonym for "mountpoint" and you're off to
> the races. Many concepts are transferable and many of the same
> tradeoffs exist in architectural decisions. It a good starting point.
>
> > ยท AU and stripe sizes - For an Oracle E-Business Suite type system,
>
> The default AU size and stripe sizes don't need tuning for most cases.
> Remember that ASM will automatically use the smaller stripe size for
> redo logs; you don't have to configure that. (It uses different
> stripe sizes for various file types on the same diskgroup.)
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Dec 17 2014 - 16:23:34 CET