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 |
|---|---|---|---|---|---|
| -1577L | Error | 3219 | QFA67 | "Invalid error raised by user-defined function: (%1) %2." | An error was raised by a user-defined function that is outside reserved range. Click here for a list of possible parameters and odbc states. |
| -1578L | Error | 3220 | WO009 | "Table parameterized functions are not allowed across server types." | Table parameterized functions are not allowed across server types if a query is not processed in full-passthrough mode. Click here for a list of possible parameters and odbc states. |
| -1579L | Error | 3221 | WO031 | "External procedures or functions are not allowed across server types." | External procedure or function calls are not allowed across server types if the query is not processed in full-passthrough mode. Click here for a list of possible parameters and odbc states. |
| -1580L | Error | 3222 | WW207 | "Failed to load the MobiLink client support libraries." | In order to use the SYNCHRONIZE command, a MobiLink client must be installed on the same computer where the database server is running. Click here for a list of possible parameters and odbc states. |
| -1581L | Error | 3223 | 08WA7 | "Database name must be specified when connecting to a cloud database server" | When connecting to a cloud database server, a database name must be specified by the connection string. Cloud database servers do not have a default database. Click here for a list of possible parameters and odbc states. |
| -1582L | Error | 3224 | 08WA8 | "Server name can only be specified when connecting to a cloud database server with NODETYPE=DIRECT" | When connecting to a cloud database server, specifying a server name on the connection string is only allowed for NODETYPE=DIRECT. When using other NODETYPE values to connect to a cloud database server, specifying the server name is not allowed. Typically, for connections to a cloud database server the HOST connection parameter or HOST protocol option is used to specify the address of one or more cloud database servers. Click here for a list of possible parameters and odbc states. |
| -1583L | Error | 3225 | WQ021 | "Cannot upgrade the database. The database can be upgraded only after starting the coordinator in single node mode." | In order to run ALTER DATABASE UPGRADE on the database, the coordinator must be started in single node mode using the '-iqmpx_sn 1' server startup option. Click here for a list of possible parameters and odbc states. |
| -1584L | Error | 3226 | 08WA9 | "Unable to load the dbrsakp shared object" | The server was unable to load the dbrsakp DLL on Windows platforms or the libdbrsakp shared object on Unix platforms. Click here for a list of possible parameters and odbc states. |
| -1585L | Error | 3227 | 08WB1 | "Invalid tool name or admin user for generating security token" | The tool name or admin user supplied is invalid for generating a security token. Click here for a list of possible parameters and odbc states. |
| -1590L | Error | 3232 | WO032 | "You cannot use a security token when making remote connections" | A security token cannot be used to make remote data access connections Click here for a list of possible parameters and odbc states. |
| -1593L | Error | 3235 | 08WB2 | "Unable to copy file %1 to destination %2" | The client database file could not be copied to the requested cloud destination. Click here for a list of possible parameters and odbc states. |
| -1597L | Error | 2363 | WW166 | "The transaction may not be committed because the primary server lost quorum" | You attempted to commit a transaction on a primary server that just lost quorum with the partner and arbiter servers. The transaction may or may not have been committed. The partner servers will attempt to determine which server will become the new primary server. Click here for a list of possible parameters and odbc states. |
| -1605L | Error | 3246 | WP020 | "Table Parameterized Functions and V4 TableUDFs are not supported for this database." | The current database does not have catalog support for table parameterized functions. To use this feature, upgrade your database to the most recent version. Click here for a list of possible parameters and odbc states. |
| -1606L | Error | 3247 | WP021 | "Multiple table parameters are not supported." | Table parameterized functions are limited to only having at most a single table parameter. Click here for a list of possible parameters and odbc states. |
| -1607L | Error | 3249 | WP022 | "Outer references are not allowed for TPF input tables." | Outer references in the select list for a TPF input table are not allowed. Click here for a list of possible parameters and odbc states. |
| -1608L | Error | 3250 | 08WB4 | "Unable to delete file %1" | The request to delete a file failed Click here for a list of possible parameters and odbc states. |
| -1609L | Error | 3251 | 08WB5 | "File %1 already exists" | The request to create a file or directory failed because the file or directory already exists Click here for a list of possible parameters and odbc states. |
| -1610L | Error | 3252 | 08WB6 | "Unable to create directory %1" | The request to create a directory failed Click here for a list of possible parameters and odbc states. |
| -1611L | Error | 3253 | 08WB7 | "Unable to copy file %1" | The request to copy a file failed Click here for a list of possible parameters and odbc states. |
| -1618L | Error | 3260 | WO034 | "The %1 remote data access class has been deprecated, please use %2 instead or change cis_option" | You attempted to use a JDBC based remote data access class which has been deprecated. Please use the appropriate ODBC based class instead; or change the cis_option setting to re-enable this feature. Click here for a list of possible parameters and odbc states. |