Re: CDB Monitoring

Thanks. Show stoppers is exactly what I am after here. I will work through some of these items.

On Fri, Jan 12, 2024 at 9:18 AM Jay Hostetter <hostetter.jay_at_gmail.com> wrote:

> Here are some basic things we monitor at the CDB level, because it covers
> all PDBs as well:
>
> Outstanding alerts (dba_outstanding_alerts)
> Recovery destination
> Blocked sessions
> Asm disk status
> Offline files
> Invalid indexes
> Block corruption
> Waiting sessions
> Last call ET for sessions
> PDB plug in violations
> Autoextend limits
> Asm free space
> Resource limits
> Archive log backups
> File backups
> Database jobs
> Scheduler jobs
> Password expiry
> Unrecoverable files
>
> These are some of the things that we have learned can become “show
> stoppers”.
>
> Regards,
> Jay
> Sent from my iPhone
>
> > On Jan 11, 2024, at 4:35 PM, Ethan Post <post.ethan_at_gmail.com> wrote:
> >
> > 
> > Most of my custom monitoring operates from within each PDB. From the CDB
> side I am watching tablespaces. What other things which can only be seen
> from CDB are critical for monitoring? Any ideas are welcome.
> >
> > Thanks
>

--
http://www.freelists.org/webpage/oracle-l