Hi Del, backup of SQL is executed at 03:00 o'clock morning and I am sure no jobs at SQL were running at this time. It is relatively small system with about 2,5 GB of full backup ... My last question, exactly what time-out parameter am I supposed to increase? I hadn't found any such timeout value in TDP doc.
Many thanks TOM -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Del Hoobler Sent: Friday, April 05, 2002 3:40 PM To: [EMAIL PROTECTED] Subject: Re: TDP SQL 2.2 problem > ACO5424E Could not connect to SQL server; SQL server returned: > [Microsoft][ODBC SQL Server Driver]Timeout expired Microsoft SQL-DMO (ODBC > SQLState: HYT00) (HRESULT:0x80040000) Tom, Do you know if there were some large jobs running against your SQL server at the times that the time-out occurred? It is possible that the SQL Server was starving TDP from getting a connection. TDP runs local and if SQL Server doesn't get a connection within a certain time limit, it will time-out. A TDP trace of the time-out as well as an idea of what other activity is going on against the SQL server will help determine what is going on. It's also possible that TDP may need to increase its time-out value in order to satisfy your environment. If you continue to see this, please call IBM support. Thanks, Del ---------------------------------------------------- Del Hoobler IBM Corporation [EMAIL PROTECTED] - Leave everything a little better than you found it. - Smile a lot: it costs nothing and is beyond price.
