Question on LOGGING which not getting enabled permanently
From: Apps DBA <dbaorapps_at_gmail.com>
Date: Mon, 21 Jan 2013 16:31:08 +0530
Message-ID: <CAHvOz+yZbp6mMjnTh+2vUc=oL-g0R0vBWDWUJAwiiEw7T6V9WQ_at_mail.gmail.com>
Hi Gurus,
We have a scenario in the database related to LOGGING. We enabled LOGGING option for a table and had altered the INITRANS option from 2 to 11 and 10 for
Table and Indexes respectively. What we found that for all the existing partitions and indexes, the LOGGING got enabled but for any new partitions NOLOGGING still coming out to be.
If NOLOGGING continue to remain, then it may impact the DB backup as well as future recoveries. Has anyone come across this or what other changes have to be done? Please advice.
Date: Mon, 21 Jan 2013 16:31:08 +0530
Message-ID: <CAHvOz+yZbp6mMjnTh+2vUc=oL-g0R0vBWDWUJAwiiEw7T6V9WQ_at_mail.gmail.com>
Hi Gurus,
We have a scenario in the database related to LOGGING. We enabled LOGGING option for a table and had altered the INITRANS option from 2 to 11 and 10 for
Table and Indexes respectively. What we found that for all the existing partitions and indexes, the LOGGING got enabled but for any new partitions NOLOGGING still coming out to be.
If NOLOGGING continue to remain, then it may impact the DB backup as well as future recoveries. Has anyone come across this or what other changes have to be done? Please advice.
Thanks,
A.Shiva
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Jan 21 2013 - 12:01:08 CET