adsmserv:/usr/lpp/adsmserv/bin/dsmserv.opt already has the line
COMMTimeout 7200

do you think I should boost it even higher? That should already be 2 hours!
What would be the downside of having a huge COMMTIMEOUT?

Kai.

On Mon, 29 Jan 2001 09:53:20 -0800, Thiha Than <Thiha_Than AT TIVOLI DOT COM> 
replied
to me:
>
>Subject: RMAN ADSM Errors
>
>hi,
>
>When you do incremental backup, Oracle has to scan through the data block
>to figure out which blocks are changed.  If there isn't much change in the
>database, it takes a while until Oracle finds some changed blocks.  On TSM
>server, if your commtimeout value is set to a low value, and your sessions
>are idle for commtimeout value while Oracle is still looking for the
>changed blocks, your session will be canceled from the server.  It looks
>like you are running into this situation.  Please increase your commtimeout
>value on the server to a value like 1000.
>
>regards,
>Thiha
>
>>The level 0 backup ran fine, but now the DBA is trying to get level 1
>backups,
>>and she keeps erroring out. She starts 3 threads. The first two go to
>idlewait
>>then die, the third one seems to be succeeding until the whole process
>dies.