11
Cannot drop the %S_MSG with object-id %ld in database %d, because it doesn't exist in the system catalogs.
This error occurs when Adaptive Server fails to drop a database, user table, procedure, rule, default, trigger, or view because the object being dropped does not exist in the appropriate system table.
Error 3703 can occur during a drop command such as drop database, drop table, drop procedure, or drop rule.
Error 3703 occurs with these states.
State |
Meaning |
|---|---|
2 |
During a drop index command, if Adaptive Server fails to find the object ID of the table for which the index is being dropped in sysobjects, error 3703 occurs with state 2. |
4 |
When Adaptive Server fails to find the referenced table in sysobjects for a trigger that is being dropped, error 3703 occurs with state 4. |
5 |
During any drop command, if Adaptive Server fails to find a sysobjects entry for any triggers belonging to the object being dropped, error 3703 occurs with state 5. |
6 |
During any drop command, if Adaptive Server fails to find a sysobjects entry for the object being dropped, error 3703 occurs with state 6. |
7 |
When Adaptive Server fails to find the referenced table in sysobjects for a trigger that is being dropped, error 3703 occurs with state 7. |
8 |
When Adaptive Server fails to drop a database, user table, procedure, rule, default, trigger, or view that is not some other object’s subsidiary part (for example, dropping a trigger because its associated table is being dropped), and the object ID is not found in sysobjects, error 3703 occurs with state 8. |
9 |
If the object being dropped cannot be located in sysobjects, error 3703 occurs with state 9. |
10 |
If the object being dropped has referential dependencies, Adaptive Server tries to delete the necessary rows from sysconstraints. If the ID of the reference is not found in sysconstraints, error 3703 occurs with state 10. |
11 |
If the database being dropped has referential dependencies, Adaptive Server tries to drop the references from the other databases. If the ID of the reference from the other database is not found in sysreferences, error 3703 occurs with state 11. |
Recovering from error 3703 requires manually modifying one or more system tables. Call Sybase Technical Support for assistance in determining which tables to modify and how to do that.
Before calling Sybase Technical Support, have the information available that is listed in “Reporting errors”.
All versions
