Msg 8964, Level 16, State 1, Line 1

SQLServerCentral is supported by Red Gate Software Ltd.

Home Tags Articles Editorials Forums Scripts Videos Blogs QotD Books Ask SSC SQL Jobs Training Authors About us Contact us Newsletters Advertise Write for us

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Data Corruption » Msg 8964, Level 16, State 1, Line 1

Msg 8964, Level 16, State 1, Line 1

Rate Topic

Display Mode

Topic Options

Author

Message

SQLdba-473999

Posted Tuesday, November 17, 2009 1:28 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, March 12, 2010 7:23 AM
Points: 118, Visits: 393

I ran DBCC CHECKDB WITH DATA_PURITY against a database and got
Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 789577851, index ID 1, partition ID 72057594040025088, alloc unit ID 71827864835260416 (type LOB data). The off-row data node at page (1:830), slot 1, text ID 119930880 is not referenced.

I then ran DBCC DBREINDEX which didn't help.
I recreated under a different name which didn't help.
I read that DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS fixes but you can lose data. So I wanted to export the table before doing so and got this error.

Error 0xc0208030: Data Flow Task: The data type for "input column "Col1" (98)" is DT_IMAGE, which is not supported.
Use DT_TEXT or DT_NTEXT instead and convert the data from, or to, DT_IMAGE using the data conversion component.
(SQL Server Import and Export Wizard)

I'm a little confused on what my actual problem is, the index or the column? The index referenced in the first error is a clustered, unique index on a column that is an int, not null. The column mentioned in the Data Flow error is image, null.

Any help is greatly appreciated!

Post #820365

Paul Randal

Posted Tuesday, November 17, 2009 2:10 PM

SSCommitted

Group: General Forum Members
Last Login: Yesterday @ 10:14 PM
Points: 1,526, Visits: 1,208

If this is the only error, then repair won't cause any data loss, as the image that it references isn't linked into the table.

Is this a database that you've recently upgraded? I'm curious as to why the corruption occured in the first place - my guess is that the corruption was there from a previous version. (Also, the fact that you're running WITH DATA_PURITY - which is recommended after an upgrade to 2005.)

Thanks

Paul Randal
CEO, SQLskills.com - Need a database maintenance/ops/HA/DR audit? Send me email!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine and SQL Server Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

Post #820396

SQLdba-473999

Posted Tuesday, November 17, 2009 2:17 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, March 12, 2010 7:23 AM
Points: 118, Visits: 393

Paul Randal (11/17/2009)

Well that is good news. I looked at the table, 47 rows only, and for that column all the values are null. I'm wondering what could possibly be the problem?

I recently migrated from 2000 to 2005 but went back to check the old database and the problem exists there as well.

Post #820399

vkundar

Posted Monday, November 23, 2009 10:49 PM

Valued Member

Group: General Forum Members
Last Login: Thursday, March 11, 2010 2:42 AM
Points: 59, Visits: 250

Paul Randal (11/17/2009)

Is this a database that you've recently upgraded? I'm curious as to why the corruption occured in the first place - my guess is that the corruption was there from a previous version. (Also, the fact that you're running WITH DATA_PURITY - which is recommended after an upgrade to 2005.)

Thanks

I love the way Paul reply..streight and simple.

Corruption might be from the previous version.

Cheers,

Got an idea..share it !!

DBA_Vishal

Post #823661

« Prev Topic | Next Topic »

Permissions