HELP PLS :( What does "Error: 644, Severity: 21, State: 3" means and how can I fix it?

Question

HELP PLS :( What does "Error: 644, Severity: 21, State: 3" means and how can I fix it?

Viewing 8 posts - 16 through 22 (of 22 total)

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

maechismo_8514 SSCoach Points: 17510 More actions · Answer 1

GilaMonster (2/19/2009)

elay (2/19/2009)
Server: Msg 8933, Level 16, State 1, Line 1
Table error: Object ID 1654296953, index ID 50. The low key value on page (1:548364) (level 0) is not >= the key value in the parent (1:818682) slot 0.
Server: Msg 8934, Level 16, State 1, Line 1
Table error: Object ID 1654296953, index ID 50. The high key value on page (1:1754006) (level 0) is not less than the low key value in the parent (0:1), slot 0 of the next page (1:548364).
Server: Msg 8934, Level 16, State 1, Line 1
Table error: Object ID 1654296953, index ID 50. The high key value on page (1:1754006) (level 0) is not less than the low key value in the parent (0:1), slot 0 of the next page (1:548364).

The corruption is on one of the non-clustered indexes(Index Id=50) on an object with object ID=1654296953 and pages: 1548364,1754006,1548364. I hope I have interpreted errors in the right way.

If you had only one page number in the errors returned you would have done Page level restore, not available in SQL 2000 though. So, just proceed as what Gail advised. Better to drop that index and recreate it.

elay Old Hand Points: 378 More actions · Answer 2

Then drop that index (it's on the StockMovements table) and recreate it. (Do not just rebuild it, that may not help). Once you've done that, run checkDB again.

We already drop and re-create the corrupted index, then when we run checkdb again. I attached the result.

Again, for your assistance if result shows that DB is already ok and index is fixed. 🙂

Thanks so much!

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

elay (2/20/2009)
We already drop and re-create the corrupted index, then when we run checkdb again. I attached the result.

Looks fine.

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

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

elay (2/20/2009)

Microsoft SQL Server 2000 - 8.00.760

I would suggest you consider applying Service pack 4. There were a number of fixes in that service pack.

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

elay Old Hand Points: 378 More actions · Answer 5

2000 RTM??? Why has this never been patched?
You're vulnerable to the Slammer worm as well as a number of other serious issues, including some bugs that cause corruption. I would strongly recommend that you upgrade this to SP4 immediately, if not sooner.

we'll upgrade it now. Thanks!

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

elay (2/20/2009)
2000 RTM??? Why has this never been patched?
You're vulnerable to the Slammer worm as well as a number of other serious issues, including some bugs that cause corruption. I would strongly recommend that you upgrade this to SP4 immediately, if not sooner.
we'll upgrade it now. Thanks!

I was wrong, it's not RTM. 760 is SP3. Not as bad as RTM, but you should still consider upgrading.

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

Paul Randal One Orange Chip Points: 29544 More actions · Answer 7

There was a bug in 2000 SP3 that could cause the corruption errors you posted - it's fixed in SP4.

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

elay Old Hand Points: 378 More actions · Answer 8

Sirs,

I think my DB is already stable (so far).

1. After dropping and re-creating corrupted index

2. We turnoff automatic shrink since last week

Thanks so much. You assistance is really appreciated, especially to Sir Gail.

Thanks.