Re: private strand flush not complete in alert log
From: Timur Akhmadeev <timur.akhmadeev_at_gmail.com>
Date: Thu, 7 Apr 2016 13:33:35 +0300
Message-ID: <CACGsLCJ1dssTQ6kfAL0k3B7Pt5QQ3hJConPxMUWqsN2-6WbMdQ_at_mail.gmail.com>
On Thu, Apr 7, 2016 at 11:57 AM, Pausch Manfred < Manfred.Pausch_at_tgw-group.com> wrote:
Date: Thu, 7 Apr 2016 13:33:35 +0300
Message-ID: <CACGsLCJ1dssTQ6kfAL0k3B7Pt5QQ3hJConPxMUWqsN2-6WbMdQ_at_mail.gmail.com>
On Thu, Apr 7, 2016 at 11:57 AM, Pausch Manfred < Manfred.Pausch_at_tgw-group.com> wrote:
> We also had “cannot allocate new log” together with “checkpoint not
> complete”.
>
> But seems that we got rid of this by increasing db_writer_processes from 2
> to 4.
>
> (we did the change yesterday, so we still observing this)
>
>
What is your redo logs configuration? Why haven't you first increased their
size in response to "checkpoint incomplete" waits?
If you need some guesstimate how much more do you need to add, I've written a
query <https://www.pythian.com/blog/do-you-have-enough-redo/> to give an
idea based on historical data.
-- Regards Timur Akhmadeev -- http://www.freelists.org/webpage/oracle-lReceived on Thu Apr 07 2016 - 12:33:35 CEST