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 |
|---|---|---|---|---|---|
| -937L | Error | 2601 | 42U06 | "Invalid reference to or operation on constraint '%1'" | You specified an invalid operation on a constraint. For example, you tried to alter a primary key constraint. Click here for a list of possible parameters and odbc states. |
| -938L | Error | 2602 | 42WA0 | "Recursion is not allowed without the RECURSIVE keyword" | The common table expressions for a recursive query must be defined using a WITH RECURSIVE clause. Click here for a list of possible parameters and odbc states. |
| -939L | Error | 2603 | 42W83 | "Invalid setting for HTTP option '%1'" | You supplied an invalid value for an HTTP option. 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. |
| -940L | Error | 2604 | 42W84 | "Invalid setting for HTTP header '%1'" | You supplied an invalid value for an HTTP header. Click here for a list of possible parameters and odbc states. |
| -941L | Error | 2605 | 08W69 | "jConnect does not support encryption" | You supplied an encryption type for a connection using jConnect. jConnect does not support encryption. Click here for a list of possible parameters and odbc states. |
| -942L | Error | 2606 | WW029 | "A workload capture (%1) is already in progress" | You have tried to initiate a workload capture when one is already in progress. You need to wait for the other capture to complete. Click here for a list of possible parameters and odbc states. |
| -943L | Error | 2607 | WW030 | "No workload capture currently exists" | You have tried to stop, pause, resume, or get the status of a workload capture, but no workload captures exist. Click here for a list of possible parameters and odbc states. |
| -944L | Error | 2608 | 42WA1 | "Too many expressions in GROUP BY list for ROLLUP, CUBE, or GROUPING SETS operation" | You specified too many expressions in the GROUP BY list for the requested ROLLUP, CUBE, or GROUPING SETS operation. The current environment where SQL Anywhere is executing cannot support this number of expressions in the GROUP BY list for the requested operation. Click here for a list of possible parameters and odbc states. |
| -945L | Error | 2609 | 42WA2 | "Recursive column %1: conversion from '%2' to '%3' loses precision" | Every column in the recursive subquery must be convertible to the type of the corresponding column in the initial subquery without loss of precision. Try casting the column in the initial subquery to an appropriate type. Click here for a list of possible parameters and odbc states. |
| -946L | Error | 2610 | 09W03 | "Result set not permitted in '%1'" | You attempted to execute a SELECT statement in a context where a result set is not permitted. Click here for a list of possible parameters and odbc states. |
| -947L | Error | 2611 | 42WA3 | "Window '%1' not found" | You have attempted to reference a window name that is not defined in the window list of the SELECT statement. Click here for a list of possible parameters and odbc states. |
| -948L | Error | 2612 | 42WA4 | "PARTITION BY not allowed in reference to window '%1'" | When an existing window name is referenced from an inline window specification, the inline specification must not have a PARTITION BY clause. Click here for a list of possible parameters and odbc states. |
| -949L | Error | 2613 | 42WA5 | "ORDER BY not allowed in window '%1'" | When an existing window name is referenced from an inline window specification, either the inline window or the referenced window may have an ORDER BY, but not both. Click here for a list of possible parameters and odbc states. |
| -950L | Error | 2614 | 42WA6 | "Frame not allowed for window '%1'" | Frames are not allowed on windows referenced from inline window specifications. Click here for a list of possible parameters and odbc states. |
| -951L | Error | 2615 | WW031 | "Cannot access schema file '%1'" | UltraLite requires a schema file to perform the current operation. Either no schema file was specified or the one specified was not accessible or was corrupt. Click here for a list of possible parameters and odbc states. |
| -952L | Error | 2616 | WW032 | "The status of the last synchronization upload is unknown" | The status of the last synchronization upload is unknown. The current operation cannot proceed until a successful upload is synchronized. Click here for a list of possible parameters and odbc states. |
| -953L | Error | 2617 | WW033 | "A schema upgrade is not currently allowed" | A schema upgrade cannot proceed because of concurrent use of the database. For example, all cursors must be closed before a schema upgrade can occur. Click here for a list of possible parameters and odbc states. |
| -954L | Error | 2618 | WW034 | "The database '%1' was not found" | The named database was not found. Ensure your connection string properly names the desired database. Click here for a list of possible parameters and odbc states. |
| -955L | Error | 2619 | WW035 | "This connection already exists" | A connection with the given SQLCA and name (or no name) already exists. Before connecting you must disconnect the existing connection, or specify a different connection name. Click here for a list of possible parameters and odbc states. |
| -956L | Error | 2620 | WW036 | "Information for synchronization is incomplete or invalid, check '%1'" | Information for synchronization is incomplete or invalid. Correct the indicated parameter before attempting to synchronize again. If init_verify is indicated, the ULInitSynchInfo function was not called. Click here for a list of possible parameters and odbc states. |