ADSM-L

Re: [ADSM-L] Strange error on TDP Oracle with DELETE OBSOLETE

2010-05-05 11:16:40
Subject: Re: [ADSM-L] Strange error on TDP Oracle with DELETE OBSOLETE
From: David McClelland <tsm AT NETWORKC.CO DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 5 May 2010 16:15:59 +0100
Bill. Weird. Just a thought though... Is the TCPSERVERADDRESS in your
dsm.sys stanza a hostname or an IP address? Could a name lookup of the TSM
server be crazily failing from time to time, particularly evident when
opening and closing lots of sessions (making lots of name server lookup
calls) in quick succession? If it is a name, perhaps replacing with an IP
address and testing could be interesting. Like I say, just a thought...

/DMc

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Bill Boyer
Sent: 05 May 2010 15:58
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Strange error on TDP Oracle with DELETE OBSOLETE

Have a TDP 5.4.1.0 running on AIX. The RMAN script does a backup of the
database, backup of the logs and then a DELETE OBSOLETE. From the output you
see the channel allocating fine and the delete starts working
until.BANG.ANS1033E Invalid TCP/IP Host. From the TSM server actlog I can
see multiple sessions start/stop for this delete obsolete. It looks like
RMAN opens/closes a session for each backup piece. So it's going along just
fine and then failing with a DNS lookup failure?? Any ideas?

RMAN> allocate channel for maintenance device type 'SBT_TAPE' parms
'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
allocated channel: ORA_MAINT_SBT_TAPE_1
channel ORA_MAINT_SBT_TAPE_1: sid=502 devtype=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0


RMAN> delete noprompt obsolete recovery window of 35 days device type
'SBT_TAPE';
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set           1528   17-APR-10
 Backup Piece       1528   17-APR-10          golbantu_1_1
Backup Set           1529   17-APR-10
 Backup Piece       1529   17-APR-10          gplbb604_1_1
Backup Set           1530   17-APR-10
 Backup Piece       1530   17-APR-10          gqlbbk1t_1_1
Backup Set           1532   18-APR-10
 Backup Piece       1532   18-APR-10          gslbd417_1_1
Backup Set           1533   18-APR-10
 Backup Piece       1533   18-APR-10          gtlbdc9s_1_1
Backup Set           1534   18-APR-10
 Backup Piece       1534   18-APR-10          gulbdqbp_1_1
Backup Set           1535   18-APR-10
 Backup Piece       1535   18-APR-10          gvlbe8dq_1_1
deleted backup piece
backup piece handle=golbantu_1_1 recid=1528 stamp=716529599
deleted backup piece
backup piece handle=gplbb604_1_1 recid=1529 stamp=716544005
deleted backup piece
backup piece handle=gqlbbk1t_1_1 recid=1530 stamp=716558398
deleted backup piece
backup piece handle=gslbd417_1_1 recid=1532 stamp=716607528
deleted backup piece
backup piece handle=gtlbdc9s_1_1 recid=1533 stamp=716615998
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on ORA_MAINT_SBT_TAPE_1 channel at
05/05/2010 01:36:05
ORA-19509: failed to delete sequential file, handle="gulbdqbp_1_1", parms=""

ORA-27027: sbtremove2 returned error
ORA-19511: Error received from media manager layer, error text:
  ANS1033E (RC-53)  An invalid TCP/IP address was specified.


Bill Boyer
"My childlike immaturity's the only thing standing between me and a major
midlife crisis" - ??

<Prev in Thread] Current Thread [Next in Thread>