ADSM-L

Re: [ADSM-L] V6 Database backup

2009-11-29 18:20:03
Subject: Re: [ADSM-L] V6 Database backup
From: Sam Sheppard <SHS AT SDDPC.SANNET DOT GOV>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sun, 29 Nov 2009 15:18:16 PST
---------------------------- Top of message ----------------------------
>>--> 11-29-09  15:10  S.SHEPPARD     (SHS)    Re: V6 Database backup

Yeah, that's what we first thought, but found a knowledgebase article
at:

https://www-304.ibm.com/ibmlink/sis/viewEskbDoc.wss?context=aparAndUsage
&documentIds=swg21408789&searchWords=anr2980e&libraryType=E&lc=en&cc=US

stating:

Although a return code -50 normally indicates a failure for the
connection to the TSM server, in the case of a TSM Server database
backup, this RC=-50 is more generic and only indicates that the backup
failed.

So I'm pretty sure it's another V6 gotcha.
Thanks
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
-----------------------------------------------------------------------`


---------------------------- Top of message ----------------------------
>>--> 11-29-09  14:55  ..NETMAIL     ()     Re: V6 Database backup
From: Richard Sims <rbs AT bu DOT edu>
Subject: Re: V6 Database backup
Date: Sun, 29 Nov 2009 17:53:22 -0500
To: Sam Sheppard <SHS AT SDDPC.SANNET DOT GOV>
_________________________________Top_of_Message_________________________________

Sam -

The -50 is DSM_RC_TCPIP_FAILURE, indicative of a bad TCP address or
port number inconsistency.
I don't have v6 so can't specifically advise.  Maybe you can find an
netaddress or port specification which is incorrect.

    Richard

On Nov 29, 2009, at 4:45 PM, Sam Sheppard wrote:

> We've been converting to version 6.1.2 for a couple of months and our
> daily TSM database backup suddenly started failing this week with the
> following message:
>
> ANR2980E Database backup terminated TCPIP failure DB2 sqlcode -2033
> sqlerrmc -50. (SESSION: 9, PROCESS: 4)
>
> Found one flash about this message being misleading, implying some
> other
> problem would be found if you looked further back in the log, but
> we had
> nothing.  We have been running full backups daily to disk. My first
> thought was lack of space in the output destination, so I attempted a
> backup to tape with the same result. Nothing esle out of the ordinary
> happening except that a lot of additional clients were added around
> that
> time and the database size increased from about 12GB to 27GB.
>
> I've opened a problem with IBM support, but wondered if anyone else
> had
> run into this and, if so, how to get around it.
>
> Thanks
> Sam Sheppard
> San Diego Data Processing Corp.
> (858)-581-9668

-----------------------------------------------------------------------`

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