RMAN-06580: the SECBYTES option cannot be used with AS COPY

最新推荐文章于 2024-06-14 09:06:28 发布
最新推荐文章于 2024-06-14 09:06:28 发布
阅读量250 收藏
点赞数

1              

问题：在创建rman多备份集的时候出现的问题：

 

RMAN> run

2> {

3> allocate channel c1 device type disk;

4> allocate channel c2 device type disk;

5> allocate channel c3 device type disk;

6> allocate channel c4 device type disk;

7> allocate channel c5 device type disk;

8> backup datafile 1 section size 150m tag='section_df1';

9> }

 

allocated channel: c1

channel c1: SID=20 device type=DISK

 

allocated channel: c2

channel c2: SID=142 device type=DISK

 

allocated channel: c3

channel c3: SID=17 device type=DISK

 

allocated channel: c4

channel c4: SID=147 device type=DISK

 

allocated channel: c5

channel c5: SID=21 device type=DISK

 

Starting backup at 04-APR-16

released channel: c1

released channel: c2

released channel: c3

released channel: c4

released channel: c5

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

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

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

RMAN-03002: failure of backup command at 04/04/2016 11:46:42

RMAN-06580: the SECBYTES option cannot be used with AS COPY

 

2

原因：

RMAN> show all;

 

RMAN configuration parameters for database with db_unique_name PROD1 are:

CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default

CONFIGURE BACKUP OPTIMIZATION OFF; # default

CONFIGURE DEFAULT DEVICE TYPE TO DISK;

CONFIGURE CONTROLFILE AUTOBACKUP ON;

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COPY PARALLELISM 1;-------备份方式是copy

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

CONFIGURE MAXSETSIZE TO UNLIMITED; # default

CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_prod1.f'; # default

 

 

3

解决办法：

RMAN> CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO backupset;----------备份方式改为备份集的方式

 

old RMAN configuration parameters:

CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COPY PARALLELISM 1;

new RMAN configuration parameters:

CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;

new RMAN configuration parameters are successfully stored

 

 

4

验证：
 

RMAN> run

 {

 allocate channel c1 device type disk;

 allocate channel c2 device type disk;

  allocate channel c3 device type disk;

  allocate channel c4 device type disk;

 allocate channel c5 device type disk;

 backup datafile 1 section size 150m tag='section_df1';

}

 

allocated channel: c1

channel c1: SID=20 device type=DISK

 

allocated channel: c2

channel c2: SID=142 device type=DISK

 

allocated channel: c3

channel c3: SID=17 device type=DISK

 

allocated channel: c4

channel c4: SID=147 device type=DISK

 

allocated channel: c5

channel c5: SID=21 device type=DISK

 

Starting backup at 04-APR-16

channel c1: starting full datafile backup set

channel c1: specifying datafile(s) in backup set

input datafile file number=00001 name=/u01/app/oracle/oradata/prod1/system01.dbf

backing up blocks 1 through 19200

channel c1: starting piece 1 at 04-APR-16

channel c2: starting full datafile backup set

channel c2: specifying datafile(s) in backup set

input datafile file number=00001 name=/u01/app/oracle/oradata/prod1/system01.dbf

backing up blocks 19201 through 38400

channel c2: starting piece 2 at 04-APR-16

channel c3: starting full datafile backup set

channel c3: specifying datafile(s) in backup set

input datafile file number=00001 name=/u01/app/oracle/oradata/prod1/system01.dbf

backing up blocks 38401 through 57600

channel c3: starting piece 3 at 04-APR-16

channel c4: starting full datafile backup set

channel c4: specifying datafile(s) in backup set

input datafile file number=00001 name=/u01/app/oracle/oradata/prod1/system01.dbf

backing up blocks 57601 through 76800

channel c4: starting piece 4 at 04-APR-16

channel c5: starting full datafile backup set

channel c5: specifying datafile(s) in backup set

input datafile file number=00001 name=/u01/app/oracle/oradata/prod1/system01.dbf

backing up blocks 76801 through 96000

channel c5: starting piece 5 at 04-APR-16

channel c1: finished piece 1 at 04-APR-16

piece handle=/u01/app/oracle/fast_recovery_area/PROD1/backupset/2016_04_04/o1_mf_nnndf_SECTION_DF1_cj3s1mpn_.bkp tag=SECTION_DF1 comment=NONE

channel c1: backup set complete, elapsed time: 00:00:04

channel c2: finished piece 2 at 04-APR-16

piece handle=/u01/app/oracle/fast_recovery_area/PROD1/backupset/2016_04_04/o1_mf_nnndf_SECTION_DF1_cj3s1nhx_.bkp tag=SECTION_DF1 comment=NONE

channel c2: backup set complete, elapsed time: 00:00:07

channel c3: finished piece 3 at 04-APR-16

piece handle=/u01/app/oracle/fast_recovery_area/PROD1/backupset/2016_04_04/o1_mf_nnndf_SECTION_DF1_cj3s1nk0_.bkp tag=SECTION_DF1 comment=NONE

channel c3: backup set complete, elapsed time: 00:00:07

channel c4: finished piece 4 at 04-APR-16

piece handle=/u01/app/oracle/fast_recovery_area/PROD1/backupset/2016_04_04/o1_mf_nnndf_SECTION_DF1_cj3s1nl9_.bkp tag=SECTION_DF1 comment=NONE

channel c4: backup set complete, elapsed time: 00:00:07

channel c5: finished piece 5 at 04-APR-16

piece handle=/u01/app/oracle/fast_recovery_area/PROD1/backupset/2016_04_04/o1_mf_nnndf_SECTION_DF1_cj3s1nmm_.bkp tag=SECTION_DF1 comment=NONE

channel c5: backup set complete, elapsed time: 00:00:07

Finished backup at 04-APR-16

 

Starting Control File and SPFILE Autobackup at 04-APR-16

piece handle=/u01/app/oracle/fast_recovery_area/PROD1/autobackup/2016_04_04/o1_mf_s_908279356_cj3s1wmb_.bkp comment=NONE

Finished Control File and SPFILE Autobackup at 04-APR-16

released channel: c1

released channel: c2

released channel: c3

released channel: c4

released channel: c5

5

查看生成的备份文件

[oracle@prod1 autobackup]$ ll 2016_04_04/

total 48000

-rw-r-----. 1 oracle oinstall 9830400 Apr  4 11:05 o1_mf_s_908275702_cj3pjbvf_.bkp

-rw-r-----. 1 oracle oinstall 9830400 Apr  4 11:13 o1_mf_s_908275702_cj3py9hq_.bkp

-rw-r-----. 1 oracle oinstall 9830400 Apr  4 11:23 o1_mf_s_908275702_cj3qlbsk_.bkp

-rw-r-----. 1 oracle oinstall 9830400 Apr  4 11:49 o1_mf_s_908279342_cj3s1h39_.bkp

-rw-r-----. 1 oracle oinstall 9830400 Apr  4 11:49 o1_mf_s_908279356_cj3s1wmb_.bkp

[oracle@prod1 autobackup]$ cd ..

[oracle@prod1 PROD1]$ ls

archivelog  autobackup  backupset  datafile  onlinelog

[oracle@prod1 PROD1]$ cd backupset/

[oracle@prod1 backupset]$ ls

2016_04_04

[oracle@prod1 backupset]$ ll 2016_04_04/

total 1229064

-rw-r-----. 1 oracle oinstall  90636288 Apr  4 12:01 o1_mf_nnndf_J_DBF1_cj3srk7d_.bkp

-rw-r-----. 1 oracle oinstall  65765376 Apr  4 11:59 o1_mf_nnndf_JUNXIAO_DBF1_cj3snxfc_.bkp

-rw-r-----. 1 oracle oinstall  75915264 Apr  4 11:59 o1_mf_nnndf_JUNXIAO_DBF1_cj3snxv4_.bkp

