Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
Error 1004005 | "Timeout period should be multiple of the Heartbeat Frequency" |
---|---|
Constant | EMSG_INVALIDTIMEOUTPERIOD2 |
SAP Sybase Error Number | 20216 |
SQL State | QIA05 |
SQL Code | -1004005L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | All the timeout periods of INC(e.g.,AUTOEXCLUDE,LIVENESS,IDLE_CONNECTION) requires to be multiple of the Heartbeat Frequency. |
Error 1004006 | "Unused Connection Pool size should be always less than the Maximum Connection Pool size" |
---|---|
Constant | EMSG_INVALIDUNUSEDPOOLSIZE |
SAP Sybase Error Number | 20217 |
SQL State | QIA06 |
SQL Code | -1004006L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Unused Connection pool size can not be greater can not be greater than the maximum allowable size of the Connection pool |
Error 1004007 | "Unable to acquire a pooled connection to the coordinator node" |
---|---|
Constant | EMSG_INC_NOPOOLEDCONNECTION |
SAP Sybase Error Number | 20218 |
SQL State | QIA07 |
SQL Code | -1004007L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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 |
Error 1004008 | "Coordinator node is offline" |
---|---|
Constant | EMSG_INC_NODE_OFFLINE |
SAP Sybase Error Number | 20219 |
SQL State | QIA08 |
SQL Code | -1004008L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Coordinator node is offline and hence, all the suspended commands on the suspended connections will be terminated |
Error 1004009 | "INC communication failure %1" |
---|---|
Constant | EMSG_INC_CONN_INTERNAL_ERROR |
SAP Sybase Error Number | 20220 |
SQL State | QIA09 |
SQL Code | -1004009L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of exception |
Probable Cause | 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 |
Error 1004010 | "Error in getting current user information" |
---|---|
Constant | EMSG_INC_NOUSERFOUND |
SAP Sybase Error Number | 20221 |
SQL State | QIA10 |
SQL Code | -1004010L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Error returned while trying to find out the current user connected to the given node |
Error 1004011 | "Coordinator node not responding" |
---|---|
Constant | EMSG_INC_NODE_NOT_ALIVE |
SAP Sybase Error Number | 21222 |
SQL State | QIA11 |
SQL Code | -1004011L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Coordinator node is not responding. Check to see if the Coordinator is running |
Error 1004012 | "INC communication between coordinator and secondary failed due to : %2 %1" |
---|---|
Constant | EMSG_INC_CONN_ERROR |
SAP Sybase Error Number | 21223 |
SQL State | QIA12 |
SQL Code | -1004012L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of exception |
Parameter 2 | Error message returned from target server |
Probable Cause | 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. |
Error 1004013 | "Cannot drop multiplex server %2 as it holds freelist. %1" |
---|---|
Constant | EMSG_MPX_CANNOT_DROP_HOLDS_FREELIST |
SAP Sybase Error Number | 21224 |
SQL State | QDD08 |
SQL Code | -1004013L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception |
Parameter 2 | Multiplex Server Name |
Probable Cause | If a writer holds a freelist, it cannot be dropped. If the writer can be started, start it. This is because a startup or a clean shutdown will clear the freelist. If the writer cannot be restarted, restart the coordinator with -iqmpx_reclaimwriterfreelist <server name> server switch to force the coordinator to reset the writer freelist. |
Error 1004014 | "Trying to execute an unknown SQL type over the INC connection" |
---|---|
Constant | EMSG_INC_CONN_UNKNOWN_STMT |
SAP Sybase Error Number | 20225 |
SQL State | QIA14 |
SQL Code | -1004014L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The node is trying to execute an unknown SQL over the dblib connections |
Error 1004015 | "Permission denied: Command not allowed on Multiplex %2 servers. %1" |
---|---|
Constant | EMSG_MPX_CMD_PERMISSION_LEVEL_DENIED |
SAP Sybase Error Number | 21225 |
SQL State | QIA15 |
SQL Code | -1004015L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception |
Parameter 2 | Role of current node |
Probable Cause | The command is not permitted on current multiplex node |
Warning 1004060 | "Warning: Heartbeat frequency should be less than or equal to other timeout periods" |
---|---|
Constant | EMSG_INVALIDHEARTBEATFREQUENCY1 |
SAP Sybase Error Number | 20211 |
SQL State | 01A60 |
SQL Code | 1004060L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | The heartbeat frequency should always be less than or equal to other timeout period. This is to make sure that the time lag between the timeout occurring and the time when it is detected is minimal. |
Warning 1004061 | "Warning: All INC timeout periods should be multiple of Heartbeat frequency" |
---|---|
Constant | EMSG_INVALIDHEARTBEATFREQUENCY2 |
SAP Sybase Error Number | 20213 |
SQL State | QIA61 |
SQL Code | 1004061L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | All the timeout periods of INC(e.g.,AUTOEXCLUDE,LIVENESS,IDLE_CONNECTION) requires to be multiple of the Heartbeat Frequency. |
Error 1005000 | "Bind parameters are not supported in data flow query processing" |
---|---|
Constant | EMSG_BINDPARAMETERS_UNSUPPORTED |
SAP Sybase Error Number | 20154 |
SQL State | QTA00 |
SQL Code | -1005000L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | No additional information available. |
Error 1005001 | "Query has exceeded the supported maximum number of tables that can be joined. %1" |
---|---|
Constant | EMSG_TOO_MANY_TABLES_TO_JOIN |
SAP Sybase Error Number | 20155 |
SQL State | QTA01 |
SQL Code | -1005001L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
Error 1005002 | "Subquery predicates are not supported in the ON clause of outer joins in this release. %1" |
---|---|
Constant | EMSG_NO_SUBQ_PREDS_IN_OUTER_JOINS |
SAP Sybase Error Number | 20156 |
SQL State | QTA02 |
SQL Code | -1005002L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
Error 1005003 | "A maximum of one subquery predicate per conjunct is supported in this release. %1" |
---|---|
Constant | EMSG_ONLY_ONE_SUBQ_PER_CONJUNCT |
SAP Sybase Error Number | 20157 |
SQL State | QTA03 |
SQL Code | -1005003L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
Error 1005004 | "Subqueries are allowed only as arguments of comparisons, IN, and EXISTS %2, %1" |
---|---|
Constant | EMSG_ILLEGAL_SUBQUERY_USAGE |
SAP Sybase Error Number | 20158 |
SQL State | QTA04 |
SQL Code | -1005004L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | SA code line |
Probable Cause | No additional information available. |
Error 1005005 | "Deleting from views is not supported. %1" |
---|---|
Constant | EMSG_NO_UPDATABLE_VIEWS |
SAP Sybase Error Number | 20159 |
SQL State | QTA05 |
SQL Code | -1005005L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
Error 1005006 | "The target DELETE table must also appear in FROM. %1" |
---|---|
Constant | EMSG_ILLEGAL_FROMCLAUSE_FOR_DELETE |
SAP Sybase Error Number | 20160 |
SQL State | QTA06 |
SQL Code | -1005006L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |