Messages 732 through 760

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

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

-734L Error 2379 09W08 "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.

-735L Error 2030 08W24 "Invalid parameter" An error occurred while evaluating a parameter.

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

-736L Error 2367 WO022 "The data type of column or variable '%1' is not supported" The column is defined with a data type that is not supported for remote tables or the variable is defined with a datatype that is not supported for using and location clauses.

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

-737L Error 2382 42W54 "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.

-738L Error 2383 54W07 "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.

-739L Error 2386 55W07 "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.

-740L Error 2385 WW024 "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.

-744L Error 2390 08W51 "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.

-745L Error 2391 08W52 "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.

-746L Error 2392 08W53 "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.

-749L Error 2395 0AW07 "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.

-750L Error 2396 42W55 "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.

-751L Error 2397 42W56 "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.

-754L Error 2400 08W54 "Parse error: %1" An invalid data source name was used in the connection string.

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

-755L Error 2401 0AW08 "You cannot synchronize or upgrade with uncommitted transactions" You attempted to synchronize or upgrade the schema of an UltraLite database and there are changes in the UltraLite database that have not been committed.

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

-757L Error 2404 55W08 "Modifications not permitted for read-only database" You attempted an update operation on a database that was declared as read-only.

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

-759L Error 2406 07W05 "SQLDA data type invalid" The data type specified for a SQLDA variable is invalid.

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

-760L Error 2407 07W06 "Invalid SQL identifier" An invalid identifier was supplied through the C language interface. For example, you may have supplied a NULL string for a cursor name.

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