Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 2043 | Error | 08W05 | -106L | "Cannot open transaction log file -- %1" | The database server was unable to open the named transaction log file. The log file name may include an invalid device or directory. If this is the case, you can use the Transaction Log utility (dblog) to find out where the transaction log should be and perhaps change it. Click here for a list of possible parameters and odbc states. |
| 2044 | Error | 08W17 | -107L | "Error writing to transaction log file" | The database server got an I/O error writing the transaction log file. The disk may be full or the log file name could be invalid. Click here for a list of possible parameters and odbc states. |
| 2045 | Error | 08W02 | -108L | "Connection not found" | The specified connection name on a DISCONNECT or SET CONNECTION statement is invalid. Click here for a list of possible parameters and odbc states. |
| 2046 | Error | 08W06 | -109L | "There are still active database connections" | You attempted to shut down a database that still has active connections. Click here for a list of possible parameters and odbc states. |
| 2047 | Error | 52010 | -110L | "Item '%1' already exists" | You attempted to create a file, table, view, column, constraint, foreign key, or publication with the same name as an existing one. Click here for a list of possible parameters and odbc states. |
| 2048 | Error | 52W04 | -111L | "Index name '%1' not unique" | You attempted to create an index with the same name as an existing index. Click here for a list of possible parameters and odbc states. |
| 2049 | Error | 55013 | -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. |
| 2050 | Error | 53030 | -113L | "Column '%1' in foreign key has a different definition than primary key" | The data type of the column in the foreign key is not the same as the data type of the column in the primary key. Change the definition of one of the columns using ALTER TABLE. Click here for a list of possible parameters and odbc states. |
| 2051 | Error | 53011 | -114L | "Number of columns defined for the view does not match SELECT statement" | You attempted to create a view, but the column list specified as part of the CREATE VIEW statement does not correspond to the list of items in the view's SELECT statement. Click here for a list of possible parameters and odbc states. |
| 2053 | Error | 55W02 | -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. |
| 2055 | Error | 55008 | -118L | "Table '%1' has no primary key" | You attempted an operation that required the referenced table to have a primary key. Examples of these operations include adding a foreign key, or using the ON EXISTING clause of an INSERT statement, while referring to a table that does not have a primary key. You must add a primary key to the referenced table. Click here for a list of possible parameters and odbc states. |
| 2056 | Error | 52009 | -119L | "Primary key column '%1' already defined" | You listed the same column name twice in the definition of a primary key. Click here for a list of possible parameters and odbc states. |
| 2057 | Error | 53W01 | -125L | "ALTER clause conflict" | A primary key clause, foreign key clause, or a uniqueness clause must be the only clause of an ALTER TABLE statement. Click here for a list of possible parameters and odbc states. |
| 2058 | Error | 52W05 | -126L | "Table cannot have two primary keys" | You specified the primary key twice in a CREATE TABLE statement. Click here for a list of possible parameters and odbc states. |
| 2059 | Error | 53W05 | -127L | "Cannot alter a column in an index" | You may have attempted to delete or modify the definition of a column that is part of a primary or foreign key. You may have attempted to delete a column that has an index on it. In this case, DROP the index or key, perform the ALTER statement, and then add the index or key again. Click here for a list of possible parameters and odbc states. |
| 2060 | Error | 55W03 | -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. |
| 2061 | Error | 54003 | -250L | "Identifier '%1' too long" | An identifier was specified is longer than 128 bytes. Click here for a list of possible parameters and odbc states. |
| 2062 | Error | 52W06 | -251L | "Foreign key '%1' for table '%2' duplicates an existing foreign key" | You attempted to define a foreign key that already exists. Click here for a list of possible parameters and odbc states. |
| 2063 | Error | 52W03 | -183L | "Cannot find index named '%1'" | You attempted to perform an operation using an index that does not exist. Check for spelling errors. Check whether the index name must be qualified with a user ID. Click here for a list of possible parameters and odbc states. |
| 2064 | Error | 52W16 | -610L | "User message %1 already exists" | The message with this error number already exists in the database. Click here for a list of possible parameters and odbc states. |