TT8000 | No primary or unique index on non-nullable column found for replicated table owner.table_name | To be replicated, a table must have a unique index over non-nullable columns. See "Table requirements and restrictions" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for details. |
TT8001 | Attempt to read invalid LSN log record | The LSN provided does not exist. See "About XLA bookmarks" in the Oracle TimesTen In-Memory Database C Developer's Guide for information on bookmarks. |
TT8002 | Cannot drop replicated table, index, or sequence | TimesTen Replication prevents tables, indexes, and sequences from being dropped when they are being used for replication.To drop such a table, index, or sequence, stop the replication agent, drop the replication scheme with theDROP REPLICATIONstatement. Then drop the table, index, or sequence. |
TT8003 | Update older than TimeStamp of existing row | The timestamp of update is older than that of the row in the database. The update was rejected. |
TT8004 | Column owner.table.column cannot be used for replication timestamp checking if in an index or added by ALTER TABLE; and must be binary(8) with NULL values allowed | The Timestamp column type must beBINARY(8) NULL, cannot be in the index and must be in the original unaltered table. |
TT8005 | Invalid update rule for timestamp-based conflict checking | Invalid flag value used by a replication stored procedure. |
TT8006 | Application must set timestamp column with 'UPDATE BY USER' | The application has not set the timestamp column. The insert or update is rejected. Set timestamp or allow TimesTen to automatically set timestamp. |
TT8007 | Cannot change aging attributes or add/drop aging policy of replicated tables while replication Agent is running | The replication agent must be stopped before attempting to perform. changing aging policies or attributes on replication tables. |
TT8009 | Transaction Log API Buffer size too small or too large | The transaction log API buffer size is too small or too large for the platform. Choose a different buffer size. See "Managing the transaction log on a replicated database" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for details. |
TT8010 | Unable to attach to XLA segment | Unable to attach to the shared memory segment used to store the transaction log updates. |
TT8011 | Unable to re-configure active XLA segment | The transaction log buffer size cannot be changed in an active transaction. |
TT8012 | Table with given ID not found | Table with the user-specified ID does not exist in the database. |
TT8013 | Attempt to specify illegal version | The version specified is not a valid TimesTen release version. |
TT8016 | No replication buffer configured | The transaction log buffer has not been configured to store updates. See "Configuring the staging buffer" in the Oracle TimesTen In-Memory Database C Developer's Guide for information on configuring the staging buffer. |
TT8017 | Foreign table has number columns while local table has number columns | The tables being compared differ in the number of columns. |
TT8018 | Foreign table indexed on different columns | The tables being compared have indexes on different sets of columns. |
TT8019 | Foreign and local table differ on column type type | The tables being compared do not match on the column types. |
TT8020 | Inconsistent row in update description | Bad row format in transaction log update. |
TT8021 | System table ID invalid | User specified system table ID does not exist. |
TT8022 | Operation not permitted on non-shared data store | Operation permitted on shared database only. |
TT8023 | Table row does not have expected value | The contents of the row do not match the expected values in the transaction log update. |
TT8024 | Illegal XLA record type | The XLA record is invalid or unsupported. |
TT8025 | Replication log threshold limit reached at master. The replication state for this subscriber data store is now set to FAILED. This store is not in sync with the master | The replication state for this database has been set to FAILED state by a replication peer. This happens when the amount of log that the peer is holding for the database exceeds a user configurable threshold. See "Setting the log failure threshold" and "Subscriber failures" in Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for further details. |
TT8027 | Network load of data store not allowed because connection was reset | Network error occurred while running attRepAdmin -duplicateoperation. Check your network connections. Make sure that the remote replication agent is still running. If not, restart the replication agent. |
TT8028 | Network load of data store timed out | Network timed out while running attRepAdmin -duplicateoperation. Check your network connections. Make sure that the remote replication agent is still running. if not, restart the replication agent. |
TT8029 | Persistent transaction log API bookmark already in use | Only one persistent transaction log API connection can use a persistent transaction log API bookmark. Close the connection using the bookmark or set up a new bookmark. |
TT8031 | Persistent transaction log API log sequence number is invalid | The transaction log API log sequence number is not a valid one. It is either not provided by the API or it is in the range already acknowledged by the connection. |
TT8032 | Stale post handle | The replication transmitter accessed a synchronization object, used for return service processing, that no longer applies to this particular service request. This is an internal condition that is externalized only as a part of the user error log warning "Attempt to awaken connection connection_id failed." |
TT8033 | Invalid post handle | The replication transmitter accessed a synchronization object, used for return service processing, that was no longer a valid synchronization object. This is an internal condition that is externalized only as a part of the user error log warning "Attempt to awaken connection connection_id failed." |
TT8034 | Record cannot be expressed in SQL | This error is returned when an XLA record presented tottXlaGenerateSQLdoes not translate into SQL. |
TT8035 | Persistent XLA requires disk based logging | Logging to disk is required for persistent transaction logging API. See "XLA concepts" in the Oracle TimesTen In-Memory Database C Developer's Guide for more information. |
TT8036 | Parameter parameter value not in valid range | The parameter is not in the valid range. Change the parameter. |
TT8037 | Table definition of record differs from the table definition in the data store | The table definition of the record at the time of its creation differs from the table definition of the record in the data s tore. Since the definitions do not match, the record cannot be interpreted by the database. |
TT8038 | Operation not permitted on system table | You cannot perform. the attempted operation on aSYStable. The operation is only permitted on a user-defined table. |
TT8039 | Attempt to drop replication timestamp column from table table_name | The timestamp column is used by TimesTen to resolve conflicts. This column cannot be dropped. |
TT8040 | No free slots in replCTNArr | Internal error. Contact TimesTen Technical Support. |
TT8041 | Invalid replCTNArr slot | Internal error. Contact TimesTen Technical Support. |
TT8042 | ReplCTNArr slot is not allocated | Internal error. Contact TimesTen Technical Support. |
TT8043 | Materialized views cannot be defined in a replication scheme | An attempt was made to replicate a materialized view. Only detail tables can be replicated. See "Replicating materialized views" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for more information. |
TT8044 | 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 | WhenRETURN RECEIPTreplication is used with theTRANSMIT NONDURABLEoption, a failed master database is allowed to recover only by restoring its state from a subscriber database using the-duplicateoption ofttRepAdmincommand. Use theForceConnectattribute to override this restriction. |
TT8046 | The input old value row does not match the data store row | The old value row of the XLA update being applied does not match the value of the row in the database. |
TT8047 | Connection is currently dedicated to XLA exclusively | The connection is in use by XLA. No direct ODBC calls may be made on this connection until the XLA connection is closed. |
TT8049 | Commit ticket number will wrap around | The commit ticket number for replication wraps around with this operation. |
TT8050 | The alter table operation on a replicated table needs to be in a transaction of its own | TheALTER TABLEstatement for a replicated table must be in a transaction of its own and cannot be preceded or followed by any other SQL statement. |
TT8051 | The alter table operation on a replicated table cannot be in a two safe by request transaction | Cannot useALTER TABLEto alter replicated tables in aRETURN TWOSAFE BY REQUESTtransaction. Rollback the transaction. |
TT8052 | Cannot commit transaction that involves commit to Oracle and TWOSAFE replication handling | Cannot commitRETURN TWOSAFEtransactions on tables in a TimesTen cache group. |
TT8056 | Temporary tables cannot be defined in a replication scheme | A temporary table was used in a replication scheme. Temporary tables cannot be used in a replication scheme. |
TT8059 | All DDLs on a replicated table need to be in a transaction of their own | This error is returned when DDL operations on a replicated table are not present exclusively in a transaction of their own. |
TT8060 | Cannot specify replication timestamp column on a cached table | The user is not allowed to configure timestamp-based conflict resolution for replication on cached tables. |
TT8061 | Operation not permitted when the connection attribute ForceConnect is set to 1 | The connection attributeForceConnectmust be set to 0 on any connections that attempt these replication operations. |
TT8062 | Local store not in ACTIVE state | The state of the local store is not in theACTIVEstate for a store that is part of an active standby replication scheme. |
TT8063 | Local store not completely quiesced | This error is returned when an active store in an active standby replication scheme has pending updates that have not yet been replicated. Turn off local application updates and ensure that replication has sent all pending updates to the standby store to avoid this error. |
TT8064 | Table is already subscribed | A subscription attempt for the same table is being attempted twice. |
TT8065 | Table is not subscribed | The table is already unsubscribed from the XLA bookmark. There is no need to perform. an unsubscribe operation. |
TT8066 | Canot alter subscription | The XLA bookmark must be closed before this operation can be performed. |
TT8067 | Inconsistency detected in the COLUMN_HISTORY system table | The contents of the system table,COLUMN_HISTORYseem to be corrupted. |
TT8068 | Cannot drop a table or view that is subscribed by an XLA bookmark. | The table must be unsubscribed from every XLA bookmark to avoid this error. |
TT8069 | Operation only supported when the character set of the data store in which the record is generated matches that of the connected store | The operation is only supported when the character set of the source and destination store match. |
TT8070 | The specified XLA bookmark does not exist | The XLA bookmark does not exist. You can create a bookmark using thettXlaBookmarkCreatebuilt-in procedure. |
TT8071 | A replicated bookmark can only be created on a store with active standby pair replication. | Enforcement of this restriction. |
TT8072 | Operation only permitted on an ACTIVE store. | User attempted an XLA operation that is only permitted on a store when in theACTIVEstate. |
TT8073 | Failed to update XLA bookmark :bookmark. | The replication agent on the standby store ran into a problem updating the XLA bookmark. The agent will keep trying until the condition that caused the error is alleviated. Standby updates to XLA bookmarks will fail every time this error is returned. Possible causes may be an unhealthy standby store or locks held on XLA tables on the standby store. |
TT8074 | Maximum number of bookmarks exceeded. | User attempted to create more than the maximum number of replicated bookmarks per database. |
TT8075 | Error loading bookmark list. | The replication agent ran into an error reading the set of replicated bookmarks from the database. Agent will keep trying until the condition that caused the error is alleviated. Possible causes may be an unhealthy standby store or locks held on XLA tables on the standby store. |
TT8076 | Bookmark reset due to state change at store. | The state of the store was recently changed. All the bookmarks that were open at the time of the state change need to be reset since their state may be stale. The bookmarks are reset and users can use them to read XLA updates. |
TT8077 | Error moving bookmark on the standby store. | The replication agent on the standby store ran into a problem updating the XLA bookmark. Agent will keep trying until the condition that caused the error is alleviated. Standby updates to XLA bookmarks will fail every time this error is returned. Possible causes may be an unhealthy standby store or locks held on XLA tables on the standby store. |
TT8078 | The deletion of replicated XLA bookmarks is not allowed while the replication agent is running. | Replicated bookmarks can only be removed when the local replication agent is not running. |
TT8079 | Cache group ownership table cannot be defined in a replication scheme. | An attempt was made to replicate a table used to store ownership table of a global cache group. Only cache group tables can be replicated. |
TT8093 | The local replication agent needs to be running for this operation | The local replication agent must be started. |
TT8094 | Mutiple concurrent executions of this built-in are not permitted | Only one execution of the built-in is allowed at any time. Once the previous call returns, a new call may be made. |
TT8095 | Truncate table not permitted when ttRepTransmitSet(0) has been invoked on the connection | The replication agent attempted to truncate a table when replication has been disabled on this connection. To allow table truncation, invoke the built-in procedurettRepTransmitSetwith argument 1. |
TT8096 | Alter table not permitted when ttRepTransmitSet(0) has been invoked on the connection | The replication agent attempted to alter a table when replication has been disabled on this connection. To alter a table, you must invoke the built-in procedurettRepTransmitSetwith argument 1. |
TT8097 | Error getting parent table during autorefresh bookmark lookup | This is a run-time error that indicates that a table that is part of an autorefreshed cache group is missing. |
TT8098 | This built-in is not permitted in an active standby pair scheme | The built-in procedure is not permitted in an active standby scheme. |
TT8099 | 2-safe operation not permitted with AutoCommit = 1. | RETURN TWOSAFEtransactions are not permitted whenAutoCommit=1. |
TT8100 | Invalid parameter value passed in | Check the validity of all parameters passed into the built-in procedure |
TT8101 | ELEMENT element_name specified more than once, being ALTER'ed or DROP'ed with ADD, already exists, or its owner (MASTER or PROPAGATOR) is already the owner for another ELEMENT with the same data store object. | Element names must be unique within a replication scheme. Also, one store cannot be aMASTERorPROPAGATORmore than once for any elements with the same underlying database object. See "Defining replication elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8102 | STORE store_name specified more than once | A store can be specified at most once in aSTOREclause of aCREATE REPLICATIONorALTER REPLICATIONstatement. See "Setting STORE attributes" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8103 | attribute specified more than once or already defined for STORE store_name | A store attribute can be specified at most once in aSTOREclause of aCREATE REPLICATIONorALTER REPLICATIONstatement. See "Setting STORE attributes" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8104 | ALTER or DROP ELEMENT for element following DROP | AnALTER ELEMENTclause cannot follow aDROP ELEMENTclause for the same element in anALTER REPLICATIONstatement. See the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8105 | STORE store_name does not have a MASTER, PROPAGATOR, or SUBSCRIBER role for any ELEMENT | It is permissible to define aSTOREto a replication scheme without assigning it a replication role. However, doing this evokes this warning. |
TT8106 | STORE store_name specified as both owner and SUBSCRIBER for replication ELEMENT element | A store cannot subscribe to the same element for which it is either theMASTERorPROPAGATOR. See the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8107 | Cannot specify both ELEMENT DATASTORE and ELEMENT TABLE or SEQUENCE since the former already covers all objects in the data store | When you specifyELEMENT DATASTORE, all tables are included in the statement. To only specify a particular table or sequence, remove theELEMENT DATASTOREclause and use theELEMENT TABLEorELEMENT SEQUENCEclause. See "Defining replication elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8108 | For TRANSMIT NONDURABLE, must use the ELEMENT element_name DATASTORE clause | Nondurable transmits require anELEMENT DATASTOREclauses. See "Setting transmit durability on data store elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8109 | Element element_name will not have any subscribers | No subscriber specified for the element in the replication scheme. A replicated element must always have at least one subscriber. Either remove the element from the scheme or specify a subscriber for the element. |
TT8110 | Connection not permitted. This store requires Master Catchup. | Master catchup is required for the database. New connections are disallowed until master catchup is complete. |
TT8111 | Connection not permitted. Master Catchup in progress. | Master catchup in progress. New connections not allowed until catchup is complete. |
TT8112 | Operation not permitted. Master Catchup not complete. | An update, insert, delete or alter to a replicated table is not permitted until master catchup is complete. |
TT8113 | Operation not permitted since replication DDL was performed in the transaction. Commit/rollback the transaction. | Replication DDL should be in a transaction of its own. If an operation that is disallowed in the same transaction as replication DDL is attempted, this error is returned. |
TT8114 | Duplicate not permitted. Reason reason. Duplicate is only permitted from the ACTIVE store to the STANDBY store, from the STANDBY store to a SUBSCRIBER, or from the ACTIVE store to a SUBSCRIBER if the STANDBY store has failed. | It occurs when you are trying to perform. a duplicate operation from a node in an active standby store to another and the source node is not in the correct state. The duplicate operation fails. Try duplicating from the correct store, or setting the state of the source store. |
TT8118 | Column column_name of table owner.table_name is longer than the maximum column size of num bytes when used with replication. | The specified column violates the max size limit for replicated columns. The message indicates the maximum limit. |
TT8119 | Set name operation skipped as the new name for the element (element_name) matches the current name. | The new name matches the existing name for the element. If you are attempting to change the element name, supply a unique name to the set operation. |
TT8120 | The TRANSMIT NONDURABLE clause can only be used with a DATASTORE element | This store attribute can only be specified for database replication elements. |
TT8121 | localhost, 127.0.0.1, ::1 or 0:0:0:0:0:0:0:1 cannot be used as a host identifier. | The IP address 'localhost' or any of its aliases cannot be used as a host identifier. |
TT8122 | The replication scheme cannot begin with '_' | An attempt was made to create a replication scheme which begins with `_'. |
TT8123 | An ACTIVE STANDBY PAIR scheme does not exist | ALTER ACTIVE STANDBY PAIRorDROP ACTIVE STANDBY PAIRwas attempted for an active standby pair that does not exist. |
TT8124 | Store DSN has been specified as an ACTIVE STANDBY PAIR node and a SUBSCRIBER | CREATE ACTIVE STANDBY PAIRdesignates a specific database as both a master database and a subscriber database. For example:CREATE ACTIVE STANDBY PAIR rep1, rep2 SUBSCRIBER rep1 |
TT8125 | The store cannot be dropped from the ACTIVE STANDBY PAIR scheme because it is a master node | An attempt was made to drop a master database that is part of an active standby pair. |
TT8126 | An ACTIVE STANDBY PAIR scheme already exists and must be the only replication scheme for the store. | A database cannot be in two active standby pairs. An attempt was made to create an active standby pair using a database that is already in an active standby pair. |
TT8127 | Cannot create ACTIVE STANDBY PAIR scheme because another replication scheme already exists. | An attempt was made to create an active standby pair, but a replication scheme already exists. |
TT8128 | Store DSN is already in the ACTIVE STANDBY PAIR scheme. | ALTER ACTIVE STANDBY PAIRattempts to add a database that is already in the active standby pair. |
TT8129 | Store DSN: The "attribute_name" attribute cannot be set for DSN in an ACTIVE STANDBY PAIR scheme. | Only thePORTandTIMEOUTattributes can be set for subscribers. |
TT8130 | CREATE ACTIVE STANDBY PAIR must only be run on one of the MASTER nodes. | TheCREATE ACTIVE STANDBY PAIRstatement must be run from one of the nodes on which a master database resides. For example,CREATE ACTIVE STANDBY PAIR rep1, rep2 SUBSCRIBER rep3must be run from the node on whichrep1orrep2resides. |
TT8131 | Table owner.name is already part of the replication scheme, or is in the process of being included | An attempt is made to add a table to a replication scheme, but the table is already part of the replication scheme or is already in the process of being added to the replication scheme. |
TT8132 | {INCLUDE|EXCLUDE} element_name cannot be used on TABLE element element_name. The operation is for DATASTORE level elements only | An attempt was made to include or exclude a table-level element. |
TT8133 | You cannot {include|exclude} table owner.name because it is part of a cache group. Use {INCLUDE|EXCLUDE} CACHE GROUP instead. | An attempt was made to include or exclude a cache group table. |
TT8134 | Store DSN is not a MASTER for any element. | TheALTER ELEMENTstatement did not find a matching element name in the database. |
TT8135 | Object_type owner.name is not part of DATASTORE element element_name, or is in the process of being excluded | An attempt was made to exclude a table or sequence that is not in the replication scheme or that is already in the process of being excluded. |
TT8136 | All tables or cache groups cannot be excluded from element element_name. Use DROP ELEMENT instead. | An attempt was made to exclude all tables or cache groups from an element. There must be at least one object in an element. |
TT8137 | Cannot exclude object_type owner.name because it is not in the Active Standby scheme. | An attempt was made to exclude a table or sequence from the databases by using anALTER ACTIVE STANDBY PAIR...EXCLUDEstatement, but the table or sequence is not in the active standby pair. |
TT8138 | All tables or cache groups cannot be excluded from the ACTIVE STANDBY PAIR scheme | An attempt was made to exclude all tables and cache groups from the databases in anALTER ACTIVE STANDBY PAIR...EXCLUDEstatement. |
TT8139 | The specified peer store is not in the standby state | An operation was attempted for a store that was not in a standby state. The operation is only permitted on stores that are in the standby state. |
TT8140 | Scheme does not exist or inconsistency detected in the local ACTIVE STANDBY PAIR scheme | Error returned for an store with an inconsistent or corrupted active standby replication scheme. |
TT8141 | Local store not eligible to be set to the active state | Local database that is part of an active standby pair is not eligible to be set to the active state. |
TT8142 | Error checking on store header attributes | An error occurred while reading the database header for attributes related to the active standby replication scheme. |
TT8143 | The standby can only be duplicated from the active | A database that is in the standby state for an active standby pair can be duplicated only from the active database. |
TT8144 | Duplicate only allowed from a standby store or from an active when the standby has failed | Subscriber databases in a active standby pair can be duplicated only from the standby database or from the active database when the standby database is in a failed state. |
TT8145 | The local store needs to be in the active state for this operation. | A database that is part of an active standby pair must be in the active state. |
TT8146 | There can be only one INCLUDE or EXCLUDE clause for object_type. | There can be only oneINCLUDEorEXCLUDEclause for an object type (cache group or table). For example, the following is invalid:ALTER ACTIVE STANDBY PAIR INCLUDE TABLE t EXCLUDE table u. |
TT8147 | INCLUDE and EXCLUDE can only be used on DATASTORE level elements. | An attempt was made to use anINCLUDEorEXCLUDEclause with a table element definition in aCREATE TABLEorCREATE ACTIVE STANDBY PAIRstatement. |
TT8148 | Host name exceeds limit of num characters | The size exceeds the maximum permitted limit. The message indicates the maximum limit. |
TT8149 | Data store name exceeds limit of max_num characters | The size exceeds the maximum permitted limit. The message indicates the maximum limit. |
TT8150 | This change is not allowed while the replication agent for data store data_store_name is running. Stop the replication agent to perform. this change. | Most replication scheme changes are not allowed while the replication agent is in the start state. For a list of supported scheme changes, see "Altering Replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8151 | owner.name's replication role disallows the requested operation | Replication denies write access to a database object underlying a replication element for which it is a subscriber or propagator, provided that the local store is not the master for any other element with the same underlying database object. |
TT8152 | No ODBC type for column owner.name.column | The type for a column in a replicated table could not be mapped to a known ODBC data type. See "Data Types" in the Oracle TimesTen In-Memory Database SQL Reference. |
TT8153 | Store store_name already owns (is MASTER or PROPAGATOR of) specified ELEMENT(s) | It is permissible to useALTER REPLICATION ALTER ELEMENT SET OWNERto reassign an element to its current owner (MASTERorPROPAGATOR). However, doing this evokes this warning |
TT8154 | REPLICATION scheme owner.name already exists | TheCREATE REPLICATIONstatement requires that each new replication scheme specified to a store have a differentowner.namefrom any replication scheme already defined there. |
TT8155 | ELEMENT element_name already has SUBSCRIBERsubscriber_name | A store can subscribe to a replication element only once. See "Defining replication elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8156 | Internal error: Column column_name for ELEMENT element_name already defined for SUBSCRIBERsubscriber_name | Replication caught itself trying to re-add column information for a replicated table. This is an internal error. Contact TimesTen Technical Support. |
TT8157 | No elements element_name found for REPLICATION owner.name | A replication element could not be found for the requested operation. This is a warning when the request is for an indefinite number of elements (* INstore_name). It is an error when the statement specifies one particular element. |
TT8158 | Failed to retrieve LSN data for initializing PEER | AMASTERorPROPAGATORstore could not get its local LSN to initialize a (subscribing) peer store. |
TT8159 | No SUBSCRIBER PEER information found for REPLICATION owner.name for MASTER or PROPAGATOR store store_name | It is permissible for there to be no peers to delete for aDROP REPLICATIONrequest. However, doing this evokes this warning. |
TT8160 | REPLICATION owner.name not found | The local store does not know about the replication scheme specified in anALTER REPLICATIONorDROP REPLICATIONrequest. (It is not registered in theTTREP.REPLICATIONStable.) |
TT8161 | No STORE store_name found for REPLICATION owner.name | Database was not found for theSTOREspecified in anALTER REPLICATION ALTER STOREorDROP REPLICATIONrequest. |
TT8162 | No subscriptions found for ELEMENT element_name in REPLICATION owner.name | No subscriptions could be found for an element in anALTER REPLICATION DROP ELEMENT,ALTER REPLICATION ALTER ELEMENT DROP SUBSCRIPTION,ALTER REPLICATION ALTER ELEMENT SET OWNERorDROP REPLICATIONrequest. |
TT8163 | Failed to retrieve table or column descriptor for table owner.name | While trying to create a replication element forCREATE REPLICATIONorALTER REPLICATION ADD ELEMENT, this information about the underlying table could not be retrieved. |
TT8165 | Replication schema is inconsistent | Replication has noticed an inconsistency in its schema. This is an internal error. Contact TimesTen Technical Support |
TT8166 | Log not writeable or transaction not initiated by system | Replication DDL requests require that transaction logging be enabled for transaction rollback. This error is returned if logging is disabled. |
TT8167 | Cannot determine system table attributes (e.g. REPACCESS) for table from replication role | Internal error. Contact TimesTen Technical Support. |
TT8168 | Cannot set system table attributes (e.g. REPACCESS) for table from replication role | Internal error. Contact TimesTen Technical Support. |
TT8169 | Store transmitting_store ON ransmitting_host already transmits to store receiving_store ON receiving_host; at most one path allowed from one store to another | An attempt was made to configure a replication scheme with an element that has the same master or propagator and subscriber as an element in another replication scheme. Two such elements must reside in the same replication scheme. See "Defining replication elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8170 | Receipt or commit acknowledgement not returned in the specified timeout interval | A subscriber withRETURN RECEIPTorRETURN TWOSAFEservice did not receive a commit acknowledgement within the current connection time limit. This can occur when the subscriber Replication Agent is not running or f the standby replication state is set toSTOPPED. For an active standby pair, this can occur when the standby replication agent is not running and the standby has not been declared as "failed" on the active. You can adjust the connection time limit with a call tottRepSyncGet, as described in "Managing return service timeout errors and replication state changes" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8171 | Illegal to replicate a system table system_table_name | At attempt was made to specify as a replicated object one of theSYS.*orTTREP.*tables that the system creates and maintains. These tables cannot be replicated. |
TT8172 | The store store_name ON host_name_1 is already specified with an equivalent host name as store_name on host_name_2 | Two different forms of host name were used to refer to one particular store in a replication scheme. The same form. of host name must be consistently used to refer to any one database. |
TT8173 | Replication may not be configured while XA transactions are active | TimesTen Replication is not supported with XA transactions. |
TT8174 | attribute specified more than once | You have specified more than one value for an attribute. Remove one of the instances of the attribute specification. |
TT8175 | Report file name report_name cannot be resolved | An attempt to configure a conflict resolution report file to a non existent directory failed. Use a valid path to the report file |
TT8176 | Conflict checking configuration conflict between elements element_name and element_name with the same underlying table | TimesTen cannot configure a partial database replication because a replication scheme already exists that covers the entire database. UseDROP REPLICATIONto drop the existing replication scheme andCREATE REPLICATIONto create a new replication scheme. |
TT8177 | Executing store (store_name) not permitted to operation_name | TimesTen cannot drop the replicating element because the specified replication scheme covers the entire database and theTRANSMIT NONDURABLEoption is set. If needed, drop the replication scheme and use aCREATE REPLICATIONstatement to create a new replication scheme. |
TT8178 | Cannot set a subscriber to state code code_number | TimesTen cannot specify theTRANSMIT NONDURABLEoption for the replication scheme because the scheme does not cover the entire database. TheNONDURABLEoption must apply to the entire database. If needed, drop the replication scheme and use aCREATE REPLICATIONstatement to create a new replication scheme, using theELEMENT DATASTOREclause with theTRANSMIT NONDURABLEoption. See "Setting transmit durability on databease elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8179 | Cannot create dupicate store: store already exists | This error message indicates that the user is attempting to overwrite an existing database during an operation to duplicate databases. |
TT8180 | Full versus partial replication conflict with an existing replication scheme on data store data_store_name | When aDATASTOREelement is used on a particular database for replication, no other element type can be used either in the same scheme or in any other scheme. See "Defining data store elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8181 | Cannot create table or alter replication because data store data_store_name is covered by a full datastore replication scheme | When aDATASTOREelement for replication is present in a database no other new element type can be introduced. See "Defining data store elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8182 | Cannot configure conflict checking on DATASTORE element | To configure conflict resolution for replicationDATASTOREelements cannot not be used. Replication must to be configured for each individual table. See "Resolving replication conflicts" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8183 | Cannot alter element because it is owned and managed by the system | ALTER REPLICATIONcannot be run on elements created as part of theDATASTOREelement configuration.ALTER REPLICATIONmust be run on theDATASTOREelement itself. |
TT8184 | Attempt to configure replication_type replication for a store with no permanent objects | An attempt was made to configure database-level replication or active standby replication with an empty database. |
TT8185 | Attempt to exceed limit for return receipt receivers | Number of subscribers to receiveRETURN RECEIPTreplication updates exceeds the system specified limit. |
TT8186 | Replication agent not responding to Return Receipt transactions | The replication agent is not processing return receipt replication updates. |
TT8187 | A Return receipt transaction has not been executed on this connection | A transaction with return receipt replication updates has not been run on the connection. |
TT8188 | Transaction handle not valid | The handle for examining the status of a transaction withRETURN RECEIPTreplication is not valid. |
TT8189 | Transaction token subscriber information not available | The replication subscriber cannot be found in the replication scheme. |
TT8190 | Host name host could not be resolved | The host name specified cannot be resolved on this host. Check the host name for correctness or make changes to the network host name lookup. See "Configuring host IP addresses" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8191 | This store store_name on host_name not involved in a replication scheme | The replication agent does not start if the database does not participate in any replication scheme. Either no replication scheme is defined on this store or the store is not part of any replication scheme. If a replication scheme is defined, verify that the name of each database involved in replication matches the names specified in theDataStoreattribute in their respective DSN definitions. This name may be different from the names specified for theData Source Nameattribute in the DSNs. This error might also occur if the replication agent cannot determine that the current running host is involved in the specified replication scheme. Confirm that you have correctly identified your database hosts, as described in "Configuring host IP addresses" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8192 | Dropping/adding a foreign key that references a replicated table is not allowed while the replication agent for data store store_name is running. Stop the replication agent to perform. this operation | You cannot add or drop a foreign key in a table that references a replicated table. Stop the replication agents, add or drop the foreign key in the table that references the replicated table, and restart the replication agents. See "Starting and stopping the replication agents" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for details on how to stop and restart the replication agents. |
TT8193 | The TWOSAFE subscriber attribute is only permitted on a DATASTORE element. | Attempt to configureRETURN TWOSAFEwith a table element. Change theELEMENTtype toDATASTOREor removeRETURN TWOSAFEfrom the replication scheme. For more information, see "Return twosafe replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8194 | The TWOSAFE subscriber attribute is not permitted on a propagator element. | Attempt to configureRETURN TWOSAFEfor a propagator database. TheRETURN TWOSAFEservice can't be used in a propagation scheme. See "Return twosafe replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for details. |
TT8195 | The TWOSAFE subscriber attribute requires an exclusive bi-directional configuration. | Attempt to configureRETURN TWOSAFEin an invalid replication scheme.RETURN TWOSAFEcan only be used in a bi-directional scheme between a master and a single subscriber database. See "Return twosafe replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for details. |
TT8196 | Remote application of the transaction ran into error : error_description. Rollback the transaction. | TheRETURN TWOSAFEtransaction ran into an error when it was applied on the subscriber. The transaction was not applied to the subscriber and must be rolled back on the master. |
TT8197 | Operation not permitted once commit processing has begun | A commit call has already been issued for thisRETURN TWOSAFEtransaction. Therefore the operation is not permitted. |
TT8198 | A 2-safe transaction has not been executed on this connection | Attempt to get the replication status of aRETURN TWOSAFEtransaction when none has been executed. |
TT8199 | A 2-safe or return receipt transaction has not been executed on this connection | The above is usually returned when attempting to get the replication status of aRETURN TWOSAFEorRETURN RECEIPTtransaction when none has been executed. |
TT8200 | Attempt to drop all columns in table | An application cannot drop all columns in a table. Consider usingDROP TABLEto drop the table instead. |
TT8201 | Column is part of the table's primary key | An application cannot drop a column that is part of a primary key. Consider dropping and recreating the table. |
TT8202 | Column is part of a foreign key | An application cannot drop a column that is part of a foreign key. Consider dropping and recreating the table. |
TT8203 | Attempt to drop indexed column | Application attempted to drop an indexed column in a table. Consider dropping the index and then dropping the column. |
TT8204 | Columns have been added to table too many times | The operation is not permitted because the table would have more than the maximum number of partitions. As described in Oracle TimesTen In-Memory Database SQL Referenceference, the maximum number of partitions for a table cannot exceed 255. Consider rebuilding the table, either usingINSERT SELECTor by using thettBulkCputility. |
TT8206 | Invalid parameter value STANDBY passed in. The command failed. | Indicates that an invalid input parameter has been passed in to an active standby pair. |
TT8207 | Illegal to replicate a system sequence (owner.sequence) | Objects owned bySYSandTTREPare system objects. Users cannot perform. operations on these items, including involving them in a replication scheme. Remove the sequence from your replication scheme. |
TT8210 | Table reference of table_name is ambiguous | More than one table with a matching foreign key constraint was found. Qualify all references to other tables with an owner name. |
TT8211 | Table table_name is not a member of the cache group | No tables external to the cache group may be referenced by a foreign key constraint from within the cache group. See "Cache groups and cache tables" in the Oracle In-Memory Database Cache User's Guide. |
TT8212 | Multiple foreign keys defined for table table_name | Foreign keys for a cache group table have been found to refer to more than one table. All foreign keys for a cache group table may only refer to a single table within the same cache group. See "Cache groups and cache tables" in the Oracle In-Memory Database Cache User's Guide. |
TT8213 | Cache group tables must have a primary key | All tables within a cache group must have a primary key. See "Cache groups and cache tables" in the Oracle In-Memory Database Cache User's Guide. |
TT8214 | Cache source cache_name is not supported | Cache group tables currently work only with Oracle data sources. |
TT8217 | Invalid duration value | A cache group duration must be a positive integer. |
TT8220 | Table table_name is both read only and propagated | Cache group tables may not be simultaneously marked as bothREADONLYandPROPAGATE. See "PROPAGATE cache table attributes" in the Oracle In-Memory Database Cache User's Guide. |
TT8221 | No parent table found | No table in the cache group was found to be a root table. Only one table in a cache group may have any foreign key constraints. All other tables in a cache group must refer to a single table within the same cache group. See "Cache groups and cache tables" in the Oracle In-Memory Database Cache User's Guide. |
TT8222 | Multiple parent tables found | Multiple potential root tables were found within the cache group. Only one table in a cache group may have foreign key constraints. All other tables in a cache group must refer to a single table within the same cache group. See "Cache groups and cache tables" in the Oracle In-Memory Database Cache User's Guide. |
TT8223 | A referenced primary key is not found in the associated parent table | The referenced primary key was not found in the cache group. See "Cache groups and cache tables" in the Oracle In-Memory Database Cache User's Guide. |
TT8224 | Cache group cache_name already exists | Attempting to create a cache group which already exists. |
TT8225 | Table table_name is read only | Tables within a cache group which are marked asREADONLYmay not be updated. |
TT8226 | Column column_name is read only | Internal error. Contact TimesTen Technical Support. |
TT8227 | Cache group cache_name not found | The referenced cache group does not exist. |
TT8228 | Cannot drop cache group table table_name; pleaes use DROP CACHE GROUP instead | Tables within a cache group may not be explicitly dropped using theDROP TABLEstatement. |
TT8229 | Memory threshold value must be between 0 and 100 | The cache group aging memory threshold must be a percentage value between zero and 100. |
TT8230 | Aging interval value must be greater than zero | The cache group aging interval must be a value greater than zero. |
TT8231 | Cache groups are not supported on this platform | Cache groups are not supported in this version of the product. For a list of supported platforms see the Oracle In-Memory Database Cache User's Guide. |
TT8232 | Oracle PassThrough not supported on this platform. PassThrough value must be set to 0 | ThePassThroughattribute is not supported on this platform. For a list of supported platforms see the Oracle In-Memory Database Cache User's Guide. |
TT8233 | PassThrough value must be between 0 and 5 | Incorrect value for thePassThroughattribute. Reset to a value between 0 and 5, as described in "Setting a passthrough level" in the Oracle In-Memory Database Cache User's Guide. |
TT8234 | PassThrough command is no longer valid. One possible cause is creation of a new table on the TimesTen data store | After creating a table in TimesTen, including a cache group table, all prepared passthrough statements are invalidated, until reprepared. This error indicates that the application is trying to use an invalidated statement.The application must prepare the passthrough statement after creating a table or cache group. |
TT8235 | Number of WITH ID keys values does not match the primary key columns for cache group cache_name | The number of values given in theWITH IDclause does not match the number of primary key columns defined on the root table of the cache group. |
TT8236 | Invalid commit value | A commit interval for aLOAD CACHE GROUPorMERGEstatement on a cache group must be a positive integer value. |
TT8237 | Cache group WHERE clauses must be less than number bytes long | EachWHEREclause of a cache group may not exceed the maximum byte length specified in the error message. |
TT8238 | Cannot truncate cache group table table_name; Use DROP/REFRESH/ UNLOAD CACHE GROUP instead. | ATRUNCATEstatement is not allowed on a cache group table. |
TT8239 | PROPAGATE syntax can only be used once in statement | This is a syntax error for theCREATE CACHE GROUPstatement. You specified aPROPAGATEorNOT PROPAGATEclause on a cache table that already has been specified as eitherPROPAGATEorNOT PROPAGATE. Check the syntax and remove the redundant or contradictoryPROPAGATEorNOT PROPAGATEclause. |
TT8240 | READONLY syntax can only be used once in statement | This is a syntax error for theCREATE CACHE GROUPstatement. You specified theREADONLYkeyword twice for the same cached table. Remove one of the instances ofREADONLY. |
TT8242 | Index on name column not supported | You cannot create an index on columnnamebecause it is a system-created column. |
TT8243 | Invalid AUTOREFRESH interval value | The specifiedAUTOREFRESH INTERVALis invalid. It must be a positive integer. |
TT8244 | Cannot alter AUTOREFRESH status of a cache group which was not initially created with AUTOREFRESH | For a cache group'sAUTOREFRESHsetting to be altered, it must be created with theAUTOREFRESHclause. For example, you cannot create a cache group without anAUTOREFRESHclause and later try to modify it toAUTOREFRESH STATE ON. |
TT8247 | The ttCGGenSQL built-in procedure requires that the cache group was initially created with AUTOREFRESH | ThettCacheSqlGetbuilt-in procedure cannot be called on a cache group that was created without anAUTOREFRESHclause |
TT8248 | Cache group cache_group_name is not currently being autorefreshed | EitherAUTOREFRESHstate is off orAUTOREFRESHhas been stopped because of a fatal error during refresh. Check user error log to find cause for refresh failure. |
TT8249 | Cache agent is shutting down autorefresh for cache group cache_group_name. Please try again | WhenAUTOREFRESHis deactivated either by dropping the cache group or by altering the state to off, the TimesTen cache agent takes some time before theAUTOREFRESHis completely shutdown. An application may not be able to reactivate (create the same cache group or alter the state toON/PAUSE) that cache group while it is being shut down. The application must wait forAUTOREFRESHto completely shut down before it can be reactivated. |
TT8252 | Table table_name is both read only and not propagated | The cache group table,table_name, cannot be specified as bothREADONLYandNOT PROPAGATE. This error can occur if you try to create aREADONLYcache group that contains a table that is specified asNOT PROPAGATE. |
TT8253 | Table table_name cannot have same name as an existing cache group or the cache group containing this table | Cache groups and tables cannot have the same name. You see this error when you try to create a cache group or a table that has the same name as another table or cache group. To correct the error, use a different name in theCREATE CACHE GROUP/TABLEstatement. |
TT8254 | Flush fails; all tables are either propagated or read only | This error occurs if you useFLUSH CACHEGROUPon a cache group where all of its tables are configured withPROPAGATEorREADONLYand therefore not flushable. You can flush a table that is markedPROPAGATEby using thettCachePropagateFlagSetbuilt-in procedure. |
TT8255 | Attempt to bi-directionally propagate multiple copies of cache group cache_group | You can create any number of cache groups that are bi-directionally propagated as long as the names of the cache groups are different and no bi-directionally propagated table appears in more than one cache group. IMDB Cache has this restriction to avoid update conflict anomalies. To correct the error, choose a different name for one of the cache group.In very rare instances, IMDB Cache falsely reports this error. The most likely cause is that there are some residual Oracle objects that were created by IMDB Cache but were not dropped when the cache group was dropped or the cache agent was shutdown. For more about the Oracle objects created by IMDB Cache, see "Oracle objects used to manage a cached environment" in the Oracle In-Memory Database Cache User's Guide. |
TT8256 | Illegal subquery used in create cache group table WHERE clause | Sub-queries are not allowed in theWHEREclause of theCREATE CACHE GROUPstatement. To correct the error, remove the sub-query. For more information, see "Using a WHERE clause" in the Oracle In-Memory Database Cache User's Guide. |
TT8257 | Parameters are not supported in Oracle WHERE clauses | Parameter binding ("?") is not allowed in theWHEREclause ofLOAD CACHE GROUPandMERGEstatements. Use SQL literals instead. For more information, see "Using a WHERE clause" in the Oracle In-Memory Database Cache User's Guide. |
TT8259 | WHERE clause does not match | You must specify identicalWHEREclauses in cache group definitions for replicating cache groups. You must: stop replication, delete the replication definitions, drop the cache groups, recreate the cache group definitions with the sameWHEREclauses, recreate replication definitions and restart replication. For more information, see "Cache groups and replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8260 | Join predicate does not match | The root/child tables in one cache group aren't joined in the same manner as the root/child tables in that cache group's replicated counterpart.You must specify identicalJOINpredicates in the cache group definitions for replicating cache groups. You must: stop replication, delete the replication definitions, drop the cache groups, recreate the cache group definitions, recreate replication definitions and restart replication. See "Cache groups and replication" of the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8261 | Cache groups operations may not be performed while XA transactions are alive | There is an active XA transaction. No cache operations are allowed when there is an XA transaction accessing the database. These two TimesTen features cannot be used at the same time. The XA and JTA APIs described in the TimesTen developer guides are not supported in cache groups. See "Summary of compatibility issues" in Oracle In-Memory Database Cache User's Guide. |
TT8262 | A READONLY or WRITETHROUGH cache group can only replicate to a cache group of the same type | Attempted to replicate a readonly or writethrough cache group to a database with another type of cache group. When replicating between cache groups, only one cache group can be specified asAUTOREFRESH. In addition, the other cache groups must be markedREADONLY. See Oracle In-Memory Database Cache User's Guide. |
TT8263 | If a replicating cache group has AUTOREFRESH specified than the remote cache group must also specify AUTOREFRESH | Replicated cache groups must both haveAUTOREFRESHset, though the subscriber must have theAUTOREFRESH STATE OFF. See "Cache groups and replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8264 | Transaction commit/rollback succeeded on Oracle but failed on TimesTen | Updates were successfully propagated to Oracle but failed on TimesTen. If a commit or rollback succeeds on Oracle but fails on TimesTen, the data in the TimesTen cache group may no longer be synchronized with the data in Oracle. After clearing up the cause of the TimesTen failure, it may be necessary to re-apply the failing transaction in TimesTen. See the discussion onPROPAGATEin the Oracle In-Memory Database Cache User's Guide. |
TT8265 | To use AUTOREFRESH, all of the tables in the cache group must be READONLY or all the tables in the cache group must be PROPAGATE | You cannot specifyAUTOREFRESHwith propagation disabled (NOT PROPAGATE). A cache group that is usingAUTOREFRESHmust be marked eitherPROPAGATEorREADONLY. By default, cache tables are markedNOT PROPAGATE. If the cache group is notREADONLY, you must explicitly mark each table eitherPROPAGATEorREADONLY. This is to avoid overwriting changes during the next C operation. See the discussions onAUTOREFRESHandPROPAGATEin the Oracle In-Memory Database Cache User's Guide. |
TT8268 | Asynchronous or Synchronous Writethrough cache group cannot have a WHERE clause | TheCREATE SYNCHRONOUS WRITETHROUGH CACHE GROUPstatement or theCREATE ASYNCHRONOUS WRITETHROUGH CACHE GROUPspecifies aWHEREclause on at least one of its tables, which is not allowed. This is a compile time error message. See "Cache group types" in the Oracle In-Memory Database Cache User's Guide for a description of asynchronous writethrough cache groups and synchronous writethrough cache groups. |
TT8270 | Table level READONLY/NOT PROPAGATE/PROPAGATE flags are not allowed in a System Managed cache group | The table-levelREADONLYandPROPAGATEattributes cannot be used in system-managed cache groups. This is a compile time error. See "Cache group types" in the Oracle In-Memory Database Cache User's Guide. |
TT8271 | Manual LOAD/UNLOAD/REFRESH/FLUSH operations are not allowed on cache group cache_name because it is system managed | TheLOAD CACHE GROUP,UNLOAD CACHE GROUP,MERGE, andFLUSH CACHE GROUPstatements cannot be used on system-managed cache groups. This is a runtime error. See "Cache group types" in the Oracle In-Memory Database Cache User's Guide. |
TT8273 | At least one of the local or remote cache groups must set autorefresh STATE to OFF or PAUSED | When replicating to a cache group, theAUTOREFRESHstate of the cache group must be set toOFF. |
TT8274 | If a replicating cache group has both AUTOREFRESH and PROPAGATE then the remote cache group must set autorefresh STATE to OFF | When replicating from a user managed cache group that is specified as bothAUTOREFRESHandPROPAGATE, to another cache group that is specified withAUTOREFRESHonly, the second cache group must have theAUTOREFRESH STATEset toOFF. To enable replication, you must first setALTER CACHE GROUPand setAUTOREFRESH STATE OFFon the cache group that currently hasAUTOREFRESHon or paused. See "Cache groups and replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8275 | Manual LOAD/UNLOAD/REFRESH/FLUSH operations are not allowed on cache group cache_group_name because it uses AUTOREFRESH | The manualLOAD CACHE GROUP,UNLOAD CACHE GROUPorFLUSH CACHE GROUPstatement failed because the cache group is specified withAUTOREFRESH. This is not allowed. |
TT8277 | If a cache group on the receiver has AUTOREFRESH specified then the corresponding cache group on the transmitter must also specify AUTOREFRESH | When replicating to a subscriber cache group withAUTOREFRESH STATE OFF, the master cache group must specify theAUTOREFRESHattribute with either theSTATE ONorOFF. See "Cache groups and replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8278 | Cache groups with AUTOREFRESH and PROPAGATE can only be replicated if both the transmitter and receiver cache groups have autorefresh STATE set to OFF | The subscriber cache group must haveAUTOREFRESH STATE OFF. See "Cache groups and replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8279 | If a transmitting cache group has AUTOREFRESH and the receiving cache group has PROPAGATE then transmitting cache group must also have PROPAGATE | Attempt to replicate from a cache group withAUTOREFRESHspecified butPROPAGATEnot specified to a cache group withPROPAGATEspecified. For details on how to replicate cache groups, "Replicating cache tables" in the Oracle In-Memory Database Cache User's Guide and "Cache groups and replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide. |
TT8287 | Manual LOAD/REFRESH operations with WHERE or WITHID clauses are not allowed on cache group cache_group_name because it is specified as AUTOREFRESH | Issued during aLOADorREFRESHcache group operation on an autorefresh cache group. ALOADorREFRESHoperation cannot have aWHEREclause orWITH IDclause for an autorefresh cache group. |
TT8288 | Manual LOAD of cache group cache_group_name is not allowed because it is specified as AUTOREFRESH and it is not empty | This error is issued during aLOAD CACHE GROUPoperation on anAUTOREFRESHcache group. ALOAD CACHE GROUPoperation cannot be performed on a non-emptyAUTOREFRESHcache group.REFRESHcache group can be used instead. |
TT8289 | Manual LOAD/REFRESH of cache group requires AUTOREFRESH STATE to be PAUSED, but the STATE of cache_group_name is state. The LOAD is not allowed. | This error is issued during aLOADorREFRESH CACHE GROUPoperation on anAUTOREFRESHcache group.AUTOREFRESH STATEmust bePAUSEDwhen issuingLOADorREFRESHcache group statements. |
TT8290 | Manual LOAD/REFRESH must have COMMIT EVERY N ROWS clause | This error is issued during aLOADorREFRESH CACHE GROUPoperation. To solve this problem, specify aCOMMIT EVERY N ROWSclause in the statement. |
TT8291 | Manual LOAD/REFRESH WITH ID statement cannot have the COMMIT EVERY N ROWS clause | This error is issued during aLOADorREFRESH CACHE GROUPoperation. ACOMMIT EVERY N ROWSclause cannot be specified when aWHEREorWITH IDclause is used. |
TT8292 | The cache group where clause contains a subquery. Changes of the subquery result may not be tracked by INCREMENTAL AUTOREFRESH | An autorefresh cache group has a subquery in theWHEREclause. IncrementalAUTOREFRESHdoes not track any changes of the subquery result list. Accordingly, IMDB Cache may not cache the result rows as specified by the cache groupWHEREclause. |
TT8293 | Autorefresh interval should be at least num milliseconds | TheAUTOREFRESHinterval should be at leastnummilliseconds. Currently the minimum number of milliseconds allowed for theAUTOREFRESHinterval is 10. |
TT8294 | Replication not allowed from a non-cache group table to a READONLY cache group table | You cannot replicate from a non-cache table to a table in aREADONLYcache group. |
TT8295 | To use NCHAR/NVARCHAR values through Cache Connect, Oracle Database national character set must be AL16UTF16 | To useNCHAR/NVARCHAR2types in a a cache group table column or a passthrough statement, the Oracle database national character set must beAL16UTF16. You can use SQL*Plus to connect to the Oracle database and issue the following query to check the database national character set: SELECT VALUE FROM v$nls_parameters WHERE PARAMETER = 'NLS_NCHAR_ CHARACTERSET'; |
TT8296 | TimesTen and Oracle database character sets do not match. TimesTen: database_character_set, Oracle: database_character_set | TimesTen databases that use cache groups or provide passthrough must have the same database character set as the Oracle database. TheDatabaseCharacterSetof the database cannot be changed after creation. |
TT8297 | The session parameter parameter cannot be altered through a PassThrough statement | TimesTen does not support passthrough execution of the indicatedparameterin a SQLALTER SESSION SETstatement. |
TT8298 | Table in autorefresh cache group cannot have more than num columns | The maximum number of columns in an autorefresh cache group table is 999. Generally TimesTen supports tables that contain up to 1000 columns. |
TT8299 | Cache Connect database character set cannot be TimesTen8 | TheTIMESTEN8database character set cannot be specified for databases that are used with cache groups. |
TT8302 | Autorefresh state of cahe group cache_group_name is off | TheAUTOREFRESHstate for the cache group isOFF. To performAUTOREFRESHoperations, set the state toON. |
TT8303 | Sequence number must be non-negative and end sequence must be greater than or equal to start sequence | A sequence number must be positive and must be greater than or equal to the first number in the sequence. |
TT8304 | Manual REFRESH operation with WHERE clause is not allowed on cache group cahegroup_name because it is specified as dynamic AUTOREFRESH | Refresh operations are automated on the dynamic autorefresh cache group. You have attempted to perform. a manual refresh operation. It is not supported. |
TT8305 | Manual LOAD/REFRESH on cache group failed because dynamic counter update failed. | Manual load or refresh of a dynamic cache group failed because of the failure in updating the internal dynamic counter. This could be because of another operation holding a lock on the row for this cache group in theSYS.CACHE_GROUPtable. |
TT8306 | A cache group cannot be created as dynamic if it is defined as both autorefresh and propagate | A dynamic user managed cache group cannot use both the autorefresh cache group attribute and thePROPAGATEcache table attribute. |
TT8307 | Autorefresh interval cannot exceed 99 days | Create the cache group with anAUTOREFRESHinterval less than or equal to 99 days. |
TT8308 | All replicated autorefresh cache groups should have autorefresh state PAUSED before calling ttRepDeactivate. | This error can occur when a user calls the built-inttRepDeactivate. The error is triggered when there are some replicated autorefresh cache groups where state isONand the cache agent is running. Alter the replicated autorefresh cache groups on the active node (to be deactivated) to thePAUSEDstate. |
TT8309 | Manual REFRESH with PARALLEL clause is not allowed for dynamic readonly cache groups. | Refresh cache group statement was allowed to have parallel clause for refreshing a dynamic read only cache group. It is disabled in this release. |
TT8311 | To set the number of parallel AWT applier threads, ReplicationParallelism must be set to > 0 | You cannot configure CacheAwtParallelism to be greater than 1 if ReplicationParallelism is 0. |
TT8312 | CacheAWTParallelism value of cache_value must be greater than or equal to ReplicationParallelism value of replication_value | CacheAwtParallelism must always be greater than or equal to ReplicationParallelism. |
TT8313 | Cannot use parallel replication or parallel AWT with SMPOptLevel=0 | Parallel Replication or Parallel AWT cannot be configured for a database with SMPOptLevel set to 0. |
TT8314 | ReplicationParallelism cannot be greater than 1 with ReplicationApplyOrdering set to 0 | You cannot set ReplicationParallelism to a greater than 1 value when ReplicationApplyOrdering is set to 0. |
TT8315 | Timeout in commit wait for parallel AWT thread | The parallel AWT applier thread timed out waiting for a dependent AWT applier to commit. |
TT8316 | Creation of AWT cache groups is disabled with ReplicationApplyOrdering set to 1 | |
TT8400 | System catalog creation failed: failure_message | When a TimesTen database is created, a number of predefined tables and views are defined in the new database. An error occurred in the process of defining these objects. Review the included message, make suggested corrections and attempt database creation again. |
TT8500 | PL/SQL feature not installed in this TimesTen instance | You have attempted to use a PL/SQL feature, but PL/SQL was not enabled for TimesTen at install time. PL/SQL features not supported unless PL/SQL was enabled for the TimesTen instance. To use PL/SQL, it is necessary to re-install TimesTen and enable PL/SQL at install time. |
TT8501 | PL/SQL feature not installed in this TimesTen database | You have attempted to use a PL/SQL feature, but PL/SQL was not enabled for TimesTen at install time. PL/SQL features not supported unless PL/SQL was enabled for the TimesTen instance. To use PL/SQL, it is necessary to re-install TimesTen and enable PL/SQL at install time. |
TT8502 | Error Error_number initializing PLSQL_MEMORY string | Internal error. Contact TimesTen Technical Support. |
TT8503 | Error_text | An error occurred while the PL/SQL compiler was compiling an anonymous block. The text of the error message references an ORA error number from the Oracle error documentation. In general, diagnosis is the same for PL/SQL in TimesTen and for PL/SQL in Oracle, though there are known differences between PL/SQL in these two environments. |
TT8504 | PL/SQL object_type object created with compilation warnings | This is a warning. A PL/SQL block specified in aCREATEorREPLACEprocedure, function or package statement cannot be compiled due to a syntax problem or other problem. |
TT8505 | PL/SQL object_type object created with compilation errors | This is an error. A PL/SQL block specified in aCREATEorREPLACEprocedure, function or package statement cannot be compiled due to a syntax problem or other problems. |
TT8506 | error_text | You have received this error for one of the following reasons:An attempted operation, such asCOMMIT,ROLLBACK, or other DDL statement, cannot proceed because of a conflict with an existing PL/SQL object. An unexpected error occurred while attempting to manage memory or locks in thePLSQL_memoryarea.
|
TT8507 | error_text | An error occurred while a PL/SQL subprogram is executing or while invoking the PL/SQL compiler. The text of the error message references an ORA error number from the Oracle error documentation. In general, diagnosis is the same for PL/SQL in TimesTen and for PL/SQL in Oracle, though there are known differences between PL/SQL in these two environments. |
TT8508 | Question mark parameter markers are not allowed in PL/SQL blocks | You provided a question mark parameter in a PL/SQL block. Parameter marker names beginning with_QMARK_are reserved for system use. This is not supported. This error generally signifies either that an attempted operation (such as commit, rollback, or some DDL statement) cannot proceed because of a conflict with an existing PL/SQL object or because some unexpected error occurred while attempting to manage memory or locks in thePLSQL_memoryarea. |
TT8509 | PL/SQL execution terminated; PLSQL_TIMEOUT exceeded | A PL/SQL block executed for longer than the value specified for thePLSQL_TIMEOUTattribute. |
TT8510 | Error loading PL/SQL system package file file_name: error_message | When a TimesTen database is created, a number of predefined PL/SQL packages are defined in the new database. Any error encountered during this process is returned in this message. |
TT8511 | PL/SQL can only be enabled during database creation or at first connect | You attempted to enable PL/SQL on an existing database. You can only enable PL/SQL at the time that you create a database. |
TT8512 | PL/SQL is not supported with exclusive mode data store access | PL/SQL is not supported with databases that are created with exclusive access. Exclusive access is a deprecated feature. |
TT8513 | PL/SQL is not supported in non-thread-safe mode | PL/SQL is not supported with databases that are created without thread safety. Non thread-safe mode is a deprecated feature. |
TT8514 | Invalid PL/SQL compiler parameter parameter_name | Only persistent parameters are allowed. The PL/SQL persistent parameters arePLSQL_OPTIMIZE_LEVEL,PLSQL_CODE_TYPE,PLSQL_DEBUG,PLSQL_WARNINGS,PLSQL_CCFLAGSandNLS_LENGTH_SEMANTICS. You supplied a parameter other than one of these. |
TT8515 | Duplicate setting for PL/SQL compiler parameter parameter_name | You can specify each parameter only once in each statement. See the Oracle Database documentation for complete compiler parameters clause information. |
TT8516 | PL/SQL is not supported with logging turned off | You must log transactions to use PL/SQL. Set theLoggingattribute to 1 for this database. |
TT8517 | Cannot attach PL/SQL shared memory; PLSQL_MEMORY_ADDRESS not valid or already in use | The virtual memory address specified byPLSQL_MEMORY_ADDRESSis in use. Specify a virtual address that is free in all processes that can connect to the database. |
TT8518 | The preceding error occurred during the execuation of an internal SQL statement | Warning message: |
TT8519 | Invalid PLSQL_MEMORY_ADDRESS specified | An illegal value (for example, 0) was specified forPLSQL_MEMORY_ADDRESS. |
TT8520 | PL/SQL library mismatch. Corrupted TimesTen installation. | Your TimesTen installation is corrupted. Some files are from a PL/SQL-enabled version of TimesTen. Others are from a non-PL/SQL-enabled version. Re-install TimesTen with PL/SQL enabled. |
TT8521 | Cannot attached PL/SQL shared memory; virtual memory at PLSQL_MEMORY_ ADDRESS already in use by TimesTen. | Your application has connected to two different TimesTen databases that use the samePLSQL_MEMORY_ADDRESSvalue. Specify a differentPLSQL_MEMORY_ADDRESSvalue for one of the databases.SeePLSQL_MEMORY_ADDRESSfor details. |
TT8522 | PLSQL_MEMORY_SIZE too small. | SeePLSQL_MEMORY_SIZEfor the appropriate memory size for your operating system. |
TT8523 | No data found. | No rows were found when the user executed aSELECTstatement inside PL/SQL. |