Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

error 602

4 views
Skip to first unread message

jfrog

unread,
Oct 22, 1998, 3:00:00 AM10/22/98
to
602 21 Could not find row in Sysindexes for dbid '%d', object
'%ld',index '%d'. Run DBCC CHECKTABLE on Sysindexes.

I receive the above error when running our applications. when i check the
log file..the above error is there
i understand that this is a problem with sql server 6.5...anyone know how
to fix it?


Neil Pike

unread,
Oct 23, 1998, 3:00:00 AM10/23/98
to

Try the below one for a match - but there are several others. If your
problem isn't one that is fixed in the latest service pack then you will
need to contact MS PSS for a hot-fix/workaround.

PSS ID Number: Q165130
Article last modified on 04-22-1997

6.0 6.5

WINDOWS

======================================================================
--------------------------------------------------------------------------
The information in this article applies to:

- Microsoft SQL Server, versions 6.0 and 6.5
--------------------------------------------------------------------------
BUG#: 16646 (6.5)

SYMPTOMS
========

If you fetch from a cursor defined on a view owned by a user other than
the owner of the underlying base table, and there are identical object
names for the view and the table, you will receive the following error
message, and the client connection will be terminated:

Error 602, Severity: 21, State 3
Could not find row in Sysindexes for dbid '4', object
'1232007420',index '-1'.


Run DBCC CHECKTABLE on Sysindexes.

For example, a view called "authors" created by user "Bill" in the pubs
database defined on the underlying "dbo" owned "authors" table will give
error 602 when Bill attempts to fetch from a cursor on this view.

CAUSE
=====

The object ID in the error 602 message corresponds to the view object. SQL
Server looks for the table object owned by its owner, when it should in
fact be looking for the view.

WORKAROUND
==========

Use qualifiers to reference the View name when declaring the cursor, as
in the following example:

[[database.]owner.]view_name

STATUS
======

Microsoft has confirmed this to be a problem in Microsoft SQL Server
versions 6.0 and 6.5. We are researching this problem and will post new
information here in the Microsoft Knowledge Base as it becomes available.

Neil Pike MVP/MCSE
Protech Computing Ltd
(Please post ALL replies to the newsgroup only unless indicated otherwise)


0 new messages