NBU備份數據庫時ORA-27211錯誤如何處理

這篇文章主要介紹NBU備份數據庫時ORA-27211錯誤如何處理，文中介紹的非常詳細，具有一定的參考價值，感興趣的小伙伴們一定要看完！

安裝配置Veritas Netbackup 7.0備份Oracle 11G數據庫時很快報6號錯誤，查NBU的輸出日志發現產生了一個ORA-27211的錯誤。具體錯誤信息如下：

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03009: failure of allocate command on ch00 channel at 09/21/2012 14:36:13

ORA-19554: error allocating device, device type: SBT_TAPE, device name: 

ORA-27211: Failed to load Media Management Library

Additional information: 2

RMAN> RMAN> 

Recovery Manager complete.

Script /usr/openv/hot_database_backup.sh

==== ended in error on Fri Sep 21 14:36:13 CST 2012 ====

在數據庫端RMAN備份時，也會遇到錯誤

oracle@dbsvr$ rman nocatalog target sys/oracle@test
Recovery Manager: Release 11.2.0.3.0 - 64bit Production
Copyright (c) 1982, 2011, Oracle. 

All rights reserved.
connected to target database: TRAIN (DBID=678348214)
using target database controlfile instead of recovery catalog
RMAN> run {
2> allocate channel ch00 type 'SBT_TAPE';
3> backup full database;
4>release channel ch00;
5>}
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ch00 channel at 11/13/2005 15:10:28
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 25

6號錯誤是NBU中比較常見的典型錯誤,關于6號錯誤的幾種情況分析,可以參見我之前的博文<netbackup7.0備份6號錯誤解析> http://xjsunjie.blog.51cto.com/999372/935347,當然今天我們遇到的這個錯誤是另外一種情況,具體問題具體分析.

檢查完NBU的輸出日志后,我們再查看一下備份時由Oracle產生的日志：

$ more data_ora_0579.trc

Oracle process number: 2917

Unix process pid: 5244, p_w_picpath: oracletrain@db

*** ACTION NAME:(0000001 STARTED1) 2012-09-21 14:36:28.230

*** SERVICE NAME:() 2012-09-21 14:36:28.230

*** SESSION ID:(160.7) 2012-09-21 14:36:28.230

SKGFQ OSD: Error in function sbtinit on line 4381

SKGFQ OSD: Look for SBT Trace messages in file  /oracle/app/oracle/product/11.2.0/admin/train/udump/sbtio.log

SBT Initialize failed for oracle.static

從上面的日志可以看出，這是由于備份時sbtinit失敗所引起的。用Oracle的測試工具試試：

oracle@db$ sbttest /etc/hosts

The sbt function pointers are loaded from oracle.static library.

libobk.so could not be loaded. Check that it is installed

經過分析，主要原因是libobk.so這個文件在Oracle中不存在引起的備份失敗錯誤。

下面我們可以這樣來操作

oracle@db$ ln -s /usr/openv/netbackup/bin/libobk.so64   /oracle/app/oracle/product/11.2.0/db_1/lib/libobk.so

將NBU中的libobk.so64文件做一個軟鏈接到ORACLE相應目錄下

再來測試一下：

oracle@db$ sbttest /etc/hosts

The sbt function pointers are loaded from libobk.so library.

-- sbtinit succeeded

-- sbtinit (2nd time) succeeded

sbtinit: Media manager supports SBT API version 2.0

sbtinit: Media manager is version 5.0.0.0

sbtinit: vendor description string=Veritas NetBackup for Oracle - Release 7.0 (2011020316)

sbtinit: allocated sbt context area of 8 bytes

sbtinit: proxy copy is supported

-- sbtinit2 succeeded

-- regular_backup_restore starts ................................

或者在NBU的BIN目錄下執行ORACLE_LINK腳本也可以實現。

再在NBU里進行該策略的備份，發現已經可以正常備份了。

注意：提示說在運行腳本前ORACLE實例需關閉，如果你是ORACLE 9i以上的版本，這個操作是可以在線直接做的。

以上是“NBU備份數據庫時ORA-27211錯誤如何處理”這篇文章的所有內容，感謝各位的閱讀！希望分享的內容對大家有幫助，更多相關知識，歡迎關注億速云行業資訊頻道！