Check DB failed

Question

Check DB failed

ramyours2003

SSChampion

Points: 12268
More actions
December 19, 2017 at 8:30 am

#409874

in one of my server CHeck DB failed due to the below error
The operating system returned error 1450(failed to retrieve text for this error. Reason: 1815)
to SQL Server during a write at offset 0x00008dfc3ca000 in file g:/mssql/DEF.mdf.
How to resolve the issue . ?

Viewing 15 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic. Login to reply

NorthernSoul SSCertifiable Points: 6869 More actions · Answer 1

How much memory does your server have and what have you set your max server memory to be? Do you have anything else running on the server and how many instances are running?

Thanks

SQLPirate SSCrazy Points: 2880 More actions · Answer 2

ramyours2003 - Tuesday, December 19, 2017 8:30 AM
in one of my server CHeck DB failed due to the below error
The operating system returned error 1450(failed to retrieve text for this error. Reason: 1815)
to SQL Server during a write at offset 0x00008dfc3ca000 in file g:/mssql/DEF.mdf.
How to resolve the issue . ?

1450 should be "Insufficient system resources exist to complete the requested service."
Possibly a space issue during your checkdb.

ramyours2003 SSChampion Points: 12268 More actions · Answer 3

The min memory is 0 and max memory is 20 GB and only one instance is running on the server .

NorthernSoul SSCertifiable Points: 6869 More actions · Answer 4

ramyours2003 - Wednesday, December 20, 2017 12:37 AM
The min memory is 0 and max memory is 20 GB and only one instance is running on the server .

And how much memory does your server have? As SQLPirate said, have you checked space?

Thanks

ramyours2003 SSChampion Points: 12268 More actions · Answer 5

Sorry we have 4 instances are there on the server , RAM is 126 GB and the data files are placed in mount points . All the four instances memory configuration is around 80 GB and also we 20% of free space on the mount point on the mount point where the check db is failed on the instance 1

inst1-20 GB
inst2-40 GB
inst3-8GB
inst4-8 GB

NorthernSoul SSCertifiable Points: 6869 More actions · Answer 6

It might be that you need to increase the amount of memory available to SQL Server in the affected instance. If that doesn't work run your checkdb again but monitor the system resources as it's running and you should be able to spot where the issue lies.

Thanks

John Mitchell-245523 SSC Guru Points: 148809 More actions · Answer 7

ramyours2003 - Wednesday, December 20, 2017 1:27 AM
Sorry we have 4 instances are there on the server , RAM is 126 GB and the data files are placed in mount points . All the four instances memory configuration is around 80 GB and also we 20% of free space on the mount point on the mount point where the check db is failed on the instance 1
inst1-20 GB
inst2-40 GB
inst3-8GB
inst4-8 GB

Your SQL Server instances use a total of 76GB of 126GB on the server? Do any other applications run on the server? I can't think why the operating system would need 50GB to itself.

John

ramyours2003 SSChampion Points: 12268 More actions · Answer 8

Thanks for your replies , when we checked in job log we found

Msg 233, Sev 16, State 1: Communication link failure [SQLSTATE 08S01]
Msg 16389, Sev 16, State 1: Communication link failure [SQLSTATE 08S01]

is some thing to investigatete from storage?

John Mitchell-245523 SSC Guru Points: 148809 More actions · Answer 9

Have you checked what that error message means? Sounds like some kind of network issue to me, but don't take my word for that.

John

NorthernSoul SSCertifiable Points: 6869 More actions · Answer 10

I agree with John, it sounds more related to the network.

Cheers

Perry Whittle SSC Guru Points: 234013 More actions · Answer 11

ramyours2003 - Tuesday, December 19, 2017 8:30 AM
in one of my server CHeck DB failed due to the below error
The operating system returned error 1450(failed to retrieve text for this error. Reason: 1815)
to SQL Server during a write at offset 0x00008dfc3ca000 in file g:/mssql/DEF.mdf.
How to resolve the issue . ?

Have you checked the sql server log for any other errors

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

ramyours2003 SSChampion Points: 12268 More actions · Answer 12

and also in job log we found

Msg 233, Sev 16, State 1: Communication link failure [SQLSTATE 08S01]
Msg 16389, Sev 16, State 1: Communication link failure [SQLSTATE 08S01]

Perry Whittle SSC Guru Points: 234013 More actions · Answer 13

ramyours2003 - Wednesday, December 20, 2017 9:00 AM
and also in job log we found
Msg 233, Sev 16, State 1: Communication link failure [SQLSTATE 08S01]
Msg 16389, Sev 16, State 1: Communication link failure [SQLSTATE 08S01]

is this a clustered setup

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" 😉

ramyours2003 SSChampion Points: 12268 More actions · Answer 14

ramyours2003

SSChampion

Points: 12268

December 21, 2017 at 12:52 am

#1973036

No its a std alone server .