Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
Error 1009061 | "There must be at least one readwrite dbspace and one relocate dbspace to relocate data. %1" |
---|---|
Constant | EMSG_NOT_OK_TO_RELOCATE |
SAP Sybase Error Number | 20082 |
SQL State | QSA61 |
SQL Code | -1009061L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | Must have at least one RW dbspace and one RR dbspace for sp_iqrelocate |
Error 1009063 | "Cannot alter this dbspace from relocate mode to readonly mode while there are active readwrite transactions that may be using it. %1" |
---|---|
Constant | EMSG_CANNOT_ALTER_RRTORO |
SAP Sybase Error Number | 20084 |
SQL State | QSA63 |
SQL Code | -1009063L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
Error 1009064 | "Cannot create or add file %2 for dbspace %3 until new readwrite space is added to dbspace %4 to hold the new freelist. %1" |
---|---|
Constant | EMSG_SDBEXT_NO_FREELIST_SPACE |
SAP Sybase Error Number | 20085 |
SQL State | QSA64 |
SQL Code | -1009064L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | pathname of file being created |
Parameter 3 | name of dbspace for which file is being created |
Parameter 4 | name of IQ_SYSTEM_MAIN dbspace |
Probable Cause | When creating a new dbspace in the IQ MAIN STORE, or creating a new file for a dbspace other than IQ_SYSTEM_MAIN in the IQ MAIN STORE, there must if sufficient freelist space available to describe the physical blocks we are adding to the database. If this is not the case, the above error occurs. (The space for the freelist can only be allocated in readwrite IQ_SYSTEM_MAIN files.) The corrective action is to first add a new file to the IQ_SYSTEM_MAIN dbspace so that new freelist space becomes available. |
Error 1009065 | "Operation '%2' not allowed in forced recovery. %1" |
---|---|
Constant | EMSG_DBSPACE_NOT_IN_FORCEDRECOVERY |
SAP Sybase Error Number | 20086 |
SQL State | QSA65 |
SQL Code | -1009065L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Dbspace name |
Probable Cause | Certain operations are not permitted in forced recovery |
Error 1009066 | "Cannot execute '%2' yet since previous alter command is not yet propagated through the multiplex. Try again. %1" |
---|---|
Constant | EMSG_CMD_NOT_REPLAYED |
SAP Sybase Error Number | 20087 |
SQL State | QSA66 |
SQL Code | -1009066L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Dbspace name |
Probable Cause | The command cannot be executed since the previous alter/create command has not propagated through multiplex yet. |
Error 1009067 | "%1" |
---|---|
Constant | EMSG_RFU_QSA67 |
SAP Sybase Error Number | 20088 |
SQL State | QSA67 |
SQL Code | -1009067L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
Error 1009068 | "Tried to insert a duplicate entry. %1" |
---|---|
Constant | EMSG_HASHTB_DUPENTRY |
SAP Sybase Error Number | 20089 |
SQL State | QSA68 |
SQL Code | -1009068L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
Error 1009069 | "Could not find key in hashtable" |
---|---|
Constant | EMSG_HASHTB_KEYNOTFOUND |
SAP Sybase Error Number | 20090 |
SQL State | QSA69 |
SQL Code | -1009069L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | No additional information available. |
Error 1009070 | "Hashtable is full" |
---|---|
Constant | EMSG_HASHTB_FULL |
SAP Sybase Error Number | 20091 |
SQL State | QSA70 |
SQL Code | -1009070L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | No additional information available. |
Error 1009071 | "Hash input key descriptor has zero fields (%2, %3). %1" |
---|---|
Constant | EMSG_PHASH_NOKEY |
SAP Sybase Error Number | 20092 |
SQL State | QSA71 |
SQL Code | -1009071L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) major context (hos_StatsObj::SubStatementId, usually dfo number) |
Parameter 3 | 3) minor context (s_phash::StatMinorContext, see s_phash.h for enum) |
Probable Cause | No additional information available. |
Error 1009072 | "Insufficient buffers for hash. (%2, %3). %1" |
---|---|
Constant | EMSG_PHASH_MAXBUFFERS |
SAP Sybase Error Number | 20093 |
SQL State | QSA72 |
SQL Code | -1009072L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) major context (hos_StatsObj::SubStatementId, usually dfo number) |
Parameter 3 | 3) minor context (s_phash::StatMinorContext, see s_phash.h for enum) |
Probable Cause | Specifically, the number of estimated buffers given to the hash object exceeds the size of the buffer cache. |
Error 1009073 | "Hash function can't handle this datatype (%2, %3). %1" |
---|---|
Constant | EMSG_PHASH_HASHDT |
SAP Sybase Error Number | 20094 |
SQL State | QSA73 |
SQL Code | -1009073L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) major context (hos_StatsObj::SubStatementId, usually dfo number) |
Parameter 3 | 3) minor context (s_phash::StatMinorContext, see s_phash.h for enum) |
Probable Cause | No additional information available. |
Error 1009074 | "Key length in hash equality function is zero (%2, %3). %1 " |
---|---|
Constant | EMSG_PHASH_EQUALKEYLEN |
SAP Sybase Error Number | 20095 |
SQL State | QSA74 |
SQL Code | -1009074L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) major context (hos_StatsObj::SubStatementId, usually dfo number) |
Parameter 3 | 3) minor context (s_phash::StatMinorContext, see s_phash.h for enum) |
Probable Cause | No additional information available. |
Error 1009075 | "Buffer mapper init incorrect (%2, %3). %1" |
---|---|
Constant | EMSG_PHASH_BUFMAPINIT |
SAP Sybase Error Number | 20096 |
SQL State | QSA75 |
SQL Code | -1009075L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) major context (hos_StatsObj::SubStatementId, usually dfo number) |
Parameter 3 | 3) minor context (s_phash::StatMinorContext, see s_phash.h for enum) |
Probable Cause | No additional information available. |
Error 1009076 | "Internal hash error; buffer was previously created: %2 (%3, %4). %1" |
---|---|
Constant | EMSG_PHASH_BUFDOUBLECREATE |
SAP Sybase Error Number | 20097 |
SQL State | QSA76 |
SQL Code | -1009076L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) Buffer Number. |
Parameter 3 | 3) major context (hos_StatsObj::SubStatementId, usually dfo number) |
Parameter 4 | 4) minor context (s_phash::StatMinorContext, see s_phash.h for enum) |
Probable Cause | No additional information available. |
Error 1009077 | "Internal hash error; next data entry should be valid (%2, %3). %1" |
---|---|
Constant | EMSG_PHASH_INVALID_NEXTENTRY |
SAP Sybase Error Number | 20098 |
SQL State | QSA77 |
SQL Code | -1009077L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) major context (hos_StatsObj::SubStatementId, usually dfo number) |
Parameter 3 | 3) minor context (s_phash::StatMinorContext, see s_phash.h for enum) |
Probable Cause | No additional information available. |
Error 1009078 | "Internal hash error; buffer not pinned (%2, %3). %1" |
---|---|
Constant | EMSG_PHASH_NOT_PINNED |
SAP Sybase Error Number | 20099 |
SQL State | QSA78 |
SQL Code | -1009078L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) major context (hos_StatsObj::SubStatementId, usually dfo number) |
Parameter 3 | 3) minor context (s_phash::StatMinorContext, see s_phash.h for enum) |
Probable Cause | No additional information available. |
Error 1009079 | "Internal hash error; too many buffers left in use: %2 (%3, %4). %1" |
---|---|
Constant | EMSG_PHASH_INUSE_HIGH |
SAP Sybase Error Number | 20100 |
SQL State | QSA79 |
SQL Code | -1009079L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) Number of buffers. |
Parameter 3 | 3) major context (hos_StatsObj::SubStatementId, usually dfo number) |
Parameter 4 | 4) minor context (s_phash::StatMinorContext, see s_phash.h for enum) |
Probable Cause | No additional information available. |
Error 1009080 | "Key doesn't fit on a single database page: %2 (%3, %4). %1" |
---|---|
Constant | EMSG_PHASH_KEY_TOO_LARGE |
SAP Sybase Error Number | 20101 |
SQL State | QSA80 |
SQL Code | -1009080L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) Key size. |
Parameter 3 | 3) major context (hos_StatsObj::SubStatementId, usually dfo number) |
Parameter 4 | 4) minor context (s_phash::StatMinorContext, see s_phash.h for enum) |
Probable Cause | No additional information available. |
Error 1009081 | "Data doesn't fit on a single database page: %2 (%3, %4). %1" |
---|---|
Constant | EMSG_PHASH_DATA_TOO_LARGE |
SAP Sybase Error Number | 20102 |
SQL State | QSA81 |
SQL Code | -1009081L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) Data size. |
Parameter 3 | 3) major context (hos_StatsObj::SubStatementId, usually dfo number) |
Parameter 4 | 4) minor context (s_phash::StatMinorContext, see s_phash.h for enum) |
Probable Cause | No additional information available. |