Error Codes

The following table lists the error codes used in ActiveSpaces:

ActiveSpaces relies on TIBCO FTL internally. TIBCO FTL generates error codes ranging between -1 and 5000. For information about TIBCO FTL error codes, see TIBCO FTL Error Codes.

 
Error Code Error Key Cause Solution
-1 TIB_NULL_EXCEPTION The program has supplied a NULL value instead of an exception object.  
0 TIB_OK

The TIBCO FTL call completed successfully.

  
1 TIB_INVALID_ARG An invalid value has been embedded as an argument.  
2 TIB_NO_MEMORY An application could not allocate sufficient memory to process an operation.  
4 TIB_TIMEOUT Internal timeout elapsed. In many cases, the library attempts to retry most operations but stops once the client’s timeout period is reached. An application might retry the function a certain number of times before taking some other course of action.
5 TIB_NOT_INITIALIZED The program has not yet called tib_Open to start TIBCO FTL or the grid is offline. In most cases, the application must retry an operation, maybe with a brief delay, some number of times until the grid is online again.
6 TIB_OS_ERROR An operating system call has failed.  
7 TIB_INTR An internal interruption has occurred in a thread.  
8 TIB_NOT_PERMITTED An invalid operation has occurred on a valid object. You do not have permission to perform the operation. To perform the operation, get permission either directly or through a group to which you belong.
9 TIB_NOT_FOUND

A client has requested a value that is not in the database.
10 TIB_ILLEGAL_STATE The action has been inconsistent with the internal state.  
11 TIB_NOT_SUPPORTED The data type or feature is not supported.  
12 TIB_END_OF_BUFFER Reached the end of the buffer when parsing an inbound message.  
13 TIB_VERSION_MISMATCH Incompatible versions of TIBCO FTL components.  
14 TIB_ALREADY_EXISTS There has been a conflict with an existing object, value, or definition.  
15 TIB_FILE_IO_ERROR I/O error occurred when accessing shared memory or when accessing the file system.  
16 TIB_INVALID_VALUE TIBCO FTL internal error has occurred due to one of the following malformed artifacts: message, packet, or realm definition.  
17 TIB_INVALID_TYPE

There has been a mismatch between field and data type.

  
18 TIB_INVALID_CONFIG

The property values have been invalid or

contradictory.

  
19 TIB_INVALID_FORMAT The FTL client library has encountered a message with an invalid format.  
20 TIB_CLIENT_SHUTDOWN The program has attempted an operation on an unusable realm object.  
21 TIB_RESOURCE_UNAVAILABLE A resource required by the client program was unavailable.  
22 TIB_LIMIT_REACHED A resource could not accept data because it had reached a specified upper limit.  
23 TIB_FORMAT_UNAVAILABLE A format required by the client program was unavailable.  
100 TIB_EXCEPTION An unclassified exception occurred.  
101 TIB_UNKNOWN_SYSPROP The client has detected a corrupted message during reassembly.  
5000 TIBDG_INVALID_BIN_EPOCH

The error could have occurred after a successful redistribution when a stale operation was sent to the old node, which previously owned the row but no longer has the ownership. Retry the operation again so that it goes to the new owner.

  
5002 TIBDG_INVALID_RESOURCE

This error code is returned when a specific resource is to be recreated. If a Prepared Statement exists before redistributing a grid, subsequent ExecuteQuery() calls might fail.

 In this case, the Prepared Statement must be closed and recreated before running any more ExecuteQuery() commands.
5003 TIBDG_GRID_IN_MAINTENANCE

An invalid operation has been submitted in maintenance mode.

This error code is returned when a client submits any operation that modifies the data on a disk while the grid is in maintenance mode.

 The application must retry the operation until the grid is no longer in maintenance mode and the operation succeeds.
  TIB_INVALID_ARG One of the arguments provided to the function is not valid. Call the function again with the same or different arguments.

SQL Error Codes

Error Code Error Key Cause Solution
5100 TIBDG_SQL_SYNTAX_ERROR An error is detected in the syntax of a SQL statement. Correct the SQL statement before submitting it again.
5101 TIBDG_SQL_NOT_SUPPORTED The string containing a SQL statement has included the syntax of an unsupported feature. Correct the SQL statement before submitting it again.
5102 TIBDG_SQL_INVALID_VALUE The string containing an SQL statement has included syntax that cannot be used in a particular scenario. Correct the SQL statement before submitting it again.
5103 TIBDG_SQL_PARSER_ERROR An unexpected error has occurred during the parsing of a SQL statement. Correct the SQL statement before submitting it again.
5104 TIBDG_SQL_STMT_ERROR An unexpected error has occurred during the processing of a SQL statement. The statement should be resubmitted as the statement is most likely valid.
5105 TIBDG_SQL_SYSTEM_ERROR An unexpected SQL system error occurred during the processing of a query. The statement should be resubmitted as the statement is most likely valid.
5106 TIBDG_SQL_QUERY_ERROR An unexpected error occurred during the processing of a query by a tibdgnode. The statement should be resubmitted as the statement is most likely valid.
5107 TIBDG_SQL_DDL_CMD_ERROR An unexpected error occurred during the processing of a table or index DDL command in the data grid. The statement should be resubmitted as the statement is most likely valid.
5108 TIBDG_SQL_QUERY_CMD_ERROR An unexpected error occurred during the processing of a query by the node. Correct the SQL statement before submitting it again.
5109 TIBDG_SQL_DML_CMD_ERROR An unexpected error occurred during the processing of an INSERT or UPDATE command in the data grid. Correct the SQL statement before submitting it again.
5110 TIBDG_SQL_CMD_ERROR A generic SQL command error occurred during the processing of a SQL command in the data grid. Running the command again might result in it being successfully processed. Correct the SQL statement before submitting it again.
5111 TIBDG_SQL_NOT_PERMITTED A SQL statement tried to perform an action that is not permitted by the data grid. Running the command again is unlikely to be successful. Correct the SQL statement before submitting it again.
  TIBDG_SQL_BAD_BATCH This error code is returned when a batch of SQL commands could not be successfully processed due to one or more bad commands in the batch. When this happens, the entire batch of commands is rolled back.
  TIBDG_SQL_RESOURCE_UNAVAILABLE when a SQL command could not be successfully processed due to a resource needed by the command being unavailable. Running the command again might result in it being successfully processed.