TDPO 怪怪怪 怪问题！

有请高手指教！谢谢！

环境：
server : tsm server 5.5 /win2003;
client：tsm client 5.5 /tdpo5.4.1/aix 5309 ;
db: oracle 10.2.0.4.0使用RAC方式,使用裸设备()，全备约100G;
1、使用client 备份系统文件ok;
2、rman 备份database(100G,)至磁盘ok;
3、client 备份（rman 备份至磁盘的文件）ok;
4、tdpo 使用脚本备份oracle 控制文件 ok;
5、tdpo 使用脚本备份两个节点上的 archlog ok;
6、COMMTimeout 9999/IDLETIMEOUT 9999;

现象：
tdpo不能backup database ,以前有过一次也是这样,后来发现tdpo向带库里写几个文件后停止（约2G)，修改filesperset 为1后可完整备份，这次改了也不行，备份时的第一个文件就30G,不知有那位高手能指点一下？

日志：
tdpoerror.log
01/04/11   02:12:50 sessSendVerb: Error sending Verb, rc: -50
01/04/11   02:12:50 ANS1017E Session rejected: TCP/IP connection failure
01/04/11   02:12:50 ANS1017E Session rejected: TCP/IP connection failure
01/04/11   02:12:50 sessSendVerb: Error sending Verb, rc: -50
01/04/11   02:12:59 ANS4994S TDP Oracle AIX ANU0599 TDP for Oracle: (102590): =>(db1) ANU2602E The object /oracle//fulldb_49_739505421.dbf was not found on the TSM Server

tdpo.opt
DSMI_ORC_CONFIG    /usr/tivoli/tsm/client/api/bin64/dsm.opt
DSMI_LOG           /usr/tivoli/tsm/client/api/bin64
TDPO_FS           /oracle
TDPO_NODE          db1
TDPO_OWNER         oracle
TDPO_PSWDPATH      /usr/tivoli/tsm/client/oracle/bin64


backup_full.log
RMAN> run
2> {
3>         allocate channel t1 type "sbt_tape" parms "ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)";
4>         crosscheck backup;      
5>         delete noprompt expired backup;
6>         delete noprompt obsolete;
7>         backup filesperset 1  database format 'fulldb_%s_%t.dbf' include current controlfile;       
8>         release channel t1;
9> }
10>
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: sid=500 instance=rac1 devtype=SBT_TAPE
channel t1: Data Protection for Oracle: version 5.4.1.0

Starting backup at 02-JAN-11
channel t1: starting full datafile backupset
channel t1: specifying datafile(s) in backupset
input datafile fno=00002 name=/dev/ro1_30g
channel t1: starting piece 1 at 02-JAN-11
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on t1 channel at 01/02/2011 22:42:53
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog
ORA-19502: write error on file "fulldb_34_739406368.dbf", blockno 8351745 (blocksize=512)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
   ANS1017E (RC-50)  Session rejected: TCP/IP connection failure

Recovery Manager complete.

arch_full.log
Recovery Manager: Release 10.2.0.4.0 - Production on Sun Jan 2 20:55:52 2011

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

connected to target database: rac (DBID=663934440)

RMAN> run
2> {
3>         allocate channel t1 type "sbt_tape" CONNECT * parms "ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)";
4>         allocate channel t2 type "sbt_tape" CONNECT * parms "ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)";
5>         crosscheck archivelog all;
6>         delete noprompt expired archivelog all;
7>         delete noprompt obsolete;
8>         sql 'alter system archive log current';
9>         backup format 'archive.dbf' archivelog all delete input;
10>         release channel t1;
11>         release channel t2;
12> }
13>
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: sid=503 instance=rac1 devtype=SBT_TAPE
channel t1: Data Protection for Oracle: version 5.4.1.0

allocated channel: t2
channel t2: sid=522 instance=rac2 devtype=SBT_TAPE
channel t2: Data Protection for Oracle: version 5.4.1.0

specification does not match any archive log in the recovery catalog

specification does not match any archive log in the recovery catalog

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found

sql statement: alter system archive log current

Starting backup at 02-JAN-11
current log archived
channel t1: starting archive log backupset
channel t1: specifying archive log(s) in backup set
input archive log thread=1 sequence=197 recid=44 stamp=739400159
channel t1: starting piece 1 at 02-JAN-11
channel t2: starting archive log backupset
channel t2: specifying archive log(s) in backup set
input archive log thread=2 sequence=112 recid=45 stamp=739400158
input archive log thread=2 sequence=113 recid=46 stamp=739400167
channel t2: starting piece 1 at 02-JAN-11
channel t1: finished piece 1 at 02-JAN-11
piece handle=archive.dbf tag=TAG20110102T205619 comment=API Version 2.0,MMS Version 5.4.1.0
channel t1: backup set complete, elapsed time: 00:00:16
channel t1: deleting archive log(s)
archive log filename=/arch1/1_197_738557800.dbf recid=44 stamp=739400159
channel t1: starting archive log backupset
channel t1: specifying archive log(s) in backup set
input archive log thread=1 sequence=198 recid=47 stamp=739400171
channel t1: starting piece 1 at 02-JAN-11
channel t2: finished piece 1 at 02-JAN-11
piece handle=archive.dbf tag=TAG20110102T205619 comment=API Version 2.0,MMS Version 5.4.1.0
channel t2: backup set complete, elapsed time: 00:01:42
channel t2: deleting archive log(s)
archive log filename=/arch2/2_112_738557800.dbf recid=45 stamp=739400158
archive log filename=/arch2/2_113_738557800.dbf recid=46 stamp=739400167
channel t1: finished piece 1 at 02-JAN-11
piece handle=archive.dbf tag=TAG20110102T205619 comment=API Version 2.0,MMS Version 5.4.1.0
channel t1: backup set complete, elapsed time: 00:02:41
channel t1: deleting archive log(s)
archive log filename=/arch1/1_198_738557800.dbf recid=47 stamp=739400171
Finished backup at 02-JAN-11

released channel: t1

released channel: t2

Recovery Manager complete.收起