more db errors - 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

more db errors

Author

Topic

PCpsyco
Starting Member

11 Posts

Posted - 2008-05-05 : 15:54:38

I have a dynamics db that is used for archival purposes and it is not used very often. Now that someone decided to get some info out of it it wont let them. when I run dbcc I get the following message:

Msg 5242, Level 16, State 1, Line 1
An inconsistency was detected during an internal operation in database 'PACIF'(ID:12) on page (1:19451). Please contact technical support. Reference number 6.
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.

I was just wondering if this meant anything to any of you? and since all of my backtapes have the same issue, is there any way to fix it?

thanks in advance.

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2008-05-05 : 16:57:20

It's an error that was raised in RTM/SP1 that says there's an incorretc NULL bitmap offset discovered while reading a page. It shouldn't be raised during CHECKDB and has been removed in SP2. Are you running RTM or SP1?

Thanks

Paul Randal
SQL Server MVP, Managing Director, SQLskills.com

PCpsyco
Starting Member

11 Posts

Posted - 2008-05-05 : 18:52:15

according to this I should be on sp2
SQL Server 9.0.3054 - sa
correct?
Thanks

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-05-05 : 22:37:15

Yes, you are in sp2.

PCpsyco
Starting Member

11 Posts

Posted - 2008-05-05 : 22:49:07

I hope you don't think that it was a smart A** response now that I'm reding it over again. I was actually asking because I have heard of cases of sql sp2 not sticking or not upgrading all tables. but I'm just a newb. also can it be the compability mode that's screwing this up?

thanks again,

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-05-05 : 23:22:23

What's compatibility level for that db? You can find out from db properties -> options. Once applied sql sp, whole server is in that level.

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2008-05-05 : 23:22:40

That's weird - let me investigate a bit more.

Paul Randal
SQL Server MVP, Managing Director, SQLskills.com

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2008-05-06 : 23:08:40

ok - I'm misremembering (been a while since I was in the code and I'm getting older every year :-)

This could be a case where CHECKDB is trying to use a record (e.g. to pull in an off-row column) before the record has been validated - and the record is corrupt. It would be really useful to know where the problem is being raised - can you do the following:

dbcc dumptrigger ('set', 5242)
go
run checkdb
go
dbcc dumptrigger ('clear', 5242)
go

There will be a sqldumpxxxx.txt file generated in the MSSQL\LOG directory with the call stack of where hit the problem. If you can do that and send it to me (v-prand@microsoft.com or paul@sqlskills.com) I'll have the dev team take a look.

Thanks

Paul Randal
SQL Server MVP, Managing Director, SQLskills.com

PCpsyco
Starting Member

11 Posts

Posted - 2008-05-07 : 18:17:50

Thanks a lot, I appreciate the time you are taking to resolve this.

PCpsyco
Starting Member

11 Posts

Posted - 2008-05-07 : 18:47:55

so when I run the query this is what I get
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'run'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

any Ideas?
Thanks

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-05-07 : 18:54:53

He wants you to run DBCC CHECKDB rather than "run checkdb":
DBCC CHECKDB(dbName)

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Database maintenance routines:
http://weblogs.sqlteam.com/tarad/archive/2004/07/02/1705.aspx

PCpsyco
Starting Member

11 Posts

Posted - 2008-06-18 : 20:04:02

I'm back trying to resolve this. I thought that if I forgot about it, it would just go away but it didn't. Runing
dbcc dumptrigger ('set', 5242)
go
dbcc checkdb
go
dbcc dumptrigger ('clear', 5242)
go

gives me the original error of
"Msg 5242, Level 16, State 1, Line 1
An inconsistency was detected during an internal operation in database 'PACIF'(ID:13) on page (1:19451). Please contact technical support. Reference number 6.
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors"
and then it stops. thanks again and any help would be appreciated

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources