zt_Resolving Shutdown Immediate Hang Situations_shutdown immediate關庫慢
作為dba在維護資料庫時,停機維護多為家常便飯.這不,前幾日測試庫由於併發使用者過多,導致關庫異常緩慢.今天閱讀blog發現一
則相當不錯的文章,摘錄於此;供後備;
連結:
http://askdba.org/weblog/2008/05/shutdown-immediate-hang-2/
(注:此文是2008年發行,而我測試版本是oracle11g)
本著知行合一,自己也測試一番;
---開啟一session,建表並插入多條記錄,未提交
SQL> create table t_big(a int);
則相當不錯的文章,摘錄於此;供後備;
連結:
http://askdba.org/weblog/2008/05/shutdown-immediate-hang-2/
(注:此文是2008年發行,而我測試版本是oracle11g)
本著知行合一,自己也測試一番;
---開啟一session,建表並插入多條記錄,未提交
SQL> create table t_big(a int);
Table created.
SQL> insert into t_big select level from dual connect by level<=5e5;
500000 rows created.
SQL> insert into t_big select level from dual connect by level<=5e5;
500000 rows created.
---開啟sysdba session,執行shutdown immediate
---檢視alert
Wed Jan 09 13:38:31 2013
Shutting down instance (immediate) --關閉例項
Stopping background process SMCO
Shutting down instance: further logons disabled
Wed Jan 09 13:38:36 2013
Stopping background process CJQ0 ---關閉後臺程式
Stopping background process QMNC
Stopping background process MMNL
Stopping background process MMON
License high water mark = 47
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
Wed Jan 09 13:38:41 2013
SMON: disabling tx recovery --禁用smon事務恢復 也可用event事件來禁用smon tx recovery event=”10513 trace name context forever, level 2″,拉起庫後移除此引數
SMON: disabling cache recovery
Wed Jan 09 13:38:45 2013
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 91
Successful close of redo thread 1
Wed Jan 09 13:39:12 2013
Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Wed Jan 09 13:39:14 2013
Stopping background process VKTM:
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Wed Jan 09 13:39:21 2013
Instance shutdown complete
Wed Jan 09 13:38:31 2013
Shutting down instance (immediate) --關閉例項
Stopping background process SMCO
Shutting down instance: further logons disabled
Wed Jan 09 13:38:36 2013
Stopping background process CJQ0 ---關閉後臺程式
Stopping background process QMNC
Stopping background process MMNL
Stopping background process MMON
License high water mark = 47
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
Wed Jan 09 13:38:41 2013
SMON: disabling tx recovery --禁用smon事務恢復 也可用event事件來禁用smon tx recovery event=”10513 trace name context forever, level 2″,拉起庫後移除此引數
SMON: disabling cache recovery
Wed Jan 09 13:38:45 2013
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 91
Successful close of redo thread 1
Wed Jan 09 13:39:12 2013
Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Wed Jan 09 13:39:14 2013
Stopping background process VKTM:
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Wed Jan 09 13:39:21 2013
Instance shutdown complete
-----繼續在上述sysdba session,執行startup,並檢視alert
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as D:\oracle11g_64bit\product\11.2.0\dbhome_1\RDBMS
Autotune of undo retention is turned on.
IMODE=BR
PMON started with pid=2, OS id=7196 --pmon開啟程式
Wed Jan 09 13:50:18 2013
VKTM started with pid=3, OS id=7396 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Wed Jan 09 13:50:18 2013
GEN0 started with pid=4, OS id=13600 --開啟各種程式
Wed Jan 09 13:50:18 2013
DIAG started with pid=5, OS id=5204
Wed Jan 09 13:50:18 2013
DBRM started with pid=6, OS id=9044
Wed Jan 09 13:50:18 2013
PSP0 started with pid=7, OS id=11972
Wed Jan 09 13:50:18 2013
DIA0 started with pid=8, OS id=5188
Wed Jan 09 13:50:18 2013
MMAN started with pid=9, OS id=4340
Wed Jan 09 13:50:18 2013
DBW0 started with pid=10, OS id=4808
Wed Jan 09 13:50:18 2013
LGWR started with pid=11, OS id=13148
Wed Jan 09 13:50:18 2013
CKPT started with pid=12, OS id=10972
Wed Jan 09 13:50:18 2013
SMON started with pid=13, OS id=4608
Wed Jan 09 13:50:18 2013
RECO started with pid=14, OS id=8800
Wed Jan 09 13:50:18 2013
MMON started with pid=15, OS id=8400
Wed Jan 09 13:50:18 2013
MMNL started with pid=16, OS id=3964
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = D:\oracle11g_64bit
Wed Jan 09 13:50:19 2013
ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 1332056859
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Wed Jan 09 13:50:24 2013
ALTER DATABASE OPEN
Thread 1 opened at log sequence 91
Current log# 7 seq# 91 mem# 0: D:\ORACLE11G_64BIT\ORADATA\ORCL\REDO07.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery ----開啟快取恢復
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery ---開啟事務恢復
Database Characterset is AL32UTF8
No Resource Manager plan active
Starting background process QMNC
Wed Jan 09 13:50:29 2013
QMNC started with pid=20, OS id=9512
Completed: ALTER DATABASE OPEN
Wed Jan 09 13:50:35 2013
Starting background process CJQ0
Wed Jan 09 13:50:35 2013
CJQ0 started with pid=22, OS id=7140
Wed Jan 09 13:50:18 2013
VKTM started with pid=3, OS id=7396 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Wed Jan 09 13:50:18 2013
GEN0 started with pid=4, OS id=13600 --開啟各種程式
Wed Jan 09 13:50:18 2013
DIAG started with pid=5, OS id=5204
Wed Jan 09 13:50:18 2013
DBRM started with pid=6, OS id=9044
Wed Jan 09 13:50:18 2013
PSP0 started with pid=7, OS id=11972
Wed Jan 09 13:50:18 2013
DIA0 started with pid=8, OS id=5188
Wed Jan 09 13:50:18 2013
MMAN started with pid=9, OS id=4340
Wed Jan 09 13:50:18 2013
DBW0 started with pid=10, OS id=4808
Wed Jan 09 13:50:18 2013
LGWR started with pid=11, OS id=13148
Wed Jan 09 13:50:18 2013
CKPT started with pid=12, OS id=10972
Wed Jan 09 13:50:18 2013
SMON started with pid=13, OS id=4608
Wed Jan 09 13:50:18 2013
RECO started with pid=14, OS id=8800
Wed Jan 09 13:50:18 2013
MMON started with pid=15, OS id=8400
Wed Jan 09 13:50:18 2013
MMNL started with pid=16, OS id=3964
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = D:\oracle11g_64bit
Wed Jan 09 13:50:19 2013
ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 1332056859
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Wed Jan 09 13:50:24 2013
ALTER DATABASE OPEN
Thread 1 opened at log sequence 91
Current log# 7 seq# 91 mem# 0: D:\ORACLE11G_64BIT\ORADATA\ORCL\REDO07.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery ----開啟快取恢復
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery ---開啟事務恢復
Database Characterset is AL32UTF8
No Resource Manager plan active
Starting background process QMNC
Wed Jan 09 13:50:29 2013
QMNC started with pid=20, OS id=9512
Completed: ALTER DATABASE OPEN
Wed Jan 09 13:50:35 2013
Starting background process CJQ0
Wed Jan 09 13:50:35 2013
CJQ0 started with pid=22, OS id=7140
另:event=”10061 trace name context forever, level 10″ --暫停smon clear up temporary segment
再次說明,oracle不同版本之間的特性一直在變化,一定要注意;
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/9240380/viewspace-752371/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 資料庫無法shutdown immediate的案例資料庫
- shutdown immediate 持久無法關閉資料庫之解決方案資料庫
- shutdown immediate物理備庫長時間無法關閉案列
- oracle 正常關閉shutdown immediate與開啟open資料庫alertOracle資料庫
- 11G的SYS連線阻止SHUTDOWN IMMEDIATE關閉資料庫資料庫
- shutdown immediate 太慢,需要進行程式查殺行程
- shutdown immediate alert出現SHUTDOWN: waiting for active calls to complete.AI
- ORA-01089: immediate shutdown in progress - no operations are permittedMIT
- Shutdown immediate命令長時間等待分析一例
- 資料庫shutdown immediate,control.ctl 檔案不能刪除資料庫
- OGG OCI Error ORA-01089: immediate shutdown in progressError
- DML_LOCKS設定為0導致SHUTDOWN IMMEDIATE失敗
- 【YashanDB知識庫】資料庫審計shutdown immediate操作導致資料庫異常退出資料庫
- 【Shutdown】同一會話存在未提交事務時使用immediate選項無法關閉資料庫會話資料庫
- 因歸檔日誌無法歸檔造成的 oracle shutdown immediate無法關閉Oracle
- Oracle OCP 1Z0 053 Q77(ASM&Shutdown Immediate)OracleASM
- ORA-01097錯誤解決辦法及探索shutdown immediate
- Oracle OCP IZ0-053 Q687(ASM Shutdown immediate when users connected)OracleASM
- EXECUTE IMMEDIATE dynamic sql in procedureSQL
- execute immediate 語法小結
- initially immediate 與 initially deferred
- execute immediate的簡單用法(oracle)Oracle
- BCSphere入門教程01:Immediate Alert
- constraint deferrable immediate checkAI
- EXECUTE IMMEDIATE 呼叫動態過程
- EXECUTE IMMEDIATE 儲存過程中 許可權不足及EXECUTE IMMEDIATE的除錯避坑儲存過程除錯
- transactional replication 的immediate_sync屬性
- 儲存過程中慎用 execute immediate儲存過程
- 資料庫日誌中Immediate Kill Session錯誤解決方法資料庫Session
- Oracle動態執行語句(Execute Immediate)Oracle
- 動態 SQL、EXECUTE IMMEDIATE、using、into、returningSQL
- EXECUTE IMMEDIATE動態SQL的使用總結SQL
- 複習execute immediate動態sql語法SQL
- ue修改datafile資料檔案導致shutdown immediate失敗一例_ora-01208
- shutdown命令被job程式hang住
- Oracle EXECUTE IMMEDIATE語句裡面的引號處理Oracle
- 儲存過程執行EXECUTE IMMEDIATE沒反應儲存過程
- 常見問題--表的約束initially immediate 理解