Re: Monitoring the "Checkpoint not complete" event
Date: Tue, 27 Oct 2009 05:23:48 +0700
About script monitor... You need to check "Checkpoint not complete" in alert log file
If you use Enterprise Manager, You can set
"Metric and Policy Settings" ->
at "Generic Alert Log Error" Metric
modify value to monitor "Checkpoint not complete" http://download.oracle.com/docs/cd/B19306_01/em.102/b25986/oracle_database.htm
if you don't have EM, you may make alert log error notification like http://www.dba-oracle.com/t_alert_log_monitoring_errors.htm
You can check, How often switch log at... SQL> alter session set nls_date_format='YYYY/MM/DD HH24:MI:SS'; SQL> select * from v$log_history order by FIRST_TIME; -- check first_time between 2 times.
If In normal time, your database often switches logfile... you have to tune
- Make DBGW faster: tune DBWR by enable ASYNC I/O, using DBGW I/O slaves (dbwr_io_slaves) or using multiple processes(db_writer_processes). - Add more redo log file.
- Re-create the log files with a larger size.
On Tue, Oct 27, 2009 at 2:19 AM, Radoulov, Dimitre <cichomitiko_at_gmail.com>wrote:
> >>> On Mon, Oct 26, 2009 at 6:29 PM, Radoulov, Dimitre wrote:
> >>> I'm trying to figure out how to implement an automated monitoring
> regarding the above mentioned "event".
> >>> When it happens the instance hang may become a problem and *I believe*
> that monitoring the single occurrence
> >>> of the "Checkpoint not complete" message in the alert log is not
> sufficient (the time between that message
> >>> and the following thread advance is quite important as well).
> >>> So what's the logic/how exactly you monitor the "Checkpoint not
> complete" event?
> >> On 26/10/2009 15.16, Surachart Opun wrote:
> >> "Checkpoint not complete" message in the alert log
> >> The database attempts to reuse an online redo log file and it can not.
> Hi Surachart Opun,
> thank you for your answer!
> I'm aware of the possible solutions. Moreover, I want to trigger a critical
> alert when an instance hangs
> because of this event. I'm not sure if only the monitoring of that message
> is sufficient
> and I would like to know how you have implemented (if implemented at all)