Home » RDBMS Server » Server Administration » LOG SWITCH CHECK POINTS (oracle 10g on Oracle linux 5.5)
|
Re: LOG SWITCH CHECK POINTS [message #599896 is a reply to message #599893] |
Wed, 30 October 2013 02:13   |
John Watson
Messages: 8976 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
Yes, if it happens. But it usually does not happen. In releases < 8.1, a log switch forced a full check point. In releases >= 8.1, it does not. If the next group to be used is still ACTIVE, then you will get log switch checkpoint (and a checkpoint incomplete message in the alert log) to make the log inactive so that LGWR can witch into it, but this should not happen if you have enough groups.
--
update: You quoted that sentence. From where did you copy it?
[Updated on: Wed, 30 October 2013 02:16] Report message to a moderator
|
|
|
|
|
Re: LOG SWITCH CHECK POINTS [message #599899 is a reply to message #599897] |
Wed, 30 October 2013 02:31   |
 |
rsb.oracle
Messages: 37 Registered: April 2013 Location: Chennai
|
Member |
|
|
Hi john;
You quoted that sentence. From where did you copy it?
Here .. http://oracleinaction.com/checkpoints/
Whenever dirty blocks are written to datafiles, it allows oracle
to reuse a redo log : A redo log can't be reused until DBWR writes all the dirty blocks protected by that logfile to disk.
If we attempt to reuse it before DBWR has finished its checkpoint,
we get the following message in alert log : Checkpoint not complete.
[Updated on: Wed, 30 October 2013 02:31] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Fri May 02 13:50:46 CDT 2025
|