Re: Database accidentally left in backup mode

From: Janine Sisk <janine_at_furfly.net>
Date: Mon, 15 Mar 2010 15:09:00 -0700
Message-Id: <FCE5DB7D-5E31-4D41-9418-2B433C7DBB15_at_furfly.net>

I wondered about that, but none of the drives are anywhere near full (sorry, should have said that before). I don't remember exactly where I sent the archivelogs to, I will have to dig a bit deeper on that.

janine

On Mar 15, 2010, at 2:59 PM, Jeremiah Wilton wrote:

> Your log_archive_dest_n is full, or the archiver is  not working for some other reason.  Everything will work again when you clear space for the archivelogs.
> 
> Regards,
> Jeremiah Wilton
> Blue Gecko, Inc.
> 
> On Mar 15, 2010, at 2:37 PM, Janine Sisk wrote:
> 

>> I've now tried ending the backup on each tablespace manually and they all hang, so clearly something is holding up the show. I looked at waits but I don't see anything directly about control files - a little Googling tells me that the log file switch errors probably mean my redo log is too small, but no indication that that would cause this problem. Am I missing something?
>>
>> SQL> select sid, event, seconds_in_wait from v$session_wait;
>>
>> SID EVENT
>> ---------- ----------------------------------------------------------------
>> SECONDS_IN_WAIT
>> ---------------
>> 29 log file switch (archiving needed)
>> 1198
>>
>> 30 log file switch (archiving needed)
>> 1198
>>
>> 33 log file switch (archiving needed)
>> 153
>>
>> 38 log file switch (archiving needed)
>> 153
>>
>> 42 log file switch (archiving needed)
>> 1198
>>
>> 48 log file switch (archiving needed)
>> 153
>>
>> 51 log file switch (archiving needed)
>> 253

---
Janine Sisk
President/CEO of furfly, LLC
503-693-6407





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

Received on Mon Mar 15 2010 - 17:09:00 CDT