Messages 1008021 through 1009001

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
-1008021L Error 21043 QNA21 "The SYSIQFILE table is not configured for this server to run in a multiplex." SYSIQFILE identifies all files which make up the given stores that the IQ server requires (main, temp, and message). For multiplex, each entry in SYSIQFILE must be associated with a particular multiplex server before that server can access the particular file. This message indicates that some these rows are missing for the active server.

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

-1008022L Error 21044 QNA22 "Bad commit identity block. The server may be out of synchronization. %1" Multiplex servers cannot start this database. Start the coordinator in single server mode.

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

-1008023L Error 21045 QNA23 "Cannot start multiplex secondary server while the coordinator is in single server mode" Restart the secondary server after the coordinator has restarted in normal mode.

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

-1008024L Error 21046 QNA24 "Multiplex coordinator must start as server@host: %2, on file: %3; to start with different settings, you must use the override switch. %1" Only the configured coordinator can start the database. Start with the override switch (-iqmpx_ov 1) to bypass this check.

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

-1008025L Error 21047 QNA25 "Multiplex secondary server cannot continue while the coordinator is in single server mode. %1" Resynchronize and restart the secondary server after the coordinator has restarted in normal mode.

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

-1008026L Error 21048 QNA26 "Multiplex secondary server out of synchronization with the coordinator. %1" The secondary server's IQ catalog cannot be brought up to date with the coordinator's IQ catalog. This server must be synchronized.

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

-1008027L Error 21057 QNA28 "Multiplex secondary node shutting down due to a file added to the IQ_SYSTEM_MAIN dbspace.\nThis node must be synchronized and restarted. %1" 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.

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

-1008029L Error 21059 QNA29 "Cannot create foreign key to an unenforced primary key or unenforced unique constraint." Existing unenforced primary keys or unique constraints cannot be used to create an referential integrity relationship to a foreign table.

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

-1008030L Error 21064 QNA30 "Only IQ index types can be created on IQ tables within a Parallel IQ block." 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.

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

-1008031L Error 21065 QNA31 "Cannot do Create Index commands on global or local temporary tables or catalog server tables in a Parallel IQ block." Cannot do Create Index commands on global or local temporary tables in a Parallel IQ block.

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

-1008032L Error 20026 QNA41 "Foreign keys disallowed on Identity/Autoincrement Columns when set option identity_enforce_uniqueness is on" 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.

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

-1008033L Error 20027 QNA42 "Identity/Autoincrement Column %1 has Invalid datatype: scale must be 0." Identity/Autoincrement Columns defined as datatype numeric must have scale 0

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

-1008034L Error 20028 QNA43 "Cannot add an Identity/Autoincrement Column to table %1, it participates in a join index." Adding an Identity/Autoincrement Column to a table that participates in a join index is not allowed, to perform this operation, the join index must be dropped

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

-1008035L Error 20029 QNA44 "Invalid datatype for Identity/Autoincrement Column %1." 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

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

-1008036L Error 20642 QNA45 "Table %1 already has an Identity/Autoincrement Column. " An Identity/Autoincrement Column cannot be added to this table because it already has one.

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

-1008037L Error 20643 QNA46 "Cannot drop %1 %2: set option 'identity_insert' must be off. " option 'identity insert' must not be set to any table name to drop an Identity Column. To turn it off use 'set identity_insert '' '

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

-1008038L Error 21123 QNA47 "create schema command not allowed on an active multiplex server. " the create schema command is not allowed on an active multiplex server

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

-1008039L Error 22005 QNA48 "Permission denied: The current multiplex server is not a writer server" The global command is not permitted on current multiplex node

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

-1009000L Error 20021 QSA00 "Bit %2 is unexpectedly on in bitmap. If the error persists, you may have a damaged index; please run sp_iqcheckdb. %1" 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.

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

-1009001L Error 20022 QSA01 "Bit %2 is unexpectedly off in bitmap. If the error persists, you may have a damaged index; please run sp_iqcheckdb. %1" 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.

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


Created May 6, 2011. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com