Applies to:

TimesTen Data Server - Version 7.0.0.0.0 and later
Information in this document applies to any platform.

Purpose

This is a list if the TimesTen Warnings and Errors from TT10001 to TT19014. It is based on Chapter 1 of Oracle TimesTen In-Memory Database Error Messages and SNMP Traps. The lists from releases 11.2.1 and 11.2.2 have been combined. The main difference is that the warnings and errors are list in the TTnnnn format for ease of searching.

Scope

Anyone who might see one of these messages.

Details

If an error is prefixed with "Warning," the command completes but has a side effect the user should know about. For all other errors, the command terminates abnormally.

The errors are listed according to the following ranges:

Errors 10000 - 10999

Error number	Error or warning message	Details
TT10001	Only temporary data stores with diskless or no logging allowed in diskless mode	The daemon is running in diskless mode, and an attempt was made to connect to a permanent database, or a database with Logging enabled and not diskless. To prevent this error from happening, only connect to a temporary database or a diskless database withLoggingdisabled.
TT10002	No record of a data store located in 'location'	Warning: When creating a database, the daemon found files whose names look like names of checkpoint or transaction log files for the database.Since it is a new database, the TimesTen daemon renames the files so they have a tilde (~) at the end. This can happen if checkpoint files get moved manually instead of using the proper utilities, or if database files from a previous version of TimesTen exist where the TimesTen daemon is attempting to put the new files.
TT10003	Unexpected data store file exists for new data store: description.	When connecting to a database, checkpoint and/or transaction log files exist which are incompatible or should not exist. Thedescriptionfield gives more information.You can destroy the existing database and replace it with a new one by specifyingOverwrite=1in your connect string. For example: ttisql -connStr "dsn=myDSN; verwrite=1"
TT10004	Unable to connect to daemon: error_details	When a process is initiating communication with the TimesTen daemon, a communication protocol error has occurred. This is most likely due to some process other than a TimesTen daemon running on the TimesTen daemon port. UsettStatusto check whether the TimesTen daemon is running, and on which port.
TT10006	Busy with another policy request	An attempt to make a request, such as changing the RAM policy, starting the replication agent, or holding a database in RAM, has timed out because some other related policy request is running.
TT10007	Could not wait for not-in-flux	Internal error. Contact TimesTen Technical Support.
TT10008	Data store was deleted while daemon was waiting for completion of changing the state of the database	While processing an attempt to make a request such as changing the RAM policy, starting the replication agent, or loading a database into RAM, the database has been deleted.
TT10009	RAM load ignored due to ramPolicy setting	A process has attempted to load a database into RAM, but the RAM policy for the database is not "manual." UsettAdmin-ramPolicyto change the RAM policy to "manual" before attempting a RAM load or unload.
TT10010	RAM unload ignored due to ramPolicy setting	A process has attempted to unload a database into RAM, but the RAM policy for the database is not "manual." UsettAdmin-ramPolicyto change the RAM policy to "manual" before attempting a RAM load or unload.
TT10011	Data store is currently not being managed	A process has attempted to unload a database from RAM, but there is no TimesTen subdaemon currently managing the database.
TT10012	Replication Agent was not started due to repPolicy setting	An attempt has been made to start a replication agent for a database, but the replication policy for the database is "always," which means the TimesTen daemon automatically starts or restarts the replication agent. UsettAdmin -repPolicyto change the replication policy to "manual" to manually control whether the replication agent is active. See "Starting and stopping the replication agents" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for details.
TT10013	Could not start Replication Agent for the requested data store	A replication agent failed during its initialization. More information is available in the user error log.
TT10014	Could not spawn Replication Agent for the requested data store. Refer to user error log for further information	The TimesTen daemon could not spawn a replication agent. Make sure you are not out of memory or process table space.
TT10015	Could not stop Replication Agent for the requested data store. Refer to user error log for further information	An attempt to stop the replication agent failed. Make sure the database still exists and the replication agent is still running.
TT10016	Replication Agent was not stopped due to repPolicy setting	An attempt has been made to stop a replication agent for a database, but the replication policy is set to "always." See "Starting and stopping the replication agents" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for information on setting the replication policy.
TT10017	OracleNetServiceName not set	An attempt was made to start the cache agent for a database, but theOracleNetServiceNameconnection string value was not set. Make sureOracleNetServiceNameattribute is correctly defined in the DSN
TT10018	ORACLE_HOME not set	An attempt was made to start the cache agent for a database, butORACLE_HOMEwas not set in the user environment. Make sure theORACLE_HOMEenvironment variable is set properly, as described in "Environment variables" in the Oracle TimesTen In-Memory Database Installation Guide.
TT10019	ORACLE_HOME path too long	The value of the ORACLE_HOME environment variable is too long. Make sure it is set correctly, and use symbolic links if necessary. See "Environment variables" in the Oracle TimesTen In-Memory Database Installation Guide.
TT10020	Could not stop cache agent for the requested data store. Refer to user error log for further information	An attempt to stop the cache agent failed. Use ttStatus to make sure the database still exists and the cache agent is still running.
TT10021	Cache agent was not stopped due to cache agent policy setting	An attempt has been made to stop an Cache Agent for a database, but the Cache Agent policy for the database is "always," which means the TimesTen daemon automatically starts or restarts the Cache Agent. Use ttAdmin-oraAgentPolicyto change the Cache Agent policy to "manual" to manually control whether the Cache Agent is active. See "Setting a cache agent start policy" in the Oracle In-Memory Database Cache User's Guide for details.
TT10022	Failed to set ORACLE_HOME	The TimesTen daemon was unable to set theORACLE_HOMEenvironment variable. Make sure you are not out of memory. See "Environment variables" in the Oracle TimesTen In-Memory Database Installation Guidefor information on settingORACLE_HOME.
TT10023	Failed to set LD_LIBRARY_PATH	The TimesTen daemon was unable to set the LD_LIBRARY_PATH environment variable. Make sure you are not out of memory. See "Shared library path environment variable" in the Oracle TimesTen In-Memory Database Installation Guide for information on setting LD_LIBRARY_PATH.
TT10024	Could not start Cache Agent for the requested data store	A Cache Agent failed during its initialization. More information is available in the user error log.
TT10025	Could not spawn Cache Agent for the requested data store	The TimesTen daemon could not spawn an Cache Agent. Make sure you are not out of memory or process table space.
TT10026	Some cache groups that hold triggers and other objects in Oracle may exist in the data store, drop all the cache groups before destroying the data store	AttDestroyoperation may not destroy the database if it contains cache groups that hold triggers and other objects on the Oracle database. Drop the cache groups and attempt the destroy operation again.
TT10028	Attempted stop of TimesTen daemon while being managed by Clusterware	If a TimesTen installation is managed by Oracle Clusterware and the user attempts to gracefully stop the daemon directly usingttDaemonAdmin -stop, the daemon refuses to stop. The user can only stop the daemon if the Cluster agent and the daemon monitor are first stopped withttCWAdmin -shutdown-hosts localhost.

Errors 11000 - 11999

