ADSM-L

Re: DB2 on Solaris 7

2003-12-18 07:48:33
Subject: Re: DB2 on Solaris 7
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 18 Dec 2003 07:48:14 -0500
>... ANR2579E Schedule SAP_ONLINE in domain TDP_SERVERS for node SAPQA-TDP 
>failed (return code 1).

John - This probably reflects a POSTSchedule or PRESchedule command failure, 
where
       return code 1 typically accompanies "Command not found".  Check that out.

If your Solaris sessions remain problematic, and neither the client nor server 
end
reflects an action by its end in causing session severance, then it would seem 
that
something in between is causing it.  Check your Solaris syslog for error 
indications,
which may have affected things other than the TSM session, too.  We've seen a 
good
number of Solaris-related postings where session problems were caused by 
ethernet
autonegotiation being in effect.  Check the network configuration of that Sun 
box
as compared with other Suns not exhibiting the problem, and compare commonality 
of
subnet/switch connection.  You could also conduct beefy, manual TSM sessions, 
such
as large Backups, to try to make the problem occur under observation.

  Richard Sims, BU

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