hi Thida, If your commtimeout value on TSM server is 60 (seconds), it's too low. Yes it might work for b/a client type of backups not with TDPO. RMAN doesn't backup NULL blocks. So it takes time for RMAN to scan through the Oracle data block to gather data. Increasing commtimeout value doesn't hurt anything except when the client is actually hung and doesn't sign off from the server, server will not disconnect your client session for the specified amount of time. So you will see inactive client sessions for a little bit longer on the server console. The only way to fix your problem is to increase commtimeout value to about 600.
regards, Thiha >Can anybody help please.... >I 've got this error.. >After run the tdp oracle >TcpRead(): recv(): errno = 73 >09/28/01 09:23:50 sessRecvVerb: Error -50 from call to 'readRtn'. >09/28/01 09:23:50 cuConfirm: Received rc: -50 trying to receive >ConfirmResp verb >09/28/01 09:23:50 TcpFlush: Error 9 sending data on Tcp/Ip socket >4294967295. >09/28/01 09:23:50 sessSendVerb: Error sending Verb, rc: -50 >09/28/01 09:23:50 TcpFlush: Error 9 sending data on Tcp/Ip socket >4294967295. >09/28/01 09:23:50 sessSendVerb: Error sending Verb, rc: -50
