July 26, 2004 at 8:49 am
I came accross this error and though might be usefull for others though i might be too dump
17052 Error 823.Severity 24,State 1
Try to fix by using CheckAlloc.
server:msg 8998,level 16 ,state 1,line 0
Page corruptions on the GAM,SGAM oe PFS pages do not allow Checkalloc to verify database ID 7 pages from (1:511232) to (1:768000).
see other errors for cause
Dialed into the server and run Dbcc CheckDb('xyz') got the following errors.
CHECKDB found 1 allocation errors and 27 consistency errors in database
'xyz'.
Try to fix by running dbcc checkdb ('xyz',repair_rebuild) with all_errormsgs
got the following errors
Table Corrupt: Object ID 0, index ID 0, page ID (1:760272). The PageId in the
page header = (0:0).
The system cannot self repair this error.
CHECKDB found 0 allocation errors and 1 consistency errors in table 'pqr'
(object ID 229575856).
CHECKDB found 1 allocation errors and 27 consistency errors in database
'xyz'.
CHECKDB fixed 0 allocation errors and 1 consistency errors in database 'xyz'.
Ran the dbcc checktable ('pqr',repair_rebuild) with all_errormsgs
DBCC results for 'pqr'.
There are 47347 rows in 3643 pages for object 'pqr'.
Again Ran the dbcc checkdb ('xyz',repair_rebuild) with all_errormsgs
got the following errors
CHECKDB found 1 allocation errors and 26 consistency errors in database
'xyz'.
DBCC execution completed. If DBCC printed error messages,
Ran the dbcc checktable ('abc',repair_rebuild) with all_errormsgs
DBCC results for 'abc'.
There are 53821 rows in 999 pages for object 'abc'.
Ran dbcc checktable (sysobjects, repair_rebuild ) with all_errormsgs
CAME TO CONCLUSION THAT
Error 823 indicates problems with physical drives.Need to ran the chkdsk on the drives as drives looks to be corrupted.
When did chkdsk it came successfull with out any issue.Thus need to come back to database
detached, reattached and renamed xyz on f drive to oldxyz and tried
running checkdb again on xyz on d drive - with no success
FINNALY
dropped database xyz and recreated /Ran dts - transferred old xyz to the
newly created xyz Detached old xyz and ran queries to verify database
successfully
Started services successfully
Ran database backup and transaction log backup successfully
verified applications could be opened and no errors in event log
So Simple isnt it
Mohammed
MCSA,MCDBA
July 26, 2004 at 10:37 am
It appears that you had some type of corruption in the SQL tables at the physical level. If chkdsk worked, then bcp out/bcp in , transfer to new db, etc, even rebuild clustered index might have worked as long as you could read all tables.
Be sure your rowcounts match exactly and a select * from all tables works. If not, be sure you call MS Support for help.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
July 26, 2004 at 11:32 am
steve ,
In my post i also wrote that it got fixed as per
FINALLY
dropped database xyz and recreated /Ran dts - transferred old xyz to the
newly created xyz Detached old xyz and ran queries to verify database
successfully
Started services successfully
Ran database backup and transaction log backup successfully
verified applications could be opened and no errors in event log
So Simple isnt it
Mohammed
MCSA,MCDBA
July 26, 2004 at 11:42 am
Any one got a simple and easy web link or Article for the Bulk Copy Utilty.Need to have simple Examples and easy for referance when needed .
Mohammed
MCSA,MCDBA
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply