oracle恢复异常处理

问题现象:

RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12> 13> 14> 15> 16> 17> 18> 19> 20> 21> 22> 23> 24>

using target database control file instead of recovery catalog

allocated channel: ch01

channel ch01: SID=1513 device type=SBT_TAPE

channel ch01: NMDA Oracle v19.8.0.1

allocated channel: ch02

channel ch02: SID=1549 device type=SBT_TAPE

channel ch02: NMDA Oracle v19.8.0.1

allocated channel: ch03

channel ch03: SID=1585 device type=SBT_TAPE

channel ch03: NMDA Oracle v19.8.0.1

allocated channel: ch04

channel ch04: SID=1621 device type=SBT_TAPE

channel ch04: NMDA Oracle v19.8.0.1

allocated channel: ch05

channel ch05: SID=1657 device type=SBT_TAPE

channel ch05: NMDA Oracle v19.8.0.1

allocated channel: ch06

channel ch06: SID=1693 device type=SBT_TAPE

channel ch06: NMDA Oracle v19.8.0.1

allocated channel: ch07

channel ch07: SID=1729 device type=SBT_TAPE

channel ch07: NMDA Oracle v19.8.0.1

allocated channel: ch08

channel ch08: SID=1765 device type=SBT_TAPE

channel ch08: NMDA Oracle v19.8.0.1

sql statement: alter session set nls_date_format="yyyy-mm-dd hh24:mi:ss"

released channel: ch01

released channel: ch02

released channel: ch03

released channel: ch04

released channel: ch05

released channel: ch06

released channel: ch07

released channel: ch08

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

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

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

RMAN-03002: failure of send command at 04/09/2024 08:50:44

ORA-19559: error sending device command: NB_ORA_CLIENT=ebsdevtest

ORA-19557: device error, device type: SBT_TAPE, device name:

ORA-27194: skgfdvcmd: sbtcommand returned error

ORA-19511: Error received from media manager layer, error text:

sbtcommand: Unable to obtain the server parameter. (100:111:2)

解决排查步骤:

  1. 检查netbackup状态是否正常

root 6992 65497 0 09:13 pts/1 00:00:00 grep --color=auto netbackup

root 11755 1 0 Apr07 ? 00:00:01 /usr/openv/netbackup/bin/vnetd -proxy inbound_proxy -number 0

root 11756 1 0 Apr07 ? 00:00:02 /usr/openv/netbackup/bin/vnetd -proxy outbound_proxy -number 0

root 11814 1 0 Apr07 ? 00:00:09 /usr/openv/netbackup/bin/vnetd -standalone

root 11819 1 0 Apr07 ? 00:00:02 /usr/openv/netbackup/bin/bpcd -standalone

root 11907 1 0 Apr07 ? 00:00:11 /usr/openv/netbackup/bin/nbdisco

  1. 由于之前安装过Dell Networker客户端,检查是否存在,如果存在卸载

rpm -qa | grep lgto

lgtonmda-19.8.0.1-1.x86_64

lgtoclnt-19.8.0.1-1.x86_64

卸载后依然存在问题

  1. 可能是NBU跟oracle lib库关联异常(该环境oracle是拷贝过来)

oraprod@testdb bin$ pwd

/usr/openv/netbackup/bin

oraprod@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: /u01/app/oracle/product/11.2.0/db_1

Oracle version: 11.2.0.4.0

Platform type: x86_64

Linking LIBOBK:

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

Done

重新执行恢复,成功恢复

相关推荐
这个DBA有点耶1 小时前
AI写的SQL跑崩了生产库,这锅谁背?
数据库·人工智能·程序员
镜舟科技2 小时前
Databricks 再提 LTAP,AI 时代的数据底座为何重回大一统叙事?
数据库·架构·agent
Databend3 小时前
从湖仓升级为 Agent 时代的数据控制面,Snowflake 和 Databricks 有哪些布局
大数据·数据库·agent
ClouGence6 小时前
SQL Server CDC 能放到 Always On 备库读吗?一文讲透原理与实践
数据库·sql server
先吃饱再说1 天前
存储的进化:从 MySQL 到浏览器缓存,数据到底住在哪?
数据库
Nturmoils1 天前
字段太多看不全,ksql 的展开模式和输出控制怎么用
数据库·后端
Databend1 天前
Agent 轨迹分析与归因的数据工程实践
大数据·数据库·agent
这个DBA有点耶1 天前
SQL改写进阶:标量子查询的“隐形代价”与消除实战
数据库·mysql·架构
smallyoung1 天前
数据库乐观锁深度解析:MySQL、PostgreSQL 实战 + Spring Boot 集成指南
数据库·mysql·postgresql
parade岁月1 天前
MySQL JOIN解析:朴实无华但食之有味
数据库·后端