Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Warning 1009122 | " %1 Sort: Merged %2 runs, %3 Secs, %4 runs remaining" |
|---|---|
Constant | EMSG_SORT_INFOMERGED |
SAP Sybase Error Number | 20143 |
SQL State | QSB22 |
SQL Code | 1009122L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | What is being sorted. |
Parameter 2 | How many merged. |
Parameter 3 | Time taken. |
Parameter 4 | How many runs still requiring to be merged. |
Probable Cause | No additional information available. |
| Error 1009123 | "Database Segment %2 is not valid. Missing DBSignature. This Segment can not be used. %1" |
|---|---|
Constant | EMSG_SDBEXT_BAD_DBSIGNATURE |
SAP Sybase Error Number | 20144 |
SQL State | QSB23 |
SQL Code | -1009123L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Probable Cause | No additional information available. |
| Error 1009124 | "Database Segment %2, blocksize %3 does not match catalog blocksize of %4. This Segment can not be used. %1" |
|---|---|
Constant | EMSG_SDBEXT_DIF_BLOCKSIZE |
SAP Sybase Error Number | 20145 |
SQL State | QSB24 |
SQL Code | -1009124L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Parameter 3 | Block size. |
Parameter 4 | Catalog Block size. |
Probable Cause | No additional information available. |
| Error 1009125 | "Database Segment %2, maxcompression %3 does not match catalog maxcompression of %4. This Segment can not be used. %1" |
|---|---|
Constant | EMSG_SDBEXT_DIF_MAXCOMPRESSION |
SAP Sybase Error Number | 20146 |
SQL State | QSB25 |
SQL Code | -1009125L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Parameter 3 | Max compression |
Parameter 4 | Catalog max compression. |
Probable Cause | No additional information available. |
| Error 1009126 | "Database Segment %2, createtime does not match catalog. This Segment can not be used. %1" |
|---|---|
Constant | EMSG_SDBEXT_DIF_CREATETIME |
SAP Sybase Error Number | 20147 |
SQL State | QSB26 |
SQL Code | -1009126L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Probable Cause | No additional information available. |
| Error 1009127 | "Database Segment %2, %3 size does not match catalog size of %4. This Segment can not be used. %1" |
|---|---|
Constant | EMSG_SDBEXT_DIF_NBLOCKS |
SAP Sybase Error Number | 20148 |
SQL State | QSB27 |
SQL Code | -1009127L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Parameter 3 | Size of segment. |
Parameter 4 | Catalog size of segment. |
Probable Cause | No additional information available. |
| Error 1009128 | "The IQ_SYSTEM_TEMP dbspace does not have dbfiles for this server. %1" |
|---|---|
Constant | EMSG_SDBEXT_NOFREELIST |
SAP Sybase Error Number | 20149 |
SQL State | QSB28 |
SQL Code | -1009128L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
| Error 1009129 | "Database Segment %2, secondary server can not find a valid header. This segment can not be used. %1" |
|---|---|
Constant | EMSG_SDBEXT_QSERVER_FAIL |
SAP Sybase Error Number | 20150 |
SQL State | QSB29 |
SQL Code | -1009129L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Probable Cause | No additional information available. |
| Error 1009130 | "Database %2, does not have a segment for catalogfileid %3. %1" |
|---|---|
Constant | EMSG_SDBEXT_MISSING_CATALOGFILEID |
SAP Sybase Error Number | 20151 |
SQL State | QSB30 |
SQL Code | -1009130L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Database segment. |
Parameter 2 | Max compression |
Parameter 3 | Catalog max compression. |
Probable Cause | No additional information available. |
| Warning 1009131 | "You have run out of %1 dbspace in database %2. In another session, please issue a CREATE DBSPACE ... %3 command and add a dbspace of at least %4 MB." |
|---|---|
Constant | EMSG_IQSTORE_OUTOFDISK_HEADER |
SAP Sybase Error Number | 20152 |
SQL State | QSB31 |
SQL Code | 1009131L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | string IQ STORE or IQ TEMPORARY STORE |
Parameter 2 | database name |
Parameter 3 | string IQ STORE or IQ TEMPORARY STORE |
Parameter 4 | the minimum number of megabytes to add |
Probable Cause | You have run out of DBSPACE in the named database. In order to continue, you must add another DBSPACE to the database unless space becomes available from another connection. |
| Warning 1009132 | "The DBA has added %1 %2 dbspaces to database %3. Sybase IQ (TM) is no longer waiting for more dbspace." |
|---|---|
Constant | EMSG_IQSTORE_OUTOFDISK_TRAILER |
SAP Sybase Error Number | 20153 |
SQL State | QSB32 |
SQL Code | 1009132L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | explanation for arg %2 delete if no %1 |
Parameter 2 | explanation for arg %3 delete if no %2 |
Parameter 3 | explanation for %3 |
Probable Cause | No additional information available. |
| Error 1009133 | "You have run out of space during the CHECKPOINT operation. %1" |
|---|---|
Constant | EMSG_IQSTORE_OUTOFSPACE_CHECKPOINT |
SAP Sybase Error Number | 20982 |
SQL State | QSB33 |
SQL Code | -1009133L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | The checkpoint operation in progress needs to allocate blocks so that it can construct and save required checkpoint information. When space is exhausted during a checkpoint operation, it is not possible to add more space via a CREATE DBSPACE command. Consequently, the checkpoint operation will fail. |
| Error 1009134 | "Insufficient buffers for '%2'. %1" |
|---|---|
Constant | EMSG_SORT_MINBUFSAVAIL |
SAP Sybase Error Number | 21023 |
SQL State | QSB34 |
SQL Code | -1009134L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | clientType |
Probable Cause | No additional information available. |
| Error 1009135 | "Cannot perform requested command as there is a CREATE DBSPACE command in progress. %1" |
|---|---|
Constant | EMSG_IQSTORE_INCREATEDBSPACE |
SAP Sybase Error Number | 21034 |
SQL State | QSB36 |
SQL Code | -1009135L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | A CREATE DBSPACE or a DROP DBSPACE command was issued when there was already a DROP DBSPACE command in progress. |
| Error 1009136 | "Cannot perform requested command as there is a DROP DBSPACE command in progress. %1" |
|---|---|
Constant | EMSG_IQSTORE_INDROPDBSPACE |
SAP Sybase Error Number | 21035 |
SQL State | QSB37 |
SQL Code | -1009136L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | A CREATE DBSPACE or a DROP DBSPACE command was issued when there was already an ALTER DBSPACE command in progress. |
| Error 1009137 | "Cannot perform DDL command now on table %2 as a DDL command is already in progress on that table. %1" |
|---|---|
Constant | EMSG_DDLINPROGRESS |
SAP Sybase Error Number | 21036 |
SQL State | QDC55 |
SQL Code | -1009137L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Parameter 1 description |
Parameter 2 | location of the exception |
Probable Cause | There is already a DDL command in progress at the moment on the table specified and you must wait until it is finished before starting another DDL command on that table. |
| Error 1009139 | "Cannot perform requested command as there is a CHECKPOINT command in progress. %1" |
|---|---|
Constant | EMSG_IQSTORE_INCHECKPOINT |
SAP Sybase Error Number | 21038 |
SQL State | QSB38 |
SQL Code | -1009139L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | A CREATE DBSPACE or a DROP DBSPACE command was issued when there was already a CHECKPOINT command in progress. |
| Error 1009140 | "Cannot restore dbspace '%2' to raw partition '%3' because its size is smaller than the size of the original raw partition (%4 vs. %5 blocks). %1" |
|---|---|
Constant | EMSG_RESTORE_RAW_PARTITION_SIZE_MISMATCH |
SAP Sybase Error Number | 21039 |
SQL State | QCA49 |
SQL Code | -1009140L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | name of the IQ dbspace being restored |
Parameter 3 | raw partition to which the IQ dbspace is being restored |
Parameter 4 | size of the new raw partition |
Parameter 5 | size of the old raw partition |
Probable Cause | This error means that the user is attempting to restore an IQ dbspace on a raw partition that is not the same size as the original raw partition on which the IQ dbspace existed at the time of the backup. The user must resize the raw partition and then retry the restore operation. |
| Error 1009141 | "Table '%2' cannot be found in the IQ store. %1" |
|---|---|
Constant | EMSG_SQL_IQTABLENOTFOUND |
SAP Sybase Error Number | 21061 |
SQL State | QCA51 |
SQL Code | -1009141L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | table name |
Probable Cause | The stored procedure sp_iqtablesize cannot find the table. This stored procedure is for IQ tables only. It cannot be run against system tables or ASA tables. |
| Warning 1009142 | " %1 SortMerge0: %2 records, PhaseI=%3 Secs, %4 runs total, %5 pgs=%6 M, runlen=%7, %8 est. phases" |
|---|---|
Constant | EMSG_SORT_INFOMERGED0 |
SAP Sybase Error Number | 21067 |
SQL State | QSB39 |
SQL Code | 1009142L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | What is being sorted. |
Parameter 2 | How many records are being sorted. |
Parameter 3 | Time taken in Phase I. |
Parameter 4 | How many runs to be merged. |
Parameter 5 | How many pages of data to be sorted. |
Parameter 6 | How many Mbytes of data to be sorted. |
Parameter 7 | Average number of pages in a run. |
Parameter 8 | Estimated number of merge phases. |
Probable Cause | This information is provided after the Phase I radix sorting is complete and the Phase II merge-sorting is about to begin. Each run consists of a sequence of pages that have been radix sorted in Phase I. These runs are merged together in Phase II to finish the sort. |