16
Table Corrupt: Object id %ld (object name = %S_OBJID) does not match between %.*s and %.*s
This error occurs when dbcc checkcatalog finds that an object exists in one system table but not in another system table where Adaptive Server expected to find it.
WARNING! This is a serious error that indicates corruption.
Error 2513 occurs with the following states:
State |
Meaning |
|---|---|
1 |
The object was found in syscolumns but not in either sysobjects or systypes. |
2 |
The object (a view) was found in sysobjects but not in syscolumns. |
3 |
The object (a view) was found in sysobjects but not in syscomments. |
4 |
The object (a view) was found in sysobjects but not in sysprocedures. |
5 |
The object (a stored procedure) was found in sysobjects but not in syscomments. |
6 |
The object (a stored procedure) was found in sysobjects but not in sysprocedures. |
7 |
The object (a rule or default) was found in sysobjects but not in syscomments. |
8 |
The object (a rule or default) was found in sysobjects but not in sysprocedures. |
9 |
The object (a table) was found in sysobjects but not in syscolumns. |
10 |
The object (a table) was found in sysobjects but not in sysindexes. |
11 |
The object (a table) was found in sysindexes but not in sysobjects. |
Call Sybase Technical Support to help you delete the object that is causing the error. However, because other objects may reference that object, deleting it cleanly may be difficult. If this is the case, recovering from backups may be a better choice.
All versions
