OraFAQ Forum: Performance Tuning » alert.log question

Home » RDBMS Server » Performance Tuning » alert.log question (Oracle DB 11, SLES 11)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

alert.log question [message #569222]

Tue, 23 October 2012 03:37

Shamall
Messages: 12
Registered: May 2012

Junior Member

Hi,

I want to count the numbers of for example messages like:
Checkpoint not complete
(maybe per minute or per hour)

But the ora log looks like this:

Wed Oct 17 18:19:03 2012
Archived Log entry 327763 added for thread 1 sequence 328789 ID 0x6dab8297 dest 1:
Thread 1 cannot allocate new log, sequence 328792
Checkpoint not complete
Wed Oct 17 18:19:07 2012
Completed checkpoint up to RBA [0x50351.2.10], SCN: 5851060
Checkpoint not complete

This messages is not in the same line with the date/time.

I need an idea how to script it or how to rewrite the log into the format
Wed Oct 17 18:19:07 2012 : Completed checkpoint up to RBA [0x50351.2.10], SCN: 5851060
Wed Oct 17 18:19:07 2012 : Checkpoint not complete

I hope you understood what I mean.

Confused

Report message to a moderator

Re: alert.log question [message #569223 is a reply to message #569222]

Tue, 23 October 2012 03:42

John Watson
Messages: 3174
Registered: January 2010
Location: Global Village

Senior Member

Something like this should do,
select MESSAGE_TEXT,ORIGINATING_TIMESTAMP from V$DIAG_ALERT_EXT where MESSAGE_TEXT like 'ORA-%';

Report message to a moderator

Re: alert.log question [message #582841 is a reply to message #569223]

Tue, 23 April 2013 01:34

nlnkapardi
Messages: 26
Registered: April 2013
Location: India

Junior Member

Hello Shamall

Hope you are Doing good !! Just came up with an Answer.Here is the Below Expalnation

this means Oracle wants to reuse a redo log file, but
the current checkpoint position is still in that log.
Point -1.) Oracle must wait until the checkpoint position passes that log. Because the
incremental checkpoint target never lags the current log tail by more than 90%
of the smallest log file size, this situation may be encountered if DBWR writes
too slowly, or if a log switch happens before the log is completely full,
or if log file sizes are too small.
Point -2 )When the database waits on checkpoints,redo generation is stopped until the
log switch is done.

So., Solution Will be Write a Basic Shell Script by grepping the Word like :Checkpoint not complete using Grep or awk
and pass it to another file if you need using >> operator and using Mailx send it your desired Destination.

Please Feel Free To get back to me

Regards
Kapardi

Report message to a moderator

Re: alert.log question [message #582876 is a reply to message #582841]

Tue, 23 April 2013 03:25

Michel Cadot
Messages: 54672
Registered: March 2007
Location: Nanterre, France, http://...

Senior Member
Account Moderator

This is COMPLETLY out of the question.
Please read it (and the other posts) BEFORE posting your answers.

Regards
Michel

Report message to a moderator

Previous Topic:	update xml eating up a lot of time
Next Topic:	checking the delete performance in the package

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Jun 18 20:32:26 CDT 2013

Total time taken to generate the page: 0.10293 seconds