Why still active? (was Re: lost of redo logs)

From: Jeff <jeff_at_work.com>
Date: Fri, 01 Mar 2002 13:44:52 GMT
Message-ID: <a5o0kk$80v$1@cronkite.cc.uga.edu>

In article <3c7f6e56.37955567_at_news.earthlink.net>, jeremy.russell_at_usa.net (Jeremy Russell) wrote:

>2. Not sure what you mean by current v active.

Oracle's definition of "active" in this context is that the redo log is still needed for recovery... ie., that it hasn't been archived off yet.

The thing that bothers me about this is that, from my brief experience, the previously "current" redo log remains "active" until another log switch occurs (perhaps several hours later), whereupon it becomes "inactive," and I'm not sure why that is, since the archiver should backup the archive log immediately after the switch from current. Anyone know why that would be?

Oracle 8.1.7.3, Solaris. Received on Fri Mar 01 2002 - 07:44:52 CST