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 |
|---|---|---|---|---|---|
| 52005 | Error | 2083 | -834L | "Column '%1' not found in table '%2'" | You misspelled the name of a column, or the column you are looking for is in a different table. Click here for a list of possible parameters and odbc states. |
| 52009 | Error | 2056 | -119L | "Primary key column '%1' already defined" | You listed the same column name twice in the definition of a primary key. Click here for a list of possible parameters and odbc states. |
| 52010 | Error | 2047 | -110L | "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. |
| 52012 | Error | 2079 | -139L | "More than one table is identified as '%1'" | You identified two tables in the same FROM clause with the same correlation name. Click here for a list of possible parameters and odbc states. |
| 52W02 | Error | 2082 | -142L | "Correlation name '%1' not found" | You misspelled a correlation name, or you used a table name instead of the correlation name. Click here for a list of possible parameters and odbc states. |
| 52W03 | Error | 2063 | -183L | "Cannot find index named '%1'" | You attempted to perform an operation using an index that does not exist. Check for spelling errors. Check whether the index name must be qualified with a user ID. Click here for a list of possible parameters and odbc states. |
| 52W04 | Error | 2048 | -111L | "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. |
| 52W05 | Error | 2058 | -126L | "Table cannot have two primary keys" | You specified the primary key twice in a CREATE TABLE statement. Click here for a list of possible parameters and odbc states. |
| 52W06 | Error | 2062 | -251L | "Foreign key '%1' for table '%2' duplicates an existing foreign key" | You attempted to define a foreign key that already exists. Click here for a list of possible parameters and odbc states. |
| 52W07 | Error | 2085 | -145L | "Foreign key name '%1' not found" | You misspelled the name of a foreign key, or the foreign key does not exist. Click here for a list of possible parameters and odbc states. |
| 52W08 | Error | 2087 | -147L | "There is more than one way to join '%1' to '%2'" | You are attempting to KEY JOIN two tables, and there are two or more foreign keys relating the two tables. There may be two foreign keys from the first table to the second table. It may be that each table has a foreign key to the other table. You must use a correlation name for the primary key table that is the same as the role name of the desired foreign key relationship. Click here for a list of possible parameters and odbc states. |
| 52W09 | Error | 2144 | -265L | "Procedure '%1' not found" | You misspelled the name of a procedure, or you did not qualify a procedure name with a user name. Click here for a list of possible parameters and odbc states. |
| 52W10 | Error | 2147 | -268L | "Trigger '%1' not found" | You misspelled the name of a trigger, or you did not qualify a trigger name with a user name. Click here for a list of possible parameters and odbc states. |
| 52W11 | Error | 2150 | -271L | "Trigger definition conflicts with existing triggers" | You attempted to create a trigger, but a trigger with the same name already exists. Click here for a list of possible parameters and odbc states. |
| 52W12 | Error | 2151 | -272L | "Invalid REFERENCES clause in trigger definition" | You supplied an invalid REFERENCES clause in a trigger definition. You may have specified an OLD correlation name in a BEFORE INSERT trigger, or a NEW correlation name in an AFTER DELETE trigger. In both cases, the values do not exist and cannot be referenced. Click here for a list of possible parameters and odbc states. |
| 52W13 | Error | 2078 | -138L | "Dbspace '%1' not found" | You tried to access a dbspace that the database server could not find. Click here for a list of possible parameters and odbc states. |
| 52W14 | Error | 2088 | -136L | "Table '%1' is in an outer join cycle" | You specified outer joins that create a cycle of tables. Click here for a list of possible parameters and odbc states. |
| 52W15 | Error | 2090 | -137L | "Table '%1' requires a unique correlation name" | You specified a join that joins a table to itself. You need to use unique correlation names in order to have multiple instances of a table. Click here for a list of possible parameters and odbc states. |
| 52W16 | Error | 2064 | -610L | "User message %1 already exists" | The message with this error number already exists in the database. Click here for a list of possible parameters and odbc states. |
| 52W17 | Error | 2097 | -612L | "User message %1 not found" | The message with this error number does not exist in the database. Click here for a list of possible parameters and odbc states. |