October 10, 2005 at 1:39 pm
Hello everyone, I ran a dbcc checkdb and below is the part where the problem is. However, when i run a object_name (750065858) I get NULL as result. Why? Also, is the problem table X or Y or another table altogether? Thanks in advance for your help.
BTW, when I ran dbcc checktable against tables x and y, they both checked out fine. Thanks again.
DBCC results for 'x'.
There are 405 rows in 2 pages for object 'x'.
Server: Msg 2576, Level 16, State 1, Line 1
IAM page (0:0) is pointed to by the previous pointer of IAM page (3:6717) object ID 750065858 index ID 2 but was not detected in the scan.
DBCC results for 'y'.
There are 232 rows in 2 pages for object 'y'.
October 10, 2005 at 2:17 pm
if you run
select object_name (750065858)
and you get null, then there is no object with an id of 750065858
to find the object id of a table use
OBJECT_ID('Tablename')
October 10, 2005 at 2:25 pm
Thanks Ray, I understand that, but the error clearly says that the object id is 750065858, but when I run the select object_name(750065858), I get null.
I ran into this problem on another server a while ago as well. Luckily I found the offending table and index quickly. Why is SQL Server giving me the wrong object id?
October 10, 2005 at 3:05 pm
tough to say.
Are you in the correct database when you manually execute statement
select object_Name(750065858)
Are you the dbo in the database, or SA on the server, it could be possible the object is owned by someone else.
Otherwise I don't know how to find the object name.
Try querying sysobjects
Select *
from sysobjects so
where id = 750065858
October 10, 2005 at 3:39 pm
Thanks for your help Ray. I am running the object_name in the right database. And I did run a query against sysobjects and nada. I am a SA and should be able to see all objects. Thanks again.
October 11, 2005 at 9:34 am
I thought this was interesting because the same thing happened to me. The error was a bit different:
Attempt to fetch logical page (1:4358712) in database 'dbname' belongs to object '2025110305', not to object 'tblname'. [SQLSTATE HY000] (Error 605).
The object ID '2025110305' does not exist. Then I noticed the previous error:
Attempt to fetch logical page (1:2152353) in database 'dbname' belongs to object '0', not to object 'tblname'. [SQLSTATE HY000] (Error 605).
BOL says "If the error reports the first object ID as 0, an unallocated page was probably encountered. (There is no object ID equal to 0.)"
So I ran a checktable then reindexed 'tblname' and got no errors (the errors occurred on a reindex job). I ran a checkdb on a copy of the database and got no errors. Curious. Am waiting for the job to run again in a couple of days to see what happens.
I wonder if the non-existent object ID error occurred as a result of not running a checktable sooner... after all the original object was '0'. Hmmm, curious.
Linda
October 11, 2005 at 12:45 pm
Could be that you were seeing phantom errors caused by naughty behavior from caching disk controllers.
I once had a SAN, an MSA1000, to be exact. In order to make the 605 error problem go away, I had to upgrade the firmware to a newer version.
Efforts to run checkdb and/or checktable returned NO errors, but I would often get these darned 605 errors. Also, running dbcc dropcleanbuffers would get me through a day's work.
It was always a problem with an index, never the table data. And always the data/index was never corrupted, after dropping the buffers.
WEERD.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply