ITPub博客

首页 > Linux操作系统 > Linux操作系统 > TSM+RMAN报错

TSM+RMAN报错

原创 Linux操作系统 作者:zhanglei_itput 时间:2009-09-03 16:02:34 0 删除 编辑

今天巡检发现一个数据库的rman备份失败了,日志如下:

Recovery Manager: Release 10.2.0.4.0 - Production on Thu Sep 3 02:00:00 2009
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
connected to target database: ORCL (DBID=1194585128)
connected to recovery catalog database

RMAN> run {
2> allocate channel 'full_sid1' type 'sbt_tape' connect *parms 'ENV=(tdpo_optfile=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
3> allocate channel 'full_sid2' type 'sbt_tape' connect *parms 'ENV=(tdpo_optfile=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
4> backup format 'njdb_full_bak_%s_%t_%p'
5> tag 'database full backup'
6> database;
7> backup format 'njdb_ctl_bak_%s_%t_%p'
8> tag 'database controlfile backup'
9> current controlfile;
10> RELEASE CHANNEL full_sid1;
11> RELEASE CHANNEL full_sid2;
12>
13> allocate channel 'arch_njdb1' type 'sbt_tape' connect *parms 'ENV=(tdpo_optfile=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
14> allocate channel 'arch_njdb2' type 'sbt_tape' connect *parms 'ENV=(tdpo_optfile=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
15> sql 'alter system archive log current';
16> backup format 'njdb_arch_bak_%s_%t_%p'
17> tag 'database archivelog backup'
18> archivelog all delete input;
19> RELEASE CHANNEL 'arch_njdb1' ;
20> RELEASE CHANNEL 'arch_njdb2' ;
21>   }
22>
allocated channel: full_sid1
channel full_sid1: sid=210 instance=orcl1 devtype=SBT_TAPE
channel full_sid1: Data Protection for Oracle: version 5.4.1.0

allocated channel: full_sid2
channel full_sid2: sid=212 instance=orcl2 devtype=SBT_TAPE
channel full_sid2: Data Protection for Oracle: version 5.4.1.0

Starting backup at 2009-09-03 02:00:07
channel full_sid1: starting full datafile backupset
channel full_sid1: specifying datafile(s) in backupset
input datafile fno=00014 name=+DATADG1/data01.dbf
input datafile fno=00006 name=+DATADG1/nnc_data01.dbf
input datafile fno=00010 name=+DATADG1/bos_d1.dbf
input datafile fno=00012 name=+DATADG1/bos_d2.dbf
input datafile fno=00016 name=+DATADG1/nnc_data02.dbf
input datafile fno=00007 name=+DATADG1/nnc_index01.dbf
input datafile fno=00005 name=+DATADG1/orcl/datafile/undotbs2.264.666805151
input datafile fno=00004 name=+DATADG1/orcl/datafile/users.259.666805017
input datafile fno=00018 name=+DATADG1/eprk.dbf
channel full_sid1: starting piece 1 at 2009-09-03 02:00:08
channel full_sid2: starting full datafile backupset
channel full_sid2: specifying datafile(s) in backupset
input datafile fno=00015 name=+DATADG1/data02.dbf
input datafile fno=00008 name=+DATADG1/indexts.dbf
input datafile fno=00001 name=+DATADG1/orcl/datafile/system.256.666805015
input datafile fno=00003 name=+DATADG1/orcl/datafile/sysaux.257.666805017
input datafile fno=00009 name=+DATADG1/bos_idx1.dbf
input datafile fno=00011 name=+DATADG1/lobts.dbf
input datafile fno=00013 name=+DATADG1/bos_d3.dbf
input datafile fno=00017 name=+DATADG1/njwz01.dbf
input datafile fno=00002 name=+DATADG1/orcl/datafile/undotbs1.258.666805017
channel full_sid2: starting piece 1 at 2009-09-03 02:00:09
channel full_sid2: finished piece 1 at 2009-09-03 02:17:25
piece handle=njdb_full_bak_2528_696564008_1 tag=DATABASE FULL BACKUP comment=API Version 2.0,MMS Version 5.4.1.0
channel full_sid2: backup set complete, elapsed time: 00:17:17
channel full_sid2: starting full datafile backupset
channel full_sid2: specifying datafile(s) in backupset
including current control file in backupset
channel full_sid2: starting piece 1 at 2009-09-03 02:17:28
channel full_sid1: finished piece 1 at 2009-09-03 02:23:53
piece handle=njdb_full_bak_2527_696564008_1 tag=DATABASE FULL BACKUP comment=API Version 2.0,MMS Version 5.4.1.0
channel full_sid1: backup set complete, elapsed time: 00:23:45
channel full_sid1: starting full datafile backupset
channel full_sid1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on full_sid2 channel at 09/03/2009 02:23:54
ORA-19502: write error on file "njdb_full_bak_2529_696565045_1", blockno 1 (blocksize=512)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
   ANS1329S (RC29)   Server out of data storage space
channel full_sid2 disabled, job failed on it will be run on another channel
including current SPFILE in backupset
channel full_sid1: starting piece 1 at 2009-09-03 02:23:54
channel full_sid1: finished piece 1 at 2009-09-03 02:24:09
piece handle=njdb_full_bak_2530_696565434_1 tag=DATABASE FULL BACKUP comment=API Version 2.0,MMS Version 5.4.1.0
channel full_sid1: backup set complete, elapsed time: 00:00:15
channel full_sid1: starting full datafile backupset
channel full_sid1: specifying datafile(s) in backupset
including current control file in backupset
channel full_sid1: starting piece 1 at 2009-09-03 02:24:11
channel full_sid1: finished piece 1 at 2009-09-03 02:24:26
piece handle=njdb_full_bak_2531_696565449_1 tag=DATABASE FULL BACKUP comment=API Version 2.0,MMS Version 5.4.1.0
channel full_sid1: backup set complete, elapsed time: 00:00:17
Finished backup at 2009-09-03 02:24:26

Starting backup at 2009-09-03 02:24:35
channel full_sid1: starting full datafile backupset
channel full_sid1: specifying datafile(s) in backupset
including current control file in backupset
channel full_sid1: starting piece 1 at 2009-09-03 02:24:38
channel full_sid1: finished piece 1 at 2009-09-03 02:24:53
piece handle=njdb_ctl_bak_2532_696565476_1 tag=DATABASE CONTROLFILE BACKUP comment=API Version 2.0,MMS Version 5.4.1.0
channel full_sid1: backup set complete, elapsed time: 00:00:17
Finished backup at 2009-09-03 02:24:53
released channel: full_sid1
released channel: full_sid2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of release command at 09/03/2009 02:24:54
RMAN-06012: channel: full_sid2 not allocated
Recovery Manager complete.

从日志上看,是空间不足了,估计是带库的磁带快满了,查看磁带库信息:

sid1#[/] cd /usr/tivoli/tsm/client/ba/bin
sid1#[/usr/tivoli/tsm/client/ba/bin]
dsmadmc
IBM Tivoli Storage Manager
Command Line Administrative Interface - Version 5, Release 4, Level 0.0
(c) Copyright by IBM Corporation and other(s) 1990, 2007. All Rights Reserved.
Enter your user id:  admin
Enter your password: 
Session established with server TSMSERVER: Windows
  Server Version 5, Release 4, Level 4.0
  Server date/time: 09/03/09   15:55:28  Last access: 09/03/09   15:35:10
tsm: TSMSERVER>q volume
Volume Name                  Storage         Device         Estimated       Pct      Volume
                             Pool Name       Class Name      Capacity      Util      Status
------------------------     -----------     ----------     ---------     -----     --------
D:\TSMDATA\SERVER1\DISK-     DISKPOOL        DISK               2.0 G       0.0     On-Line
 1.DSM                                                                                     
Y20340L2                     TAPEPOOL        TAPE             462.6 G      75.2     Filling
Y20341L2                     TAPEPOOL        TAPE             685.6 G     100.0       Full 
Y20342L2                     TAPEPOOL        TAPE             713.4 G     100.0       Full 
Y20343L2                     TAPEPOOL        TAPE             711.6 G     100.0       Full 
Y20344L2                     TAPEPOOL        TAPE             679.5 G     100.0       Full 
Y20345L2                     TAPEPOOL        TAPE             712.0 G     100.0       Full 
Y20346L2                     TAPEPOOL        TAPE             680.1 G     100.0       Full 
Y20347L2                     TAPEPOOL        TAPE             719.5 G     100.0       Full
 

果真是磁带快满了,更换磁带,问题解决。

参考文献:http://space.itpub.net/12778571/viewspace-462882

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

下一篇: ITIL V2+ISO 20000
请登录后发表评论 登录
全部评论

注册时间:2009-02-10

  • 博文量
    400
  • 访问量
    1108271