Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| QHA13 | Error | 20185 | -1003013L | No message | No additional information available. Click here for a list of possible parameters and odbc states. |
| QHA14 | Error | 20186 | -1003014L | No message | No additional information available. Click here for a list of possible parameters and odbc states. |
| QIA00 | Error | 20209 | -1004000L | "The number of connections in the connection pool have exceeded the upper limit" | The number of connections in the connection pool have exceeded the total number of connections allowed in the connection pool. No more connections can be allocated. Click here for a list of possible parameters and odbc states. |
| QIA01 | Error | 20210 | -1004001L | "Number of unused connections exceeded the maximum number of unused connections in the connection pool" | The number of unused connections in the connection pool has exceeded the maximum number of unused connections in the connection pool. Click here for a list of possible parameters and odbc states. |
| QIA03 | Error | 20212 | -1004003L | "Timeout period should be greater than or equal to the heartbeat frequency" | All the timeout periods should be greater than or equal to the heartbeat frequency. Click here for a list of possible parameters and odbc states. |
| QIA04 | Error | 20215 | -1004004L | "No connection found for the server id %1 on the coordinator" | A secondary node with the given server id does not exist on the coordinator connection list Click here for a list of possible parameters and odbc states. |
| QIA05 | Error | 20216 | -1004005L | "Timeout period should be multiple of the Heartbeat Frequency" | All the timeout periods of INC(e.g.,AUTOEXCLUDE,LIVENESS,IDLE_CONNECTION) requires to be multiple of the Heartbeat Frequency. Click here for a list of possible parameters and odbc states. |
| QIA06 | Error | 20217 | -1004006L | "Unused Connection Pool size should be always less than the Maximum Connection Pool size" | Unused Connection pool size can not be greater can not be greater than the maximum allowable size of the Connection pool Click here for a list of possible parameters and odbc states. |
| QIA07 | Error | 20218 | -1004007L | "Unable to acquire a pooled connection to the coordinator node" | There are no empty pooled connections on the secondary node and also no new connections can be established because the total number of connections has exceeded the maximum capacity of the connection pool Click here for a list of possible parameters and odbc states. |
| QIA08 | Error | 20219 | -1004008L | "Coordinator node is offline" | Coordinator node is offline and hence, all the suspended commands on the suspended connections will be terminated Click here for a list of possible parameters and odbc states. |
| QIA09 | Error | 20220 | -1004009L | "INC communication failure %1" | INC communication failure. This can happen if either the coordinator or the secondary node is restarted or shutdown down when the other node is trying to connect to it Click here for a list of possible parameters and odbc states. |
| QIA10 | Error | 20221 | -1004010L | "Error in getting current user information" | Error returned while trying to find out the current user connected to the given node Click here for a list of possible parameters and odbc states. |
| QIA11 | Error | 21222 | -1004011L | "Coordinator node not responding" | Coordinator node is not responding. Check to see if the Coordinator is running Click here for a list of possible parameters and odbc states. |
| QIA12 | Error | 21223 | -1004012L | "INC communication between coordinator and secondary failed due to : %2 %1" | INC communication failed between coordinator and secondary nodes. The error returned from target node is also displayed. This connection is similar to a client connection. Click here for a list of possible parameters and odbc states. |
| QIA14 | Error | 20225 | -1004014L | "Trying to execute an unknown SQL type over the INC connection" | The node is trying to execute an unknown SQL over the dblib connections Click here for a list of possible parameters and odbc states. |
| QIA15 | Error | 21225 | -1004015L | "Permission denied: Command not allowed on Multiplex %2 servers. %1" | The command is not permitted on current multiplex node Click here for a list of possible parameters and odbc states. |
| QIA61 | Warning | 20213 | 1004061L | "Warning: All INC timeout periods should be multiple of Heartbeat frequency" | All the timeout periods of INC(e.g.,AUTOEXCLUDE,LIVENESS,IDLE_CONNECTION) requires to be multiple of the Heartbeat Frequency. Click here for a list of possible parameters and odbc states. |
| QNA00 | Error | 20596 | -1008000L | "Users are not allowed to create an FP index. FP indexes are created automatically when the table is created." | Users are not able to create Fast Projection indexes on columns. They are created automatically when the table is created. Click here for a list of possible parameters and odbc states. |
| QNA01 | Error | 20621 | -1008001L | "The user cannot create indexes on a join virtual table." | Users cannot create indexes on a join virtual table. They are automatically created. Click here for a list of possible parameters and odbc states. |
| QNA02 | Error | 20623 | -1008002L | "There is a join index using table '%1'. The table cannot be dropped until the join index is dropped or altered." | There is at least one join index using this table in a join relationship. The table cannot be dropped until the join index is dropped or it is altered such that it no longer uses this table. Click here for a list of possible parameters and odbc states. |