22
Could not find row in sysdatabases with database id %d. Run DBCC CHECKTABLE on sysdatabases.
This error occurs when Adaptive Server cannot find an entry in sysdatabases when looking for a specific database ID.
Possible causes of error 913 are:
Accessing a stored procedure or view that refers to a table in a database that has been dropped.
Accessing a stored procedure or view that refers to a table in a database that has been dropped and re-created.
A nonclustered index on the sysdatabases table in the master database has been corrupted.
Running the system stored procedure sp_help_rep_agent without parameters, which is due to a problem in Adaptive Server Enterprise versions 12.0.x and version 12.5.0.2 or earlier.
This is a serious error if the index is corrupt or recovery fails.
If the 913 error is caused by accessing a stored procedure or view that refers to a table in a database that has been dropped, either re-create the database or update the procedure or view to point to the appropriate database.
When a database has been dropped and re-created, it can end up with a different database ID. If a stored procedure still references the old database ID, drop and re-create the stored procedure so that it will reference the new database ID. Refer to drop procedure and create procedure in the Reference Manual: Commands for information about dropping and re-creating stored procedures.
If the cause of the error is a corrupted nonclustered index on a system table, use one of these options:
Use the sp_fixindex stored procedure to repair the index.
Restore master from backup. See the chapter “Adaptive Server System Recovery” in most recent version of the Troubleshooting and Disaster Recovery guide for information about restoring the master database.
If the error was raised when you ran the system stored procedure sp_help_rep_agent without parameters, contact Sybase Technical Support for instructions on how to resolve this error.
All versions
