I just noticed that using ALTER SYSTEM SWITCH LOGFILE is not causing a
checkpoint. Which cause the last redo group to remain archived but active.
I had to force a checkpoint to get it to inactive state. The docs state:
The SWITCH LOGFILE clause lets you explicitly force Oracle to begin writing
to a new redo log file group, regardless of whether the files in the current
redo log file group are full. When you force a log switch, Oracle begins to
perform a checkpoint. Oracle returns control to you immediately rather than
when the checkpoint is complete. To use this clause, your instance must have
the database open.
But I am sitting here looking tailing my alert log and no checkpoint occurs
till I force it. Is this a bug? 8.1.6.0 AIX (I know I am patching soon!)
- Ethan
- http://www.geocities.com/epost1
------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain
privileged, confidential, or proprietary information that is exempt from disclosure
under law. If you have received this message in error, please inform us promptly by
reply e-mail, then delete the e-mail and destroy any printed copy. Thank you.
==============================================================================
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Post, Ethan
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
