Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1008025 | "Multiplex secondary server cannot continue while the coordinator is in single server mode. %1" |
|---|---|
Constant | EMSG_IQMPX_SPXONLY |
SAP Sybase Error Number | 21047 |
SQL State | QNA25 |
SQL Code | -1008025L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | Resynchronize and restart the secondary server after the coordinator has restarted in normal mode. |
| Error 1008026 | "Multiplex secondary server out of synchronization with the coordinator. %1" |
|---|---|
Constant | EMSG_IQMPX_CATSYNC |
SAP Sybase Error Number | 21048 |
SQL State | QNA26 |
SQL Code | -1008026L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | The secondary server's IQ catalog cannot be brought up to date with the coordinator's IQ catalog. This server must be synchronized. |
| Error 1008027 | "Multiplex secondary node shutting down due to a file added to the IQ_SYSTEM_MAIN dbspace.\nThis node must be synchronized and restarted. %1" |
|---|---|
Constant | EMSG_IQMPX_SEGCOUNT |
SAP Sybase Error Number | 21057 |
SQL State | QNA28 |
SQL Code | -1008027L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | The user has added a dbspace file to IQ_SYSTEM_MAIN on the coordinator. This causes secondary nodes to shut down. All secondary nodes must be synchronized and restarted after this operation. |
| Error 1008029 | "Cannot create foreign key to an unenforced primary key or unenforced unique constraint." |
|---|---|
Constant | EMSG_NOFKEY_TO_UNENFORCED |
SAP Sybase Error Number | 21059 |
SQL State | QNA29 |
SQL Code | -1008029L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Existing unenforced primary keys or unique constraints cannot be used to create an referential integrity relationship to a foreign table. |
| Error 1008030 | "Only IQ index types can be created on IQ tables within a Parallel IQ block." |
|---|---|
Constant | EMSG_SQL_PLBEGINONLYCI |
SAP Sybase Error Number | 21064 |
SQL State | QNA30 |
SQL Code | -1008030L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Parallel IQ Begin/End blocks allow users to create multiple indexes simultaneously. At this time, only Create Index statements for HG, HNG, LF, LD, DATE, TIME, WD, and CMP index types on IQ tables are allowed within Parallel IQ Begin and End statements. |
| Error 1008031 | "Cannot do Create Index commands on global or local temporary tables or catalog server tables in a Parallel IQ block." |
|---|---|
Constant | EMSG_SQL_NOTEMPINPLB |
SAP Sybase Error Number | 21065 |
SQL State | QNA31 |
SQL Code | -1008031L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Cannot do Create Index commands on global or local temporary tables in a Parallel IQ block. |
| Error 1008032 | "Foreign keys disallowed on Identity/Autoincrement Columns when set option identity_enforce_uniqueness is on" |
|---|---|
Constant | EMSG_FOREIGN_KEY_DISALLOWED |
SAP Sybase Error Number | 20026 |
SQL State | QNA41 |
SQL Code | -1008032L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | An Identity/Autoincrement Column cannot be a foreign key when the set option identity_enforce_uniqueness is on. Either turn the option off, or chose a different column for the foreign key. |
| Error 1008033 | "Identity/Autoincrement Column %2 has Invalid datatype: scale must be 0. %1" |
|---|---|
Constant | EMSG_NON_ZERO_SCALE |
SAP Sybase Error Number | 20027 |
SQL State | QNA42 |
SQL Code | -1008033L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | column name |
Probable Cause | Identity/Autoincrement Columns defined as datatype numeric must have scale 0 |
| Error 1008035 | "Invalid datatype for Identity/Autoincrement Column %2. %1" |
|---|---|
Constant | EMSG_INVALID_DATATYPE |
SAP Sybase Error Number | 20029 |
SQL State | QNA44 |
SQL Code | -1008035L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | column name |
Probable Cause | The datatype used is not supported by Identity/Autoincrement column. Valid datatypes are bigint, unsigned bigint, integer, unsigned integer, smallint, tinyint, numeric scale 0 and decimal scale 0 |
| Error 1008036 | "Table %2 already has an Identity/Autoincrement Column. %1 " |
|---|---|
Constant | EMSG_ALREADY_HAS_IDENTITY_COLUMN |
SAP Sybase Error Number | 20642 |
SQL State | QNA45 |
SQL Code | -1008036L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Table name |
Probable Cause | An Identity/Autoincrement Column cannot be added to this table because it already has one. |
| Error 1008037 | "Cannot drop %1 %2: set option 'identity_insert' must be off. " |
|---|---|
Constant | EMSG_IDENTITY_INSERT_IS_ON |
SAP Sybase Error Number | 20643 |
SQL State | QNA46 |
SQL Code | -1008037L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | string literal 'Table' or 'Column' |
Parameter 2 | column name |
Probable Cause | option 'identity insert' must not be set to any table name to drop an Identity Column. To turn it off use 'set identity_insert '' ' |
| Error 1008038 | "create schema command not allowed on an active multiplex server. " |
|---|---|
Constant | EMSG_NOSCHEMACMD_MULTIPLEX |
SAP Sybase Error Number | 21123 |
SQL State | QNA47 |
SQL Code | -1008038L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | the create schema command is not allowed on an active multiplex server |
| Error 1008039 | "Permission denied: The current multiplex server is not a writer server" |
|---|---|
Constant | EMSG_MPX_GLOBAL_CMD_PERMISSION_DENIED |
SAP Sybase Error Number | 22005 |
SQL State | QNA48 |
SQL Code | -1008039L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The global command is not permitted on current multiplex node |
| Error 1009000 | "Bit %2 is unexpectedly on in bitmap. If the error persists, you may have a damaged index; please run sp_iqcheckdb. %1" |
|---|---|
Constant | EMSG_BM_BITON |
SAP Sybase Error Number | 20021 |
SQL State | QSA00 |
SQL Code | -1009000L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Bit that is on. |
Probable Cause | This is either an internal calling error (some component called bitmap SET with a duplicate bit), a corrupt bitmap (and dbcc needs be run), or a bitmap operator that has gone awry and mis-computed a result. |
| Error 1009001 | "Bit %2 is unexpectedly off in bitmap. If the error persists, you may have a damaged index; please run sp_iqcheckdb. %1" |
|---|---|
Constant | EMSG_BM_BITOFF |
SAP Sybase Error Number | 20022 |
SQL State | QSA01 |
SQL Code | -1009001L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Bit that is off. |
Probable Cause | This is either an internal calling error (some component called bitmap CLEAR with a duplicate bit), a corrupt bitmap (and dbcc needs be run), or a bitmap operator that has gone awry and mis-computed a result. |
| Warning 1009002 | " Index %2: Starting Insert Pass 2. %1" |
|---|---|
Constant | EMSG_HG_STARTING_PASS2 |
SAP Sybase Error Number | 20023 |
SQL State | 00002 |
SQL Code | 1009002L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Index name |
Probable Cause | No additional information available. |
| Warning 1009003 | " Index %1: Thread %2 Inserting %3 Recs, %4 Secs." |
|---|---|
Constant | EMSG_HG_INSERTED |
SAP Sybase Error Number | 20024 |
SQL State | 00003 |
SQL Code | 1009003L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | Index name |
Parameter 2 | Thread index |
Parameter 3 | Number of records |
Parameter 4 | Time |
Probable Cause | No additional information available. |
| Error 1009004 | "Statistics context = %2 %3\n %1" |
|---|---|
Constant | EMSG_STATS_CONTEXT |
SAP Sybase Error Number | 20025 |
SQL State | QSA04 |
SQL Code | -1009004L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | majContext |
Parameter 3 | minContext |
Probable Cause | No additional information available. |
| Error 1009012 | "Cannot create %2 index on a column having a datatype %3. %1" |
|---|---|
Constant | EMSG_ERROR_INDEX_NOTALLOWED |
SAP Sybase Error Number | 20033 |
SQL State | QSA12 |
SQL Code | -1009012L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | the index type (e.g., LF, HG) |
Parameter 3 | textual name of the column's datatype |
Probable Cause | A named index type index cannot be created on named datatype |
| Error 1009019 | "An internal server component, a bitmap, was given invalid input. %1" |
|---|---|
Constant | EMSG_BM_BADINPUT |
SAP Sybase Error Number | 20040 |
SQL State | QSA19 |
SQL Code | -1009019L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | Some non-bitmap component has called a bitmap with an illegal argument. This is an internal programming error and not the (direct) result of customer error. |