January 18, 2007 at 5:44 pm
SQL Server 2000 EE on a Win2K cluster. Four 1.5ghz processors and 4gb of memory. Optimizing a 100gb database. Recently, the optimization job quit working. The job wouldn't fail. SQL Server would simply freeze causing the cluster to recycle it. Here are some of the messages I COULD find.
[Microsoft SQL-DMO (ODBC SQLState: 01000)] Error 0: This server has been disconnected. You must reconnect to perform this operation.
** Execution Time: 1 hrs, 23 mins, 30 secs **
Deleting old text reports... 0 file(s) deleted.
End of maintenance plan 'dbsprtHc6' on 1/18/2007 6:12:42 PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = b; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
This occurs at the same particular table during the job. I have attempted changing MAXDOP from using all 4 processors to 3 of them with the same results. Dynamic memory is configured to use all available memory. This database isn't that heavily used. I restored the database to a test system and all worked fine. The average disk queue length during the most recent optimization run was 34.9 with a maximum of 115. It's apparently a disk issue but not sure why this began so recently. Does anyone have any ideas on how to get this to complete until the disk issue is addressed?
January 18, 2007 at 11:16 pm
Might be your Maintenance plan has the option to repair the db incase of corruption..
Please remove it because SQL server tries bring bring the db in single user mode...when it tries to reparir...
Did you check the cluster log and system log for any errors?
MohammedU
Microsoft SQL Server MVP
January 19, 2007 at 5:31 am
Repair has never been checked on this plan. Some of the errors in my original post came from the system log and the cluster log. That's about all I have been given to work with.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply