| TT16001 | TimesTen Replication Agent (version version_number) started | Informational message. No action required. |
| TT16002 | TimesTen Replication Agent termination begun | Informational message. No action required. |
| TT16003 | Replication Agent will not be restarted automatically | Informational message. No action required. |
| TT16004 | Failed to connect to datastore 'data_store_name' for 'thread_name' thread | The specified thread was unable to connect to the named database. |
| TT16005 | Failed to disconnect from datastore 'data_store_name' for 'thread_name' thread | The specified thread was unable to disconnect from the named database. |
| TT16006 | Failed to create DB context for 'thread_name' thread | Creation of the structure that maintains status information for a specific thread failed. |
| TT16007 | Failed to set DB context for 'thread_name' thread | The internal request to create the structure that maintains status information for a specific thread failed. |
| TT16008 | Failed to retrieve datastore info | Fetching the database information block failed. |
| TT16009 | Failed to determine diskless status of the data store | Replication agent failed to determine the diskless status of the database. |
| TT16010 | Failed to update diskless status of the data store | Replication agent failed to set the diskless status of the database. |
| TT16011 | To avoid data inconsistency, copy the data store from a replication subscriber using 'ttRepAdmin -duplicate'. Use ForceConnect=1 in the connection string to override this restriction | Attempt to reconnect to the master store without first performing the duplicate operation. Set theForceConnectattribute as described in "Recovering NONDURABLE databases" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for more information. |
| TT16012 | Data store is invalid. Replication Agent exiting but may be restarted by TimesTen daemon (depending on restart policy) | The replication agent considers the database to be invalid. |
| TT16014 | Current replication schema version is schema_version_number; we require schema_version_number | The version of the SQL schema that contains the replication schema is incompatible with the version of TimesTen that is currently operating. |
| TT16015 | Failed to determine replication schema version | The replication agent was unable to determine the version of the SQL schema that contains the replication schema. |
| TT16016 | Internal Error. Error from TimesTen daemon: daemon_name | A request to the TimesTen daemon failed with the specified error message. |
| TT16017 | Failed to initialize socket_name socket due to malloc failure | The replication agent was unable to allocate a data structure for communicating with the TimesTen daemon. This is a memory allocation failure. |
| TT16018 | Failed to connect to TimesTen daemon for socket_name socket; port: port_number; id: replication_agent_subdaem on id_number | The replication agent was unable to initiate a connection to the TimesTen daemon. |
| TT16019 | Error reading from deadman socket. System Error: error_message | A network or out-of-memory problem prevented a thread in the replication agent from opening a socket to the TimesTen daemon to perform. a read. |
| TT16020 | Fatal Error. Data received on deadman socket | A thread in the replication agent opened a socket to the TimesTen daemon to perform. a read. The read returned information, which means that the TimesTen daemon failed. |
| TT16021 | TimesTen daemon appears to be vanished. Terminating Replication Agent | TimesTen daemon appears to have terminated. Terminating replication agent. |
| TT16022 | Received a command_name command | Informational message. No action required. |
| TT16023 | Failed to create thread_name thread | Creation of a thread failed. This can occur because of an operating system failure or a memory resource shortage. |
| TT16024 | Not enough memory to start thread_name thread | A memory allocation failed for a TimesTen data structure that is used to manage threads. |
| TT16025 | Thread thread_name (context pointer_to_context_structure) starting | Informational message. No action required. |
| TT16026 | Thread 'thread_name' (context pointer_to_context_structure; return code return_code_name) exiting | Informational message. No action required. |
| TT16027 | All replication service threads have finished | Informational message. No action required. |
| TT16028 | Number_of_threads replication service threads did not finish | The replication agent is exiting, but some of the threads are not properly terminated. |
| TT16029 | Waiting for thread_name' thread to finish | Informational message. No action required. |
| TT16030 | *** CANNOT PERFORM. ANY REPLICATION WORK *** The replication schema has no information about the local store. The schema may be empty or incomplete, or the local store incorrectly represented. Monitoring the schema for changes... | Informational message. No action required. |
| TT16031 | Failed to allocate number_of_bytes bytes | Memory allocation failure |
| TT16032 | Call to function_name() failed. System Error: error_number | The specified operating system call failed with the error that is displayed. |
| TT16033 | Waiting for resolution of in-doubt transaction | XA transaction has been prepared but not committed. Informational message. No action required. |
| TT16034 | Invalid special purpose debug options entry in debug.options file | An unrecognized debug option was specified. |
| TT16035 | Special Purpose. Repagent enabled for check debugging_option | Informational message. No action required. |
| TT16036 | A transmitter thread already exist for peer 'dsname' on 'host_name' | Internal error. Two master threads are started for the same subscriber. |
| TT16037 | Internal Error. Nested transaction started by function_name() | Unexpected nested internal query |
| TT16038 | Failed to begin transaction for caller: function_name() | The replication agent was unable to start a transaction. |
| TT16039 | Failed to commit transaction for caller: function_name() | The replication agent was unable to commit a transaction. |
| TT16040 | Failed to rollback transaction for caller: function_name() | Replication agent requested that a completed transaction be rolled back, but the request failed. |
| TT16041 | Failed to compute a new replication hold LSN in function_name() | The replication agent was unable to set theHOLDlog sequence number. The hold log is the oldest record held in the log for possible transmission to a subscriber. |
| TT16042 | Failed to awaken log readers (TRANSMITTER threads) | A keep-alive message to a replication master failed. |
| TT16043 | Failed to retrieve replication LSN from data store | Reading the log sequence number failed. |
| TT16044 | Failed to retrieve my store ID from data store | The replication agent could not determine the ID of the connected database. |
| TT16045 | Failed to retrieve peer store ID for 'dsname' ON 'host_name' from data store. error_code. error_message | The replication agent failed to get a store ID for a specific database name and host name. |
| TT16046 | Failed to force log | A full flush of the replication log to the subscriber failed. |
| TT16048 | Mismatch in TimesTen version for source and destination machine | The same version of TimesTen must be operating on the source and destination machines. |
| TT16049 | Failed to update CTN for peer 'dsname' | An attempt to update a Commit Transaction Number in the database failed. |
| TT16050 | Failed to update replication hold LSN | An attempt to update theHOLDLog Sequence Number failed. |
| TT16051 | Failed to update replication state | An attempt to update a log sequence number failed during a backup. |
| TT16052 | Failed to set DB-level locking | Attempt to set the data-store-level lock failed. |
| TT16053 | Failed to open temporary file needed for this operation. OS-detected error: OS_error_name | A temporary file could not be opened during a backup. The operating system error is displayed. |
| TT16054 | Failed to perform. file seek in the temporary file needed for this operation. OS-detected error: OS_error_name | A seek on a temporary file failed during a backup. The operating system error is displayed. |
| TT16055 | Failed to read from the temporary file needed for this operation. OS-detected error: OS_error_name | A read on a temporary file failed during a backup. The operating system error is displayed. |
| TT16056 | Failed to backup data store. error_message | Database backup operation failed. The error message provides details. |
| TT16057 | Failed to perform. Network Checkpoint | Database checkpoint over a network connection failed. |
| TT16058 | Failed to execute table renewal. error_code.error_message | An attempt to create a list of tables on the subscriber failed. |
| TT16059 | Failed to send request/response to peer. error_message | Sending a message to the peer failed. The error message is displayed. |
| TT16060 | Failed to read data from the network. error_message | A read on a socket failed. This is often the result of network problems. The underlying error message is displayed. |
| TT16062 | Failed to compile command: command_name | Compilation of a SQL statement that is used by the replication agent failed. |
| TT16063 | Failed to execute command: command_name | Execution of a SQL command used by the replication agent failed. |
| TT16064 | Failed to execute prepared command in function_name() | Execution of a SQL command in the specified function failed. |
| TT16065 | Failed to open cursor for command: command_name | Opening a cursor during execution of a SQL statement used by the replication agent failed. The SQL statement is specified. |
| TT16066 | Failed to open cursor in function_name() | Opening a cursor during execution of a SQL statement used by the replication agent failed. The replication agent function in which this occurred is specified. |
| TT16067 | Failed to retrieve next row for command: command_name | Opening a cursor during execution of a SQL statement used by the replication agent failed. The SQL statement is specified. |
| TT16068 | Failed to retrieve next row in function_name() | Opening a cursor during execution of a SQL statement used by the replication agent failed. The replication agent function in which this occurred is specified. |
| TT16069 | Failed to find a row for command: command_name | The replication agent on the subscriber could not find replication information about a peer. |
| TT16070 | Internal Error. Failed to get format from command arguments for command_name | Command argument substitution failed for a SQL statement used by the replication agent. |
| TT16071 | Internal Error. Failed to get format from command results for command_name | Command result substitution failed for a SQL statement used by the replication agent. |
| TT16072 | Failed to delete command | Attempt to delete a compiled SQL command failed. |
| TT16073 | Internal Error. Failed to allocate a new slot for CTN. Retrying | The commit ticket number identifies a transaction. This error means that a slot could not be allocated to store the commit ticket number. |
| TT16074 | No table found with id table_id | A specified table cannot be found. This can occur when the SQL schema is updated. |
| TT16075 | Failed to lookup table table_name | Given an owner and table name, the table could not be found in the database. |
| TT16076 | Failed to retrieve version information of table table_name | The version of a table could not be determined. |
| TT16077 | Failed to retrieve format of table table_name | The format of a table could not be determined. |
| TT16078 | Table definition for ID table_id is invalid (Original failure message_id message_details) | A specified table cannot be found. This can occur when the SQL schema is updated. |
| TT16079 | Failed to retrieve information for column column_number of table table_name | The replication agent could not obtain description information for some column. |
| TT16080 | Table: table_name. Failed to lookup row row from master master for operation | A specific row was not found in a SQL table. This can occur during conflict resolution. |
| TT16081 | Table: table_name. Failed to update row | A row of a table could not be updated. |
| TT16082 | Table: table_name. Failed to update row row from master master for operation | A row of a table could not be updated. |
| TT16083 | Table: table_name. Failed to delete row for 'operation_name' | A row of a table could not be deleted. |
| TT16084 | Table: table_name. Failed to insert row for 'operation_name' | A row of a table could not be inserted. This can occur during conflict resolution. |
| TT16085 | Table: table_name. Failed to empty table | An attempt to make a table empty failed. |
| TT16086 | Wrong number (number_of_peers) of peers updated | An attempt to update the peer in the database returned an unexpected number of results. |
| TT16087 | Failed to read duplicate options | An attempt to determine the options given for a duplicate operation failed. |
| TT16088 | Unique constraint violation | A uniqueness constraint failed on update or insert. |
| TT16089 | Foreign Key constraint violation | A foreign key constraint failed on an update or insert. |
| TT16090 | Failed to check constraints for table table_name | A constraint check failed on an update or insert. |
| TT16091 | Failed to retrieve constraints information for table table_name | A table constraint failed on a update or insert. |
| TT16092 | Unexpected log record type record_type | An unrecognized record type was found in the log. |
| TT16093 | Invalid column type: column_type | An unrecognized column type was encountered in a log entry. |
| TT16094 | Failed to execute SQL: SQL_statement | A SQL statement failed to execute for a command generated by the replication agent. The SQL string is displayed. |
| TT16095 | No matching index columns for table table_name | The unique key on a column that was chosen by TimesTen on the table in the master does not exist on the subscriber. |
| TT16096 | Failed to retrieve information on index table_name.index_name for table table_name | The replication agent was unable to determine information about an index. |
| TT16097 | Failed to retrieve inline partition widths for table table_name | Internal error. Contact TimesTen Technical Support. |
| TT16098 | Invalid replicationschema. More than one entry for element element_name in replication scheme replication_owner. scheme_name. Continuing... | More than one replication element has been found for a specific element such a table. |
| TT16099 | Invalid replication schema. More than one master transmits table table_owner.table_name to me in replication scheme replication_owner. scheme_name. Continuing... | Multiple tables with a particular owner and name were found in a replication schema. |
| TT16100 | More than one host has peer 'dsname' | Multiple hosts have been identified as masters by a replication agent acting in a subscriber role. |
| TT16101 | Count of zero return subscribers disagrees with peer return service of machine_name for table id table_id | There is a difference in the return service specified by the two sides of a replication scheme. |
| TT16102 | Count of zero return by request subscribers disagrees with having a return by request peer for table id table_id | TheReturn Receipt by Requestattribute is inconsistent between two peers. |
| TT16103 | Failed look up cache group owner.cache_group_name | Named cache group was not found. |
| TT16104 | Incompatible cache group definition. Length of join predicate/where clause does not match for cache group owner.cache_group_name | Cache group definitions are inconsistent. |
| TT16105 | Incompatible definition for cache group owner. cache_group_name | The cached group on the two peers is incompatible. |
| TT16106 | Table table_name of cache group cache_name is not subscribed | There is an inconsistency in defining which tables are in a cache group. |
| TT16107 | Failed to check cache cache group subscription for cache_name | Failed to check whether all tables of a cache view are subscribed to by a specific peer. |
| TT16108 | Failed to retrieve local store information | The replication agent was unable to locate theTTREP.REPLICATIONStable. |
| TT16109 | Failed to update send LSN (operation: operation_name) | TheSENDLog Sequence Number could not be updated in the database. |
| TT16110 | Failed to update return-receipt send LSN | Update ofreturn-receiptLog Sequence Number in the database failed. |
| TT16111 | Failed to initialize send LSN (operation: operation_name) | The data structure used to read theSENDLog Sequence Number could not be initialized. |
| TT16112 | Failed to initialize replication meta-data | Initialization of the control block used to query the database for replication schema information failed. Additional messages about the cause of the problem are displayed, also. |
| TT16113 | Failed to get IP address for host host_name. Retry in 60 seconds | The attempt to map a host name used in a replication schema to an IP address failed. |
| TT16114 | Attempting to connect to dsname on host_name (host_ip_address); port: port_number | Informational message. No action required. |
| TT16115 | Connected to dsname (host_name); socket: socket_number; port: port_number | Informational message. No action required. |
| TT16116 | Added definition for column column_name (in table table_owner.table_name) into TTREP.REPTABLES | Informational message. No action required. |
| TT16117 | Dropped definition for column column_name (in table table_owner.table_name) from TTREP.REPTABLES | Informational message. No action required. |
| TT16118 | Failed to get replication hold value | An attempt to read the log sequence number for the hold log failed. |
| TT16119 | Failed to enable log buffer pad | Failed to set an internal TimesTen engine flag. This failure occurs if something is inconsistent in the database. Additional messages about the cause of the problem are displayed. |
| TT16120 | Failed to update transaction statistics for peer dsname | The replication master attempted by update statistics about a peer, but the attempt failed. |
| TT16121 | Failed to flush transaction queue. Restarting log read loop | Flush of the transaction log failed. Restarting read from the initial read LSN. |
| TT16122 | Failed to send heartbeat to peer. Restarting log read loop | The replication agent was unable to send its heartbeat message to its peer. |
| TT16123 | Transaction (transaction_id) already on send queue | This is an internal consistency check. The master adds a transaction to a queue to be sent to the subscriber, but the transaction is already on the queue. |
| TT16124 | Failed to retrieve subscription information for table id table_id | A query of the replication schema information about subscribers failed. |
| TT16125 | Inline data length for partitioned tuple (number_of_bytes bytes) exceeds maximum of maximum_number_of_bytes | Inline data for row is too long. |
| TT16126 | Failed to initialize buffer for transaction log read | Transaction log failed to open. |
| TT16127 | Failed to read transaction logs | A read of an entry from the transaction log failed. |
| TT16128 | Log seek operation failed at LSN log_sequence_number (caller line: line_number | Aseek(setting position) on the transaction log failed. |
| TT16129 | Starting log read at LSN log_sequence_number (caller line: line_number) | Informational message. No action required. |
| TT16130 | Update record does not contain old values | An internal consistency check for the TimesTen engine shows that an update does not include old values. |
| TT16131 | Internal Error. Bad copy to action ends at log_field not log_field with nbuf buffer primkeylen primary_key_length | A log record has field lengths that are inconsistent. |
| TT16132 | Internal Error. Buffer buffer addr address_value, size size | This message provides details for message16131: the buffer address size is wrong. |
| TT16133 | Peer signals change in its configuration | The peer configuration has changed. |
| TT16134 | Received a packet of type: packet_type | The type of network packet from a peer is not a recognized type. |
| TT16135 | Failed to retrieve column information for table table_owner.table_name | An attempt to query the database for information about a table in the replication scheme failed. |
| TT16136 | Sending definition for table table_owner.table_name (number_of_columns columns) | Informational message. No action required. |
| TT16137 | Transmitter signon to peer failed with signon error: error_number. Shutting down transmitter | The master attempted to sign on with the subscriber, but the attempt failed. |
| TT16138 | Propagation cannot co-exist with Master Catchup | Catchup mode on a propagating replication agent has occurred due to corruption in the database. |
| TT16139 | Failed to add table to transmit queue | The master replication agent was unable add a table to its queue to be sent to the subscriber. Details in other error messages. |
| TT16140 | Failed to initialize post handle from sbLRRepSync log record | Synchronous"Post Procedure Fail". For synchronous replication, concerns a data structure used to "wake up" a thread. |
| TT16141 | Failed to initialize semaphore from sbLRRepSync log record | There was a problem initializing a data structure used to manage the peers of the replication agent. Details in other error messages. |
| TT16142 | Failed to retrieve peer information. No peers found | The replication peer was not found in replication schema. This message is usually due to a change in the schema. |
| TT16143 | Failed to retrieve any timeout information | Internal information about the replication scheme was not found. |
| TT16144 | Failed to get a slot in the return-receipt buffer | Failed to allocate the buffer used byRETURN RECEIPT. Details in other error messages. |
| TT16145 | Failed to update state in return-receipt buffer | The return receipt updated failed in the database. |
| TT16146 | Failed to exchange initial diskless CTN with peer | Diskless"Commit Transaction Number"exchange to a peer failed. Details in other error messages. |
| TT16147 | Failed to change transmit byte to 0 for diskless transmit | An update of a table related to diskless replication failed. Details in other error messages. |
| TT16148 | Reinitialize due to changes in replication schema | Informational message. No action required. |
| TT16149 | Current state is FAILED for peer dsname | While reading the transaction log, the transmitter notices that its state is "peer failed". |
| TT16150 | Failed to send FAIL packet to peer | The replication agent failed to notify a peer that the replication has failed. Details in other error messages. |
| TT16151 | Log record type record_type, data size number_of_bytes, LSN log_sequence_number | Internal error. Contact TimesTen Technical Support. |
| TT16152 | Failed to determine whether replication state is FAILED | An attempt by the subscriber replication agent to determine if it has been markedFailedhas failed. |
| TT16153 | Failed to initialize return-receipt buffer | The subscriber replication agent was unable to initialize itsRETURN RECEIPTstate. |
| TT16154 | Failed to check for replication schema changes | An attempt to mark a replication schema as changed has failed. |
| TT16155 | Temporary failure to access replication configuration | The agent cannot access configuration information about replication. The agent can recover and continue. |
| TT16156 | Failed to access replication configuration. Restarting replication agent | An attempt by the replication agent to access the replication schema failed. |
| TT16157 | REPLISTENER thread waiting for number_of_threads RECEIVER thread(s) to exit | Informational message. No action required. |
| TT16158 | Failed to retrieve peer list | Query of the replication schema to determine subscribers failed. |
| TT16159 | Starting new transmitter for 'dsname' on 'host_name' | Informational message. No action required. |
| TT16160 | Failed to flush log records. Replication Agent exiting; but will be restarted by TimesTen daemon | Failed to flush log records. Replication agent exiting; but the TimesTen daemon restarts the replication agent. |
| TT16161 | Listening on configured port: port_number (assigned port: port_number) | Informational message. No action required. |
| TT16162 | Call to setsockopt (tcp_socket_option) failed. System Error: error_number | A "Set Socket Options Failed" networking OS call failed. The details are included in this message. |
| TT16163 | RECEIVER thread terminating due to certain error already recorded in the system log | The subscriber replication agent is exiting due to an error. |
| TT16164 | Received a FAIL packet. Setting replication state to FAILED and shutting down myself | The subscriber replication agent received a request to mark the replication state as "failed". |
| TT16165 | Failed to perform. backup operation | A subscriber backup operation failed. Details in other error messages. |
| TT16166 | Failed to perform. memory copy operation | Memory copy operation Fail. |
| TT16167 | Failed to check catchup status | Automatic catch-up operation for a failed master database has failed. |
| TT16168 | Master Catchup started for 'data_store_name' from CTN commit_transaction_number to commit_transaction_number | Informational message. No action required. |
| TT16169 | TimesTen Replication Agent termination begun because of permanent failure during Master Catchup | Internal error. Contact TimesTen Technical Support. |
| TT16170 | Master Catchup completed for 'data_store_name' | Informational message. No action required. |
| TT16171 | Confirm Name packet with unreasonable name length number_of_bytes | Internal error. Contact TimesTen Technical Support. |
| TT16172 | Confirm Name packet for dsname received, but I am dsname | Internal error. Contact TimesTen Technical Support. |
| TT16173 | Accepting messages from a peer which is unknown locally | A request was received from an unknown peer. This is usually due to a change in the replication schema that has not yet been applied. |
| TT16174 | Found more than one peer; cannot determine default | A subscriber discovered more than one peer with the same replication name and owner. |
| TT16175 | Defaulted connection to peer store id peer_store_id; protocol: protocol_number | Informational message. No action required. |
| TT16176 | Signon message after transmitting peer assigned | A subscriber replication agent is reporting that the master requesting to sign on is already signed on. |
| TT16177 | Lookup of transmitting peer dsname failed | A subscriber got a sign on request from a master, but there is no appropriate information about that master in the replication schema. |
| TT16178 | Found transmitting peer dsname in TTREP.TTSTORES with no entry in TTREP.REPPEERS; continuing | A subscriber got a connection request from a master, but the subscriber does not recognize it as a peer according to information in the replication schema. |
| TT16179 | Transmitting peer dsname not defined to me | Warning: A subscriber got a connection request from a master, but the subscriber does not recognize it as a peer according to information in the replication schema. |
| TT16180 | Transmitting peer dsname ON host_name has the same store id (data_store_id) as me | The peer ID found by a replication agent was its own ID. Possible cause is corrupt TTREP.REPNETWORK table. |
| TT16181 | Replication reserve slot failed | Query to reserve a "commit transaction number" slot failed (and logged its own error message). |
| TT16182 | Replication ctnlist (CTN: commit_ticket_number) value read failed | The replication agent was unable to read the Commit Transaction Number from the database. |
| TT16183 | Failed to set replication status for this connection | Query to set replication status failed (and logged its own error message). |
| TT16184 | Failed to determine whether to propagate | Query to determine if there is any propagation for the current database has failed. Details in other error messages. |
| TT16185 | RECEIVER thread noticed replication configuration change | Informational message. No action required. |
| TT16186 | RECEIVER thread disconnects due to superseded connection from peer (internal version was version_number, now version_number) | The peer uses a different version of the replication schema than this replication agent. Note that this is not the same as the TimesTen version. |
| TT16187 | Transaction commit_ticket_number; Error: transient flag, permanent flag error message : number | The commit of a block of transactions had errors. Details in other error messages for the individual failures. Some of the failures may be temporary. |
| TT16188 | rxCommitTx() failed to commit | The commit of a block of transactions failed. |
| TT16189 | Failed to begin transaction. Subscriber state is state_number | The replication agent is beginning a transaction, but it is not in the idle state. Internal error. Contact TimesTen Technical Support. |
| TT16190 | Failed to push propagation loop | A propagation path could not be stored, usually because it is a loop. |
| TT16191 | Replacing old table definition (table_definition) with the one received from peer (dsname) | A SQL table that has already been seen in the replication stream has been encountered. This can occur if there are SQL schema changes. |
| TT16192 | Skipping definition received for already-defined table table_name. Part of previously processed transaction | A SQL table that has already been seen in the replication stream has been encountered. This can occur if there are SQL schema changes. The transaction is skipped and the new table definition is discarded. |
| TT16193 | Adding definition for table: table_name | Informational message. No action required. |
| TT16194 | Subscriber return service attribute conflict for element element_name (table table_name) in replication scheme replication_owner. scheme_name. Transmitting peer dsname ON host_name says 'message'; local schema says 'message'. Transmitter's value will be used | The return attribute on this replication element is different for each peer. |
| TT16195 | Failed to find owner for element element_name (table table_name) in replication scheme replication_owner. scheme_name (received from peer dsname ON host_name). Continuing ... | Failed to find owner for this table element in the replication scheme on the named replication peer. |
| TT16196 | Master/subscriber conflict with peer peer_name on table_name for element element_name (object table_name) in replication scheme owner.scheme. | The owner of this table element conflicts on the two replication peers. |
| TT16197 | Failed to add element element_name (table table_name) for transmitting peer dsname ON host_name | Attempt to add a replication element has failed, probably due to a duplicate. This is a race condition where something happens between when a check is made and the attempt to add the element. |
| TT16198 | Table definition mismatch on number of columns for table table_name. Local definition: number_of_columns; transmitting peer: number_of_columns | "Table Definition Mismatch" between the two peers. Some differences are tolerated, but others are not. |
| TT16199 | Table definition mismatch on attribute_name for column column_number in table table_name. Local definition: attribute_name; transmitting peer: attribute_name | "Table Definition Column Mismatch" between the two peers. |
| TT16200 | Table definition mismatch on timestamp column in table table_name. Local definition: timestamp; transmitting peer: timestamp. Continuing with transmitter's value | TheTIMESTAMPcolumn on one peer is not the same as theTIMESTAMPcolumn on another peer. This can occur during conflict resolution based on timestamps. |
| TT16201 | Table definition mismatch on timestamp exception action in table table_name. Local definition: action; transmitting peer: action. Continuing with transmitter's value | When there is a difference in timestamps between two peers, the action that each peer should take is different. The action of the transmitting peer is chosen. |
| TT16202 | No cache view entry for table table_name | A subscriber replication agent could not find a cache group associated with a particular table sent by the master. |
| TT16203 | Passed extended comparison for table table_name | Informational message. No action required. |
| TT16204 | Table table_name marked invalid. Will not apply transactions received for it until a valid definition is received | A replicated table was marked invalid. |
| TT16205 | Skipping definition received for cache group cache_group_name. Part of previously processed transaction | Informational message. No action required. |
| TT16206 | Definition for different cache group received. Current: cache_group_definition; New: cache_group_definition. Table table_name marked invalid | The cache group definitions are different between the two peers. |
| TT16207 | Internal error. Table ID mismatch | Internal error. Contact TimesTen Technical Support. |
| TT16208 | Failed to open file file_name for Timestamp report | Could not open the replication agent report file. |
| TT16210 | Varying length part of key tuple > number_of_bytes bytes | The size of a primary key caused an overflow of a data packet. |
| TT16211 | No matching V* value found for Table: table_name; column: column_name; offset: column_offset; ID: hexadecimal "Insert LSN from peer (dsname) was log_sequence_number | There is an inconsistency between the master and subscriber in the area ofVARCHARorVARBINARYcolumns in a replicated table. Internal error. Contact TimesTen Technical Support. |
| TT16212 | Failed to set column column_number of table table_name | Subscriber replication could not set a column value. |
| TT16213 | Table: table_name. Failed to insert row. error_message | Subscriber replication agent could not insert a row into a table due to a timestamp conflict. |
| TT16214 | Table: table_name. Failed to delete row. error_message | Subscriber replication agent could not delete a row due to a timestamp conflict. |
| TT16215 | Table: table_name. Failed to update row. error_message | Subscriber replication agent could not update a row due to a timestamp conflict. |
| TT16216 | Failed to retrieve column number for column_name of table table_name | In an update, given a column name, the column number could not be computed. |
| TT16217 | Connection connection_id awakened | Replication transactions have been halted, but the peers are connected again. |
| TT16219 | Failed to retrieve any compression information | The replication agent cannot find information to complete compression. |
| TT16220 | Replication is not supported with an agent using the protocol protocol_type | Incompatible versions of the replication protocol between the two peers. |
| TT16221 | Table table_name not found | Table specified by master not found on receiver. |
| TT16222 | The call gettimeofday failed | The system call to get time of day failed. |
| TT16223 | Transmitter thread failure due to high latency milliseconds with peer store DSN | The network latency between the databases is higher than permitted for an active standby pair. |
| TT16224 | Transmitter thread failure due to high clock skew milliseconds with peer store DSN | The clock slew between the databases is higher than permitted for an active standby pair. |
| TT16225 | Transmitter thread failure due to lack of scheme consistency with peer store | The databases that are a part of the active standby pair have replication schemes that are not the same. If the replication scheme is altered, a duplicate operation must be executed to ensure that the schemes on the two stores match. |
| TT16226 | Receiver thread failure due to scheme read failure | The local database was unable to read the replication scheme. |
| TT16227 | Standby store has replicated transactions not present on the active | The standby database has transactions present that are not present on the active database. This indicates that the present active database was incorrectly set up to be an active database. To remedy this situation, duplicate the standby database from the active database. |
| TT16228 | Transmitter thread failure due to lack of state consistency between active and standby stores | The databases that are part of the active standby scheme have replication schemes that are not the same. If the replication scheme is altered, then a duplicate operation must be executed to ensure that the schemes on the two stores match. |
| TT16229 | Transmitter thread failure due to lack of state consistency at subscriber store DSN | The databases that are part of the active standby scheme have replication schemes that are not the same. If the replication scheme is altered, then a duplicate operation must be executed to ensure that the schemes on the two stores match. |
| TT16230 | Store not in standby state | An error returned by the replication agent that indicates a transitory condition. No user action is necessary. |
| TT16231 | The duplicate operation on this store was not successfully completed | The local database was created by a duplicate operation that did not complete successfully. Destroy the database and perform. the duplicate operation again. |
| TT16232 | Connection rejected from the standby until connection received from the active | Usually indicates a transitory error. A subscriber database allows a standby database to connect only after it has a connection from the active store. |
| TT16233 | The subscriber store has updates not present on the active store | The subscriber database has transactions present that are not present on the active database. This indicates that present active database was incorrectly set up.To remedy this situation, duplicate the subscriber database. |
| TT16234 | The subscriber store has been classified as failed by the active | The stores that are a part of the active standby scheme have replication schemes that are not consistent. This is usually a transitory error. If the error persists, then a duplicate operation must be executed to ensure that the replication schemes on the two stores match. |
| TT16235 | Failed to update CTNs for standby 'DSN' | Error updating replication bookmark information (Commit Ticket Number) in the replication agent. |
| TT16236 | Failed to update CTN for the subscriber store | Error updating replication bookmark information (Commit Ticket Number) in the replication agent. |
| TT16235 | Failed to update CTNs for standby 'DSN' | Replication did not update Commit Ticket Number for the specified standby database. |
| TT16236 | Failed to update CTN for the subscriber store | Replication did not update Commit Ticket Number for the subscriber database. |
| TT16237 | Awt thread initialized for racleNetServiceName= <net_svc_name>, CacheUid=<cache_uid>, BatchCommitSize=size, AwtErrorFile=<awt_err_file>, AwtBufSize=size KB | This message appears in the user error log. It is informational. No action is necessary. |
| TT16240 | An error occurred replicating changes to Oracle but an AWT error file will not be generated since TimesTen is running in diskless mode | An asynchronous writethrough error file is not created when TimesTen is operating in diskless mode. |
| TT16242 | Failed to retrieve subscription information for sequence id sequence_id | A failure occurred while retrieving subscription information for a sequence. |
| TT16243 | No sequence found with id sequence_id | A sequence with the specified ID was not found. |
| TT16244 | Skipping definition received for already-defined sequence sequence_id. Part of previously processed transaction | A subscriber received information about a sequence but already has the information. |
| TT16245 | Adding definition for sequence: sequence_id | Generated when information about a replicated sequence on the subscribing side is added to the list of sequence information. |
| TT16246 | Sequence definition mismatch for sequence sequence_id. Local definition: Minval : value, Maxval: value, Increment: value; transmitting peer: Minval: value, Maxval: value, Increment: value | The sequence definition on the master database does not match the sequence information generated for the subscriber databases. |
| TT16247 | Sequence sequence_id marked invalid. Will not apply transactions received for it until a valid definition is received | An invalid sequence definition has been received by the subscriber databases. No updates are applied for this sequence until a valid description is sent. |
| TT16248 | Sequence sequence_id not found | A subscriber database received a definition for a sequence that does not exist on the subscribing side. |
| TT16249 | Failed to add sequence to transmit queue | This error occurs a sequence update message from the master database was not added to the queue. |
| TT16250 | Failed to update sequence sequence_id | Failed to apply a sequence update to the subscriber database. |
| TT16251 | Sending definition for sequence owner.sequence_id | Informational message from master database. |
| TT16252 | Table definition mismatch on cascade delete configuration for table table_name. Local definition: subscriber; transmitting peer: master | The foreign key cascade delete constraints for the table do not match between the master and subscriber stores. |
| TT16253 | Failed to revtrieve cascade delete configuration for table table_name | This is an internal error. TheCASCADE DELETEdefinition on the master and subscriber may not be the same. Contact TimesTen Technical Support. |
| TT16254 | Master has not been assigned an Active or Standby Role | This message could occur when a replication agent for a master store in anACTIVE STANDBYscheme has been started but has not been classified as either master or standby. The thread attempts to restart until a state has been determined. |
| TT16255 | Invalid replication schema. More than two _ORACLE stores found in scheme | Internal error. A sanity check has failed in anACTIVE STANDBYscheme that includes autorefresh cache groups. Contact TimesTen Technical Support. |
| TT16256 | Invalid replication schema. No _ORACLE stores found | Internal error. A sanity check has failed in anACTIVE STANDBYscheme that includes Autorefresh cache groups. Contact TimesTen Technical Support. |
| TT16257 | The ID for this store does not match either of the master Ids | Internal error. A sanity check has failed after attRepAdmin -duplicateoperation on anACTIVE STANDBYscheme that includes Autorefresh cache groups. Contact TimesTen Technical Support. |
| TT16258 | Failed to retrieve heartbeat factor information | Internal error. Contact TimesTen Technical Support. |
| TT16259 | Wrong number of rows (number_of_rows) affected on Oracle when updating Active Standby Information | Internal error. A sanity check failed in anACTIVE STANDBYscheme when information was updated on an Oracle subscriber. Contact TimesTen Technical Support. |
| TT16260 | Failed to update autorefresh bookmark | The replication operation was unable to update the autorefreshed cache group bookmark on the subscriber store at runtime.This may occur because the cache group does not exist on the subscriber. |
| TT16261 | Failed to add cache bookmark to transmit queue | This error occurred while adding the replicated autorefreshed cache group bookmark to the sending queue. The cache group may no longer exist on the master store. |
| TT16262 | Failed to retrieve subscription information for cache bookmark id ID | This error occurred while accessing the subscription information for an autorefreshed cache group bookmark. The cache group may no longer exist on the master store. |
| TT16263 | Secure protocol violation | There was a connection attempt from another replication agent that violated the security challenges presented on the protocol. |
| TT16264 | Awt Ctn initialized to timestamp=value SeqNum=value | Informational message. No action required. |
| TT16265 | This store is currently the STANDBY. Change to owner.name not permitted | When an active standby master is inSTANDBYmode you cannot update the store directly. Operations such as adding or dropping a column,INSERT,UPDATE,TRUNCATE, orDELETEare prohibited. |
| TT16266 | The remoteDaemonPort cannot be used for this -duplicate operation because the sending data store has stores that use automatic port allocation. | A remote daemon port cannot be selected during a duplication operation when the replication scheme is using automatic port allocation. To use automatic port allocation, do not specify the-remoteDaemonPortoption in the duplicate operation or supply a value of 0 for the operation. |
| TT16267 | The host name list is not available from ttrep.ttnework. | An error occurred in performing a query onTTREP.REPNETWORKtable. This is usually a transient error, if the database is already running and a replication scheme is already defined on the master database. The transmitter in the replication agent attempts to run this query again in one second. |
| TT16268 | Failed to retrieve aging configuration for table owner.tablename. | This is part of replication. The first time the transmitter sends a transaction for a particular table, TimesTen sends the table definition. This message indicates something went wrong while trying to retrieve the aging information. There is an additional error message detailing the specific failure. Review that message to determine the problem and fix. |
| TT16269 | In an Active Standby scenario, AWT Monitoring should be enabled on the Standby node | In an active standby pair with an AWT cache group, monitoring gives relevant results only on the standby node, which does the propagation of the workload to the Oracle database. Enabling AWT monitoring on the active node does not record any monitoring information. If the standby node fails and if the active node takes over, calling thettCacheAwtMonitorConfigbuilt-in procedure automatically enables monitoring the AWT statistics. |
| TT16270 | AWT Monitoring should not be enabled on the Subscriber node in an Active Standby scenario | In an active standby pair with subscribers and an AWT cache group, monitoring on a subscriber does not reveal any useful information. Call thettCacheAwtMonitorConfigbuilt-in procedure to disable monitoring the AWT statistics. |
| TT16271 | Monitoring could not be configured because replication agent does not have an active AWT thread | This error is thrown if the replication agent is either invalid or in an initialization phase. If the AWT receiver is killed due to an unexpected situation, the replication agent is in an invalid state. It is also possible that the AWT receiver has not been started by the replication agent, in which case it is in an initialization phase. Resolution for this error is to call thettCacheAwtMonitorConfigbuilt-in procedure again, with the state parameter set to "ON." |
| TT16272 | Operation not permitted on a store in the ACTIVE state. | This is an internal mismatch. In an active standby pair, a routine that should only be running on a standby is running on the active. This is most likely caused during the detection of a "split-brain" (both masters marked active) problem and should be self-correcting. |
| TT16273 | Error updating standby store. | A failure occurred while trying to get the latest status for an active standby pair standby. This error may occur following the error that generated message 16272. |
| TT16274 | Failed to modify active standby data. caller: caller_name | After a duplicate operation, some data on TimesTen system tables must be modified for the destination store on both TimesTen and Oracle. This operation has failed, but the replication agent retries the operation. |
| TT16275 | RECEIVER network helper thread terminating due to certain error already recorded in the system log | Warning. No action required. |
| TT16276 | RECEIVER restarting daemon because helper thread failed to spawn | Warning. No action required. |
| TT16277 | The Instance Admin user id is not the same in both instances. | The instance administrator name must be the same on both the source and target databases when runningttRepAdmin -duplicateorttRepDuplicateEx. |
| TT16278 | Failed to get Cache AWT method | Unable to get the attribute value for use in the replication agent. An invalidation was most likely detected. |
| TT16279 | Cannot start AWT propagation because replication agent cannot connect to Oracle RDBMS database: racleNetServiceName = \"name\", uid = \"uid\",pwd is hidden, TNS_ADMIN = \"TNS_ADMIN_name\", Error Msg= \"message\" | Replication agent is not able to connect to Oracle server.
Check to see that TNS_ADMIN is configured properly and make sure the Oracle server is reachable. |
| TT16280 | Parallel AWT requested restart of the worker threads | Parallel AWT thread encountered an error and restarting of the threads was necessary. |
| TT16281 | Replication receiver track %d waiting for receiver track %d to initialize | This is an informational start up message. |
| TT16282 | Replication receiver track %d waiting for receiver track %d to finish | This is an informational shut down message. |
| TT16287 | Replication receiver with local store id %llu, remote store id %llu, track id %d still finds a previous track 0 receiver running. | A master thread running on the receiver was detected and should not have been. |
| TT16288 | Replication receivers are stopping. | This is an informational shut down message. |
| TT16289 | Replication receivers face dependency error. | There was an internal error during a replication dependency wait for parallel processing. |
| TT16290 | Replication transmitters are stopping. | This is an informational shut down message on the transmitter. The group of threads for a particular subscriber are stopping. |
| TT16291 | Replication receivers are starting serial commit mode | This is an informational message. If a parallel failure occurs, TimesTen will try to reprocess the transactions in serial mode. |
| TT16292 | Replication receivers are stopping serial commit mode | This is an informational message indicating that the replication receivers are stopping serial commit mode. |
| TT16293 | Failed Replication thread thread is exiting description | This error occurs when the transmitter is stopping. You should see a description of what the transmitter was doing before it exited. |
| TT16810 | Successfully executed: command | Informational message. No action required. |
| TT16999 | Replication_Message | This is an informational replication message that is found in the replication log. The message text provides details on the message. |