Re: Root cause for ORA-00471
Date: Tue, 9 Jul 2024 09:56:20 -0300
Message-ID: <CAJdDhaPJQNxD3pUQL93fUXnt_6YmOW3+ktTNsGGUcGuhbF8eHg_at_mail.gmail.com>
Hi all,
I think that looking for the disk throughput metric, is a good way to
measure how much data can be transferred to and from a storage device in a
given amount of time.
Regards
Eriovaldo
Em seg., 8 de jul. de 2024 às 20:43, Mladen Gogala <gogala.mladen_at_gmail.com> escreveu:
> On 7/8/24 9:30 AM, Chris Taylor wrote:
>
> For the redo log question (if 3 groups of 200MB each are enough) you can
> check the log switch frequency. Oracle recommends trying to hit 4-5 redo
> log switches per hour. (*ref: **Can Not Allocate Log Doc ID 1265962.1*)
>
> So if your redo log switches are around 15 every hour (for example),
> they're not large enough.
>
> You can check your log switches with this script:
>
> Script To Find Redolog Switch History And Find Archivelog Size For Each
> Instances In RAC (Doc ID 2373477.1)
>
> Depending on your hardware age and storage, don't be afraid to have large
> redo logs. On a very busy medical system I used to work on, we had 2G redo
> logs to get the redo log switches down to 4-5 per hour.
>
> HTH,
> Chris
>
> There is a problem with large redo logs: standby databases. If you have a
> remote standby, then your archives go over the WAN. And that might be
> problematic with a slow network. One of my previous employers used to have
> the primary in NYC and the standby in Louisville, KY. The WAN was slower
> than 1Gb/sec, so 2GB redo logs were out of the question. I had to live with
> approximately 10 - 15 switches per hour.
>
>
> --
> Mladen Gogala
> Database Consultant
> https://dbwhisperer.wordpress.com
> -- http://www.freelists.org/webpage/oracle-l
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Jul 09 2024 - 14:56:20 CEST