Results 1 to 7 of 7
  1. #1
    Join Date
    Sep 2006
    Posts
    105

    Unanswered: TSM error code - 41.

    Backup is getting failed twice a week due to the tsm error code:

    SQL2025N An I/O error "41" occurred on media "TSM".

    Unix server - oslevel 5.2 with db2 level v8.1 FP14.

    This server holds 5 databases and the backup script is in such a manner it runs sequentially.

    and the error says the that the client was attempting to use more mountpoints for a backup.

    Checked with the tsm team and they have updated the backup is using >1 moutpoints for this backup and they will not be able to update the node for increasing the mountpoints.

    Could anybody suggest on this to resolve the issue.


    Thanks for your help in advance.

    Meena.s

  2. #2
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Based on my understanding, the number of sessions is limited by the maxnummp (TSM parameter). So, if this parameter is set to 1, then backup is limited to 1 session. The number of sessions open to TSM is what you specify with the "open n sessions" parameter on the backup command. I think another session will be open if the logs are included in the backup image. So, try the backup command using one session if mannummp can't be increased.

  3. #3
    Join Date
    Sep 2006
    Posts
    105
    TSM team updated they will not be able to increase maxnummp parameter.
    and the backup command inside the script is the normal one like below:

    db2 backup database dbname online use tsm;

    Any Help....

  4. #4
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    - check how many sessions were used using "db2adutl query full db <db name>"
    - specify "open 1 sessions" and "exclude logs" (default in v8)

  5. #5
    Join Date
    Sep 2006
    Posts
    105
    Thanks for your reply.

    Its using only one session for the backup.

  6. #6
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    If maxnummp and # of sessions is 1, then I'm not sure what else to suggest from DB2 side. Consider opening a pmr with TSM Support.

  7. #7
    Join Date
    Sep 2006
    Posts
    105
    Thanks for your reply.

    Will check and let you know if i found anything.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •