Re: Flashback_on disabled automatically

From: Rich Jesse <rjoralist_at_society.servebeer.com>
Date: Mon, 4 Jan 2010 13:31:44 -0600 (CST)
Message-ID: <326b60f40d6b0732550482199f4c6532.squirrel_at_society.servebeer.com>

It's been more than two years since I originally configured Grid Control -- and perhaps standalone Database Monitoring differs -- but GC rightly squawks at me with every ORA- error via the "Generic Alert Log Error" metric setting.

I believe I removed the warning threshold making every ORA-* error critical in GC's eyes. Perhaps this could help you as well. You'll need to be the judge of how that setting will affect your environment.

I also have a home-grown Perl script that monitors every log and trace for me that picks it up as well, just in case.

Rich

> On Jan 4, 2010, at 6:06 AM, John Hallas wrote:
>>
>> If I make the decision, based on business requirements and technical
>> reasons, that I want flashback logging to be enabled for a database
>> then I would expect that to remain the situation.
>> However Oracle can disable flashback and not really inform the user
>> at all. Yes there is a message in the alert log
>>
>> Errors in file /app/oracle/admin/FLASH10G/bdump/
>> flash10g_rvwr_22255.trc:
>> ORA-38701: Flashback database log 77 seq 201 thread 1: "+FRA/
>> flash10g/flashback/log_77.2579.702048581"
>> ORA-17503: ksfdopn:2 Failed to open file +PETRAFRA/flash10g/
>> flashback/log_77.2579.702048581
>> ORA-15012: ASM file '+FRA/flash10g/flashback/log_77.2579.702048581'
>> does not exist
>> Thu Nov 5 15:14:07 2009
>> *************************************
>> RVWR encountered an error when writing flashback database logs.
>> See error stack in alert log. To avoid crashing the instance,
>> this instance has turned off flashback database.
>> *************************************
>>
>> However that is very easily to miss and there is no OEM policy to
>> raise an alert.
>

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

Received on Mon Jan 04 2010 - 13:31:44 CST