Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
Error 1000215 | "An invalid filler option (e.g., filler()) was specified in the load statement. %1" |
---|---|
Constant | EMSG_INVALID_FILLER_OPTION |
SAP Sybase Error Number | 20875 |
SQL State | QDC15 |
SQL Code | -1000215L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | An invalid filler option was specified on the load statement. |
Warning 1000216 | No message |
---|---|
Constant | EMSG_JOIN_EJP1ADD_EMPTY_SLOT |
SAP Sybase Error Number | 20876 |
SQL State | 01C16 |
SQL Code | 1000216L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | No additional information available. |
Warning 1000217 | No message |
---|---|
Constant | EMSG_JOIN_EJP1STARTRECID_EMPTY_SLOT |
SAP Sybase Error Number | 20877 |
SQL State | 01C17 |
SQL Code | 1000217L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | No additional information available. |
Warning 1000218 | "Join virtual table fetches (JP1%1) complete for '%2'." |
---|---|
Constant | EMSG_JOIN_EJP12DONE |
SAP Sybase Error Number | 20878 |
SQL State | 01C18 |
SQL Code | 1000218L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Parameter 1 description |
Parameter 2 | Parameter 2 description |
Probable Cause | This is an informational message displayed in context with other messages. |
Error 1000219 | "The specified indextype does not exist in the given target. %1" |
---|---|
Constant | EMSG_DBCC_INDEXTYPE_NOT_FOUND |
SAP Sybase Error Number | 20879 |
SQL State | QDC19 |
SQL Code | -1000219L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Probable Cause | The indextype the user requested to check with sp_iqcheckdb does not exist in the given table or database. |
Warning 1000220 | " Left Rows: %1, Right Rows: %2, Ratio: %3 to %4\n" |
---|---|
Constant | EMSG_JOIN_EJP12CNTS |
SAP Sybase Error Number | 20880 |
SQL State | 01C20 |
SQL Code | 1000220L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Parameter 1 description |
Parameter 2 | Parameter 2 description |
Parameter 3 | Parameter 3 description |
Parameter 4 | Parameter 4 description |
Probable Cause | This is an informational message displayed in context with other messages. |
Warning 1000221 | " Right Rows Skipped: %1 (former left outers).\n" |
---|---|
Constant | EMSG_JOIN_EJP12SKIPS |
SAP Sybase Error Number | 20881 |
SQL State | 01C21 |
SQL Code | 1000221L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Parameter 1 description |
Probable Cause | This is an informational message displayed in context with other messages. |
Error 1000222 | "JP3&4" |
---|---|
Constant | EMSG_JOIN_ESORT34 |
SAP Sybase Error Number | 20882 |
SQL State | QDC22 |
SQL Code | -1000222L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | This is an informational message displayed in context with other messages. |
Error 1000223 | "Column name '%2' is invalid. The column name must follow the format [OWNER.]TABLE.COLUMN. %1" |
---|---|
Constant | EMSG_INVALID_COLUMN_NAME |
SAP Sybase Error Number | 20883 |
SQL State | QDC23 |
SQL Code | -1000223L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Parameter 2 | The name of the column typed by the user. |
Probable Cause | The column name must follow the format [OWNER.]TABLE.COLUMN. |
Warning 1000224 | "Join record rejected: '%1', duplicate rows in 1st indexset. \nRow# %2 & %3X, row %4 rejected." |
---|---|
Constant | EMSG_CLBK_JOINIDXRECORDREJECTEDX |
SAP Sybase Error Number | 20884 |
SQL State | 01C24 |
SQL Code | 1000224L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Parameter 1 description |
Parameter 2 | Parameter 2 description |
Parameter 3 | Parameter 3 description |
Parameter 4 | Parameter 4 description |
Probable Cause | This is an informational message displayed in context with other messages. |
Error 1000225 | "Cannot open table %2. The table has already been opened by a cursor declared FOR UPDATE in transaction %3. %1" |
---|---|
Constant | EMSG_CAT_CANNOT_OPEN_TABLE |
SAP Sybase Error Number | 20885 |
SQL State | QDC25 |
SQL Code | -1000225L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Parameter 2 | Tablename. |
Parameter 3 | The id of the transaction during which the cursor was opened. |
Probable Cause | A table opened by a CURSOR that has been declared FOR UPDATE cannot be opened again by another operation. |
Warning 1000226 | "\n Inner Rows: %1, Left Outer Rows: %2, Right Outer Rows: %3" |
---|---|
Constant | EMSG_JOIN_EJP3CNT1 |
SAP Sybase Error Number | 20886 |
SQL State | 01C26 |
SQL Code | 1000226L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Parameter 1 description |
Parameter 2 | Parameter 2 description |
Parameter 3 | Parameter 3 description |
Probable Cause | This is an informational message displayed in context with other messages. |
Error 1000226 | "The LOCATION string passed to the attached database insert is invalid. %1" |
---|---|
Constant | EMSG_INVALIDLOCATION |
SAP Sybase Error Number | 20996 |
SQL State | QDC36 |
SQL Code | -1000226L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | The user passed an invalid LOCATION string in an attached database insert. Check the format of the string. It must be of the form "servername.dbname". |
Warning 1000227 | " Join Rows: %1, Left m2m Rows: %2, Right m2m Rows: %3\n" |
---|---|
Constant | EMSG_JOIN_EJP3CNT2 |
SAP Sybase Error Number | 20887 |
SQL State | 01C27 |
SQL Code | 1000227L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Parameter 1 description |
Parameter 2 | Parameter 2 description |
Parameter 3 | Parameter 3 description |
Probable Cause | This is an informational message displayed in context with other messages. |
Error 1000227 | "Cannot load data with both BINARY and delimited columns. %1" |
---|---|
Constant | EMSG_LOADBINARYDELIMITED |
SAP Sybase Error Number | 20997 |
SQL State | QDC37 |
SQL Code | -1000227L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | You cannot load data with both BINARY and delimited columns in the same LOAD command. |
Error 1000228 | "JP4&5" |
---|---|
Constant | EMSG_JOIN_ESORT45 |
SAP Sybase Error Number | 20888 |
SQL State | QDC28 |
SQL Code | -1000228L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | This is an informational message displayed in context with other messages. |
Error 1000229 | "Only BINARY [WITH NULL BYTE] can be used as a column specification when using UNLOAD FORMAT. %1" |
---|---|
Constant | EMSG_CANTUSEINLOAD |
SAP Sybase Error Number | 20998 |
SQL State | QDC38 |
SQL Code | -1000229L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | When using UNLOAD FORMAT, you cannot specify any column specification other than BINARY. If need to load null values for a column using the BINARY column spec, you must specify the WITH NULL BYTE option. You cannot use the [ROW] DELIMITED BY options with UNLOAD FORMAT. |
Warning 1000230 | "\nInsert for '%1',\n completed in %2 seconds." |
---|---|
Constant | EMSG_DELETE_INSERTDONE |
SAP Sybase Error Number | 20890 |
SQL State | 01C30 |
SQL Code | 1000230L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Parameter 1 description |
Parameter 2 | Parameter 2 description |
Probable Cause | This is an informational message displayed in context with other messages. |
Error 1000230 | "Columns that allow nulls must use the WITH NULL BYTE option. %1" |
---|---|
Constant | EMSG_MUSTUSENULLBYTE |
SAP Sybase Error Number | 20999 |
SQL State | QDC39 |
SQL Code | -1000230L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | The user must use the WITH NULL BYTE option for a BINARY column spec for columns that allow nulls. |
Error 1000232 | "Partial input record skipped at EOF. %1" |
---|---|
Constant | EMSG_PARTIAL_INPUT_ROW |
SAP Sybase Error Number | 20892 |
SQL State | QDC32 |
SQL Code | -1000232L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | A partial input record was detected during a 'load' operation. This can occur as a result of an OS/hardware error or simply because the input data file was missing values for one or more columns in the table. |