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 |
|---|---|---|---|---|---|
| 42U08 | Error | 2899 | -1221L | "Duplicate options not allowed in the CREATE DATABASE statement" | You have specified one of the options more than once when executing the CREATE DATABASE statement. Click here for a list of possible parameters and odbc states. |
| 42W01 | Error | 2065 | -120L | "User '%1' already has GRANT permission" | You attempted to give GRANT OPTION permission to a user that already has it. Click here for a list of possible parameters and odbc states. |
| 42W02 | Error | 2067 | -122L | "Operation would cause a group cycle" | You attempted to add a member to group that would result in a member belonging to itself. The membership may be direct or indirect. Click here for a list of possible parameters and odbc states. |
| 42W03 | Error | 2068 | -123L | "User '%1' is not a user group" | You attempted to add a member to group, but the user ID specified as a group has not been granted GROUP permission. Click here for a list of possible parameters and odbc states. |
| 42W04 | Error | 2071 | -131L | "Syntax error near '%1' %2" | The database server cannot understand the statement you are trying to execute. If you used a keyword (such as DATE) for a column name, try enclosing the keyword in quotation marks ("DATE"). Click here for a list of possible parameters and odbc states. |
| 42W05 | Error | 2091 | -148L | "Unknown function '%1'" | You misspelled the name of a database function (such as MAXIMUM instead of MAX) in a query definition or in a query column name. Click here for a list of possible parameters and odbc states. |
| 42W06 | Error | 2093 | -150L | "Invalid use of an aggregate function" | You attempted to use an aggregate function inappropriately. For example, a SELECT statement cannot contain an aggregate function within a predicate in the WHERE clause unless the aggregate function constitutes an outer reference. Other invalid uses include specifying an aggregate function in the SET clause of an UPDATE statement, or using an aggregate function in a CHECK constraint. Click here for a list of possible parameters and odbc states. |
| 42W07 | Error | 2102 | -155L | "Invalid host variable" | You supplied an invalid host variable to the database using the C language interface. You may have supplied the variable as a host variable or through a SQLDA. Click here for a list of possible parameters and odbc states. |
| 42W08 | Error | 2103 | -156L | "Invalid expression near '%1'" | You supplied an expression that the database server cannot understand. For example, you may have tried to add two dates. Click here for a list of possible parameters and odbc states. |
| 42W09 | Error | 2534 | -877L | "SETUSER not allowed in procedures, triggers, events, or batches" | The SETUSER statement is not allowed in stored procedures, triggers, event handlers, or batches, and cannot be called from an EXECUTE IMMEDIATE statement. Click here for a list of possible parameters and odbc states. |
| 42W13 | Error | 2106 | -159L | "Invalid column number" | You gave an invalid column number, or the column you are looking for is in a different table. Click here for a list of possible parameters and odbc states. |
| 42W14 | Error | 2139 | -260L | "Variable '%1' not found" | You attempted to DROP or SET the value of a SQL variable that was not created or was previously dropped. Click here for a list of possible parameters and odbc states. |
| 42W15 | Error | 2140 | -261L | "There is already a variable named '%1'" | You attempted to create a variable with the name of another variable that already exists. Click here for a list of possible parameters and odbc states. |
| 42W16 | Error | 2167 | -200L | "Invalid option '%1' -- no PUBLIC setting exists" | You may have misspelled the name of an option in the SET OPTION statement. You can only define an option for a user if the database administrator has supplied a PUBLIC value for that option. Click here for a list of possible parameters and odbc states. |
| 42W17 | Error | 2168 | -201L | "Invalid setting for option '%1'" | You supplied an invalid value for an option in the SET statement. Some options allow only numeric values, while other options allow only the values On and Off. Click here for a list of possible parameters and odbc states. |
| 42W18 | Error | 2169 | -210L | "User '%1' has the row in '%2' locked" | You attempted to read or write a row that is locked by another user, while the database option 'blocking' is set to Off. Click here for a list of possible parameters and odbc states. |
| 42W19 | Error | 2170 | -211L | "Not allowed while '%1' is using the database" | You attempted a data definition language operation that cannot be completed while another user is connected. Click here for a list of possible parameters and odbc states. |
| 42W20 | Error | 2171 | -212L | "CHECKPOINT statement requires a rollback log" | You cannot use a CHECKPOINT statement when the database server is running in bulk mode without a rollback log. Click here for a list of possible parameters and odbc states. |
| 42W21 | Error | 2172 | -214L | "Table in use" | You attempted to ALTER or DROP a table that is being used by other active users of the database. Click here for a list of possible parameters and odbc states. |
| 42W22 | Error | 2187 | -298L | "Attempted two active database requests" | In embedded SQL, you attempted to submit a database request while you have another request in progress. You should either use a separate SQLCA and connection for each thread accessing the database, or use thread synchronization calls to ensure that a SQLCA is only accessed by one thread at a time. Click here for a list of possible parameters and odbc states. |