Messages 998 through 1020

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
-998L Error 2665 WO026 "Cannot close a remote JDBC connection that is not the current connection" When attempting to close a remote JDBC connection, the specified connection must be the local connection.

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

-999L Error 2667 WW020 "Invalid request log format on line %1" The request log file format is invalid. The request log may have been created with an older version of the software.

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

-1000L Error 2668 54W05 "Temporary space limit exceeded" The connection has exceeded its temporary-space usage limit. This limit is based in part on the amount of free-space remaining on the drive containing the temporary file. Try deleting unused files from the drive, or placing the temporary file on a drive with more space available. See the -dt server option to specify a directory for temporary files.

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

-1001L Error 2669 08W71 "Parameter '%1' in procedure or function '%2' does not have a default value" An attempt was made to use DEFAULT as a procedure or function argument, but the corresponding parameter does not have a default value.

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

-1002L Error 2670 WW062 "The option '%1' is not recognized" The specified option was not recognized. The option may have been spelled incorrectly.

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

-1003L Error 2671 28W10 "Too many distinct group mappings for integrated user" The integrated user does not have an explicit mapping in the database but does have group mappings. There are too many distinct group mappings. You must either reduce the number of distinct group mappings or add an explicit mapping for the user.

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

-1004L Error 2672 08W85 "Unable to start specified database: '%1' is not a database" The specified file is not a valid database file.

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

-1005L Error 2673 08W86 "Unable to start specified database: '%1' was created by a different version of the software" The specified database file was created by a different version of the software, and it can not be read by this version.

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

-1006L Error 2674 08W87 "Unable to start specified database: '%1' is not a valid database file" The specified file is not a valid database.

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

-1007L Error 2675 08W88 "Unable to start specified database: '%1' is an invalid transaction log" The specified file is not a valid transaction log.

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

-1008L Error 2676 08W72 "Unable to start specified database: '%1' is an invalid transaction log mirror" The specified file is not a valid transaction log mirror.

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

-1009L Error 2677 08W73 "Unable to start specified database: The transaction log '%1' or its mirror '%2' is invalid" The transaction log differs from the transaction log mirror. Either the transaction log or its mirror is invalid.

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

-1010L Error 2678 08W74 "Unable to start specified database: '%1' not expecting any operations in transaction log" The transaction log contains operations, but the database server was not expecting any.

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

-1011L Error 2679 08W75 "Unable to start specified database: Unknown encryption algorithm" The database is encrypted with an algorithm not supported by this server.

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

-1012L Error 2680 08W76 "Unable to start specified database: '%1' must be upgraded to start with this server (capability %2 missing)" The specified database must be upgraded to start with this server.

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

-1016L Error 2684 08W80 "Unable to start specified database: Cannot use log file '%1' since it has been used more recently than the database file" The transaction log file has been used more recently than the database file.

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

-1017L Error 2685 08W81 "Unable to start specified database: '%1': transaction log file not found" The transaction log file was not found.

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

-1018L Error 2686 08W82 "Unable to start specified database: Cannot use log file '%1' since the offsets do not match the offsets in the database file" The transaction log file has an offset that does not match the offset expected by the database file.

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

-1019L Error 2687 08W83 "Unable to start specified database: Cannot use log file '%1' since the database file has been used more recently" The database file has been used more recently than the transaction log file.

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

-1020L Error 2688 08W84 "Unable to start specified database: Cannot use log file '%1' since it is shorter than expected" The transaction log file is shorter than expected.

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


Created April 27, 2010. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com