Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 7,2000
»
Data Corruption
»
REPAIR_ALLOW_DATA_LOSS not resolving the...
19 posts, Page 2 of 2
««
1
2
REPAIR_ALLOW_DATA_LOSS not resolving the allocation error
Rate Topic
Display Mode
Topic Options
Author
Message
Lynn Pettis
Lynn Pettis
Posted Wednesday, August 29, 2012 3:14 PM
SSC-Insane
Group: General Forum Members
Last Login: Yesterday @ 11:14 PM
Points: 21,832,
Visits: 27,862
Not that much in there really and the following is the only error I see:
DBCC results for 'EXAMPLEUsers'.
Msg 2576, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:3878384) in object ID 1591012749, index ID 22, partition ID 72057594103005184, alloc unit ID 72057594108379136 (type In-row data), but it was not detected in the scan.
There are 29537 rows in 697 pages for object "EXAMPLEUsers".
CHECKDB found 1 allocation errors and 0 consistency errors in table 'EXAMPLEUsers' (object ID 1591012749).
Lynn Pettis
For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here
or
when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here
and
here
Managing Transaction Logs
SQL Musings from the Desert
Fountain Valley SQL
(My Mirror Blog)
Post #1351927
sierra4
sierra4
Posted Thursday, August 30, 2012 7:23 AM
SSC Rookie
Group: General Forum Members
Last Login: Yesterday @ 1:07 PM
Points: 34,
Visits: 430
gail,
the complete output for
DBCC CHECKDB (ExampleProd3x) WITH NO_INFOMSGS, ALL_ERRORMSGS
is
Msg 2576, Level 16, State 1, Line 1
The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:3878384) in object ID 1591012749, index ID 22, partition ID 72057594103005184, alloc unit ID 72057594108379136 (type In-row data), but it was not detected in the scan.
CHECKDB found 1 allocation errors and 0 consistency errors in table 'EXAMPLEUsers' (object ID 1591012749).
CHECKDB found 1 allocation errors and 0 consistency errors in database 'ExampleProd3x'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (ExampleProd3x).
thanks
Post #1352204
sierra4
sierra4
Posted Thursday, August 30, 2012 7:43 AM
SSC Rookie
Group: General Forum Members
Last Login: Yesterday @ 1:07 PM
Points: 34,
Visits: 430
the results for
select * from sys.indexes where object_id=1591012749
name index_id
PK_EXAMPLEUsers 1 CLUSTERED 1
IX_EXAMPLEUsers_clientid 7 NONCLUSTERED 0
_dta_index_EXAMPLEUsers_9_1591012749__1K 8 NONCLUSTERED 0
_dta_index_EXAMPLEUsers_9_1591012749__2K 14 NONCLUSTERED 0
_dta_index_EXAMPLEUsers_9_1591012749__3K 15 NONCLUSTERED 0
_dta_index_EXAMPLEUsers_9_1591012749__4K 16 NONCLUSTERED 0
_dta_index_EXAMPLEUsers_9_1591012749__5K 18 NONCLUSTERED 0
_dta_index_EXAMPLEUsers_9_1591012749__6K 20 NONCLUSTERED 0
i don't see index_id 22 which was specified in the dbcc results
does this mean the table itself needs to be recreated?
thanks
Post #1352223
GilaMonster
GilaMonster
Posted Thursday, August 30, 2012 11:11 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 1:13 AM
Points: 38,103,
Visits: 30,394
Looks like either someone's been messing with the metadata or there's been some odd problem dropping an index somewhere. The index structure still exists but the metadata's gone.
Recreating the table might help (select into, drop the old table, rename the new one, recreate all indexes). If it doesn't, you'll need to recreate the database.
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #1352380
RBarryYoung
RBarryYoung
Posted Thursday, August 30, 2012 12:20 PM
SSCrazy Eights
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 11:17 AM
Points: 9,855,
Visits: 9,376
You know, instead of "REPAIR_ALLOW_DATA_LOSS", they should have named that option "RISK_SHOOTING_YOURSELF_IN_THE_FOOT", or maybe "DO_NOT_USE_UNLESS_YOU_REALLY_KNOW_WTF_YOU_ARE_DOING".
-- RBarryYoung
,
(302)375-0451
blog:
MovingSQL.com
, Twitter:
@RBarryYoung
Proactive
Performance Solutions, Inc.
"Performance is our middle name."
Post #1352413
GilaMonster
GilaMonster
Posted Thursday, August 30, 2012 1:33 PM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 1:13 AM
Points: 38,103,
Visits: 30,394
To be honest, this looks more like it could have been caused by someone doing a DELETE FROM sysindexes WHERE... on SQL 2000 (if the DB was an upgrade)
I've seen an IAM lose it's link to the metadata before, but not a case where all of the index metadata was completely gone.
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #1352463
RBarryYoung
RBarryYoung
Posted Thursday, August 30, 2012 2:57 PM
SSCrazy Eights
Group: General Forum Members
Last Login: Wednesday, June 12, 2013 11:17 AM
Points: 9,855,
Visits: 9,376
Gail:
Didn't the OP say that this was Sql Server 2005? Can you still do something like that on 2005? (Yikes!!!)
-- RBarryYoung
,
(302)375-0451
blog:
MovingSQL.com
, Twitter:
@RBarryYoung
Proactive
Performance Solutions, Inc.
"Performance is our middle name."
Post #1352510
GilaMonster
GilaMonster
Posted Friday, August 31, 2012 12:06 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 1:13 AM
Points: 38,103,
Visits: 30,394
RBarryYoung (8/30/2012)
Didn't the OP say that this was Sql Server 2005? Can you still do something like that on 2005? (Yikes!!!)
Yes, it is actually still possible, though I'm not going say how.
DB may be SQL 2005 now, but if it was upgraded from SQL 2000 it could be someone messed with it there. Or it could just be some weird-*** corruption.
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #1352605
karrylopez
karrylopez
Posted Monday, September 03, 2012 7:03 AM
Forum Newbie
Group: General Forum Members
Last Login: Friday, April 05, 2013 4:48 AM
Points: 4,
Visits: 2
As per your discuss and all reply i think so that now your data is corrupted and you should be used a third party data recovery software.
There are so many Sql server related data recovery software you can find it on Google just search as "repair sql database" and you can find a large list of software you can one of them .
As I have personal experience with a data recovery software which was really helpful for me if you want i can recommended for which is "
Kernel for Sql Server Repair[b]
[/b]"
You should be try this.
Post #1353499
« Prev Topic
|
Next Topic »
19 posts, Page 2 of 2
««
1
2
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.