April 14, 2013 at 2:01 am
Hi,
We are running DBCC CHECKDB WITH ALL_ERRORMSGS.
After couple of minutes, the execution fails, sql service crashes and we get the following error:
Msg 64, Level 20, State 0, Line 0
A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
We then retry executing the same command again. In the second attempt the command executes successfully.
Why is it failing on the first attempt?
April 14, 2013 at 4:27 am
What's in the SQL error log?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 15, 2013 at 3:13 am
Nothing special. It just show the the SQL Service is restarting.
April 15, 2013 at 3:18 am
If SQL's failing abruptly there should be a message somewhere (not the error log that shows the start, the previous one)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 15, 2013 at 3:26 am
The last log is recorded before the CHECKDB by 20 minutes and then the next message is when the SQL service restarted.
April 15, 2013 at 3:32 am
Windows event logs?
Without some log of something it's going to be near-impossible to even tell what happened, let alone why.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 15, 2013 at 3:37 am
Windows log show that cluster have failed over to the other node since connectivity to disks 1,2,3,4 have been lost.
April 15, 2013 at 3:53 am
Right, that's a good hint.
SQL's system databases are on one of those drives? If so, with connectivity lost to a drive, SQL will fail immediately, no way around that.
Can you speak to your storage admin, see if he can see anything in the storage logs that may indicate why connectivity to the drives was lost?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 15, 2013 at 4:06 am
That was already tested. There is no problem on the storage level.
We can see high I/O during DBCC CHECKDB execution but there is nothing in the storage logs that refer to a connectivity problem.
April 15, 2013 at 4:32 am
The windows logs showing a loss of connectivity to the drives certainly indicates some problem with the storage, specifically that the drives went away temporarily. If SQL's system databases were on those drives, then losing connectivity to the drives would result in SQL terminating.
You need to figure out why the connectivity to the drives is being lost and resolve that.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 15, 2013 at 5:56 am
pete_20 (4/14/2013)
Hi,We are running DBCC CHECKDB WITH ALL_ERRORMSGS.
After couple of minutes, the execution fails, sql service crashes and we get the following error:
Msg 64, Level 20, State 0, Line 0
A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
We then retry executing the same command again. In the second attempt the command executes successfully.
Why is it failing on the first attempt?
How large is the database you are checking?
How much free space is on the volume?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply