Forcing Log Switches
Forcing Log Switches
A log switch occurs when LGWR stops writing to one redo log group and starts writing to another. By default, a log switch occurs automatically when the current redo log file group fills.
You can force a log switch to make the currently active group inactive and available for redo log maintenance operations. For example, you want to drop the currently active group, but are not able to do so until the group is inactive. You may also wish to force a log switch if the currently active group needs to be archived at a specific time before the members of the group are completely filled. This option is useful in configurations with large redo log files that take a long time to fill.
To force a log switch, you must have the ALTER SYSTEM privilege. Use the ALTER SYSTEM statement with the SWITCH LOGFILE clause.
The following statement forces a log switch:
ALTER SYSTEM SWITCH LOGFILE;
A log switch occurs when LGWR stops writing to one redo log group and starts writing to another. By default, a log switch occurs automatically when the current redo log file group fills.
You can force a log switch to make the currently active group inactive and available for redo log maintenance operations. For example, you want to drop the currently active group, but are not able to do so until the group is inactive. You may also wish to force a log switch if the currently active group needs to be archived at a specific time before the members of the group are completely filled. This option is useful in configurations with large redo log files that take a long time to fill.
To force a log switch, you must have the ALTER SYSTEM privilege. Use the ALTER SYSTEM statement with the SWITCH LOGFILE clause.
The following statement forces a log switch:
ALTER SYSTEM SWITCH LOGFILE;
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26477398/viewspace-2122495/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- LGWR,Log Switches, and Checkpoints
- Summary For Forcing The Database Open With `_ALLOW_RESETLOGS_CORRUPTION`Database
- SGA: allocation forcing component growth分析
- CF1993C Light Switches 題解
- 【MySQL】崩潰恢復問題解決:Forcing InnoDB RecoveryMySql
- Deal With "SGA: allocation forcing component growth" Wait Events_1270867.1AI
- ASM 翻譯系列第十三彈:ASM 高階知識 - Forcing the issueASM
- HyperLogLog
- Redis HyperLogLogRedis
- MySQL四種日誌binlog/redolog/relaylog/undologMySql
- Redis的HyperLogLogRedis
- DialogFragment以及AlertDialogFragmentFragment
- rman restore archivelog logRESTHive
- undo log和redo log
- Android中級教程之----Log圖文詳解(Log.v,Log.d,Log.i,Log.w,Log.e)!Android
- 【Mysql】三大日誌 redo log、bin log、undo logMySql
- 使用mysqlbinlog備份binlog 搭建Binlog ServerMySqlServer
- Log check error: Log file /var/log/messages is not readable!Error
- Archive Log模式下Redo Log、Check Point和Switch LogHive模式
- logminer工具對redo log或archive log的挖掘Hive
- ClassCastException Log4jLoggerFactory LoggerContexASTException
- MySQL error log和bin logMySqlError
- mysqlbinlog檢視binlogMySql
- Archivelog & Noarchivelog mode in RMANHive
- redis命令之-hyperloglogRedis
- openGauss 支援HyperLogLog
- 使用LOGMNR工具分析Oracle Redo Log和Archive Log教程Oracle RedoHive
- MySQL的Redo log 以及Bin logMySql
- Redis 集合統計(HyperLogLog)Redis
- 用adb logcat抓取logGC
- Mysql的redolog和binlogMySql
- From CORBA technology To Thrift technologyORB
- exclude Log4j print Log
- redis知識之HyperLogLogRedis
- nologging、force logging、supplemental log的理解
- mysql日誌:redo log、binlog、undo log 區別與作用MySql
- MySQL中redo log、undo log、binlog關係以及區別MySql
- 深入理解MySQL系列之redo log、undo log和binlogMySql