Messages 2352 through 2378

Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.

Number Msg Type SQL State SQL Code Message Possible Cause
2352 Error 42W53 -217L "The option '%1' cannot be set from within a procedure" The option specified in the SET OPTION statement cannot be set from within a procedure.

Click here for a list of possible parameters and odbc states.

2353 Error 08W48 -218L "Authentication failed" You set the database_authentication or connection_authentication option incorrectly.

Click here for a list of possible parameters and odbc states.

2354 Error WO015 -721L "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.

2355 Error WO016 -722L "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.

2356 Error WO017 -723L "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.

2357 Error WO018 -724L "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.

2358 Error WO019 -725L "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.

2359 Error WO020 -726L "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.

2360 Warning 01W13 115L "Database server cannot convert data from/to character set '%1', conversion may not be correct" The database server cannot convert character data from/to the character set requested by the application because the character set is not supported. The connection succeeds, but character conversion may not be correct for all characters.

Click here for a list of possible parameters and odbc states.

2361 Error 40W08 -309L "Memory error -- transaction rolled back" The UltraLite runtime has received an unexpected error from the system calls being used to store the UltraLite database. For example, a write to persistent memory failed. This is an internal error and indicates faulty or corrupt persistent storage on the device. A ROLLBACK statement has been automatically executed.

Click here for a list of possible parameters and odbc states.

2362 Error WI010 -727L "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.

2366 Error WO021 -732L "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.

2367 Error WO022 -736L "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.

2372 Error 42W35 -728L "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.

2373 Error 23507 -729L "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.

2374 Error WP010 -730L "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.

2375 Warning 01W14 116L "Language '%1' is not supported, '%2' will be used" The language that the application requested is not supported by the server to which the application is connecting. Instead, the server will send message strings in the language stated.

Click here for a list of possible parameters and odbc states.

2376 Warning 01W15 117L "Unsupported character set '%1' and unsupported language '%2'; language used is '%3' instead" The character set that the application requested is not supported by the server to which the application is connecting. The language that the application requested is not supported either. Language strings will be sent in the language specified.

Click here for a list of possible parameters and odbc states.

2377 Error 55W06 -731L "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.

2378 Error 23504 -733L "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.


Created May 6, 2011. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com