Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 733 | "Number of columns allowing NULLs exceeds limit" |
|---|---|
Constant | TOO_MANY_NULL_COLUMNS |
SAP Sybase Error Number | 2378 |
SQL State | 23504 |
SQL Code | -733L |
ODBC 2 State | 23000 |
ODBC 3 State | 23000 |
Severity Code | |
Probable Cause | 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). |
| Error 734 | "Cannot update or delete an all-NULL row from table '%1'" |
|---|---|
Constant | CANNOT_UPDATE_NULL_ROW |
SAP Sybase Error Number | 2379 |
SQL State | 09W08 |
SQL Code | -734L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The name of the table that cannot be modified. |
Probable Cause | 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. |
| Error 735 | "Invalid parameter" |
|---|---|
Constant | INVALID_PARAMETER |
SAP Sybase Error Number | 2030 |
SQL State | 08W24 |
SQL Code | -735L |
ODBC 2 State | 08004 |
ODBC 3 State | 08004 |
Severity Code | |
Probable Cause | An error occurred while evaluating a parameter. |
| Error 736 | "The data type of column or variable '%1' is not supported" |
|---|---|
Constant | OMNI_UNSUPPORTED_DATATYPE |
SAP Sybase Error Number | 2367 |
SQL State | WO022 |
SQL Code | -736L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the column or variable. |
Probable Cause | 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. |
| Error 737 | "Signature '%1' does not match procedure parameters" |
|---|---|
Constant | SIGNATURE_MISMATCH |
SAP Sybase Error Number | 2382 |
SQL State | 42W54 |
SQL Code | -737L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The value of the signature. |
Probable Cause | 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. |
| Error 738 | "Password must be at least %1 characters" |
|---|---|
Constant | PASSWORD_TOO_SHORT |
SAP Sybase Error Number | 2383 |
SQL State | 54W07 |
SQL Code | -738L |
ODBC 2 State | 37000 |
ODBC 3 State | 54000 |
Severity Code | |
Probable Cause | The password is shorter than that allowed by the current min_password_length option setting. |
| Error 739 | "db_init has not been called or the call to db_init failed" |
|---|---|
Constant | DB_INIT_NOT_CALLED |
SAP Sybase Error Number | 2386 |
SQL State | 55W07 |
SQL Code | -739L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
| Error 740 | "The communications environment could not be created" |
|---|---|
Constant | FAILED_TO_CREATE_STREAMS_ENV |
SAP Sybase Error Number | 2385 |
SQL State | WW024 |
SQL Code | -740L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The communications environment could not be created. Either there are insufficient resources to create the environment or the language resource file cannot be found. |
| Error 744 | "Invalid IQ database command line option or parameter value: %1" |
|---|---|
Constant | IQ_INVALID_COMMAND_LINE |
SAP Sybase Error Number | 2390 |
SQL State | 08W51 |
SQL Code | -744L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | The command line option that is invalid. |
Probable Cause | An invalid command line option was used. The option began with -iq, but is either invalid or contained a bad parameter. |
| Error 745 | "Cannot initialize IQ memory manager: %1" |
|---|---|
Constant | IQ_MEMORY_MANAGER_FAILED |
SAP Sybase Error Number | 2391 |
SQL State | 08W52 |
SQL Code | -745L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | A message describing the error that occurred. |
Probable Cause | System V shared memory was requested but could not be allocated. |
| Error 746 | "Cannot allocate System V resources" |
|---|---|
Constant | IQ_SYSTEM_V_FAILURE |
SAP Sybase Error Number | 2392 |
SQL State | 08W53 |
SQL Code | -746L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | 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. |
| Error 749 | "Feature not available with UltraLite" |
|---|---|
Constant | NOT_SUPPORTED_IN_ULTRALITE |
SAP Sybase Error Number | 2395 |
SQL State | 0AW07 |
SQL Code | -749L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted to execute a statement or use a feature that is not supported in an UltraLite database. |
| Error 750 | "User owns procedures in use" |
|---|---|
Constant | USER_OWNS_PROCEDURES_IN_USE |
SAP Sybase Error Number | 2396 |
SQL State | 42W55 |
SQL Code | -750L |
ODBC 2 State | 40001 |
ODBC 3 State | 40001 |
Severity Code | |
Probable Cause | You attempted to drop a user that owns a procedure being used by other active users of the database. |
| Error 751 | "User owns tables in use" |
|---|---|
Constant | USER_OWNS_TABLES_IN_USE |
SAP Sybase Error Number | 2397 |
SQL State | 42W56 |
SQL Code | -751L |
ODBC 2 State | 40001 |
ODBC 3 State | 40001 |
Severity Code | |
Probable Cause | You attempted to REVOKE CONNECT from a user that owns a table being used by other active users of the database. |
| Error 754 | "Parse error: %1" |
|---|---|
Constant | INVALID_DSN_NAME |
SAP Sybase Error Number | 2400 |
SQL State | 08W54 |
SQL Code | -754L |
ODBC 2 State | 08004 |
ODBC 3 State | 08004 |
Severity Code | |
Parameter 1 | The invalid data source name. |
Probable Cause | An invalid data source name was used in the connection string. |
| Error 755 | "You cannot synchronize or upgrade with uncommitted transactions" |
|---|---|
Constant | UNCOMMITTED_TRANSACTIONS |
SAP Sybase Error Number | 2401 |
SQL State | 0AW08 |
SQL Code | -755L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |
| Error 757 | "Modifications not permitted for read-only database" |
|---|---|
Constant | READ_ONLY_DATABASE |
SAP Sybase Error Number | 2404 |
SQL State | 55W08 |
SQL Code | -757L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted an update operation on a database that was declared as read-only. |
| Error 759 | "SQLDA data type invalid" |
|---|---|
Constant | SQLDA_INVALID_DATATYPE |
SAP Sybase Error Number | 2406 |
SQL State | 07W05 |
SQL Code | -759L |
ODBC 2 State | 07001 |
ODBC 3 State | 07W05 |
Severity Code | |
Probable Cause | The data type specified for a SQLDA variable is invalid. |
| Error 760 | "Invalid SQL identifier" |
|---|---|
Constant | INVALID_SQL_IDENTIFIER |
SAP Sybase Error Number | 2407 |
SQL State | 07W06 |
SQL Code | -760L |
ODBC 2 State | 07001 |
ODBC 3 State | 07W06 |
Severity Code | |
Probable Cause | An invalid identifier was supplied through the C language interface. For example, you may have supplied a NULL string for a cursor name. |
| Error 761 | "Server capability name '%1' could not be found in the database." |
|---|---|
Constant | CAPABILITY_NOT_FOUND |
SAP Sybase Error Number | 2343 |
SQL State | WO014 |
SQL Code | -761L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of server capability. |
Probable Cause | An ALTER SERVER statement was attempted on a capability that was not defined. |