The best choice is increasing maximum mount point to 2.

On 2/9/06, Robert Ouzen <rouzen AT univ.haifa.ac DOT il> wrote:
>
> Hi to All
>
> I saw this morning on a Oracle file systems backup this error:
>
> 02/08/2006 22:11:27  ANR0539W Transaction failed for session 6866 for
> node   ALEPHTEST. This node has exceeded its maximum number of
>                      mount points. (SESSION: 6866)
>
> My Maximum  mount point for this node is 1 and never had problem with that
> before ..... I upgrade my Tsm version to 5.3.2.0 just now.
>
> I search in the forum about the ANR0539W and just fount what Thomas Rupp
> asked , the same behaviour !!!!!!!!!!!!!!!!!!!!
>
>
>
> 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.=20
> This node has exceeded its maximum number of mount points. (SESSION:
> 1268)=20
>
> 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
>
> Did I have to increase the maximum mounts of point to 2 ???????? or
> another advice ....
>
> Regards
>
> Robert Ouzen
> E-mail:rouzen AT univ.haifa.ac DOT il
>
>