-rw-r-----. 1 oracle oinstall  83394560 Apr  4 11:59 o1_mf_nnndf_JUNXIAO_DBF1_cj3snxwb_.bkp

-rw-r-----. 1 oracle oinstall  91668480 Apr  4 11:59 o1_mf_nnndf_JUNXIAO_DBF1_cj3snzg5_.bkp

-rw-r-----. 1 oracle oinstall  80019456 Apr  4 11:59 o1_mf_nnndf_JUNXIAO_DBF1_cj3so11v_.bkp

-rw-r-----. 1 oracle oinstall     57344 Apr  4 11:59 o1_mf_nnndf_JUNXIAO_DBF1_cj3so1cq_.bkp

-rw-r-----. 1 oracle oinstall    401408 Apr  4 12:04 o1_mf_nnndf_KK_DBF_cj3sxzvm_.bkp

-rw-r-----. 1 oracle oinstall    409600 Apr  4 12:04 o1_mf_nnndf_KK_DBF_cj3sy0c2_.bkp

-rw-r-----. 1 oracle oinstall    409600 Apr  4 12:04 o1_mf_nnndf_KK_DBF_cj3sy0d8_.bkp

-rw-r-----. 1 oracle oinstall    409600 Apr  4 12:04 o1_mf_nnndf_KK_DBF_cj3sy0mw_.bkp

-rw-r-----. 1 oracle oinstall    409600 Apr  4 12:04 o1_mf_nnndf_KK_DBF_cj3sy0vm_.bkp

-rw-r-----. 1 oracle oinstall    409600 Apr  4 12:04 o1_mf_nnndf_KK_DBF_cj3sy15f_.bkp

-rw-r-----. 1 oracle oinstall    409600 Apr  4 12:04 o1_mf_nnndf_KK_DBF_cj3sy1fy_.bkp

-rw-r-----. 1 oracle oinstall    409600 Apr  4 12:04 o1_mf_nnndf_KK_DBF_cj3sy1or_.bkp

-rw-r-----. 1 oracle oinstall    409600 Apr  4 12:04 o1_mf_nnndf_KK_DBF_cj3sy1xb_.bkp

。。。。。。。。。。。。。

6

验证数据文件备份

RMAN> validate datafile 1 section size 150m;

 

Starting validate at 04-APR-16

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=22 device type=DISK

channel ORA_DISK_1: starting validation of datafile

channel ORA_DISK_1: specifying datafile(s) for validation

input datafile file number=00001 name=/u01/app/oracle/oradata/prod1/system01.dbf

validating blocks 1 through 19200

channel ORA_DISK_1: validation complete, elapsed time: 00:00:01

channel ORA_DISK_1: starting validation of datafile

channel ORA_DISK_1: specifying datafile(s) for validation

input datafile file number=00001 name=/u01/app/oracle/oradata/prod1/system01.dbf

validating blocks 19201 through 38400

channel ORA_DISK_1: validation complete, elapsed time: 00:00:01

channel ORA_DISK_1: starting validation of datafile

channel ORA_DISK_1: specifying datafile(s) for validation

input datafile file number=00001 name=/u01/app/oracle/oradata/prod1/system01.dbf

validating blocks 38401 through 57600

channel ORA_DISK_1: validation complete, elapsed time: 00:00:01

channel ORA_DISK_1: starting validation of datafile

channel ORA_DISK_1: specifying datafile(s) for validation

input datafile file number=00001 name=/u01/app/oracle/oradata/prod1/system01.dbf

validating blocks 57601 through 76800

channel ORA_DISK_1: validation complete, elapsed time: 00:00:01

channel ORA_DISK_1: starting validation of datafile

channel ORA_DISK_1: specifying datafile(s) for validation

input datafile file number=00001 name=/u01/app/oracle/oradata/prod1/system01.dbf

validating blocks 76801 through 96000

channel ORA_DISK_1: validation complete, elapsed time: 00:00:01

List of Datafiles

=================

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

---- ------ -------------- ------------ --------------- ----------

1    OK     0              14644        96071           1067580  

  File Name: /u01/app/oracle/oradata/prod1/system01.dbf

  Block Type Blocks Failing Blocks Processed

  ---------- -------------- ----------------

  Data       0              63473          

  Index      0              13174          

  Other      0              4705           

 

channel ORA_DISK_1: starting validation of datafile

channel ORA_DISK_1: specifying datafile(s) for validation

including current control file for validation

including current SPFILE in backup set

channel ORA_DISK_1: validation complete, elapsed time: 00:00:01

List of Control File and SPFILE

===============================

File Type    Status Blocks Failing Blocks Examined

------------ ------ -------------- ---------------

SPFILE       OK     0              2              

Control File OK     0              756            

Finished validate at 04-APR-16

 

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/30606702/viewspace-2074933/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/30606702/viewspace-2074933/

congwei2855
关注
IMP-00003: ORACLE error 3113 encountered ORA-03113: end-of-file on communication channel
weixin_33748818的博客
02-29 758
IMP-00003: ORACLE error 3113 encountered ORA-03113: end-of-file on communication channel . . importing table "SFP_FILE_6" 11179rows imported IMP-00017: following ...
12C ORA 错误汇总18 ORA 57000 to ORA 65535 EXP 00000 to EXP 00114
ugghhj的博客
11-07 2484
12C ORA 错误汇总18 ORA 57000 to ORA 65535 EXP 00000 to EXP 00114
RMAN备份恢复常见报错及处理办法（一）
Sebastien23的博客
03-17 3099
解决办法：RMAN-06102一般是由于备库缺少部分归档日志（可能已被清理），需要去别的地方备份缺少的归档日志，或者重新备份数据库（如果数据量整体不大），然后重新恢复数据库。恢复数据库时收到报错RMAN-11003，并且尝试关闭归档模式时会报错ORA-01143和ORA-01110。解决办法：备份对应的数据文件（这里是datafile 317），然后重新进行恢复。解决办法：去备库备份缺少的归档日志，从SCN最小的时间点开始备份，然后继续恢复。如果还是不行，可以尝试去重新备份数据库文件进行恢复。
RMAN恢复案例之--不完全恢复错误案例
weixin_34245082的博客
09-20 295
RMAN恢复案例之--不完全恢复错误案例RMAN恢复案例：不完全恢复，由于在先前的数据文件备份有误，导致恢复失败。[oracle@rh6~]$rmantarget/ RecoveryManager:Release11.2.0.1.0-ProductiononSatSep2015:54:252014 Copyright(c)1982,2009...
[WK-T]ORACLE RAC +ASM Backup and Recovery(三)
cpj46358的博客
09-02 263
Loss of control files 前言：默认创建好的RAC集群只有一个控制文件，而在单实例数据库中有三个控制文件，基于控制文件的重要性，我们手动添加两个控制文件，RAC环境下添加控制文件可以参考文章：http://b...
expdp导出报ORA-06580: Hash Join ran out of memory
killvoon的专栏
08-24 487
一套测试环境使用expdp导出数据，报出ORA-06580: Hash Join ran out of memory的错误，这个是倒是第一次遇到，随手记录一下。 看到这个错误第一反应就是哪块内存区设置的小了，导致expdp操作的时候内存不足。查询了下，MOS上有相关文档，可能是由于 pga_aggregate_target=0 workarea_size_policy=MANUAL 这俩参数设置成如上值导致的。 看了下环境参数，pga_aggregate_target倒是设置了具体的值，但work
12C ORA-错误汇总17 NZE-43000 to ORA-56974
ugghhj的博客
11-11 1370
12C ORA-错误汇总17 NZE-43000 to ORA-56974
OCP-043之：数据库备份操作
最新发布
大龄IT民工
06-14 1256
1 RMAN备份操作 1.1 基本操作 基本的控制和数据文件备份 RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/tmp/backup/cs_%F'; new RMAN configuration parameters: CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/tmp/backup/cs_%F'; new RMAN
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
04-10 1631
<br />问题：<br />今天在AIX 5L 的一个双节点RAC环境测试一个数据库的备份脚本，一开始遇到了一些错误，但没能记录下来，最后就记录下来了这一个ORA-27054错误。<br />以下是操作过程：<br />RMAN-00571: ===========================================================<br /><br />RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ======
数据库没有备份无法打开处理方法之二dul
ylqiu1028的博客
06-10 7814
由于企业的数据库人员经验不足，或是根本没有dba，因此，可能会出现数据瘫痪，数据库不能打开的现象，那么我们可能有两种方法：  a，数据库强行打开；  b，使用oracle dul工具来把数据抽取出来 一般使用dul都是强行打开数据库都无法打开，或是某个表空间文件无法online的情况下才使用。并且此工具需要system表空间是好的。 dul是oracle内部工具，这个工具只是为了挽救数据，
Oracle Recovery Manager Overview and Configuration
weixin_34161064的博客
02-19 100
从这一章, 到最后一章都是讲 RMAN Rman is an Oracle utility that helps you manage the backup, restore, and recovery oerations on Oracle database. Rman has a powerful command language that is independent of the ...
rman完全恢复
ZhuangLiang
02-08 1970
连接到: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL&gt; shutdown immediate ORA-01507...
RMAN Restore Optimizat…
babymouse1212的博客
05-02 464
Recover database时哪些数据文件还没有Restore?     RMAN Restore Optimization and Oracle Managed Files (OMF) (文档 ID 1621319.1) 转到底部 Restore Optimization and Oracle Managed Files (OMF)" /> Restore Optimi
ORA-报错解释
热门推荐
wrh_csdn的博客
11-07 3万+
ORA-00001: 违反唯一约束条件 (.)  ORA-00017: 请求会话以设置跟踪事件  ORA-00018: 超出最大会话数  ORA-00019: 超出最大会话许可数  ORA-00020: 超出最大进程数 ()  ORA-00021: 会话附属于其它某些进程；无法转换会话  ORA-00022: 无效的会话 ID；访问被拒绝  ORA-00023: 会话引用进程私用内存
ORACLE错误一览表，方便查询！
u012525662的专栏
11-27 9009
ORA-06000: NETASY: 端口打开失败 ORA-06001: NETASY: 端口设置失败 ORA-06002: NETASY: 端口读失败 ORA-06003: NETASY: 端口写失败 ORA-06004: NETASY: 对话文件打开失败 ORA-06005: NETASY: 对话文件读失败 ORA-06006: NETASY: 对话执行失败 ORA-06007:
oracle error
cuijiu2464的博客
04-08 796
ORA-00001: 违反唯一约束条件 (.)ORA-00017: 请求会话以设置跟踪事件ORA-00018: 超出最大会话数ORA-00019: 超出最大会话许可数ORA-00020: 超出最大进程数 ()ORA-00021:...
oracle function 创建 ora-06550,解决问题：Oracle/PLSQL: ORA-06550
weixin_32466193的博客
04-10 1387
Home >Oracle/PLSQL >Oracle Error MessagesOracle/PLSQL: ORA-06550Learn the cause and how to resolve the ORA-06550 error message in Oracle.DescriptionWhen you encounter an ORA-06550 error, the fol...
RMAN-03002: failure of Duplicate Db command at 06/05/2023 22:52:15 RMAN-05501: aborting duplication of target database RMAN-03015: error occurred in stored script Memory Script RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
06-06
这个错误通常出现在辅助数据库的TNS Names文件中没有正确配置服务名称。请确保TNS Names文件中定义的服务名称与您要连接的辅助数据库的服务名称相匹配。您还可以尝试通过检查辅助数据库的监听器状态来确定是否存在...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值