ANS1512E with RC=8

[tsmdumber]

Hi I have the backups failing with RC 8

This is for only this node. Although the files are gtting backed up it fails with rc 8.

This is jus for only 1 node increasing idletime out to more than 60 for backup failure on only 1 node is not that clever!

Any inputs?

02/07/11 01:00:38 ANR0406I Session 43594 started for node LI0EBDB1P
(Linux86) (Tcp/Ip 10.1.10.184(41895)). (SESSION: 43594)
02/07/11 02:12:09 ANR0482W Session 43593 for node LI0EBDB1P (Linux86)
terminated - idle for more than 60 minutes. (SESSION:
43593)
02/07/11 02:57:56 ANR0406I Session 43669 started for node LI0EBDB1P
(Linux86) (Tcp/Ip 10.1.10.184(44166)). (SESSION: 43669)
02/07/11 02:58:06 ANR0403I Session 43594 ended for node LI0EBDB1P (Linux86).
(SESSION: 43594)
02/07/11 02:58:06 ANE4952I (Session: 43669, Node: LI0EBDB1P) Total number
of objects inspected: 6,320 (SESSION: 43669)
02/07/11 02:58:06 ANE4954I (Session: 43669, Node: LI0EBDB1P) Total number
of objects backed up: 644 (SESSION: 43669)
02/07/11 02:58:06 ANE4958I (Session: 43669, Node: LI0EBDB1P) Total number
of objects updated: 0 (SESSION: 43669)
02/07/11 02:58:06 ANE4960I (Session: 43669, Node: LI0EBDB1P) Total number
of objects rebound: 0 (SESSION: 43669)
02/07/11 02:58:06 ANE4957I (Session: 43669, Node: LI0EBDB1P) Total number
of objects deleted: 0 (SESSION: 43669)
02/07/11 02:58:06 ANE4970I (Session: 43669, Node: LI0EBDB1P) Total number
of objects expired: 16 (SESSION: 43669)
02/07/11 02:58:06 ANE4959I (Session: 43669, Node: LI0EBDB1P) Total number
of objects failed: 0 (SESSION: 43669)
02/07/11 02:58:06 ANE4961I (Session: 43669, Node: LI0EBDB1P) Total number
of bytes transferred: 112.86 GB (SESSION: 43669)
02/07/11 02:58:06 ANE4963I (Session: 43669, Node: LI0EBDB1P) Data transfer
time: 1,656.00 sec (SESSION: 43669)
02/07/11 02:58:06 ANE4966I (Session: 43669, Node: LI0EBDB1P) Network data
transfer rate: 71,465.46 KB/sec (SESSION: 43669)
02/07/11 02:58:06 ANE4967I (Session: 43669, Node: LI0EBDB1P) Aggregate data
transfer rate: 16,789.02 KB/sec (SESSION: 43669)
02/07/11 02:58:06 ANE4968I (Session: 43669, Node: LI0EBDB1P) Objects
compressed by: 0% (SESSION: 43669)
02/07/11 02:58:06 ANE4964I (Session: 43669, Node: LI0EBDB1P) Elapsed
processing time: 01:57:29 (SESSION: 43669)
02/07/11 02:58:06 ANR0403I Session 43669 ended for node LI0EBDB1P (Linux86).
(SESSION: 43669)
02/07/11 02:58:07 ANR2579E Schedule DAILY_INCR in domain LINUX_DOM for node
LI0EBDB1P failed (return code 8). (SESSION: 43592)


02/07/2011 02:29:31 ANS1809W A session with the TSM server has been disconnected. An attempt will be made to reestablish the connection.
02/07/2011 02:29:31 ANS1809W A session with the TSM server has been disconnected. An attempt will be made to reestablish the connection.
02/07/2011 02:29:57 ANS1909E The scheduled command failed.
02/07/2011 02:29:57 ANS1512E Scheduled event 'DAILY_INCR' failed. Return code = 8.


dsm.sys jus have the mandatory parameters nothing inthere for performance tuning.

The usual suspects are marked in read but why is it idle for over 60 minutes is the big question.

Regards,
TSMDUMBER

 

[mahmurth]

In your case the producer session which is responsible for querying the server for establishing communication with the server and resporting results to the server is getting terminated after 60 minutes.

The producer session (43593) is getting terminated due to timeout, while there is nothing for producer session to do and will get restarted when needed. And producer session again re-started (43669) when it has some work to do.

May be you can use resourceutilization 1 and check. By doing this, backups will share one session for both producer and consumer sessions and will eliminate session timeout.

Hope this helps you.

 

[domino]

...
02/07/11 02:12:09 ANR0482W Session 43593 for node LI0EBDB1P (Linux86)
terminated - idle for more than 60 minutes. (SESSION:
43593)

Increase the value for IDLETIMEOUT option, e.g.

SETOPT IDLETimeout 240