May 9, 2009 at 5:21 pm
Hi,
I am getting the following error on my SQL Server.
Error: 602, Severity: 21, State: 30. Could not find an entry for table or index with partition ID in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
Could you please provide a solution to overcome this error.
I had run DBCC CHECKDB on tempdb database but found no errors.
The SQL Server has the latest service pack.
Regards,
Spellbound
May 10, 2009 at 5:01 pm
Did you drop and re-create the offending stored procedure?
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.May 11, 2009 at 3:35 pm
spellbound (5/9/2009)
Hi,I am getting the following error on my SQL Server.
Error: 602, Severity: 21, State: 30. Could not find an entry for table or index with partition ID in database 2. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.
Could you please provide a solution to overcome this error.
I had run DBCC CHECKDB on tempdb database but found no errors.
The SQL Server has the latest service pack.
Regards,
Spellbound
As the message suggests if you did not find your tempdb corrupted, then is your code trying to refer to a temporary table the tempdb? Have you restarted the server? OR have u dropped any object that is refrrenced by your code?
May 11, 2009 at 4:35 pm
Could you plz let me know how to get the offending stored procedure.
May 11, 2009 at 4:38 pm
No the server has not been restarted.No idea about the dropped object.
I am getting this error everyday more than four times a day.
July 13, 2009 at 7:51 am
Not sure if this issue got resolved for you but I wanted to pass on this fix that Microsoft issued for this particular error :
Cumulative Update 4 for SQL Server 2005 Service Pack 2 (build 3200)
http://support.microsoft.com/kb/937343
Apparently this error then causes the sql server to shutdown inadvertantly, and if you are running in a cluster then it may failover or may have to manually failover and re-start SQL.
August 17, 2009 at 12:16 pm
I just had this problem on one of my test servers. Simply restarted it and it went away, which you would expect with the problem being in tempdb, unless there was corruption in model database (and/or systemresource database on 2005 and 2008?).
March 2, 2010 at 7:55 am
December 2, 2010 at 7:08 am
Hello
We have installed SP2 (9.00.3042.00SP2Standard Edition)
but get this error yesterday.
Is there another known problem?
December 2, 2010 at 9:43 am
Did you apply the cumulative update for SP2, we had the same issue when we did a migration a couple of months ago and just applied the cumulative update to fix.
Please take a look at this link, it is a list of all SP's and updates with links for download.
http://sqlserverbuilds.blogspot.com/
Good Luck
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
December 3, 2010 at 2:28 am
Hello
Thanks for your reply.
Why did you not install SP3 and the cumulative updates packages 12 for SP3?
Is there any reason for not installing SP3 and or the cumulative update package 12?
Thanks and regards
Remo
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply