Re: Redo per transaction inconsistency when running SLOB
From: Jonathan Lewis <jlewisoracle_at_gmail.com>
Date: Tue, 28 Apr 2020 16:57:27 +0100
Message-ID: <CAGtsp8nfaWs31qdY-gsvdCLCh+-ywcpW-+6ivgZFs9r6UejWeA_at_mail.gmail.com>
Date: Tue, 28 Apr 2020 16:57:27 +0100
Message-ID: <CAGtsp8nfaWs31qdY-gsvdCLCh+-ywcpW-+6ivgZFs9r6UejWeA_at_mail.gmail.com>
Paul,
Thanks for the update.
Nice to know it wasn't some horrid, exotic detail waiting to cause chaos.
Regards
Jonathan Lewis
On Tue, Apr 28, 2020 at 12:00 PM Paul Houghton <Paul.Houghton_at_uis.cam.ac.uk> wrote:
> Thanks Jonathan (and the others who replied).
>
>
>
> I did one update and compared the log dumps just for that (Mostly to have
> a look at them). It is clear both from the dumps, and
> v$database.supplemental* that it is supplemental logging that is the
> culprit. It is switched off in the “fast” database. It is on in production
> because we have a logical standby. Your other email that mentioned reasons
> for extra logging made me realise that is what it would likely be.
>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Apr 28 2020 - 17:57:27 CEST