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 |
|---|---|---|---|---|---|
| 01C55 | Warning | 20915 | 1000255L | "Join Record Rejected: '%1', duplicate rows in 1st table. \nRow# %2 & %3, row %4 rejected." | This is an informational message describing duplicate rows encountered. Click here for a list of possible parameters and odbc states. |
| 01C56 | Warning | 20916 | 1000256L | "Join virtual table '%1'. \nTotal rows rejected: %2" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| 01C59 | Warning | 20919 | 1000259L | "\nDelete of %1 rows completed for table: %2, %3 seconds." | This is an informational message displayed at the end of a delete. Click here for a list of possible parameters and odbc states. |
| 01S02 | Warning | 2500 | 121L | "Cursor option values changed" | The database server could not support the requested cursor option values for the associated query. Similar option settings were substituted. Click here for a list of possible parameters and odbc states. |
| 01U48 | Warning | 20971 | 1012048L | "(%1) Archive media mounted on '%2'." | No additional information available. Click here for a list of possible parameters and odbc states. |
| 01U49 | Warning | 20972 | 1012049L | "(%1) Done with archive media on '%2'." | No additional information available. Click here for a list of possible parameters and odbc states. |
| 01W01 | Warning | 2532 | 124L | "Invalid data conversion: NULL was inserted for column '%1' on row %2" | The database could not convert a value to the required type. The value being converted was supplied to the database in a data file and inserted using LOAD TABLE. A NULL value has been inserted into the column. Click here for a list of possible parameters and odbc states. |
| 01W02 | Warning | 2003 | 102L | "Using temporary table" | A temporary table has been created in order to satisfy the query. This warning can only occur on an OPEN statement. Click here for a list of possible parameters and odbc states. |
| 01W03 | Warning | 2004 | 103L | "Invalid data conversion" | The database could not convert a value to the required type. The value being converted was either supplied to the database on an insert, update, or as a host bind variable, or was a value retrieved from the database into a host variable or SQLDA. Click here for a list of possible parameters and odbc states. |
| 01W04 | Warning | 2005 | 104L | "Row has been updated since last time read" | You fetched a row from a SCROLL cursor. The row was previously fetched from the same cursor, and one or more columns in the row has been updated since the previous fetch. The column(s) updated may or may not be fetched by the cursor; this warning just indicates that the row from the table has been updated. If the cursor involves more than one table, a row from one or more of the tables has been updated. Click here for a list of possible parameters and odbc states. |
| 01W05 | Warning | 2006 | 105L | "Procedure has completed" | There are no more result sets available for this procedure. An OPEN or a RESUME statement may have caused the procedure to execute to completion. Click here for a list of possible parameters and odbc states. |
| 01W06 | Warning | 2007 | 106L | "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. |
| 01W07 | Warning | 2238 | 107L | "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. |
| 01W08 | Warning | 2008 | 111L | "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. |
| 01W09 | Warning | 2252 | 112L | "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. |
| 01W10 | Warning | 2249 | 110L | "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. |
| 01W11 | Warning | 2255 | 113L | "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. |
| 01W12 | Warning | 2350 | 114L | "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. |
| 01W13 | Warning | 2360 | 115L | "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. |
| 01W14 | Warning | 2375 | 116L | "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. |