Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
Error 151 | "Subquery allowed only one SELECT list item" |
---|---|
Constant | SUBQUERY_SELECT_LIST |
SAP Sybase Error Number | 2094 |
SQL State | 53023 |
SQL Code | -151L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You entered a subquery that has more than one column in the SELECT list. Change the SELECT list to have only one column. |
Warning 151 | "UltraLite performed database recovery on startup" |
---|---|
Constant | DATABASE_RECOVERED |
SAP Sybase Error Number | 3357 |
SQL State | WW247 |
SQL Code | 151L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | The database file was not shut down cleanly. Any uncommitted rows have been rolled back. This indicates that not all connections were closed when the application terminated. |
Error 152 | "Invalid ORDER BY specification" |
---|---|
Constant | INVALID_ORDER |
SAP Sybase Error Number | 2095 |
SQL State | 53005 |
SQL Code | -152L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | Either you used an integer in an ORDER BY list and the integer is larger than the number of columns in the SELECT list, or you specified an ORDER BY expression that is semantically invalid. For example, for UNION, EXCEPT, and INTERSECT queries you can only use integers or column names of the first SELECT query block to specify an ordering of the result. |
Error 153 | "Select lists in UNION, INTERSECT, or EXCEPT do not match in length" |
---|---|
Constant | INVALID_UNION |
SAP Sybase Error Number | 2096 |
SQL State | 53026 |
SQL Code | -153L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You specified a UNION, INTERSECT, or EXCEPT, but the SELECT statements involved in the operation do not have the same number of columns in the SELECT list. |
Error 154 | "Wrong number of parameters to function '%1'" |
---|---|
Constant | WRONG_PARAMETER_COUNT |
SAP Sybase Error Number | 2100 |
SQL State | 37505 |
SQL Code | -154L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the function. |
Probable Cause | You supplied an incorrect number of parameters to a database function. |
Error 155 | "Invalid host variable" |
---|---|
Constant | VARIABLE_INVALID |
SAP Sybase Error Number | 2102 |
SQL State | 42W07 |
SQL Code | -155L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You supplied an invalid host variable to the database using the C language interface. You may have supplied the variable as a host variable or through a SQLDA. |
Error 156 | "Invalid expression near '%1'" |
---|---|
Constant | EXPRESSION_ERROR |
SAP Sybase Error Number | 2103 |
SQL State | 42W08 |
SQL Code | -156L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The invalid expression. |
Probable Cause | You supplied an expression that the database server cannot understand. For example, you may have tried to add two dates. |
Error 157 | "Cannot convert %1 to a %2" |
---|---|
Constant | CONVERSION_ERROR |
SAP Sybase Error Number | 2104 |
SQL State | 53018 |
SQL Code | -157L |
ODBC 2 State | 07006 |
ODBC 3 State | 07006 |
Severity Code | |
Parameter 1 | The value that could not be converted. |
Parameter 2 | The name of the type for the conversion. |
Probable Cause | An error occurred while trying to convert a value to another data type. |
Error 158 | "Value %1 out of range for destination" |
---|---|
Constant | OVERFLOW_ERROR |
SAP Sybase Error Number | 2105 |
SQL State | 22003 |
SQL Code | -158L |
ODBC 2 State | 22003 |
ODBC 3 State | 22003 |
Severity Code | |
Parameter 1 | The value that caused the overflow. |
Probable Cause | You supplied to or fetched from the database a value that is out of range for the destination column or host variable. For example, the value 10 may have been supplied for a DECIMAL(3,2) field. |
Error 159 | "Invalid column number" |
---|---|
Constant | INVALID_COLUMN_NUMBER |
SAP Sybase Error Number | 2106 |
SQL State | 42W13 |
SQL Code | -159L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You gave an invalid column number, or the column you are looking for is in a different table. |
Error 160 | "Can only describe a SELECT statement" |
---|---|
Constant | DESCRIBE_NONSELECT |
SAP Sybase Error Number | 2107 |
SQL State | 07005 |
SQL Code | -160L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | In the C language interface, you attempted to describe the SELECT list of a statement other than a SELECT statement. In UltraLite this error can result from trying to retrieve the schema of any statement other than a SELECT. |
Error 161 | "Invalid type on DESCRIBE statement" |
---|---|
Constant | INVALID_DESCRIBE_TYPE |
SAP Sybase Error Number | 2108 |
SQL State | 07W01 |
SQL Code | -161L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | A Java type specified on a DESCRIBE statement has no corresponding SQL type. |
Error 162 | "Cannot convert %1 to a %2. The bad value was supplied for column '%3' on row %4 of the data file" |
---|---|
Constant | CONVERSION_ERROR_LOAD_TABLE |
SAP Sybase Error Number | 2533 |
SQL State | 53017 |
SQL Code | -162L |
ODBC 2 State | 07006 |
ODBC 3 State | 07006 |
Severity Code | |
Parameter 1 | Value that could not be converted. |
Parameter 2 | Destination data type. |
Parameter 3 | Name of the column where the value was to be inserted. |
Parameter 4 | Line number of the data file where the invalid data occurred. |
Probable Cause | The data file supplied to LOAD TABLE contains a value that cannot be converted to the required data type. |
Error 163 | "Derived table '%1' has no name for column %2" |
---|---|
Constant | NO_COLUMN_NAME |
SAP Sybase Error Number | 2302 |
SQL State | 52004 |
SQL Code | -163L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the derived table. |
Parameter 2 | Number of the column for which there is no name. |
Probable Cause | The specified column of the derived table has no column name. Use a SELECT list alias in the query specification or use a derived columns specifier. |
Error 164 | "Namespace heap exhausted at internal function: %1" |
---|---|
Constant | NAMESPACE_HEAP_EXHAUSTED |
SAP Sybase Error Number | 2310 |
SQL State | WP007 |
SQL Code | -164L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The internal function is for debugging purposes. |
Probable Cause | The amount of space allocated for the Java Namespace is insufficient to continue loading Java classes. Increase the size by using: SET OPTION PUBLIC.java_namespace_size = nnnnnnnn. |
Error 165 | "Java VM heap exhausted at internal function: %1" |
---|---|
Constant | JAVA_VM_HEAP_EXHAUSTED |
SAP Sybase Error Number | 2311 |
SQL State | WP008 |
SQL Code | -165L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The internal function is for debugging purposes. |
Probable Cause | The amount of space allocated for the Java VM is insufficient to continue allocating new objects. Increase the size by using: SET OPTION PUBLIC.java_heap_size = nnnnnnnn. |
Error 170 | "Cursor has not been declared" |
---|---|
Constant | CURSOR_NOT_DECLARED |
SAP Sybase Error Number | 2109 |
SQL State | 24W01 |
SQL Code | -170L |
ODBC 2 State | 24000 |
ODBC 3 State | 24000 |
Severity Code | |
Probable Cause | You attempted to OPEN a cursor that has not been declared. |
Error 171 | "Error opening cursor" |
---|---|
Constant | OPEN_CURSOR_ERROR |
SAP Sybase Error Number | 2110 |
SQL State | 07003 |
SQL Code | -171L |
ODBC 2 State | 24000 |
ODBC 3 State | 24000 |
Severity Code | |
Probable Cause | You attempted to open a cursor on a statement that is not SELECT, CALL or EXEC. |
Error 172 | "Cursor already open" |
---|---|
Constant | CURSOR_ALREADY_OPEN |
SAP Sybase Error Number | 2111 |
SQL State | 24502 |
SQL Code | -172L |
ODBC 2 State | 24000 |
ODBC 3 State | 24000 |
Severity Code | |
Probable Cause | You attempted to OPEN a cursor that is already open. |
Error 180 | "Cursor not open" |
---|---|
Constant | CURSOR_NOT_OPEN |
SAP Sybase Error Number | 2112 |
SQL State | 24501 |
SQL Code | -180L |
ODBC 2 State | 34000 |
ODBC 3 State | 34000 |
Severity Code | |
Probable Cause | You attempted to use a cursor that has not been opened. |