Error number	Error or warning message	Details
TT11000	XA internal error	An unexpected XA-specific internal error has occurred. Contact TimesTen Technical Support.
TT11002	XA asynchronous operation error	An asynchronous XA operation was attempted. TimesTen does not support asynchronous XA calls.
TT11003	XA Resource Manager error	A TimesTen error has occurred resulting in the failure of an XA operation. Typically, this error is accompanied by another TimesTen error that indicates the nature of the problem.
TT11004	XA invalid XID	The XID specified for an XA operation cannot be found in the list of currently active XA transactions.
TT11005	XA invalid argument	An invalid argument was passed to an XA function. Refer to the XA specification for a description of the valid arguments supported for each XA function.
TT11006	XA protocol error	An XA function was called out of sequence. Refer to the XA specification for a description of the valid function transition states.
TT11007	XA Resource Manager failure	A TimesTen error has occurred resulting in the invalidation of the database. All applications must reconnect.
TT11008	XA duplicate XID	The XID specified for a new XA transaction is already associated with another XA transaction.
TT11009	XA Resource Manager doing work outside a global transaction	A local transaction must be committed before starting work on an XA transaction.
TT11013	Transaction committed since no log records were generated	A "prepare to commit" request for an XA transaction resulted in the transaction being committed. The transaction made no persistent changes to the database.
TT11014	Request ignored due to blocking condition	An XA request was denied to a temporary resource conflict. The operation can be retried.
TT11016	Transaction has been heuristically rolled back	An XA transaction was rolled back outside the control of a transaction manager.
TT11017	Transaction has been heuristically committed	An XA transaction was committed outside the control of a transaction manager.
TT11020	Transation has been marked rollback-only	Due to an internal condition, TimesTen has marked the XA transaction rollback-only. The application must request a rollback of the transaction.
TT11030	Autocommit must be turned off when working on global (XA) transactions	Autocommit is not supported with XA transactions. See "Distributed Transaction Processing XA" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT11031	Illegal combination of local transaction and global (XA) transaction	Use ofSQLTransactto commit an XA transaction is not allowed. XA transactions may only be committed through the use ofxa_commit. See "Distributed Transaction Processing XA" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT11033	XA support requires that logging to disk be enabled	XA support requires that theLoggingconnection attribute be set to 1.
TT11035	In-doubt transactions awaiting resolution in recovery must be resolved first	Due to recovery of in-doubt transactions, normal operation of the database has been suspended. Normal operation resumes once the in-doubt transactions have been resolved by the transaction manager.
TT11036	XA transactions may not be started while replication is configured	TimesTen Replication is not supported with XA transactions.
TT11037	XA transactions may not be started while the cache agent is running	IMDB Cache is not supported with XA transactions.
TT11038	XA transaction cannot be constructed because record record_number not found	A transaction log record needed to recover an XA transaction could not be found in the existing transaction log files. Contact TimesTen Technical Support.
TT11039	XA reconstruct of xcb record failed	Recovery of an XA transaction failed due to an Internal error. Contact TimesTen Technical Support.
TT11040	DDL statementes are not allowed in XA transactions when DDLCommitBehavior. is set to 0	XA transactions require explicit commits after DDL statements. Set theDDLCommitBehaviorattribute to 1, if your application uses XA. (

Errors 12000 - 13999

Error number	Error or warning message	Details
TT12000	Unknown error in TimesTen utility library	Internal error. Contact TimesTen Technical Support.
TT12001	Specified DSN is NULL or of 0-length	The DSN argument is eitherNULLor an empty string. You must specify a valid DSN name.
TT12002	User and system odbc.ini file not found	UNIX only. TimesTen could not locate the user or systemODBC.INIfile. The search order for locating anODBC.INIfile is: the file pointed to by theODBCINIenvironment variable, if set $HOME/.odbc.ini theODBC.INIfile located in the user's home directory the file pointed to by theSYSODBCINIenvironment variable, if set /var/TimesTen/instance/sys.odbc.ini See "ODBCINI environment variable" in the Oracle TimesTen In-Memory Database Installation Guide for more information.
TT12003	Cannot open user/system odbc.ini file	UNIX only. TimesTen could not open either the user or systemODBC.INIfile.
TT12004	Syntax error in odbc.ini file	UNIX only. TimesTen encountered a syntax error while parsing the user or systemODBC.INIfile.
TT12005	Environment variable specified in the attribute is not set	UNIX only. In either the user or systemODBC.INIfile, you have specified an attribute of the DSN with an environment variable that has not been set.
TT12006	Invalid attribute name	The specified DSN attribute name isNULL, an empty string or not a valid attribute for a TimesTen data manager DSN. This error is also returned if the user or systemODBC.INIfile contains an invalid attribute_name=value pair.
TT12007	The value of the attribute in the ini file is empty. It should not be empty	UNIX only. TimesTen DSN attributes are defined in the user or systemODBC.INIfile using aattribute_name=valuepair. The value specified is either an empty string or white space.
TT12008	The length of the value-string in the ini file is too long for this attribute	UNIX only. TimesTen DSN attributes are defined in the user or systemODBC.INIfile using aattribute_name=valuepair. The length of the value specified exceeds the maximum length allowed for the attribute.
TT12009	Specified DSN is not found in user and system odbc.ini files (or registry)	On Windows, the DSN has not been defined as a user or system DSN using the ODBC Data Source Administrator. On UNIX, the DSN is not defined as a user or system DSN in aODBC.INIfile.
TT12010	Specified buffer is NULL or of 0-length	The buffer specified for returning a value is eitherNULLor the length of the buffer is 0.
TT12011	Specified buffer length is not big enough to hold the value for this attribute. Value truncated.	The specified buffer length is less than the length of the requested DSN attribute value. TimesTen returns a truncated value.
TT12012	malloc() failed	Unable to allocate memory for TimesTen internal data structures.
TT12013	Specified data store name is NULL or of zero length, or a client DSN was used	The specified database name is eitherNULLor an empty string. You must specify a valid database name.
TT12014	Internal error in TimesTen utility library. Could not get current context	Internal error. Contact TimesTen Technical Support.
TT12015	Internal error in TimesTen utility library. Could not set current context	Internal error. Contact TimesTen Technical Support.
TT12016	The number of seconds must be > 0	The number of seconds for the RAM Grace Period must be greater than 0 seconds.
TT12017	Failed to allocate environment handle	A call to the ODBCSQLAllocEnvfunction failed.
TT12018	Failed to allocate connection handle	A call to the ODBCSQLAllocConnectfunction failed.
TT12019	Failed to locate data store files	TimesTen cannot determine the path and names of the database files for the specified database.
TT12020	Failed to connect to data store	A call to the ODBCSQLDriverConnectfunction failed to connect to the database using the specified connection string.
TT12021	Failed to disconnect from data store	A call to the ODBCSQLDisconnectfunction failed.
TT12022	Failed to free connection handle	A call to the ODBCSQLFreeConnectfunction failed.
TT12023	Failed to free environment handle	A call to the ODBCSQLFreeEnvfunction failed.
TT12024	Data store already loaded into RAM and being managed	A request to load a database into RAM failed because the database has already been loaded into RAM.
TT12025	Data store already manually unloaded from RAM	A request to unload a database from RAM failed because the database has already been unloaded from RAM.
TT12026	The agent is already running for the data store	The specified agent has already been started by the TimesTen daemon.
TT12027	The agent is already stopped for the data store	The specified agent has already been stopped by the TimesTen daemon.
TT12028	No record of a data store in the location specified by the DataStore attribute of the DSN. Specified DSN may be a temporary data store	The database does not exist in the location specified by theDataStoreattribute of the DSN.
TT12030	Data store is in use	The TimesTen daemon cannot perform. the requested operation because another application is connected to the database.
TT12032	Invalid RamPolicy specified	The valid RAM Policy values are: TT_RAMPOL_MANUAL TT_RAMPOL_ALWAYS TT_RAMPOL_INUSE
TT12034	RamPolicy cannot be set for temporary data stores	RAM Policy can only be set for permanent databases.
TT12035	Could not initialize winsock	Windows only. A call to WSAStartup failed.
TT12036	No winsock.dll (that supports version 1.1.) found	Windows only. A call toWSAStartupcould not locate awinsock.dllthat supports version 1.1.
TT12037	Could not terminate winsock	Windows only. A call toWSACleanupfailed.
TT12038	Could not connect to TimesTen daemon on remote host host_name	Make sure that the TimesTen daemon is running on the remote host.
TT12039	Could not get port number of TimesTen replication agent on remote host. The replication agent may have either not been started or may have just been started and have not had time to communicate its port number to the TimesTen daemon	Make sure that the TimesTen replication agent for the specified database is running on the remote host.
TT12040	Could not connect to TimesTen replication agent on remote host	Internal error. Contact TimesTen Technical Support.
TT12041	Host not found	TimesTen failed to determine the IP addresses associated with the specified host name in the system's/etc/hostsfile. Verify that you have correctly identified the host name, as described in "Configuring host IP addresses" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.
TT12042	Cannot start transaction to perform. this operation	Internal error. Contact TimesTen Technical Support.
TT12043	Unable to create temporary file name	Internal error. Contact TimesTen Technical Support.
TT12044	Transmission failure sending	TimesTen failed to transmit data to the remote TimesTen replication agent.
TT12045	Cannot create temporary file	Internal error. Contact TimesTen Technical Support.
TT12046	Transmission failure receiving	TimesTen failed to receive data from the remote TimesTen replication agent.
TT12047	Data transmitted corrupt	The type of response received from the remote TimesTen replication agent does not match the expected response type.
TT12048	Error performing backup at source	This error can occur during a ttRepDuplicateEx operation when the backup operation on the source database fails. See the verbose user error log on the source database for additional diagnostic information.
TT12049	Cannot write to temporary file	Internal error. Contact TimesTen Technical Support.
TT12050	Transaction commit for the swap operation failed	Internal error. Contact TimesTen Technical Support.
TT12052	Replication scheme name too long	Maximum length is 30 characters.
TT12053	Replication scheme owner too long	Maximum length is 30 characters.
TT12054	Internal Error: Cannot determine userid	Internal error. Contact TimesTen Technical Support.
TT12055	No changes needed to upgrade the replication schema	During upgrade, if the replication schema version of the old database is same as the current installation, no upgrade is required.
TT12056	Size values of local store must match that of the remote store	ThePermSize,TempSizeandLogBuffSizeattributes of the local database do not match those of the remote database.
TT12057	Error creating temporary data store	Failed to create a local database.
TT12058	Failed to read replication backup CTN	Failed to read replication backup Commit Ticket Number.
TT12059	Deadlock/Timeout	Either the operation caused a deadlock or the operation timed out.
TT12060	Invalid remote host specified	A call to gethostbyname with the specified remote host name failed.
TT12061	Invalid local host specified	A call to gethostbyname with the specified local host name failed.
TT12062	Failed to upgrade from unsupported version	Upgrade from this previous replication schema version is not supported.
TT12063	Cannot read from temporary file	Internal error. Contact TimesTen Technical Support.
TT12064	Failed to execute SQL command during update	Internal error. Contact TimesTen Technical Support.
TT12065	Multiple records of replication schema version	Internal error. Contact TimesTen Technical Support.
TT12066	Failed to compile command	Internal error. Contact TimesTen Technical Support.
TT12067	Failed to open cursor	Internal error. Contact TimesTen Technical Support.
TT12068	Failed to get next row	Internal error. Contact TimesTen Technical Support.
TT12069	Failed to get format handle of the SQL command	Internal error. Contact TimesTen Technical Support.
TT12070	Failed to get column information	Internal error. Contact TimesTen Technical Support.
TT12071	Failed to get column value	Internal error. Contact TimesTen Technical Support.
TT12072	Multiple definitions of replication store id for the specified data store	Internal error. Contact TimesTen Technical Support.
TT12073	Cannot determine my own store name	Internal error. Contact TimesTen Technical Support.
TT12074	Cannot determine my own hostname	Internal error. Contact TimesTen Technical Support.
TT12075	Replication tables are from an earlier version. Consider using 'ttRepAdmin -self -upgrade' to upgrade	The specified operation is not allowed on replication schemes for older versions of TimesTen.
TT12076	Replication schema is later than TimesTen utility library	The specified operation is not allowed on replication schemes for new versions of TimesTen.
TT12077	Hostname is not set on this machine	Internal error. Contact TimesTen Technical Support.
TT12078	Failed to rest is_local_store	Internal error. Contact TimesTen Technical Support.
TT12079	Failed to set is_local_store	Internal error. Contact TimesTen Technical Support.
TT12080	No receiver found to swap with	Internal error. Contact TimesTen Technical Support.
TT12081	Unsupported column type in upgrade	Internal error. Contact TimesTen Technical Support.
TT12082	Failed to reset receiver CTN	TimesTen failed to reset receiver Commit Ticket Number.
TT12083	Found no source store ID in TTREP.REPLICATIONS	Internal error. Contact TimesTen Technical Support.
TT12084	Call to gethostname() failed	Internal error. Contact TimesTen Technical Support.
TT12085	No table found for table id	Internal error. Contact TimesTen Technical Support.
TT12086	Cannot get information on table	Internal error. Contact TimesTen Technical Support.
TT12087	Cannot get format of table	Internal error. Contact TimesTen Technical Support.
TT12088	Multiple definitions of source store id	Internal error. Contact TimesTen Technical Support.
TT12089	Cannot get column information of table	Internal error. Contact TimesTen Technical Support.
TT12090	Cannot get type mapping for column	Internal error. Contact TimesTen Technical Support.
TT12091	Cannot determine if version 2 replication tables exist	Internal error. Contact TimesTen Technical Support.
TT12092	Replication schema is not empty; cannot upgrade	Replication schema must be empty for the upgrade operation.
TT12093	No count information returned from upgrade's scan of TTREP.TABLES	Internal error. Contact TimesTen Technical Support.
TT12094	Cannot get count information from TTREP.TABLES	Internal error. Contact TimesTen Technical Support.
TT12095	Cannot update object id	Internal error. Contact TimesTen Technical Support.
TT12096	Cannot set object id	Internal error. Contact TimesTen Technical Support.
TT12097	Cannot get column values from TTREP.PEER	Internal error. Contact TimesTen Technical Support.
TT12098	Failed to determine correct write LSN for TTREP.REPPEERS.SENDLSN	Internal error. Contact TimesTen Technical Support.
TT12099	Multiple schemes found. Must specify -scheme to identify which replication scheme to use	Multiple replication schemes found.
TT12100	Cannot create replication table definition	Internal error. Contact TimesTen Technical Support.
TT12101	Cannot start transaction to check replication schema version	Internal error. Contact TimesTen Technical Support.
TT12102	Failed to commit transaction for checking replication schema version	Internal error. Contact TimesTen Technical Support.
TT12103	Cannot get column value from TTREP.REPELEMENTS table	Internal error. Contact TimesTen Technical Support.
TT12104	Cannot find write LSN	Internal error. Contact TimesTen Technical Support.
TT12105	Failed to update LSN	Internal error. Contact TimesTen Technical Support.
TT12106	Cannot set new replication hold LSN	Internal error. Contact TimesTen Technical Support.
TT12107	Deleting table definition info failed	Internal error. Contact TimesTen Technical Support.
TT12108	Invalid policy 'invalid_policy' specified. Must be valid_policy_list	The policy value supplied to the built-in procedure must be of the values in the valid_policy_list. Refer to the documentation on each specific built-in procedure for a description of its valid policy values. See "Built-In Procedures" in Oracle TimesTen In-Memory Database Reference.
TT12109	Syntax error in connection string	There is a syntax error in the specified connection string. Correct the connection string and try connecting again.
TT12110	Neither DSN= nor DRIVER= attributes are present in the connection string	The connection string must contain either aDSNorDRIVERattribute.
TT12111	Signal signal_name received	The application received a signal and terminated.
TT12114	Version mismatch between the backup files and restore. Backed-up files are version version_number; ttRestore is version version_number	The restore operation failed because the backup files were created by a different version of TimesTen than the ttRestore utility used.
TT12116	Cannot create database for restore	Internal error. Contact TimesTen Technical Support.
TT12117	Disconnect from newly created database failed	Internal error. Contact TimesTen Technical Support.
TT12119	Cannot open destination file	Failed to open database file while restoring from stream input.
TT12120	Insufficient bytes read from input stream	Internal error. Contact TimesTen Technical Support.
TT12125	Bad data store file header read from input stream	Verify that the stream input is valid.
TT12132	Error forming basename of data store	Failed to create a file name from theDataStoreattribute of the DSN.
TT12133	Data store file already exists	A database file with the same name as indicated by theDataStoreattribute of the DSN already exists.
TT12134	Log file(s) already exist	Log file(s) with the same name as indicated by theDataStoreattribute of the DSN already exists.
TT12135	Failed to delete data store files; OS-detected error: error_number	Internal error. Contact TimesTen Technical Support.
TT12136	Error while deleting log files	Internal error. Contact TimesTen Technical Support.
TT12148	Specified connection string is NULL or of 0-length	The connection string argument passed is eitherNULLor an empty string. You must specify a valid connection string argument.
TT12150	Cannot start transaction to update receiver CTN in TTREP.REPPEERS	Internal error. Contact TimesTen Technical Support.
TT12151	Failed to commit TimesTen transaction for updating receiver CTN	Internal error. Contact TimesTen Technical Support.
TT12152	Cannot set timestamp column for table	Internal error. Contact TimesTen Technical Support.
TT12153	Cannot get DS_OBJ_ID value from TTREP.REPELEMENTS	Internal error. Contact TimesTen Technical Support.
TT12154	Cannot get TBLID value from SYS.TABLES	Internal error. Contact TimesTen Technical Support.
TT12155	Cannot get row id for row in TTREP.REPELEMENTS	Internal error. Contact TimesTen Technical Support.
TT12156	Too many tables found on second pass	Internal error. Contact TimesTen Technical Support.
TT12157	Failed to update the table IDs from the mapping we've created	Internal error. Contact TimesTen Technical Support.
TT12158	Cannot set replication fields in SYS.TABLES	Internal error. Contact TimesTen Technical Support.
TT12159	NULL passed for a pointer argument	The pointer argument must be a non-NULLvalue.
TT12160	Timeout - the agent is still starting	Under some conditions, you may receive this error when trying to stop the cache agent for a database while the agent is starting up. Retry the operation.
TT12161	Cannot backup temporary data stores	Backup is not allowed for temporary databases.
TT12164	RamGrace cannot be set for temporary data stores	ttAdmin-ramGracecan only be set on a permanent database.
TT12166	Failed to start Backup	The replication agent ran into an error while running thettBackuputility on the subscriber database or when runningttRepAdmin-duplicateconcurrently on more than one database. Run thettBackuputility on the subscriber with replication disabled, or avoid running two duplicate operations concurrently.
TT12184	Could not initialize connection to TimesTen daemon	Internal error. Contact TimesTen Technical Support.
TT12185	No definitions of replication store id for the specified data store	Internal error. Contact TimesTen Technical Support.
TT12186	fstat() system call failed for user/system odbc.ini fle	Internal error. Contact TimesTen Technical Support.
TT12187	read() system call failed for user/system odbc.ini file	Internal error. Contact TimesTen Technical Support.
TT12188	close() system call failed for user/system odbc.ini file	Internal error. Contact TimesTen Technical Support.
TT12189	Scan stopped for user/system odbc.ini file	Internal error. Contact TimesTen Technical Support.
TT12190	Attribute name is too long	Maximum length of attribute names is 30 characters.
TT12191	Invalid length for connection string	The value specified for the length of the connection string to theSQLDriverConnectODBC call is less than 0 and not equal toSQL_NTS.
TT12192	Invalid backup type	An invalid value was passed as the type parameter of thettBackuputility library function. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12193	No backup directory specified	A null pointer or empty string was passed as thebackupDirparameter of thettBackuputility library function. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12194	Failed to retrieve data store information	Internal error. Contact TimesTen Technical Support.
TT12195	Basename contains invalid characters	An invalid value was passed as thebaseNameparameter of thettBackuputility library function. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12196	Backup status file not found	No backup status file was found for the given backup directory and/or base name. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12197	Existing backup files do not match data store	The backup files indicated by the given backup directory and/or base name are not from the database that is being backed up.Causes for the mismatch include:These backup files can be overwritten by specifying a non-atomic backup. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide. The database that is stored in the backup files has a different database path name than the database that is being backed up. The database being backed up has the same database path name as the database that is stored in the backup files, but the two databases do not have the same creation time. This can happen if the backed up database was destroyed and a new database was created with the same database path name.
TT12198	One or more files missing from backup directory	One or more backup files are missing from the backup indicated by the given backup directory and/or base name. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12199	Cannot read directory contents; OS-detected error: error_number	The contents of the backup directory could not be read due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12200	Failed to open backup status file: OS-detected error: error_number	The backup status file for the backup indicated by the backup directory and/or base name could not be opened due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12201	Failed to read backup status file: OS-detected error: error_number	The backup status file for the backup indicated by the backup directory and/or base name could not be read due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12202	Failed to write backup status file: OS-detected error: error_number	The backup status file for the backup indicated by the backup directory and/or base name could not be written due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12203	Failed to close backup status file: OS-detected error: error_number	The backup status file for the backup indicated by the backup directory and/or base name could not be closed due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12204	Invalid or corrupted backup status file	The backup status file for the backup indicated by the backup directory and/or base name is invalid or corrupt. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12205	Backup is incomplete	The backup status file for the backup indicated by the backup directory and/or base name is incomplete. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12206	Backup control information corrupted or incomplete (may indicate TimesTen version mismatch)	The backup status information for the backup indicated by the backup directory and/or base name is corrupted or incomplete. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12207	Failed to write backup status record; OS-detected error: error_number	Backup status information for the backup indicated by the given backup directory and/or base name could not be written due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12208	Failed to retrieve file information; OS-detected error: error_number	An attempt to retrieve information about one or more of the backup files indicated by the backup directory and/or base name failed due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12209	Failed to open file file_name; OS-detected error: error_number	One or more of the backup files indicated by the backup directory and/or base name could not be opened due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12210	Failed to read backup file; OS-detected error: error_number	One or more of the backup files indicated by the backup directory and/or base name could not be read due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12211	Backup file is shorter than expected	One or more of the backup files indicated by the given backup directory and/or base name have been truncated. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12212	Failed to write backup file; OS-detected error: error_number	One or more of the backup files indicated by the backup directory and/or base name could not be written due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12213	Failed to close backup file; OS-detected error: error_number	One or more of the backup files indicated by the backup directory and/or base name could not be closed due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12214	Failed to rename backup file; OS-detected error: error_number	One or more of the backup files indicated by the backup directory and/or base name could not be renamed due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12215	Backkup terminated because data store connection invalidated	The requested backup operation was terminated because the database connection was terminated. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12216	Invalid restore type	An invalid value was passed as the type parameter of thettRestoreutility library function. See "ttRestore" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12217	Cannot restore into a temporary data store	A temporary database cannot be the target of a database restore operation. See "ttRestore" in the Oracle TimesTen In-Memory Database C Developer's Guide.
TT12218	Could not get port number of TimesTen Server. Make sure that it is running	Generally, the TimesTen Server is automatically started by the TimesTen daemon. Upon start up, the TimesTen Server lets the daemon know the port number that the Server is listening on. This error indicates that there was a problem starting the TimesTen Server. Hence, the daemon does not know the port number of the TimesTen Server. Refer to the daemon/server log for further details.
TT12219	Failed to connect to TimesTen Server. Refer to user error log for further details	A socket connection to the TimesTen Server failed. Refer to the daemon/server log for further details.
TT12220	Failed to send request to TimesTen Server	A socketsendcall failed. Normally, this is accompanied with a description of the OS error.
TT12221	Platform. mismatch between backed-up files and ttRestore. Backed-up files are backup_platform; ttRestore is restore_platform	Files can only be restored on the same platform. type where they were backed up.
TT12222	Backed-up files appear to be from a TimesTen release prior to TimesTen 5.0	Files that were backed up using a TimesTen release prior to 5.0 cannot be restored using this TimesTen release's utilities.
TT12231	Failed to truncate tables	A problem occurred during the execution of the ttRepAdmin-duplicateutility with the-truncateoption.
TT12232	Failed to drop objects	A problem occurred during the execution of ttRepAdmin-duplicateutility with the-dropoption
TT12233	Failed to truncate table	Specifies the table that had the problem referred to in error 12231.
TT12234	Failed to drop table	Specifies a table that was referred to in error 12232.
TT12235	There are identifiers supplied for the drop option which are also quoted for the truncate option	The ttRepAdmin-duplicateutility tries to drop and truncate the same table or tables with the-dropand-truncateoptions.
TT12236	There are duplicate identifiers specified in the drop option	The same table is listed twice for the-dropoption ofttRepAdmin -duplicate.
TT12237	There are duplicate identifiers specified in the truncate option.	The same table is listed twice for the-truncateoption ofttRepAdmin -duplicate.
TT12238	For -truncate or -drop you can specify \"ALL\" or a list of tables, not both.	For the-truncateor-dropoptions of thettRepAdmin -duplicateutility, you can specify "ALL" or a list of tables, but you cannot specify both in the same statement.
TT12245	No definitions of replication store id for the data store DSN on host_name	Arguments passed during database duplication are not consistent with store definitions on the source database.
TT12246	DSN DSN_name exceeds the maximum length of length	A database name cannot exceed 32 characters.
TT12247	A sequence cannot be truncated	Occurs when the name of a sequence is supplied to the-truncateoption ofttRepAdmin-duplicateor tottRepDuplicateEx.
TT12248	RamGrace cannot be specified with always or manual RAM policy	When setting the RAM residence policy for a database, a grace period can be used only with theinUsepolicy.
TT12249	The remoteDaemonPort can only be 0 or between 1024 and 65535	Reset the value of thettRepAdmin -duplicate -remoteDaemonPortoption to a value specified in the error message.
TT12250	The duplicate verbosity level must be 0, 1, or 2	Acceptable values for thettRepAdmin -duplicate -verbosityoption are 0, 1 or 2.
TT12251	The duplicate verbosity level must be 0, 1, or 2	Acceptable values for thettRepAdmin -duplicate -verbosityoption are 0, 1 or 2.
TT12252	Could not check Oracle DB	An additional error message from the cache layer accompanies this message. Review that message to determine the problem and fix.
TT12253	The Active Standby Oracle Database is the same as the DR Oracle database	When thettRepAdmin -duplicate -initCacheDRoption is used the DR Oracle database cannot be the same database as the active standby Oracle subscribing database. The check has identified att_03_reppeersentry which is from one of the Active Standby master stores to the DR Oracle Database. Reconfigure the data recovery to resolve this conflict.
TT12254	Remote peer does not support parallel replication.	There is a mismatch in the parallel replication configuration between two stores involved in a replication scheme, where one store is enabled for parallel replication and the other is not.
TT12255	A/S pairs cannot be created when parallel mode replication configured.	Active Standby Pair replication schemes are not configured while the database has been created with parallel replication attributes, with theReplicationApplyOrderingattribute configured greater than 0.
TT12257	Error creating bookmarks for the parallel tracks.	Internal error. Tried to create entries inTTREP.REPPEERSfor parallel replication tracks. When parallel replication is enabled, there are more than one TTREP.REPPEERS entry for master->subscriber. The number of entries is dependent upon theReplicationParallelismparameter.
TT12258	Return Receipt or Return TwoSafe cannot be used when parallel mode replication is configured.	Return Receipt and Return Twosafe cannot be used for a return service when the database has been created with parallel replication attributes, where theReplicationApplyOrderingattribute is greater than 0.
TT12259	A store cannot be defined as a PROPAGATOR when parallel mode replication is configured.	Propagator stores are not supported when the database has been created with parallel replication attributes, where theReplicationApplyOrderingattribute is greater than 0.
TT12260	Create cache group is not permitted when parallel mode replication is configured.	Cache groups are not supported when the database has been created with parallel replication attributes, where theReplicationApplyOrderingattribute is greater than 0.
TT12261	ALTER TABLE is not permitted on a replicated table when parallel mode replication is configured.	ALTER TABLEis not allowed when the database has been created with parallel replication attributes, where theReplicationApplyOrderingattribute is greater than 0. This error is raised at application time.
TT12262	Error setting track for connection.	Internal Error. The replication agent cannot use a specific track for its database connection.
TT12263	Aging is not permitted on a replicated table when parallel mode replication is configured.	In 11.2.1.6.0, aging on tables was allowed whenReplicationApplyOrderingwas set to 1. Currently, we disable aging whenReplicationApplyOrderingis set to 1. When a database withReplicationApplyOrderingset to 1 is upgraded from 11.2.1.6.0, aging will be disabled
TT12264	ALTER TABLE cannot be replicated to a store with parallel mode replication enabled.	This error occurs if the replication agent detectsALTER TABLEwhen parallel mode replication is enabled.
TT12274	Failed to read track entries for peer.	This is an internal error that is returned if the transmitter could not read metadata fromttrep.reppeers. Contact TimesTen Technical Support.
TT12275	Failed to convert replicated XLA bookmarks to non-replicated for read only subscriber	This error is returned after ttRepAdmin -duplicate processing. When a read-only subscriber is created with the -duplicate qualifier, TimesTen modifies replicated bookmarks to non-replicated. This error is returned if there is a problem modifying the bookmarks.
TT12700	NLSRTL environment could not be initialized	The NLS data files could not be located. The installation directory may have been corrupted or become unreadable.
TT12701	DatabaseCharacterSet attribute required for data store creation. Refer to the TimesTen documention for information on selecting a character set.	You must specify a value for theDatabaseCharacterSetattribute when creating a database. The database character set cannot be changed after database creation. For more details on selecting a database character set, see "Choosing a database character set" in the Oracle TimesTen In-Memory Database Operations Guide.
TT12702	Unable to load NLS data data from NLS_data_item	A particular NLS data file could not be located. The installation directory may have been corrupted or become unreadable. NLS_data_item could be a character set name or a sort name.
TT12705	Invalid session parameter	The session parameter is unknown or unsupported by TimesTen. For example: ALTER SESSION SET NLS_BOGUS='french'; returns 12705: Invalid NLS session parameter
TT12706	Invalid session parameter value.	The value supplied for the session parameter is unknown or unsupported by TimesTen. or example: ALTER SESSION SET NLS_SORT='bogus'; returns 12706: Invalid NLS session parameter value
TT12707	Linguistic index maximum key value length limit exceeded	The value computed for the linguistic index key exceeds the maximum length allowed for that index. There is a 64k upper limit for linguistic index key values.
TT12708	Conversion of TIMESTEN8 character set data is not allowed	An operation either explicitly or implicitly tried to convertTIMESTEN8data to another character set. Conversion ofTIMESTEN8character data is undefined and therefore not allowed.
TT12713	Character data loss in NCHAR/CHAR conversion	NLS_NCHAR_CONV_EXCPwas set toTRUEand a conversion was attempted for anNCHARcharacter having no corresponding mapping in the database character set.
TT12714	NLSSORT computation failed due to invalid characters in string	The string passed to theNLSSORTfunction contained invalid characters for the given character set. A meaningfulNLSSORTresult value could not be computed. Character data containing invalid characters is of dubious usefulness and should be eliminated from the database.
TT12715	NLS_SORT value must be BINARY when database character set is TIMESTEN8	When the database character set isTIMESTEN8, the only setting allowed forNLS_SORTisBINARY. Non-binary comparison rules forTIMESTEN8data are undefined.
TT12716	'\' must be followed by four hexadecimal characters or another '\'	TheUNISTRfunction argument allows the back-slash character only as an escape for a hexadecimal Unicode character or itself. For example: UNISTR('\0041') UNISTR('abc\\nop')
TT12717	Character data loss in character set conversion	This is a warning. During character set conversion of data, a character was encountered for which no valid conversion exists. TimesTen substituted a replacement character in its place. You should change your connection character set to one that is compatible with the database character set in use.
TT12718	Error setting default date/timestamp format format_string	Contact TimesTen Technical Support.
TT12719	Error in conversion of NCHAR to ASCII	If you attempt to convert the NCHAR type to either the DATE type or numeric type, TimesTen first converts the NCHAR type to ASCII. There was an error when TimesTen attempted to convert NCHAR TO ASCII. Check the data for your NCHAR type.
TT13000	License file file_name does not exist.	TimesTen cannot locate the evaluation license file.
TT13001	License file file_name unreadable.	TimesTen cannot read the evaluation license file.
TT13002	License key in file_name is invalid.	Invalid evaluation license.

Errors 14000 - 14999

Error number	Error or warning message	Details
TT14000	TimesTen daemon internal error: error_number	Internal error. Contact TimesTen Technical Support.
TT14001	TimesTen daemon out of memory allocated_size	The TimesTen daemon has run out of swap space.
TT14002	TimesTen daemon port in use port_number	The TimesTen daemon cannot listen on its specified port because the port is already in use.
TT14003	TimesTen daemon thread creation failed: thread_name	TimesTen daemon thread creation failed.
TT14004	TimesTen daemon creation failed: reason_for_failure	TimesTen daemon could not create database for specified reason.
TT14005	TimesTen daemon connection failed: reason_for_failure	TimesTen daemon could not make new database connection for specified reason.
TT14006	TimesTen daemon disconnect failed: reason_for_failure	TimesTen daemon could not do database disconnect for specified reason.
TT14007	TimesTen daemon destroy failed: reason_for_failure	TimesTen daemon could not destroy the database for specified reason.
TT14008	TimesTen daemon association table full (number_of_connections entries)	Too many simultaneous connections have been made.
TT14009	TimesTen daemon startup failed: reason_for_failure	Startup of TimesTen daemon failed for the specified reason.
TT14010	TimesTen daemon spawn failed: process_name	TimesTen daemon could not spawn a subprocess.
TT14011	TimesTen daemon operation failed due to invalidation: reason_for_failure	Specified operation failed due to a database invalidation.
TT14012	TimesTen daemon subdaemon failed: reason_for_failure	A TimesTen subdaemon failed to perform. the requested operation.
TT14013	TimesTen daemon out of subdaemons: reason_for_failure	The TimesTen daemon could not spawn a subdaemon to perform. some operation, such as managing a database or rolling back transactions for a dead process.
TT14014	TimesTen daemon policy request failed: reason_for_failure	AttAdminrequest failed for the specified reason.
TT14015	User user_name, not instance admin admin_name, trying to start TimesTen daemon as setuid root	A user other than the instance administrator attempted to start the main TimesTen daemon.

Errors 15000 - 15999

Error number	Error or warning message	Details
TT15000	Password is incorrect	Incorrect password given.
TT15001	User lacks privilege privilege_needed	The users lacks the privilege for the given operation.
TT15002	No such user	Attempt to modify or remove a user which does not exist.
TT15003	Number of users specified at daemon startup exceeded	Attempt to add another user when the limit has been reached. The daemon should be restarted with a new-maxusersoption specified in thettendaemon.optionsfile.
TT15004	User user already exists	Attempt to add a user whose name already exists.
TT15005	User defined as 'identified externally' but password provided, or vice/versa	Authentication failed because either no password was provided for a TimesTen user, or a password was provided for a user defined asIDENTIFIED EXTERNALLYby the operating system or network.
TT15006	Cannot delete the instance administrator user	Attempt to remove the instance administrator user.
TT15007	Access control not enabled	Attempt to perform. authorization functions when access control has not been enabled.
TT15008	User name exceeds limit of 30 characters	Specified user name is too long. Must be 30 characters or less.
TT15009	Password required for username	APWDorPWDCryptattribute must be specified for the given user name.
TT15010	Cannot convert user from 'identified externally' to internal or vice versa.	Cannot give a password to a user defined asIDENTIFIED EXTERNALLY, or remove a password for a user defined as an internal TimesTen user.
TT15011	Password exceeds limit of number characters	PWDattribute is too long.
TT15012	Encrypted password must have exactly number characters	PWDCryptattribute is not the correct length.
TT15013	Cannot alter privileges for the instance administrator user	Must be logged into administrator account to alter administrator privileges.
TT15014	Only the instance administrator user can perform. this command	Insufficient privileges to execute command restricted to the administrator.
TT15015	Cannot alter password for predefined users	Insufficient privileges to alter administrator password.
TT15016	Unsupported use of an internal system-user acccount	One of the predefined users ('PUBLIC', 'SYS', 'TTREP') is being used in an unsupported operation.
TT15017	ADMIN privilege required to alter attribute_name attribute	When Access Control is in use, changing first-connection attributes from their previous values requires theADMINprivilege.
TT15018	Password is illegal. Either it is empty, has leading or trailing white space characters, or contains carriage-return, newline or semi-colon characters.	Due to limitations in the ODBC connection string and.inifile syntax, passwords having any of the listed restrictions cannot be correctly recognized and are disallowed at password creation time.
TT15019	Only the instance admin may alter the attribute attribute.	The current user is attempting to connect to the database using the specified first connection attribute with a value different from the existing database value. Only the instance administrator user may change that attribute. The user can either connect as instance administrator to change the attribute value, or connect without changing the value.
TT15020	UID not specified	TheUIDwas not specified when executing attRepAdmin -duplicateoperation. The user must provide theUIDand rerun thettRepAdmin -duplicateoperation.
TT15021	PWD or PWDCrypt not specified	ThePWDorPWDCryptwere not specified when executing attRepAdmin -duplicateoperation. The user must provide a password or a value for thePWDCryptattribute and rerun thettRepAdmin -duplicateoperation,
TT15100	User user_name lacks privilege privilege_name	The specified user must have the indicated privilege to perform. the attempted operation.
TT15101	Cannot grant or revoke more than a single atomic privilege when logging is not enabled	Perform. separateGRANTorREVOKEoperations for each privilege you wish to grant or revoke from the user.
TT15102	Statement compilation failed. During privilege checking for statement, could not allocate num bytes on the compilation heap	Internal error. Contact TimesTen Customer Support.
TT15103	System-defined users and roles cannot be dropped	You cannot drop users and roles from TimesTen system tables.
TT15104	Only the instance administrator can destroy a database	You must be the instance administrator to create or destroy a database.
TT15105	User username requesting database creation is not the instance administrator. Only the instance administrator can create a database	You must be the instance administrator to create or destroy a database.
TT15106	Database users cannot invoke internal built-in procedures	You attempted to execute a TimesTen built-in procedure that is reserved for internal use only.
TT15107	User lacks CREATE SESSION privilege; logon denied	To perform. operations on a TimesTen database, you must have the CONNECT or CREATE SESSION privilege in addition to any other privileges required for the specific operation.
TT15109	The system privilege SYSDBA is not supported. The system privilege ADMIN can be used for most administrative tasks.	SYSDBA is not a valid privilege. Use the ADMIN privilege.
TT15110	object does not exist	This message displays in cases where the lack of existence should have been caught prior to privilege computation.
TT15111	Invalid privilege: privilege. Roles are not supported.	Check the name or spelling of this privilege. The name supplied is not supported.
TT15140	GRANT failed: User user_name already has object privilege privilege_name	The specified user already has the privilege that you attempted to GRANT. No action is required.
TT15141	GRANT failed: User user_name already has system privilege privilege_name	The specified user already has the privilege that you attempted to GRANT. No action is required.
TT15142	REVOKE failed: User user_name does not have system privilege privilege_name	The specified user does not have the privilege that you attempted to REVOKE. No action is required.
TT15143	REVOKE failed: User user_name does not have object privilege privilege_name	The specified user does not have the privilege that you attempted to REVOKE. No action is required.
TT15144	REVOKE failed: Cannot revoke system-granted object privilege privilege_name on object from PUBLIC	This error is generated when the user tries to revoke one of the privileges that were granted to PUBLIC as part of database creation. Any other privileges that a user grants to PUBLIC can be revoked as usual.
TT15150	operation failed: (internal error) error_message	The specified operation failed for the reason indicated in the error message.
TT15151	operation failed: User user_name does not exist	The specified operation failed because the indicated user does not exist on the database.
TT15152	operation failed: Object object_name does not exist	The specified operation failed because the indicated object does not exist on the database.
TT15154	operation failed: Invalid privilege privilege_name for object object_name type type_name	The operation failed because there is a mismatch between the specific privilege and the object.
TT15155	operation failed: You do not have the rights to grant or revoke privilege privilege_name	You do not have adequate privileges necessary to grant or revoke the specified privilege.
TT15156	operation failed: You do not have the rights to grant or revoke privilege privilege_name on object_name	You do not have adequate privileges necessary to grant or revoke requested privilege on the specified object.
TT15157	operation failed: User user_name is the owner of object_name	User attempted to grant or revoke privileges for the indicated object to the current owner. An object's owner always has all privileges for that object. Additional privileges cannot be granted, and none of these privileges can be revoked. If necessary attempt the operation again after correcting the user name or object name.
TT15158	operation failed: Cannot grant or revoke privilege from instance admin user_name	You do not have adequate privileges to grant or revoke privileges to/from the instance administrator.
TT15159	operation failed: privilege_name listed more than once in privilege list.	You must indicate a privilege only once in the SQL statement when attempting to grant or revoke it.
TT15160	operation failed: privilege_name on object_name is listed more than once in privilege list	You must indicate a privilege only once for a specific object in the SQL statement when attempting toGRANTorREVOKEit.
TT15161	operation failed: keyword is redundant with ALL	You issued aGRANT ALLorREVOKE ALLstatement, while attempting to grant or revoke other specific privileges. Adding additional privileges to theGRANT ALL(orREVOKE ALL) statement is redundant. Attempt the operation again and specify eitherALLor the specific privileges that you wish toGRANTorREVOKE.
TT15162	operation failed: keyword is redundant with ALL on object_name	You issued aGRANT ALLorREVOKE ALLstatement on the indicated object, while attempting to grant or revoke other specific privileges. Adding additional privileges to theGRANT ALL(orREVOKE ALL) statement is redundant. Attempt the operation again and specify eitherALLor the specific privileges that you wish toGRANTorREVOKE.
TT15163	operation failed: user_name is listed more than once in user list.	You must list the user name only once in a SQL statement.
TT15164	operation failed: Cannot grant or revoke privileges from internal system-user user_name	The operation failed because you attempted toGRANTorREVOKEa privilege to/from an internal TimesTen user, such as sys. or ttrep.
TT15165	Invalid system privilege sys_privilege.	The user specified an invalid privilege in aGRANTorREVOKEstatement when a system privilege was expected. See the documentation for the list of valid system privileges and the appropriate syntax for specifying them.
TT15166	Invalid object privilege object_privilege.	The user specified an invalid privilege in aGRANTorREVOKEstatement when an object privilege was expected. See the documentation for the list of valid object privileges and the appropriate syntax for specifying them.
TT15167	Cannot drop a user that is currently connected.	An attempt was made to drop a user that is currently connected to the database. That user must disconnect first, then theDROP USERcommand can be retried.
TT15168	Cannot drop a user that owns database objects (string string).	An attempt was made to drop a user that owns objects in the database. The existing object triggering the error is listed in the error message text, though there may be additional objects not listed. Drop all the objects owned by the user first, and then retry theDROP USERcommand.

Errors 16000 - 16999

Error Number	Error or warning message	Details
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.

Errors 17000 - 19999

Error number	Error or warning message	Details
TT17000	{TABLE\|CACHE GROUP} owner.name was quoted in an {INCLUDE\|EXCLUDE} clause but does not exist.	The table or cache group specified in anINCLUDEorEXCLUDEclause does not exist.
TT17001	The {INCLUDE\|EXCLUE} {TABLE\|CACHE GROUP} clause has the same name (table_name\| cache_group_name) mentioned more than once.	TheINCLUDEorEXCLUDEclause mentions the same table name or cache group name more than once.
TT17002	You cannot exclude everything from being replicated.	All objects in the database were excluded in theCREATE REPLICATIONstatement. There must be at least one object in the database.
TT17003	Maximum number of peers max_peers exceeded for store	The limit on the maximum number of peer stores was exceeded. The message indicates the maximum limit.
TT17004	Table owner.table_name of cache group owner.cache_group_name cannot be part of a replication subscription if the cache group is using autorefresh.	A table that is part of an autorefresh cache group, whose autorefresh state is on, cannot be a subscriber in a replication scheme. Turn theAUTOREFRESH STATEtoOFF.
TT17005	Cannot configure conflict checking on a object_type element	Conflict checking cannot be configured on aSEQUENCEelement, for example.
TT17006	Cannot configure return service on a object_type element	Return service cannot be configured on aSEQUENCEelement, for example.
TT17007	Sequence owner.sequence_id cannot be replicated because it was created with CYCLE specified	TimesTen does not support the replication of sequences that were defined withCYCLEspecified. If a replication element is created (either byCREATE REPLICAIONorALTER REPLICATION...ADD ELEMENT) and anINCLUDEorEXCLUDEclause is used or aELEMENT SEQUENCEclause is used, and if the element involves a cycling sequence, then this error is generated.
TT17008	Sequence owner.sequence_id will not be included in the replication scheme as part of this operation because it was created with CYCLE specified	If a database level element is created (either byCREATE REPLICATIONorALTER REPLICATION...ADD ELEMENT) and a cycling sequence is involved, then the cycling sequence is not replicated.
TT17009	Stores store_name and store_name on host host_name would be using the same replication port (port_number). These stores are not necessarily in the same replication scheme.	The port number for the replicated stores conflict. Master and subscriber port numbers in a replication scheme must be the same.
TT17010	Store store_name has been configured with a timeout of msecs. This is lower than the recommended minimum of num and could lead to unncessary replication timeouts to occur.	The replication connection timeout is below the recommended value. This may lead to a large number of unnecessary connects and disconnects, thereby flooding thesyslogand slowing down replication. The message indicates the minimum limit.
TT17011	The RELEASE attribute has been specified for store store_name. This feature has been deprecated and the value supplied has been ignored.	This feature has been deprecated.
TT17012	All AWT cache groups must be part of the Active Standby scheme. The AWT cache group for table owner.tablename has been quoted in an EXCLUDE CACHE GROUP clause.	AWT cache groups cannot be excluded from anACTIVE STANDBYscheme. Redefine yourACTIVE STANDBYscheme in such a way that these cache groups are included in the scheme.
TT17013	The default hostname cannot be set to host_name because a local host of host_name is currently in use.	Using the built-in procedurettHostNameSetyou have specified a hostname for a replication subscribe to a value that differs from the default hostname already in use by a replication scheme. The hostname is not changed. To view the current hostname specified in the scheme, use the procedurettHostNameGet.
TT17014	The replication heartbeat factor must be between 0.25 and 4.0.	Internal error. A heartbeat factor outside of the specified range was supplied as a store attribute.
TT17015	The aging policy for table table_name differs from its peer: details.	The replication aging policy for a table used in a replication scheme differs between master and subscriber. The details can be one of: "Time-based aging versus LRU aging," "No aging versus LRU aging," "LRU aging versus time-based aging," "Time-based aging versus no aging," "Aging enabled versus aging disabled," "Aging disabled versus aging enabled," "Different lifetime," "Different lifetime unit," "Different cycle" "Different cycle unit."
TT17016	Error getting dbcharset ID	Internal error. A sanity check between the master and subscriber of a replication scheme failed to identify the character set used in the store. Contact TimesTen Technical Support.
TT17017	The database character set differs from its peer	Internal error. The database character set used by a master in a replication scheme is different than that used by the subscriber. Contact TimesTen Technical Support.
TT17018	Cannot replicate to peer because it is a pre-7.0 data store and this store does not have the DatabaseCharacterSet attribute set to 'TIMESTEN8'	For TimesTen to be able to replicateNCHARtype columns between this release and pre-7.0 releases of TimesTen the store in this release must have theDatabaseCharacterSetattribute set toTIMESTEN8.
TT17019	Store store_name on host_ name would be using the same port as the daemon.	A replication configuration operation failed because the same port number as the main daemon was used for the store. Use a port number for the replication store that does not clash with the main daemon port.
TT17020	Failed to check CG state for duplicate	TimesTen failed to check the state of cache groups in the source store. See the message log for the cause of the failure.
TT17021	Failed to reset Autorefresh bookmark	A part of the-duplicateinitialization we were unable to reset the autorefresh bookmarks for cache groups in the store. See the message log for the cause of the failure.
TT17022	The same attribute (attribute_name) has been set multiple times for the same subscriber (subscriber_name) for element element_name	AnALTER REPLICATIONstatement has altered the return service attribute more than once for the same store
TT17023	Store store_name is used in a route clause but does not exist	AROUTEclause quoted a non-existent store. Retry the operation with a differentROUTEname.
TT17024	ROUTE master master_name subscribersubscriber_name hostname host_name not found	A non-existentROUTEname was specified in a statement that is attempting toADDorDROPa route to a scheme. Retry the operation with a differentROUTEname.
TT17025	ROUTE master master_name subscriber subscriber_name cannot be created because a Master->Subscriber relationship does not exist between these stores	An attempt was made to set up a replicationROUTEfor a non-existent master/subscriber relationship. Retry the operation with a differentROUTEname.
TT17026	ROUTE master master_name subscribersubscriber_name cannot be created because an entry for this route already exists with priority priority_level, or is in the process of being created	TheROUTEname already exists. Retry the operation with a differentROUTEname or wait for the process that uses the specifiedROUTEname to complete.
TT17027	ROUTE master master_name subscribersubscriber_name cannot be created because an entry for this route already exists using interface interface, or is in the process of being created	TheROUTEname already exists. Retry the operation with a differentROUTEname or wait for the process that uses the specifiedROUTEname to complete.
TT17028	The PRIORITY attribute must be between 1 and 99	The specifiedPRIORITYvalue is out of range.
TT17029	This store (store_name on host_name) is not involved as a local store in replication scheme host_name.scheme	A scheme is attempting to be created on a store that is not involved in the scheme. Retry the operation with the correct store name, or involve the store in the specified scheme.
TT17031	CONFLICT REPORTING RESUME must be less than CONFLICT REPORTING SUSPEND for STORE store_name	TheRESUMEvalue must be less than theSUSPENDvalue for conflict reporting. Retry the operation with a smaller value.
TT17032	CONFLICT REPORTING RESUME cannot be set without a CONFLICT REPORTING SUSPEND value for STORE store_name	You cannot resume conflict reporting without specifying aSUSPENDvalue. Retry the operation after specifying aSUSPENDvalue.
TT17033	CONFLICT REPORTING RESUME or SUSPEND cannot be set for stores in an Active Standby scheme	Conflict resolution cannot be configured in an active standby scheme, therefore trying to supply conflict suspend/resume parameters is invalid.
TT17034	ASYNCHRONOUS WRITETHROUGH Cache groups cannot co-exist with a replication scheme that uses RETURN TWOSAFE	You cannot haveASYNCHRONOUS WRITETHROUGHcache groups in a replication scheme that usesRETURN TWOSAFE.
TT17035	CONFLICT SUSPEND/RESUME cannot be used with DATASTORE level replication or ACTIVE STANDBY schemes	Conflict resolution cannot be configured in a scheme that uses database level replication. Therefore attempting to supply conflict suspend/resume parameters is not allowed.
TT17036	SYNCHRONOUS WRITETHROUGH cache groups cannot be replicated in an ACTIVE STANDBY scheme. Either DROP or EXCLUDE the cache group for table owner.table_name	SYNCHRONOUS WRITETHROUGHcache groups cannot be replicated in anACTIVE STANDBYscheme.
TT17037	The receiver state in an ACTIVE STANDBY scheme cannot be set to STOP	When the store is involved in an active standby scheme, you cannot callttrepsubscriberstateset(,,,,2)or specify the utility operationttRepAdmin -receiver -name rep2 -host somemachine -dsn rep1 -state stop.
TT17038	The store is not a valid peer	The peer specified is not valid in the replication scheme
TT17039	Failed to bind name (name); socket: socket	Informational message about the host and IP address to which the replication agent was binding.
TT17040	Trying to create socket for name on DSN	Trying to create socket on an IP address for the indicated database.
TT17041	Failed to create Oracle DR scheme	This is a generic error, there is an accompanying detailed error message concerning the actual failure. Review that message to determine the problem and the fix.
TT17042	A Cache DR scheme can only be created on an ACTIVE STANDBY SUBSCRIBER	ThettRepAdmin -duplicate -initCacheDRoption can only be used when duplicating to an active standby subscriber. You have attempted to create a disaster recovery scheme on a database that is not involved in active standby replication. This is not supported.
TT17043	Failed to initialize Oracle DR tables	The initialization of the Oracle Disaster Recovery tables failed. In the user error log, review any error messages that were returned during the operation in which the error occurred for more details. Destroy the destination database and attempt to re-initialize the disaster recovery process.
TT17044	Exited early because could not get cache group information	The disaster recovery process exited early because it could not get required information. In the user error log, review any error messages that were returned during the operation in which the error occurred for more details. Destroy the destination database and attempt to re-initialize the disaster recovery process.
TT17045	Could not truncate cached tables on Oracle DR site	During disaster recovery, the replication agent could not truncate any cached tables. In the user error log, review any error messages that were returned during the operation in which the error occurred for more details. Destroy the destination database and attempt to re-initialize the disaster recovery process.
TT17046	Could not flush data to Oracle DR site	During disaster recovery, the replication agent could not flush data to Oracle. In the user error log, review any error messages that were returned during the operation in which the error occurred for more details. Review any error messages that were returned during the operation in which the error occurred for more details. Destroy the destination database and attempt to re-initialize the disaster recovery process.
TT17047	Could not commit data to the Oracle DR site	During disaster recovery, the replication agent could not commit data to Oracle. In the user error log, review any error messages that were returned during the operation in which the error occurred for more details. Destroy the destination database and attempt to re-initialize the disaster recovery process.
TT17048	Could not create thread to initialize the Oracle DR site	During disaster recovery, the replication agent could not create the thread to initialize Oracle. In the user error log, review any error messages that were returned during the operation in which the error occurred for more details. Destroy the destination database and attempt to re-initialize the disaster recovery process.
TT17049	Error invalidating store due to scheme inconsistency	To correct this problem, verify that the schemes involved in this operation are identical.
TT17050	Conflict Replication Reporting starting	Conflict reporting suspend/resume is configured on your system and the rate of conflict rate has fallen below the resume value. Reports are now being sent. This is an informational message.
TT17051	Conflict Replication Reporting stopping	Conflict reporting suspend/resume is configured on your system and the rate of conflict rate exceeds the suspend value. Reports are now suspended. This is an informational message.
TT17052	System table owner.tablename cannot be excluded from replication	System tables cannot be modified by users and must be included in the replication process.
TT17053	Table table_name is replicating in relaxed mode.	Informational message that appears in the log on the subscribing side. The master table being replicated is structurally different than the subscriber. As a result, there some performance overhead is required to achieve replication for this table.
TT17054	TABLE DEFINITION CHECKING cannot be set for stores in an Active Standby scheme	The store attributeTABLE DEFINITION CHECKINGcannot be used for stores in an active standby pair scheme.
TT17055	Asynchronous Materialized View Log Table schema.table cannot be included in a Replication Scheme.	An explicitALTERreplication include table was used on an Asynchronous materialized view log table.
TT17056	Dynamic Cache Group Table schema.table can only be replicated in an ACTIVE STANDBY PAIR replication scheme	A dynamic cache group can only be replicated if the replication scheme is an active standby pair. Dynamic cache groups cannot be replicated with regular replication.
TT17057	PROPAGATE cache groups cannot be replicated in an ACTIVE STANDBY scheme. Either DROP or EXCLUDE the cache group for table schema.table	User managed cache groups with propagated tables are not allowed in active standby replication schemes. You must either drop the cache group or exclude it from the replication scheme.
TT17058	Table <owner>.<tablename> cannot be part of a replication scheme when parallel mode replication is configured because it is defined with aging	You cannot include a table in a replication scheme when it has aging configured andReplicationApplyOrdering=1.
TT17059	Replicated INCLUDE TABLE failed for ( <owner>.<tablename>) because the table is not empty	You attempted a replicatedALTERSTANDBY PAIR...INCLUDE TABLEand the table is not empty.
TT17060	DDLReplicationAction can only be set to INCLUDE or EXCLUDE on the ACTIVE store in an ACTIVE STANDBY PAIR replication scheme	You attemptedALTER SESSION...SETDDL_REPLICATION_ACTIONon a store that is not active in the active standby pair replication scheme.
TT17061	When DDLReplicationAction = 'INCLUDE' tables must be created with a primary key or a unique constraint on non-nullable column(s)	You specified aDDL_REPLICATION_ACTIONthat requires the table(s) to be created with an index.
TT17062	DDLReplicationAction and DDLReplicationLevel can only be set on a store with an ACTIVE STANDBY PAIR scheme	You attempted to use theALTER SESSIONstatement to setDDLReplicationActionandDDLReplicationLevelon a store that is not part of an active standby pair scheme.
TT17063	CREATE INDEX can only refer to empty tables when DDLReplicationLevel > 1	WhenDDLReplicationLevelis greater than 1,CREATE INDEXis replicated. However, your tables must be empty.
TT17064	CREATE AS SELECT cannot be used when DDLReplicationLevel > 1	WhenDDLReplicationLevelis greater than 1,CREATE TABLEis configured for replication. However,CREATE TABLE ASSELECTis not supported.
TT17065	%s not permitted because DDLReplicationLevel > 1 and the store is not active	%srefers to a DDL action that is not permitted becauseDDLReplicationLevelis greater than 1 and the store is not active.
TT17066	Create table not permitted without ADMIN privilege when DDLReplicationLevel > 1 and DDLReplicationLevel is INCLUDE	WhenDDLReplicationLevelis greater than 1 and whenDDLReplicationActionis set to INCLUDE, then ADMIN privilege is required when replicatingCREATE TABLEstatements.
TT17067	Table <tablename> was truncated before inclusion into the ACTIVE STANDBY PAIR replication scheme	WhenALTER ACTIVE STANDBYPAIR...INCLUDEis executed, the table contents are truncated on the standby and subscriber(s) stores.
TT17068	Invalid value for ttDurableWhenAgentStoppedSet. Valid values are 0 and 1.	You specified an invalid value forttDurableWhenAgentStoppedSet.
TT17069	<stmt> is not permitted on the standby in an ACTIVE STANDBY PAIR scheme	The statements CREATE/DROP SYNONYM, GRANT/REVOKE, or CREATE/ALTER/DROP USER are not permitted on the standby in an ACTIVE STANDBY PAIR scheme.
TT19000	Open of document document_name failed	The TimesTen webserver received an error while sending data to the browser. Attempt to open the document again and verify that you have entered the correct name of the document.
TT19001	Send of number_of bytes to browser failed, error err_number	The TimesTen webserver received an error while sending data to the browser. The error referenced in this message provides more details on the problem.
TT19002	Spawn of CGI script, failed, error error_number	The TimesTen webserver received an error while spawning a CGI script. The error referenced in this message provides more details on the problem.
TT19003	Write of POST data failed	The TimesTen webserver received an error while sendingPOSTparameters to a CGI process.
TT19004	CGI script. script_name not executable	A CGI script. requested of the TimesTen webserver is not executable. Check your installation to verify that the script. is in the correct location and has the appropriate privileges.
TT19005	Web server bind to port failed, error error_number	The TimesTen Web server was unable to bind to its port. The port may be in use by another process. Verify that you specified the correct port number.
TT19006	Cannot filed perl in path	The TimesTen webserver was unable to find the version of PEL with the product. Check your installation.
TT19007	Web server system_call failed, error error_number	The TimesTen webserver was unable to get the host name of the client.
TT19008	Invalid HTTP date from client (string)	A date sent to the TimesTen Server is in an invalid format.
TT19009	Stat of file_name failed, error error_number	The TimesTen webserver was unable to determine file information for an HTTP document.
TT19010	Web server denying connection from host_ name(IP_address)	The TimesTen webserver is denying access from the indicated host. The webserver configuration file can be used to control access.
TT19011	Authorization failure from file_name	The TimesTen webserver is denying access to a password-protected page because the user name supplied is unknown or the password does not match. Verify that you have supplied the correct user name and password.
TT19012	Cannot open password file file_name	The TimesTen webserver is unable to open its password file. Check your installation.
TT19013	Bad entry in password file file_name	There is a bad entry in the TimesTen webserver's password file. Correct the entry and try again.
TT19014	TimesTen web server internal error	The TimesTen webserver has encountered an internal error. See the TimesTen user error log for more information.

References

NOTE:1274161.1 - TimesTen 11.2.1.X Documentation Set - Error And SNMP Trap Guide
NOTE:1338450.1 - TimesTen Warnings and Errors - TT0400 to TT9999
NOTE:1339522.1 - TimesTen Warnings and Errors - TT20000 to TT30103
NOTE:1339892.1 - TimesTen Warnings and Errors - TT40005 to TT48119

ITPub博客

TimesTen Warnings and Errors - TT10001 to TT19014 [ID 1339251.1]