Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Warning 1009143 | " %1 SortMergePass: Merged %2 runs, %3 Secs, %4 runs remaining, %5 reads = %6 M, runlen=%7, phase %8, %9 M on disk" |
|---|---|
Constant | EMSG_SORT_INFOMERGED1 |
SAP Sybase Error Number | 21068 |
SQL State | QSB40 |
SQL Code | 1009143L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | What is being sorted. |
Parameter 2 | How many runs were merged in this merge pass.. |
Parameter 3 | Time taken in this merge pass. |
Parameter 4 | How many runs still to be merged. |
Parameter 5 | How many page reads done in this pass. |
Parameter 6 | How many Mbytes of data read in this pass. |
Parameter 7 | Average length of runs in pages, this pass. |
Parameter 8 | Fractional phase number reached. |
Parameter 9 | How many Mbytes of data physically read in this pass. |
Probable Cause | This information is provided after each merge pass. One merge pass merges a certain number of runs, using one pinned buffer page per run plus one pinned buffer for the output run. Note that there can be several passes in a merge phase. One merge phase reads all the sort data and produces a new set of runs that provide input to the next phase. |
| Warning 1009144 | " %1 SortMergeDone: Ave mem %2 M, %3 Secs, %4 passes, %5 reads, %6 M data= %7 pgs, %8 phases, %9 M on disk" |
|---|---|
Constant | EMSG_SORT_INFOMERGED2 |
SAP Sybase Error Number | 21069 |
SQL State | QSB41 |
SQL Code | 1009144L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | What is being sorted. |
Parameter 2 | Time-average number of pinned page buffers used by Phase II of the sort. |
Parameter 3 | Time taken for Phase II of the sort. |
Parameter 4 | Total number of passes in Phase II. |
Parameter 5 | Total number of page reads in Phase II. |
Parameter 6 | Total Mbytes of data sorted. |
Parameter 7 | Total number of pages of data sorted. |
Parameter 8 | Number of merge phases in the merge sort of Phase II. |
Parameter 9 | Total Mbytes of physical reads in Phase II. |
Probable Cause | This information is provided at the end of Phase II to summarize the resource usage of the whole merge sort. The last pass of the sort is separately reported on by an EMSG_SORT_INFOMERGED1 message. |
| Error 1009145 | "Data exception - data type conversion is not possible. %2, %1" |
|---|---|
Constant | EMSG_TYPECONVERSION_W_ARG |
SAP Sybase Error Number | 21070 |
SQL State | QFA2E |
SQL Code | -1009145L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Exception line number |
Parameter 2 | SA parse source code line |
Probable Cause | No additional information available. |
| Error 1009146 | "Cannot perform requested command as there is a DBCC command in progress. %1" |
|---|---|
Constant | EMSG_IQSTORE_INDBCC |
SAP Sybase Error Number | 21071 |
SQL State | QSB42 |
SQL Code | -1009146L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | A CHECKPOINT command was issued when there was already a DBCC command in progress. |
| Warning 1009147 | "Space has become available in the %1 store of database %2. Sybase IQ (TM) is no longer waiting for more dbspace." |
|---|---|
Constant | EMSG_IQSTORE_OUTOFDISK_SPACEAVAILABLE |
SAP Sybase Error Number | 20188 |
SQL State | QSB43 |
SQL Code | 1009147L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | string IQ STORE or IQ TEMPORARY STORE |
Parameter 2 | Database Name |
Probable Cause | No additional information available. |
| Error 1009148 | "Cannot use -iqfrec to start a multiplex secondary server. %1" |
|---|---|
Constant | EMSG_IQSTORE_NOFREC |
SAP Sybase Error Number | 21049 |
SQL State | QSB44 |
SQL Code | -1009148L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | A sp_iqcheckdb procedure call was issued on an IQ multiplex secondary server, or it was started in drop-leaks or forced recovery mode. These operations are only allowed on the coordinator |
| Error 1009149 | "%2 Internal Inconsistency: %1 (%3,%4,%5)" |
|---|---|
Constant | EMSG_INDEXCONTAINER_CORRUPT |
SAP Sybase Error Number | 20189 |
SQL State | QSB45 |
SQL Code | -1009149L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Container type |
Parameter 3 | Internal Error Code |
Parameter 4 | Internal Error Info 1 |
Parameter 5 | Internal Error Info 2 |
Probable Cause | A corrupt index container was found. DBCC cannot repair the container. The database object using the container must be re-created. |
| Error 1009150 | "Cannot delete/truncate CK %2 because of RI violation - FK has non-nulls. %1" |
|---|---|
Constant | EMSG_RI_VIOLATION_FKNOTNULL |
SAP Sybase Error Number | 20190 |
SQL State | QSB46 |
SQL Code | -1009150L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Parameter 2 | index name of candidate key |
Probable Cause | No additional information available. Cannot truncate or delete all from candidate table if there exists any associated foreign key which has any all non-null data. |
| Error 1009151 | "Cannot %2 CK %3 row %4 because of RI violation. %1" |
|---|---|
Constant | EMSG_RI_VIOLATION_CK |
SAP Sybase Error Number | 20191 |
SQL State | QSB47 |
SQL Code | -1009151L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Parameter 2 | operation: update or delete |
Parameter 3 | index name for CK |
Parameter 4 | row id that violated RI |
Probable Cause | No additional information available. Cannot delete/update CK if there exists same value in associated FK. any associated foreign key which has any all non-null data. |
| Error 1009152 | "Cannot %2 FK %3 row %4 because of RI violation. %1" |
|---|---|
Constant | EMSG_RI_VIOLATION_FK |
SAP Sybase Error Number | 20192 |
SQL State | QSB48 |
SQL Code | -1009152L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Parameter 2 | operation: update or insert/load |
Parameter 3 | role name for FK |
Parameter 4 | row id that violated RI |
Probable Cause | No additional information available. Cannot insert/update FK if there does not exist same value in associated CK any associated foreign key which has any all non-null data. |
| Error 1009153 | "Cannot remove row %3 from CK %2 during LOAD cleanup because of RI violation. %1" |
|---|---|
Constant | EMSG_RI_VIOLATION_LOADCLEANUP |
SAP Sybase Error Number | 20193 |
SQL State | QSB49 |
SQL Code | -1009153L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of exception |
Parameter 2 | index name for CK |
Parameter 3 | row id that violated RI |
Probable Cause | No additional information available. If removing self-referential CK during LOAD cleanup phase and there exists a FK of removed value, we roll back the whole operation. |
| Error 1009154 | "Cannot alter dbspace when a backup is in progress" |
|---|---|
Constant | EMSG_IQSTORE_CANNOT_ALTERDBSPACE |
SAP Sybase Error Number | 21118 |
SQL State | QSB50 |
SQL Code | -1009154L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | An alter dbspace operation was attempted while a backup was running. The alter dbspace operation cannot proceed since it may modify internal database structures that are being backed up. |
| Error 1009155 | "Cannot perform requested command as there is an ALTER DBSPACE command in progress. %1" |
|---|---|
Constant | EMSG_IQSTORE_INALTERDBSPACE |
SAP Sybase Error Number | 22000 |
SQL State | QSB55 |
SQL Code | -1009155L |
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 1009156 | "Drop disallowed for dbspace %2. One or more of the file(s) are in use by the database. %1" |
|---|---|
Constant | EMSG_SDBEXT_DROPSEGMENTINUSE |
SAP Sybase Error Number | 20194 |
SQL State | QSB51 |
SQL Code | -1009156L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Probable Cause | A segment must contain no user data and no database structures to drop |
| Error 1009157 | "There is insufficient reserve space to add %3 blocks to segment %2. Only %4 blocks or less may be added. %1" |
|---|---|
Constant | EMSG_SDBEXT_SEGMENTNORESERVE |
SAP Sybase Error Number | 20195 |
SQL State | QSB52 |
SQL Code | -1009157L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Parameter 3 | Number of blocks user attempted to add |
Parameter 4 | Maximum blocks that may be added |
Probable Cause | Since a segment must use a contiguous range of block numbers, it can only be resized larger when the blocks following it are not in use by the next segment. |
| Error 1009158 | "Cannot resize segment %2 since the truncated region is in use. %1" |
|---|---|
Constant | EMSG_SDBEXT_RESIZESEGMENTINUSE |
SAP Sybase Error Number | 20196 |
SQL State | QSB53 |
SQL Code | -1009158L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Probable Cause | A segment can only be resized smaller when no blocks in the truncated are in use. |
| Error 1009159 | "The status specified for segment %2 is unchanged. %1" |
|---|---|
Constant | EMSG_SDBEXT_SEGMENTSAMERWMODE |
SAP Sybase Error Number | 20197 |
SQL State | QSB54 |
SQL Code | -1009159L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Probable Cause | The "alter dbspace status" syntax requires the new status to be different than the original status. |
| Error 1009160 | "There must be at least one readwrite dbspace (%2). %1" |
|---|---|
Constant | EMSG_SDBEXT_MUST_HAVE_RW |
SAP Sybase Error Number | 20198 |
SQL State | QSB56 |
SQL Code | -1009160L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Probable Cause | There must at least one readwrite segment |
| Error 1009161 | "Cannot resize segment %2 since it is readonly. %1" |
|---|---|
Constant | EMSG_SDBEXT_RO_RESIZE |
SAP Sybase Error Number | 20199 |
SQL State | QSB57 |
SQL Code | -1009161L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Probable Cause | A readonly segment cannot be resized |
| Error 1009162 | "Insufficient space to relocate structures on %2. %1" |
|---|---|
Constant | EMSG_SDBEXT_NO_RELOCATE_SPACE |
SAP Sybase Error Number | 20200 |
SQL State | QSB58 |
SQL Code | -1009162L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Probable Cause | Database structures may need to be relocated in order to drop a segment or make it readonly. This space must be available on other segments. |