error 'An inconsistency was detected during an internal operation in database '

Question

error 'An inconsistency was detected during an internal operation in database '

mayank jarsaniya

Hall of Fame

Points: 3532
More actions
August 7, 2009 at 5:46 am

#213255

I get following massage repeatedly in duration of 2 or 3 days.
Database name is 'DBNAME'.
'An inconsistency was detected during an internal operation in database
'DBNAME'(ID:16) on page (1:524021).
Please contact technical support. Reference number 4.'
I run following script and it worked out each and every time.
GO
ALTER DATABASE DBNAME SET EMERGENCY
ALTER DATABASE DBNAME SET SINGLE_USER
DBCC CHECKDB (DBNAME, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS;
DBCC CHECKDB WITH NO_INFOMSGS;
ALTER DATABASE DBNAME SET MULTI_USER
But I want to know the issue and permanent solution for them.
I have used 'SELECT * FROM msdb..suspect_pages'
but it does not give relevant results for my problem.
Can I know which table has corruption or any thing else which solve this problem or explain?

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Why on earth are you running repair without checking what's wrong? Repair is a last resort. It should never be the first thing done and it should never be run without doing some analysis of the problem first.

Take a look at this article. http://www.sqlservercentral.com/articles/65804/

Next time this happens, run the following and post the full output.

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

Have you checked for errors from the IO subsystem - disks, raid controller, SAN, etc?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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

mayank jarsaniya Hall of Fame Points: 3532 More actions · Answer 2

Hi I et following msg:

DBBC MSG:

'

Msg 8914, Level 16, State 1, Line 1

Incorrect PFS free space information for page (1:42063) in object ID 485576768, index ID 1, partition ID 72057594039173120, alloc unit ID 72057594043957248 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

Msg 8914, Level 16, State 1, Line 1

Incorrect PFS free space information for page (1:42064) in object ID 485576768, index ID 1, partition ID 72057594039173120, alloc unit ID 72057594043957248 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

Msg 8914, Level 16, State 1, Line 1

Incorrect PFS free space information for page (1:42065) in object ID 485576768, index ID 1, partition ID 72057594039173120, alloc unit ID 72057594043957248 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

Msg 8914, Level 16, State 1, Line 1

Incorrect PFS free space information for page (1:42066) in object ID 485576768, index ID 1, partition ID 72057594039173120, alloc unit ID 72057594043957248 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

Msg 8914, Level 16, State 1, Line 1

Incorrect PFS free space information for page (1:42068) in object ID 485576768, index ID 1, partition ID 72057594039173120, alloc unit ID 72057594043957248 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

CHECKDB found 0 allocation errors and 5 consistency errors in table 'rep_keysentences' (object ID 485576768).

CHECKDB found 0 allocation errors and 5 consistency errors in database 'DBNAME'.

repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (DBNAME).'

mayank jarsaniya Hall of Fame Points: 3532 More actions · Answer 3

please note that this msg is previously before running repair option.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

What's the version of 2005 that you're on? (run SELECT @@Version)

I know there were a couple bugs in earlier versions of 2005 that caused this.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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

mayank jarsaniya Hall of Fame Points: 3532 More actions · Answer 5

Hi,

I am running

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 6

You've got SQL 2005 RTM there (unpatched). I would suggest that you apply service pack 3 as soon as you can. Once that's applied you shouldn't see these errors any more. If you do, it's a bug and you should probably call Customer Support.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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

mayank jarsaniya Hall of Fame Points: 3532 More actions · Answer 7

Hi,

As per your instruction i have updated my installation with Sp3.

Now i running with following version (instead of previously mentioned/old one.)

select @@version

now I have used DBBC CHECKDB for my database and i get following error.

Msg 8914, Level 16, State 1, Line 1

Incorrect PFS free space information for page (1:374) in object ID 1077578877, index ID 1, partition ID 72057594140950528, alloc unit ID 72057594045661184 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

Msg 8914, Level 16, State 1, Line 1

Incorrect PFS free space information for page (1:219264) in object ID 1077578877, index ID 1, partition ID 72057594140950528, alloc unit ID 72057594045661184 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

Msg 8914, Level 16, State 1, Line 1

Incorrect PFS free space information for page (1:219280) in object ID 1077578877, index ID 1, partition ID 72057594140950528, alloc unit ID 72057594045661184 (type LOB data). Expected value 0_PCT_FULL, actual value 100_PCT_FULL.

have any solution for this error?

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 8

Run repair with allow_data_loss (it won't actually lost any data in this case). Those may be errors left over from before the service pack was applied.

If, after repairing you get these again, call Microsoft's Customer Support people. All the errors relating to inaccurate PFS free space are supposed to have been fixed by SP3

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
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

mayank jarsaniya Hall of Fame Points: 3532 More actions · Answer 9

Hi Gila Monster,

Hi one thing i have noted.....

your selection for new photograph in your profile is good one.