Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL Code | Msg Type | Number | SQL State | Message | Possible Cause |
|---|---|---|---|---|---|
| 106L | Warning | 2007 | 01W06 | "Value for column '%1' in table '%2' has changed" | A replicated UPDATE has found a value in an updated column that does not match the value when the original UPDATE was made. Click here for a list of possible parameters and odbc states. |
| -106L | Error | 2043 | 08W05 | "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. |
| -107L | Error | 2044 | 08W17 | "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. |
| 107L | Warning | 2238 | 01W07 | "Language extension detected in syntax near '%1' on line %2" | The statement you are executing contains syntax that is not allowed with the current setting of the option SQL_FLAGGER_WARNING_LEVEL. Modify the offending statement or set the SQL_FLAGGER_WARNING_LEVEL option to a different value. Click here for a list of possible parameters and odbc states. |
| -108L | Error | 2045 | 08W02 | "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. |
| -109L | Error | 2046 | 08W06 | "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. |
| 109L | Warning | 2241 | 01003 | "Null value eliminated in aggregate function" | The expression argument of the aggregate function evaluated to NULL for one or more rows. Click here for a list of possible parameters and odbc states. |
| -110L | Error | 2047 | 52010 | "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. |
| 110L | Warning | 2249 | 01W10 | "Transaction log backup page only partially full" | A DB_LOG_BACKUP_READ_WAIT was issued against the transaction log and the page returned was not full. The application should reissue the request for the same page. Click here for a list of possible parameters and odbc states. |
| 111L | Warning | 2008 | 01W08 | "Statement cannot be executed" | You specified a SQL statement for the PREPARE ... WITH EXECUTE statement that cannot be executed. If you specified an output SQLDA, it may contain a DESCRIBE of the prepared statement. Click here for a list of possible parameters and odbc states. |
| -111L | Error | 2048 | 52W04 | "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. |
| -112L | Error | 2049 | 55013 | "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. |
| 112L | Warning | 2252 | 01W09 | "More information required" | More information is required to complete the request. This is used internally in the database interface library to process a unified login. It should not be returned to an application. Click here for a list of possible parameters and odbc states. |
| -113L | Error | 2050 | 53030 | "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. |
| 113L | Warning | 2255 | 01W11 | "Database option '%1' for user '%2' has an invalid setting" | Upon processing a connection request for a specific user, the server processed a database option that has an invalid setting. The server will use the default option value. Click here for a list of possible parameters and odbc states. |
| -114L | Error | 2051 | 53011 | "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. |
| 114L | Warning | 2350 | 01W12 | "Character set conversion to '%1' cannot be performed; '%2' is used instead" | The server is unable to perform a character conversion from the character set the database is using to the character set the application requested. Click here for a list of possible parameters and odbc states. |
| 115L | Warning | 2360 | 01W13 | "Database server cannot convert data from/to character set '%1', conversion may not be correct" | The database server cannot convert character data from/to the character set requested by the application because the character set is not supported. The connection succeeds, but character conversion may not be correct for all characters. Click here for a list of possible parameters and odbc states. |
| -116L | Error | 2053 | 55W02 | "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. |
| 116L | Warning | 2375 | 01W14 | "Language '%1' is not supported, '%2' will be used" | The language that the application requested is not supported by the server to which the application is connecting. Instead, the server will send message strings in the language stated. Click here for a list of possible parameters and odbc states. |