rman備份產生等待事件
最近資料庫升級後rman備份出現了很多等待事件
SQL> select * from v$version;
BANNER
------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE 11.2.0.3.0 Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
SQL>
SQL> SELECT sid,event FROM v$session WHERE wait_class#<>6;
SID EVENT
---------- ----------------------------------------------------------------
1165 Backup Restore Throttle sleep
1208 Backup Restore Throttle sleep
1292 Backup Restore Throttle sleep
1379 Backup Restore Throttle sleep
1552 Backup Restore Throttle sleep
2239 resmgr:cpu quantum
2542 SQL*Net message to client
查詢alert日誌資訊
Tue Oct 23 22:00:00 2012
Setting Resource Manager plan SCHEDULER[0x256B668]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Tue Oct 23 22:00:00 2012
Starting background process VKRM
Tue Oct 23 22:00:00 2012
VKRM started with pid=120, OS id=16419
Tue Oct 23 22:00:02 2012
Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Tue Oct 23 22:00:34 2012
Thread 1 advanced to log sequence 18849 (LGWR switch)
Current log# 1 seq# 18849 mem# 0: /oradata/finance/datafile/redo01.log
Current log# 1 seq# 18849 mem# 1: /oradata/finance/datafile/redo01_1.log
Tue Oct 23 22:00:38 2012
Archived Log entry 19993 added for thread 1 sequence 18848 ID 0x99d4983c dest 1:
Tue Oct 23 23:00:05 2012
End automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"
Tue Oct 23 23:30:10 2012
Thread 1 advanced to log sequence 18850 (LGWR switch)
Current log# 4 seq# 18850 mem# 0: /oradata/finance/datafile/redo04.log
Current log# 4 seq# 18850 mem# 1: /oradata/finance/datafile/redo04_4.log
Tue Oct 23 23:30:14 2012
Archived Log entry 19994 added for thread 1 sequence 18849 ID 0x99d4983c dest 1:
Wed Oct 24 01:17:07 2012
Thread 1 advanced to log sequence 18851 (LGWR switch)
Current log# 5 seq# 18851 mem# 0: /oradata/finance/datafile/redo05.log
Current log# 5 seq# 18851 mem# 1: /oradata/finance/datafile/redo05_5.log
Wed Oct 24 01:17:17 2012
Archived Log entry 19995 added for thread 1 sequence 18850 ID 0x99d4983c dest 1:
Wed Oct 24 02:00:00 2012
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager plan via parameter
Wed Oct 24 07:23:20 2012
從這裡可以看出來,因為SCHEDULER定時啟動和關閉資源管理的DEFAULT_MAINTENANCE_PLAN從而導致在晚上10點到2點Resource Manager plan處於啟用狀態,所有rman執行任務,Backup Restore Throttle sleep等待是因為Resource Manager plan啟用導致(使用SCHEDULER控制其啟用和關閉),很多情況下資料庫跑的應用比較單一,不是十分的需要啟動資源管理.
在11g中關閉方法如下:
1. Set the current resource manager plan to null (or another plan that is not restrictive):
alter system set resource_manager_plan='' scope=both;
2. Change the active windows to use the null resource manager plan (or other nonrestrictive plan) using:
execute dbms_scheduler.set_attribute('WEEKNIGHT_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('WEEKEND_WINDOW','RESOURCE_PLAN','');
3. Then, for each window_name (WINDOW_NAME from DBA_SCHEDULER_WINDOWS), run:
execute dbms_scheduler.set_attribute('<window name>','RESOURCE_PLAN','');
SQL> select WINDOW_NAME from DBA_SCHEDULER_WINDOWS;
WINDOW_NAME
------------------------------
WEEKNIGHT_WINDOW
WEEKEND_WINDOW
MONDAY_WINDOW
TUESDAY_WINDOW
WEDNESDAY_WINDOW
THURSDAY_WINDOW
FRIDAY_WINDOW
SATURDAY_WINDOW
SUNDAY_WINDOW
9 rows selected.
execute dbms_scheduler.set_attribute('WEEKNIGHT_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('WEEKEND_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('MONDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('TUESDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('WEDNESDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('THURSDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('FRIDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('SATURDAY_WINDOW','RESOURCE_PLAN','');
execute dbms_scheduler.set_attribute('SUNDAY_WINDOW','RESOURCE_PLAN','');
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/28211342/viewspace-2141191/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 【RMAN】RMAN備份至ASMASM
- RMAN備份概述
- 【RMAN】RMAN的備份保留策略
- RMAN備份恢復典型案例——RMAN備份&系統變慢
- RMAN備份進度
- rman 備份指令碼指令碼
- RMAN的備份原理
- rman 增量備份恢復
- Oracle RMAN備份實戰Oracle
- Oracle OCP(60):RMAN 備份Oracle
- RMAN備份恢復技巧
- 【rman備份策略】實驗
- 【RMAN】同時建立多個備份(建立多重備份)
- 【RMAN】在備庫執行rman備份時報錯RMAN-06820 ORA-17629
- RMAN備份詳解(轉載)
- [20190522]rman備份問題.txt
- RMAN 備份相關的概念
- 使用RMAN備份資料庫資料庫
- RMAN備份異機恢復
- oracle 12c rman備份pdbOracle
- 利用RMAN備份重建資料庫資料庫
- 分享Oracle Rman的備份指令碼Oracle指令碼
- RMAN備份恢復效能優化優化
- RMAN備份中發現壞塊
- RMAN備份與恢復測試
- RMAN加密備份的三種方式加密
- RMAN自動備份任務新增
- 【備份】RMAN中對控制檔案的幾種備份方法
- rman開啟備份優化對備份歸檔的影響優化
- Oracle 備份恢復篇之RMAN catalogOracle
- 揭秘ORACLE備份之----RMAN之五(CATALOG)Oracle
- rman備份archivelog出現ORA-19625Hive
- ORACLE DG從庫 Rman備份恢復Oracle
- Oracle RMAN備份以及壓縮原理分析Oracle
- rman備份異機恢復(原創)
- oracle10g RMAN增量備份策略Oracle
- 33、buffer_cache_3(redo的產生、LRBA、buffer cache裡的等待事件)事件
- 【RMAN】Oracle12c以後rman 備份恢復命令參考Oracle
- 【RMAN】在多租戶環境下的RMAN備份及恢復