October 11, 2017 at 1:49 am
I have encountered the below error message when i try to do sql query.
Server: Msg 823, Level 24, State 2, Line 1
I/O error 23(Data error (cyclic redundancy check).) detected during read at offset 0x000001ac1c4000 in file 'C:\sql\PDB_Data.mdf'.
Did a DBCC CHECKDB (PDB) WITH NO_INFOMSGS, ALL_ERRORMSGS and below is the result.
Server: Msg 8946, Level 16, State 12, Line 2
Table error: Allocation page (1:72792) has invalid PFS_PAGE page header values. Type is 0. Check type, object ID and page ID on the page.
Server: Msg 8921, Level 16, State 1, Line 1
CHECKTABLE terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:72792) with latch type UP. 菴恟 failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:72792) with latch type UP. 菴恟 failed.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 8 pages from (1:72792) to (1:80879). See other errors for cause.
CHECKDB found 2 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 2 allocation errors and 1 consistency errors in database 'PDB'.
Hope to get some help on what can i do. Do not have a clean back up of it.
P.S. Have no idea on what the chinese text are. Everytime i run the DBCC CHECKDB, the chinese text is always different.
Thanks in advance.
Ron
October 11, 2017 at 9:27 pm
bump
Urgently seeking for help to resolve issue.
October 11, 2017 at 10:33 pm
I've seen that error when a bug with storage device has taken some sort of lock on a segment of data (as small as 32kb in some cases) and won't release it. Windows has access to the rest of the file, but just a few blocks cannot be accessed.
Sometimes the solution is a just cold boot of the server to get it to release the blocks.
In one case, the SAN detected disk-level corruption and held the block, so we went to a backup. In any case you should already be deep into your DR plan for this database, and getting ready to restore from backup and roll forward the logs.
-Eddie
Eddie Wuerch
MCM: SQL
December 4, 2018 at 12:14 am
This may help you out:
https://www.sqlserverlogexplorer.com/resolve-microsoft-sql-server-error-823/
December 4, 2018 at 1:02 am
spherical_x - Wednesday, October 11, 2017 1:49 AMI have encountered the below error message when i try to do sql query.Server: Msg 823, Level 24, State 2, Line 1
I/O error 23(Data error (cyclic redundancy check).) detected during read at offset 0x000001ac1c4000 in file 'C:\sql\PDB_Data.mdf'.Did a DBCC CHECKDB (PDB) WITH NO_INFOMSGS, ALL_ERRORMSGS and below is the result.
Server: Msg 8946, Level 16, State 12, Line 2
Table error: Allocation page (1:72792) has invalid PFS_PAGE page header values. Type is 0. Check type, object ID and page ID on the page.
Server: Msg 8921, Level 16, State 1, Line 1
CHECKTABLE terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:72792) with latch type UP. è´æŸ failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:72792) with latch type UP. è´æŸ failed.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 8 pages from (1:72792) to (1:80879). See other errors for cause.
CHECKDB found 2 allocation errors and 1 consistency errors not associated with any single object.
CHECKDB found 2 allocation errors and 1 consistency errors in database 'PDB'.Hope to get some help on what can i do. Do not have a clean back up of it.
P.S. Have no idea on what the chinese text are. Everytime i run the DBCC CHECKDB, the chinese text is always different.
Thanks in advance.
Ron
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 8 pages from (1:72792) to (1:80879).
Looks like the corruption is with allocation pages, Check the recent backup and make a another copy of database and try checkDB and verify data.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
December 4, 2018 at 7:12 am
a year later, and people are just now contributing suggestions.
I would suggest that either the OP has fixed the problem, or he has found a new opportunity. Possibly in the fast food business, where DB means Double Bacon.
Thomas Rushton
blog: https://thelonedba.wordpress.com
December 4, 2018 at 10:50 pm
ThomasRushton - Tuesday, December 4, 2018 7:12 AMa year later, and people are just now contributing suggestions.I would suggest that either the OP has fixed the problem, or he has found a new opportunity. Possibly in the fast food business, where DB means Double Bacon.
Ha ha.. I just took it from "Latest forum posts" home page of SSC.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy