如何删除控制文件中过去rman备份到磁带的备份集
2024-05-10
1. 如何删除控制文件中过去rman备份到磁带的备份集
RMAN> delete noprompt obsolete; ...... using channel ORA_DISK_1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of delete command at 02/10/2014 14:00:50 RMAN-06091: no channel allocated for maintenance (of an appropriate type) rman 下list backup of database 发现有几个备份到磁带的备份集。 List of Backup Sets =================== BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 4943 838M SBT_TAPE 00:00:35 02/10/2014 BP Key: 4943 Status: UNAVAILABLE Tag: TAG20100411T004252 Piece Name: arch_20100411_4970_1 List of Archived Logs in backup set 4943 Thrd Seq Low SCN Low Time Next SCN Next Time ---- ------- ---------- --------- ---------- --------- 1 16014 4006475789091 10-APR-10 4006475846928 10-APR-10 1 16015 4006475846928 10-APR-10 4006475885650 10-APR-10 1 16016 4006475885650 10-APR-10 4006475943776 10-APR-10 1 16017 4006475943776 10-APR-10 4006475979118 10-APR-10 1 16018 4006475979118 10-APR-10 4006476023785 10-APR-10 1 16019 4006476023785 10-APR-10 4006476071180 10-APR-10 1 16020 4006476071180 10-APR-10 4006476158466 10-APR-10 1 16021 4006476158466 10-APR-10 4006476250848 10-APR-10 1 16022 4006476250848 10-APR-10 4006525513941 11-APR-10 BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 4948 517M SBT_TAPE 00:00:29 02/10/2014 BP Key: 4948 Status: AVAILABLE Tag: TAG20100412T002657 Piece Name: arch_20100412_4976_1 List of Archived Logs in backup set 4948 Thrd Seq Low SCN Low Time Next SCN Next Time ---- ------- ---------- --------- ---------- --------- 1 16030 4006527200207 11-APR-10 4006527247642 11-APR-10 1 16031 4006527247642 11-APR-10 4006527316362 11-APR-10 1 16032 4006527316362 11-APR-10 4006527374966 11-APR-10 1 16033 4006527374966 11-APR-10 4006527472280 11-APR-10 1 16034 4006527472280 11-APR-10 4006528044006 11-APR-10 1 16035 4006528044006 11-APR-10 4006576257046 02/10/2014 BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 且前一天备份的那个backupset也没有被删掉。 所以，至此问题清楚了，FRA使用率高是因为多了一个前一天的backupset 。 问题是，为什么命令块里面明明有 report obsolete; CROSSCHECK BACKUP; CROSSCHECK COPY; DELETE noprompt EXPIRED BACKUP; DELETE noprompt EXPIRED COPY; delete noprompt obsolete; 这些命令，为什么没有把那个已经过期的备份集删掉呢？ 于是，rman单独执行 RMAN> delete noprompt obsolete; ...... using channel ORA_DISK_1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of delete command at 02/10/2014 14:00:50 RMAN-06091: no channel allocated for maintenance (of an appropriate type) 同样不能删除。 这时候才反映过来，备份集删不掉应该是与控制文件中Device Type 为 SBT_TAPE 的东西有关。 这才想起年前放假前测试过一款备份软件，备份集已经没了，但是备份信息依然存在于控制文件中，正因为rman试图去删除 这些backup set 的时候发现 没有分配合适的通道，无法删除，所以导致FRA上expired 的backupset 也无法被成功删除。 所以现在问题就是怎样去把控制文件中的那些到磁带的备份信息删掉。 rman target / RMAN> show channel ; using target database control file instead of recovery catalog RMAN configuration parameters for database with db_unique_name FINAPRIM are: RMAN configuration has no stored or default parameters 没有已分配的渠道。 然后问题的关键是，现在已经没有磁带备份设备了，怎样去分配一个到磁带的渠道，幸运的是看到了一个兄弟类似的案例， 有这么一段： Suppose your current backup strategy uses only disk, but you have several old tape backups you want to get rid of. You can allocate a maintenance channel for performing the deletion of the tape backups by using the dummy sbt API (because the media manager isn’t available any longer). You can then use the delete obsolete command to remove the tape backups. Here’s an example showing how to do those things: RMAN> allocate channel for maintenance device type sbt parms 'SBT_LIBRARY=oracle.disksbt, ENV=(BACKUP_DIR=/tmp)'; RMAN> delete obsolete; Although the media manager isn’t available any longer, RMAN simulates a callout to the media management layer (MML) and successfully initiates the maintenance command to delete the old tape backups you want toget rid of. 哈哈，看起来太合适我了。 RMAN> allocate channel for maintenance device type sbt parms 'SBT_LIBRARY=oracle.disksbt, ENV=(BACKUP_DIR=/tmp)'; RMAN> delete noprompt obsolete; RMAN> DELETE noprompt EXPIRED ; RMAN> release channel ;
2. 如何解决Oracle10gR2 ORA-19554关于SBT
show all配置输出: RMAN> show all; RMAN 配置参数为: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION ON; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # defa ult CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1; CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 2 G; CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 2 G; CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\10.2.0\DB_1\DATABASE\SNCFORCL10G.ORA'; # default 我在同样的平台进行简单测试，结果是一切正常，我归结为Kamus有RPWT，结果他非常不愿意承认，还找到同样有问题的外国朋友。 为了不引起国际纠纷，我仔细比较了一下他的show all结果和我的设置，发现了问题所在。 原来他的配置里多了很多SBT_TAPE的设置，虽然default的配置仍然是Disk，可是这些参数可能是导致问题的罪魁祸首。 RMAN> show default device type; RMAN configuration parameters are: CONFIGURE DEFAULT DEVICE TYPE TO DISK; 建议他清除这些设置，清除后恢复正常。
3. 如何Catalog磁带库中的备份集
如何Catalog磁带库中的备份集
在NBU备份的环境中，可以使用以下步骤来Catalog磁带库中的备份集。
1. 查找需要Catalog的备份集名称
可以使用两种方法查找Oracle备份集.
方法一是使用RMAN的list命令查找，例如：
查找数据文件的备份
RMAN> list backup of datafile 324,325 completed between "to_date('2013-12-20 02:00:00','yyyy-mm-dd hh24:mi:ss')" and "to_date('2013-12-22 02:00:00','yyyy-mm-dd hh24:mi:ss')";
方法二是使用NBU的bplist命令查找，
如果是在备份服务器端，使用以下命令：
#/usr/openv/netbackup/bin/bplist -C ofs00biiacc002 -t 4 -s 12/20/2013 02:00:00 -e 12/22/2013 02:00:00 -l -R /
如果是在备份客户端，使用以下命令：
#/usr/openv/netbackup/bin/bplist -t 4 -s 12/20/2013 02:00:00 -e 12/22/2013 02:00:00 -l -R /
其中：
-C client name
-t is a policy type , where 4 means Oracle
-l shows more details info
-R recursively
/ root directory
2. 在RMAN中catalog备份集
RMAN> configure CHANNEL device type 'SBT_TAPE' PARMS 'ENV=(NB_ORA_POLICY=ACC2_Oracle_Backup,NB_ORA_SERV=abs00biiacc001,NB_ORA_CLIENT=ofs0accprc01)';
RNAB> catalog device type 'SBT_TAPE' backuppiece 'bk_47693_1_834129921';
3. catalog后恢复CHANNEL设置
RMAN> CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' CLEAR;
转载
4. 如何删除rman配置参数 configure channel 2 ……
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' clear; 如果想恢复到默认值： configure default device type clear;
5. 如何删除控制文件中过去rman备份到磁带的备份集
RMAN> allocate channel for maintenance device type sbt parms 'SBT_LIBRARY=oracle.disksbt, ENV=(BACKUP_DIR=/tmp)'; RMAN> delete noprompt obsolete; RMAN> DELETE noprompt EXPIRED ; RMAN> release channel ; 然后 然后就大功告成了，很顺利的就删掉了。
6. 如何通过TSM FOR ORACLE 备份windows 2003 64位操作系统中32位oracle数据库
这是因为64位操作系统不支持32位oracle数据库造成的原因，可以查看数据库日志有相关报错的。 跟备份脚本无关。
7. TSM新手，求助一个RMAN恢复的问题
run {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE' parms 'ENV=(tdpo_optfile=/usr/tivoli/tsm/client/Oracle/bin64/tdpo.opt)';
restore spfile from 'c-1142373573-20120814-02';
release channel ch00;
}
run {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE' parms 'ENV=(tdpo_optfile=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
restore controlfile from 'ctl20120814SGCRM5xx_1214_1_791316611';
release channel ch00;
}
alter database mount;
run {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE' parms 'ENV=(tdpo_optfile=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE' parms 'ENV=(tdpo_optfile=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
restore database;
release channel ch00;
release channel ch01;
}
8. 如何从磁带库中恢复备份集
操作如下
RMAN> list backupset 1055;
using target database control file instead of recovery catalog
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
1055 81.25M SBT_TAPE 00:00:25 23-OCT-12
BP Key: 1055 Status: AVAILABLE Compressed: NO Tag: TAG20121023T042751
Handle: zlxppc_arch_20121023_797401672_1enoeoi8_1_1 Media: 47
List of Archived Logs in backup set 1055
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 711 22333056 22-OCT-12 22392632 23-OCT-12
1 712 22392632 23-OCT-12 22392640 23-OCT-12
RMAN> run{
2> allocate channel t1 type sbt send 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
3> backup backupset 1055 format '/home/oracle/%U';
4> release channel t1;
5> }
allocated channel: t1
channel t1: sid=3228 devtype=SBT_TAPE
channel t1: Data Protection for Oracle: version 5.5.1.0
Starting backup at 24-OCT-12
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 10/24/2012 14:28:08
RMAN-06160: no backup pieces found for backup set key: 1055
最新文章
热门文章
推荐阅读