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 |
|---|---|---|---|---|---|
| -721L | Error | 2354 | WO015 | "The data type specified for column '%1' is not compatible with the actual data type" | The data type of the column specified in the CREATE EXISTING statement is not compatible with the actual data type of the column in the remote table. Click here for a list of possible parameters and odbc states. |
| -722L | Error | 2355 | WO016 | "The column '%1' does not exist in the remote table" | The column specified in the CREATE EXISTING statement does not exist in the remote table. Click here for a list of possible parameters and odbc states. |
| -723L | Error | 2356 | WO017 | "The length specified for column '%1' is different than the actual length" | The length of the column specified in the CREATE EXISTING statement is different than the length of the column in the remote table. Click here for a list of possible parameters and odbc states. |
| -724L | Error | 2357 | WO018 | "NULL attribute mismatch for column '%1'" | The NULL attribute of the column specified in the CREATE EXISTING statement differs from the NULL attribute of the actual column. Click here for a list of possible parameters and odbc states. |
| -725L | Error | 2358 | WO019 | "Identity attribute mismatch for column '%1'" | The identity attribute of the column specified in the CREATE EXISTING statement differs from the identity attribute of the actual column. Click here for a list of possible parameters and odbc states. |
| -726L | Error | 2359 | WO020 | "The table specification '%1' identifies more than one remote table" | More than one table was found on the remote server for the given table specification. Add a database or owner name to the specification. Click here for a list of possible parameters and odbc states. |
| -727L | Error | 2362 | WI010 | "The optimizer was unable to construct a valid access plan" | The database server was unable to construct a valid access plan for the given request. This is a SQL Anywhere internal error. If it can be reproduced, it should be reported to iAnywhere. You may be able to work around this problem by modifying the query statement. Click here for a list of possible parameters and odbc states. |
| -728L | Error | 2372 | 42W35 | "Update operation attempted on non-updatable remote query" | You attempted an update or delete operation on a remote table that is currently not implemented. Examples of such operations include positioned updates and updates that require building of work tables. Click here for a list of possible parameters and odbc states. |
| -729L | Error | 2373 | 23507 | "The specified foreign key (%1) can not be enforced" | You attempted to create a foreign key that cannot be enforced. In order to be enforceable, the primary and foreign table for the specified key must exist on the same server. You can use the UNENFORCED keyword to create a foreign key specification that is not to be enforced. Click here for a list of possible parameters and odbc states. |
| -730L | Error | 2374 | WP010 | "Invalid JAR file" | A file passed to the INSTALL JAVA statement was not a valid JAR file. Click here for a list of possible parameters and odbc states. |
| -731L | Error | 2377 | 55W06 | "Cannot drop a user that owns objects involved in replication" | You attempted to drop a user that is the creator of a database object involved in replication. For example, the user may own a table that is part of a publication. Click here for a list of possible parameters and odbc states. |
| -732L | Error | 2366 | WO021 | "Creating remote tables with computed columns is not supported" | Computed columns are not supported in CREATE TABLE statements that specify a remote location. Click here for a list of possible parameters and odbc states. |
| -733L | Error | 2378 | 23504 | "Number of columns allowing NULLs exceeds limit" | You attempted to create or modify a table definition such that the number of columns that allow NULLS is now more than the limit on such columns. The limit is a function of database page size and is approximately 8*(page-size - 30). Click here for a list of possible parameters and odbc states. |
| -734L | Error | 2379 | 09W08 | "Cannot update or delete an all-NULL row from table '%1'" | You attempted to modify or delete a row in the specified table, which is part of the NULL-supplying side of an outer join. However, the cursor is currently positioned on a derived row that contains an all-NULL row for this table, which is the result of the failure of one or more ON conditions to evaluate to TRUE. Verify that the UPDATE or DELETE statement is correct. Click here for a list of possible parameters and odbc states. |
| -735L | Error | 2030 | 08W24 | "Invalid parameter" | An error occurred while evaluating a parameter. Click here for a list of possible parameters and odbc states. |
| -736L | Error | 2367 | WO022 | "The data type of column '%1' is not supported" | The column is defined with a data type that is not supported for remote tables. Click here for a list of possible parameters and odbc states. |
| -737L | Error | 2382 | 42W54 | "Signature '%1' does not match procedure parameters" | The number of types in the signature must match the number of procedure parameters. If a DYNAMIC RESULT SETS clause was specified, the number of dynamic result sets must match the quantity found in the signature. Click here for a list of possible parameters and odbc states. |
| -738L | Error | 2383 | 54W07 | "Password must be at least %1 characters" | The password is shorter than that allowed by the current min_password_length option setting. Click here for a list of possible parameters and odbc states. |
| -739L | Error | 2386 | 55W07 | "db_init has not been called or the call to db_init failed" | The SQLCA passed to a dblib entry point has not been initialized by a call to db_init or the call to db_init failed. Click here for a list of possible parameters and odbc states. |
| -740L | Error | 2385 | WW024 | "The communications environment could not be created" | The communications environment could not be created. Either there are insufficient resources to create the environment or the language resource file cannot be found. Click here for a list of possible parameters and odbc states. |