ADSM-L

MAXNUMMP changed between TSM server 4.2.2.8 and 5.3.2.0

2005-11-15 07:21:39
Subject: MAXNUMMP changed between TSM server 4.2.2.8 and 5.3.2.0
From: Thomas Rupp <Thomas.Rupp AT ILLWERKE DOT AT>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 15 Nov 2005 13:21:28 +0100
Hi TSM-ers,

yesterday we upgraded our old NSM from TSM 4.2.2.8 to 5.3.2.0.
Now I'm seeing the following messages for our ORACLE backups.

ANR0539W Transaction failed for session 1268 for node xxxx_ORA. 
This node has exceeded its maximum number of mount points. (SESSION:
1268) 

The node has MAXNUMMP set to 1. On TSM 4.2.2.8 the session would wait
for
a mountpoint to be available. On 5.3.2.0 the session is cancelled.

Is there anything I can change to make the second session wait for a
mountpoint?

Kind regards
Thomas Rupp

<Prev in Thread] Current Thread [Next in Thread>
  • MAXNUMMP changed between TSM server 4.2.2.8 and 5.3.2.0, Thomas Rupp <=