Messages 828 through 847

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
-828L Error 2475 WW027 "A conflict with the dbmlsync download phase was detected" Dbmlsync uses this error to detect download phase conflicts with rows modified by other connections.

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

-829L Error 2476 08W59 "TLS handshake failure" The connection failed because of a failure in the TLS handshaking process.

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

-830L Error 2477 42W60 "Alias '%1' is not unique" The same alias is used more than once in a select list.

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

-831L Error 2478 42W61 "Definition for alias '%1' must appear before its first reference" An expression contains a reference to an alias, but the alias is defined later in the select list. The alias definition must appear before its first reference.

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

-832L Error 2479 08W60 "Connection error: %1" An error occurred while attempting to establish a connection with the database server, but before attempting to connect to a database. Failure to initialize a communication link during the connection attempt is an example of this error. Creating a debug log file using the LogFile connection parameter may provide more information.

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

-833L Error 2480 42W62 "Row in table '%1' was modified or deleted in BEFORE trigger" A BEFORE trigger has updated or deleted the row that caused the trigger to fire, preventing the original operation from completing. The trigger must be re-written so that it does not attempt to change the row via UPDATE or DELETE statements.

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

-834L Error 2083 52005 "Column '%1' not found in table '%2'" You misspelled the name of a column, or the column you are looking for is in a different table.

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

-835L Error 2482 WE009 "Event '%1' in use" You have attempted to drop an event that is currently in use.

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

-836L Error 2483 42W63 "Procedure '%1' is no longer valid" A procedure definition cannot be loaded from the catalog. Check for tables or columns that have been renamed or that may be reserved words. If this procedure is an internal procedure, you may have an older version. Database upgrade may be needed to run it successfully.

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

-837L Error 2484 42W64 "Trigger or foreign key for table '%1' is no longer valid" A trigger definition cannot be loaded from the catalog. Check for tables or columns that have been renamed or that may be reserved words. The trigger may be a system-generated trigger to enforce the referential actions of a foreign key.

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

-838L Error 2485 08W61 "TLS initialization on server failed" The connection failed because the initialization of the TLS library on the server failed.

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

-839L Error 2486 0AW11 "Download failed because of conflicts with existing rows" You attempted a download-only synchronization with modified rows in the UltraLite database. There was a conflict between one or more rows in the download stream and rows in the UltraLite database.

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

-840L Error 2487 08W62 "Incorrect or missing encryption key" The database is encrypted with a key. There was no key given to start the database, or the key given was incorrect.

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

-841L Error 2488 WJ026 "The JDK version in '%1' does not match '%2'" The JDK version specified in the CREATE DATABASE statement does not match the JDK version in the JDK JAR file.

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

-842L Error 2489 WJ025 "JDK '%1' is not a supported JDK" Either the JDK version specified in the CREATE DATABASE statement is unsupported or the version in the manifest file of the JDK JAR file is unsupported.

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

-843L Error 2490 5RW37 "Cannot find synchronization user with the name '%1'" You misspelled the name of a synchronization site or you did not qualify it correctly with a user name.

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

-844L Error 2491 5RW39 "Cannot find synchronization definition with the name '%1'" You misspelled the name of a synchronization definition or you did not qualify it correctly with a user name.

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

-845L Error 2492 42U02 "Owner '%1' used in a qualified column reference does not match correlation name '%2'" Your query contains a qualified column reference to a table name, but either a correlation name has been used for that table, or the owner of the table does not match the owner name specified in the column reference. Remove the owner qualification, and qualify column references only by correlation name.

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

-846L Error 2493 42U03 "SET clause for column '%1' used incorrectly" Your UPDATE statement contains an invalid SET clause, for example, there are multiple SET clauses for the same column.

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

-847L Error 2494 WJ027 "Java SecurityManager class not found: %1" The class specified is either not a SecurityManager subclass or cannot be found.

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