New redo log sizing advisor in Oracle10g
Every DBA knows that the size of their redo logs is very important. Too small, and the frequent log switches tie-up the LGWR, ARCH and DBWR background processes. To large, and you risk loosing data during an instance crash.
Oracle 10g has introduced a new advisory utility that allows you to specify your optimal mean time to recovery (MTTR) recovery interval and uses this to suggest the optimal redo log size. In Oracle 10g the fast_start_mttr_target parameter is used. Oracle recommends using the fast_start_mttr_target initialization parameter to control the duration of startup after instance failure. With 10g, the Oracle database can now self-tune check-pointing to achieve good recovery times with low impact on normal throughput. You no longer have to set any checkpoint-related parameters. This method reduces the time required for cache recovery and makes the recovery bounded and predictable by limiting the number of dirty buffers and the number of redo records generated between the most recent redo record and the last checkpoint. Administrators specify a target (bounded) time to complete the cache recovery phase of recovery with the fast_start_mttr_target initialization parameter, and Oracle automatically varies the incremental checkpoint writes to meet that target. The target_mttr field of v$instance_recovery contains the MTTR target in effect. The estimated_mttr field of v$instance_recovery contains the estimated MTTR should a crash happen right away. For example, SQL> SELECT TARGET_MTTR, ESTIMATED_MTTR, CKPT_BLOCK_WRITES FROM V$INSTANCE_RECOVERY; TARGET_MTTR ESTIMATED_MTTR CKPT_BLOCK_WRITES ----------- -------------- ----------------- 37 22 209187 Whenever you set fast_start_mttr_target to a nonzero value, and while MTTR advisory is ON, Oracle Corporation recommends that you disable (set to 0) the following parameters: LOG_CHECKPOINT_TIMEOUT LOG_CHECKPOINT_INTERVAL FAST_START_IO_TARGET
In addition to the MTTR information in v$instance_recovery we also have an important column called optimal_logfile_size, and we can query for this value at any time. The value for optimal_logfile_size is expressed in megabytes and it changes frequently, based on the DML load on your database. For example, SQL> SELECT OPTIMAL_LOGFILE_SIZE FROM V$INSTANCE_RECOVERY; OPTIMAL_LOGFILE_SIZE -------------------- 256 If your database is relatively stable, then you can use this suggested size and rebuild your online redo log files to match the value. We would expect that a future version of Oracle will automate this and allow for dynamic re-sizing of online redo log files, but this is an issues because many Oracle systems expect the archived redo log files to always be the same size. |
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/7185924/viewspace-964691/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Redo Log之一:理解Oracle redo logOracle Redo
- undo log和redo log
- MySQL:Redo & binlogMySql
- mysql之 redo logMySql
- oracle redo log operationOracle Redo
- MySQL的Redo log 以及Bin logMySql
- oracle10g data guard(dg)__Adding or Dropping Online Redo Log FilesOracle
- standby redo log的理解
- redo_log_switch_date
- redo log file 優化優化
- Oracle redo log重組Oracle Redo
- Oracle Dump Redo Log FileOracle
- oracle10g data guard redo transport serviceOracle
- Oracle10g New Features(1)Oracle
- MySQL中的redo log和undo logMySql
- MySQL Undo Log和Redo Log介紹MySql
- Redo Log之二:遷移redo log到不同的儲存路徑
- redo的等待log file sync和log file parallel write和redo size設定Parallel
- 【Mysql】三大日誌 redo log、bin log、undo logMySql
- Archive Log模式下Redo Log、Check Point和Switch LogHive模式
- logminer工具對redo log或archive log的挖掘Hive
- MySQL 日誌系統 redo log、binlogMySql
- MySQL重做日誌(redo log)MySql
- MySQL redo log最佳化MySql
- (轉)老白的理解REDO LOG
- redo log日誌挖掘(二)
- redo log日誌挖掘(一)
- 修改oracle redo log的大小Oracle Redo
- 增大redo log檔案大小
- Oracle redo log 常見操作Oracle Redo
- LGWR writes redo log (117)
- 【轉】cannot allocate new log
- Oracle redo解析之-1、oracle redo log結構計算Oracle Redo
- 使用LOGMNR工具分析Oracle Redo Log和Archive Log教程Oracle RedoHive
- 【REDO】Archived redolog is (significant) smaller than the redologfileHiveNifi
- 聊聊Append、nologging和Redo LogAPP
- InnoDB文件筆記(二)—— Redo Log筆記
- MySQL中的redo log和checkpointMySql