Re: standby databases and memory consumption

From: Niall Litchfield <niall.litchfield_at_gmail.com>
Date: Tue, 7 Jan 2014 08:18:06 +0000
Message-ID: <CABe10sZ4hrSaGdAV_9AThcrVnP9R=q+NDNja6KLP9Stej2WSgg_at_mail.gmail.com>

Absolutely agree. You should also consider some planned periods of running from the standby so you know

1. it works
2. how to switch everything
3. that your docs/processes can be followed by someone else. On Jan 7, 2014 2:10 AM, "De DBA" <dedba_at_tpg.com.au> wrote:

> That'll probably work, however I tend to keep them the same as the
> production database, if possible. When the roles are switched, the memory
> parameters must be adjusted to suit the new role. No problem if they are
> kept the same, but an extra point on the check list to be executed in a
> (usually) stressful situation.. and easy to overlook ;)
>
> Cheers,
> Tony
>
> On 07/01/14 10:12, Andy Gmail wrote:
>
>> Start with 1g sga and 512m PGA.
>>
>> Sent from my iPhone
>>
>> On Jan 6, 2014, at 5:36 PM, Maureen English <maureen.english_at_alaska.edu>
>>> wrote:
>>>
>>> Anyone willing to share what they set pga and sga values to for a
>>> standby database?
>>>
>>> We currently have ours set to the same as our primary databases, but are
>>> looking at
>>> finding what minimum values we can use for as long as the database is in
>>> standby mode.
>>>
>>> - Maureen
>>> --
>>> http://www.freelists.org/webpage/oracle-l
>>>
>>>
>>> --
>> http://www.freelists.org/webpage/oracle-l
>>
>>
>>
>>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

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

Received on Tue Jan 07 2014 - 09:18:06 CET