Messages 1000222 through 1000235

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
-1000222L Error 20882 QDC22 "JP3&4" This is an informational message displayed in context with other messages.

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

-1000223L Error 20883 QDC23 "Column name '%2' is invalid. The column name must follow the format [OWNER.]TABLE.COLUMN. %1" The column name must follow the format [OWNER.]TABLE.COLUMN.

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

1000224L Warning 20884 01C24 "Join record rejected: '%1', duplicate rows in 1st indexset. \nRow# %2 & %3X, row %4 rejected." This is an informational message displayed in context with other messages.

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

-1000225L Error 20885 QDC25 "Cannot open table %2. The table has already been opened by a cursor declared FOR UPDATE in transaction %3. %1" A table opened by a CURSOR that has been declared FOR UPDATE cannot be opened again by another operation.

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

1000226L Warning 20886 01C26 "\n Inner Rows: %1, Left Outer Rows: %2, Right Outer Rows: %3" This is an informational message displayed in context with other messages.

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

-1000226L Error 20996 QDC36 "The LOCATION string passed to the attached database insert is invalid. %1" 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".

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

1000227L Warning 20887 01C27 " Join Rows: %1, Left m2m Rows: %2, Right m2m Rows: %3\n" This is an informational message displayed in context with other messages.

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

-1000227L Error 20997 QDC37 "Cannot load data with both BINARY and delimited columns. %1" You cannot load data with both BINARY and delimited columns in the same LOAD command.

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

-1000228L Error 20888 QDC28 "JP4&5" This is an informational message displayed in context with other messages.

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

1000229L Warning 20889 01C29 "%1 records were inserted and %2 records were rejected for %3 tables \nfor join index '%4'.\n" This is an informational message displayed in context with other messages.

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

-1000229L Error 20998 QDC38 "Only BINARY [WITH NULL BYTE] can be used as a column specification when using UNLOAD FORMAT. %1" 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.

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

1000230L Warning 20890 01C30 "\nInsert for '%1',\n completed in %2 seconds." This is an informational message displayed in context with other messages.

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

-1000230L Error 20999 QDC39 "Columns that allow nulls must use the WITH NULL BYTE option. %1" The user must use the WITH NULL BYTE option for a BINARY column spec for columns that allow nulls.

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

-1000231L Error 20891 QDC31 "You do not have permission to create join index %2%3%4. %1" A user can only create a join index under the following conditions 1) They are the DBA account 2) They have DBA authority. 3) They did not specify a creator and have RESOURCE authority 4) The specified creator is the same as the current user and they have RESOURCE authority.

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

-1000232L Error 20892 QDC32 "Partial input record skipped at EOF. %1" 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.

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

-1000233L Error 20893 QDC33 "Cannot SYNCHRONIZE join index %2. %1" The requested SYNCHRONIZE operation for the named join index failed because not all read-write locks could be obtained for all tables and related joins/tables in the join indexes' transitive closure. Try the SYNCHRONIZE operation later when there are no access conflicts with other users.

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

1000234L Warning 20894 01C34 "\nInsert into table '%1', %2 rows rejected (in all)." This is an informational message displayed in context with other messages. During the LOAD, some records were rejected.

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

-1000234L Error 21000 QDC40 "The record size of the unloaded data: %2, does not match the record size of the load: %3. %1" The record size of the unloaded data does not match the size of the record described by the LOAD command.

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

1000235L Warning 20895 00C35 "%3 Pass %1 completed in %2 seconds." This is an informational message displayed in context with other messages.

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

-1000235L Error 21001 QDC42 "The total number of columns of unloaded data: %2, does not match the total number of columns in the load: %3. %1" The total number of columns in the unloaded data does not match the number of columns in the LOAD command.

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


Created June 15, 2009. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com