Database Monitoring Automation starts from simple steps with Grid Control

Imagine you have hundreds of databases, or more. Each time when you add a database to be monitored, you have to do an action to apply a monitoring template.

Why not apply a default template each time a new database target is discovered by Grid Control and avoid extra steps!

Here’s how!

Advertisements

Importance of monitoring

What could happen if you don’t monitor what’s happening?

CRASH.

Oracle 11.2.0.2+  new feature: if writes to a datafile fail, crash the database by default.

Go back to old ways:  by setting underscore parameter  _datafile_write_errors_crash_instance= false



This fix introduces a notable change in behaviour in that
from 11.2.0.2 onwards an I/O write error to a datafile will
now crash the instance.

Before this fix I/O errors to datafiles not in the system tablespace
offline the respective datafiles when the database is in archivelog mode.
This behavior is not always desirable. Some customers would prefer
that the instance crash due to a datafile write error.

This fix introduces a new hidden parameter to control if the instance
should crash on a write error or not:
  _datafile_write_errors_crash_instance 

With this fix:
 If _datafile_write_errors_crash_instance = TRUE (default) then
  any write to a datafile which fails due to an IO error causes
  an instance crash. 

 If _datafile_write_errors_crash_instance = FALSE then the behaviour
  reverts to the previous behaviour (before this fix) such that
  a write error to a datafile offlines the file (provided the DB is
  in archivelog mode and the file is not in SYSTEM tablespace in
  which case the instance is aborted)

Golden Gate monitoring framework

We were discussing with a few fellow DBAs how to monitor Golden Gate replication as a starting point for widely deployed systems.

Sure, there’s a chapter in the GG’s Adminisration guide and Oracle guys always refer to GGSCI command line tool, which you can use.

Yeah, you can..

But how about with a high number of databases?  Because there are lots of other things to do and time could be saved, if you had a utility kit with monitoring scripts.

So why nobody has provided essential scripts to monitor Golden Gate with the product itself?

  • Grid Control management pack support for Golden Gate is still a work in progress.
  • There’s GoldenGate director.. as an extra application (and needs a separate license).

There are some scripts from DBAs around the web:

  •  http://oracleabout.blogspot.com/2010/08/golden-gate-lag-monitoring.html

My idea:

Possible direction to add Golden Gate monitoring into monitoring frameworks:

Not a bad idea?