Messages 55013 through 55W21

Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.

SQL State Msg Type Number SQL Code Message Possible Cause
55013 Error 2049 -112L "Table already has a primary key" You attempted to add a primary key on a table that already has a primary key defined. You must delete the current primary key before adding a new one.

Click here for a list of possible parameters and odbc states.

55W02 Error 2053 -116L "Table must be empty" You attempted to modify a table, and the database server can only perform the change if there are no rows in the table.

Click here for a list of possible parameters and odbc states.

55W03 Error 2060 -128L "Cannot drop a user that owns tables in runtime system" You attempted to drop a user that owns tables while running the runtime server. This operation would result in dropping tables. The runtime server cannot drop tables. Use the full server.

Click here for a list of possible parameters and odbc states.

55W04 Error 2149 -270L "Cannot drop a user that owns procedures in runtime server" You attempted to drop a user that owns procedures while using the runtime server. This operation would result in dropping procedures. The runtime server cannot drop procedures. Use the full server.

Click here for a list of possible parameters and odbc states.

55W05 Error 2099 -614L "Cannot drop a user that owns messages or data types" You attempted to drop a user that is the creator of a message or user-defined data type. The message or user-defined data type must be dropped first.

Click here for a list of possible parameters and odbc states.

55W06 Error 2377 -731L "Cannot drop a user that owns objects involved in replication" You attempted to drop a user that is the creator of a database object involved in replication. For example, the user may own a table that is part of a publication.

Click here for a list of possible parameters and odbc states.

55W07 Error 2386 -739L "db_init has not been called or the call to db_init failed" The SQLCA passed to a dblib entry point has not been initialized by a call to db_init or the call to db_init failed.

Click here for a list of possible parameters and odbc states.

55W08 Error 2404 -757L "Modifications not permitted for read-only database" You attempted an update operation on a database that was declared as read-only.

Click here for a list of possible parameters and odbc states.

55W09 Error 2447 -800 "Cannot commit or rollback while enlisted in a transaction" You tried to explicitly commit or rollback on a connection that is enlisted in a transaction. You must use the Commit/Abort protocol of the transaction instead.

Click here for a list of possible parameters and odbc states.

55W10 Error 2448 -801L "Cannot enlist in a transaction while already enlisted in a transaction" You tried to enlist a second transaction on a connection that is already enlisted in a transaction.

Click here for a list of possible parameters and odbc states.

55W11 Error 2449 -802L "Cannot enlist in a transaction with uncommitted data pending" You tried to enlist a transaction on a connection that has pending uncommitted data.

Click here for a list of possible parameters and odbc states.

55W12 Error 2843 -1167L "Cannot drop a user that owns text configurations" You attempted to drop a user that is the creator of a text configuration. The text configuration must be dropped first.

Click here for a list of possible parameters and odbc states.

55W14 Error 2574 -908L "Invalid operation on a closed object" An illegal attempt was made to access a closed UltraLite object.

Click here for a list of possible parameters and odbc states.

55W15 Error 2582 -924L "Service '%1' in use" You have attempted to drop a service that is currently in use.

Click here for a list of possible parameters and odbc states.

55W16 Error 2706 -1037L "Cannot drop or modify object '%1' because at least one other object ( %2 '%3') depends upon it" You attempted to drop or modify an object, such as a table or a column, that is used by another object, such as a materialized view, that cannot be automatically invalidated. The dependent object must be disabled or dropped before a drop or modification can be permitted.

Click here for a list of possible parameters and odbc states.

55W17 Error 2707 -1038L "Cannot use view '%1' because it has been disabled" You attempted to reference a view that has been disabled. The view must be enabled before it can be used again.

Click here for a list of possible parameters and odbc states.

55W18 Error 2709 -1040L "Cannot use view '%1' because it is invalid" You attempted to reference an invalid view. The view must be enabled before it can be used again.

Click here for a list of possible parameters and odbc states.

55W19 Error 2715 -1046L "Illegal column definition: %1" You are attempting to define a column in a way that is not allowed.

Click here for a list of possible parameters and odbc states.

55W20 Error 2716 -1047L "This database does not support encrypted tables" You tried to create an encrypted table in a database that does not support them.

Click here for a list of possible parameters and odbc states.

55W21 Error 2861 -1184L "Cannot drop last unique index of an immediate materialized view" You attempted to drop the last unique index on non-nullable columns of an immediate materialized view. Immediate materialized view needs at least one unique index on non-nullable columns to be valid.

Click here for a list of possible parameters and odbc states.


Created November 10, 2011. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com