Appendix A Error Codes
Table A.1 Database Integration Service Errors and Warnings lists the native error and warning messages that may be logged by the Database Integration Service daemon. While some of these messages may actually provide enough information by themselves to help users fix the problem, many have to be used along with other data to help with debugging the issue.
Often several of these messages will be logged for a single problem. A failure at a lower layer will cause log messages to be printed at various levels of the Database Integration Service daemon logic. These messages will be valuable to you and to RTI support engineers in debugging issues with Database Integration Service.
|
Code |
Message |
Details |
|
0 - 1023 Database Integration Service daemon errors |
||
|
0 |
Unexpected error |
Should never occur. Contact support@rti.com if seen. |
|
1 |
<message> |
General error. |
|
2 |
Error storing RTI DDS sample in table '<table>' |
There was an error when storing value received with Connext into the database. |
|
3 |
Error creating <entity> |
|
|
4 |
Error creating <entity> associated to the table '<table>' |
|
|
5 |
Error getting <entity> |
|
|
6 |
<meta-table> entry not valid |
There was an entry in a meta-table (RTIDDS_PUBLICATIONS or RTIRTCSUBSCRIPTIONS) that was not valid. |
|
7 |
Error creating '<type>' SQL statement |
There was an error when creating or preparing a SQL statement. |
|
8 |
Error creating table '<table>' |
|
|
9 |
Error opening RTI DDS connection |
There was a problem initializing Connext. |
|
10 |
The type of the column '<column>' is not valid |
The meta-columns RTIDDS_DOMAIN_ID and RTIRTC_REMOTE must be added to tables that the user creates and wished to connect to via Database Integration Service. They will be automatically if the Database Integration Service daemon creates the table. If the user creates the table and adds the two columns, they must be of type INTEGER. This message is produced if these columns exist and are of the wrong type. |
|
11 |
Error publishing record/instance |
The Database Integration Service daemon had a problem publishing a table change as a Topic. |
|
12 |
Error disposing record/instance |
The Database Integration Service daemon had a problem disposing of an instance of Topic when the user deleted a row in a table. |
|
13 |
Error initializing <module> module |
The Database Integration Service daemon had problems initializing an internal code module. |
|
14 |
The definition of environment variable '%s' is required |
|
|
15 |
Error opening the database connection associated to the DSN '<DSN>' |
|
|
16 |
Error enabling database log |
|
|
17 |
<string> too long (maximum length: <length>) |
|
|
18 |
Error creating connection to database log |
|
|
19 |
The value of the column 'column' in the table '<meta-table>' is not valid |
|
|
20 |
Error generating '<type>' SQL statement string Error generating SQL statement string |
The Database Integration Service daemon had a problem in generating the string for preparing or executing a SQL statement. |
|
21 |
Error skipping parameter for the field '<column>' |
|
|
22 |
Error binding parameter for the column '<column>' Error binding parameters |
|
|
23 |
The column '<column>' has an unexpected SQL Type |
Supported SQL types are: |
|
24 |
Error opening configuration file ’filename’ |
|
|
25 |
Error reading configuration file ’filename’ |
|
|
26 |
Error parsing configuration file ’filename’ |
|
|
27 |
The maximum length for a <type> field is <length> |
|
|
28 |
Error serializing record |
A problem occurred when serializing a table row for publishing as a Topic. |
|
29 |
Error deserializing RTI DDS sample |
A problem occurred when deserializing data received via Connext for storing into a table. |
|
30 |
Error creating key cache |
Could not create cache of known instance keys see 4.5.2.1.7 cache_maximum_size, cache_initial_size. |
|
31 |
Error inserting key in cache |
Problem occurred while storing instance key in cache see 4.5.2.1.7 cache_maximum_size, cache_initial_size. |
|
32 |
Null pointer argument |
A precondition failed in which a NULL pointer was passed to an internal daemon function. |
|
33 |
Error reading table '<table>' |
|
|
34 |
The resolution column '<column>' does not exist in the table '<table>' |
The RTIDDS_PUBLICATIONS table contained an entry in the ’resolution_column’ which does not match the name of an existing column in the corresponding table. See 4.5.1.1.6 resolution_column. |
|
35 |
The type of the resolution column '<column>' in the table '<table>' is not valid. The type of the resolution column can be: SQL_INTEGER, SQL_SMALLINT, SQL_BIGINT and SQL_TIMESTAMP |
A column specified in the column ’resolution_column’ in the RTIDDS_PUBLICATIONS table is not of an acceptable type. See 4.5.1.1.6 resolution_column. |
|
36 |
Error gathering instance information |
Error gathering Connext instance information through the execution of the associated SELECT statement |
|
37 |
Invalid metatable schema |
The schema of the metatables is not valid. It is possible that those tables were created with a previous version of Database Integration Service. |
|
38 |
Error deleting key from cache |
|
|
39 |
Error deleting a row from '<table>' |
There was a problem deleting a row from a user data table. |
|
41 |
Error creating publication/subscription for the '<table>' without primary key. |
The user tried to create a publication/subscription for a table without a primary key. |
|
43 |
Key not supported |
Non-primitive IDL keys are not supported. When Database Integration Service tries to create a table with complex keys, it will report this error message. Example with supported keys: struct SupportedKeysSt {string id_str; //@key long id_long; //@key short id_short; //@key }; Example with unsupported keys: struct KeySt {long id_long; } struct NonSupportedKeysSt {KeySt id_st; //@key } |
|
44 |
Error creating subscriber state queue |
|
|
45 |
Error updating subscription state |
|
|
46 |
Error creating '<object>' |
|
|
47 |
Path too long |
The path to the configuration file is too long. |
|
48 |
Error creating database publication cache |
The Database Integration Service daemon had a problem creating the publication database cache. |
|
49 |
Error adding record to publication cache |
The Database Integration Service daemon had a problem adding a new record to the publication database cache. |
|
50 |
Column name length exceeds maximum length |
The maximum length of a column name in Database Integration Service is 30 characters. To control the length of a column name, use the configuration tags <idl_member_prefix_max_length> and <idl_member_suffix_max_length> under <database_mapping_options>. See 4.4.4.2 Database Mapping Options. |
|
1024 - 2047 Connext-related errors |
||
|
1024 |
<message> |
General Connext error message. |
|
1025 |
Error getting <entity> default QoS |
|
|
1026 |
Error getting <entity> QoS |
|
|
1027 |
Error setting <entity> QoS |
|
|
1028 |
Error creating <entity> |
|
|
1029 |
Error getting <entity> |
|
|
1030 |
Error enabling <entity> |
|
|
1031 |
Error cloning type code |
|
|
1032 |
Error reading RTI DDS samples |
|
|
1033 |
Error setting <entity> user data |
|
|
1034 |
Error disposing RTI DDS instance |
|
|
1035 |
Error unregistering RTI DDS instance |
|
|
1036 |
Error writing RTI DDS sample |
|
|
1037 |
Error ignoring <entity> |
|
|
1038 |
Error creating <waitset type> waitset |
|
|
1039 |
Error waiting in <waitset type> waitset |
|
|
1040 |
Error getting builtin transport property |
|
|
1041 |
Error setting builtin transport property |
|
|
1042 |
Error creating <waitset type> guard condition |
|
|
1043 |
Error attaching condition |
|
|
1044 |
Error registering type '<type>' |
|
|
1045 |
Error taking REDA buffer |
|
|
1046 |
Error creating mutex |
|
|
1047 |
Error creating <thread> thread |
|
|
1048 |
Error creating REDA fast buffer |
|
|
1049 |
Error taking semaphore |
|
|
1050 |
Error giving semaphore |
|
|
1051 |
Error creating worker factory |
|
|
1052 |
Error creating worker |
|
|
1053 |
Error creating clock |
|
|
1054 |
Error creating event manager |
|
|
1055 |
Error creating timer |
|
|
1056 |
Error posting event |
|
|
1057 |
Error getting time |
|
|
1058 |
Error creating semaphore |
|
|
1059 |
Error loading DDS XML Profile |
|
|
1060 |
Error getting TypeCode |
|
|
1061 |
Error cloning TypeCode |
|
|
1062 |
Error parsing TypeCode |
|
|
1063 |
Error creating TypeCode |
|
|
2048 - 4095 ODBC-related errors |
||
|
2048 |
<message> <message>: <ODBC driver error message> |
General ODBC error message. |
|
4096 - 8191 DBMS Log Connection-related errors |
||
|
4096 |
<message> |
General DBMS log connection error message. |
|
8192 - 16383 OS-related errors |
||
|
8192 |
<message> |
General OS error message. |
|
8193 |
Error handling OS signals |
|
|
8194 |
Unable to set signal handler for <signal> |
|
|
8195 |
Error getting the host name |
|
|
8196 |
Error allocating memory for <object> |
|
|
16384+ Warning messages |
||
|
16384 |
Timestamps prior to '1970-01-01 00:00:00.00' cannot be used for conflict resolution. The Database Integration Service daemon will always use '1970-01-01 00:00:00,00' as the timestamp for those cases |
|
|
16385 |
The Timestamp value of the resolution column is NULL. The Database Integration Service daemon will use the value '1970-01-01 00:00:00,00'. |
|
|
16387 |
IDL member identifier collision |
The prefix/suffix-based name associated with member A in IDL type T collides with the name of another member inside the same type. Database Integration Service will resolve the conflict using an index. |
|
16388 |
Invalid configuration parameter |
|
|
16389 |
Ignored QoS value |
A QoS value has been ignored by Database Integration Service. |
|
16392 |
Dynamic loading of monitoring library is not supported |
RTI Monitoring Library is statically linked. In Database Integration Service there is no need to load this library dynamically. |
|
32769 |
Requested incompatible QoS |
The QoS of a Database Integration Service subscription is incompatible with the QoS of a Connext publication. The name of the policy that is incompatible is shown in this warning message. |
|
32770 |
Offered incompatible QoS |
The QoS of a Database Integration Service publication is incompatible with the QoS of a Connext subscription. The name of the policy that is incompatible is shown in this warning message. |
|
32771 |
Sample lost message |
A Database Integration Service subscription lost a sample. |
|
32772 |
Sample rejected message |
A Database Integration Service subscription rejected a sample. |