error for DBCC Checkdb - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

Data Corruption Issues

error for DBCC Checkdb

Author

Topic

jiayue
Starting Member

4 Posts

Posted - 2011-03-14 : 16:19:43

Hi, I'm getting the following results after running the script of
DBCC Checkdb ('DBNAME',repair_rebuild) with no_infomsgs, all_errormsgs
GO

--------------------------------------------
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=1146591273) of row (object_id=1146591273,parameter_id=1) in sys.parameters does not have a matching row (object_id=1146591273) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=1146591273) of row (object_id=1146591273,parameter_id=2) in sys.parameters does not have a matching row (object_id=1146591273) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=1146591273) of row (object_id=1146591273,parameter_id=3) in sys.parameters does not have a matching row (object_id=1146591273) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=1146591273) of row (object_id=1146591273,parameter_id=4) in sys.parameters does not have a matching row (object_id=1146591273) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=1146591273) of row (object_id=1146591273,parameter_id=5) in sys.parameters does not have a matching row (object_id=1146591273) in sys.objects.
CHECKDB found 0 allocation errors and 5 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 5 consistency errors in database 'DBNAME'.

Can anyone take a look for me and point me a direction?

thanks a lot!

JJ

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-03-14 : 16:56:25

Please run the following and post the full and complete output


DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

Got a backup from before this problem started? This is not repairable without some serious low-level (and very risky) hacking or a complete export and recreate of the DB.

--
Gail Shaw
SQL Server MVP

jiayue
Starting Member

4 Posts

Posted - 2011-03-15 : 09:07:30

hi Gail, thanks for looking into this for me.

here is the script:
DBCC CHECKDB (databasename) WITH NO_INFOMSGS, ALL_ERRORMSGS

here is the complete output:
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=1146591273) of row (object_id=1146591273,parameter_id=1) in sys.parameters does not have a matching row (object_id=1146591273) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=1146591273) of row (object_id=1146591273,parameter_id=2) in sys.parameters does not have a matching row (object_id=1146591273) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=1146591273) of row (object_id=1146591273,parameter_id=3) in sys.parameters does not have a matching row (object_id=1146591273) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=1146591273) of row (object_id=1146591273,parameter_id=4) in sys.parameters does not have a matching row (object_id=1146591273) in sys.objects.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (object_id=1146591273) of row (object_id=1146591273,parameter_id=5) in sys.parameters does not have a matching row (object_id=1146591273) in sys.objects.
CHECKDB found 0 allocation errors and 5 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 5 consistency errors in database 'databasename'.

I have three databases with this same error (there are same structure but used by different people) and the biggest is over $150GB in size. I have checked with the backup file we have and they all have the same issue.

Please let me know what to expect next, and if there is still anything I can do to fix it.

Again, thank you very much for your time!

JJ

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-03-15 : 09:54:12

There's no easy fix for this. this is not repairable by checkDB.

There are two options.
1) You can hack the system tables and try and fix the problem. Get it wrong and you could damage the database beyond repair. You may also lose support from MS by doing this. If you chose this route, see Paul's blog - http://sqlskills.com/BLOGS/PAUL/post/Disaster-recovery-101-fixing-metadata-corruption-without-a-backup.aspx
Your error is not exactly what Paul was showing, so you're partially on your own for fixing the problem if you go that way.

2) Script all objects. Export all data. Recreate the database.

While I can do the first, were I working on a client's database I would use the second as it's safer, although far more work.

--
Gail Shaw
SQL Server MVP

rahulrajpal08
Starting Member

8 Posts

Posted - 2011-03-22 : 06:48:18

Two solutions for the above problem:
Recreate the database and try to import all the records from an updated backup.
In case there is no backup available and you desperately need the database records, then you should read the below article:
unspammed

Database expert

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2011-03-22 : 07:02:49

Rather don't.

That article is incomplete and misleading, deleting a table is in no way the best solution for a corrupt page and it makes no mention of CheckDB's repair options. In fact it reads like just an advertisement for a data recovery tool.

The article refers to a different version of SQL than this question does. The question refers to either a SQL 2005 or 2008 database, that article is on a SQL 2000-specific corruption (there's no sysindexes table in SQL 2005)

The errors that the article badly handles are not the ones referred to in the initial post here. They are totally different problems with different resolutions.

--
Gail Shaw
SQL Server MVP

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources