symantec NBU 备份oracle 11g/user/openv/下的备份日志报错Recovery Manager: Release 11.2.0.3.0 - Production on Mon Sep 17 1
symantec NBU 备份Oracle 11g
/user/openv/下的备份日志报错
Recovery Manager: Release 11.2.0.3.0 - Production on Mon Sep 17 14:36:11 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: testdb (DBID=123456)
using target database control file instead of recovery catalog
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39> RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24> 25> 26> 27> 28> 29> 30> 31> 32> 33> 34> 35> 36> 37> 38> 39>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on ch00 channel at 09/17/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.
检查带库、和脚本都没有问题，网络解析也没问题
解决方法：
Ora企业建站系统内置模板引擎,支持代码分离,内置多种缓存机制,有效提高了页面响应时间,支持多种数据库(目前仅有Mysql数据库驱动类),支持3种路由(URL)模式 系统设置 管理帐号 清除缓存 企业管理 网站信息 类别管理 新闻动态 业务产品 其他管理产品模板 标签管理 导航管理 自定义页面 Ora 企业建站系统 v2.0 build 20110318 重构了整个系统 调整了缓存
symantec nbu在备份是需要调用oracle lib库文件，symantec bin目录下提供了此脚本
[oracle@testdb bin]$ pwd
/usr/openv/netbackup/bin
[oracle@testdb bin]$ ls oracle_link
oracle_link
[oracle@testdb bin]$ ./oracle_link
All Oracle instances should be shutdown before running this script.
Please log into the Unix system as the Oracle owner for running this script
Do you want to continue? (y/n) [n] y
LIBOBK path: /usr/openv/netbackup/bin
ORACLE_HOME: /oracle/app/oracle/product/11.2.0/db_1
Oracle version: 11.2.0.3.0
Platform type: x86_64
Linking LIBOBK:
ln -s /usr/openv/netbackup/bin/libobk.so64 /oracle/app/oracle/product/11.2.0/db_1/lib/libobk.so
Done
再次启动备份，，问题解决
