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 |
|---|---|---|---|---|---|
| 2379 | Error | 09W08 | -734L | "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. |
| 2380 | Error | 08W49 | -95L | "Parse error: %1" | An error occurred while parsing a connection string. Click here for a list of possible parameters and odbc states. |
| 2381 | Warning | 01W16 | 118L | "Illegal user selectivity estimate specified" | You specified a user selectivity estimate that is either not a literal constant or is outside the range 0.0 to 100.0 (estimates are specified as percentages). The estimate has been ignored. Click here for a list of possible parameters and odbc states. |
| 2382 | Error | 42W54 | -737L | "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. |
| 2383 | Error | 54W07 | -738L | "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. |
| 2384 | Warning | 01W17 | 120L | "'%1' is an unknown option" | You attempted to set the value of an option that is not known to the server. Click here for a list of possible parameters and odbc states. |
| 2385 | Error | WW024 | -740L | "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. |
| 2386 | Error | 55W07 | -739L | "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. |
| 2388 | Error | WJ015 | -742L | "JDBC SAStatement batch execute abandoned" | An error occurred when executing a statement in the batch. The rest of the statements in the batch will be abandoned. Click here for a list of possible parameters and odbc states. |
| 2389 | Error | WJ016 | -743L | "Seek absolute 0 was attempted on a JDBC SAResultSet" | There is no row zero on JDBC resultSets. The valid row numbers are 1, 2, ..., -2, -1. Click here for a list of possible parameters and odbc states. |
| 2390 | Error | 08W51 | -744L | "Invalid IQ database command line option or parameter value: %1" | An invalid command line option was used. The option began with -iq, but is either invalid or contained a bad parameter. Click here for a list of possible parameters and odbc states. |
| 2391 | Error | 08W52 | -745L | "Cannot initialize IQ memory manager: %1" | System V shared memory was requested but could not be allocated. Click here for a list of possible parameters and odbc states. |
| 2392 | Error | 08W53 | -746L | "Cannot allocate System V resources" | IQ was unable to allocate System V resources. Delete unused System V semaphores and shared memory segments or increase operating system configuration values for these resources. Click here for a list of possible parameters and odbc states. |
| 2393 | Error | WJ017 | -747L | "Invalid JDBC resultset type" | An invalid resultset type was used when creating a JDBC statement. Click here for a list of possible parameters and odbc states. |
| 2394 | Error | WJ018 | -748L | "Invalid JDBC resultset concurrency" | An invalid resultset concurrency was used when creating a JDBC statement. Click here for a list of possible parameters and odbc states. |
| 2395 | Error | 0AW07 | -749L | "Feature not available with UltraLite" | You attempted to execute a statement or use a feature that is not supported in an UltraLite database. Click here for a list of possible parameters and odbc states. |
| 2396 | Error | 42W55 | -750L | "User owns procedures in use" | You attempted to drop a user that owns a procedure being used by other active users of the database. Click here for a list of possible parameters and odbc states. |
| 2397 | Error | 42W56 | -751L | "User owns tables in use" | You attempted to REVOKE CONNECT from a user that owns a table being used by other active users of the database. Click here for a list of possible parameters and odbc states. |
| 2398 | Error | WJ019 | -752L | "Cannot call the '%1' function on a JDBC resultset when it is positioned on an insert row" | Some resultset functions such as updateRow and deleteRow are invalid when the cursor of the resultset is positioned at the insert row. Click here for a list of possible parameters and odbc states. |
| 2399 | Error | WJ020 | -753L | "The JDBC resultset must be positioned on an insert row in order to use the '%1' function" | Resultset functions such as insertRow can only be called when the resultset is positioned on the insert row. Click here for a list of possible parameters and odbc states. |