Messages 985 through 1004

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
-985L Error 2845 08W20 "The database name 'utility_db' is reserved for the utility database." You are attempting to start a database with the name "utility_db". This name is reserved for the utility database.

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

-986L Error 2653 WW055 "Invalid procedure type '%1'" A procedure or function was specified with an invalid type.

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

-987L Error 2654 WW056 "Invalid procedure subtype '%1' for type '%2'" A procedure or function was specified with an invalid subtype for the given procedure type.

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

-988L Error 2655 WW057 "Invalid response from the HTTP server" The response from the remote HTTP server was invalid. It may have been empty, malformed, missing header information, and so on.

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

-989L Error 2656 WW058 "NAMESPACE attribute is not valid with procedure type '%1'" The NAMESPACE attribute is only applicable to procedures of type SOAP.

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

-990L Error 2657 WW059 "The secure connection to the remote host failed: %1" The server was unable to initiate a secure connection with the remote host.

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

-991L Error 2658 WW060 "Clause '%1' has invalid attribute '%2'" The attribute value specified on the procedure is not valid.

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

-992L Error 2659 54W04 "The specified listener could not be registered" The specified listener could not be registered because the maximum number of listeners has been reached, the class name is already in use, or system resources are not available.

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

-993L Error 2660 WL007 "LOAD TABLE not allowed on temporary table with ON COMMIT DELETE ROWS" The LOAD TABLE statement automatically commits at completion. If a temporary table being loaded was declared with ON COMMIT DELETE ROWS, the rows are discarded at completion.

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

-994L Error 2661 42WAC "Too many arguments for function or procedure '%1'" You supplied an argument list that the database server cannot handle. This can happen if the argument list of the function or stored procedure is too long. Rebuilding the database with a larger page size could prevent this error.

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

-995L Error 2662 WP016 "Warning detected when optimizing SELECT INTO is treated as an error" The SELECT...INTO #TEMPTABLE statement cannot proceed if a warning is detected while optimizing the query. To fix the problem, test the query by removing the INTO clause, and resolve the reported warning.

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

-996L Error 2663 WO024 "Specified local connection ID not found" There is no connection with the specified connection ID.

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

-997L Error 2664 WO025 "Local connection ID does not refer to the current database" The specified connection ID is for a connection to a database other than the current database.

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

-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.


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