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 |
|---|---|---|---|---|---|
| -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. |
| -1299L | Error | 2988 | WW127 | "Drop multiplex server is allowed only in a multiplex setup." | Drop multiplex server is allowed only in a multiplex setup. Click here for a list of possible parameters and odbc states. |
| -1300L | Error | 2989 | WW128 | "Cannot add first multiplex server with excluded status." | Users are not allowed to add the first multiplex server with status excluded. Click here for a list of possible parameters and odbc states. |
| -1301L | Error | 2990 | WW129 | "Cannot create multiplex server with role coordinator." | Users are not allowed to create a multiplex server with role as coordinator. Click here for a list of possible parameters and odbc states. |
| -1302L | Error | 2982 | WW121 | "Host Port specification (%1) is invalid." | Host port specification is invalid. Click here for a list of possible parameters and odbc states. |
| -1303L | Error | 2991 | 54W16 | "Too many MESSAGE ... FOR CONNECTION messages" | You executed a MESSAGE ... FOR CONNECTION statement and the maximum number of messages for the connection have already been queued. Click here for a list of possible parameters and odbc states. |
| -1304L | Error | 2992 | WT021 | "Could not create a new text index for this table with the same settings as \"%1\No message | Two text indexes with the same column list and configuration settings cannot be created for a table. Click here for a list of possible parameters and odbc states. |
| -1305L | Error | 2993 | 0AWD5 | "MobiLink communication error; code: %1, parameter: %2, system code %3" | An error was encountered while communicating with a MobiLink server. Click here for a list of possible parameters and odbc states. |
| -1306L | Error | 2994 | WW238 | "IN DBSPACE clause cannot be used for column '%1' since table '%2' is a partitioned table." | Entire column cannot be assigned to a dbspace using the IN DBSPACE clause, if the table is a partitioned table. Click here for a list of possible parameters and odbc states. |
| -1313L | Error | 2969 | 54W17 | "Maximum string length exceeded" | A string operation attempted to create a string longer than the maximum allowed by the server. Click here for a list of possible parameters and odbc states. |
| -1315L | Error | 2931 | WW046 | "Script file missing statement \"go\" delimiter on a separate line" | For UltraLite, all non-comment SQL statements in a script file (including the final one) must be followed by "go" on a line by itself. For strings, you can use "\ngo" to end a statement. Click here for a list of possible parameters and odbc states. |
| -1316L | Error | 2930 | 0AW25 | "Unsupported load column specification used for a catalog store table." | For catalog store tables, only some of the load column specifications (e.g. filler) are permitted. Click here for a list of possible parameters and odbc states. |
| -1317L | Error | 2919 | WW239 | "Multiplex server '%1' is shutting down due to a successful configuration change" | Successful execution of certain commands to change multiplex configuration forces server shutdown. You will get the above error if you issue such a command. Click here for a list of possible parameters and odbc states. |
| -1320L | Error | 2822 | QFA62 | "Error raised by user-defined function: %1" | An error was raised by a user-defined function. Click here for a list of possible parameters and odbc states. |
| -1330L | Error | 2823 | 42WE0 | "The function '%1' does not allow use of the '%2' clause" | You have attempted to use the specified SQL clause within the context of a function that does not permit such use. Note that the function may have been used directly in the query or indirectly within a named window. Click here for a list of possible parameters and odbc states. |
| -1331L | Error | 2807 | 42WE1 | "The function '%1' requires the use of the '%2' clause" | You have attempted to invoke the specified function without the use of a mandatory SQL clause within the context of the function. Note that the function may have been used directly in the query or indirectly within a named window. Click here for a list of possible parameters and odbc states. |
| -1347L | Error | 2776 | 28W16 | "Use of authority '%1' is not supported on the current database" | The current database is an older database and does not have the capability to support given authority. You must upgrade your database to use this authority. Click here for a list of possible parameters and odbc states. |