ORACLE tsm 備份錯誤
使用TSM 備份出現如下錯誤
RMAN-03009: failure of backup command on ch00 channel at 01/26/2015 19:33:59
ORA-19502: write error on file "db_HZWSJ_2177_1_01_26", block number 1 (block size=8192)
ORA-27030: sk**rt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
ANS0326E (RC41) This node has exceeded its maximum number of mount points.
channel ch00 disabled, job failed on it will be run on another channel
channel ch01: finished piece 1 at 26-JAN-15
經查資料:
RMAN-03009: failure of backup command on ch00 channel at 01/26/2015 19:33:59
ORA-19502: write error on file "db_HZWSJ_2177_1_01_26", block number 1 (block size=8192)
ORA-27030: sk**rt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
ANS0326E (RC41) This node has exceeded its maximum number of mount points.
channel ch00 disabled, job failed on it will be run on another channel
channel ch01: finished piece 1 at 26-JAN-15
經查資料:
RMAN backup of Oracle database may fail with ANS0326E (RC41)
Technote (troubleshooting)
Problem(Abstract)
RMAN backup may fail unexpectedly with message ANS0326E (RC41), indicating that the maximum number of mount points exceeded.
Symptom
RMAN may terminate a channel with error
ORA-19511: Error received from media manager layer, error text:
ANS0326E (RC41) This node has exceeded its maximum number of mount points.
RMAN-12018: channel t4 disabled, job failed on it will be run on another channel.
This might be logged on processing of the second or of a following backup piece by this RMAN channel, although setting of MAXNUMMP is the same as the number of RMAN channels.
Cause
The Tivoli Storage Manager Server and the client (in this case the Data Protection for Oracle) work asynchronously after ending a session.
In case of a Library Server / Library Client configuration it might take longer to release a mountpoint. So, a new session, requesting a new mountpoint, exceeds the maximum number of mountpoints, set for this node.
Diagnosing the problem
The 'Maximum Mount Points Allowed (MAXNUMMP)' value can be found on the Node definition on TSM Server via the 'query node {nodename} f=d' command.
Resolving the problem
Increase / up to double the setting for MAXNUMMP for the Oracle node, in case the above issue is faced. Use this command:
>UPDate NOde {nodename} MAXNUMMP={value}
This will have no long-term side-effects as the Tivoli Data Protection option (in the above case the number of allocated RMAN channel) will throttle the resource use to the expected level.
Problem(Abstract)
RMAN backup may fail unexpectedly with message ANS0326E (RC41), indicating that the maximum number of mount points exceeded.
Symptom
RMAN may terminate a channel with error
ORA-19511: Error received from media manager layer, error text:
ANS0326E (RC41) This node has exceeded its maximum number of mount points.
RMAN-12018: channel t4 disabled, job failed on it will be run on another channel.
This might be logged on processing of the second or of a following backup piece by this RMAN channel, although setting of MAXNUMMP is the same as the number of RMAN channels.
Cause
The Tivoli Storage Manager Server and the client (in this case the Data Protection for Oracle) work asynchronously after ending a session.
In case of a Library Server / Library Client configuration it might take longer to release a mountpoint. So, a new session, requesting a new mountpoint, exceeds the maximum number of mountpoints, set for this node.
Diagnosing the problem
The 'Maximum Mount Points Allowed (MAXNUMMP)' value can be found on the Node definition on TSM Server via the 'query node {nodename} f=d' command.
Resolving the problem
Increase / up to double the setting for MAXNUMMP for the Oracle node, in case the above issue is faced. Use this command:
>UPDate NOde {nodename} MAXNUMMP={value}
This will have no long-term side-effects as the Tivoli Data Protection option (in the above case the number of allocated RMAN channel) will throttle the resource use to the expected level.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26764973/viewspace-1419577/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- TSM ORACLE 備份排程Oracle
- sap brtools發起oracle備份失敗,tsm備份軟體備份報錯Oracle
- TSM備份ANS0326E錯誤及解決
- TSM + Oracle備份出現問題Oracle
- TSM for Oracle備份指令碼及策略說明Oracle指令碼
- ORACLE 備份故障,原因是tsm密碼過期Oracle密碼
- 資料庫重啟,TSM不能備份,需要在TSM的客戶端(ORACLE)啟動TSM監控程式資料庫客戶端Oracle
- 基於tsm的oracle資料庫備份及恢復Oracle資料庫
- AIX 上配置完成TSM API後,備份DB2時報SQL2062N錯誤AIAPIDB2SQL
- TSM無法備份故障解決(續)
- TSM備份軟體實施步驟
- AIX上oracle匯出備份EXP-00056: 遇到 ORACLE 錯誤 600AIOracle
- oracle備份把日誌錯Oracle
- TSM+RMAN 自動備份指令碼 on aix指令碼AI
- IBM TSM備份軟體的安裝方法IBM
- TSM備份時因歸檔日誌丟失而導致備份失敗
- SqlServer NBU備份出現錯誤程式碼2SQLServer
- oracle rman備份時出現ORA-19502錯誤解決案例Oracle
- TSM中備份(Backup)和歸檔(Archive)的區別Hive
- oracle備份--離線備份Oracle
- 【RMAN】Oracle12c之後,rman備份Dataguard備端恢復可能出現邏輯錯誤Oracle
- oracle 備份Oracle
- oracle備份Oracle
- TSM單個資料庫無法備份故障一則資料庫
- 轉:IBM儲存備份管理軟體TSM介紹IBM
- Oracle備份時出現AIX系統的3D32B80D錯誤OracleAI3D
- Oracle RMAN 備份控制檔案報錯問題Oracle
- oracle的熱備份和冷備份Oracle
- TSM file client檔案備份,歸檔基本命令總結client
- 使用TSM備份30天前生成的檔案的指令碼指令碼
- Oracle備份及備份策略及基於Linux下 Oracle 備份策略(RMAN)OracleLinux
- Oracle 冷備份Oracle
- Oracle 熱備份Oracle
- oracle rac 備份Oracle
- ORACLE備份策略Oracle
- ORACLE 備份表Oracle
- ORACLE 錯誤Oracle
- Oracle 聯機備份 離線備份 物理備份 恢復Oracle