[原]配置RMAN恢复目录应注意兼容性

      近日打算对灾备的Oracle备份进行优化,其中一项就是引入恢复目录(Recover Catalog)进行管理,但是在测试过程中遇到了一个问题,记录如下:

      创建恢复目录所需要的表空间、相应的用户并赋予相应的权限:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
create tablespace rman
datafile
  '/u02/oradata/mydb/rman01.dbf' size 50M autoextend on
logging
segment space management auto
extent management local;
 
create user rman
identified by rman
default tablespace rman;
alter user rman quota unlimited on rman;
 
grant connect to rman;
grant resource to rman;
grant create any view to rman;
grant recovery_catalog_owner to rman;
revoke unlimited tablespace from rman;

      在注册target为Oracle 11g(11.2.0.2)的数据库时出现了错误。

1
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
[oracle@test01 admin]$ rman target / catalog rman/rman@catalog 
 
Recovery Manager: Release 11.2.0.2.0 - Production on Tue Jan 18 10:29:33 2011
 
Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
 
connected to target database: ORCL (DBID=1263384177)
connected to recovery catalog database
 
RMAN> create catalog ;
 
recovery catalog created
 
RMAN> register database ;
 
 
       
       
       
       
 
 
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 01/18/2011 10:36:40
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 1: ORA-04023: Object RMAN.DBMS_RCVCAT could not be validated or authorized

      经查证是RMAN的各组件之间的兼容性所导致的问题,下表转自:http://download.oracle.com/docs/cd/E11882_01/backup.112/e10643/compat003.htm#i634479

Table B-2 RMAN Compatibility Table

Target/Auxiliary Database RMAN client Recovery Catalog Database Recovery Catalog Schema

8.0.6

8.0.6

>=8.1.7

>=8.0.6

8.1.7

8.0.6.1

>=8.1.7

>=8.1.7

8.1.7

8.1.7

>=8.1.7

>=RMAN client

8.1.7.4

8.1.7.4

>=8.1.7

8.1.7.4

8.1.7.4

8.1.7.4

>=8.1.7

>= 9.0.1.4

9.0.1

9.0.1

>=8.1.7

>= RMAN client

9.2.0

>=9.0.1.3 and <= target database executable

>=8.1.7

>= RMAN client

10.1.0

>=9.0.1.3 and <= target database executable

>=9.0.1

>= RMAN client

10.2.0

>=9.0.1.3 and <= target database executable

>=9.0.1

>= RMAN client

11.1.0

>=9.0.1.3 and <= target database executable

>=10.2.0.3

>= RMAN client

11.2.0

>=9.0.1.3 and <= target database executable

>=10.2.0.3

>= RMAN client

      作为catalog的数据库版本是10.2.0.1,这就是问题所在。

posted @   killkill  阅读(1222)  评论(0编辑  收藏  举报
编辑推荐:
· 如何编写易于单元测试的代码
· 10年+ .NET Coder 心语,封装的思维:从隐藏、稳定开始理解其本质意义
· .NET Core 中如何实现缓存的预热?
· 从 HTTP 原因短语缺失研究 HTTP/2 和 HTTP/3 的设计差异
· AI与.NET技术实操系列:向量存储与相似性搜索在 .NET 中的实现
阅读排行:
· 周边上新:园子的第一款马克杯温暖上架
· Open-Sora 2.0 重磅开源!
· 分享 3 个 .NET 开源的文件压缩处理库,助力快速实现文件压缩解压功能!
· Ollama——大语言模型本地部署的极速利器
· [AI/GPT/综述] AI Agent的设计模式综述
历史上的今天:
2009-01-18 [原]一次SQL Server调优经历
点击右上角即可分享
微信分享提示