Re: Database accidentally left in backup mode

From: Jeremiah Wilton <jwilton_at_bluegecko.net>
Date: Mon, 15 Mar 2010 14:59:28 -0700
Message-Id: <6782F43B-7910-4B7C-9548-49E7BC365EE3_at_bluegecko.net>

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

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

Received on Mon Mar 15 2010 - 16:59:28 CDT