August 6, 2003 at 8:33 am
Maybe it's the heatwave but something's not right! Trying to access the master database through EM results in:
Invalid object name dbo.sysobjects
Not a good start.
Logging in through Query Analyzer lets me access the master database and I can query various tables e.g.
select * from sysdatabases
select * from syscolumns etc.
However trying to select from sysobjects gives me an invalid object name again.
Then I ran
dbcc checkdb('master')
Sample output was:
DBCC results for 'master'.
DBCC results for 'sysobjects'.
There are 965 rows in 19 pages for object 'sysobjects'.
So it can see it. Then ran
dbcc checktable ('sysobjects')
Again the invalid object name. There's nothing in the error logs to indicate anything strange and the 3 or 4 user databases on the server appear to be working as before.
I'm tempted to think corruption of the sysobjects table but thought the dbcc commands would have picked this up? Not too keen to start restoring the master when everything else is working.
Anyone any ideas?
cheers
August 6, 2003 at 10:05 am
select * from information_Schema.tables? Does this work?
Steve Jones
August 7, 2003 at 2:15 am
Server: Msg 208, Level 16, State 1, Procedure TABLES, Line 4
Invalid object name 'sysobjects'.
Server: Msg 4413, Level 16, State 1, Line 1
Could not use view 'information_Schema.tables' because of previous binding errors.
By the way the box is running SQL7 sp3
cheers
August 7, 2003 at 6:06 am
Is it possible that the install is case-sensitive and in query analyzer you are using an upper case character when referring to 'sysobjects'?
August 7, 2003 at 7:37 am
It's a non case sensitive install but thanks anyway.
It also crossed my mind that maybe the owner had been changed from dbo (how or why I don't know) but I can't check this because the owner is stored in........the sysobjects table!
August 7, 2003 at 9:44 am
I had the same problem a few months back. I could not find anything anywhere that I could use to fix the issue.
I did not want to 'hack' the sysobjects table because of the potention issues, so in a last ditch attempt, I bounced the server. When it came back up, the issue had resolved itself.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply