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 |
|---|---|---|---|---|---|
| -1278L | Error | 2965 | WW230 | "Operation is not allowed" | The requested operation is not allowed while schema is being modified. Click here for a list of possible parameters and odbc states. |
| -1279L | Error | 2966 | WW231 | "Operation '%1' failed for reason: '%2'" | The requested operation failed. Click here for a list of possible parameters and odbc states. |
| -1280L | Error | 2967 | WW232 | "Underflow when converting '%1'" | An underflow occurred when converting the specified type. The source type may be too small (for example zero length binary) or value may be too small to be represented by the destination type. Click here for a list of possible parameters and odbc states. |
| -1281L | Error | 2968 | 42W80 | "Another connection has the row in '%1' locked" | You attempted modify or delete a row that is locked by another connection. The row will be unlocked once that connection commits or rolls back. Click here for a list of possible parameters and odbc states. |
| -1283L | Error | 2970 | WT020 | "A CONTAINS query is not allowed on the view or derived table '%1'." | A view or derived table can only be queried using CONTAINS if it does not use TOP, FIRST, DISTINCT, GROUP BY, or FOR XML. In addition, the list of columns to search must all come from a single base table in the FROM clause of the view. They cannot come from multiple tables, or from another view or derived table in the FROM clause. Click here for a list of possible parameters and odbc states. |
| -1284L | Error | 2971 | WW233 | "Invalid partition key specification: must use '%1'. " | Partition key cannot be changed for ALTER TABLE ADD PARTITION. It must specify the same partition key column as the CREATE TABLE did. Click here for a list of possible parameters and odbc states. |
| -1285L | Error | 2973 | 40W09 | "%1 -- Transaction rolled back" | This transaction has been rolled back because the server encountered an error during a critical operation. Click here for a list of possible parameters and odbc states. |
| -1286L | Error | 2974 | 42WCD | "Immediate materialized view definition cannot contain a SUM function over a nullable expression." | You attempted to change the refresh type to immediate for a materialized view whose definition contains a SUM function over a nullable expression. Click here for a list of possible parameters and odbc states. |
| -1287L | Error | 2975 | 55W35 | "Operation not allowed on global temporary table %1 as it is in use. Reconnect and try again." | A global temporary table cannot be modified if it is in use. The user must reconnect and re-execute the statement. Click here for a list of possible parameters and odbc states. |
| -1288L | Error | 2976 | WW120 | "'%1' statement is not allowed on a mirrored database" | You attempted to execute a statement that is not allowed when using a mirrored database. Click here for a list of possible parameters and odbc states. |
| -1289L | Error | 2977 | WL016 | "LOAD TABLE option '%1' not allowed with FORMAT %2" | The specified LOAD TABLE option is not meaningful for the LOAD TABLE FORMAT. Click here for a list of possible parameters and odbc states. |
| -1290L | Error | 2978 | 42WD4 | "FOR UPDATE or FOR READ ONLY clause must be specified on PREPARE (not on DECLARE CURSOR)" | You specified the FOR UPDATE or FOR READ ONLY clause on a DECLARE CURSOR statement. The FOR UPDATE or FOR READ ONLY clause must be specified on the PREPARE statement and not the DECLARE CURSOR statement. Click here for a list of possible parameters and odbc states. |
| -1291L | Error | 2979 | WW235 | "Column '%1' Partition '%2' may not be assigned to a dbspace because partitioning is not supported for datatype '%3'." | The column storage for certain datatypes (such as the BIT datatype) cannot be assigned to a dbspace. Click here for a list of possible parameters and odbc states. |
| -1292L | Error | 2980 | WW236 | "Column '%1' may not be assigned to a dbspace because partitioning is not supported for datatype '%2'." | The column storage for certain datatypes (such as the BIT datatype) cannot be assigned to a dbspace. Click here for a list of possible parameters and odbc states. |
| -1293L | Error | 2981 | WW237 | "Partition key of '%1' is unsupported." | Partitioning over the specified datatype is not supported. Click here for a list of possible parameters and odbc states. |
| -1294L | Error | 2983 | WW122 | "Parameter (%1) length has exceeded its limit (%2)." | Given parameter's length has exceeded the specified limit. Click here for a list of possible parameters and odbc states. |
| -1295L | Error | 2984 | WW123 | "Database path must be absolute." | Specified Database path must be absolute. Click here for a list of possible parameters and odbc states. |
| -1296L | Error | 2985 | WW124 | "(%1) is not unique." | Specified value for a given parameter already exist in the multiplex configuration. Click here for a list of possible parameters and odbc states. |
| -1297L | Error | 2986 | WW125 | "No of servers in multiplex setup has reached to the maximum limit." | No of servers in multiplex setup has reached to the maximum limit. User cannot add any more secondary servers. Click here for a list of possible parameters and odbc states. |
| -1298L | Error | 2987 | WW126 | "Cannot alter multiplex failover node and other multiplex server properties in the same statement." | Users are not allowed to alter the multiplex failover node status and other multiplex server properties in the same statement. Click here for a list of possible parameters and odbc states. |