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 |
|---|---|---|---|---|---|
| 23510 | Error | 2937 | -1254L | "MERGE statement for table '%1' failed because of a RAISERROR specification in the statement" | You have attempted to execute a MERGE statement that contains the RAISERROR clause in one or more merge operation branches and one of the input rows satisfies the conditions for one of these branches Click here for a list of possible parameters and odbc states. |
| 23W01 | Error | 2124 | -193L | "Primary key for table '%1' is not unique : Primary key value ('%2')" | You attempted to add a new row to a table, but the new row has the same primary key as an existing row. The database has not added the incorrect row to the database. For example, you might have added a student with student number 86004 and there is already a row for a student with that number. Click here for a list of possible parameters and odbc states. |
| 23W05 | Error | 2129 | -198L | "Primary key for row in table '%1' is referenced by foreign key '%2' in table '%3'" | You attempted to delete or modify a row whose primary key value is referenced elsewhere in the database. Click here for a list of possible parameters and odbc states. |
| 24000 | Error | 2501 | -853L | "Cursor not in a valid state" | You attempted to use a cursor that is not in a valid state for the attempted operation. For example, the cursor may have encountered an error. Click here for a list of possible parameters and odbc states. |
| 24001 | Error | 2924 | -1241L | "Value-sensitive cursor used after a TRUNCATE" | You attempted to use a value-sensitive cursor opened WITH HOLD after a TRUNCATE or after a COMMIT removed all rows from a temporary table declared as ON COMMIT DELETE ROWS. Click here for a list of possible parameters and odbc states. |
| 24501 | Error | 2112 | -180L | "Cursor not open" | You attempted to use a cursor that has not been opened. Click here for a list of possible parameters and odbc states. |
| 24502 | Error | 2111 | -172L | "Cursor already open" | You attempted to OPEN a cursor that is already open. Click here for a list of possible parameters and odbc states. |
| 24503 | Error | 2128 | -197L | "No current row of cursor" | You attempted to perform an operation on the current row of a cursor, but the cursor is not positioned on a row. The cursor is before the first row of the cursor, after the last row, or is on a row that has since been deleted. Click here for a list of possible parameters and odbc states. |
| 24504 | Error | 2467 | -820L | "Invalid scroll position '%1'" | You attempted to scroll to a position that is not supported. Scroll positions must be between -2147483647 and 2147483646. Click here for a list of possible parameters and odbc states. |
| 24W01 | Error | 2109 | -170L | "Cursor has not been declared" | You attempted to OPEN a cursor that has not been declared. Click here for a list of possible parameters and odbc states. |
| 26501 | Error | 2073 | -132L | "SQL statement error" | The statement identifier (generated by PREPARE) passed to the database for a further operation is invalid. Click here for a list of possible parameters and odbc states. |
| 28000 | Error | 2039 | -103L | "Invalid user ID or password" | You supplied an invalid user ID or an incorrect password. Click here for a list of possible parameters and odbc states. |
| 28W01 | Error | 2041 | -104L | "Invalid user ID or password on preprocessed module" | You specified an invalid user ID or password when a module was preprocessed. Click here for a list of possible parameters and odbc states. |
| 28W02 | Error | 2257 | -205L | "Integrated logins are not permitted" | The login_mode database option is set to Standard, and you attempted an integrated login. Change the option setting or supply an explicit user ID. Click here for a list of possible parameters and odbc states. |
| 28W03 | Error | 2258 | -206L | "Integrated logins are required, standard logins are not permitted" | The login_mode database option is set to Integrated, and you attempted a standard login. Change the option setting or use an integrated login. Click here for a list of possible parameters and odbc states. |
| 28W04 | Error | 2259 | -245L | "Integrated login failed" | The integrated login failed. You may not have a system account on the server machine. Click here for a list of possible parameters and odbc states. |
| 28W05 | Error | 2262 | -246L | "Integrated logins are not supported for this database" | The current database is an older database and does not have the information to map integrated login IDs to database user IDs. You must upgrade your database to use integrated logins. Click here for a list of possible parameters and odbc states. |
| 28W06 | Error | 2263 | -247L | "The integrated login ID guest can only be mapped to the guest database user ID" | You attempted to map the guest login ID to something other than guest. Click here for a list of possible parameters and odbc states. |
| 28W07 | Error | 2264 | -248L | "Cannot map a login ID to the sys or public user ID" | You attempted to map a login ID to either SYS or PUBLIC. Click here for a list of possible parameters and odbc states. |
| 28W08 | Error | 2265 | -249L | "The login ID '%1' is already mapped to user ID '%2'" | You attempted to map a login ID twice. Click here for a list of possible parameters and odbc states. |