Re: OEM 13c Metric for nologging

From: Nagaraj chk <nagaraj.chk_at_gmail.com>
Date: Wed, 17 Jan 2018 09:55:19 +0530
Message-ID: <CAG6s0C3PNhTvwz7gkZVb+_GmZTPTUdOfdT==rKSa8nuU+qn30w_at_mail.gmail.com>



Hi Rick,

thank you. Yes that's right, we are going to enable databases force logging,however since the database count is huge at first we need to identify the list of databases with objects in nologging and also as a proactive measure to monitor the newly build databases.

-Naga

On Mon, Jan 15, 2018 at 7:45 PM, Rich J <rjoralist3_at_society.servebeer.com> wrote:

> On 2018/01/15 05:02, Nagaraj chk wrote:
>
> In our environment most of the databases have few tables in nologging
> option. I like to know, do we have any monitoring metric in OEM to monitor
> the nologging objects or do i need to create any custom metric extension to
> monitor nologging ? Please suggest.
>
>
> This doesn't sound like a built-in metric, but it would be the simplest of
> metric extensions to make with a query of the LOGGING column of the
> DBA_TABLES view. The real question is, if logging is that important that
> it needs to be monitored, why isn't force logging used at the database
> level?
>
> My $.02,
> Rich
>

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Jan 17 2018 - 05:25:19 CET

Original text of this message