List of Errors and Warnings

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 anomalously.

Note:

A C language header file containing symbolic names for the various TimesTen internal error codes is shipped with TimesTen. It is named tt_errCode.h and is installed in:

• timesten_home/install/include on Linux or UNIX
• timesten_home\install\include on Windows

ODBC applications that want to handle TimesTen native errors can use this header file to identify the errors.

The errors are listed according to the following ranges:

• Errors 0-999

• Errors 1000-1999

• Errors 2000-2999

• Errors 3000-3999

• Errors 4000-4999

• Errors 5000-5999

• Errors 6000-6999

• Errors 7000-7999

• Errors 8000-8999

• Errors 9000-9999

• Errors 10000-10999

• Errors 11000-11999

• Errors 12000-13999

• Errors 14000-14999

• Errors 15000-15999

• Errors 16000-16999

• Errors 17000-19999

• Errors 20000-39999

• Errors 40000-49999

• Errors 50000-59999

Errors 0-999

Error number	Error or warning message	Details
400	Database header fails basic sanity test	Type of Message: Internal Error Cause: The checkpoint file contains inconsistent or corrupted information. Impact: You cannot load or recover from the checkpoint file. User Action: If you receive this error for both checkpoint files, restore your database from a backup. For additional help, contact TimesTen Customer Support. For more information, see Back Up, Restore, and Migrate Data in TimesTen Classic in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.
402	Cannot close database file. OS-detected error: error_details	Type of Message: Internal Error Cause: While attempting to close the database file, the operating system encountered an error. Impact: You may be unable to connect to the database or load it into memory. User Action: Diagnose and troubleshoot the operating system error. Then, load the database into memory using ttAdmin -ramload. For more information, see ttAdmin in Oracle TimesTen In-Memory Database Reference. For additional help, contact TimesTen Customer Support.
403	Attempt to read from checkpoint truncated	Type of Message: Internal Error Cause: During a checkpoint read, TimesTen detected that the checkpoint file contains less information than expected. Impact: You cannot load or recover from the checkpoint file. User Action: If you receive this error for both checkpoint files, restore your database from a backup. For additional help, contact TimesTen Customer Support. For more information, see Back Up, Restore, and Migrate Data in TimesTen Classic in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.
404	Corrupted block header	Type of Message: Internal Error Cause: The checkpoint file contains inconsistent or corrupted information. Impact: You cannot load or recover from the checkpoint file. User Action: If you receive this error for both checkpoint files, restore your database from a backup. For additional help, contact TimesTen Customer Support. For more information, see Back Up, Restore, and Migrate Data in TimesTen Classic in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.
406	Incomplete write to file file_name. OS-detected error: error_details	Type of Message: Error Cause: TimesTen failed to write to a file. Impact: The operation you attempted failed. User Action: Diagnose and troubleshoot the operating system error. Then, verify the functionality of the file system or device that holds the reported file. After verifying the functionality, retry the operation. If the problem persists, contact TimesTen Customer Support.
407	Failed to seek in checkpoint file. OS-detected error: error_details	Type of Message: Internal Error Cause: An attempt to seek within a checkpoint file has failed. An operating system call failed with the specified operating system error. Impact: If this error occurs while loading or recovering from a checkpoint file, the attempt fails with that particular checkpoint file. User Action: If this error occurred while performing a checkpoint, retry the checkpoint. If the second attempt fails or the error occurred for any other reason, contact TimesTen Customer Support.
408	Failed to sync checkpoint file file_name to disk. OS-detected error: error_details	Type of Message: Internal Error Cause: An attempt to synchronize a checkpoint file to the file system has failed. An operating system call failed with the specified operating system error. Impact: If checkpoints keep failing, database recovery takes longer and transaction log files do not get purged. User Action: If this error occurred while performing a checkpoint, retry the checkpoint. If the second attempt fails or the error occurred for any other reason, contact TimesTen Customer Support.
409	Invalid checkpoint LSN	Type of Message: Internal Error Cause: The checkpoint file contains invalid internal information. Impact: The database cannot be recovered from the checkpoint file. User Action: Contact TimesTen Customer Support.
411	OS-detected error error while destroying directory directory_name	Type of Message: Error Cause: TimesTen cannot destroy the specified directory because of an operating system error. Impact: TimesTen cannot destroy the specified directory. User Action: Diagnose and troubleshoot the operating system error.
412	Bad file-open mode	Internal error. Contact TimesTen Customer Support.
413	Bad file-exists mode	Internal error. Contact TimesTen Customer Support.
414	Bad file-missing mode	Internal error. Contact TimesTen Customer Support.
415	Incompatible file-open modes	Internal error. Contact TimesTen Customer Support.
416	Block merge operation terminated due to high contention	Type of Message: Error Cause: The ttCompact built-in procedure failed to merge one or more blocks. Another operation is currently using one or more blocks. Impact: The ttCompact built-in procedure did not finish executing. User Action: Retry the operation using the ttCompact built-in procedure.
420	Operation is not permitted over unencrypted client-server connections	Type of Message: Error Cause: TimesTen cannot perform the operation in unencrypted client/server connections, and it is only supported in direct connections and encrypted client/server connnections. Impact: TimesTen cannot perform the operation. User Action: Attempt the operation over a direct connection or encrypted client/server connections. For information on defining DSNs for direct connections, see Defining DSNs for Direct or Client/Server Connections in Oracle TimesTen In-Memory Database Operations Guide.
421	Invalid file handle (may have been closed by application)	Type of Message: Error Cause: The file handle that reads the transaction log unexpectedly closed. This error generally indicates an application programming error. Impact: Your application cannot read the transaction log. User Action: Check your application to see if it is improperly closing the file handle associated with the transaction log.
422	File handle repositioned (may have been read or written by application)	Type of Message: Error Cause: The file handle that reads the transaction log unexpectedly repositioned. This error generally indicates an application programming error. Impact: Your application cannot read the transaction log. User Action: Check your application to see if it is reading from or writing to the wrong file handle.
423	Log directory in NFS is not supported on this platform	Type of Message: Error Cause: You attempted to store transaction log files in a Windows network share. Impact: TimesTen does not support storing transaction log files in a Windows network share. User Action: Ensure that the transaction log directory is not in a Windows network share.
424	Configuration option option not found in timesten.conf	Type of Message: Error Cause: TimesTen was unable to find either the timesten.conf file or the specified configuration option in the file. Impact: TimesTen cannot perform the operation. User Action: Ensure that the timesten.conf file is available and that it includes the specified configuration option. Then, retry the operation.
600	Checkpoint not done due to transaction commit/rollback failure	Type of Message: Error Cause: Commit or rollback of the transaction failed. Impact: Checkpointing was not attempted. User Action: Consider calling the ttCkpt built-in procedure to create a checkpoint. For more information, see ttCkpt in Oracle TimesTen In-Memory Database Reference.
601	Checkpoint failure	Type of Message: Error Cause: Checkpointing failed. Impact: TimesTen cannot create the checkpoint. User Action: Check that there is sufficient space on the file system and that database files are writable, then retry the operation.
604	Log missing record for checkpoint file_name (lsn log_file_number.log_file_offset). Error_details	Type of Message: Error Cause: The transaction log files may be truncated or corrupted. The transaction log may be missing log records related to the specified checkpoint file. Impact: TimesTen ignores the transaction log on the file system, moves any existing log files to the specified directory, and recovers the database from the checkpoint files. User Action: None.
605	Checkpoint log record (number.number) not present.	Type of Message: Error Cause: The specified log record is either missing or corrupted. If the transaction log file has been truncated or otherwise corrupted, it may be missing log records corresponding to the checkpoints on the file system. Impact: The database cannot be loaded into memory. User Action: Contact TimesTen Customer Support.
608	Another connection (# connection_id) has already configured table table_name for parallel insert	Type of Message: Error Cause: This error message can only occur on an Exalytics Business Intelligence server. The ttParallelInsertBegin built-in procedure failed because another connection already configured the specified table for parallel insert mode. Impact: The specified table cannot be configured for parallel insert mode. User Action: Wait and retry the operation. Consider terminating the existing ttParallelInsertBegin built-in procedure by using the ttParallelInsertEnd built-in procedure.
609	Database failed validity check	Type of Message: Internal Error Cause: TimesTen found an invalid database block while performing a checkpoint. Impact: The current checkpoint operation cannot complete. If several checkpoints fail in a row, the log files will start accumulating. User Action: Retry the checkpoint operation. If the problem persists, use the ttAdmin utility to unload and then reload the database into memory. For more information on the ttAdmin utility, see ttAdmin in Oracle TimesTen In-Memory Database Reference. If this does not solve the error, contact TimesTen Customer Support.
610	End-checkpoint log record not found	Type of Message: Internal Error Cause: TimesTen cannot find a checkpoint related log record while loading the database into memory. Impact: The database cannot be loaded into memory. User Action: Contact TimesTen Customer Support.
611	Backup process died	Type of Message: Error Cause: The ttBackupStatus built-in procedure returns this error message when an in-progress backup was killed or died unexpectedly. Impact: TimesTen cannot to create a backup copy of the database. User Action: Attempt to create another backup of the database with the ttBackup utility. For more information on the ttBackup utility, see ttBackup in Oracle TimesTen In-Memory Database Reference. If this is a recurrent error, contact TimesTen Customer Support.
615	Checkpoint failure: Error code error_number: error_message	Type of Message: Error Cause: TimesTen failed to complete the checkpoint operation. The accompanying error message describes the details of the failure. Impact: TimesTen did not complete the checkpoint operation. User Action: Retry the checkpoint operation. If the problem persists, contact TimesTen Customer Support.
616	Could not extract error message for checkpoint error code error_number	Type of Message: Error Cause: TimesTen failed to complete the checkpoint operation and could not retrieve the error message that describes the details of the failure. Impact: TimesTen did not complete the checkpoint operation. User Action: Retry the checkpoint operation. If the problem persists, contact TimesTen Customer Support.
617	Checkpoint invariant broken: message	Type of Message: Error Cause: Internal logic error. Impact: TimesTen did not complete the checkpoint operation. User Action: Retry the checkpoint operation. If the problem error persists, contact TimesTen Customer Support.
618	Cannot determine whether the checkpoint succeeded or failed	Type of Message: Warning Cause: The current connection requested a checkpoint operation and did not clear the checkpoint data structures within the allowed time. The connection cannot determine the result of the checkpoint operation because TimesTen reinitialized the checkpoint data structures to allow new checkpoint requests. Impact: TimesTen may not have completed the checkpoint operation. User Action: Use either the SYS.GV$CKPT_HISTORY or SYS.V$CKPT_HISTORY system views or the ttCkptHistory built-in procedure to determine whether the checkpoint operation succeeded or failed. See SYS.GV$CKPT_HISTORY or SYS.V$CKPT_HISTORY in Oracle TimesTen In-Memory Database System Tables and Views Reference for details on these views. For more information on the ttCkptHistory built-in procedure, see ttCkptHistory in the Oracle TimesTen In-Memory Database Reference.
620	Another table (table_name) is already configured for parallel insert	Type of Message: Error Cause: This error message can only occur on an Exalytics Business Intelligence server. The ttParallelInsertBegin built-in procedure failed because another table is already configured for parallel insert mode. Only one table is allowed to be in parallel insert mode at any given time. Impact: The table you specified cannot be configured for parallel insert mode. User Action: Wait and retry the operation. Consider terminating the existing ttParallelInsertBegin built-in procedure by using the ttParallelInsertEnd built-in procedure.
621	Table table_name is already configured for parallel insert. To change parallelism, call ttParallelInsertEnd and then ttParallelInsertBegin again.	Type of Message: Error Cause: This error message can only occur on an Exalytics Business Intelligence server. The ttParallelInsertBegin built-in procedure failed because the specified table is already configured for parallel insert mode. Only one table is allowed to be in parallel insert mode at any given time. Impact: None. User Action: None.
624	Recovery failed because the current value for CONNECTIONS is lower than the previous value (value)	Type of Message: Error Cause: You attempted to connect to a database that has currently in effect a larger value for the Connections first connection attribute. Impact: You cannot connect to the database. User Action: Modify the value of the Connections first connection attribute to increase the number of user-specified concurrent connections. For more information on the Connections first connection attribute, see Connections in Oracle TimesTen In-Memory Database Reference
625	blocked_operation cannot proceed because the following conflicting operation is in progress: blocker_info	Type of Message: Error Cause: TimesTen cannot execute the blocked operation because a checkpoint, backup, or data redistribution operation is in progress. Impact: The current blocked operation cannot begin. User Action: Wait until the checkpoint, backup, or data redistribution operation is completed and retry the checkpoint operation.
629	No permission to access database files	Type of Message: Error Cause: The TimesTen users does not have the file system permissions to access the database files or directory. Impact: TimesTen cannot connect to or create a database from the specified directory. User Action: Ensure that the TimesTen user belongs to a user group that has the proper file system permissions for the database files and directory. For more information, see Understanding the TimesTen users group in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.
649	Log file log_file_number has been purged	Type of Message: Warning Cause: TimesTen purged the specified log file. By default, TimesTen automatically removes archived transaction log files at checkpoint time. Impact: TimesTen removed the specified transaction log file from the file system. User Action: To retain archived transaction log files, set the LogPurge connection attribute to 0. For more information on transaction log files, see Managing Transaction Log Buffers and Files in Oracle TimesTen In-Memory Database Operations Guide. For more information on the LogPurge connection attribute, see LogPurge in the Oracle TimesTen In-Memory Database Reference.
650	Invalid backup type	Type of Message: Error Cause: The specified backup type is invalid. Impact: TimesTen cannot perform the backup. User Action: Specify a valid backup type. For more information about valid backup types, see ttBackup in Oracle TimesTen In-Memory Database Reference.
651	Backup path is not enabled for incremental backup	Type of Message: Error Cause: The backup file must be enabled for incremental backups when it is created. Impact: TimesTen cannot perform the incremental backup. User Action: Use the ttBackup -type option to enable incremental backups. For more information, see ttBackup in Oracle TimesTen In-Memory Database Reference.
652	Backup directory does not exist	Type of Message: Error Cause: The backup path you specified with the -dir option of the ttBackup utility does not exist. Impact: The backup cannot be performed. User Action: Create or specify a valid backup directory. For more information about the ttBackup utility, see ttBackup in Oracle TimesTen In-Memory Database Reference.
653	Operation is not permitted in parallel insert mode	Type of Message: Error Cause: This error message can only occur on an Exalytics Business Intelligence server. The operation failed because it is not permitted in parallel insert mode. When a table is configured for parallel insert mode, only INSERT operations are permitted. Also, the table ID of the target table must match the ID stored for the connection. Impact: The operation cannot be completed. User Action: Make sure you are performing INSERT operations on the table. Also, check that the table ID of the target table matches the ID stored for the connection.
654	Too many incremental-enabled backup directories.	Type of Message: Error Cause: You attempted to create an incremental backup instance. TimesTen is already at the maximum supported number of incremental-enabled backup instances for this database. For more information on the supported number of incremental-enabled backup instances, see Types of backups in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide. Impact: The incremental backup instance cannot be created. User Action: If you want to create a new incremental-enabled backup instance for this database, consider disabling incremental backups for another backup instance of this database. For more information on how to disable incremental backups, see ttBackup in Oracle TimesTen In-Memory Database Reference.
655	Global thread-pool limit (number) reached - operation aborted	Type of Message: Error Cause: This error message can only occur on an Exalytics Business Intelligence server. The ttParallelInsertBegin built-in procedure failed because the limit of the global thread pool has been reached. Impact: The requested degree of parallelism cannot be obtained. User Action: Consider stopping parallel insert operations initiated by other connections. Then, retry the operation.
657	Backup path exceeds maximum length of number characters	Type of Message: Error Cause: The backup path you specified with the -dir option of the ttBackup utility exceeds the maximum supported path length. The error message indicates the maximum supported path length. Impact: The backup cannot be performed. User Action: Create or specify a path no longer than the maximum supported path length. For more information about the ttBackup utility, see ttBackup in Oracle TimesTen In-Memory Database Reference.
658	Backup point is behind backup's log hold	Internal error. Contact TimesTen Customer Support.
659	Backup is out of date	Type of Message: Error Cause: The backup files specified by the backup directory, or base name, or both are not from the database that TimesTen is trying to back up. The backup files may be from a previous database that had the same database path name but which has since been destroyed. Impact: TimesTen failed to create a backup of the database. User Action: Use the -force option of the ttBackup utility to overwrite the out-of-date backup file. For more information on how to use ttBackup -force, see ttBackup in Oracle TimesTen In-Memory Database Reference.
660	Requested backup point cannot be honored because needed log files have been purged	Internal error. Contact TimesTen Customer Support.
661	Requested backup point cannot be honored because it is in the future	Internal error. Contact TimesTen Customer Support.
662	Database file file_name reflects unfinished restore operation	Type of Message: Error Cause: TimesTen cannot to recover from the specified database file because it is the result of an incomplete restore operation. Common causes for this are: - A user-initiated interruption of an in-progress restore operation. - An out of space condition in the file system that contains the database's checkpoint files. - A system failure. Impact: The TimesTen database cannot recover from the specified database file. User Action: Ensure that there is available space on the file system that contains your checkpoint files. If the file system is low on space, make more space available. Once you have made more space available, retry the restore operation.
664	Log record size of number bytes exceeds maximum size of number bytes	Internal error. Contact TimesTen Customer Support.
665	The size of LogBufMB should be at least LogBufParallelism * 8	Type of Message: Error Cause: You specified a value for the LogBufMB connection attribute that is too small. Impact: TimesTen cannot set the specified LogBufMb size. User Action: Increase the size of the LogBufMB connection attribute to a value that is at least eight times the value of the LogBufParallelism connection attribute. For more information on the LogBufMB connection attribute, see LogBufMB in Oracle TimesTen In-Memory Database Reference.
666	ReplicationApplyOrdering cannot be 0 if ReplicationParallelism is greater than 1.	Type of Message: Error Cause: If the number of replication threads is greater than 1, which configures the transmit and application of transactions in parallel, then configuration of an ordering mode is required in the ReplicationApplyOrdering attribute. The value of ReplicationApplyOrdering cannot be 0 if ReplicationParallelism is set to a value greater than 1. Impact: Parallel replication is not configured. User Action: In the DSN .ini file change either ReplicationApplyOrdering to a supported nonzero value or ReplicationParallelism to 0 or 1. For more information about ReplicationApplyOrdering, see ReplicationApplyOrdering in Oracle TimesTen In-Memory Database Reference. For more information about ReplicationParallelism, see ReplicationParallelism in the Oracle TimesTen In-Memory Database Reference.
668	LogBufParallelism value of value cannot be smaller than ReplicationParallelism value of value	Type of Message: Error Cause: The value of the ReplicationParallelism data store attribute is greater than the value of the LogBufParallelism first connection attribute. Impact: TimesTen cannot create or connect to the database. User Action: Change the value of the LogBufParallelism attribute, or the value of the ReplicationParallelism attribute, or both values so that the value of the ReplicationParallelism attribute is not greater than the value of the LogBufParallelism attribute. For more information on the LogBufParallelism first connection attribute, see LogBufParallelism in Oracle TimesTen In-Memory Database Reference. For more information on the ReplicationParallelism data store attribute, see ReplicationParallelism in the Oracle TimesTen In-Memory Database Reference.
669	Cannot change replication track within an active transaction.	Type of Message: Error Cause: Your application is not allowed to change the parallel replication track in which it writes logs after it has started a transaction. Impact: TimesTen cannot change the replication track. User Action: None. For more information on parallel replication tracks, see ReplicationTrack in Oracle TimesTen In-Memory Database Reference.
670	Batch cursors cannot be used because replication tracks are not enabled. (ReplicationParallelism =value ReplicationApplyOrdering =value).	Type of Message: Error Cause: Your application is not allowed to use batch cursors unless you have enabled parallel replication. Impact: You cannot use batch cursors in this situation. User Action: Either enable parallel replication or do not use batch cursors. For more information on parallel replication, see Configuring Automatic Parallel Replication with Disabled Commit Dependencies in Oracle TimesTen In-Memory Database Replication Guide.
680	Global thread-pool limit (number) reached - parallelism was set to value	Type of Message: Warning Cause: This warning message can only occur on an Exalytics Business Intelligence server. The degree of parallelism you specified for the ttParallelInsertBegin built-procedure cannot be met because the global thread pool limit has been reached. Impact: TimesTen sets the degree of parallelism to the maximum possible value based on the current global thread pool limit. User Action: Consider increasing the global thread pool limit with the ttParallelOpsPoolSizeSet built-in procedure.
681	Parallel Insert is not supported on this platform	Type of Message: Error Cause: This error message can only occur on an Exalytics Business Intelligence server. You attempted to use the ttParallelInsertBegin built-in procedure on an unsupported platform. Impact: The ttParallelInsertBegin built-in procedure cannot be used on the current platform. User Action: None.
682	Global thread-pool limit was set to value (max. allowable in this system)	Type of Message: Warning Cause: This warning message can only occur on an Exalytics Business Intelligence server. You specified a global thread pool limit that is greater than the maximum supported value. Impact: TimesTen sets the global thread pool to the maximum supported value. User Action: None.
683	Parallelism was set to value (max. allowable value)	Type of Message: Warning Cause: This warning message can only occur on an Exalytics Business Intelligence server. The degree of parallelism you specified for the ttParallelInsertBegin built-in procedure cannot be set because it exceeds the maximum allowable value. Impact: TimesTen sets the degree of parallelism to the maximum allowable value. User Action: None.
684	No table is configured for parallel insert	Type of Message: Warning Cause: This warning message can only occur on an Exalytics Business Intelligence server. You attempted to call the ttParallelInsertEnd built-in procedure. However, the current connection has not started a parallel insert operation. Impact: None. User Action: None.
700	Waiting for other 'in flux' threads failed	Type of Message: Error Cause: A flux is a semaphore used to serialize certain operations on a TimesTen database. This message is written to the log when a user process dies while waiting as multiple processes or threads are trying to connect, disconnect, recover, load, or unload the same database at the same time. Impact: The operation fails. User Action: Retry the operation. If the problem persists, contact TimesTen Customer Support.
701	Marking database 'in flux' failed	Type of Message: Error Cause: A flux is a semaphore used to serialize certain operations on a TimesTen database. This message is written to the log when a user process dies while waiting as multiple processes or threads are trying to connect, disconnect, recover, load, or unload the same database at the same time. Impact: The operation fails. User Action: Retry the operation. If the problem persists, contact TimesTen Customer Support.
702	Connect failed because max number of connections exceeded (max 2048)	Type of Message: Error Cause: TimesTen reached the maximum number of connections allowed for the database or instance. Impact: You cannot connect to the database. User Action: Consider disconnecting applications that are not using the database. For more information, see System Limits in Oracle TimesTen In-Memory Database Reference.
703	Subdaemon connect to database failed with error TTerror_number	Check other error messages for more information. If the problem cannot be identified from other errors, contact TimesTen Customer Support.
704	Connecting to a database undergoing recovery after invalidation	Type of Message: Error Cause: Another application connected to the database has failed; the RAM-resident version of the database is corrupted. Impact: You cannot connect to the database while it is being invalidated. User Action: Try to reconnect after the database invalidation completes.
706	Spawning a thread in the daemon failed	Internal error. Contact TimesTen Customer Support.
707	Attempt to connect to a database that has been manually unloaded from RAM	Type of Message: Error Cause: The application failed to connect to a database because the RAM residence policy of the database is set to manual. Also, the database has been manually unloaded from RAM. Impact: Applications cannot connect to the database. User Action: Load the database into memory using ttAdmin -ramload. For more information, see ttAdmin in Oracle TimesTen In-Memory Database Reference.
709	Adding new database to catalog failed, OS error 'error_details'	Type of Message: Error Cause: The TimesTen daemon cannot add the new database to the catalog. When a database is created, the daemon stores certain information about the database on the file system. Impact: The daemon cannot add the new database to the catalog. User Action: Diagnose and troubleshoot the reported operating system error. Additional information about the issue may be found in the Linux or UNIX syslog, or Windows Event Log. For Linux and UNIX, ensure that the daemon is running as the instance administrator.
711	Database creation in progress, try later	Type of Message: Error Cause: The database is currently being created and, therefore, cannot be accessed. Impact: You cannot access the database. User Action: Wait until the database is created. Then, try to reconnect to the database.
712	Unable to lock database memory segment, error os_error_number	1 (EPERM) - indicates that the daemon was started by a user other than the root user on Linux or a user without administrative privileges on Windows. Restart the daemon, as described in Working with the TimesTen Daemon in Oracle TimesTen In-Memory Database Operations Guide. 12 (ENOMEM) - indicates there was not enough lockable memory available on the system. Add more real memory, delete other memory consuming processes or connect with a different value for the MemoryLock attribute.
714	Log directory attribute does not match current value	Type of Message: Error Cause: The specified log directory for the connection does not match the log directory that was specified when the database was created. Impact: TimesTen cannot connect to the database and placed a warning for the directory name in conflict in the Linux or UNIX syslog, or the Windows Event Log. User Action: Specify a correct value for the LogDir connection attribute and try reconnecting. For more information on the LogDir connection attribute, see LogDir in Oracle TimesTen In-Memory Database Reference.
715	Unable to access log directory 'directory_name'. OS-detected error: error_details	Type of Message: Internal Error Cause: The path specified in the LogDir attribute is not accessible due to reasons described in error_details. Impact: TimesTen cannot perform the requested connect or disconnect operation. User Action: Change the LogDir attribute in the DSN to a valid directory or create the directory as needed. For more information about the LogDir attribute, see LogDir in Oracle TimesTen In-Memory Database Reference.
716	Undo of dead connection failed	Type of Message: Internal Error Cause: TimesTen returns this error in the daemon log. TimesTen cannot recover after a user application was terminated abruptly. Impact: The database is unloaded from memory. User Action: You should not exit from a TimesTen application before all connections are disconnected. Use signal handlers to catch signals that set a variable indicating that all connections must disconnect. Contact TimesTen Customer Support.
717	Update of database catalog entry failed	Type of Message: Error Cause: The TimesTen main daemon failed to update the DBI file in the daemon home directory to indicate a change in the meta-information about a database. Common causes for this are: - Your file system is full. - Ownership of the DBI file has changed. Impact: The database cannot be accessed. User Action: Check that your file system is not full. Also, check that file permission and ownership of the DBI file is correct. If the problem persists, contact TimesTen Customer Support.
720	Permission denied while opening directory directory_name	Permissions are not set correctly on the specified directory. Ensure that the directory has read and execute permissions for the TimesTen application.
721	No such directory: directory_name	The specified directory does not exist. Create that directory, or specify another one.
722	Log flusher reports error error_number (error_details)	The log manager was not able to flush the log due to operating system error.
723	Log cursor is not open	Internal error. Contact TimesTen Customer Support.
724	Log cursor has no current position	Internal error. Contact TimesTen Customer Support.
725	Log cursor is unpositioned	Internal error. Contact TimesTen Customer Support.
726	Log cursor is at end of log	Internal error. Contact TimesTen Customer Support.
743	Action is not permitted	Type of Message: Error Cause: You attempted to perform an action that is not supported by TimesTen. Impact: TimesTen cannot perform the attempted action. User Action: None.
744	Additional log data may exist after last valid log record (lsn log_file_number.log_file_offset)	Type of Message: Error Cause: TimesTen recovered from an operating system failure or an external event that corrupted one or more log files. Impact: Recovery has encountered log data after the last complete and intact log record, which suggests that one or more log records may have been lost. User Action: Recover the database from a backup or failover to a standby node. For additional help, contact TimesTen Customer Support.
745	Log file log_file_number contains partial log block (log file length = log_file_offset)	Type of Message: Error Cause: TimesTen recovered from an operating system failure or an external event that corrupted one or more log files. Impact: Recovery has encountered a log file that ends with a partial log block, which suggests that one or more log records may have been lost. User Action: Recover the database from a backup or failover to a standby node. For additional help, contact TimesTen Customer Support.
746	Extra log files found after end of log (log_file_offset files, starting with log_file_number)	Type of Message: Error Cause: TimesTen recovered from an operating system failure or an external event that corrupted one or more log files. Impact: Recovery has encountered log files after the file containing the last complete and intact log record, which suggests that one or more log records may have been lost. User Action: Recover the database from a backup or failover to a standby node. For additional help, contact TimesTen Customer Support.
747	Log read encountered incomplete log record at location log_file_number.log_file_offset	Type of Message: Error Cause: TimesTen recovered from an operating system failure or an external event that corrupted one or more log files. Impact: Recovery has encountered an incomplete log record after the logical end of the log, which suggests that one or more log records may have been lost. User Action: Recover the database from a backup or failover to a standby node. For additional help, contact TimesTen Customer Support.
748	Log ended unexpectedly at LSN log_file_number.log_file_offset; recovery terminated	Type of Message: Error Cause: TimesTen recovery encountered a defective log record at the specified LSN, and the LogAutoTruncate attribute is set to 0. Impact: TimesTen terminated recovery. Checkpoint and transaction log files remain unmodified. User Action: If possible, diagnose and troubleshoot the problem. Otherwise, contact TimesTen Customer Support. Do not modify or remove any TimesTen checkpoint or transaction log file without first creating a backup copy of the file. For more information on the LogAutoTruncate attribute, see LogAutoTruncate in Oracle TimesTen In-Memory Database Reference.
749	Invalid log block found at location log_file_number.log_file_offset -- details: error_details	Internal error. Contact TimesTen Customer Support.
750	Log read encountered log record with incorrect LSN at location log_file_number.log_file_offset -- remainder of log ignored	Type of Message: Error Cause: TimesTen encountered an unexpected value while reading the log. The transaction log corruption is likely the result of a crash affecting the file system. Impact: During recovery, the transaction log is effectively truncated at the point of the unexpected value, and the operation continues. Depending on the position of the error, some logged information may be lost. It is extremely unlikely that durable commits are lost, but it is possible on some operating systems. User Action: If this error is encountered at any time other than recovery, is not the result of a crash that you believe may have affected the disk controller, or if you are concerned that durably committed information may have been lost, contact TimesTen Customer Support.
751	Log read encountered log record with bad length at location log_file_number.log_file_offset -- remainder of log ignored	Type of Message: Error Cause: TimesTen encountered an unexpected value while reading the log. The transaction log corruption is likely the result of a crash affecting the file system. Impact: During recovery, the transaction log is effectively truncated at the point of the unexpected value, and the operation continues. Depending on the position of the error, some logged information may be lost. It is extremely unlikely that durable commits are lost, but it is possible on some operating systems. User Action: If this error is encountered at any time other than recovery, is not the result of a crash that you believe may have affected the disk controller, or if you are concerned that durably committed information may have been lost, contact TimesTen Customer Support.
752	Log read encountered log record with bad type at location log_file_number.log_file_offset -- remainder of log ignored	Type of Message: Error Cause: TimesTen encountered an unexpected value while reading the transaction log. The transaction log corruption is likely the result of a crash affecting the file system. Impact: During recovery, the transaction log is effectively truncated at the point of the unexpected value, and the operation continues. Depending on the position of the error, some logged information may be lost. It is extremely unlikely that durable commits are lost, but it is possible on some operating systems. User Action: If this error is encountered at any time other than recovery, is not the result of a crash that you believe may have affected the disk controller, or if you are concerned that durably committed information may have been lost, contact TimesTen Customer Support.
754	Cannot open log copy file log_file_name. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
755	Cannot chmod log copy file log_file_name. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
756	Cannot write to log copy file log_file_name: error_details	Internal error. Contact TimesTen Customer Support.
759	Log file log_file_number has invalid file header -- details: error_details	Internal error. Contact TimesTen Customer Support.
760	Attempt to read past the end of the log; LSN = log_file_number.log_file_offset	Internal error. Contact TimesTen Customer Support.
761	Cannot determine size of log file log_file_name. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
762	Invalid log truncation LSN log_file_number.log_file_offset	Internal error. Contact TimesTen Customer Support.
763	Cannot truncate log file log_file_name. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
764	Cannot move away log file log_file_number. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
765	Cannot create log file copy directory. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
766	Cannot create log reserve file log_file_name. OS-detected error: error_details	The log manager was not able to create reserved log space due to operating system error.
767	Cannot chmod log reserve file. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
768	Cannot determine size of log reserve file log_file_name. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
769	Log reserve file has invalid size value	Internal error. Contact TimesTen Customer Support.
770	Cannot open log reserve file log_file_name. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
771	Cannot write log reserve file log_file_name. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
772	Cannot seek in log reserve file log_file_name. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
773	Cannot sync log reserve file log_file_name. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
774	Cannot close log reserve file. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
775	Cannot delete log reserve file log_file_name. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
776	Cannot rename log reserve file; old name = old_file_name; new name = new_file_name. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
777	Log reserve exhausted	Internal error. Contact TimesTen Customer Support.
778	Log write failed because file system is full	Type of Message: Error Cause: The file system that holds the transaction log directory is full. Impact: If your application has AUTOCOMMIT set to 0, your application must rollback the transaction. If your application has AUTOCOMMIT set to 1, the command fails and the application has no further responsibilities. User Action: You must terminate your transaction. For more information, see Transaction Autocommit Behavior in Oracle TimesTen In-Memory Database Operations Guide.
779	Request denied; transaction must rollback because log file system is full	Type of Message: Error Cause: TimesTen is not accepting new requests for the transaction because error 778 was previously issued. Impact: TimesTen denied the request and performed a rollback of the transaction. User Action: None. For more information, see error 778.
780	Log file log_file_name not found	Internal error. Contact TimesTen Customer Support.
781	Cannot sync log file. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
782	Cannot rename log file log_file_name. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
783	Cannot sync log file even after retrying for number msec. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
784	Log record type is disallowed at this time	Internal error. Contact TimesTen Customer Support.
785	No log record exists at LSN log_file_number.log_file_offset	Internal error. Contact TimesTen Customer Support.
786	Cannot truncate log reserve file log_file_name. OS-detected error: error_details	The log manager was not able to maintain reserved log space due to operating system error.
787	Log file size exceeds maximum size of value MB	Type of Message: Error Cause: The transaction log file size exceeds the maximum defined size for TimesTen. Impact: TimesTen could not set the specified value for the LogFileSize attribute. User Action: Set the transaction log file size to a smaller value than the maximum allowed limit. For more information, see LogFileSize in Oracle TimesTen In-Memory Database Reference.
788	Log file size less than minimum size of number MB	Type of Message: Error Cause: The transaction log file size is less than the minimum size allowed by TimesTen. Impact: TimesTen could not set the specified value for the LogFileSize attribute. User Action: Set the transaction log file size to a bigger value than the minimum allowed limit. For more information, see LogFileSize in Oracle TimesTen In-Memory Database Reference.
789	LogFileSize size with parallel mode of replication is less than minimum size of 8* LogBufParallelism = value MB	Type of Message: Error Cause: You specified a value for the LogFileSize first connection attribute that is less than the minimum allowed value. Impact: TimesTen cannot create or connect to the database. User Action: Set the LogFileSize attribute to at least the specified value, eight times the value of the LogBufParallelism attribute. For more information on the LogFileSize attribute, see LogFileSize in Oracle TimesTen In-Memory Database Reference.
790	Incomplete write to log file log_file_number. OS-detected error: error_details	Unable to write all bytes to the log. If this happens during commit, it may be due to limited space on the file system for reclaim. See the description of error 902 for more information.
791	Cannot communicate with subdaemon	Type of Message: Error Cause: The TimesTen subdaemon is not running. Impact: TimesTen could not connect to or disconnect from a subdaemon. User Action: Restart the TimesTen daemon once all applications have disconnected from the database. For more information on how to start the daemon, see Working with the TimesTen Daemon in Oracle TimesTen In-Memory Database Operations Guide.
792	Attempt to read from log file log_file_number truncated; number/numberbytes read	Unable to read all bytes from the log. Internal error. Contact TimesTen Customer Support.
793	No idle subdaemons	Type of Message: Error Cause: TimesTen does not have any idle subdaemons available. Impact: You cannot connect to the database. User Action: Increase the maximum number of subdaemons that the TimesTen daemon may spawn in the ttendaemon.options file. For more information, see Managing Subdaemons in Oracle TimesTen In-Memory Database Operations Guide.
794	Thread join failed	Internal error. Contact TimesTen Customer Support.
795	Protocol failure	Internal error. Contact TimesTen Customer Support.
796	Failed to initialize procedure procedure_name with arguments/results list	Internal error. Contact TimesTen Customer Support.
797	Two threads using a single context	Type of Message: Error Cause: This error is issued by the debug version of the library. Impact: None. User Action: Contact TimesTen Customer Support.
798	Daemon reports error error_number	Daemon encountered a problem while TimesTen was creating a database, connecting to a database, disconnecting from a database or destroying a database.
799	Unable to connect to daemon; check daemon status	Type of Message: Error Cause: You attempted to create, connect, or destroy a database while the TimesTen daemon is not running. Impact: The operation was not successful. User Action: Start the daemon with the ttDaemonAdmin -start utility. For more information on the ttDaemonAdmin utility, see ttDaemonAdmin in Oracle TimesTen In-Memory Database Reference.
800	Too many errors - error buffer overflow	The number of errors pushed onto the error buffer exceeds the maximum of 50.
801	Malloc (C library) failed	Unable to allocate memory for TimesTen internal data structures.
802	Database memory_region space exhausted	Type of Message: Error Cause: TimesTen cannot allocate memory from the heap. An additional error message indicates which memory region is full. Impact: The database cannot continue normal operations. User Action: Increase the size of the appropriate memory region by modifying the set value for the PermSize or the TempSize attribute. You must unload the database from memory for changes in the PermSize or the TempSize attribute to take effect. For more information on how to unload the database from memory, see Unloading a Database from Memory for TimesTen Classic in Oracle TimesTen In-Memory Database Operations Guide. For more information on the PermSize or the TempSize attribute, see PermSize or TempSize, respectively, in the Oracle TimesTen In-Memory Database Reference.
803	Name length exceeds number characters	Type of Message: Error Cause: You specified an identifier or user name that exceeds the maximum number of characters allowed for basic names. Impact: TimesTen cannot create the specified identifier or user name. User Action: Select an identifier or user name within the allowed length for basic names. For more information on the number of characters allowed for basic names, see System Limits in Oracle TimesTen In-Memory Database Reference. For more information on the creation of identifiers or user names, see Creating or Identifying a Database User in the Oracle TimesTen In-Memory Database Security Guide.
804	Internal error: unknown error code error_string	Internal error. Contact TimesTen Customer Support.
805	Operation_name has not been implemented	Operation is recognized by the parser but its functionality is not currently available.
806	Garbage left on heap	Internal error. Contact TimesTen Customer Support.
807	Null pointer argument	Internal error. Contact TimesTen Customer Support.
808	Operation not atomic (failed and not undone)	Type of Message: Error Cause: Operation was not rolled back because logging was not enabled. Impact: Database may be inconsistent and may not be recoverable. User Action: You can try dumping and reloading the database using the ttBulkCp utility. You can also attempt the operation again with logging turned on (Logging=1). For more information about the ttBulkCp utility, see ttBulkCp in Oracle TimesTen In-Memory Database Reference.
809	Heap page directory overflow - cannot allocate space	This error indicates that the database's allocation structures are full. Try freeing any items possible or compacting the database, using ttCompact, and retrying the operation. Disconnecting all connections and reconnecting may also free up some space.
810	Pointer does not reference the database	Internal error. Contact TimesTen Customer Support.
812	Platform not supported (platform_name)	Type of Message: Error Cause: Some characteristics of your system (that is, alignments, type sizes) do not match the expected values, this indicates an installation error. Common causes for this are: - The TimesTen installation was copied directly from another system. - The TimesTen installation is on a network or shared drive, and that installation was installed by a system with different characteristics than your actual system. Impact: TimesTen cannot run on your system until the installation issue is resolved. User Action: Reinstall TimesTen. For more information, see Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.
814	Size specified by 'attribute' connection attribute is less than the minimum size of number megabytes	Type of Message: Error Cause: The specified PermSize or TempSize value is less than the allowed minimum. Impact: TimesTen cannot create the database or failed to establish a connection to the database. User Action: Increase the value for the PermSize or TempSize attribute, or both, to at least the minimum size indicated. For more information on defining DSNs, see Defining DSNs for Direct or Client/Server Connections in Oracle TimesTen In-Memory Database Operations Guide. For more information on the PermSize attribute, see PermSize in the Oracle TimesTen In-Memory Database Reference. For more information on the TempSize attribute, see TempSize in the Oracle TimesTen In-Memory Database Reference.
817	Internal error - TimesTen initialization failed	Internal error. Contact TimesTen Customer Support.
818	Sum of permanent and temporary region sizes (number MB) exceeds maximum size (number MB) allowed on this platform	During a database creation operation, the initial total size exceeded the maximum.
819	Database not compatible with library (library_name)	An attempt was made to connect to a database whose release is not recognized by the current release of TimesTen. Database must be upgraded to current release.
820	Cannot destroy database logs	Unable to remove the database logs because of an operating system error, such as "File in use."
821	No readable checkpoint files. OS error: 'error_number'.	Type of Message: Error Cause: TimesTen attempted to connect to a database that has been deleted and where both checkpoint files are missing. Impact: TimesTen cannot connect to the specified database. User Action: In TimesTen Classic, connect to the database with the Overwrite attribute set to 1 in the connection string to create a new database. For more information on the Overwrite attribute, see Overwrite in Oracle TimesTen In-Memory Database Reference.
823	Compact operation not fully completed	This warning is issued when a compaction operation cannot complete. Additional errors that are pushed should indicate the reason for the failure. For example, the failure could be caused by an out-of-space error.
824	Error information lost. Operation was at line number	The operation failed, but error information was lost. Contact TimesTen Customer Support regarding this lost error information.
826	Temporary database exists but is unattached	Type of Message: Error Cause: TimesTen cannot connect to a temporary database (Temporary attribute set) that is not attached to an application process. Impact: TimesTen cannot create or connect to the specified database. User Action: Destroy the temporary database with the ttDestroy utility, or set the AutoCreate and Overwrite attributes to 1 to overwrite the database. For more information on temporary databases, see Temporary in Oracle TimesTen In-Memory Database Reference. For more information on the AutoCreate or Overwrite attribute, see AutoCreate or Overwrite, respectively, in the Oracle TimesTen In-Memory Database Reference. For more information on the use of the ttDestroy utility, see ttDestroy in the Oracle TimesTen In-Memory Database Reference.
829	Bad options: Cannot copy logging options if first connection	Type of Message: Error Cause: The MatchLogOpts attribute is set to 1. Impact: TimesTen cannot create or connect to the database. User Action: Set the MatchLogOpts connection attribute to 0 and retry the operation.
830	Cannot create database file. OS-detected error: error_details	Type of Message: Error Cause: TimesTen is unable to overwrite an existing database or create the database checkpoint files because of an operating system error. Impact: You cannot create the database. User Action: Diagnose and troubleshoot the operating system error.
831	Cannot change mode on database file, error error_details	Unable to change the permissions on the database file during a database creation operation because of an operating system error such as file system permission problems.
832	Cannot open database file for reading. OS-detected error: error_details	Unable to open the database file for reading during a database connection operation because of an operating system error such as file system permission problems.
833	Database database_name not found	Type of Message: Error Cause: You attempted to destroy the specified database from the odbc.ini file. However, the specified database has already been destroyed or was never created. Impact: TimesTen cannot destroy the specified database. User Action: Verify the database name and retry the operation.
834	Database file invalid or corrupted	Type of Message: Error Cause: During recovery or a database connection operation the database file was found to be corrupted. Impact: You cannot use the TimesTen database. User Action: Recover the database from a backup or failover to a standby node. For more information, see General Failover and Recovery Procedures in Oracle TimesTen In-Memory Database Replication Guide. For additional help, contact TimesTen Customer Support.
835	Database file file_name reflects unfinished checkpoint	Type of Message: Error Cause: Either the application failed when writing the checkpoint or that there was not sufficient space on the file system to store the checkpoint. Impact: TimesTen cannot recover from the specified database file because the file is incomplete. Generally a connection is still possible when you receive this error because TimesTen saves two different checkpoints. User Action: Ensure that there is sufficient space on the file system to store the checkpoint and retry creating the checkpoint. For more information, see Check Transaction Log File Use of File System Space in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
836	Cannot create database shared-memory segment, error os_error_number	Type of Message: Error Cause: Unable to create a shared memory segment during a database creation or database connection operation. On Linux or UNIX systems, the shmget call can receive UNIX error EINVAL due to an inability to allocate a shared memory segment of the requested size. Common causes for this are: - The daemon is configured to use huge pages but huge pages are not configured or unavailable (under configured or being used by another process) on the system. - The operating system denies the request because the kernel parameters shmmax or shmall are set too low. - The configured swap space is insufficient for the requested shared memory segment. It is possible that some Linux or UNIX systems have additional possible causes for the error. The shmget man page lists the possibilities. Impact: You may be unable to connect to the database or load it into memory. User Action: Diagnose and troubleshoot the operating system error. For more information see Manage semaphores and shared memory segments in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
837	Cannot attach database shared-memory segment, error os_error_number	Type of Message: Error Cause: Unable to attach the database to the shared memory segment. On Linux or UNIX systems, the shmat call can fail due to one of: - The application does not have access to the shared memory segment. In this case the system error code is EACCESS. - The system cannot allocate memory to keep track of the allocation, or there is not enough data space to fit the segment. In this case the system error code is ENOMEM. - The attach exceeds the system limit on the number of shared memory segments for the process. In this case the system error code is EMFILE. It is possible that some Linux or UNIX systems have additional possible causes for the error. The shmat man page lists the possibilities. On Windows systems, the error could occur because of one of these reasons: - Access denied. - The system has no handles available. - The segment cannot be fit into the data section. Impact: You may be unable to connect to the database or load it into memory. User Action: Diagnose and troubleshoot the operating system error. For more information see Manage semaphores and shared memory segments in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
838	Cannot get database shared-memory segment, error os_error_number	Type of Message: Error Cause: Unable to access a shared memory segment during a database creation or database connection operation. On Linux or UNIX systems, the shmget call can receive UNIX error EINVAL due to an inability to allocate a shared memory segment of the requested size. Common causes for this are: - The daemon is configured to use huge pages but huge pages are not configured or unavailable (under configured or being used by another process) on the system. - The operating system denies the request because the kernel parameters shmmax or shmall are set too low. - The configured swap space is insufficient for the requested shared memory segment. It is possible that some Linux or UNIX systems have additional possible causes for the error. The shmget man page lists the possibilities. Impact: You may be unable to connect to the database or load it into memory. User Action: Diagnose and troubleshoot the operating system error. For more information see Manage semaphores and shared memory segments in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
839	Cannot access database because it is in use. A database may be considered to be in use due to its RAM Policy setting, even though there are no active connections to it.	Type of Message: Error Cause: TimesTen is unable to overwrite an existing database because a database with the same DSN is in use, or loaded into RAM, or both. Impact: You cannot create the database. User Action: Before you can overwrite an existing database, you must first unload the database from memory, close all active connections, set the RAM policy of the database to manual or inUse, or a combination of all of the above. - To unload the database from memory, use the ttStatus utility to find processes connected to the database and stop them. Then use the -ramUnload option of the ttAdmin utility to unload the database from memory. For more information on the ttAdmin or ttStatus utility, see ttAdmin or ttStatus, respectively, in the Oracle TimesTen In-Memory Database Reference. - To set the RAM policy to manual or inUse, see Specifying a RAM Policy in Oracle TimesTen In-Memory Database Operations Guide. - If you do not want to overwrite an existing database, set the Overwrite attribute to 0. For more information on the Overwrite attribute, see Overwrite in the Oracle TimesTen In-Memory Database Reference.
840	Cannot allocate space (number bytes) for non-shared database	Unable to allocate memory for the database header of a non-sharable database during a database creation or database connection operation. Not enough available swap space or physical memory. On Sun and IBM systems the data space limit may be increased with the command /usr/bin/ulimit -d n This command is built in some shells, in which case the shell may take precedence. For csh and tcsh: limit datasize n For bash: ulimit -d n For ksh, zsh and posix shells (sh or sh-posix): ulimit -d n # this is kbytes Bourne shells (sh or sh-bourne) have no built-in but may fall back on /usr/bin/ulimit.
841	Cannot detach database shared-memory segment, error os_error_number	Type of Message: Internal Error Cause: Unable to detach a shared memory segment during a disconnect from database operation. On Linux or UNIX systems, the shmdt call can receive UNIX error EINVAL. Common causes for this are: - There is no shared memory segment attached at shmaddr. - shmaddr is not aligned on a page boundary. It is possible that some Linux or UNIX systems have additional possible causes for the error. The shmdt man page lists the possibilities. Impact: The process that encounters this error is still attached to the shared memory segment. This may be problematic if this process is still running when an attempt is made to release the shared memory segment back to the operating system. User Action: Contact TimesTen Customer Support.
842	Invalid database identifier	Internal error. Contact TimesTen Customer Support.
843	Query/feature is not supported	The requested type of query is not supported.
844	Cannot write database file file_name. OS-detected error: error_details	Unable to write to the database file during creation of a database or initiation of a checkpoint, most likely due to a lack of space on the file system.
845	Cannot read database file. OS-detected error: error_details	Unable to read the database file during a database connection operation.
846	Database connection invalid or not current	To execute the current operation, an existing valid database connection was expected but not detected.
847	Cannot open database file for writing. OS-detected error: error_details	Unable to open a database file for writing during an initiation of a checkpoint because of an operating system error such as file system permission problems.
848	Recovery failed on number set(s) of database files; the TimesTen user error log has more information	Type of Message: Error Cause: Recovery failed on one or more checkpoint files. The user error log contains warning messages that indicate where the problem occurred. Impact: Review the warning messages in the user error log for possible impacts on the system. User Action: Recover the database from a backup or failover to a standby node. For more information, see General Failover and Recovery Procedures in Oracle TimesTen In-Memory Database Replication Guide. For additional help, contact TimesTen Customer Support.
849	Recovery failed on number set(s) of database files; try connecting with a larger database size	Type of Message: Error Cause: Recovery failed on one or more checkpoint files. During recovery, the database ran out of available space on the file system. Impact: The database cannot continue normal operations. User Action: Increase the value of the PermSize attribute so that your database has at least five percent available space on the permanent memory region. For more information on how to check the amount of memory in use by the database, see Check the amount of memory allocated to the database in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide. For more information on how to increase the value of PermSize, see Specifying the Memory Region Sizes of a Database in the Oracle TimesTen In-Memory Database Operations Guide. If you increase the PermSize attribute and still receive this error, contact TimesTen Customer Support.
850	Application has existing connection to database	Unable to create, connect to or destroy a database because the application has an existing connection to the database.
851	Cannot destroy database file: file_name	Warning: unable to destroy the database file during a database connection or destroy database operation because of an operating system error such as file system permission problems.
852	Unable to lock database memory segment, error error_number ...continuing with connection...	The system was unable to lock memory, but the error was ignored as per the MemoryLock attribute value. 1 - indicates that the daemon was started by a user other than the instance administrator. Restart the daemon as the instance administrator. 12 - indicates there was not enough lockable memory available on the system. Add more real memory, delete other memory-consuming processes or connect with a different value for the MemoryLock attribute.
854	Database database_name already exists	Unable to create a database because it already exists. Either use ttDestroy to destroy the existing database or connect with the Overwrite attribute set.
855	Top level heap not defined	Internal error. Contact TimesTen Customer Support.
857	Invalid flags for heap creation	Internal error. Contact TimesTen Customer Support.
860	Invalid savepoint	Internal error. Contact TimesTen Customer Support.
862	Number of active transactions exceeds the maximum	Internal error. Contact TimesTen Customer Support.
863	Operation requires an active transaction	Type of Message: Error Cause: When encountered during LOB operations, this error means the LOB reference has been invalidated due to transaction commit or rollback. Impact: The operation you attempted failed. User Action: In non-LOB contexts, this is an internal error. Contact TimesTen Customer Support in this case.
864	Operation prohibited with an active transaction.	Internal error. Contact TimesTen Customer Support.
865	Cannot destroy log file log_file_name. OS-detected error: error_details	Unable to destroy the log file during a database creation, database connection or destroy database operation because of an operating system error.
867	Cannot flush file buffers to disk. OS-detected error: error_details	While attempting to flush file buffers to file system, the operating system encountered an error. Check the OS error message.
868	Cannot open directory directory_name for reading. OS-detected error: error_details	While attempting to open the specified directory, the operating system encountered an error. Check the OS error message.
870	Cannot close database shared-memory segment, error error_number	Warning: Unable to close shared memory segment handle after detaching the segment.
871	Column column_name cannot be set to null	Cannot insert a NULL value into a non-nullable column or field. Check the input values and retry.
872	Length of inline columns (value) exceeds limit (value)	Length of the inline columns exceeds the maximum limit. Decrease the number or length of the columns in the table (only length of non-variable types matters). For more information on system limits, see System Limits and Defaults in Oracle TimesTen In-Memory Database Reference.
874	In an XE distribution PermSize can be no greater than number megabytes	Type of Message: Error Cause: The specified PermSize value is greater than the allowed maximum for an XE distribution. Impact: TimesTen cannot create the database or failed to establish a connection to the database. User Action: Decrease the value for the PermSize attribute, or both, to no more than the maximum size indicated.
875	Invalid or missing column number in column descriptor	Internal error. Contact TimesTen Customer Support.
876	Overlapping columns in column descriptor	Internal error. Contact TimesTen Customer Support.
877	Misaligned columns in column descriptor	Internal error. Contact TimesTen Customer Support.
878	Invalid column number	Type of Message: Internal Error Cause: Column number is not valid. Note that column numbers start at 1 (not 0). Impact: The operation you attempted failed. User Action: Contact TimesTen Customer Support.
879	Table owner_name.table_name has existing primary index	Internal error. Contact TimesTen Customer Support.
880	Cannot create index; table has maximum of number indexes	Type of Message: Error Cause: You attempted a CREATE INDEX statement on a table that has reached the maximum number of indexes per table. Impact: TimesTen cannot perform the operation. User Action: Consider using the DROP INDEX statement to remove an existing index that you no longer use from the table and retry the operation. For more information on CREATE INDEX, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference. For more information on DROP INDEX, see DROP INDEX in the Oracle TimesTen In-Memory Database SQL Reference.
881	Hash key and primary key columns must be identical	For a hash table, the columns of the hash key must be the same as the columns of the primary key.
882	Primary index must be unique	Internal error. Contact TimesTen Customer Support.
883	Index has open cursors	Cannot insert into, delete from or destroy an index that has open cursors on it.
884	Invalid hash index	Internal error. Contact TimesTen Customer Support.
885	Invalid T-tree index index_name	Internal error. Contact TimesTen Customer Support.
886	Index operation unsupported	Internal error. Contact TimesTen Customer Support.
887	Table has no primary index	Internal error. Contact TimesTen Customer Support.
888	Tail of log truncated at position number.number	Type of Message: Error Cause: Recovery was unable to read the log past the specified LSN. Impact: The log was truncated at that point to allow recovery to continue. User Action: You may want to review the original pre-truncated log file. This log file can be found in a directory called savedLogFiles, which is a subdirectory of the log directory of the database.
889	Number of log files exceeded the maximum	Cannot create a transaction log file because the number of transaction log files that currently exists is at the maximum of 9,999. Roll back and perform a checkpoint. See Checkpoint Operations in Oracle TimesTen In-Memory Database Operations Guide.
890	Log file name too long	Internal error. Contact TimesTen Customer Support.
891	Log file log_file_name already exists	Internal error. Contact TimesTen Customer Support.
892	Cannot create log file log_file_name. OS-detected error: error_details	While attempting to create a log file, the operating system encountered an error such as file system permission problems.
893	Cannot open log file log_file_name. OS-detected error: error_details	While attempting to open a log file, the operating system encountered an error such as file system permission problems.
894	Cannot write log file log_file_number. OS-detected error: error_details	While attempting to write to a log file, the operating system encountered an error such as file system permission problems.
895	Cannot close log file. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
896	Cannot read log file log_file_number	While attempting to read from a log file, the operating system encountered an error such as file system permission problems.
897	Cannot seek in log file. OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
898	Log record exceeds maximum size of log file	Internal error. Contact TimesTen Customer Support.
899	Log buffer size exceeds maximum size of number MB	Type of Message: Error Cause: You have specified a log buffer size value that exceeds the log buffer size limit. For more information on the log buffer size limit, see LogBufMB in Oracle TimesTen In-Memory Database Reference. Impact: You cannot create or connect to the database. User Action: Call the ttConfiguration built-in procedure to check the current value of LogBufMB. If the current value of LogBufMB exceeds the log buffer size limit, modify the value of LogBufMB to a supported value. For more information on ttConfiguration, see ttConfiguration in Oracle TimesTen In-Memory Database Reference. For more information on modifying the value of LogBufMB, see LogBufMB in the Oracle TimesTen In-Memory Database Reference.
900	Cannot generate temporary file name	Internal error. Contact TimesTen Customer Support.
901	Cannot create file file_name for reclaim records: OS-detected error: error_details	Unable to create a temporary file to be used to spool the headers of reclaimed log records.
902	Cannot write file file_name for reclaim records: OS-detected error: error_details	Unable to write to the temporary file used to spool the headers of reclaimed transaction log records. Ensure that there is enough space in the file system where your temporary directory resides or change the location of your temporary directory by setting the TMP environment variable on Windows or the TMPDIR environment variable on Linux and UNIX. To avoid writing this file all together, each transaction should limit the number of deleted rows, deleted varying-length data and updated varying-length data. In particular, the total of (number of deletes) + (number of deletes to varying-length data) + (number of updates to varying-length data) should be limited to 90, to avoid writing to this file.
903	Cannot seek in file file_name for reclaim records: OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
904	Cannot read file file_name for reclaim records: OS-detected error: error_details	Unable to read the temporary file used to spool the headers of reclaimed log records.
905	Invalid index identifier	Internal error. Contact TimesTen Customer Support.
906	Cannot change mode on log file log_file_name, error error_details	While attempting to change file mode access permissions on the log file, the operating system encountered an error.
907	Unique constraint (constraint_name) violated at Rowid <row_number>extra_info	There are duplicate values in the primary key column(s) of a table or in the column(s) of a unique index. If the problem persists, contact TimesTen Customer Support.
908	Key not found in object_name	Internal error. Contact TimesTen Customer Support.
909	Cannot update primary key or hash key	Cannot update values in the primary key columns or hash key columns of a table.
910	Row has already been deleted	A transaction is trying to delete or update a row that it has already deleted.
911	Null or blank table name	During table creation, no name was provided for the table.
912	Row with id not found in table	Internal error. Contact TimesTen Customer Support.
913	MaxCnt exceeds number	Internal error. Contact TimesTen Customer Support.
914	'String' is not a valid table name	The length of the table name exceeds its maximum of 30 characters.
916	Key column must be not-null	Cannot insert a NULL value into a key column.
917	Invalid column number for key	The column number of the table that is specified as a key column is invalid.
918	Key column count is zero or greater than the number of table columns	The number of key columns is either zero or exceeds the number of columns in the table.
919	Invalid comparison condition	Internal error. Contact TimesTen Customer Support.
920	Invalid default value for column column_name	The specified default value is not a constant or one of the allowed values, NULL was specified for a non-nullable column or the default data type is not compatible with that of the column.
921	Unsupported column type	Data type is recognized by the parser but is not currently supported.
922	Invalid row identifier	Internal error. Contact TimesTen Customer Support.
923	Invalid row implementation	Internal error. Contact TimesTen Customer Support.
924	Row implementation unsupported for operation	Internal error. Contact TimesTen Customer Support.
925	Cannot create database semaphores (error_info)	Type of Message: Error Cause: Unable to create a semaphore during a database creation or database connection operation. This error usually indicates that your system is not tuned for TimesTen. Impact: Cannot create database semaphores. User Action: Tune your system for TimesTen. For more information, see Operating system prerequisites in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.
926	Cannot create database latch (error error_number, info extra_info)	Type of Message: Error Cause: On Windows, there is a shortage of system resources such as "named events." Impact: Cannot create database latch. User Action: End any stray processes that are running. If that does not help, restart the system. If the problem persists, contact TimesTen Customer Support.
927	Cannot open database semaphore (number) number	Type of Message: Error Cause: On Windows, there is a shortage of system resources such as "named events." Impact: Cannot open the database semaphore. User Action: End any stray processes that are running. If that does not help, restart the system. If the problem persists, contact TimesTen Customer Support.
928	Error in semaphore operation (error error_number)	Type of Message: Error Cause: An operating system semaphore operation failed. Impact: The severity of the impact is unknown and requires additional diagnosis. User Action: Contact TimesTen Customer Support.
931	Database has maximum number of connections	Type of Message: Error Cause: TimesTen is unable to create a reserved connection to a database that has reached the maximum allowed number of concurrent connections. Impact: TimesTen cannot perform the operation. User Action: Close one or more of the open connections to the database. Then, retry the operation.
932	Invalid column name: string	The specified column name is invalid. The string in the error message gives more information about the specific problem or column name involved.
933	Invalid SQL string	SQL string is NULL.
934	Invalid binary string	A SQL statement has a binary string constant that is larger than 20,000 characters. To get around this limitation, specify the binary value as a parameter. Then, it can be bound to a program variable of arbitrary length.
935	SQL statement must return a result	Internal error. Contact TimesTen Customer Support.
936	SQL statement may return multiple results	Internal error. Contact TimesTen Customer Support.
937	Invalid compiled command number	Internal error. Contact TimesTen Customer Support.
938	SQL statement has arguments	Internal error. Contact TimesTen Customer Support.
939	SQL statement has no arguments	Internal error. Contact TimesTen Customer Support.
940	SQL command has too many results	A maximum of 32,767 projected expressions are allowed for a single SELECT statement. This includes all columns referenced indirectly by any * expressions.
941	Execution of operation not possible - dependent object(e.g. command or index) is in use.	The application is currently scanning the table or a corresponding index, so it cannot perform operations such as creating an index, dropping the table or dropping an index. The application must wait until scanning is complete.
942	Imprecise numeric coercion	Warning: unable to convert a numeric value from one type to another without losing precision.
943	MaxTups argument must be positive	Internal error. Contact TimesTen Customer Support.
946	SQL command is no longer valid	Type of Message: Error Cause: The command has been invalidated. This may happen as the result of some DDL operations, such as ALTER TABLE, CREATE INDEX, DROP INDEX, or a modification of optimizer statistics. TimesTen cannot re-prepare the command. Impact: In some cases, TimesTen attempts to re-prepare the command. In other cases, such as if a table has been dropped and re-created, TimesTen does not attempt to re-prepare the command. User Action: Restart your application. If you still receive this error, attempt to re-prepare the command.
947	Cannot generate log file name	A failure occurred generating a name for the log file. Additional errors are returned indicating the reason for this failure.
948	Read log buffer size specified is too small or too large	Internal error. Contact TimesTen Customer Support.
950	Invalid format width	Internal error. Contact TimesTen Customer Support.
951	Invalid float precision	The precision of a float type cannot be negative.
952	Null string too long - value will be truncated	Internal error. Contact TimesTen Customer Support.
954	SQL command has mismatched version number	Internal error. Contact TimesTen Customer Support.
955	Current Connections attribute setting (value) exceeded by this connection.	Type of Message: Error Cause: You attempted to connect to a database that has reached the maximum number of user-specified concurrent connections. Impact: You cannot connect to the database. User Action: Modify the value of the Connections attribute to increase the maximum number of user-specified concurrent connections. The database must be unloaded from memory for the change to take effect. For more information on the Connections attribute, see Connections in Oracle TimesTen In-Memory Database Reference.
956	Merge statement cannot update a primary key	You are attempting to update a primary key through a MERGE statement. This is not supported.
957	Cannot start a transaction because the database is in quiesced state	Type of Message: Error Cause: You attempted to start a transaction while the database was in quiesced state. Impact: TimesTen cannot start the transaction. User Action: Unload and re-load the database to return it to normal state.
958	Cannot connect because the database is in quiesced state	Type of Message: Error Cause: You attempted to connect to a database that was in quiesced state. Impact: The connection attempt failed. User Action: Unload and re-load the database to return it to normal state.
959	Subdaemon can't find the clean checkpoint [expected_ckpt] it is supposed to load from; found [found_ckpt] instead	Type of Message: Error Cause: The subdaemon could not find the clean checkpoint to load the database. The checkpoint file may be corrupted. Impact: TimesTen cannot load the database. User Action: Contact TimesTen Customer Support.
960	String exceeds column width for column column_name - value will be truncated	Warning: attempting to insert a string into a character or binary column that is larger than the column's maximum length. The string is truncated.
962	Bad value for parameter_name	Type of Message: Warning Cause: While estimating or updating statistics, TimesTen found an invalid value for a variable-length data type. Impact: None. TimesTen ignored the invalid value for the statistics operation. User Action: Contact TimesTen Customer Support.
963	Internal error writing checkpoint log record	Type of Message: Internal Error Cause: An error was encountered while writing the checkpoint log record. A common cause for this is low available space in the file system that contains your transaction log files. Impact: The checkpoint cannot complete. If checkpoints keep failing, database recovery takes longer and transaction log files do not get purged. User Action: Ensure that there is available space on the file system that contains your transaction log files. If the file system is low on space, make more space available. For more information, see Check Transaction Log File Use of File System Space in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide. Once you have made more space available, retry the checkpoint. If you still receive this error, contact TimesTen Customer Support.
965	Specified join order is not applicable - valid join orders will be considered	Warning: the specified join order is not applicable and is ignored. All valid join orders are considered.
966	Join string too long - join order not changed	Warning: the length of the specified join order exceeds the maximum of 1,024, and is ignored. All valid join orders are considered.
967	Bad join string - join order not changed	The join order set by ttOptSetOrder built-in either has incorrect format and therefore is ignored. The correct format is a list of table names separated by spaces.
968	Invalid index usage specification	The index usage string provided to the ttOptUseIndex built-in procedure has a syntax error.
969	Index string too long - default index usage will be used	The index usage string provided to the ttOptUseIndex built-in procedure is too long.
970	Invalid cursor handle	Internal error. Contact TimesTen Customer Support.
971	Supplied buffer too small	Internal error. Contact TimesTen Customer Support.
972	Invalid database handle	Internal error. Contact TimesTen Customer Support.
973	Invalid savepoint handle	Internal error. Contact TimesTen Customer Support.
974	Invalid format handle	Internal error. Contact TimesTen Customer Support.
975	Invalid table handle	Internal error. Contact TimesTen Customer Support.
976	Invalid index handle	Internal error. Contact TimesTen Customer Support.
977	Invalid row handle	Internal error. Contact TimesTen Customer Support.
978	Invalid command handle	Internal error. Contact TimesTen Customer Support.
979	Invalid command argument handle	Internal error. Contact TimesTen Customer Support.
980	Input buffer not properly aligned	Internal error. Contact TimesTen Customer Support.
981	Invalid cursor type (R/W)	Internal error. Contact TimesTen Customer Support.
982	String exceeds column widthcolumn_name	Type of Message: Error Cause: You attempted to insert a string that exceeds the column width of the specified column. Impact: TimesTen cannot perform the operation. User Action: Consider dropping and re-creating the table with the appropriate column width for the specified column or shortening the length of the string to insert.
983	Invalid index or table name string - default index usage will be used	The specified table or index was not found. The default index is used.
984	Cannot find index that matches index_name. This index usage specification will be ignored.	The specified index was not found. No index specification is used.
985	Application cannot change statistics on statistics system tables	Statistics system tables are maintained by the system and cannot be changed by the application.
990	Invalid maxCnt value for table	Internal error. Contact TimesTen Customer Support.
991	Quota exceeds maximum row count for table	Internal error. Contact TimesTen Customer Support.
992	Number of table pages in use exceeds quota	Internal error. Contact TimesTen Customer Support.
993	Number of index pages in use exceeds quota	Internal error. Contact TimesTen Customer Support.
994	Database connection terminated. Please reconnect.	Type of Message: Error Cause: An unexpected error or abrupt disconnect (that is, control-C) caused the connection to be terminated. Impact: The database connection is terminated. User Action: The application can reconnect once all connections have disconnected. If this error was accompanied by other errors indicating an assertion or unexpected error from the engine, contact TimesTen Customer Support.
995	Cannot destroy database shared-memory segment, error os_error_number	This indicates a failed attempt to remove a shared memory segment. The OS-specific error code given in the message indicates the reason for this failure.
997	Database path too long	The path to the database files is too long. The maximum allowed is 256 characters.
998	Connections cannot be used across fork()	TimesTen does not allow a child process to use a connection opened by its parent. Any attempt from a child process using fork() to use a connection opened by the parent process returns this error.
999	Constraint columns and index columns used for that constraint must be identical	Type of Message: Error Cause: The columns on which we want to apply a constraint and their order cannot differ from that of the columns of the index which is used to implement that constraint. Impact: TimesTen cannot perform the operation. User Action: Change index columns to match with constraint columns.

Errors 1000-1999

Error number	Error or warning message	Details
1000	Cannot set primary key columns to different values	Type of Message: Error Cause: You attempted to change the value of a primary key column. TimesTen does not support changing the values of primary key columns. Impact: TimesTen cannot change the value of the primary key column. User Action: Specify a valid SQL UPDATE statement and retry the operation. For more information about the UPDATE SQL statement, see UPDATE in Oracle TimesTen In-Memory Database SQL Reference.
1001	Syntax error in SQL statement statement	Type of Message: Error Cause: The parser detected a syntax error in the specified SQL statement. Impact: TimesTen cannot perform the SQL operation. User Action: Correct the SQL syntax and retry the operation. For more information about SQL syntax, see SQL syntax in Oracle TimesTen In-Memory Database SQL Reference. If your SQL syntax is correct, check if you are using a TimesTen SQL reserved word. If you are using a TimesTen SQL reserved word, add quotes around the reserved word or use an alternate identifier. For more information, see Reserved Words in the Oracle TimesTen In-Memory Database SQL Reference.
1002	Identifier \"string\" in SQL statement exceeds maximum length (number)	Type of Message: Error Cause: The length of the specified identifier of the SQL statement exceeds the maximum allowed length. Impact: TimesTen cannot perform the SQL operation. User Action: Set the identifier to a value that is greater than zero and does not exceed the maximum allowed length. Then, retry the operation.
1004	Identifier in SQL statement is zero-length	Type of Message: Error Cause: You specified a SQL statement that is missing an identifier name such as a table name, correlation schema name, host name, etc. Impact: TimesTen cannot perform the SQL operation. User Action: Ensure that your SQL statement contains valid identifiers. Then, retry the operation.
1005	Identifier in SQL statement is all spaces	Type of Message: Error Cause: You specified a table name or identifier that is all spaces. Impact: TimesTen cannot perform the SQL operation. User Action: Specify a valid table name or identifier. Then, retry the operation.
1006	Identifier \"string\" contains invalid characters	Type of Message: Error Cause: The specified identifier contains invalid characters. Identifiers can contain only characters from the ASCII character set. TimesTen does not support other characters, such as native language characters, in identifiers. Impact: TimesTen cannot perform the operation. User Action: Correct the identifier using only characters from the ASCII character set. Then, retry the operation.
1007	Invalid parameter marker name	Type of Message: Error Cause: You attempted to use a parameter marker name that is reserved for system use. Impact: TimesTen cannot perform the operation. User Action: Use a valid parameter marker name. If you are using a TimesTen SQL reserved word, add quotes around the reserved word or use an alternate identifier. For more information, see Reserved Words in Oracle TimesTen In-Memory Database SQL Reference.
1008	PL/SQL object names cannot contain lower-case letters or trailing spaces in the TimesTen environment	Type of Message: Error Cause: The PL/SQL program unit name contains lower-case letters or trailing spaces. Impact: TimesTen cannot create the PL/SQL program unit. User Action: Specify a valid name for the PL/SQL program unit. Then, retry the operation. For more information, see Creating Procedures and Functions in Oracle TimesTen In-Memory Database PL/SQL Developer's Guide.
1009	Pre-allocated log block found at location log_file_number.log_file_offset -- details: details	Type of Message: Error Cause: TimesTen found a preallocated log block at the specified location. A common cause for this is that TimesTen is reading past the logical end of a log file. Impact: The log reading application failed. It is possible that your database is invalidated, but it is unlikely. User Action: Contact TimesTen Customer Support.
1010	Cannot start a transaction because the element has lost contact with membership service	Type of Message: Error Cause: The element is in frozen state. The data instance is unable to connect with the servers of the membership service. Impact: TimesTen failed to start a transaction. User Action: To return the element to a normal state, ensure that the data instance is able connect to the servers of the membership service.
1011	Cannot connect because the element has lost contact with membership service	Type of Message: Error Cause: The element is in frozen state. The data instance is unable to connect with the servers of the membership service. Impact: No new connections can be established to the element. User Action: To return the element to a normal state, ensure that the data instance is able to connect to the servers of the membership service.
1012	Identifier \"string\" begins with a prefix that may only be used for internal objects	Type of Message: Error Cause: The specified identifier begins with a prefix which can only be used for internal objects of global indexes. Impact: TimesTen cannot perform the operation. User Action: Correct the identifier by changing the prefix. Then retry the operation.
1017	Column number in ORDER BY clause must be greater than zero	Type of Message: Error Cause: You attempted to reference a column number in an ORDER BY clause with a value of zero. Impact: TimesTen cannot perform the operation. User Action: Set the column number in the ORDER BY clause to a value greater than zero and retry the operation.
1022	Constant number is out of representable range	Type of Message: Error Cause: The specified constant value is out of range for the data type and cannot fit in the buffer. Impact: TimesTen cannot perform the operation. User Action: Set a constant value within the supported range and retry the operation. For information on the range of each data type, see Type specifications in Oracle TimesTen In-Memory Database SQL Reference.
1024	Referenced table table_name not in FROM list	Type of Message: Error Cause: The referenced table is not specified in the FROM list of the query. Impact: TimesTen cannot perform the operation. User Action: Ensure that you specify valid table names and that you specify referenced tables in the FROM list. Then, retry the operation.
1025	Number of column names in INSERT statement is not equal to number of values	Type of Message: Error Cause: You specified a number of column names in the INSERT statement that does not match the number of values of the VALUES clause. Impact: TimesTen cannot perform the operation. User Action: Specify a number of column names in the INSERT statement that matches the number of values in the VALUES clause and retry the operation.
1026	Column names must contain at least one character	Type of Message: Error Cause: You specified an invalid column name. The name of a column name cannot be blank. The name of a table column is missing. Impact: TimesTen cannot perform the operation. User Action: Use at least one character to set the column name and retry the operation.
1027	Floating-point precision out of suppported range	Type of Message: Error Cause: You specified a floating-point value that is out of the supported range. Impact: TimesTen cannot perform the operation. User Action: Set the floating-point precision to a number that is within the supported range and retry the operation. For more information on FLOAT precision, see FLOAT and FLOAT(n) in Oracle TimesTen In-Memory Database SQL Reference.
1032	Aggregate function cannot be nested	Type of Message: Error Cause: You attempted to nest an aggregate function. An aggregate function cannot be called within another aggregate function. Impact: TimesTen cannot perform the operation. User Action: Correct the nested aggregate and retry the operation. For more information about aggregate functions, see Aggregate functions in Oracle TimesTen In-Memory Database SQL Reference.
1033	Aggregate function cannot be specified in group by clause	Type of Message: Error Cause: You specified an aggregate function in a GROUP BY clause. An aggregate function cannot be called within a GROUP BY clause. Impact: TimesTen cannot perform the operation. User Action: Specify a correct GROUP BY clause and retry the operation. For more information about the GROUP BY clause, see GROUP BY clause in Oracle TimesTen In-Memory Database SQL Reference.
1061	PRIMARY KEY syntax can only be used once in statement	Type of Message: Error Cause: You specified more than one PRIMARY KEY clause. A table can have at most one PRIMARY KEY column list or constraint. Impact: TimesTen cannot perform the operation. User Action: Ensure that your SQL statement only contains one PRIMARY KEY clause. If you are attempting to create a primary key on multiple columns, ensure that all of the columns are specified within the same PRIMARY KEY clause. For more information, see Primary Keys, Foreign Keys and Unique Indexes in Oracle TimesTen In-Memory Database Operations Guide.
1062	HASH distribution syntax can only be used once in statement	Type of Message: Error Cause: You attempted a CREATE TABLE statement while specifying more than one DISTRIBUTE BY clause. Impact: TimesTen cannot perform the operation. User Action: Verify the CREATE TABLE statement and ensure that the DISTRIBUTE BY clause is only specified once. For more information on the CREATE TABLE statement, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference.
1063	Changing the value of a distribution key is not permitted	Type of Message: Error Cause: You attempted to update a value in a column that is used as the distribution key of the table. Impact: TimesTen cannot perform the operation. User Action: Ensure that your SQL statement does not update any value of the distribution key columns list of the table, and retry the operation.
1064	Multiple matching foreign key constraints for 'distribute by reference'.	Type of Message: Error Cause: You attempted to create a table with a BY REFERENCE distribution scheme and two or more foreign key constraints without specifying which foreign key constraint to use for the BY REFERENCE distribution of the table. Impact: TimesTen cannot create the table. User Action: Specify the foreign key constraint to use for the BY REFERENCE distribution scheme, and retry the operation. For more information, see Reference in Oracle TimesTen In-Memory Database Scaleout User's Guide.
1065	No matching foreign key constraint for 'distribute by reference'.	Type of Message: Error Cause: You attempted to create a table with a BY REFERENCE distribution scheme that references a foreign key name that does not exist. Impact: TimesTen cannot create the table. User Action: Verify the foreign key name specified in the DISTRIBUTE BY REFERENCE clause, retry the operation. For more information, see Reference in Oracle TimesTen In-Memory Database Scaleout User's Guide.
1066	The Parent table for a distribute by reference table must be either hash distributed or itself distributed by reference.	Type of Message: Error Cause: You attempted to create a table with a BY REFERENCE distribution scheme that references a parent table with an unsupported distribution scheme for BY REFERENCE distribution. Impact: TimesTen cannot create the table. User Action: Ensure that the parent table in the DISTRIBUTE BY REFERENCE clause has one of the supported distribution schemes for BY REFERENCE distribution, and retry the operation. For more information, see Reference in Oracle TimesTen In-Memory Database Scaleout User's Guide.
1067	The Parent keys for a distribute by reference table with hash distributed parent must include the distribution keys of the parent.	Type of Message: Error Cause: You attempted to create a table with a BY REFERENCE distribution scheme that does not references to the BY HASH distribution key columns of the parent table. Impact: TimesTen cannot create the table. User Action: Ensure that you include in the DISTRIBUTE BY REFERENCE clause the key columns of the BY HASH distribution scheme of the parent table, and retry the operation. For more information, see Reference in Oracle TimesTen In-Memory Database Scaleout User's Guide.
1068	The child key columns of a foreign key constraint used to distribute by reference must be declared not null.	Type of Message: Error Cause: You attempted to create a table with a BY REFERENCE distribution scheme that uses child foreign key columns that are not specified as NOT NULL. Impact: TimesTen cannot create the table. User Action: Ensure that the child foreign key columns specified for the DISTRIBUTE BY REFERENCE clause are set as NOT NULL, and retry the operation. For more information, see Reference in Oracle TimesTen In-Memory Database Scaleout User's Guide.
1069	Table not empty. Alter table distribution is only permitted on empty tables.	Type of Message: Error Cause: You attempted to change the table distribution scheme on a table that is not empty. Impact: TimesTen cannot perform the operation. User Action: Ensure that the specified table is empty, and retry the operation. For more information, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
1070	Multiple foreign keys defined on the table. Please specify the key to distribute on.	Type of Message: Error Cause: You attempted to alter a table with two or more foreign key constraints to a BY REFERENCE distribution scheme without specifying which foreign key constraint to use for the BY REFERENCE distribution of the table. Impact: TimesTen cannot perform the operation User Action: Specify the foreign key constraint to use for the BY REFERENCE distribution scheme, and retry the operation. For more information, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
1071	Dropping hidden column column_name in TimesTen Scaleout is not allowed.	Type of Message: Error Cause: You attempted to drop the specified column in an ALTER TABLE statement. The dropping of hidden columns is not allowed in TimesTen Scaleout. Impact: TimesTen cannot perform the operation. User Action: None.
1072	Dropping a table's reference by distribution foreign key is not allowed.	Type of Message: Error Cause: You attempted to drop a foreign key that is being used for the BY REFERENCE distribution scheme of the table. Impact: TimesTen cannot drop the foreign key. User Action: Alter the table to a distribution scheme where the foreign key you wish to drop is not used as reference for distribution, and retry the operation.
1073	Failed to reclaim the operation: reclaim_log_info	Type of Message: Error Cause: A failure occurred during reclaim while processing this log record. Impact: TimesTen cannot perform the reclaim operation of the transaction. User Action: Try to reconnect after database recovery completes.
1074	Dropping internal object_type object_name in TimesTen Scaleout is not allowed.	Type of Message: Error Cause: You attempted to drop an internal object created for global index. Dropping internal objects is not allowed in gridshortname. Impact: TimesTen cannot perform the operation. User Action: Dropping the global index will remove this object.
1102	Stale table handle	Type of Message: Internal Error Cause: The internal version number of a table does not match the version in an associated table handle. Impact: TimesTen needs to reacquire the table handle and cannot access the table for the current operation. User Action: Contact TimesTen Customer Support.
1103	Error in converting sysdate to Timestamp.	Type of Message: Error Cause: You specified an Oracle database SYSDATE or TimesTen SYSDATE with an invalid TIMESTAMP or DATE value. Impact: TimesTen cannot convert the value to a TIMESTAMP value. User Action: Ensure that the Oracle database SYSDATE or TimesTen SYSDATE contains valid TIMESTAMP or DATE values. For more information on datetime data types, see Datetime data types in Oracle TimesTen In-Memory Database SQL Reference.
1104	Unable to obtain current date and time for SYSDATE.	Unable to get the time from the system specific call.
1105	Invalid column reference.	Type of Message: Error Cause: You specified an invalid column or column list. Impact: TimesTen cannot perform the operation. User Action: Specify a valid column or column list.
1106	Start num number must be between minValue number and maxValue number.	Type of Message: Error Cause: You specified a CREATE SEQUENCE statement that has a START WITH clause that is not within the defined MINVALUE and MAXVALUE range. Impact: TimesTen cannot perform the operation. User Action: Ensure that the START WITH clause is within the specified MINVALUE and MAXVALUE range. Alternatively, modify the MINVALUE and MAXVALUE values so that the START WITH value is within the range. For more information on the CREATE SEQUENCE statement, see CREATE SEQUENCE in Oracle TimesTen In-Memory Database SQL Reference.
1107	Error in converting sysdate to Date.	Type of Message: Error Cause: You specified an Oracle database SYSDATE or TimesTen SYSDATE with an invalid TIMESTAMP or DATE value. Impact: TimesTen cannot convert the value to a DATE value. User Action: Ensure that the Oracle database SYSDATE or TimesTen SYSDATE contains valid TIMESTAMP or DATE values. For more information on datetime data types, see Datetime data types in Oracle TimesTen In-Memory Database SQL Reference.
1108	Error in converting Oracle rowid to TimesTen rowid.	Type of Message: Error Cause: TimesTen encountered an invalid or improperly formatted Oracle database ROWID value in a SQL statement. Impact: TimesTen cannot convert the Oracle database ROWID to a TimesTen ROWID value. User Action: Specify a valid Oracle database ROWID value.
1109	Error converting char to ROWID	Type of Message: Error Cause: TimesTen encountered an invalid or improperly formatted CHAR value in a SQL statement. Impact: TimesTen cannot convert the CHAR value to a ROWID value. User Action: Specify a valid CHAR value. For more information on the CHAR data type, see CHAR in Oracle TimesTen In-Memory Database SQL Reference.
1110	FOR UPDATE with aggregate function is deprecated	Type of Message: Warning Cause: You specified a FOR UPDATE clause while selecting an aggregate function. The FOR UPDATE clause maintains a lock on an element (usually a row) until the end of the current transaction. Aggregate functions perform a specific operation over all rows in a group, causing the FOR UPDATE clause to not know which row to lock. Therefore, this operation is not recommended. Impact: None. User Action: Consider rewriting your SQL query. For more information on the FOR UPDATE clause and aggregate functions, see SELECT and Aggregate functions respectively in the Oracle TimesTen In-Memory Database SQL Reference.
1111	Error in converting rowid to char string.	Type of Message: Error Cause: Your application provided a buffer that is too small to store a ROWID string. Impact: TimesTen cannot convert the ROWID value to a CHAR string. User Action: Provide a buffer that can hold an 18 byte string.
1112	Error in converting char string to rowid.	Type of Message: Error Cause: You specified an invalid CHAR string or your application provided a buffer that is too small to store a ROWID string. Impact: TimesTen cannot convert the CHAR string to a ROWID value. User Action: Specify a valid CHAR string and provide a buffer that can hold an 18 byte string.
1119	arguments/bind variables not allowed for data definition operations	Type of Message: Error Cause: You specified a binding variable or argument in a DDL statement. Impact: TimesTen cannot perform the operation. Binding variables or arguments are not allowed for any DDL statements, such as CREATE VIEW, CREATE TABLE. User Action: Consider using a CREATE TABLE statement with an INSERT INTO ... SelectQuery statement instead of a CREATE TABLE ... AS SelectQuery ... :BindingVariable statement. For more information on the CREATE TABLE statement, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference. For more information on the INSERT...SELECT statement, see INSERT...SELECT in the Oracle TimesTen In-Memory Database SQL Reference. For more information on CREATE VIEW, see CREATE VIEW in the Oracle TimesTen In-Memory Database SQL Reference.
1120	SQL command does not exist.	Type of Message: Error Cause: You specified a SQL unique identifier (sqlCmdID) that cannot be found in the SQL command query cache. Impact: TimesTen cannot perform the operation. User Action: Ensure that you specify a correct sqlCmdID value when you call a TimesTen built-in procedure that expects a sqlCmdID argument. Call the ttSQLCmdCacheInfo built-in procedure to view the TimesTen SQL command cache and the sqlCmdID of recent SQL statements. For more information on the ttSQLCmdCacheInfo built-in procedure, see ttSQLCmdCacheInfo in Oracle TimesTen In-Memory Database Reference. For more information on TimesTen built-in procedures, see Built-In Procedures in the Oracle TimesTen In-Memory Database Reference.
1121	Parser Stack Overflow in SQL statement statement	Type of Message: Error Cause: The TimesTen parser exhausted its stack while parsing the SQL statement. This is usually due to too many nested or repeating elements in the SQL statement. Impact: TimesTen cannot perform the SQL operation. User Action: Contact TimesTen Customer Support.
1122	Feature is disabled in the current release.	Type of Message: Error Cause: This feature has been temporarily disabled in the current version of TimesTen. Impact: TimesTen cannot perform the operation. User Action: Contact TimesTen Customer Support for more information.
1123	Invalid value specified for shmtype connection attirbute.	Type of Message: Error Cause: You specified an invalid value for the ShmType connection attribute. Impact: TimesTen could not create the database or the connection failed. User Action: Specify an appropiate value for the ShmType connection attribute: 0 or 1.
1200	Invalid transaction ID was specified	Type of Message: Error Cause: You specified an incorrect transaction ID (xactID) for the ttXactIdRollback utility API. Impact: TimesTen cannot roll back the transaction. User Action: Ensure that when you call the ttXactIdRollback utility API you specify a correct xactID argument. For more information on the ttXactIdRollback utility API, see ttXactIdRollback in Oracle TimesTen In-Memory Database C Developer's Guide.
1203	This transaction needs rollback because it was marked for rollback by an external process	Type of Message: Error Cause: An external process, like the ttXactAdmin -xactIdRollback or ttAdmin -ramUnload command, requested a rollback for this transaction. Impact: The transaction no longer exists, cannot do any further work, and cannot commit. The resources associated with the transaction have been reclaimed. User Action: You must issue a rollback from your connection to complete the rollback requested by the external process. Then, retry the transaction.
1205	The specified transaction did not match the criteria to commit the transaction externally. Reason	Type of Message: Error Cause: You attempted to use the ttXactAdmin -xactIdCommit command on a transaction that cannot be externally committed. The accompanying message provides further details on the cause of the error. Impact: TimesTen did not commit the transaction. User Action: Verify that the specified transaction supports being externally committed. Otherwise, roll back the transaction. For more information on how to externally commit or roll back a transaction, see ttXactAdmin in Oracle TimesTen In-Memory Database Reference.
1206	The specified transaction did not match the criteria to rollback the transaction externally: reason	Type of Message: Error Cause: You attempted to use the ttXactAdmin -xactIdRollback command on a transaction that cannot be externally rolled back. The accompanying message provides further details on the cause of the error. Impact: TimesTen did not roll back the transaction, and freed no resources. User Action: Verify that the specified transaction supports being externally rolled back. Otherwise, roll back the transaction from the application that initiated it or unload the database from memory. For more information on the ttXactAdmin -xactIdRollback command, see ttXactAdmin in Oracle TimesTen In-Memory Database Reference.
1207	This distributed transaction [transaction_info] needs to roll back because it failed to complete: reason	Type of Message: Error Cause: An element of the grid may be down. Sending a message to an element failed. Impact: The transaction is inconsistent and may be holding resources. User Action: Issue a rollback from your connection to free any remaining resources. Then, retry the operation.
1208	Database connection terminated.	Type of Message: Warning Cause: An external process, like the ttAdmin -disconnect or ttGridAdmin dbDisconnect command, requested that this database connection be disconnected. Impact: The connection no longer exists and cannot do any further work. The resources associated with the connection have been reclaimed. User Action: Reconnect to the database. Consider that there may be administrative operations underway that need to complete before you are able to reconnect.
1209	No outstanding transaction found with specified id	Type of Message: Error Cause: You specified the transaction ID of a transaction that does not exist. Impact: TimesTen cannot find the transaction. User Action: Ensure that when you call the utility API you specify a valid xactID argument.
1740	Missing double quote in identifier identifier_name	You must delimit an identifier name with double quotes. Add the double quote and try the operation again.
1742	Comment not terminated properly message	Comments must be terminated with the character specified in the message. Add the specified character and try the operation again.
1756	Quoted string not properly terminated message	The quoted string must be terminated with the character specified in the message. Add the specified character and try the operation again.
1801	Cannot create index on expression with datatype LOB	Type of Message: Error Cause: You attempted to create an index on a LOB column. Impact: TimesTen cannot perform the operation. User Action: Change the column data type or do not create the index on the LOB column.
1802	Column of datatype LOB cannot be unique or a primary key	Type of Message: Error Cause: You attempted to create a PRIMARY KEY or UNIQUE constraint on a column of data type LOB. Impact: TimesTen cannot perform the operation. User Action: Change the column data type or remove the constraint. Then retry the operation.
1803	Specified trim length is greater than current LOB value's length	The input length for which to trim the LOB value to is greater than the current length of the LOB value. You may not need to trim the LOB value because it is already smaller than the specified trim length. If trimming the LOB value is required, use a smaller trim length.
1804	Invalid character set form	An invalid character set form was passed into an OCI LOB function. For example, SQLCS_CHAR could have been specified for a CLOB or SQLCS_IMPLICIT could have been specified for a NCLOB. Specify a valid character set form.
1806	Invalid LOB locator specified	The LOB locator in the LOB API call is either not properly allocated or is not initialized. Initialize the LOB locator.
1807	LOB already opened in the same transaction	You attempted to open a LOB that is already opened in the transaction. Close the LOB before attempting to re-open it.
1808	Cannot update a LOB opened in read-only mode	You attempted to write to or update a LOB opened in read-only mode. Close the LOB and re-open it in read-write mode before attempting to write to or update the LOB.
1809	LOB type mismatch	When copying or appending LOB locators, both source and destination LOB locators should be of the same type. Pass the same type of LOB locators for copying or appending.
1812	Operation would exceed maximum size allowed (number bytes) for a data_type value	You attempted an operation that would result in writing too much data to the LOB value. Maximum size for the CLOB and the NCLOB data types is 4 MB and maximum size for the BLOB data type is 16 MB. Either start writing at a smaller LOB offset or write less data to the LOB value.
1813	Less data provided for writing than indicated	When issuing the OCILobWrite call, ensure that the length of the data buffer is large enough to accommodate the data to be written.
1814	Source offset is beyond the end of the source LOB	The source offset for the LOB copy or convert operation is beyond the end of the source LOB. Check the length of the LOB and then adjust the source offset.
1818	Warning: Open LOBs exist at transaction commit time	Type of Message: Warning Cause: You attempted to commit a transaction with open LOBs. Impact: TimesTen closes the LOBs and commits the transaction. User Action: Make sure your application closes open LOBs before a commit. For more information on closing LOBs, see CLOSE Procedures in Oracle TimesTen In-Memory Database PL/SQL Packages Reference.
1819	Inconsistent datatypes: expected data_type got data_type	You attempted an operation (such as an INSERT) that was expecting a data type (such as a CLOB) and you provided an invalid data type (such as a BLOB). Check the supported data types and conversions for the operation.
1820	Cannot create materialized view that includes LOB columns	You attempted to create a materialized view on a table with a column of type CLOB, NCLOB, or BLOB. Recreate the materialized view without including the LOB column.
1821	Offset or offset+amount does not land on character boundary	You provided an offset that would cause the operation to override the character boundary. This error occurs with NCLOB data types stored in a single byte or multibyte database or CLOB data types stored in a multibyte database.
1822	Cannot perform operation operation on an unopened file or LOB	Type of Message: Error Cause: The file or LOB is not open for the required operation to be performed. Impact: The indicated operation cannot be performed. User Action: Precede the current operation with a successful open operation on the file or LOB.
1824	Row containing the LOB value is not locked	The row containing the LOB value must be locked before updating the LOB value. Lock the row containing the LOB value before updating the LOB value.
1825	CLOB or NCLOB in multibyte character set not supported	A CLOB or NCLOB in a fixed-width or varying-width multibyte character set was passed to a SQL character function which does not support multibyte LOB data.
1826	Invalid parameter value in OCI LOB function	You specified an invalid parameter value in the OCI LOB function. Check each parameter in the OCI LOB function call to ensure that they are correct.
1829	CLOBs are not supported when database character set is TIMESTEN8	Your database character set is TIMESTEN8. CLOB and NCLOB functionality is not supported in this character set.
1830	BLOB/CLOBs are not supported in the SELECT lists of set operators such as UNION, INTERSECT, and MINUS	You attempted to specify a LOB data type in the SELECT list of a set operator such as UNION, INTERSECT, or MINUS. Do not use the LOB data type with these set operators.
1831	Cannot create global index on LOB columns	Type of Message: Error Cause: You attempted to create a global index on a column of type CLOB, NCLOB, or BLOB. Impact: TimesTen cannot perform the operation. User Action: Recreate the global index without including the LOB column.
1851	Operation on a passthrough LOB is not supported	Operations such as ConvertToClob and ConvertToBlob are not supported.

Errors 2000-2999

Error number	Error or warning message	Details
2042	Column defined with interval data type is not supported	Type of Message: Error Cause: You attempted to define a column with the interval data type. This is not a supported data type. Impact: TimesTen did not perform the operation. User Action: Recreate the table using a supported data type for the column definition. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2043	Binary data exceeds column width for column column_name - value will be truncated	Type of Message: Warning Cause: You attempted to insert a string into a binary column and the string exceeds the maximum length defined for the column. Impact: TimesTen performed the insert operation, but truncated the value. User Action: If you do not wish the value to be truncated, increase the length of the column definition for the table. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2044	Binary data exceeds column width value	Type of Message: Error Cause: The length of a value you attempted to insert or update into a column exceeds the declared length of the binary column. Impact: TimesTen did not perform the operation. User Action: Redefine the column length or insert/update a value that does not exceed the length of the column. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2206	Table table_name not found	Type of Message: Error Cause: The specified table does not exist. Impact: TimesTen cannot perform any operation with the specified table name. User Action: Verify the table name and retry the operation.
2207	Table table_name already exists	Type of Message: Error Cause: You attempted to create a table that already exists. Impact: TimesTen did not create the table. User Action: Specify a different name for the table. For more information, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2208	Column column_name does not exist in table	Type of Message: Error Cause: You referenced a column that does not exist in the table. Impact: TimesTen did not perform the operation. User Action: Try the operation again, making sure to specify a column name that exists in the table.
2209	Column column_name specified more than once	Type of Message: Error Cause: You referenced the same column more than once in the SQL statement. Impact: TimesTen did not perform the operation. User Action: Retry the operation, ensuring that you only specify the column name once.
2210	Column reference of column_name is ambiguous	Type of Message: Error Cause: You attempted to reference a column without qualifying the table name. The column reference can be associated with more than one table. Impact: TimesTen did not perform the operation. User Action: Fully qualify the name by specifying the table name and column.
2211	Referenced column column_name not found	Type of Message: Error Cause: You attempted to reference a column in a table that does not exist. Impact: TimesTen did not perform the operation. User Action: Specify the correct name for the column.
2212	Named index not found in table	Type of Message: Error Cause: You attempted to drop a non-existent index from a table. Impact: TimesTen did not perform the operation. User Action: Examine the indexes for the table and drop an index that exists. For more information, see DROP INDEX in Oracle TimesTen In-Memory Database SQL Reference.
2213	Named index already exists on specified table	Type of Message: Error Cause: You attempted to create an index on a table and the index name for that table already exists. Impact: TimesTen did not create the index. User Action: Specify an index name that does not exist for the table. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference.
2214	Column cannot be named ROWID	Type of Message: Error Cause: You specified the ROWID reserved word for your column name. Impact: TimesTen did not perform the operation. User Action: Do not specify ROWID as the column name for your column.
2215	Attempt to drop a primary key index	Type of Message: Error Cause: You attempted to drop a primary key index. Impact: TimesTen did not perform the DROP operation. User Action: Do not attempt to drop a primary key.
2216	Index key length is long, lookup based on the indexed key may be slow.	Type of Message: Warning Cause: You created an index on a column whose length is greater then 4MB. Impact: TimesTen created the index, but issued a warning that lookups based on this index may be slow. User Action: Re-examine the columns for your index. If an index is needed for this column, no action is necessary. Just note that index lookups may be slow. For more information, see Understanding Indexes in Oracle TimesTen In-Memory Database Operations Guide.
2221	Duplicate column name found in insert list	Type of Message: Error Cause: You specified a duplicate column name in the column list of an INSERT statement. Impact: TimesTen did not perform the INSERT. User Action: Retry the INSERT operation without a duplicate column name. For more information, see INSERT in Oracle TimesTen In-Memory Database SQL Reference.
2222	Index name is not unique. More than one table has an index with this name.	Type of Message: Error Cause: You attempted to drop an index while just specifying the index name. The specified index name is assigned to an index in more than one table. Impact: TimesTen did not drop the index. User Action: Retry the DROP INDEX statement while specifying the table where the desired index is defined. For more information on the DROP INDEX statement, see DROP INDEX in Oracle TimesTen In-Memory Database SQL Reference.
2223	Named index does not exist	Type of Message: Error Cause: You attempted to reference an index that does not exist in the database. Impact: The operation failed. User Action: Specify an index that exists. To verify existing indexes, run the indexes command in the ttIsql utility. For more information, see ttIsql in Oracle TimesTen In-Memory Database Reference.
2230	View view_name not valid input to ttSize	Type of Message: Error Cause: You attempted to run or call the ttSize utility or built-in procedure and specified a regular view. Only materialized views are supported with the ttSize utility or built-in procedure. Impact: TimesTen failed to run or call the ttSize utility or built-in procedure. User Action: None.
2231	New index index_name would be identical to existing index index_name	Type of Message: Error Cause: You attempted to create a redundant index. There is a defined index on the table and you specified a new index name for the same columns. Impact: TimesTen did not create the index. User Action: Review the indexes on the table to decide if a new index is necessary. If so, make sure the index is not redundant. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference.
2232	New index index_name is identical to existing index index_name; consider dropping index index_name	Type of Message: Warning Cause: You attempted to define a new index on a column that is identical to an existing index. Impact: TimesTen created the index, but issued a warning that you should consider dropping one of the indexes. User Action: Review the index definitions and consider dropping one of the indexes. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference.
2233	Key columns of new index index_name are a prefix of the columns of existing index index_name; consider dropping index index_name	Type of Message: Warning Cause: You created an index that uses columns that are a prefix to the columns specified in an existing index. Impact: TimesTen created the index, but issued a warning that you should consider dropping one of the indexes. User Action: Review the index definitions and consider dropping one of the indexes. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference.
2234	Key columns of existing index index_name are a prefix of the columns of new index index_name; consider dropping index index_name	Type of Message: Warning Cause: You attempted to define an index in which the key columns of an existing index are a prefix of the columns of the new index. Impact: TimesTen created the index, but issued a warning that you should consider dropping one of the indexes. User Action: Run the ttISql indexes command to review the indexes and consider dropping one of the indexes. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference or ttIsql in the Oracle TimesTen In-Memory Database Reference.
2235	Table can have only one primary key	Type of Message: Error Cause: You attempted to specify more than one primary key for the table. Impact: TimesTen did not perform the operation. User Action: Specify one primary key for the table.
2236	Nullable column cannot be part of a primary key	Type of Message: Error Cause: Primary key columns must be defined as NOT NULL. Impact: TimesTen did not perform the operation. User Action: Specify NOT NULL for all primary key columns.
2237	Adding a primary key constraint on a replicated table is not allowed while the replication agent for database database_name is running. Please stop the replication agent to perform this operation.	Type of Message: Error Cause: You attempted to add a primary key on a replicated table while the replication agent was running. Impact: TimesTen did not add the primary key. User Action: Stop the replication agent before making changes to the table. For more information, see CREATE REPLICATION in Oracle TimesTen In-Memory Database SQL Reference.
2238	System table cannot be altered	Type of Message: Error Cause: You attempted to alter a system table or system view. Impact: TimesTen did not perform the operation. User Action: Do not attempt to alter a system table or system view. These are used to store and retrieve metadata. For more information, see Oracle TimesTen In-Memory Database System Tables and Views Reference.
2239	New unique index index_name has the same key columns as existing non-unique index index_name; consider dropping index index_name	Type of Message: Warning Cause: You attempted to create a unique index with the same columns as a previously created non-unique index. Impact: TimesTen created the new unique index but issued a warning to consider dropping the new index. User Action: Consider dropping the new unique index. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference.
2240	New non-unique index index_name has the same key columns as existing unique index index_name; consider dropping index index_name	Type of Message: Warning Cause: You attempted to create a non-unique index with the same columns as a previously created unique index. Impact: TimesTen created the new non-unique index, but issued a warning to consider dropping the new index. User Action: Consider dropping the new non-unique index. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference.
2241	Primary or Unique key cannot be created, constraint already exists for table table_name on column column_name	Type of Message: Error Cause: You attempted to specify a unique or primary key on a table that already has the other such key on that column. Impact: TimesTen did not perform the operation. User Action: Check the constraints defined on the columns of the table, ensuring that the column you want to add a unique constraint to does not have one already defined. Run the ttIsql command, indexes, to view the constraints on the table. For more information, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference or ttIsql in the Oracle TimesTen In-Memory Database Reference.
2242	Invalid value for MAXVALUES in 'COMPRESS BY DICTIONARY' clause	Type of Message: Error Cause: You entered an incorrect value for the MAXVALUES clause in a column-based compression definition. Impact: TimesTen did not perform the operation. User Action: Specify the COMPRESS BY DICTIONARY clause again supplying a correct value for MAXVALUES. Valid values are between 1 and 232-1. For more information, see Store Data Efficiently with Column-Based Compression of Tables in Oracle TimesTen In-Memory Database Operations Guide.
2243	Invalid use of compression: error_details	Type of Message: Error Cause: You attempted to compress a unique or primary key column, or create a unique index from a compressed column or a set of columns that are all in the same compression group. Impact: TimesTen cannot perform the operation. User Action: Ensure that you do not specify unique or primary key columns for compression or that you do not define a unique index from a compressed column or a set of columns that are all from the same compression group in your SQL statement. For more information, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2244	Cannot drop compressed column column_name without also dropping column column_name which is in same compression group.	Type of Message: Error Cause: You did not drop all columns in a multiple column compression group. Impact: TimesTen did not drop the columns. User Action: Perform the ALTER TABLE statement again making sure to drop all of the columns in the multiple column compression group. For more information, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2245	Maximum values for compression group containing column column_name already present	Type of Message: Error Cause: The space allocated for the dictionary table for your compressed column has been exhausted. Impact: Inserts or updates in the base table for values that do not have a corresponding value in the dictionary table will fail. User Action: Investigate the maximum number of distinct values you require in your compressed column group and consider changing the MAXVALUES clause. For more information on the maximum supported number of values for a compression group, see Store Data Efficiently with Column-Based Compression of Tables in Oracle TimesTen In-Memory Database Operations Guide.
2246	Cannot change compression clause for already defined column column_name	Type of Message: Error Cause: You attempted to alter a table adding a new column and specified a previously created column in the compression clause. You cannot use the ALTER TABLE statement to add a column and then specify the compression clause on a previously defined column. Impact: TimesTen did not perform the alter statement. User Action: Do not specify a previously defined column in the compression clause of the ALTER TABLE statement. You may also consider dropping the column. For more information, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2247	Total table size calculation overflowed unsigned 32-bit integer; table too large to exist in a 32-bit TimesTen installation	Type of Message: Error Cause: The size projection for the specified table overflowed an unsigned 32-bit integer. This table cannot exist on a 32-bit TimesTen installation, but may be able to exist on a 64-bit TimesTen installation. Impact: TimesTen did not perform the operation. User Action: Consider reducing the size of the table.
2248	Total table size calculation overflowed unsigned 64-bit integer; table too large to exist in a 64-bit TimesTen installation	Type of Message: Error Cause: The size projection for the specified table overflowed an unsigned 64-bit integer. Impact: TimesTen cannot support the table size. User Action: Review the size of your table and decide how to reduce the size of the table.
2249	Duplicate column name found in update set list	Type of Message: Error Cause: You attempted to update a table and specified the same column more than once in the column list of the SET clause. Impact: TimesTen did not update the table. User Action: Reissue the UPDATE statement, but do not specify the same column more than once in the column list of the SET clause. For more information, see UPDATE in Oracle TimesTen In-Memory Database SQL Reference.
2250	New column name column_name duplicates existing column name	Type of Message: Error Cause: You attempted to ALTER a table by adding a column with the same name as an existing column. Impact: TimesTen did not alter the table to add the column. User Action: Specify a column name that does not already exist in the table. For more information, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2251	Compressed column group exceeds maximum allowable number of rows with equal value	Type of Message: Error Cause: The limit on occurrences of a value for a compressed column (group) has been exceeded. Impact: Inserts into the base table that have this column value will fail. User Action: If the number of occurrences of a column group value is expected to exceed the limit, then you cannot use compression for that column group. For more information on the limit of a value for a compressed column, see Store Data Efficiently with Column-Based Compression of Tables in Oracle TimesTen In-Memory Database Operations Guide.
2252	Different number of pages specified for hash index index_name in table and index definition. Index created with pages = pages	Type of Message: Warning Cause: You attempted to create primary key hash index with conflicting pages value in table and index definition. Impact: TimesTen created the index, but issued a warning that pages value in table definition is used for that index. User Action: Review the table and index definitions and recreate the table with pages value used in index definition if you want that value to be used for primary key hash index. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference.
2253	Distribution key for global index cannot be same as that of the table or other global index. Consider creating a local index.	Type of Message: Error Cause: You attempted to create a global index with same distribution key as the table or other global index. Local index is better optimized for this case. Impact: TimesTen did not perform the operation User Action: Review the index definition and create a local index if distribution key for global index is going to be same as that of the table or other global index on that table.
2254	New global index index_name has the same key columns as existing global index index_name; consider creating a single global index with include columns from both the indexes.	Type of Message: Warning Cause: You attempted to create a global index with the same key columns as a previously created global index. Impact: TimesTen created the new global index but issued a warning to consider dropping the new index. User Action: Consider dropping the new global index. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference.
2255	New local index index_name has the same key columns as existing global index index_name; consider dropping local index index_name.	Type of Message: Warning Cause: You attempted to create a local index with the same key columns as a previously created global index. Impact: TimesTen created the new local index but issued a warning to consider dropping the new index. User Action: Consider dropping the new local index. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference.
2256	New global index index_name has the same key columns as existing local index index_name; consider dropping local index index_name.	Type of Message: Warning Cause: You attempted to create a global index with the same key columns as a previously created local index. Impact: TimesTen created the new global index but issued a warning to consider dropping the previously created local index. User Action: Consider dropping the previously created local index. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference.
2286	Attempt to define constraint on column that does not exist	Type of Message: Error Cause: You attempted to create a primary key or unique constraint on a column that does not exist. Impact: TimesTen did not perform the operation. User Action: Make sure the column used for the primary key or unique constraint exists.
2294	UNIQUE/PRIMARY KEY column must specify NOT NULL	Type of Message: Error Cause: You specified a nullable primary key or unique constraint. Impact: TimesTen did not perform the DDL or DML operation. User Action: Make sure primary key or unique constraint columns are not null.
2295	Duplicate columns in primary key specification	Type of Message: Error Cause: You specified a column more than once in the primary key or unique hash clause of a create table statement. Impact: TimesTen did not create the table. User Action: Retry the create table operation making sure to not define the same column more than once in the primary key or unique hash clause.
2296	Duplicate columns in hash distribution key specification	Type of Message: Error Cause: You attempted to create a table with a BY HASH distribution scheme and specified a column more than once in the distribution key columns list. Impact: TimesTen cannot perform the operation. User Action: Ensure that your SQL statement only specifies once any of the columns included in the distribution key columns list of the BY HASH distribution scheme, and retry the operation. For more information, see Hash in Oracle TimesTen In-Memory Database Scaleout User's Guide.
2376	Duplicate entries in FROM clause	Type of Message: Error Cause: You specified the same table name more than once in the FROM clause of a SELECT statement. Impact: TimesTen did not perform the SELECT operation. User Action: Perform the SELECT statement again specifying the table name once. For more information, see SELECT in Oracle TimesTen In-Memory Database SQL Reference.
2400	Number of columns (number) exceeds the maximum (number)	Type of Message: Error Cause: You attempted to CREATE or ALTER a table with more than 1000 columns. Impact: TimesTen did not create the table. User Action: Make sure the number of columns does not exceed the maximum limit of 1000 for the CREATE or ALTER table statement.
2401	Number of columns in compression group (number) exceeds the maximum (number)	Type of Message: Error Cause: You specified too many columns for a compression group in the COMPRESS clause of a CREATE TABLE or ALTER TABLE statement. Impact: The CREATE TABLE or ALTER TABLE statement failed. TimesTen did not create or alter a table. User Action: Reduce the number of columns in each compression column group to be less than the maximum allowed per compression group. For more information, see Store Data Efficiently with Column-Based Compression of Tables in Oracle TimesTen In-Memory Database Operations Guide or CREATE TABLE or ALTER TABLE in the Oracle TimesTen In-Memory Database SQL Reference.
2404	Number of primary key columns exceeds the maximum	Type of Message: Error Cause: You attempted to create a primary key with more than 32 columns. Impact: TimesTen did not perform the operation. User Action: Redefine the primary key definition using 32 columns or fewer. For more information, see System Limits in Oracle TimesTen In-Memory Database Reference.
2405	Number of index key columns (number) exceeds the maximum (number)	Type of Message: Error Cause: You attempted to create an index with more than 32 columns. Impact: TimesTen did not create the index. User Action: Recreate the index specifying 32 columns or fewer. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference or System Limits in the Oracle TimesTen In-Memory Database Reference.
2406	Number of include columns (number) exceeds the maximum (number)	Type of Message: Error Cause: You attempted to create a gloabl index with more than 32 included columns. Impact: TimesTen did not create the index. User Action: Recreate the index specifying 32 include columns or fewer. For more information, see CREATE INDEX in Oracle TimesTen In-Memory Database SQL Reference or System Limits in the Oracle TimesTen In-Memory Database Reference.
2407	Length of column column_name (number) exceeds maximum (number)	Type of Message: Error Cause: You attempted to define a CHAR or BINARY column whose length exceeds 8,300 or a VARCHAR2 or VARBINARY column whose length exceeds its maximum of 4,194,304. Impact: TimesTen did not perform the operation. User Action: Specify the correct length for your column making sure not to exceed the maximum allowable length. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2414	Length of column column_name (number) below minimum (number)	Type of Message: Error Cause: You attempted to define a CHAR, BINARY, VARCHAR2 or VARBINARY column whose length is less than 1. Impact: TimesTen did not perform the operation. User Action: Specify the correct length for your column making sure to specify a length greater than 0. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2416	Number of hash key columns exceeds the maximum	Type of Message: Error Cause: You attempted to define more than 32 primary key columns for a table. The maximum number of primary key columns for a table is 32. Impact: TimesTen did not create the table. User Action: Specify 32 or less primary key columns for the table. For more information, see System Limits in Oracle TimesTen In-Memory Database Reference.
2417	Cannot add not null column column_name unless it has a default value specified	Type of Message: Error Cause: If you use the ALTER TABLE statement to add a NOT NULL column, you must specify a default value. Impact: You cannot use the ALTER TABLE statement to add a NOT NULL column without specifying a default value. User Action: When you use the ALTER TABLE ADD statement to add a NOT NULL column, ensure that you specify a default value for the NOT NULL column. For more information on ALTER TABLE, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2418	Cannot add not null column column_name to replicated table owner_name.table_name	Type of Message: Error Cause: You attempted to use the ALTER TABLE statement to add a NOT NULL column to a table that is part of a replication scheme. Impact: You cannot use the ALTER TABLE statement to add a NOT NULL column to a table that is replicated. User Action: Drop the table from the replication scheme. For more information, see Dropping a Table or Sequence from a Classic Replication Scheme in Oracle TimesTen In-Memory Database Replication Guide. Add the NOT NULL column to the table with ALTER TABLE. For more information see ALTER TABLE in the Oracle TimesTen In-Memory Database SQL Reference. Add the table back into the replication scheme. For more information, see Adding a Table or Sequence to an Existing Classic Replication Scheme in the Oracle TimesTen In-Memory Database Replication Guide.
2419	All columns in a primary key constraint must be in the initial partition; column column_name was added by ALTER TABLE	Type of Message: Error Cause: When you use the ALTER TABLE statement to add a column, the newly added column is located in a secondary partition. You cannot use the ALTER TABLE statement to add a primary key constraint on a column that is in the secondary partition. Impact: TimesTen did not create a primary key on the specified column because it is in a secondary partition. User Action: Use ttMigrate -r -relaxedUpgrade to condense the secondary partition into a single partition. Once you condense the partitions, you can then ALTER the table and add a primary key constraint on the column. For more information on partitions and using ALTER TABLE, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2420	Number of values specified in INSERT statement exceeds number of columns in table	Type of Message: Error Cause: You attempted an INSERT statement in which you specified more values in the VALUES clause than the number of columns in the table. Impact: TimesTen did not perform the INSERT operation. User Action: Perform the INSERT operation again ensuring the number of values in the VALUES clause is not greater than the maximum number of columns in the table. For more information, see INSERT in Oracle TimesTen In-Memory Database SQL Reference.
2421	Column number exceeds length of select list	Type of Message: Error Cause: You attempted to reference one ore more columns by position in the ORDER BY clause and the number of columns exceeds the number of columns in the SELECT list. Impact: TimesTen did not perform the SELECT operation. User Action: Re-issue the SELECT statement making sure the number of columns in the ORDER BY clause is less than or equal to the number of columns in the SELECT list. For more information, see SELECT in Oracle TimesTen In-Memory Database SQL Reference.
2430	Precision of decimal or numeric type is out of range	Type of Message: Error Cause: You specified an out of range value for the precision of a DECIMAL or NUMERIC data type. The accepted values are between 1 and 40. Impact: TimesTen did not perform the operation. User Action: Retry the operation, making sure to specify a valid precision for the DECIMAL or NUMERIC data type. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2431	Scale of decimal or numeric type is out of range	Type of Message: Error Cause: You specified an out of range value for the scale of the DECIMAL or NUMERIC data type. The accepted value must be between 0 and 40. Impact: TimesTen did not perform the operation. User Action: Retry the operation, making sure to specify a valid scale for the DECIMAL or NUMERIC data type. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2432	Scale of decimal or numeric type must not be larger than precision	Type of Message: Error Cause: You specified a scale value that is greater than the precision value for the DECIMAL or NUMERIC data type. Impact: TimesTen did not perform the operation. User Action: Retry the operation, making sure to specify the scale value does not exceed the precision value for the DECIMAL or NUMERIC data type. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2433	Invalid fixed-point number provided	Type of Message: Error Cause: You specified an invalid value for a fixed-point numeric data type. You must specify a fixed-point value in this order: a sign, digits (0-9), a decimal point and digits (0-9). The sign and decimal point are optional. Impact: TimesTen did not perform the operation. User Action: Retry the operation, making sure to specify a correct fixed-point value for the numeric data type. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2434	Decimal overflow	Type of Message: Error Cause: You specified too many digits to the left of the decimal point based on the defined precision and scale. Impact: TimesTen did not perform the operation. User Action: Retry the operation, making sure to specify the correct number of digits to the left of the decimal point based on the precision and scale previously defined. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2435	Decimal value exceeds column scale - value will be truncated	Type of Message: Warning Cause: You specified too many digits to the right of the decimal point based on the previously defined scale for the data type. Impact: This is a warning. TimesTen performed the operation, but truncated the value. User Action: Retry the operation, making sure to specify the correct number of digits to the right of the decimal point for the previously defined column. Check the defined scale. Run the ttIsql describe command to display the column data types. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2436	Decimal divide by zero	Type of Message: Error Cause: You attempted to divide a decimal value by zero. Impact: TimesTen did not perform the operation. User Action: Retry the operation, making sure that the operation does not divide the decimal value by 0. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2437	Decimal product cannot be represented; scale number is greater than maximum of number	Type of Message: Error Cause: You attempted an operation involving the multiplication of decimal values. The product of this operation did not preserve the scale of the data type. Impact: TimesTen did not perform the operation because precision might be lost. User Action: Perform the multiplication operation again, making sure the product is not greater than the scale value. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2438	Precision of decimal or numeric value is out of range	Type of Message: Error Cause: You specified an out of range value for the precision of a decimal or numeric data type. The value must be between 1 and 40. Impact: TimesTen did not perform the operation. User Action: Specify a correct precision for the data type. Run the ttIsql describe command to check the defined precision for the column. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2439	Scale of decimal or numeric value is out of range	Type of Message: Error Cause: You specified an incorrect scale value for the decimal or numeric data type. The scale must be between 0 and 40. Impact: TimesTen did not perform the operation. User Action: Retry the operation, making sure to specify a valid scale value. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2440	Value outside of range supported by decimal or floating point type	Type of Message: Error Cause: You specified an out of range value for the decimal or floating-point data type. Impact: TimesTen did not perform the operation. User Action: Retry the operation, making sure to specify a valid value for the data type. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2599	Overflow: Value too big for TimestampDiff's return type	Type of Message: Error Cause: You attempted to invoke the TIMESTAMPDIFF function and provided timestamps in which the difference between the two resulted in a return interval value that is greater than the maximum acceptable value of the TT_BIGINT data type. Note: The return data type for the TIMESTAMPDIFF function is TT_BIGINT. Impact: TimesTen did not invoke the function. User Action: Check the value provided for the interval parameter to the function. This value could be too small for the timestamps provided. For more information, see TIMESTAMPDIFF in Oracle TimesTen In-Memory Database SQL Reference.
2600	Integer overflow	Type of Message: Error Cause: The operation resulted in a value greater than the maximum supported value for an integer data type. Impact: TimesTen did not perform the operation. User Action: Ensure that the result of your operation is not greater than the maximum supported value for an integer data type.
2601	Integer value required	Type of Message: Error Cause: The operation expected a integer value for the parameter. Impact: Integer value required User Action: Use integer value for the parameter
2602	Integer divide by zero	Type of Message: Error Cause: You specified an operation in which an integer was divided by zero. Impact: TimesTen did not perform the operation. User Action: Retry the operation again making sure not to divide the integer by 0.
2603	Extended precision overflow	Type of Message: Error Cause: The specified or calculated value is greater than the upper bound for the signed floating-point data type. Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure the value is not greater than the upper bound of the signed floating-point data type.
2604	Extended precision divide by zero	Type of Message: Error Cause: You attempted a divide by 0 operation. Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure not to divide by 0.
2605	Extended precision underflow	Type of Message: Error Cause: The specified or calculated value is less than the lower bound for the signed floating-point data type. Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure the value is not less than the lower bound of the signed floating-point data type.
2606	Error converting from character string 'string' to date	Type of Message: Error Cause: TimesTen encountered a conversion error when converting a CHAR or VARCHAR2 data type to the DATE data type format. Impact: TimesTen did not perform the conversion. User Action: Check the conversion rules for converting a character string to a DATE data type. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2607	Error converting from character string 'string' to time	Type of Message: Error Cause: TimesTen encountered a conversion error when converting a CHAR or VARCHAR2 data type to the TIME data type format. Impact: TimesTen did not perform the operation. User Action: Check the conversion rules for converting a CHAR or VARCHAR2 data type to a TIME data type. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2608	Error converting from character string 'string' to timestamp	Type of Message: Error Cause: TimesTen encountered a conversion error when converting a CHAR or VARCHAR2 data type to the TIMESTAMP data type format. Impact: TimesTen did not perform the operation. User Action: Check the conversion rules for converting a CHAR or VARCHAR2 data type to a TIMESTAMP data type. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2610	Operand data type 'data_type' invalid for operator 'operator' in expr (expression)	Type of Message: Error Cause: You attempted to specify an invalid operand data type for an operator in an expression. Impact: TimesTen did not execute the expression. User Action: Check the syntax and semantic rules for the operands, operator, and expression. For more information, see Expressions in Oracle TimesTen In-Memory Database SQL Reference.
2611	Error converting date to character string	Type of Message: Error Cause: You specified an invalid date format for the character string conversion. Impact: TimesTen did not perform the conversion. User Action: Retry the operation making sure to specify a correct date format.
2612	Error converting time to character string	Type of Message: Error Cause: You specified an invalid time format for the character string conversion. Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure to specify a correct time format.
2613	Error converting timestamp to character string	Type of Message: Error Cause: You specified an invalid timestamp format for the character string conversion. Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure to specify a correct timestamp format.
2614	Value outside of range supported by integral type	Type of Message: Error Cause: You attempted a conversion that resulted in an overflow. Impact: TimesTen did not perform the operation. User Action: Check the allowable values for the data types in question. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2616	Error converting Oracle date to TT_TIMESTAMP	Type of Message: Error Cause: The data type conversion failed. Impact: You cannot convert the ORA_DATE data type to a TT_TIMESTAMP data type. User Action: Ensure that the ORA_DATE data type you are attempting to convert is within the ranges supported by the TT_TIMESTAMP data type. For more information on ranges supported by the TT_TIMESTAMP data type, see Type specifications in Oracle TimesTen In-Memory Database SQL Reference.
2617	Error converting Oracle date to Oracle timestamp	Type of Message: Error Cause: The data type conversion failed. Impact: You cannot convert the ORA_DATE data type to a ORA_TIMESTAMP data type. User Action: Ensure that the ORA_DATE data type you are attempting to convert is within the ranges supported by the ORA_TIMESTAMP data type. For more information on ranges supported by the ORA_TIMESTAMP data type, see Type specifications in Oracle TimesTen In-Memory Database SQL Reference.
2618	Error converting Oracle timestamp to TT_TIMESTAMP	Type of Message: Error Cause: The data type conversion failed. Impact: You cannot convert the ORA_TIMESTAMP data type to a TT_TIMESTAMP data type. User Action: Ensure that the ORA_TIMESTAMP data type you are attempting to convert is within the ranges supported by the TT_TIMESTAMP data type. For more information on ranges supported by the TT_TIMESTAMP data type, see Type specifications in Oracle TimesTen In-Memory Database SQL Reference.
2619	Error converting Oracle timestamp to Oracle date	Type of Message: Error Cause: The data type conversion failed. Impact: You cannot convert the ORA_TIMESTAMP data type to a ORA_DATE data type. User Action: Ensure that the ORA_TIMESTAMP data type you are attempting to convert is within the ranges supported by the ORA_DATE data type. For more information on ranges supported by the ORA_DATE data type, see Type specifications in Oracle TimesTen In-Memory Database SQL Reference.
2620	Error converting TT_TIMESTAMP to Oracle date	Type of Message: Error Cause: The data type conversion failed. Impact: You cannot convert the TT_TIMESTAMP data type to a ORA_DATE data type. User Action: Ensure that the TT_TIMESTAMP data type you are attempting to convert is within the ranges supported by the ORA_DATE data type. For more information on ranges supported by the ORA_DATE data type, see Type specifications in Oracle TimesTen In-Memory Database SQL Reference.
2621	Error converting TT_TIMESTAMP to Oracle timestamp	Type of Message: Error Cause: The data type conversion failed. Impact: You cannot convert the TT_TIMESTAMP data type to a ORA_TIMESTAMP data type. User Action: Ensure that the ORA_TIMESTAMP data type you are attempting to convert is within the ranges supported by the ORA_TIMESTAMP data type. For more information on ranges supported by the ORA_TIMESTAMP data type, see Type specifications in Oracle TimesTen In-Memory Database SQL Reference.
2622	Format string in string must be a string literal	Type of Message: Error Cause: You attempted to specify an expression in the format string. The format string must be a string literal. Impact: TimesTen did not perform the operation. User Action: Specify the format string again using a string literal. For more information, see Format models in Oracle TimesTen In-Memory Database SQL Reference.
2623	Invalid number	Type of Message: Error Cause: You specified an invalid value for the NUMBER data type. Impact: TimesTen did not perform the operation. User Action: Specify a correct value for the NUMBER data type. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2705	Column column_name in statement is not in group by list	Type of Message: Error Cause: You specified one or more columns in the SELECT column list or the HAVING clause and did not include the column(s) in the GROUP BY clause. Simple columns (not aggregate or expressions) referenced in the SELECT column list or the HAVING clause must be specified in the GROUP BY column list. Impact: TimesTen did not perform the SELECT operation. User Action: Perform the operation again making sure to include columns in the SELECT list or HAVING clause in the GROUP BY clause. For more information, see SELECT in Oracle TimesTen In-Memory Database SQL Reference.
2706	Query not in select distinct list	Type of Message: Error Cause: You issued a query using the DISTINCT and ORDER BY clauses in which the column(s) specified in the ORDER BY clause were not in the SELECT DISTINCT list. Impact: TimesTen did not execute the query. User Action: Review the query making sure the columns specified in the ORDER BY clause have been specified in the SELECT DISTINCT list. For more information, see SELECT in Oracle TimesTen In-Memory Database SQL Reference.
2712	Attempt to update primary key column(s) of table table_name	Type of Message: Error Cause: You attempted to update the values of a primary key column. Impact: TimesTen did not perform the operation. User Action: Review the operation making sure not to update primary key columns.
2764	DISTINCT within aggregate function cannot reference expression	Type of Message: Error Cause: You attempted to invoke an aggregate function specifying the DISTINCT operator within the aggregate function and used the DISTINCT operator to reference an expression. Impact: TimesTen did not invoke the function. User Action: Invoke the aggregate function and ensure that the DISTINCT operator references a simple column, not an expression. For more information, see Aggregate functions in Oracle TimesTen In-Memory Database SQL Reference.
2765	Invalid use of aggregate function	Type of Message: Error Cause: You attempted to use an aggregate function in an invalid context. For example, you cannot use an aggregate function in the SET clause of an UPDATE statement. Impact: TimesTen did not perform the operation. User Action: Review your use of the aggregate function to make sure it is used in a valid context. For more information, see Aggregate functions in Oracle TimesTen In-Memory Database SQL Reference.
2774	Invalid character following escape character	Type of Message: Error Cause: You attempted to use the escape character in the LIKE predicate, but did follow this escape character with % (percent), or _ (underscore), or the escape character itself. Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure to follow the escape character with %, _, or the escape character itself.
2775	Invalid ESCAPE clause in LIKE expression	Type of Message: Error Cause: You specified an invalid escape character in the LIKE expression. Invalid escape characters are % (percent) and _ (underscore). Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure not to specify % or _ as the escape character in the escape clause. For more information, see LIKE predicate in Oracle TimesTen In-Memory Database SQL Reference.
2776	Both arguments of binary operation cannot be parameters with undefined type; please use CAST operator to define data type for parameters	Type of Message: Error Cause: You attempted a binary operation in which the operands were parameters of undefined type. Impact: TimesTen did not perform the binary operation. User Action: Retry the binary operation making sure the operands have a defined type. Use the CAST operator to define the data type for the parameters. For more information, see CAST in Oracle TimesTen In-Memory Database SQL Reference.
2777	Argument of unary operation cannot be parameter with undefined type; please use CAST operator to define a data type for parameter	Type of Message: Error Cause: You attempted a unary operation in which the operands were parameters of undefined type. Impact: TimesTen did not perform the unary operation. User Action: Retry the unary operation making sure the operands have a defined type. Use the CAST operator to define the data type for the parameter. For more information, see CAST in Oracle TimesTen In-Memory Database SQL Reference.
2778	Cannot infer type of parameter from its use	Type of Message: Error Cause: You attempted an operation involving dynamic parameters and TimesTen cannot infer the data type. Impact: TimesTen did not perform the operation. User Action: Review the use of the parameters in the operation.
2779	Value length is inconsistent with type length	Type of Message: Error Cause: You provided a VARBINARY value that is inconsistent with the defined length of the column. Impact: TimesTen did not perform the operation. User Action: Check the VARBINARY value, making sure the length is appropriate for the defined column. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2781	Pages value must be greater than zero and less than number	Type of Message: Error Cause: You specified an inappropriate value for the PAGES clause of a table or materialized view definition. Impact: TimesTen did not perform the operation. User Action: Specify a constant value that is greater than 0 for the PAGES value. For more information, see CREATE TABLE, ALTER TABLE, or CREATE MATERIALIZED VIEW in Oracle TimesTen In-Memory Database SQL Reference.
2783	Alter table to set new pages value is valid only if the table has a hash index on the primary key	Type of Message: Error Cause: You issued an ALTER TABLE...SET PAGES statement to possibly resize the hash index of a primary key, but there is no defined hash index for the primary key of the table. Impact: TimesTen did not perform the ALTER operation. User Action: Run the ttIsql indexes command on the table to check the indexes defined on the table. ALTER TABLE...SET PAGES is used to resize an already defined primary key hash index. For more information, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2784	Column column_name has no default value defined	Type of Message: Error Cause: You attempted to specify the DEFAULT clause of an INSERT or UPDATE statement on a column defined as not null, but with no defined DEFAULT clause. Impact: TimesTen did not perform the INSERT or UPDATE operation. User Action: Make sure the default clause has been defined on the column used in the DEFAULT clause of the INSERT or UPDATE statement. For more information, see INSERT or UPDATE in Oracle TimesTen In-Memory Database SQL Reference.
2785	Column column_name has no unique constraint	Type of Message: Error Cause: You attempted to issue an ALTER TABLE statement to drop a UNIQUE constraint, but there was no UNIQUE constraint defined for the column. Impact: TimesTen did not alter the table to drop the constraint. User Action: Check the constraints defined on the columns of the table, making sure the column you want to drop has a unique constraint defined on it. Run the ttIsql indexes command on the table to display the constraint information. For more information, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference or ttIsql in the Oracle TimesTen In-Memory Database Reference.
2786	Column column_name already has unique constraint	Type of Message: Error Cause: You attempted to issue an ALTER TABLE statement to add a UNIQUE constraint, but there was a UNIQUE constraint previously defined for the column. Impact: TimesTen did not alter the table to add the constraint. User Action: Check the constraints defined on the columns of the table, making sure the column you want to add a constraint to does not have a unique constraint defined on it. Run the ttIsql indexes command on the table to display the constraint information. For more information, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference or ttIsql in the Oracle TimesTen In-Memory Database Reference.
2787	DateTime arithmetic error. error_details	Type of Message: Error Cause: You attempted a date time arithmetic operation that resulted in an invalid DATE, TIME or TIMESTAMP. Impact: TimesTen did not perform the operation. User Action: Check the details of the error message for possible causes. Check conversion rules. As an example, the operation could have resulted in an month that is greater than 12. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2788	Value too big for the interval type	Type of Message: Error Cause: You attempted a conversion of an interval data type that resulted in too large of a value for the data type or you specified an interval constant that is too large. Impact: TimesTen did not perform the operation. User Action: Check the conversion rules and review the semantics of INTERVAL in Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2789	An interval data type must be specified for a datetime arithmetic result	Type of Message: Error Cause: You attempted a datetime arithmetic operation, but did not specify a valid interval type or did not cast to an interval type for the datetime arithmetic operation. Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure to cast to an interval type. For more information, see Datetime and interval data types in arithmetic operations in Oracle TimesTen In-Memory Database SQL Reference.
2790	Cannot infer type of case expression from its use	Type of Message: Error Cause: You specified a case expression in which the data types cannot be inferred from their use in the expression. Impact: TimesTen did not perform the operation. User Action: Check the case expression making sure that TimesTen can determine the resulting data type based on the use of the data types. For more information, see CASE expressions in Oracle TimesTen In-Memory Database SQL Reference.
2791	The FROM clause of a join update statement must include the updated table	Type of Message: Error Cause: You issued an UPDATE statement, specifying a join in the SET clause, but did not specify the table to be updated in the FROM clause. Impact: TimesTen did not perform the operation. User Action: Retry the UPDATE statement making sure to specify the table to be updated in the FROM clause. For more information, see UPDATE in Oracle TimesTen In-Memory Database SQL Reference.
2792	All updated columns must belong to updated table	Type of Message: Error Cause: You issued an UPDATE statement, specifying a join in the SET clause, but the updated columns were not found in the table to be updated. Impact: TimesTen did not perform the UPDATE operation. User Action: Retry the UPDATE statement making sure the columns used in the join operation are defined in the updated table. For more information, see UPDATE in Oracle TimesTen In-Memory Database SQL Reference.
2793	A selected rowid or column reference is not found in the current scope	Type of Message: Error Cause: You attempted to select a ROWID or column that is not accessible in the current scope. Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure that the ROWID or column is not in the current scope. For more information, see SELECT in Oracle TimesTen In-Memory Database SQL Reference.
2794	Argument argument_name is out of range	Type of Message: Error Cause: You specified an out of range value as an argument to a function. Impact: TimesTen did not invoke the function. User Action: Check the arguments to the function, in particular the argument given in the error message. For more information, see Functions in Oracle TimesTen In-Memory Database SQL Reference.
2795	column_name not in the select list of the first select	Type of Message: Error Cause: You specified a column name in the ORDER BY clause, but the column of the table or column alias was not in the left most SELECT list. Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure the column name of the table or the column alias in the left most select list is in the ORDER BY clause. For more information, see SELECT in Oracle TimesTen In-Memory Database SQL Reference.
2796	ON COMMIT option is only supported with temporary tables	Type of Message: Error Cause: You specified the ON COMMIT clause for a table that is not a temporary table. This clause is valid on temporary tables only. Impact: TimesTen did not create the table. User Action: Omit this clause when creating tables that are not temporary tables. For more information, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2797	First two arguments of INSTR operation cannot be both parameters with undefined type; please use CAST operator to define data type for parameters	Type of Message: Error Cause: You attempted to invoke the INSTR function, but the first two arguments (expressions) resulted in undefined data types. Impact: TimesTen did not invoke the function. User Action: Retry invoking the function, making sure to cast the expression to a defined data type. For more information, see INSTR, INSTRB, INSTR4 in Oracle TimesTen In-Memory Database SQL Reference.
2798	First argument of SUBSTR operation cannot be parameter with undefined type; please use CAST operator to define data type for parameter	Type of Message: Error Cause: You invoked the SUBSTR function but specified an undefined type for the first parameter to the function. Impact: TimesTen did not invoke the function. User Action: Invoke the function again making sure to pass a parameter with a defined type. Consider using the CAST operator to cast the parameter to the correct type. For more information, see SUBSTR, SUBSTRB, SUBSTR4 in Oracle TimesTen In-Memory Database SQL Reference.
2803	Only one unique value for NLS_SORT is allowed for an index and all character type fields must be specified with that NLS_SORT	Type of Message: Error Cause: You attempted to create a linguistic index, but did not use the same NLS_SORT value for the columns. Impact: TimesTen did not create the index. User Action: Recreate the linguistic index using the same NLS_SORT value for all columns used in the index or consider creating separate indexes for each NLS_SORT value. For more information, see NLSSORT in Oracle TimesTen In-Memory Database SQL Reference.
2804	NLS parameter for linguistic index must be a constant string	Type of Message: Error Cause: You attempted to create a linguistic index, but did not specify a constant for the NLS_SORT value. Impact: TimesTen did not create the index. User Action: Recreate the linguistic index making sure to specify a constant NLS_SORT value as a parameter to the NLSSORT function. For more information, see NLSSORT in Oracle TimesTen In-Memory Database SQL Reference.
2806	Invalid NLS parameter for NLSSORT function sort_value	Type of Message: Error Cause: You attempted to create a linguistic index using the NLSSORT function, but you specified an invalid NLS_SORT parameter. Impact: TimesTen did not create the index. User Action: Check the NLS_SORT value, making sure it is a supported linguistic sort sequence. For more information, see NLSSORT in Oracle TimesTen In-Memory Database SQL Reference.
2807	Oracle timestamp precision overflow	Type of Message: Error Cause: An ORA_TIMESTAMP data type conversion failed due to fractional seconds precision overflow. Impact: TimesTen cannot perform the operation. User Action: Ensure that the source and target columns of type ORA_TIMESTAMP have compatible fractional seconds precision length to avoid overflow.
2809	Invalid interval	Type of Message: Error Cause: You specified an invalid string format for the INTERVAL literal. Impact: TimesTen did not perform the operation. User Action: Specify the INTERVAL again, making sure to use a valid string literal. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2811	Not a group by expression	Type of Message: Error Cause: You attempted to use an expression that is not in the GROUP BY list. Impact: TimesTen did not execute the query. User Action: Check your query making sure columns in the expression are included in the GROUP BY list. Then, retry the query. For more information, see SELECT in Oracle TimesTen In-Memory Database SQL Reference.
2812	Error converting from character string 'string' to Oracle date	Type of Message: Error Cause: TimesTen encountered a conversion error when converting a character string to the Oracle DATE data type. One possible cause is you specified an invalid character string to the TO_DATE function. Impact: TimesTen did not perform the operation or did not invoke the TO_DATE function. User Action: Retry the operation or function making sure to specify a valid character string. For more information, see TO_DATE in Oracle TimesTen In-Memory Database SQL Reference.
2813	Error converting from character string 'string' to Oracle timestamp	Type of Message: Error Cause: TimesTen encountered a conversion error when converting a character string to the Oracle TIMESTAMP data type. Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure to specify a valid character string. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2814	Trim character value should be a single character	Type of Message: Error Cause: You attempted to invoke the TRIM function, but specified more than one trim character. You must specify one trim character. Impact: TimesTen did not invoke the function. User Action: Invoke the function again, making sure to specify only one trim character. For more information, see TRIM in Oracle TimesTen In-Memory Database SQL Reference.
2815	Invalid number of arguments for function function_name	Type of Message: Error Cause: You specified an incorrect number of arguments for the specified function. Impact: TimesTen did not invoke the function. User Action: Check the syntax for the function, making sure to specify the correct number of arguments. For more information, see Functions in Oracle TimesTen In-Memory Database SQL Reference.
2816	Given or computed year value is out of range	Type of Message: Error Cause: You specified a value that was out of range or resulted in an out of range year value. Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure to specify a valid year value.
2817	Invalid data type data_type for argument argument_name for function function_name	Type of Message: Error Cause: You specified an invalid data type as an argument to a function. Impact: TimesTen did not invoke the function. User Action: Check the details of the error message to find out which argument to the function is invalid. For more information, see Functions in Oracle TimesTen In-Memory Database SQL Reference.
2818	Unknown function function_name. If this is a PLSQL function note that such functions are not yet supported in SQL statements.	Type of Message: Error Cause: You specified a function that is not supported in TimesTen. Impact: TimesTen returned an unknown function error. User Action: Check the supported functions. For more information, see Functions in Oracle TimesTen In-Memory Database SQL Reference.
2819	Invalid value 'value' for argument number of procedure procedure_name. The valid values are <values>.	Type of Message: Error Cause: You specified an invalid value for a parameter used in a built-in procedure. Impact: TimesTen did not call the built-in procedure. User Action: Check the details of the error message to find out the parameter value that is invalid for the particular built-in procedure. For more information, see Built-In Procedures in Oracle TimesTen In-Memory Database Reference.
2820	Invalid USERENV parameter	Type of Message: Error Cause: You specified an invalid parameter to the SYS_CONTEXT function. Impact: TimesTen did not invoke the function. User Action: Check the supported values for the parameters of the SYS_CONTEXT function. For more information, see SYS_CONTEXT in Oracle TimesTen In-Memory Database SQL Reference.
2821	Date_format_model is not a valid date format model for date function	Type of Message: Error Cause: You specified an invalid date format model for the date function. Impact: TimesTen did not invoke the function. User Action: Check the valid date format model for the function. Then, retry invoking the function with the correct date format model. For more information, see Datetime format models in Oracle TimesTen In-Memory Database SQL Reference.
2822	Index type was changed	Type of Message: Warning Cause: You changed the primary key index type while replication was using the index. Impact: TimesTen retried the operation using the new index. User Action: This is a warning alerting you that the index type was changed. No action is necessary.
2823	Expression ('expression') in value list is not supported	Type of Message: Error Cause: You specified a column reference in an IN value list. Impact: TimesTen cannot execute the SQL statement. User Action: Rewrite the IN value clause with an OR condition. Alternatively, remove the column reference from the SQL statement and retry the operation.For more information, see ANY / IN predicate (value list) in Oracle TimesTen In-Memory Database SQL Reference.
2860	Invalid zero-length parameter value	Type of Message: Error Cause: You provided a value to a parameter that had a zero length, but a length was required. Impact: TimesTen did not perform the operation. User Action: Check the parameter requirements, making sure not to specify a zero length value.
2861	Incorrect parameter value length	Type of Message: Error Cause: You provided a value to a parameter, but the length was invalid. Impact: TimesTen did not perform the operation. User Action: Check the parameter requirements, making sure not to specify an invalid parameter length.
2862	Parameter length exceeds maximum	Type of Message: Error Cause: You provided a value to a parameter in which the length exceeds the maximum allowed length for the parameter. Impact: TimesTen did not perform the operation. User Action: Check the parameter requirements, making sure not to specify a value that exceeds the maximum length allowed for the parameter.
2863	Char parameter length exceeds maximum length	Type of Message: Error Cause: You provided a value to a character type parameter in which the length exceeds the maximum allowed for the parameter. Impact: TimesTen did not perform the operation. User Action: Check the parameter requirements, making sure not to specify a character length that exceeds the maximum for the parameter.
2864	Output parameter value truncated	Type of Message: Warning Cause: You provided a value to an output parameter that is too large for the buffer. Impact: TimesTen issued a warning, performed the operation, but truncated the value of the output parameter. User Action: Check the buffer allocation and consider increasing the allocation. Also, make sure that the truncation is an acceptable result.
2865	Output parameter buffer is too small	Type of Message: Warning Cause: You attempted to supply an output parameter but the output parameter buffer is too small. Impact: TimesTen issued a warning, performed the operation, but truncated the value. User Action: Consider increasing the allocation size of the output parameter buffer. Also, check the results making sure a truncated value is an acceptable result.
2866	Parameter value too large for 2-byte included-length	Type of Message: Error Cause: You provided a value to a parameter that is greater than the 2-byte included length. Impact: TimesTen did not perform the operation. User Action: Check the parameter requirements, making sure that the parameter value does not exceed the 2-byte included length.
2867	Length of number value exceeds maximum	Type of Message: Error Cause: You provided a value to a parameter expressed as NUMBER, but the length provided exceeded the maximum length of NUMBER. Impact: TimesTen did not perform the operation. User Action: Check the parameter requirements. Retry the operation, specifying a parameter value that does not exceed the maximum for the NUMBER type.
2868	String contains an invalid hexadecimal character	Type of Message: Error Cause: TimesTen attempted a conversion of a character string to binary, but the string contained an invalid hexadecimal character. Valid characters are 0-9, A-F, and a-f. Impact: TimesTen did not perform the conversion. User Action: Check the string making sure to specify correct hexadecimal characters. Then, retry the operation with the modified string.
2869	String is not a valid numeric literal	Type of Message: Error Cause: TimesTen attempted a conversion of a string to a numeric literal, but the literal was invalid. Impact: TimesTen did not perform the conversion. User Action: Check the string making sure to specify a valid numeric literal. Then, retry the operation with the modified string.
2870	String contains an invalid date-time character	Type of Message: Error Cause: TimesTen attempted a conversion of a string to a datetime data type, but the string contained an invalid datetime character. Impact: TimesTen did not perform the conversion. User Action: Check the string making sure to specify a valid datetime character. Then, retry the operation with the modified string.
2871	Truncation occurred during conversion to date-time value	Type of Message: Warning Cause: TimesTen performed a conversion to a datetime value, but the value was truncated. One cause could be that the data type resolved to TT_TIMESTAMP, but the source value specified more digits than the destination value. Impact: TimesTen issued a warning, performed the operation, but truncated the value. User Action: Check the datetime value making sure that truncation is an acceptable result.
2872	Error converting to date-time value	Type of Message: Error Cause: TimesTen attempted a conversion to a datetime value, but encountered a conversion error. Impact: TimesTen did not perform the operation. User Action: Check that the source value contains a valid datetime value. Also check that the values are not out of range.
2873	Invalid statement handle	Type of Message: Error Cause: Your application attempted to bind an invalid statement handle to a REF CURSOR parameter. Impact: The compilation or execution failed. User Action: Modify the application code, making sure to bind a valid statement handle.
2874	Statement handle for ref cursor is in an invalid state	Type of Message: Error Cause: Your application attempted to bind a statement handle to a REF CURSOR parameter, but the handle was in an invalid state. Impact: The compilation or execution failed. User Action: Modify the application code, making sure to bind a statement handle that is in the correct state. Make sure that a statement handle bound to an OUT REF CURSOR does not have an open result set.
2875	Ref cursor statement handle must be from same connection as base statement handle	Type of Message: Error Cause: Your application attempted to bind a statement handle to a REF CURSOR, but the handle was allocated to a different connection than the connection of the base statement handle. The statement handle bound to the REF CURSOR must be from the same connection as the base statement handle. Impact: The compilation or execution failed. User Action: Modify the application code, making sure the statement handle bound to the REF CURSOR is in the same connection as the base statement handle.
2876	Value number out of range; specify 0 or 1	Type of Message: Error Cause: You called a built-in procedure in which you did not pass the required 0 or 1 value as a parameter. Impact: TimesTen did not execute the procedure. User Action: Check the details of the error message to determine the out of range value. Retry the procedure making sure to pass 0 or 1 as a parameter value. For more information, see Built-In Procedures in Oracle TimesTen In-Memory Database Reference.
2877	Output parameter conversion resulted in an incomplete character	Type of Message: Error Cause: TimesTen attempted a conversion of an output parameter, but your allocated buffer was too small. This resulted in a partial multibyte character value. Impact: TimesTen did not perform the conversion. User Action: Check the allocation of the output buffer. Consider increasing the size of the buffer so that it can accommodate the entire result value.
2878	Output parameter conversion error (code=string)	Type of Message: Error Cause: TimesTen encountered an error when trying to convert an output parameter. Impact: TimesTen did not perform the conversion. User Action: Check the error code and string in the error message to determine the specifics of the conversion error. Once determined, make the necessary corrections, and retry the operation.
2879	Non-positive timestamps not allowed for function_name	Type of Message: Error Cause: You attempted to invoke a function, but specified a timestamp value with a year less than or equal to 0. TimesTen does not support negative years because the timestamp arithmetic could result in a value equal to year 0. TimesTen does not support year 0. Impact: TimesTen did not invoke the function. User Action: Check the details of the error message to determine the function name. Invoke the function again, making sure to specify positive timestamp values as arguments to the function. For more information, see Functions in Oracle TimesTen In-Memory Database SQL Reference.
2903	Invalid character character	Type of Message: Error Cause: The specified SQL statement contains a character that is not acceptable in SQL. Impact: TimesTen did not execute the statement. User Action: Correct the SQL statement and try the operation again.
2904	Invalid element string in number format	Type of Message: Error Cause: You specified an invalid string in the number format. One cause could be an improper use of the TO_CHAR function. Impact: TimesTen did not perform the operation. User Action: Check the string used in the number format. If you are attempting to invoke a TO_CHAR function, check the arguments to the function. Modify the string and retry the operation. For more information, see TO_CHAR in Oracle TimesTen In-Memory Database SQL Reference.
2905	Invalid element string in date format	Type of Message: Error Cause: You specified an invalid string in the date format. One cause could be an improper use of the TO_CHAR or TO_DATE function. Impact: TimesTen did not perform the operation. User Action: Check the string used in the date format. If you are attempting to invoke the TO_CHAR or TO_DATE function, check the arguments to the function. Modify the string and retry the operation. For more information, see TO_CHAR or TO_DATE in Oracle TimesTen In-Memory Database SQL Reference.
2906	Bad number format	Type of Message: Error Cause: You specified an invalid number format. One cause could be an improper use of the TO_CHAR function. Impact: TimesTen did not perform the operation. User Action: Check the number format. If you are attempting to invoke a TO_CHAR function, check the arguments to the function. Modify the number format and retry the operation. For more information, see TO_CHAR in Oracle TimesTen In-Memory Database SQL Reference.
2907	Bad date format	Type of Message: Error Cause: You specified an invalid date format. One cause could be an improper use of the TO_CHAR or TO_DATE function. Impact: TimesTen did not perform the operation. User Action: Check the date format. If you are attempting to invoke a TO_CHAR or TO_DATE function, check the arguments to the function. Modify the string and retry the operation. For more information, see TO_CHAR or TO_DATE in Oracle TimesTen In-Memory Database SQL Reference.
2908	Error Converting decimal to character string	Type of Message: Error Cause: TimesTen encountered an error when converting a decimal to a character string. One cause could be an improper use of the TO_CHAR function. Impact: TimesTen did not perform the operation. User Action: Check the decimal and character string. If you are attempting to invoke a TO_CHAR function, check the arguments to the function. For more information, see TO_CHAR in Oracle TimesTen In-Memory Database SQL Reference.
2909	Error Converting numeric value numeric_value to character string	Type of Message: Error Cause: TimesTen encountered an error when converting an integer or float data type to a character string. One cause could be an improper use of the TO_CHAR function. Impact: TimesTen did not perform the operation. User Action: Check the numeric and character string used in the conversion. If you are attempting to invoke a TO_CHAR function, check the arguments to the function. Make necessary modifications and retry the operation. For more information, see TO_CHAR in Oracle TimesTen In-Memory Database SQL Reference.
2910	Overflow converting floating-point value to char	Type of Message: Error Cause: There was an overflow error when TimesTen attempted to convert a floating-point value to a character. One cause could be an improper use of the TO_CHAR function. Impact: TimesTen did not perform the operation. User Action: Check the floating-point value and the character used in the conversion. If you are attempting to invoke a TO_CHAR function, check the arguments to the function. Make necessary modifications and retry the operation. For more information, see TO_CHAR in Oracle TimesTen In-Memory Database SQL Reference.
2911	Float underflow for TO_CHAR function	Type of Message: Error Cause: You attempted to invoke the TO_CHAR function, but TimesTen encountered an underflow error when attempting to convert a floating-point value to a character type. Impact: TimesTen did not perform the operation. User Action: Check the invalid floating-point value and the character string passed as arguments to the TO_CHAR function. Make any modifications and retry the operation. For more information, see TO_CHAR in Oracle TimesTen In-Memory Database SQL Reference.
2912	Invalid escape sequence string	Type of Message: Error Cause: TimesTen detected an improperly formed Unicode escape sequence string. Impact: TimesTen did not perform the operation. User Action: Check the valid escape sequence string. Retry the operation, making sure to specify a valid escape sequence string. For more information, see Character and Unicode Strings in Oracle TimesTen In-Memory Database Reference.
2913	Invalid argument 'argument' for NUMTODSINTERVAL function	Type of Message: Error Cause: You specified an invalid interval constant as the second argument to the NUMTODSINTERVAL function. Valid constants are: DAY, HOUR, SECOND or MINUTE. Impact: TimesTen did not invoke the function. User Action: Invoke the function again, making sure to specify a valid string constant as the second argument to the function. For more information, see NUMTODSINTERVAL in Oracle TimesTen In-Memory Database SQL Reference.
2914	Invalid argument 'argument' for NUMTOYMINTERVAL function	Type of Message: Error Cause: You specified an invalid interval constant as the second argument to the NUMTOYMINTERVAL function. Valid constants are YEAR or MONTH. Impact: TimesTen did not invoke the function. User Action: Invoke the function again, making sure to specify a valid string constant as the second argument to the function. For more information, see NUMTOYMINTERVAL in Oracle TimesTen In-Memory Database SQL Reference.
2915	Too many values in the subquery of the set clause	Type of Message: Error Cause: You attempted to issue a join UPDATE statement, but the subquery of the SET clause contains more values than the column list. Impact: TimesTen did not perform the update operation. User Action: Check the subquery used in the SET clause and make sure it does not contain more values than the updated column list. For more information, see UPDATE in Oracle TimesTen In-Memory Database SQL Reference.
2916	Not enough values in the subquery of the set clause	Type of Message: Error Cause: You attempted to issue a join UPDATE statement, but the subquery of the SET clause contains less values than the column list. Impact: TimesTen did not perform the update operation. User Action: Check the subquery used in the SET clause and make sure it does not contain less values than the updated column list. For more information, see UPDATE in Oracle TimesTen In-Memory Database SQL Reference.
2917	Invalid extract field for extract source	Type of Message: Error Cause: You attempted to extract an incompatible field from a value. One cause could be extracting a YEAR field from an interval DAY to SECOND. Impact: TimesTen did not perform the operation. User Action: Check the extract source and the extract field, making sure both are compatible. Then, retry the operation.
2918	Precision of number type is out of range [1,38]	Type of Message: Error Cause: You attempted to define the NUMBER data type with a precision that is out of range. The correct precision is between 1 and 38. Impact: TimesTen did not perform the operation. User Action: Redefine the column definition specifying the correct precision for the NUMBER data type. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2919	Scale of number type is out of range [-84,127]	Type of Message: Error Cause: You attempted to define the NUMBER data type with a scale that is out of range. The correct range is between -84 and 127. Impact: TimesTen did not perform the operation. User Action: Redefine the column definition specifying the correct scale for the NUMBER data type. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2920	Number type arithmetic overflow	Type of Message: Error Cause: The result of the arithmetic operation was too large for the result type, based on the defined precision and scale of the NUMBER data type of the column. Impact: TimesTen did not perform the operation. User Action: Review the result data type and the precision and scale you defined for the NUMBER data type of your column definition. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2921	Number type arithmetic underflow	Type of Message: Warning Cause: The result of the arithmetic operation was too small for the result type, based on the precision and scale of the NUMBER data type of the column. Impact: TimesTen performed the operation, but rounded the result to 0. User Action: Review the result data type making sure it is sufficient for the defined precision and scale of the data type column. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2922	Invalid number type value	Type of Message: Error Cause: You specified an operand to an arithmetic operation that is not a valid number. Impact: TimesTen did not perform the operation. User Action: Review the operands of the arithmetic operation and also the definition of the NUMBER data type to determine why the operand is invalid. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2923	Number type value overflow	Type of Message: Error Cause: You specified a value for the NUMBER data type that exceeded the maximum NUMBER limit for the type of variable. Impact: TimesTen did not perform the operation. User Action: Retry the operation making sure to specify a value that does not exceed the maximum allowable for the NUMBER data type. For more information, see NUMBER in Oracle TimesTen In-Memory Database SQL Reference.
2924	Number type value underflow	Type of Message: Warning Cause: You specified a value for the NUMBER data type that was less than the lower bound of this type of variable. Impact: TimesTen generated a warning, but continued the operation, and rounded the result to 0. User Action: Check the value. If the result is rounded to 0, ensure that it is acceptable. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2925	Overflow converting number to char	Type of Message: Error Cause: TimesTen attempted to convert a NUMBER data type to a character data type and the result was too large to be converted. Impact: TimesTen did not perform the operation. User Action: Check the parameters of the TO_CHAR function and the conversion rules. Then, retry the operation. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2926	Underflow converting number to char	Type of Message: Warning Cause: TimesTen attempted to convert a NUMBER data type to a character data type and the result was too small to be converted. Impact: TimesTen issued a warning, completed the operation, but rounded the result to 0. User Action: Check the parameters of the TO_CHAR function and the data type conversion rules to confirm the rounding to 0 is an acceptable result. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2927	Error converting Number to Char	Type of Message: Error Cause: TimesTen attempted a conversion of a NUMBER data type to a character data type and the conversion resulted in an error. Impact: TimesTen did not perform the conversion. User Action: Check the semantics of the data types and the conversion rules. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2928	Error converting Char to Number	Type of Message: Error Cause: TimesTen attempted a conversion of a character data type to a NUMBER data type and the conversion resulted in an error. Impact: TimesTen did not perform the operation. User Action: Check the semantics of the data types and the conversion rules. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2929	Error converting Number to Double	Type of Message: Error Cause: TimesTen attempted a conversion of a NUMBER data type to a DOUBLE data type and the conversion resulted in an error. Impact: TimesTen did not perform the conversion. User Action: Check the semantics of the data types and the conversion rules. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2930	Error converting Number to Float	Type of Message: Error Cause: TimesTen attempted a conversion of a NUMBER data type to a FLOAT data type and the conversion resulted in an error. Impact: TimesTen did not perform the conversion. User Action: Check the semantics of the data types and the conversion rules. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2931	Overflow converting Number to TinyInt	Type of Message: Error Cause: TimesTen attempted a conversion of a NUMBER data type to a TT_TINYINT data type and the result was too large for the TT_TINYINT data type. Impact: TimesTen did not perform the conversion. User Action: Check the semantics of the data types and the conversion rules. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2932	Underflow converting Number to TinyInt	Type of Message: Warning Cause: TimesTen attempted a conversion of a NUMBER data type to a TT_TINYINT data type and the result was too small for the TT_TINYINT data type. Impact: TimesTen issued a warning, performed the operation, but rounded the result to 0. User Action: Check the semantics of the data types and the conversion rules and make sure the rounding to 0 is an acceptable result. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2933	Error converting Number to TinyInt	Type of Message: Error Cause: TimesTen attempted a conversion of a NUMBER data type to a TT_TINYINT data type and the conversion resulted in an error. Impact: TimesTen did not perform the conversion. User Action: Check the semantics of the data types and the conversion rules. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2934	Overflow converting Number to SmallInt	Type of Message: Error Cause: TimesTen attempted a conversion of a NUMBER data type to a SMALLINT data type and the conversion resulted in a value that was to large for the SMALLINT data type. Impact: TimesTen did not perform the conversion. User Action: Check the semantics of the data types and the conversion rules. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2935	Underflow converting Number to SmallInt	Type of Message: Warning Cause: TimesTen attempted a conversion of a NUMBER data type to a SMALLINT data type and the conversion resulted in an value that is too small for the SMALLINT data type. Impact: TimesTen issued a warning, performed the operation, but rounded the result to 0. User Action: Check the semantics of the data types and the conversion rules, making sure the rounding to 0 is an acceptable result. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2936	Error converting Number to SmallInt	Type of Message: Error Cause: TimesTen attempted a conversion of a NUMBER data type to a SMALLINT data type and the conversion resulted in an error. Impact: TimesTen did not perform the conversion. User Action: Check the semantics of the data types and the conversion rules. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2937	Overflow converting Number to Int	Type of Message: Error Cause: TimesTen attempted a conversion of a NUMBER data type to an integer data type and the conversion resulted in a value that was too large for the integer data type. Impact: TimesTen did not perform the conversion. User Action: Check the semantics of the data types and the conversion rules. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2938	Underflow converting Number to Int	Type of Message: Warning Cause: TimesTen attempted a conversion of a NUMBER data type to an integer data type and the conversion resulted in a value that was too small to be converted. Impact: TimesTen issued a warning, performed the operation, but rounded the result to 0. User Action: Check the semantics of the data types and the conversion rules, making sure the rounding to 0 is an acceptable result. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2939	Error converting Number to Int	Type of Message: Error Cause: TimesTen attempted a conversion of a NUMBER data type to a TT_INTEGER data type and the conversion resulted in an error. Impact: TimesTen did not perform the conversion. User Action: Check the semantics of the data types and the conversion rules. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2940	Overflow converting Number to BigInt	Type of Message: Error Cause: TimesTen attempted a conversion of a NUMBER data type to a TT_BIGINT data type and the conversion resulted in a value that was too large for the TT_BIGINT data type. Impact: TimesTen did not perform the conversion. User Action: Check the semantics of the data types and the conversion rules. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2941	Underflow converting Number to BigInt	Type of Message: Warning Cause: TimesTen attempted a conversion of a NUMBER data type to a TT_BIGINT data type and the conversion resulted in a value that was too small for the TT_BIGINT data type. Impact: TimesTen issued a warning, performed the operation, but rounded the result to 0. User Action: Check the semantics of the data types and the conversion rules, making sure the rounding to 0 is an acceptable result. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2942	Error converting Number to BigInt	Type of Message: Error Cause: TimesTen attempted a conversion of a NUMBER data type to a TT_BIGINT data type and the conversion resulted in an error. Impact: TimesTen did not perform the conversion. User Action: Check the semantics of the data types and the conversion rules. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2943	Error truncating a date	Type of Message: Error Cause: An error occurred while attempting to round or truncate a date. A common cause for this is that there is not enough free space in the target column. Impact: The date cannot be rounded or truncated. User Action: None. For more information on the ROUND (date) and TRUNC (date) functions, see ROUND (date) and TRUNC (date) in Oracle TimesTen In-Memory Database SQL Reference.
2944	Invalid number format model	Type of Message: Error Cause: You specified an invalid number format model for the TO_CHAR or TO_NUMBER function. Impact: TimesTen did not invoke the function. User Action: Check the semantics of the function, making sure to specify a valid number format model. For more information, see Number format models in Oracle TimesTen In-Memory Database SQL Reference.
2945	Truncation occurred during Number conversion	Type of Message: Warning Cause: The result was truncated during conversion. Impact: The result of your operation may be less precise than the original number value. User Action: If you are attempting INSERT or UPDATE operations, consider increasing the size of the target column. For more information on column sizes, see Column Overview in Oracle TimesTen In-Memory Database Operations Guide.
2946	Truncation occurred converting Number to Char	Type of Message: Warning Cause: The result is truncated when converting from NUMBER to CHAR, and some fractional data (i.e., numeric data to the right of the decimal point) could not be converted because the supplied CHAR column length is not big enough. Impact: The result of your operation may be less precise than the original number value. User Action: Allocate a larger CHAR buffer to accommodate the result of the conversion. Allocating a large enough CHAR buffer size will prevent truncation of the result. For more information on the CHAR data type, see CHAR in Oracle TimesTen In-Memory Database SQL Reference.
2947	Buffer too small for number to char conversion	Type of Message: Error Cause: The application allocated a buffer that was too small for the number to character conversion. Impact: TimesTen did not perform the conversion operation. User Action: Increase the current allocation size of your buffer to accommodate the specified conversion. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2948	Bad format string 'string'	Type of Message: Error Cause: You specified an invalid format string. Impact: TimesTen did not perform the operation. User Action: Check the details of the error message, your string, and the operation.
2949	Error occurred during Number conversion	Type of Message: Error Cause: An error occurred while attempting to convert a numeric data type. Impact: The conversion operation cannot be completed. User Action: Ensure that your numeric input data is correct. For more information on numeric data types, see Numeric data types in Oracle TimesTen In-Memory Database SQL Reference.
2950	Merge may not update a row more than once, but the row at rowid rowid matched at least two source rows	Type of Message: Error Cause: You attempted a MERGE operation in which you attempted to update the same row of the target table more than once. Impact: TimesTen did not perform the MERGE operation. User Action: Check the details of the error message to retrieve the ROWID information, then retry the operation making sure to update the target row once. For more information, see MERGE in Oracle TimesTen In-Memory Database SQL Reference.
2951	The table being merged into cannot be used for insert values	Type of Message: Error Cause: You attempted a MERGE operation in which you attempted to insert values from the target table columns. Impact: TimesTen did not perform the operation. User Action: Check the semantics of the MERGE statement, making sure not to insert values of the target table. For more information, see MERGE in Oracle TimesTen In-Memory Database SQL Reference.
2952	Source table table_name cannot be updated	Type of Message: Error Cause: You attempted a MERGE operation in which you attempted to update the columns of the source table. Impact: TimesTen did not perform the operation. User Action: Check the details of the error message for the specified source table. Check the semantics of the MERGE statement. Retry the operation, making sure not to update the columns of the source table. For more information, see MERGE in Oracle TimesTen In-Memory Database SQL Reference.
2953	Columns referenced in the ON Clause cannot be updated	Type of Message: Error Cause: You attempted a MERGE operation in which you attempted to update columns that were referenced in the ON clause. Impact: TimesTen did not perform the operation. User Action: Check the semantics of the MERGE statement, making sure that only the target table is updated. For more information, see MERGE in Oracle TimesTen In-Memory Database SQL Reference.
2954	Column in update whereclause is not in either source or target table	Type of Message: Error Cause: You attempted a MERGE operation in which the WHERE condition of the SET UPDATE clause contained a column reference that could not be resolved. Impact: TimesTen did not perform the operation. User Action: Check the column reference in the WHERE condition of the SET UPDATE clause. Verify that the column exists in the source or target table. For more information, see MERGE in Oracle TimesTen In-Memory Database SQL Reference.
2955	Column in insert whereclause cannot refer to target table	Type of Message: Error Cause: You attempted a MERGE operation in which the WHERE condition of the UPDATE or INSERT clause contained a column reference that resolved to the target table. Impact: TimesTen did not perform the operation. User Action: Check the column reference in the WHERE condition of the INSERT or UPDATE clause, making sure that the column reference does not resolve to the target table. For more information, see MERGE in Oracle TimesTen In-Memory Database SQL Reference.
2956	Column in insert whereclause is not in source table	Type of Message: Error Cause: You attempted a MERGE operation in which the WHERE condition of the INSERT or UPDATE clause contained a column reference that was not found in the source table. Impact: TimesTen did not perform the operation. User Action: Check the column reference in the WHERE condition of the INSERT or UPDATE cause, making sure the column reference resolves to the source table. For more information, see MERGE in Oracle TimesTen In-Memory Database SQL Reference.
2957	Bad insert value	Type of Message: Error Cause: You attempted to insert an invalid value in the MERGE operation. One possible cause is the attempt to use an aggregate function as an insert value. Impact: TimesTen did not perform the operation. User Action: Do not use an aggregate function as an insert value. For more information, see MERGE in Oracle TimesTen In-Memory Database SQL Reference.
2958	Source table table_name with set operators such as UNION, INTERSECT, and MINUS is not supported in merge statements	Type of Message: Error Cause: You attempted to use a set operator (UNION, MINUS, or INTERSECT) in the MERGE statement. Impact: TimesTen did not perform the operation. User Action: Do not use set operators in the source table of the MERGE statement. For more information, see MERGE in Oracle TimesTen In-Memory Database SQL Reference.
2960	Scale of timestamp type is out of range [0,9]	Type of Message: Error Cause: You specified an invalid scale for the TIMESTAMP data type.The valid range is 0 to 9. Impact: TimesTen did not perform the operation. User Action: Check the semantics of the TIMESTAMP data type, making sure to specify a range from 0 to 9. For more information, see TIMESTAMP in Oracle TimesTen In-Memory Database SQL Reference.
2961	Inconsistent datatypes: cannot convert data_type to data_type in expression (expression)	Type of Message: Error Cause: TimesTen could not convert one data type to another. Impact: TimesTen did not perform the operation. User Action: Check the details of the message for the data types that could not be converted. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2962	Inconsistent datatypes: expected data_type got data_type in expression (expression)	Type of Message: Error Cause: TimesTen attempted an operation expecting a specific data type, but this data type was not provided. Impact: TimesTen did not perform the operation. User Action: Check the details of the message for the data types that could not be converted. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2963	Inconsistent datatypes: (data_type,data_type) are not compatible in expression (expression)	Type of Message: Error Cause: You attempted an operation in which TimesTen encountered incompatible data types in your expression. Impact: TimesTen did not perform the operation. User Action: Check the details of the message for the data types that are incompatible. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
2970	Decode syntax error: not enough operands	Type of Message: Error Cause: You attempted to invoke the DECODE function and specified less than three arguments. The DECODE function must have at least three arguments: the expression, the search value, and the result. Impact: TimesTen did not invoke the function. User Action: Specify at least three arguments for the DECODE function. For more information, see DECODE in Oracle TimesTen In-Memory Database SQL Reference.
2971	Coalesce syntax error: need at least two operands	Type of Message: Error Cause: You attempted to invoke the COALESCE function by specifying less than two arguments. You must specify at least two arguments for this function. Impact: TimesTen did not invoke the function. User Action: Specify at least two expressions as arguments for the COALESCE function. For more information, see COALESCE in Oracle TimesTen In-Memory Database SQL Reference.
2972	Invalid relational operator: all group of values in the value list must have the same number of values as the left operand	Type of Message: Error Cause: You attempted an operation where the relational operator IN is specified with more than one value in the left operand but at least one group of values in the right operand has a different number of values than the number of values in the left operand. For example: SELECT * FROM t WHERE (a,b) IN ((1,1),(2)); In this example, the second group of values in the IN list contains one less entry than the number specified in the left operand. Impact: TimesTen cannot perform the operation. User Action: Add the missing value or values to the SQL statement and retry the operation. For more information on SQL statements, see SQL Statements in Oracle TimesTen In-Memory Database SQL Reference.
2973	Invalid relational operator: subquery does not project same number of columns as specified in the left operand	Type of Message: Error Cause: You attempted an operation where the relational operator ANY or IN is specified with a subquery that returns a different number of values than the specified in the left operand. For example: SELECT * FROM t1 WHERE (a,b) IN (SELECT c FROM t2); In this example, the group of values returned in the IN list contains one less entry than that the number specified in the left operand. Impact: TimesTen cannot perform the operation. User Action: Add the missing value or values to the SQL statement and retry the operation. For more information on SQL statements, see SQL Statements in Oracle TimesTen In-Memory Database SQL Reference.
2974	Using rownum to restrict number of rows returned cannot be combined with first N or rows M to N	Type of Message: Error Cause: You attempted to use ROWNUM in a query that also uses FIRST N or ROWS M TO N. Impact: TimesTen did not perform the query. User Action: Review the SELECT query and remove ROWNUM from it. Then, retry the query using FIRST N or ROWS M TO N. For more information, see SELECT in Oracle TimesTen In-Memory Database SQL Reference.
2975	Number divide by zero	Type of Message: Error Cause: You attempted an operation that resulted in a divide by 0 error. Impact: TimesTen did not perform the operation. User Action: Investigate why the operation resulted in a divide by 0 error.
2976	Parallel value must be greater than one	Type of Message: Error Cause: You called the ttLoadFromOracle built-in procedure to do a parallel load, but the number of threads was set to 1. Impact: TimesTen did not perform the operation. User Action: Specify a value greater than 1 for the number of threads. For more information, see ttLoadFromOracle in Oracle TimesTen In-Memory Database Reference.
2977	Only DAY lifetime unit is allowed with a TT_DATE column	Type of Message: Error Cause: You attempted to use time-based aging, in which the column used for aging is of type TT_DATE. If the data type is TT_DATE, you must specify DAY as the LIFETIME unit. You specified a different LIFETIME unit. Impact: TimesTen did not perform the create or alter operation. User Action: If the column used for time-based aging is of type TT_DATE, then make sure to specify DAY as the LIFETIME unit. For more information, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2978	Transparent load value must be between 0 and 2	Type of Message: Error Cause: You specified an invalid value for the TransparentLoad attribute. Valid values are 0, 1 or 2. Impact: TimesTen did not perform the operation. User Action: Change the value of the TransparentLoad attribute to 0, 1, or 2.
2979	Invalid relational operator	Type of Message: Error Cause: You specified an invalid relational operator for expressions that are equal or not equal. Impact: TimesTen did not perform the operation. User Action: Retry the expression making sure to specify a valid relational operator.
2980	Cannot add aging policy to a table with an existing aging policy. Have to drop the old aging first	Type of Message: Error Cause: You attempted to add aging to a table that already has an aging policy. Impact: TimesTen could not add the specified aging policy. User Action: Drop the original aging policy and add the new policy or keep the original policy. For more information, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2981	Non existent column column_name specified for time-based aging	Type of Message: Error Cause: The column you specified for time-based aging does not exist. Impact: TimesTen could not perform the operation. User Action: Make sure the column used for time-based aging exists in your table. For more information, see CREATE TABLE or ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2982	Column column_name specified for time-based aging is not a timestamp or date column	Type of Message: Error Cause: The column used for time-based aging must be of type DATE, TT_DATE, TIMESTAMP, or TT_TIMESTAMP. Impact: TimesTen could not perform the operation. User Action: Redefine the table and specify the column used for time-based aging as type DATE, TT_DATE, TIMESTAMP, or TT_TIMESTAMP. For more information, see CREATE TABLE or ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2983	Cannot drop aging or change aging attribute of a table with no aging policy	Type of Message: Error Cause: You attempted to drop or change an aging attribute from a table that does not have a defined aging policy. Impact: The operation failed. User Action: Add the aging policy to your table and specify the desired attributes for the policy or make sure to choose the correct table for aging. For more information, see CREATE TABLE or ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2984	LRU aging does not have the specified attribute	Type of Message: Error Cause: You attempted to alter an LRU aging attribute that does not exist. Impact: TimesTen did not perform the operation. User Action: Check the valid attributes for LRU aging and retry the operation. For more information, see ttAgingLRUConfig in Oracle TimesTen In-Memory Database Reference.
2985	Cannot add aging policy to a materialized view table	Type of Message: Error Cause: You cannot specify an aging policy on a materialized view or on the detail tables of a materialized view. Impact: TimesTen did not add the aging policy. User Action: Redefine the materialized view without specifying an aging policy. For more information, see CREATE MATERIALIZED VIEW in Oracle TimesTen In-Memory Database SQL Reference.
2986	Detail table of materialized view cannot have aging policy	Type of Message: Error Cause: You attempted to specify an aging policy on the detail tables of a materialized view. Impact: TimesTen did not perform the operation. User Action: Redefine the materialized view, making sure not to specify detail tables that have an aging policy. For more information, see CREATE MATERIALIZED VIEW in Oracle TimesTen In-Memory Database SQL Reference.
2987	A temporary table cannot have an aging policy	Type of Message: Error Cause: You attempted to specify an aging policy on a temporary table. Impact: TimesTen did not perform the operation. User Action: Redefine the temporary table without the aging policy. For more information, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2988	Cannot add aging policy to a non-root table of a cache group	Type of Message: Error Cause: You attempted to specify aging on a child table of a cache group. Aging is supported on parent (root) tables only. Impact: TimesTen did not create or alter the cache group. User Action: Redefine the cache group without specifying aging on a child (non-root) table. For more information, see CREATE CACHE GROUP in Oracle TimesTen In-Memory Database SQL Reference.
2989	LRU aging policy is not allowed with autorefresh cache group	Type of Message: Error Cause: You attempted to specify an LRU aging policy on an autorefresh cache group. Impact: TimesTen did not create the cache group. User Action: Remove the LRU aging policy from the cache definition and retry the operation. For more information, see CREATE CACHE GROUP in Oracle TimesTen In-Memory Database SQL Reference.
2990	Cannot change aging attributes or add/drop aging policy of autorefresh cache group while cache agent is active	Type of Message: Error Cause: You attempted to add or drop aging from an autorefresh cache group while the cache agent was running. Impact: TimesTen did not change the cache group definition. User Action: If you wish to drop or add aging, first stop the cache agent. Then, add aging to or drop aging from the cache group and restart the agent. For more information, see CREATE CACHE GROUP in Oracle TimesTen In-Memory Database SQL Reference.
2991	Cannot combine aging duration with other aging policy	Type of Message: Error Cause: You attempted to use aging duration which is deprecated. Impact: TimesTen did not add aging to the table. User Action: If you wish to use aging, specify time-based or LRU aging for the tables of the cache group. For more information, see CREATE CACHE GROUP in Oracle TimesTen In-Memory Database SQL Reference.
2992	Cannot drop aging column	Type of Message: Error Cause: You attempted to drop the column that is used by time-based aging. Impact: TimesTen cannot drop the column. User Action: Drop the time-based aging policy first, then drop the column. For more information, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2993	Aging column cannot be nullable	Type of Message: Error Cause: You attempted to specify the time-based aging column as NULL. Impact: TimesTen did not perform the operation. User Action: Redefine the table making sure to specify NOT NULL for the time-based aging column. For more information, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2994	Parent table_name of table table_name has different aging policy: policy	Type of Message: Error Cause: You attempted to specify different aging policies for your parent and child tables. Impact: TimesTen did not perform the operation. User Action: Make sure the parent aging policy matches the child aging policy. For more information, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2995	Child table_name of table table_name has different aging policy: policy	Type of Message: Error Cause: You attempted to define an aging policy on a child table that does not match the policy on the parent table. Impact: TimesTen did not create or alter the table. User Action: Review the primary and foreign key definitions making sure that the aging policies match. For more information, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2996	Cannot start aging on table without aging policy	Type of Message: Error Cause: You cannot start aging on a table that does not have a defined aging policy. This could be due to you calling the ttAgingScheduleNow built-in procedure in which you specified a table that has no defined aging policy. Impact: TimesTen did not start aging on the table. User Action: To start aging on a table, you must first define an aging policy for the table. For more information, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference.
2997	Transparent load cannot be used with passthrough 3	Type of Message: Error Cause: You attempted to specify transparent load with a passthrough policy of 3. Impact: TimesTen did not perform the operation. User Action: Use a valid passthrough policy for the transparent load operation. For more information, see Setting a Passthrough Level in Oracle TimesTen In-Memory Database Cache Guide.
2998	Named constraint not found in table	Type of Message: Error Cause: You attempted to drop a foreign key that was not defined. Impact: TimesTen did not perform the operation. User Action: Run the ttISQL DESCRIBE command to review the table definition. For more information, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference or ttIsql in the Oracle TimesTen In-Memory Database Reference.
2999	Circular-referencing foreign keys are not allowed	Type of Message: Error Cause: You attempted to define a primary and foreign key relationship with circular referencing foreign keys. Impact: TimesTen did not create the primary and foreign key relationship. User Action: Redefine the primary and foreign key relationship making sure to avoid circular referencing. For more information, see CREATE TABLE in Oracle TimesTen In-Memory Database SQL Reference.

Errors 3000-3999

Error number	Error or warning message	Details
3000	self-referencing foreign keys are not allowed	Type of Message: Error Cause: You attempted to modify/add a foreign key that is referencing a column of same table. Impact: TimesTen cannot execute the SQL statement. User Action: Ensure that your statement does not include a foreign key that specifies self references (column of the same table) and retry the operation.
3001	Foreign key violation error	Type of Message: Error Cause: You attempted to perform an operation that violates a foreign key constraint. Impact: TimesTen cannot execute the SQL statement. User Action: Rewrite your DML statement to avoid foreign key constraint violation. For more information, see SQL Statements in Oracle TimesTen In-Memory Database SQL Reference.
3003	Table/Index is in use by a foreign key	Type of Message: Error Cause: You attempted to drop or modify a parent table or index that is referenced by a foreign key. Impact: TimesTen did not perform the operation. User Action: Drop the foreign key, and then drop the index.
3004	Foreign key column column_name has a type mismatch	Type of Message: Error Cause: You attempted to create foreign key columns that do not match the primary key columns in number, type, length, precision or scale. Impact: TimesTen cannot perform the operation. User Action: Modify your DDL statement and ensure that the foreign key columns match the primary key columns in number, type, length, precision or scale, and retry the operation.
3005	There is no unique index on the referenced columns for foreign key defined on table table_name	Type of Message: Error Cause: You attempted to create a foreign key referencing columns, which are not the referenced table's primary key and are not the columns in a unique index on that table. Impact: TimesTen cannot perform the operation. User Action: Create a primary key or unique index on the referenced columns of the referenced table, and then create the foreign key.
3006	System/Cached tables cannot be referenced by a foreign key	Type of Message: Error Cause: You attempted to create a foreign key on system or cache tables. Foreign key on system tables are not allowed. Foreign key on cached tables are not supported. Impact: TimesTen cannot perform the operation. User Action: None.
3007	Both foreign key function arguments are null	Type of Message: Error Cause: You called the ttForeignkKey built-in, which takes two arguments, and both of them are NULL. Impact: The SQL operation fails. User Action: Ensure that at least one of the arguments is not NULL.
3008	Scalar subquery returned more than one row	Type of Message: Error Cause: You issued a query that contained a SQL subquery that returns more than one row of information. Impact: TimesTen cannot perform the SQL operation. User Action: Rewrite your query so that the subquery returns a single row. Alternatively, modify your query to use a keyword (ANY, ALL, IN or NOT IN) with your subquery results. For more information, see Scalar subqueries in Oracle TimesTen In-Memory Database SQL Reference.
3009	Dropping an index used to enforce unique column constraint is not allowed	Type of Message: Error Cause: You attempted to drop an index used to force a unique constraint using a DROP INDEX statement. Impact: TimesTen cannot perform the SQL operation. User Action: Use ALTER TABLE DROP UNIQUE to drop the unique constraint.
3011	Duplicate columns in foreign key specification	Type of Message: Error Cause: You attempted to define a foreign key using duplicate column names. Impact: TimesTen did not perform the operation. User Action: Construct foreign key columns without using duplicate names.
3015	Cascade delete and non-cascade delete foreign keys cannot be mixed on paths leading to a table. The endpoints are tables table_name and table_name	Type of Message: Error Cause: You attempted to use both cascade delete and non-cascade delete foreign keys on paths leading to a table. Impact: TimesTen did not perform the operation. User Action: Use either cascade delete or non-cascade delete foreign keys on paths leading to a table.
3017	Child table table_name in a foreign key relationship with ON DELETE CASCADE must be replicated if its parent table table_name is replicated	Type of Message: Error Cause: When a primary key table is included in a replication scheme, its corresponding foreign key table must be included in the replication scheme, as well. This error is returned when an ON DELETE CASCADE operation is attempted on a foreign key table in a replication scheme, but the primary key table is not included in the replication scheme. Impact: This requirement prevents foreign key conflicts from occurring on the standby master tables when a cascade deletion occurs on the active master database. User Action: Ensure that if a child table with a foreign key defines ON DELETE CASCADE, then you must replicate any other table with a foreign key relationship to the child table. See Replicating Tables with Foreign Key Relationships in an Active Standby Pair in Oracle TimesTen In-Memory Database Replication Guide.
3018	Child table table_name in a foreign key relationship must be replicated if its parent table table_name is replicated	Type of Message: Error Cause: A foreign key table in a primary key/foreign key relationship is not being replicated. Make sure both or neither of the tables is in the replication scheme. Impact: This requirement prevents foreign key conflicts from occurring on the standby master tables when a cascade deletion occurs on the active master database. User Action: Ensure that if a child table with a foreign key defines ON DELETE CASCADE, then you must replicate any other table with a foreign key relationship to the child table. See Replicating Tables with Foreign Key Relationships in an Active Standby Pair in Oracle TimesTen In-Memory Database Replication Guide.
3019	Parent table table_name in a foreign key relationship with ON DELETE CASCADE must be replicated if its child table table_name is replicated	Type of Message: Error Cause: When a primary key table is included in a replication scheme, its corresponding foreign key table must be included in the replication scheme, as well. This error is returned when an ON DELETE CASCADE operation is attempted on a primary key table in a replication scheme, but the foreign key table is not included in the replication scheme. Impact: This requirement prevents foreign key conflicts from occurring on the standby master tables when a cascade deletion occurs on the active master database. User Action: Ensure that if a child table with a foreign key defines ON DELETE CASCADE, then you must replicate any other table with a foreign key relationship to the child table. See Replicating Tables with Foreign Key Relationships in an Active Standby Pair in Oracle TimesTen In-Memory Database Replication Guide.
3020	Parent table table_name in a foreign key relationship must be replicated if its child table table_name is replicated	Type of Message: Error Cause: A primary key table in a primary key/foreign key relationship is not being replicated. Make sure both or neither of the tables is in the replication scheme. Impact: This requirement prevents foreign key conflicts from occurring on the standby master tables when a cascade deletion occurs on the active master database. User Action: Ensure that if a child table with a foreign key defines ON DELETE CASCADE, then you must replicate any other table with a foreign key relationship to the child table. See Replicating Tables with Foreign Key Relationships in an Active Standby Pair in Oracle TimesTen In-Memory Database Replication Guide.
3021	LRU aging policy for a readonly cache group is allowed only if the cache group is dynamic	Type of Message: Error Cause: You have specified an LRU aging policy on a explicitly loaded cache group. Impact: TimesTen did not perform the operation. User Action: LRU aging is defined by default on dynamic cache groups. For more information, see ttAgingLRUConfig in Oracle TimesTen In-Memory Database Reference.
3022	Refresh cache group with a where clause is only allowed only if the cache group is not dynamic	Type of Message: Error Cause: You cannot execute the REFRESH CACHE GROUP command with a WHERE clause for dynamic cache groups. Impact: The SQL statement is not executed. User Action: For more information, see REFRESH CACHE GROUP in Oracle TimesTen In-Memory Database SQL Reference.
3023	Aging column must be in the initial partition; column column_name was added by ALTER TABLE	Type of Message: Error Cause: When you use the ALTER TABLE statement to add a column, the newly added column is located in a secondary partition. You cannot add a time-based aging policy on a column that is in the secondary partition. Impact: TimesTen cannot perform the SQL operation. User Action: Use ttMigrate -r -relaxedUpgrade to condense the secondary partition into a single partition. Once you condense the partitions, you can then set a time- based aging policy on the column. For more information on partitions, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
3025	Missing ORDER BY expression in the window specification	Type of Message: Error Cause: You attempted to specify a window specification without the ORDER BY clause for an analytic function. Impact: TimesTen cannot perform the SQL operation. User Action: Specify your function and include the ORDER BY clause.
3026	ORDER BY is not allowed with analytic aggregation with distinct	Type of Message: Error Cause: You attempted to specify both the DISTINCT qualifier and the ORDER BY clause for your analytic aggregate function. Impact: TimesTen cannot perform the SQL operation. User Action: Specify your function omitting either the DISTINCT qualifier or the ORDER BY clause.
3027	Windowing clause is not allowed with RANK/DENSE_RANK/ROW_NUMBER analytical functions	Type of Message: Error Cause: You attempted to use the windowing clause for the RANK or DENSE_RANK or ROW_NUMBER analytic functions. Impact: TimesTen cannot perform the SQL operation. User Action: Specify the function omitting the windowing clause.
3028	Invalid analytic window argument	Type of Message: Error Cause: You specified an incorrect start point or end point of your windowing clause in the analytic function. The start point and end point must evaluate to a positive numeric value and the start point value must be less than the end point value. Impact: TimesTen cannot perform the SQL operation. User Action: Check your start point and end point specifications and redefine your analytic function using the correct windowing clause specification.
3029	Invalid use of analytic function function_name	Type of Message: Error Cause: You did not specify the analytic function in the SELECT list of a query. Impact: TimesTen cannot perform the SQL operation. User Action: Specify the analytic function including the function in the SELECT list of your query.
3030	Argument specification error for this function	Type of Message: Error Cause: You attempted to specify an analytic function that does not accept function arguments. Impact: TimesTen cannot perform the SQL operation. User Action: Specify the function without the function arguments.
3031	Nested Analytical functions are not allowed	Type of Message: Error Cause: Your SQL statement contains nested analytic functions. Impact: TimesTen cannot perform the SQL operation. User Action: Specify a SQL statement without nested analytic functions. For more information on analytic functions, see Analytic functions in Oracle TimesTen In-Memory Database SQL Reference.
3039	The first argument of NULLIF cannot be NULL literal	Type of Message: Error Cause: You attempted to specify NULL as the first argument to the NULLIF function. Impact: TimesTen cannot perform the operation. User Action: Invoke your function without specifying NULL as the first argument.
3040	GROUPING function only supported with GROUP BY	Type of Message: Error Cause: You attempted to specify a grouping function such as GROUP_ID, GROUPING, or GROUPING_ID that was not within the GROUP BY clause. Impact: TimesTen cannot perform the SQL operation. User Action: Modify your query by specifying the grouping function as part of the GROUP BY clause.
3041	Number of groupings exceeds the maximum (2147483648)	Type of Message: Error Cause: You specified a number of groupings in the GROUP BY clause that exceeds the maximum limit of 2147483648. Impact: TimesTen cannot perform the SQL operation. User Action: Modify your clause by reducing the number of groupings and retry the operation.
3050	Subquery is not allowed in the RETURNING clause	Type of Message: Error Cause: You specified a subquery in a RETURNING clause. Impact: TimesTen cannot perform the SQL operation. User Action: Modify your query and retry the operation.
3051	Number of returning expressions(number) should match the number of arguments in the INTO clause(number)	Type of Message: Error Cause: You attempted to use an INTO clause where the number of expressions and arguments do not match. Impact: TimesTen cannot perform the SQL operation. User Action: Modify your query and retry the operation.
3052	Rownum is not allowed in the RETURNING clause	Type of Message: Error Cause: You specified rownum in a RETURNING clause. This is not supported. Impact: TimesTen cannot perform the SQL operation. User Action: Modify your query and retry the operation.
3053	Sequence references are not allowed in the RETURNING clause	Type of Message: Error Cause: You specified a sequence reference in a RETURNING clause. This is not supported. Impact: TimesTen cannot perform the SQL operation. User Action: Modify your query and retry the operation.
3054	Out parameter (:parameter_name) in the INTO clause is referenced more than once in the SQL statement	Type of Message: Error Cause: You specified a parameter that is referenced more than once in the INTO clause. Impact: TimesTen cannot perform the SQL operation. User Action: Remove one of the references from your INTO clause and retry the operation.
3055	Error in handling the output parameters in the INTO clause:(error_message)	Type of Message: Error Cause: There is an error when processing the output values in the specified INTO clause. Impact: TimesTen cannot perform the SQL operation. User Action: Review the provided error message for more information on the failure and retry the operation.
3056	Aggregate functions are not allowed in the RETURNING clause	Type of Message: Error Cause: You specified an aggregate function in a RETURNING clause. This is not supported. Impact: TimesTen cannot perform the SQL operation. User Action: Remove the aggregate function from the clause and retry the operation.
3057	Foreign key column count mismatch	Type of Message: Error Cause: You attempted to create a table while the number of foreign key columns is not equal to the number of primary key columns in the referenced table. Impact: TimesTen cannot create the table. User Action: Ensure that the number of foreign key columns is equal to the number of primary key columns in the referenced table.
3070	Cannot create a synonym with same name as object	Type of Message: Error Cause: You attempted to create a synonym for an object with the same name as the synonym. Impact: TimesTen cannot create the synonym. User Action: Ensure the name of the synonym is not the same name as that of another object. See CREATE SYNONYM in Oracle TimesTen In-Memory Database SQL Reference and Understanding Synonyms in the Oracle TimesTen In-Memory Database Operations Guide for details.
3071	Synonym synonym does not exist	Type of Message: Error Cause: You attempted to drop a private synonym that does not exist. The synonym may have been previously dropped or may have never existed. Impact: TimesTen cannot drop the private synonym. User Action: Ensure the private synonym exists before attempting to drop it. See DROP SYNONYM in Oracle TimesTen In-Memory Database SQL Reference and Understanding Synonyms in the Oracle TimesTen In-Memory Database Operations Guide for details.
3072	Public synonym synonym does not exist	Type of Message: Error Cause: You attempted to drop a public synonym that does not exist. The public synonym may have been previously dropped or may have never existed. Impact: TimesTen cannot drop the public synonym. User Action: Ensure the public synonym exists before attempting to drop it. See DROP SYNONYM in Oracle TimesTen In-Memory Database SQL Reference and Understanding Synonyms in the Oracle TimesTen In-Memory Database Operations Guide for details.
3073	Public synonym cannot have a schema name	Type of Message: Error Cause: You attempted to create a public synonym with a schema name. Impact: TimesTen cannot create the synonym. User Action: Do not preface the public synonym name with a schema name. See CREATE SYNONYM in Oracle TimesTen In-Memory Database SQL Reference and Understanding Synonyms in the Oracle TimesTen In-Memory Database Operations Guide for details.
3074	Looping chain of synonyms	Type of Message: Error Cause: You attempted to create a chain of synonyms that resulted in a circular reference. You can create a synonym to point to another synonym. But, if two or more synonyms are created to point to each other, this synonym chain forms a loop. Impact: TimesTen cannot complete the operation. User Action: Correct the synonyms to remove the loop and retry the operation.
3076	Using synonyms in this statement is not implemented	Type of Message: Error Cause: You attempted to use synonyms in a statement that does not support synonyms. Impact: TimesTen cannot complete the operation. User Action: Do not use synonyms in this statement.
3077	Cannot resolve synonym synonym to any existing object	Type of Message: Error Cause: You attempted to use a synonym that points to a non-existing object. Impact: TimesTen cannot complete the operation. User Action: Ensure that your synonym points to an object that exists and retry the operation.
3078	Circular view definition encountered	Type of Message: Error Cause: You attempted to create a view that uses a synonym inside its SELECT statement and that references itself. Impact: TimesTen cannot perform the operation. User Action: Check the view definitions, remove any circular references, and retry the operation.
3079	Creating synonyms in schema schema_name is not allowed	Type of Message: Error Cause: You attempted to create synonyms in restricted schemas, such as SYS, GRID, and TTREP. Impact: TimesTen cannot complete the operation. User Action: Specify a different schema to contain the synonyms and retry the operation. For more information, See CREATE SYNONYM in Oracle TimesTen In-Memory Database SQL Reference.
3080	Cannot create a public synonym with the same name as TimesTen built-in procedure procedure_name	Type of Message: Error Cause: You attempted to create a public synonym with the same name as a TimesTen built-in procedure. Impact: TimesTen cannot complete the operation. User Action: Ensure your public synonym does not use the same name as a TimesTen built-in procedure and retry the operation.
3096	Object object_name not found	Type of Message: Error Cause: You attempted to execute a SQL statement that references a database object that does not exist. Impact: TimesTen cannot complete the operation. User Action: Specify the name of an existing database object and retry the operation.
3097	A object_type with this name (object_name) already exists	Type of Message: Error Cause: You attempted to create an object with a name that is already in use in the database. Impact: TimesTen cannot complete the operation. User Action: Specify a unique name for the indicated object and retry the operation.
3098	User user_name does not exist	Type of Message: Error Cause: You attempted to create a database object for a schema that does not exist. Impact: TimesTen cannot execute the SQL statement. User Action: Create a database object for an existing schema.
3099	Object object_name does not exist in element element_id	Type of Message: Error Cause: TimesTen is unable to find the specified SQL object in the specified element. Impact: TimesTen cannot execute the SQL statement. User Action: Contact TimesTen Customer Support.
3100	Outer join operator (+) in this OR expression is not supported	Type of Message: Error Cause: You attempted to use the OUTER JOIN operator (+) either in an OR condition (for example, x1(+)=1 OR x1(+)=2...) or in an IN condition (for example, x1(+)IN (1,2,3)). Neither of these uses are supported. Impact: TimesTen cannot execute the SQL statement. User Action: Do not use the OUTER JOIN operator (+) in OR or in IN conditions.
3101	Outer join operator(+) not allowed in select list, order by or group by clause	Type of Message: Error Cause: You attempted to use the OUTER JOIN operator (+) in a SELECT list (for example, SELECT x1(+)FROM...) or in an ORDER BY clause (for example, ORDER BY x1(+)) or in a GROUP BY clause (for example: GROUP BY x1(+)). Neither of these uses are supported. Impact: TimesTen cannot execute the SQL statement. User Action: Do not use the OUTER JOIN operator (+) in a SELECT list, in an ORDER BY clause, or in a GROUP BY clause.
3102	A table may be outer joined with at most one outer table	Type of Message: Error Cause: You attempted to perform an outer join to the same table from more than one table. For example, T1.X1(+) = T2.X2 AND T2.X3(+)=T1.X1. Table T1 was outer joined with both T1 and T2. This operation is not supported. Impact: TimesTen cannot execute the SQL statement. User Action: Modify your SQL statement to outer join a table with only one other table, and then retry the operation.
3103	Two tables cannot be outer joined together	Type of Message: Error Cause: A cycle of OUTER JOIN was found, where each table is both an inner and an outer table. For example: T1.X1(+) = T2.X2 AND T3.X3(+)=T1.X1. This is not supported. Impact: TimesTen cannot execute the SQL statement. User Action: Modify your SQL statement so that you do not outer join both tables together, and then retry the operation.
3104	A predicate may reference only one outer-joined table	Type of Message: Error Cause: You attempted to execute a SQL statement that joins two tables and both tables were outer joined. For example: T1.X1(+) + T2.X2(+)=T3.X3. In this case, both tables T1 and T2 are inner tables. This is not supported. Impact: TimesTen cannot execute the SQL statement. User Action: Modify your SQL statement and ensure that only one of the tables is an outer join table and retry the operation.
3105	In the First or Rows Clause the number must be greater than 0	Type of Message: Error Cause: You passed a negative or zero value for the FIRST N clause. Impact: TimesTen cannot execute the SQL statement. User Action: Use a positive value for the FIRST N clause and retry the operation.
3106	FIRST keyword cannot be used in subquery	Type of Message: Error Cause: You attempted to use the FIRST keyword in a subquery. This keyword can be used only in the main query. TimesTen does not support the FIRST keyword in subqueries. Impact: TimesTen cannot execute the SQL statement. User Action: Modify your subquery statement and retry the operation.
3108	Outer join operator (+) cannot be used in query that specifies joined table	Type of Message: Error Cause: You specified a joined table and an outer join operator (+) in the same query. Impact: TimesTen cannot execute the SQL statement. User Action: Do not use an outer join operator in a query that specifies a joined table.
3110	Expression expression has no name	Type of Message: Error Cause: You did not specify a name for a column in the select list of a CREATE VIEW statement. Impact: TimesTen cannot execute the SQL statement. User Action: Specify an expression name and retry the operation.
3111	Column name column_name specified more than once	Type of Message: Error Cause: You specified a column name that already exists. Impact: TimesTen cannot execute the SQL statement. User Action: Specify a unique column name and retry the operation.
3112	Cannot drop view table table_name; please use DROP VIEW instead	Type of Message: Error Cause: You attempted to drop a table that is a view. Impact: TimesTen cannot execute the SQL statement. User Action: Use the DROP VIEW statement to drop this table.
3113	Cannot drop tables with defined materialized views: the view view_name refers to table_name	Type of Message: Error Cause: You attempted to drop a detail table that has an associated view. You cannot drop a detail table without first dropping the view. Impact: TimesTen cannot execute the SQL statement. User Action: Drop the view and then retry the operation. See Working with Materialized Views in Oracle TimesTen In-Memory Database Operations Guide.
3114	Cannot alter view tables	Type of Message: Error Cause: You attempted to alter a view. Impact: TimesTen cannot execute the SQL statement. User Action: To alter a view, drop the view using the DROP VIEW statement, and then create a new view using the CREATE MATERIALIZED VIEW statement. See Working with Materialized Views in Oracle TimesTen In-Memory Database Operations Guide.
3115	Cannot drop columns referenced in materialized views	Type of Message: Error Cause: You specified a column that is referenced in a view. Impact: TimesTen cannot execute the SQL statement. User Action: As long as the view exists, you cannot drop this column. See Working with Materialized Views in Oracle TimesTen In-Memory Database Operations Guide.
3117	View SQL must be less than number bytes long	Type of Message: Error Cause: The view's select text is bigger than the maximum size of 400*1024 bytes. Impact: TimesTen cannot execute the SQL statement. User Action: Ensure that the view's select text does not exceed the maximum size allowed.
3118	View view_name already exists	Type of Message: Error Cause: You attempted to create a view using the CREATE MATERIALIZED VIEW statement with a name that is already in use. Impact: TimesTen cannot execute the SQL statement. User Action: Rename your view and retry the operation. Alternatively, drop the existing view and create a new one.
3119	More than number views reference table table_name	Type of Message: Error Cause: In your CREATE MATERIALIZED VIEW statement, you specified a detail table that already has 100 views referencing it. Impact: TimesTen cannot execute the SQL statement. User Action: Review the views that reference this table and drop the views that are not required. Then, retry the operation. For more information on the CREATE MATERIALIZED VIEW statement , see CREATE MATERIALIZED VIEW in Oracle TimesTen In-Memory Database SQL Reference.
3120	View view_name does not exist	Type of Message: Error Cause: You attempted to drop a non-existent view using the DROP VIEW statement. Impact: TimesTen cannot execute the SQL statement. User Action: Examine the views and drop a view that exists. For more information on the DROP VIEW statement , see DROP VIEW in Oracle TimesTen In-Memory Database SQL Reference.
3121	A cache group table table_name cannot be referenced in a materialized view	Type of Message: Error Cause: Your CREATE MATERIALIZED VIEW statement specified a cache group table as a detail table. This is not supported. Impact: TimesTen cannot execute the SQL statement. User Action: Do not reference cache group tables in your CREATE MATERIALIZED VIEW statement. For more information, see CREATE MATERIALIZED VIEW in Oracle TimesTen In-Memory Database SQL Reference.
3123	Foreign keys on view tables are not allowed	Type of Message: Error Cause: You attempted to define foreign keys on materialized views. This operation is not allowed. Impact: TimesTen cannot execute the SQL statement. User Action: Do not define a foreign key if the referencing or referenced table is a materialized view. For more information, see CREATE MATERIALIZED VIEW in Oracle TimesTen In-Memory Database SQL Reference.
3124	Cannot create a view that references a system table	Type of Message: Error Cause: Your CREATE MATERIALIZED VIEW statement specified a system table as a detail table. This is not supported. Impact: TimesTen cannot execute the SQL statement. User Action: Do not reference system tables or views in your CREATE MATERIALIZED VIEW statement.
3125	View definition was too long. Could not store the definition in the system tables.	Type of Message: Error Cause: You attempted to create a materialized view, but the view definition exceeded the maximum size of 400*1024 bytes. Impact: TimesTen cannot store the definition in the system tables. User Action: Modify your materialized view definition query so that it does not exceed the maximum size allowed.
3128	Invalid size of column name list	Type of Message: Error Cause: You specified a column name list for a derived table or non-materialized view, but its size does not match the number of projected columns. Impact: TimesTen cannot execute the SQL statement. User Action: Specify a number of projected columns that matches the size of the column name list.
3129	Invalid column name for view	Type of Message: Error Cause: You specified a column name that is invalid. Names in the column name list of a derived table or view cannot have table name specification. Impact: TimesTen cannot execute the SQL statement. User Action: Specify a column name that is valid and retry the operation.
3130	Derived table name table_name is not unique among all based/viewed/derived table names	Type of Message: Error Cause: You specified a derived table name that is not unique. A derived table name must be unique among the names of all derived tables, base tables and views referenced in the same query. Impact: TimesTen cannot execute the SQL statement. User Action: Specify a derived table name that is unique and retry the operation.
3131	View view_name is not a materialized view; please use DROP VIEW instead	Type of Message: Error Cause: You attempted to use the DROP MATERIALIZED VIEW statement to drop a non-materialized view. Impact: TimesTen cannot execute the SQL statement. User Action: Use the DROP VIEW statement. For more information, see DROP VIEW in Oracle TimesTen In-Memory Database SQL Reference.
3132	A materialized view cannot reference a regular view	Type of Message: Error Cause: You referenced a non-materialized view in the definition of a materialized view. Impact: TimesTen cannot execute the SQL statement. User Action: Do not use non-materialized views to define a materialized view.
3133	Cannot truncate tables with defined materialized views: the view view_name refers to table_name	Type of Message: Error Cause: You attempted to truncate a table, but the table has a materialized view defined on it. Impact: TimesTen cannot execute the SQL statement. User Action: Either drop the materialized view or do not use the TRUNCATE statement. Consider using the DELETE statement. For more information on the DELETE statement, see DELETE in Oracle TimesTen In-Memory Database SQL Reference.
3134	Cannot truncate materialized view: view_name	Type of Message: Error Cause: You attempted to truncate a materialized view. This operation is not supported. Impact: TimesTen cannot execute the SQL statement. User Action: Do not use the TRUNCATE statement to delete rows. Consider using the DELETE statement to delete the rows from the table. For more information on the DELETE statement, see DELETE in Oracle TimesTen In-Memory Database SQL Reference.
3135	Cannot truncate table: table_name; child table: table_name is not empty. Please execute truncate on child table first	Type of Message: Error Cause: You attempted to truncate a parent table, but the child table was not empty. Impact: TimesTen cannot execute the SQL statement. User Action: Consider truncating the child table first, and then truncate the parent table. For more information on the TRUNCATE TABLE statement, see TRUNCATE TABLE in Oracle TimesTen In-Memory Database SQL Reference.
3136	Cannot truncate temp table: table_name; Please use delete	Type of Message: Error Cause: You attempted to truncate a global temporary table. This operation is not supported. Impact: TimesTen cannot execute the SQL statement. User Action: Use the DELETE statement to delete the rows from the table. For more information on the DELETE statement, see DELETE in Oracle TimesTen In-Memory Database SQL Reference.
3137	Cannot insert into a truncated table in an uncommitted transaction	Type of Message: Error Cause: An in-progress transaction is attempting to insert rows into a table that has already been truncated. Impact: TimesTen cannot execute the SQL statement. User Action: Commit the transaction with the TRUNCATE statement, and then execute the INSERT operation. For more information on the INSERT statement, see INSERT in Oracle TimesTen In-Memory Database SQL Reference.
3138	Cannot delete from a truncated table in an uncommitted transaction	Type of Message: Error Cause: An in-progress transaction is attempting to delete rows from a table that has already been truncated. Impact: TimesTen cannot execute the SQL statement. User Action: Commit the truncate transaction, and then execute the DELETE operation.
3139	Cannot update a truncated table in an uncommitted transaction	Type of Message: Error Cause: An in-progress transaction is attempting to update rows from a table that has already been truncated. Impact: TimesTen cannot execute the SQL statement. User Action: Commit the truncate transaction, and then execute the UPDATE operation.
3140	Cannot alter to change hash page a truncated table in an uncommitted transaction	Type of Message: Error Cause: An in-progress transaction is attempting to alter the hash pages on a table that has already been truncated. Impact: TimesTen cannot execute the SQL statement. User Action: Commit the truncate transaction, and then execute the ALTER operation.
3141	Cannot alter to add/drop column a truncated table in an uncommitted transaction	Type of Message: Error Cause: An in-progress transaction is attempting to add or drop a column on a table that has already been truncated. Impact: TimesTen cannot execute the SQL statement. User Action: Commit the truncate transaction, and then DROP or ADD the column.
3143	Cannot drop Materialized View Log table table_name with Drop Table. Use Drop Materialized View Log On view_log	Type of Message: Error Cause: You attempted to drop a materialized view log table using the DROP TABLE statement. Impact: TimesTen cannot execute the SQL statement. User Action: Use the DROP MATERIALIZED VIEW LOG SQL statement and retry the operation.
3144	Cannot drop table table_name with defined Materialized View Log. First drop materialized view log	Type of Message: Error Cause: You attempted to drop a table with a defined materialized view log. Impact: TimesTen cannot execute the SQL statement. User Action: Drop the materialized view log before dropping the table. Use the DROP MATERIALIZED VIEW LOG SQL statement.
3145	view_name is not an Asynchronous Materialized View	Type of Message: Error Cause: The view name that you provided in the REFRESH MATERIALIZED VIEW statement is not an asynchronous materialized view. Impact: TimesTen cannot execute the SQL statement. User Action: Verify the view name and retry the operation.
3146	Column table_name.column_name not found in the Materialized View Log	Type of Message: Error Cause: Your CREATE MATERIALIZED VIEW with REFRESH FAST statement specifies a column that is not in the materialized view log. Impact: TimesTen cannot execute the SQL statement. User Action: Drop the materialized view log, then re-create the materialized view log with all the desired columns. If there are any asynchronous materialized views that depend on this materialized view log, first drop all those materialized views, and then drop the materialized view log.
3147	Key Column or rowid table_name.column_name not found in the select list or it is a part of an expression	Type of Message: Error Cause: Your CREATE MATERIALIZED VIEW with REFRESH FAST statement does not include all the primary key columns or ROWIDs of all the detail tables. Impact: TimesTen cannot execute the SQL statement. User Action: Ensure that the CREATE MATERIALIZED VIEW with REFRESH FAST statement includes all the primary key columns or ROWIDs of all the detail tables. If the primary key column is an argument to a function such as UPPER, it does not satisfy this rule.
3148	No Primary Key in the detail table table_name. Specify ROWID option for the Materialized View Log	Type of Message: Error Cause: The CREATE MATERIALIZED VIEW LOG statement has the primary key clause (either explicitly coded or by default). However, the detail table does not have a primary key. Impact: TimesTen cannot execute the SQL statement. User Action: Use the ROWID clause in the CREATE MATERIALIZED VIEW LOG statement.
3149	Insert/delete/update/truncate operations not allowed in a Materialized View Log Table	Type of Message: Error Cause: You attempted to perform SQL operations in a Materialized View Log table that change the data in the table. These operations are not allowed on Materialized View Log tables. Impact: TimesTen cannot execute the SQL statement. User Action: Do not perform INSERT, DELETE, UPDATE, or TRUNCATE operations in a Materialized View Log table.
3150	Refresh name is not accepted. System is busy. Try again	Type of Message: Error Cause: You attempted to perform a refresh operation while the system was busy. Only one refresh request can be processed at any given time. Impact: TimesTen cannot execute the SQL statement. User Action: Retry the operation.
3151	Asyncmv Thread encountered error while refreshing the view view_name. Check the Daemon Log	Type of Message: Error Cause: An error was encountered by the asynchronous materialized view daemon thread while refreshing the materialized view. Impact: The refresh failed. User Action: Check the error message on the daemon log. If the error is due to a lock conflict, you can retry the refresh statement. If it is due to some other internal error, contact TimesTen Customer Support.
3152	Refresh Interval of 0 is not allowed for Asynchronous Materialized View with refresh mode Complete	Type of Message: Error Cause: You attempted to refresh an asynchronous materialized view, but entered a refresh interval of 0. Impact: TimesTen cannot execute the SQL statement. User Action: Ensure that the refresh interval value is a positive integer and retry the operation.
3153	There is no materialized view log on table table_name	Type of Message: Error Cause: You issued a DROP MATERIALIZED VIEW LOG statement on the indicated table. However, there is no materialized view log on that table. Impact: TimesTen cannot execute the SQL statement. User Action: Verify that the indicated table is the one you want to use. If not, specify the correct table and retry the operation.
3154	A materialized view log already exists on table table_name	Type of Message: Error Cause: You issued a CREATE MATERIALIZED VIEW LOG statement on the indicated table. However, there is a materialized view log on that table already. Impact: TimesTen cannot execute the SQL statement. User Action: None.
3155	Cannot drop column column_name that is included in the corresponding Materialized View Log	Type of Message: Error Cause: You attempted to drop the specified column. You cannot drop a column from a detail table if the column is in the corresponding materialized view log. Impact: TimesTen cannot execute the SQL statement. User Action: Verify that the indicated column is the one you want to drop.
3156	Cannot create a materialized view on a materialized view log	Type of Message: Error Cause: You attempted to create a materialized view on a materialized view log table. This operation is not supported. Impact: The materialized view was not created. User Action: Check the FROM list of the CREATE MATERIALIZED VIEW statement to ensure that no materialized log views are listed, and then retry the operation.
3157	Cannot drop Materialized View Log on a detail table with defined Asynchronous Materialized View. View view_name refers to the detail table	Type of Message: Error Cause: You attempted to drop a materialized view log that has a dependent asynchronous materialized view. The materialized view log cannot be dropped if there is an asynchronous materialized view that depends on the log for refreshing. Impact: The materialized view log was not dropped. User Action: First drop the dependent asynchronous materialized view, and then drop the materialized view log.
3158	Cannot create a materialized view log on a system table	Type of Message: Error Cause: You attempted to create a materialized view log on a system table by executing CREATE MATERIALIZED VIEW LOG ON system_table. This operation is not allowed. Impact: The materialized view log is not created. User Action: Specify a different table name and retry the operation.
3159	SELECT not allowed on invalid materialized view view_name	Type of Message: Error Cause: When a materialized view is invalid, the owner of the view does not have SELECT privileges on every detail table referenced by that view. Impact: TimesTen cannot execute the SQL statement. User Action: To fix an invalid materialized view, re-grant SELECT privileges on every detail table to the view owner (or grant higher-level privileges such as SELECT ANY TABLE or ADMIN). Once the privileges are granted, drop the materialized view, and then re-create it.
3160	REFRESH not allowed on invalid materialized view view_name	Type of Message: Error Cause: When a materialized view is invalid, the table cannot be refreshed and the owner of the view does not have SELECT privileges on every detail table referenced by that view. Impact: TimesTen cannot execute the SQL statement. User Action: To fix an invalid materialized view, re-grant SELECT privileges on every detail table to the view owner (or grant higher-level privileges such as SELECT ANY TABLE or ADMIN). Once the privileges are granted, drop the materialized view and then re-create it.
3200	Sequence increment by value cannot be 0	Type of Message: Error Cause: You specified a sequence increment value of 0. Impact: TimesTen cannot execute the SQL statement. User Action: Specify a sequence increment option greater than 0 and retry the operation.
3201	Sequence cache has not been allocated	Type of Message: Error Cause: This is an internal error. Impact: TimesTen cannot execute the SQL statement. User Action: Contact TimesTen Customer Support.
3202	Invalid max value. Possible reasons: maximum/minimum limit, or max < min	Type of Message: Error Cause: You specified a CREATE SEQUENCE statement with a value of the MAXVALUE parameter that is lower than or equal to the value specified for the MINVALUE parameter. Impact: TimesTen cannot create the sequence object. User Action: Specify a value for the MAXVALUE parameter that is greater than the value specified for the MINVALUE parameter and retry the CREATE SEQUENCE statement. For more information on the CREATE SEQUENCE statement, see CREATE SEQUENCE in Oracle TimesTen In-Memory Database SQL Reference.
3204	Sequence sequence_name not found	Type of Message: Error Cause: The specified sequence object does not exist. Impact: TimesTen cannot perform any operation with the specified sequence object name. User Action: Verify the sequence object name and retry the operation.
3205	A table or sequence with this name already exists.	Type of Message: Error Cause: You specified a sequence object name or table object name that already exists. Impact: TimesTen cannot create a sequence object or table object with the specified identifier. User Action: Select a different name for the sequence object or table object and retry the operation.
3206	CURRVAL or NEXTVAL not allowed in select with distinct, aggregate function, group by or order by	Type of Message: Error Cause: The specified sequence value CURRVAL or NEXTVAL is not allowed in your statement. The use of a sequence is limited. Impact: TimesTen cannot perform the operation. User Action: Do not use CURRVAL or NEXTVAL in a SELECT statement with the DISTINCT operator, or in aggregate functions in a GROUP BY clause or an ORDER BY clause in a SELECT statement. For more information, see CREATE SEQUENCE in Oracle TimesTen In-Memory Database SQL Reference.
3207	CURRVAL or NEXTVAL not allowed in subquery of update, delete or select	Type of Message: Error Cause: The specified sequence value CURRVAL or NEXTVAL is not allowed in your statement. The use of a sequence is limited. Impact: TimesTen cannot perform the operation. User Action: Do not use CURRVAL or NEXTVAL in a subquery of an UPDATE, DELETE or SELECT statement. References to CURRVAL and NEXTVAL are allowed in main query statements. For more information, see CREATE SEQUENCE in Oracle TimesTen In-Memory Database SQL Reference.
3208	CURRVAL or NEXTVAL not allowed in where clause	Type of Message: Error Cause: The specified sequence value CURRVAL or NEXTVAL is not allowed in your statement. The use of a sequence is limited. Impact: TimesTen cannot perform the operation. User Action: Do not use CURRVAL or NEXTVAL in the WHERE clause in the SELECT, UPDATE or CREATE VIEW SQL statements. However, CURRVAL is allowed in the SELECT WHERE clause. For more information, see CREATE SEQUENCE in Oracle TimesTen In-Memory Database SQL Reference.
3209	CURRVAL or NEXTVAL is not supported in views	Type of Message: Error Cause: The specified sequence value CURRVAL or NEXTVAL is not supported in your statement. Impact: TimesTen cannot perform the operation. User Action: Do not use CURRVAL or NEXTVAL in a VIEW statement. For more information on sequences, see CREATE SEQUENCE in Oracle TimesTen In-Memory Database SQL Reference.
3210	Sequence max/min limit has been reached	Type of Message: Error Cause: The value in the sequence has already reached its maximum or minimum limit. This occurs when the CYCLE option is not turned on for the sequence, and the minimum or maximum has been reached. Impact: TimesTen cannot complete the operation. User Action: Use the CYCLE parameter in your statement to allow the sequence number generator to continue generating numbers after it reaches the maximum or minimum value. For more information, see CREATE SEQUENCE in Oracle TimesTen In-Memory Database SQL Reference.
3211	CURRVAL may not be referenced before NEXTVAL in this session	Type of Message: Error Cause: You attempted to reference CURRVAL before NEXTVAL for a sequence in your session. Impact: TimesTen cannot complete the operation. User Action: Before you use CURRVAL for a sequence in your session, you must first initialize the sequence with NEXTVAL. For more information on sequences, see CREATE SEQUENCE in Oracle TimesTen In-Memory Database SQL Reference.
3212	Failed to get the NEXTVAL	Type of Message: Error Cause: Possible causes for this error message are: The application cannot get the next value of the sequence from the cache because of an update problem or lock timeout. There is a problem in posting the NEXTVAL in the environment due to a memory allocation problem. The application is adding the NEXTVAL to the session context. Impact: TimesTen is unable to obtain a NEXTVAL. User Action: Check if temporary heap space is available and retry the failed statement.
3214	An error occurred while adding sequence value info to context	Type of Message: Error Cause: An internal error occurred while trying to add a sequence value into the context, possibly because of a memory allocation failure. Impact: TimesTen cannot perform the operation. User Action: Contact TimesTen Customer Support.
3215	An error occurred while cleaning up sequence cache during rollback.	When a rollback is performed, TimesTen clears up the cached sequences appropriately. An error is reported when the cleanup is not successful.
3221	Invalid statistics information: error_number.	Type of Message: Error Cause: You passed invalid or incorrectly formatted statistics information to the ttOptSetColIntvlStats built-in procedure. The error_number describes the specific problem. Impact: TimesTen cannot complete the operation. User Action: Review the error_number and fix the format of your ttOptSetColIntvlStats built-in procedure. For a description of the correct format, see ttOptSetColIntvlStats in Oracle TimesTen In-Memory Database Reference.
3222	Estimate statistics on owner_name.table_name failed due to concurrent operations; try again	Type of Message: Error Cause: Possible causes for this error message are: The ttOptEstimateStats built-in procedure may throw this error when there are concurrent transactions, which makes it difficult to estimate statistics. There are many rows are deleted in a concurrent transaction. The table listed is the one on which the statistics are being updated. Impact: TimesTen cannot complete the operation. User Action: Retry the operation.
3230	Another session changed the enhanced write concurrency mode while this session was waiting for the mode transition to complete	Type of Message: Error Cause: The enhanced write concurrency mode was changed by another session before the mode transition completed. Impact: The enhanced write concurrency mode transition started but did not complete. User Action: Ensure that other sessions have completed the transition of the enhanced write concurrency mode. Then, retry changing the mode of the ttDbWriteConcurrencyModeSet built-in procedure.
3231	You must first call function_name before you can switch from mode current_mode to mode specified_mode	Type of Message: Error Cause: You attempted to change the enhanced write concurrency mode from current_mode to specified_mode. Impact: The enhanced write concurrency mode cannot be changed. User Action: Call the function that the error message specifies. Then, retry changing the mode of the ttDbWriteConcurrencyModeSet built-in procedure.
3232	Invalid value_type value: value	Type of Message: Error Cause: You specified an invalid parameter value. Impact: The parameter changes you specified cannot be completed. User Action: Specify valid parameter values and retry calling the built-in procedure.
3233	Failed to wait for a SQL command to complete that was not compiled in write concurrency mode mode	Type of Message: Error Cause: The ttDbWriteConcurrencyModeSet built-in procedure could not acquire a lock. A common cause for this is that there is a long running SQL statement. Impact: The enhanced write concurrency mode transition started and will continue until all SQL statements in transition are executed. The ttDbWriteConcurencyModeSet built-in procedure cannot wait because it could not acquire a lock. User Action: Use the ttXactAdmin utility to check if there is SQL statement blocking the lock acquisition for the ttDbWriteConcurencyModeSet built-in procedure. If there is a SQL statement blocking the lock acquisition, wait for the SQL statement to finish executing. Alternatively, consider terminating the SQL statement. For more information about using the ttXactAdmin utility, see Using the ttXactAdmin utility in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
3234	Waiting for mode transition on active SQL commands prepared or executed in this connection would never finish	Type of Message: Error Cause: You attempted to change the enhanced write concurrency mode in a transaction with active SQL statements. Impact: The enhanced write concurrency mode cannot be changed. User Action: Commit the current transaction. Then, retry changing the mode of the ttDbWriteConcurrencyModeSet built-in procedure.
3235	Waiting for mode transition on SQL commands with open cursors in this connection would never finish	Type of Message: Error Cause: You attempted to change the enhanced write concurrency mode in a transaction with open cursors. Impact: The enhanced write concurrency mode cannot be changed. User Action: Close the open cursors and commit the current transaction. Then, retry changing the mode of the ttDbWriteConcurrencyModeSet built-in procedure.
3236	Waiting for SQL commands to transition cannot be done with database level locking	Type of Message: Error Cause: You attempted to change the enhanced write concurrency mode in a database with database level locking. Impact: The enhanced write concurrency mode cannot be changed. User Action: Consider disabling database level locking with the ttLockLevel built-in procedure. Then, retry changing the mode of the ttDbWriteConcurrencyModeSet built-in procedure. For more information on database level locks, see Locking Granularities in Oracle TimesTen In-Memory Database Operations Guide. Alternatively, consider setting the wait parameter of the ttDbWriteConcurrencyModeSet built-in procedure to 0. Then, retry changing the mode of the ttDbWriteConcurrencyModeSet built-in procedure.
3240	Built-in stream has no result and therefore cannot be used in the FROM clause of a SELECT statement	Type of Message: Error Cause: You attempted a SELECT statement while specifying in the FROM clause a built-in with no results. The specified built-in cannot be used. Impact: TimesTen cannot perform the operation. User Action: None.
3241	Built-in specified in the FROM clause of a SELECT statement cannot update any value	Type of Message: Error Cause: You attempted a SELECT statement while specifying in the FROM clause a built-in that attempts to update one or more parameters. The specified built-in cannot be used. Impact: TimesTen cannot perform the operation. User Action: None.
3300	Type_name is not a valid type name; use type_name instead	Type of Message: Error Cause: You attempted to use a type name that is not valid in the current type mode. Impact: TimesTen cannot perform the operation. User Action: Use the suggested name instead and retry the operation.
3301	Type mode must be set to Oracle to use this feature	Type of Message: Error Cause: Only databases that have the TypeMode attribute set to Oracle Database type (TypeMode=0; the default) can contain cache groups. The TypeMode of the database cannot be changed after creation. Impact: TimesTen cannot perform the operation. User Action: To use cache groups, recreate the database with Oracle database type mode.
3304	Foreign key definition is not allowed for CREATE TABLE AS SELECT	Type of Message: Error Cause: You specified a foreign key clause in your CREATE TABLE AS SELECT statement. This operation is not allowed. Impact: TimesTen cannot perform the operation. User Action: Remove the foreign key clause from your statement or create a foreign key using the ALTER TABLE statement. For more information, see ALTER TABLE in Oracle TimesTen In-Memory Database SQL Reference.
3305	Invalid number of column names specified	Type of Message: Error Cause: Possible causes for this error are: You specified too many column names. You attempted to execute a CREATE TABLE AS SELECT statement and the number of columns specified for the table does not match the projected columns in SELECT. For example, CREATE TABLE atab1(c1) AS SELECT c1, c2 FROM atab; or CREATE TABLE atab1(c1, c2) AS SELECT c1 FROM atab;. Impact: TimesTen cannot perform the operation. User Action: Either use fewer column names or modify your statement so that the number of columns specified for the table matches the projected columns in SELECT, and then retry the operation.
3306	No column name specified when creating table with hash index	Type of Message: Error Cause: You did not specify a column name when creating a table with a hash index. Impact: TimesTen cannot perform the operation. User Action: Specify column name(s) for the hash index and retry the operation.
3307	Need to specify the datatype for the column	Type of Message: Error Cause: You did not specify data type for a column in your statement. Impact: TimesTen cannot perform the operation. User Action: Specify a data type for the column and retry the operation.
3308	May not specify column datatypes in this CREATE TABLE	Type of Message: Error Cause: You specified data type in your CREATE TABLE statement. The statement does not allow the specification of a data type for the column. Impact: TimesTen cannot perform the operation. User Action: Retry the operation without specifying a data type for the column.
3309	No column name specified when creating table with aging	Type of Message: Error Cause: You did not specify a column name for the column used in the AGING USE clause of your CREATE TABLE statement. Impact: TimesTen cannot perform the operation. User Action: Specify ColumnName as the name of the column used for time-based aging, and then retry the operation.
3338	The instance has been deleted and has not been propagated to Oracle. Please make sure replication agent is up	Type of Message: Error Cause: You deleted a cache group instance and this delete was not propagated to the Oracle database. Impact: The current operation failed and will continue to fail until the delete is propagated to the Oracle database. User Action: Ensure that the replication agent is up and completes propagating all changes, and retry the operation.
3404	Cannot drop AWT cache group with unpropagated deletes	Type of Message: Error Cause: You attempted to drop a cache group before all deletes of a dynamic asynchronous writethrough cache group were propagated to the Oracle database. Impact: TimesTen cannot perform the operation. User Action: Ensure the replication agent is up and completes propagating all changes, and retry the operation.
3405	Cannot do blocking checkpoint until all committed deletes of AWT cache groups have been propagated to Oracle	Type of Message: Error Cause: You attempted to perform a non-fuzzy checkpoint before all committed deletes of all dynamic asynchronous writethrough cache groups were propagated to the Oracle database. Impact: The current operation failed. User Action: Ensure the replication agent is up and completes propagating all changes, and retry the operation. For more information, see Fuzzy or Non-Blocking Checkpoints in Oracle TimesTen In-Memory Database Operations Guide.
3406	Unique constraint (constraint_name) violated at Rowid <rowid> due to unpropagated delete	Type of Message: Error Cause: A delete of a row with the same constraint values has not be propagated to the Oracle database. Impact: TimesTen cannot perform the operation. User Action: Ensure the replication agent is up and completes propagating all changes, and retry the operation.
3422	The instance has been updated and unloaded and the update has not been propagated to Oracle. Please make sure replication agent is up	Type of Message: Error Cause: You updated and unloaded a cache group instance, but the update did not propagate to the Oracle database. Impact: The instance cannot be reloaded until the delete is propagated to the Oracle database. User Action: Ensure that the replication agent is up and completes propagating all changes. If not, start the replication agent and retry the operation.
3423	The instance has been unloaded by the same transaction and cannot be reloaded. Please commit the transaction first and retry the operation	Type of Message: Error Cause: You did not commit a transaction that unloaded a cache group instance. Impact: The instance cannot be reloaded until the transaction is committed and the update is propagated to the Oracle database. User Action: Commit the transaction and ensure the replication agent is up, and retry the operation.
3428	Dynamic load is not allowed with multiple cache groups when dynamicloadEnable connection attribute is set to 1. Set it to 2 instead and retry the query	Type of Message: Error Cause: You issued a query where the DynamicLoadEnable connection attribute was set to 1. A dynamic load is not allowed if your query references multiple cache groups. Impact: The current operation failed. User Action: Set DynamicLoadEnable to 2 and retry the operation.
3429	Dynamic load is not allowed with cache group table in subquery when dynamicloadEnable connection attribute is set to 1. Set it to 2 instead and retry the query	Type of Message: Error Cause: You issued a query where the DynamicLoadEnable connection attribute was set to 1. A dynamic load is not allowed if your query references any cache group in the subquery. Impact: The current operation failed. User Action: Set DynamicLoadEnable to 2 and retry the operation. With DynamicLoadEnable set to 2, a dynamic load is not performed if your cache group is referenced in the subquery. However, a dynamic load is performed if your cache group is referenced in the main query.
3474	Internal error: error_message	Type of Message: Error Cause: There was a communication failure between elements of the grid. Impact: The current operation failed. User Action: Review the provided error message for more information on the failure and retry the operation.
3475	Internal error: error_message	Type of Message: Error Cause: An error occurred while trying to perform the operation. Impact: The current operation failed. User Action: Review the accompanying message to determine the cause of the error. If it is a transient issue, retry the operation.
3478	Remote error detected	Type of Message: Error Cause: TimesTen detected a failure on a remote element. Impact: The current operation failed. User Action: None.
3480	Failed to locate remote connection: error_message	Type of Message: Error Cause: The transaction manager requested a remote connection before the cleanup of the previous connection finished. Impact: TimesTen failed to perform the operation. User Action: Disconnect and reconnect to the database, and retry the operation.
3493	Grid partition table invalid	Type of Message: Error Cause: No valid partition map is available for the database. Impact: TimesTen cannot perform any DDL or DML operations. User Action: Run the ttGridAdmin dbDistribute command to create a valid distribution map. For more information on the ttGridAdmin dbDistribute command, see Set or Modify the Distribution Scheme of a Database (dbDistribute) in Oracle TimesTen In-Memory Database Reference.
3495	Grid fiber allocation failed	Type of Message: Error Cause: TimesTen failed to allocate memory for a grid operation. Impact: The current operation failed. User Action: Verify that the system is not running out of memory and retry the operation.
3496	Grid channel transport closed	Type of Message: Error Cause: There was a communication failure between elements of the grid. Impact: The current operation failed. User Action: Retry the operation.
3498	SQL command does not exist on remote connection	Type of Message: Error Cause: The SQL statement is not compiled on the remote element Impact: TimesTen is unable to execute the statement User Action: The statement must be re-compiled.
3500	Concurrent conflict update/delete among elementserror_message	Type of Message: Error Cause: Concurrent transactions are updating or deleting the same row. Impact: TimesTen cannot execute the statement. User Action: Retry the statement.
3501	Unable to connect to grid connection worker	Type of Message: Error Cause: There was a communication failure between elements of the grid. Impact: The current operation failed. User Action: Review the daemon log for further details on the issue. For information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
3502	Element does not exist in partition table	Type of Message: Error Cause: Element is not present in the current distribution map. Impact: TimesTen cannot perform any operation involving this element. User Action: Add this element to the distribution map with the ttGridAdmin dbDistribute command. For more information on the ttGridAdmin dbDistribute command, see Set or Modify the Distribution Scheme of a Database (dbDistribute) in Oracle TimesTen In-Memory Database Reference.
3503	Cannot execute query before calling ttDistributionSet	Type of Message: Error Cause: User tried to execute a query before setting a distribution map in the database Impact: User cannot execute any SQL statement on the database User Action: Execute ttGridAdmin dbDistribute on the database
3506	dbDistribute attempted with an invalid number of elements	Type of Message: Error Cause: You attempted to modify the distribution map of a database while exceeding the allowed maximum number of elements. Impact: TimesTen cannot perform the operation. User Action: Reduce the number of elements by removing as many data instances as necessary from the distribution map of the database. For more information, see Removing Elements from the Distribution Map in Oracle TimesTen In-Memory Database Scaleout User's Guide and System Limits and Defaults in the Oracle TimesTen In-Memory Database Reference.
3510	Unable to connect to remote timesten daemon	Type of Message: Error Cause: There was a communication failure between elements of the grid. Impact: The current operation failed. User Action: Review the daemon log for further details on the issue. For information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
3511	Only selects are supported on elements on secondary synchronous space	Type of Message: Error Cause: Statement tried to execute on a secondary data space Impact: Statement may return incorrect results User Action: Execute the statement on the primary synchronous data space.
3512	Host address host_address port port element element_id state element_state. Element not available.	Type of Message: Error Cause: A remote element is not available to execute a statement. Impact: TimesTen cannot execute the statement. User Action: Verify the state of the element and, if necessary, bring the element back online. See Monitor the Status of a Database (dbStatus) in Oracle TimesTen In-Memory Database Reference for more information.
3513	Grid query (query) does not exist in element (element_id)	Type of Message: Error Cause: An application attempted to execute a query on an element that could not find the prepared SQL statement. In some cases, the TimesTen daemon might have encountered an issue and restarted. When the TimesTen daemon restarts, prepared SQL statements are removed from the SQL command cache. Impact: TimesTen cannot execute the query. User Action: Prepare the SQL statement again and re-execute the statement.
3514	Grid query command (query) does not exist on remote elements or it failed to prepare the command on remote elements. Please retry the operation.	Type of Message: Error Cause: The specified statement does not exist in the remote node. Impact: TimesTen was unable to execute the statement. User Action: Include retry logic in the application to have it retry the statement.
3515	Grid connection connection_id interrupted	Type of Message: Error Cause: A timestenwrkr parent process terminated while a grid worker process was waiting. Impact: The current operation failed. User Action: Retry the operation if a replica of the instance is running.
3516	Grid element temporarily unavailable	Type of Message: Error Cause: An element of the grid is temporarily unavailable because it is undergoing a load or recovery operation. Impact: If the WaitForConnect attribute is set to 1 (default), TimesTen makes another connection attempt. Otherwise, the connection attempt fails. User Action: Check the state of the element and bring the element back online.
3517	Failed to get next batch of sequence values: reason	Type of Message: Error Cause: TimesTen could not get the next batch of sequence values. The accompanying message provides further details on the failure. Impact: TimesTen failed to complete the operation. User Action: Retry the operation.
3518	Cannot commit unless working partition table is fully configured	Type of Message: Error Cause: TimesTen is still configuring the partition table of the database. Impact: TimesTen failed to update the distribution map of the database. User Action: Retry the ttGridAdmin dbDistribute command.
3519	Partition Table has not yet been created	Type of Message: Error Cause: You have not defined the distribution map of the database. Impact: TimesTen cannot perform any DDL or DML operations. User Action: Use the ttGridAdmin dbDistribute command to define the distribution map of the database. For more information on the ttGridAdmin dbDistribute command, see Set or Modify the Distribution Scheme of a Database (dbDistribute) in Oracle TimesTen In-Memory Database Reference.
3520	State of element replica_element_id on element local_element_id mismatches state on Transaction Manager tm_element_id	Type of Message: Error Cause: Transaction manager state of replica mismatches the local element state. The replica probably did not get an element state transition message. Impact: TimesTen cannot perform any DDL or DML operations. User Action: Roll back and restart the transaction.
3700	The database has been re-distributed during the execution of this transaction. Please rollback the current transaction and retry in a new transaction.	Type of Message: Error Cause: The instance administrator re-distributed the database data during the execution of this transaction. The data re-distribution may have modified the location of the data. Impact: The results from the transaction are no longer valid. User Action: Roll back the current transaction, then retry in a new transaction.
3701	Grid channel closed (host host_name, elem element_id, conn connection_id, pid pid)	Type of Message: Error Cause: An element of the database failed. Impact: TimesTen failed to execute the SQL statement. User Action: Retry the SQL statement.
3702	Host address host_address port port element element_id recovering	Type of Message: Error Cause: An element of the database is recovering and currently unavailable. Impact: TimesTen failed to execute the SQL statement. User Action: Retry the SQL statement.
3703	Host address host_address port port element element_id failed	Type of Message: Error Cause: An element of the database failed. Impact: TimesTen failed to execute the SQL statement. User Action: Retry the SQL statement.
3704	Host address host_address port port element element_id down	Type of Message: Error Cause: A data instance is down. Impact: TimesTen failed to execute the SQL statement. User Action: Retry the SQL statement.
3705	Host address host_address port port element element_id unloaded	Type of Message: Error Cause: An element of the database is not loaded into memory. Impact: TimesTen failed to execute the SQL statement. User Action: Retry the SQL statement.
3706	Host address host_address port port element element_id is active but refused to connect.	Type of Message: Error Cause: An element of the database returned a communication error. Impact: TimesTen failed to execute the SQL statement. User Action: Retry the SQL statement.
3707	No more replicas available for master of duplicate	Type of Message: Error Cause: TimesTen attempted a duplicate operation on a failed element but there are no replicas available to perform the operation. Impact: TimesTen cannot perform the duplicate operation. User Action: Duplicate the failed element manually.
3708	Transmitter Grid Worker failed during duplicate operation: error_message	Type of Message: Error Cause: The process acting as transmitter in a duplicate operation failed. Impact: TimesTen did not complete the duplicate operation. TimesTen will attempt the duplicate operation with another replica of the failed element, if available. User Action: Review the provided error message for more information on the failure.
3709	Receiver Grid Worker failed during duplicate operation: error_message	Type of Message: Error Cause: The process acting as receiver in a duplicate operation failed. Impact: TimesTen did not complete the duplicate operation. TimesTen will attempt the duplicate operation with another replica of the failed element, if available. User Action: Review the provided error message for more information on the failure.
3710	Element is going through duplicate. error_message	Type of Message: Warning Cause: TimesTen is performing a duplicate operation to recover a failed element. Impact: Some operations are restricted on the recovering element while the duplicate operation is in-progress. User Action: Wait until TimesTen finishes the duplicate operation to retry the operation that triggered the warning.
3711	Information about replica elements could not be retrieved.	Type of Message: Error Cause: While attempting a duplicate operation on a failed element, TimesTen was unable to retrieve information on the replicas of the failed element. Impact: TimesTen cannot perform the duplicate operation. User Action: Verify the status of the replicas of the failed element.
3712	Grid element element_id unknown	Type of Message: Error Cause: The partition table of the database is in an inconsistent state. Impact: TimesTen failed to complete the current operation. User Action: Retry the operation.
3713	Concurrent cursors: error_message	Type of Message: Error Cause: You attempted to open two or more concurrent cursors. Impact: TimesTen failed to materialize or close one of the cursors. User Action: Retry the operation. If possible, avoid using concurrent cursors.
3714	Membership API error: error_message	Type of Message: Error Cause: A problem occurred while accessing the membership service. The accompanying error message details the reason for the failure. Impact: TimesTen failed to perform the operation. User Action: Verify that the membership service is available, and retry the operation. For more information on the membership service, see Overview of the Membership Service in TimesTen Scaleout in Oracle TimesTen In-Memory Database Scaleout User's Guide.
3715	Unable to connect to grid admin worker	Type of Message: Error Cause: The daemon failed to communicate with the process used to access the management database. Impact: The operation failed to update the management database. It may be holding a RS Recovery lock that needs to be released. User Action: Ensure that the management instance is running or switch to the standby management instance.
3716	Host address host_address port port element element_id busy performing log-based catch-up	Type of Message: Error Cause: An element of the database returned an error because it was busy performing log-based catch-up. Impact: TimesTen failed to execute the SQL statement. User Action: Retry the SQL statement.
3717	LBCU Apply failed : error_message	Type of Message: Error Cause: The failed element was unable to recover through log-based file catch-up. The accompanying error details the reason for the failure. Impact: TimesTen attempts to recover the failed element through a duplicate operation. User Action: None.
3718	LBCU request denied by master : error_message	Type of Message: Error Cause: The replica of the failed element rejected the log-based file catch-up request. The replica does not hold the log records required to recover the failed element. Impact: TimesTen attempts to recover the failed element through a duplicate operation. User Action: None.
3719	Export failed: Error error_code returned from ttMigrate	Type of Message: Error Cause: The ttMigrate utility encountered an error during the database export operation. Impact: TimesTen failed to export the database. User Action: Review the daemon log for further details on the issue, and retry the ttGridAdmin dbExport command. For information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
3720	Backup failed: Error error_code returned from ttBackup	Type of Message: Error Cause: The ttBackup utility encountered an error during the backup operation. Impact: TimesTen failed to backup the database. User Action: Review the daemon log for further details on the issue, and retry the ttGridAdmin dbBackup command. For information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
3722	Epoch wait timeout	Type of Message: Error Cause: Transaction timed out while epoch waited for dependent transactions to commit. Impact: TimesTen did not commit the epoch transaction. User Action: None.
3723	Replica set replica_set_id down	Type of Message: Error Cause: The specified replica set is down, and TimesTen was unable to retrieve data from any of its elements. Impact: TimesTen failed to execute the query. User Action: Recover the failed replica set. See Availability Despite the Failure of One Element in a Replica Set in Oracle TimesTen In-Memory Database Scaleout User's Guide for details on how to recover a failed replica set.
3724	dbImport failed during initialization phase: Error error_code returned from ttMigrate	Type of Message: Error Cause: The ttMigrate utility encountered an error during the process of creating the database objects. Impact: TimesTen failed to successfully import the database. User Action: Review the daemon log for further details on the issue. For information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
3725	dbImport failed during restore rows phase: Error error_code returned from ttMigrate	Type of Message: Error Cause: The ttMigrate utility encountered an error during the process of importing data into the tables of the database. Impact: TimesTen failed to successfully import the database. User Action: Review the daemon log for further details on the issue. For information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
3726	dbImport failed during finale phase: Error error_code returned from ttMigrate	Type of Message: Error Cause: The ttMigrate utility encountered an error during the final steps of importing the database. Impact: TimesTen failed to successfully import the database. User Action: Review the daemon log for further details on the issue. For information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
3727	Replica set state mismatch. This transaction is excluding elements that are now accepting updates. This transaction must be rolled back.	Type of Message: Error Cause: An element of the database changed state and is now accepting updates. Impact: The results from the transaction are no longer valid. User Action: Roll back the current transaction, then retry in a new transaction.
3728	dbRestore failed: Error error_code returned from ttRestore	Type of Message: Error Cause: An error occurred while trying to restore the database. Impact: TimesTen did not successfully restore the database. User Action: Use the ttGridAdmin dbRestoreStatus command for further details on the failure. For more information on the ttGridAdmin dbRestoreStatus command, see Display the Status of a Database Restore (dbRestoreStatus) in Oracle TimesTen In-Memory Database Reference.
3729	dbRestore failed during restore finale phase: Error error_code returned from dbDistribute	Type of Message: Error Cause: An error occurred while trying to restore the database. Impact: TimesTen failed to define the partition table of the database. User Action: Review the daemon log for further details on the issue. For information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
3730	Load failed because there is no valid epoch or final checkpoint	Type of Message: Error Cause: TimesTen is unable to load an element of the database. There is no valid epoch or checkpoint file available. Impact: TimesTen cannot load the element into memory. User Action: Verify that the checkpoint and transaction log files are not corrupted.
3731	Backup Init failed: Could not create epoch	Type of Message: Error Cause: An error occurred while trying to create a backup of the database. TimesTen failed to create an epoch. Impact: TimesTen failed to create a backup of the database. User Action: Retry the backup operation. For more information, see Backing Up and Restoring a Database in Oracle TimesTen In-Memory Database Scaleout User's Guide.
3732	Internal error: error_message	Type of Message: Error Cause: An error occurred while trying to execute the query. Impact: TimesTen failed to execute query. User Action: Review the accompanying message to determine the cause of the failure. If it is a transient issue, try executing the query again.
3733	Element cannot be recovered because it is not a seed element and replica set is down	Type of Message: Error Cause: The replica set is down and the current element is not the seed element for recovery. Impact: The current element cannot recover until its replica is operational. User Action: Ensure that the replica of the current element is operational or recovering.
3734	LockWait failed, element element_id is recovering and cannot execute the sql statement	Type of Message: Error Cause: An element of the grid is recovering and there are objects in lock contention. Impact: TimesTen cannot execute the SQL statement. User Action: Roll back the transaction and retry.
3735	Element is not in UNLOADED or FAILED state	Type of Message: Error Cause: You attempted an operation that is only allowed when the element is unloaded. Impact: TimesTen cannot perform the operation. User Action: Ensure that the element is unloaded. Then, retry the operation.
3736	Object object_name was altered while element element_id was down, cannot be used until element is ACTIVE	Type of Message: Error Cause: You attempted to create or use an object while an element of the database is recovering. Impact: TimesTen cannot perform the operation. User Action: Wait for the element to recover and replay logs relevant to this object. Then, retry the operation.
3737	Element string format error: error_message	Type of Message: Error Cause: The element string format is incorrect. Impact: TimesTen failed to perform the operation. User Action: Ensure that the configuration parameters of the element are valid and retry the operation.
3738	Element was unloaded without a final checkpoint	Type of Message: Warning Cause: An element of the database was ungracefully unloaded from memory. The element did not perform a final checkpoint operation. Impact: When the database is reloaded into memory, the element may take a longer time than normal to reload. User Action: None.
3739	Command failed, element element_id is in LBCU and cannot execute DDL	Type of Message: Error Cause: This is a transient error. An element of the grid is currently recovering. The element cannot execute DDL statements until all prior DML operations have been applied. Impact: TimesTen cannot execute the SQL statement. User Action: Once the element finishes recovering from the log-based catch-up operation, retry the statement.
3740	Checkpoint was aborted because durability=0 and there are no epochs associated with the latest completed checkpoint. Creating a checkpoint at this point will result in deletion of all valid epochs on this element.	Type of Message: Error Cause: The Durability attribute is set to 0 and an element of the grid is currently down. Impact: TimesTen aborted the checkpoint operation. TimesTen did not truncate the transaction log files, so you should monitor them carefully. User Action: Recover the down element, and do not delete any transaction log files or checkpoint files. Otherwise, the database would be unrecoverable. For more information, see Recovering When a Data Instance Is Down in Oracle TimesTen In-Memory Database Scaleout User's Guide.
3741	Write request denied. The database is in read-only mode. Roll back the transaction.	Type of Message: Error Cause: TimesTen is in read-only mode because a replica set is down. The current transaction performed some writes and thus needs to rollback. Impact: TimesTen denied the request and the transaction needs to rollback. User Action: Roll back the transaction.
3742	Element cannot be recovered because replica set recovery lock could not be released after repeat attempts during recovery	Type of Message: Error Cause: Replica set recovery lock could not be released as part of recovery. This can happen if the grid admin worker could not handle the request. Impact: The current element's recovery will fail and the element will transition into unloaded state. User Action: Restart the main daemon, which results in the cleaning up of orphaned locks. If the main daemon cannot be restarted, contact TimesTen Customer Support.
3743	This operation is not supported on management instances	Type of Message: Error Cause: You attempted to perform an operation that is not supported on management instances. Impact: The current operation fails. User Action: Retry the operation on a data instance.
3744	Grid channel create from elem src_element_id to elem dst_element_id timed out after timeout_secs seconds	Type of Message: Error Cause: An element of the database took too long to respond to a channel create request. Impact: TimesTen fails to execute the SQL statement. User Action: Retry the SQL statement.
3745	Grid IPC request from elem src_element_id to elem dst_element_id timed out after timeout_secs seconds	Type of Message: Error Cause: An element of the database took too long to respond to an IPC request. Impact: TimesTen fails to execute the SQL statement. User Action: Retry the SQL statement.
3746	Grid IPC request skipped because there is already an outstanding request	Type of Message: Error Cause: The connection timed out for the previous IPC request, which has not been cleared yet. Impact: TimesTen fails to execute the SQL statement. User Action: Retry the SQL statement.
3800	advisor_type information collection is in progress.	Type of Message: Error Cause: Another distribution advisor is in progress. Impact: TimesTen cannot start a distribution advisor process. User Action: Wait for other distribution advisor processes to finish and retry the operation.

Errors 4000-4999

Error number	Error or warning message	Details
4053	Internal error: error_message	Type of Message: Error Cause: An internal error occurred. Review the error_message for more information. Impact: Review the error_message for more information. User Action: Review the error_message for more information. If this error persists, contact TimesTen Customer Support.
4054	Internal warning: warning_message	Type of Message: Warning Cause: An internal warning occurred. Review the warning_message for more information. Impact: Review the warning_message for more information. User Action: Review the warning_message for more information. If this error persists, contact TimesTen Customer Support.
4056	Assertion failure (assertion) in file file_name at line number	Type of Message: Error Cause: An internal assertion occurred at the specified location. Impact: Your current operation failed. User Action: Contact TimesTen Customer Support.
4066	Retry log cursor read: error_message	Type of Message: Error Cause: An internal error occurred during log cursor read. Review the error_message for more information. Impact: Review the error_message for more information. User Action: Review the error_message for more information. If this error persists, contact TimesTen Customer Support.
4501	Database cannot checkpoint to a network file system	Type of Message: Error Cause: You attempted to perform a checkpoint operation while your DATASTORE connection attribute is set to a network file system. Impact: The checkpoint operation failed. User Action: Change the DATASTORE connection attribute value from a network file system to a local file system value. Then, retry the checkpoint operation. For more information on the DATASTORE connection attribute, see DataStore in Oracle TimesTen In-Memory Database Reference.
4502	Database cannot log to a network file system	Type of Message: Error Cause: TimesTen attempted to create database logs while your LOGDIR connection attribute is set to a network file system. Impact: TimesTen cannot create database logs. User Action: Change the LOGDIR connection attribute value from a network file system to a local file system value. For more information on the LOGDIR connection attribute, see LogDir in Oracle TimesTen In-Memory Database Reference.
4600	Error min_range and max_range	Type of Message: Error Cause: You specified argument values that are not within the permitted min_range and max_range. Impact: TimesTen cannot complete the operation. User Action: Specify argument values that are within the permitted min_range and max_range.
4601	Error value message	Type of Message: Error Cause: You specified an invalid argument value. Impact: TimesTen cannot complete the operation. User Action: Specify a valid argument value.

Errors 5000-5999

Error number	Error or warning message	Details
5002	Unable to connect to the cache agent for database_path_name; check agent status	Type of Message: Error Cause: The cache agent is not running. Impact: TimesTen cannot autorefresh cache groups. User Action: Call the ttCacheStart built-in procedure to start the cache agent. For more information about the ttCacheStart built-in procedure, see ttCacheStart in Oracle TimesTen In-Memory Database Cache Guide.
5007	cache agent error	Type of Message: Error Cause: There was a communication failure between the TimesTen cache agent and the client process. Impact: TimesTen cannot load or autorefresh cache groups. User Action: Attempt to stop and restart the cache agent with the ttCacheStop and ttCacheStart built-in procedures. For more information about the ttCacheStart built-in procedure, see ttCacheStart in Oracle TimesTen In-Memory Database Cache Guide.
5010	No OracleNetServiceName specified in DSN	Type of Message: Error Cause: An attempt was made to start a TimesTen cache agent for a DSN that does not have the OracleNetServiceName attribute specified. Impact: Without the OracleNetServiceName specified, TimesTen cannot enable communication with the Oracle database, which disables caching of Oracle database tables. User Action: Ensure that the OracleNetServiceName set in your DSN definition matches the Oracle Service Name for the Oracle Database instance that contains the tables to cache in TimesTen. See Unable to resolve Oracle Service Name in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
5011	Oracle(OCI8) call failed	Type of Message: Error Cause: The TimesTen cache agent got an error on an Oracle database (OCI8) call. Impact: The cache agent uses OCI to communicate with the Oracle database. User Action: For more details on what the origination issue is for the error, look at the user error log entries. You may need to re-initialize OCI. See OCI initialization failed in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
5012	Oracle login failed	Type of Message: Error Cause: The TimesTen cache agent could not connect to the Oracle database with the given user name or password. Impact: All caching operations cannot proceed unless the cache agent connects to the Oracle database. User Action: This may be an issue with the cache administration user name and password. Or there are other issues that may cause the Oracle database user name and password to fail. See Registering the Cache Administration User Name and Password in Oracle TimesTen In-Memory Database Cache Guide and Unable to validate the Oracle database user name and password in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
5013	Operation requires cache connection	Type of Message: Error Cause: The TimesTen cache agent could not execute the operation because it was not able to connect to either the TimesTen or the Oracle databases. Ensure that the user name, password and Oracle database ID are correct. Impact: All caching operations cannot proceed unless the cache agent connects to the TimesTen and Oracle databases. User Action: You must specify the cache manager user name in the UID connection attribute, which is the same user name for both the TimesTen and Oracle databases. However, you specify separate passwords for each database. See Registering the Cache Administration User Name and Password in Oracle TimesTen In-Memory Database Cache Guide.
5015	Mismatch in number of columns extracted and number of columns in cached table	Type of Message: Error Cause: The schema of the cached table changed on the Oracle database after the cache group was created. Impact: The specified cached tables cannot function correctly. User Action: Recreate the cache group. For more information, see Create the cache groups in Oracle TimesTen In-Memory Database Cache Guide. Then, retry the operation.
5016	cache agent has too many existing connections	Type of Message: Warning Cause: The Oracle database has run out of resources to accommodate any additional connections made by the TimesTen cache agent. Impact: The TimesTen Cache features cannot function correctly. User Action: Diagnose and troubleshoot any connection leaks to the Oracle database. Also, consider configuring the Oracle database to allow additional connections. Then, retry the operation.
5019	Bad table name specification	Type of Message: Error Cause: The configuration file contains a cache table specification with an invalid table name. Review the user error log for additional error messages. Impact: The cache agent may have failed certain operations, such as loading a cached table. User Action: Review the user error log for how to proceed.
5020	Warning(s) during population of cache. See the TimesTen user error log for details. error_message.	Type of Message: Warning Cause: A warning message was generated while TimesTen was populating a cached table. Review the user error log for more information. Impact: TimesTen may not have completed the population of the cached table. User Action: Review the user error log for how to proceed.
5021	Could not get meta data from Oracle: error_message.	Type of Message: Error Cause: The TimesTen cache administrator cannot retrieve the requested metadata from the Oracle database. Impact: The cache agent may have failed certain operations, such as a refresh operation. Review the user error log for more information. User Action: Review the user error log for how to proceed.
5025	Commit failure in Oracle. Transaction must be rolled back in TimesTen.	Type of Message: Error Cause: Commit failed in the Oracle database. The TimesTen transaction must be explicitly rolled back. Impact: The transaction cannot continue. User Action: If an error is encountered by a user connection, rollback the transaction.
5026	Cannot alter cached tables	Type of Message: Error Cause: Cache tables cannot be altered. Impact: No requested alterations are made to the cache table. User Action: To modify the cache table, you must first drop and re-create it using the CREATE CACHE GROUP statement. See CREATE CACHE GROUP in Oracle TimesTen In-Memory Database Reference.
5029	Warning(s) while populating the cache. warning_message	Type of Message: Warning Cause: A warning was generated while populating the cached table. The details are attached to the message. Impact: There is an issue with how you are populating your cache group. User Action: Refer to the warning message and take appropriate action.
5030	Communication buffer overflow. The cache group definition of cache_group_name is too large to perform this operation.	Type of Message: Error Cause: The TimesTen cache communication buffer overflowed. The operation failed. The most likely cause of this error is that the cache group contains several tables or each table contains several columns and the total length of these tables and columns has exceeded the communication buffer. Impact: The operation fails. User Action: Reduce the number of table names or column names in the request message to the cache agent.
5034	The operation must be executed within its own transaction	Type of Message: Error Cause: Each cache group operation must be executed within its own transaction. Impact: The cache group operation failed. User Action: Ensure that your cache group operations are executed within its own transaction. A commit must be done both before and after executing a cache group operation.
5035	A cache group may not have a negative number of tables	Type of Message: Error Cause: The cache group has a negative number of tables. Impact: The severity of the impact is unknown and requires additional diagnosis. User Action: Contact TimesTen Customer Support.
5036	Warning(s) while populating the cache. warning_message	Type of Message: Warning Cause: Some SQL warnings were generated while loading or refreshing the cached table. Detail warning messages are appended to the end. Impact: The cache tables may not be populated as expected. User Action: See attached warning messages for direction on how to proceed.
5037	An error occurred while loading cache_group_name:warning_message	Type of Message: Error Cause: An error occurred while loading or refreshing the cached table. The detailed error follows this error message. Impact: The cache table was not loaded or refreshed. User Action: Note the warning message for directions on how to proceed.
5038	Warning(s) while populating the cache. warning_message	Type of Message: Warning Cause: Some SQL warnings were generated during the population stage of the REFRESH CACHE GROUP operation.The detailed error follows this error message. Impact: The cache table may not have been populated correctly during the REFRESH CACHE GROUP operation. User Action: See the warning message for directions on how to proceed.
5039	An error occurred while refreshing cache_group_name: error_message	Type of Message: Error Cause: An error occurred while refreshing the specified cache group. A detailed error message follows this message. Impact: Review the error message for possible impacts. User Action: Review the error message for how to proceed.
5040	Warning(s) while unloading the cache. warning_message	Type of Message: Warning Cause: Some SQL warnings were generated while unloading the cache group. A detailed warning message follows this message. Impact: Review the warning message for possible impacts. User Action: Review the warning message for how to proceed.
5041	An error occurred while unloading cache_group_name:error_message	Type of Message: Error Cause: An error occurred while unloading the specified cache group. A detailed error message follows this message. Impact: The cache group unload operation was unsuccessful. Review the error message for possible impacts. User Action: Review the warning message for how to proceed.
5045	Cache group operations may not use database level locking	Type of Message: Error Cause: Cache group operations require row-level locking to enable the TimesTen cache agent to get simultaneous access to the database. Impact: Cache group operations are not proceeding. User Action: Set the LockLevel connection attribute to its default of 0 for row-level locking) in the DSN. See LockLevel in Oracle TimesTen In-Memory Database Reference.
5046	Commit/rollback required after Cache operation	Type of Message: Error Cause: An error occurred after executing a LOAD, UNLOAD or REFRESH command. This error occurs when the user does not immediately commit or rollback the transaction after executing a LOAD, UNLOAD or REFRESH command. These cache group commands are required to be the only operation in the transaction. Impact: The transaction cannot continue. User Action: To fix this error, commit or rollback right after the cache group operations.
5047	This operation is not allowed on cached tables	Type of Message: Error Cause: A primary key is required for all cache groups. Thus, any operation where you try to add or drop a primary key is not allowed. In addition, if you add or drop a foreign key, this may alter the parent/child relationship between the tables in the cache group. Thus, you are not allowed to add or drop a foreign key on a cache table. Impact: The operation trying to add or drop the primary key or foreign key constraint on a cache table fails. An index on a cache table cannot be dropped. User Action: Create or drop any primary or foreign key constraints on the tables that are to be cached before creating the cache group.
5048	Feature not supported: feature_name	Type of Message: Error Cause: The feature is invalid or unsupported. Impact: The feature does not work. User Action: Do not attempt to use this feature.
5050	Cache group definition is too long. Current system limit on field_name field is number bytes. Specified definition requires number bytes	Type of Message: Error Cause: Either the cache group WHERE clause is too long or the cache group has too many long column names or too many tables. The maximum allowed length of the cache group WHERE clause is 4096 characters. Impact: The cache group is not defined. User Action: Either limit the column names or decrease the number of tables so that the WHERE clause is equal to or less than 4096 characters.
5051	Commit message to cache agent failed. Cache agent must be restarted	Type of Message: Error Cause: Failed to notify the cache agent of the transaction commit. Check if cache agent has been shut down. If so, restart the cache agent. Impact: The cache agent must be active in order for any transactions to be complete. User Action: Use the ttStatus utility to check if the cache agent is active. Then, use the ttCacheStart built-in procedure to start the cache agent. See the Checking the Status of the Cache and Replication Agents in TimesTen Classic and Managing the Cache Agent sections in the Oracle TimesTen In-Memory Database Cache Guide.
5052	Cache group name required with install_flag value 1	Type of Message: Error Cause: No cache_group_name parameter was provided for the ttCacheSqlGet built-in procedure call. The cache_group_name parameter cannot be NULL or empty when the install_flag parameter is set to 1. Impact: The ttCacheSqlGet built-in procedure does not complete. User Action: Provide the cache group name when specifying a value 1 for the install_flag parameter. See ttCacheSqlGet in Oracle TimesTen In-Memory Database Reference.
5053	Add/Drop foreign keys are not allowed on cached tables	Type of Message: Error Cause: A primary key is required for all cache groups. Thus, any operation where you try to add or drop a primary key is not allowed. In addition, if you add or drop a foreign key, this may alter the parent/child relationship between the tables in the cache group. Thus, you are not allowed to add or drop a foreign key on a cache table. Impact: The operation trying to add or drop the primary key or foreign key constraint on a cache table fails. An index on a cache table cannot be dropped. User Action: Create or drop any primary or foreign key constraints on the tables that are to be cached before creating the cache group.
5054	Detect loss of Oracle Connection (error_number) during rollback. Oracle rollback will be implicit	Type of Message: Error Cause: The Oracle database connection terminated during a transaction rollback. The pending Oracle database transaction was (or will be) rolled back by the Oracle database server. The error_number is either an ORA-xxxxx message, an Oracle database error code that was returned by the Oracle database during rollback, or "no error code," which means the connection was broken before the Oracle database rollback request. Impact: The Oracle database connection terminated during a transaction rollback. The transaction on the Oracle database will be rolled back. User Action: Investigate the source reason for the Oracle database connection failure. After ensuring that the transaction is rolled back on the TimesTen database, re-initiate the transaction.
5058	The cache operation received a warning: warning_type=<warning_type>, warning_code=<warning_code>, warning_message: error_message	Type of Message: Warning Cause: The cache agent generates this warning message. The specific warning is indicated at the end of message. Impact: The cache agent generated a warning message that may require your attention. User Action: Note the warning message and take any appropriate action.
5064	The Oracle client version version_number is not compatible with Oracle server version version_number. Please upgrade Oracle server to version_number or higher	Type of Message: Error Cause: The Oracle database client version is not compatible with the Oracle Database server version. This error can be encountered by the application during any operation that requires a connection to the Oracle database. Impact: TimesTen cannot perform cache operations unless its included Oracle client is compatible with the back-end Oracle database. User Action: Use the compatible Oracle database client/server versions. See the Oracle TimesTen In-Memory Database Release Notes (README.html) in your installation directory for specific platform versions supported by TimesTen.
5067	Name string is already used by an existing object_type.	Type of Message: Error Cause: The name specified is already in use. Impact: The object is not created. User Action: Specify a unique name for the indicated object.
5068	Argument argument_name ignored.	Type of Message: Warning Cause: The ttCacheConfig built-in procedure was called with an argument that was not needed. Impact: The argument was ignored and the ttCacheConfig built-in was called without the argument. User Action: If used within a script, eliminate the unnecessary argument. For more information on the ttCacheConfig built-in procedure, see ttCacheConfig in Oracle TimesTen In-Memory Database Reference.
5069	Argument argument_name error_message.	Type of Message: Error Cause: A TimesTen Cache built-in procedure was called with an invalid argument. The error message indicates the invalid argument. Impact: The built-in procedure fails. User Action: Refer to the built-in procedure documentation in the Oracle TimesTen In-Memory Database Reference for details on each built-in procedure. Re-execute the built-in procedure with the appropriate arguments.
5070	Error compiling PL/SQL block. Check that user_name has privilege_type on table_name	Type of Message: Error Cause: There was an error compiling an Oracle Database PL/SQL block because the application user does not have the correct privileges on Oracle Database. Impact: The PL/SQL block did not compile. User Action: Check that the user has the appropriate privileges as indicated in the message.
5071	Name string reused within statement. Use different names.	Type of Message: Error Cause: One of the cached tables uses the same name as the cache group. Impact: The operation is not executed. User Action: Use a unique name for the cache group.
5073	Cache operation failed. Rollback required.	Type of Message: Error Cause: Review the error message on the error stack for possible causes. Impact: The transaction must be rolled back. User Action: Rollback the transaction. For more information on how to rollback a transaction, see Using ttIsql to Manage Transactions in Oracle TimesTen In-Memory Database Operations Guide. Then diagnose and troubleshoot the error on the error stack and retry the cache operation.
5074	Could not log in to Oracle database. Login Attempt: number, Allowed attempts: number.	Type of Message: Error Cause: The cache or replication agent failed to connect to the Oracle database. Impact: TimesTen cannot connect to the Oracle database. When the number of log in attempts reaches the number of allowed attempts, the agent will stop trying to connect to the Oracle database. User Action: Review the daemon log for more details about the problem. For more information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
5075	Null or blank cache group name.	Type of Message: Error Cause: You provided either a null or blank cache group name. Impact: TimesTen did not excute the statement. User Action: Provide a cache group name and retry the operation.
5101	An error occurred while generating the name of the type database shared library for database type: database_type	Type of Message: Error Cause: An error occurred while initializing the shared library to support cache group operations. Impact: No cache group operations can be executed. User Action: Retry the operation. Check the support log for further clarification.
5102	Cannot load backend library 'library_name' for Cache Connect. OS error message 'error_details'.	Type of Message: Error Cause: The library used by TimesTen Cache could not be loaded. This can happen if: The library was not installed or is a different name within OCI. The library was not found. The library search path does not contain the TimesTen library directory. The search path is defined by the PATH environment variable on Windows NT systems or the LD_LIBRARY_PATH environment variable on Linux and UNIX systems. The Oracle library bits do not match the TimesTen bits. Impact: Cache group operations cannot be executed. User Action: You may have to revisit the shared library path environment variable. Some platforms use something other than LD_LIBRARY_PATH. See the Shared library path environment variable in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide for details.
5103	The cache group operation could not unload the backend database shared library. library_name	Type of Message: Error Cause: The operating system had some problem unloading the back-end database library. Impact: The back-end database library is not unloaded. User Action: Check support log for further information.
5104	Could not initialize the function pointers backend database api. Function function_name was not in the library.	Type of Message: Error Cause: An older version of the back-end library was loaded. Impact: TimesTen cache needs a supported version of the back-end library to be loaded in order to perform. User Action: Check the library search path to verify that it is pointing to the correct library directory. See the Shared library path environment variable in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide for details.
5105	OCI initialization failed: error_details.	Type of Message: Error Cause: OCI could not be initialized. This is a necessary component for TimesTen Cache. Impact: TimesTen Cache cannot perform. User Action: There may not be enough memory on the client system.
5106	Could not allocate handle_name handle	Type of Message: Error Cause: This usually occurs when there is very little memory left on the client system. Impact: TimesTen Cache cannot perform. User Action: Provide more memory on the client system.
5107	Oracle(OCI) Oracle_error_id in OCI_call: Oracle_error_number	Type of Message: Error Cause: An error that occurred while executing an OCI function. Details on the error are specified within the error message. Impact: The operation that was being performed has failed because of an error that occurred while executing an OCI function. User Action: Refer to the error message for the error number.
5109	Cache Connect general error: Oracle_operation	Type of Message: Error Cause: TimesTen Cache failed in the identified Oracle database operation. This error is usually accompanied by a more specific error message. If not, contact TimesTen Customer Support. Impact: The Oracle database operation failed within a TimesTen cache transaction. User Action: Refer to the error information on how to proceed.
5110	Table does not exist in Oracle: table_name	Type of Message: Error Cause: The cache group table does not exist on the Oracle database. Impact: The cache group cannot be created. User Action: Before you define the cache group table, create the Oracle Database tables that are to be cached.
5111	Could not find matching unique index for cache table table_name	Type of Message: Error Cause: The primary key defined on TimesTen must match the primary key or unique NOT NULL key on the Oracle database. Impact: The cache group table cannot be created. User Action: The TimesTen cache table primary key must be defined on the full Oracle Database table primary key or on all of the columns in the unique index. See Cache Groups and Cache Tables in Oracle TimesTen In-Memory Database Cache Guide.
5113	Cache owner_name table_name contains REAL/DOUBLE/FLOAT column(s). Cached value may have different precision.	Type of Message: Warning Cause: Oracle Database and TimesTen have different implementations of floating point data types and the precisions are different. Impact: The cached value may be slightly different than the value in Oracle Database. TimesTen generates this warning when you try to create a table with a REAL, FLOAT or DOUBLE type. User Action: Note the differences as described in the Type specifications and Floating-point numbers sections in the Oracle TimesTen In-Memory Database SQL Reference.
5114	Unsupported type mapping for key column column_name	Type of Message: Error Cause: The data type mapping rules were violated on a key field. Impact: The SQL statement was not executed. User Action: Conform to the data type mapping rules. See the Data Type Support and Mappings Between Oracle Database and TimesTen Data Types sections in the Oracle TimesTen In-Memory Database Cache Guide for more information.
5115	Unsupported type mapping for column column_name	Type of Message: Error Cause: The data type mapping rules were violated on a non-key field. Impact: The SQL statement was not executed. User Action: Conform to the data type mapping rules. See the Data Type Support and Mappings Between Oracle Database and TimesTen Data Types sections in the Oracle TimesTen In-Memory Database Cache Guide for more information.
5116	Column column_name does not exist in Oracle	Type of Message: Error Cause: The column name you specified does not exist in the Oracle table. Impact: Cannot create the cache group. User Action: Verify that you have correctly spelled the column name or provide a new name.
5117	Unsupported WHERE clause for cache table table_name	Type of Message: Error Cause: The WHERE clauses specified in the CREATE CACHE GROUP statement does not work on the Oracle database. Impact: You cannot use the WHERE clause in this SQL statement for this cache table. User Action: Verify that the WHERE clause is valid.
5118	Column column_name has different precision/scale in Oracle	Type of Message: Warning Cause: Oracle Database and TimesTen have different implementations of floating point data types and their precision are different. TimesTen issues this warning when a TimesTen DECIMAL type is mapped to an Oracle Database NUMBER type. Impact: None. User Action: Ensure that the data type and its precision conform. See Numeric data types in Oracle TimesTen In-Memory Database SQL Reference.
5119	Column column_name has different nullability setting in Oracle	Type of Message: Warning Cause: The nullability setting of a column on TimesTen differs from that of the column on the Oracle database. Impact: None. User Action: Change the nullability of the column to conform to the Oracle database. See Unsupported data type mapping in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
5120	No matching unique index with not null columns, unique key constraint with not null columns, or primary key constraint on table table_name, cache operations are restricted	Type of Message: Warning Cause: TimesTen cannot find a primary key or a unique NOT NULL index on the Oracle database to match the cache table's primary key. Impact: The cache group is created. However, the cache group operations are restricted to full cache group LOAD CACHE GROUP, UNLOAD CACHE GROUP and MERGE operations. User Action: See Cache Groups and Cache Tables in Oracle TimesTen In-Memory Database Cache Guide for directions on how the Oracle database table must be created to be used as a cache table.
5121	Non-standard type mapping for column column_name, cache operations are restricted	Type of Message: Warning Cause: Non-standard type mapping was found while creating cache group. Impact: The cache group is created, but operations are restricted to full cache group LOAD CACHE GROUP, UNLOAD CACHE GROUP and MERGE operations. User Action: Ensure that the data type mapping conforms to compatibility requirements as documented in Mappings Between Oracle Database and TimesTen Data Types in Oracle TimesTen In-Memory Database Cache Guide.
5123	Operation not allowed on restricted cache group cache_group_name	Type of Message: Error Cause: The specified operation is not allowed on a restricted cache group. A cache group is restricted if it has a non-standard data type mapping in one of its columns or if there is no matching primary key on the Oracle database. Impact: Ensure that the data types used for the Oracle database are compatible. User Action: See Cache Groups and Cache Tables in Oracle TimesTen In-Memory Database Cache Guide for directions on how the Oracle database table must be created to be used as a cache table.
5124	Autorefresh/propagate are not allowed on restricted cache group	Type of Message: Error Cause: AUTOREFRESH and PROPAGATE are not allowed on a restricted cache group. A cache group is restricted if it has a non-standard data type mapping in one of its columns or if there is no matching primary key on the Oracle database. Impact: The autorefresh or propagate did not execute for your cache group. User Action: Each Oracle table used for caching must have a primary key or unique index as described in Cache Groups and Cache Tables in Oracle TimesTen In-Memory Database Cache Guide. Ensure that the data type mapping conforms to compatibility requirements as documented in Mappings Between Oracle Database and TimesTen Data Types in Oracle TimesTen In-Memory Database Cache Guide.
5125	Caching of Timestamp column(s) with difference scale: fractional seconds may be truncated	Type of Message: Error Cause: The scale of the TimesTen TIMESTAMP type is always 6. Mapping of Oracle database TIMESTAMP COLUMNS with a scale other than 6 to a TimesTen TIMESTAMP column may cause silent truncation of the column value at runtime. Impact: The column may be truncated. User Action: Any values for the fraction not specified in full microseconds results in a "Data Truncated" error. Conform to the format, which is YYYY-MM-DD HH:MI:SS [.FFFFFFFFF].
5126	A system managed cache group cannot contain non-standard column type mapping	Type of Message: Error Cause: There are certain data types supported on TimesTen that is not supported within the Oracle database. Impact: TimesTen cannot perform the operation. User Action: See Data Type Support in Oracle TimesTen In-Memory Database Cache Guide for a list of supported data type mappings.
5127	Backend connection invalid. error_details	Type of Message: Error Cause: You specified an invalid back-end database in the connection or an error occurred while trying to connect to the Oracle database. Impact: The operation fails. See additional information in error_details. User Action: The operation is retried automatically. If the problem persists, verify the state of the Oracle database.
5128	handle_name handle is invalid. The Oracle connection may have been lost. Retry your operation.	Type of Message: Error Cause: The connection to the Oracle database was lost. Impact: TimesTen cannot complete the transaction. User Action: Check if the Oracle database instance is up and retry the operation.
5129	SQL command is no longer valid. handle_name handle has been invalidated. The Oracle connection may have been lost after the statement was prepared.	Type of Message: Error Cause: The connection to the Oracle database was lost. Impact: TimesTen cannot complete the transaction. User Action: Check if the Oracle database instance is up, re-prepare your statement, and retry the operation.
5130	Error executing the following statement on Oracle_database_name: statement	Type of Message: Error Cause: A TimesTen cache operation tried to execute a malformed SQL statement on the Oracle database. Impact: The query execution failed on the Oracle database. User Action: Examine your query and verify that the Oracle database schema has not changed during TimesTen Cache operations.
5131	Cannot connect to backend database: OracleNetServiceName = \"service_name\", uid = \"user_id\", pwd is hidden, TNS_ADMIN = \"path\", ORACLE_HOME= \"path\"	Type of Message: Error Cause: You did not specify the Oracle database user password (ORACLEPWD) attribute. Alternatively, you specified an incorrect OracleNetServiceName, user id or password, TNS_ADMIN, or location of the Oracle database installation. Impact: The operation fails. User Action: You may also find the Oracle database error number in other messages on the error stack. For more information on the corresponding Oracle database error, see the Oracle Database Error Messages.
5132	SQL command is no longer valid. Type handle has been invalidated. The Oracle connection may have been lost after the statement was prepared.	Type of Message: Warning Cause: The Oracle database SQL statement used by TimesTen cache is no longer valid. Impact: The operation fails. User Action: None.
5133	Could not re-install SIGINT signal handler	Type of Message: Error Cause: The handler was changed by the Oracle database. Impact: TimesTen Cache failed to re-install the SIGINT signal handler. User Action: Contact TimesTen Customer Support.
5134	Could not determine Oracle server version	Type of Message: Error Cause: Check the TimesTen log for and additional Oracle Error code. Impact: TimesTen Cache failed to determine the version of the Oracle database server. User Action: Contact TimesTen Customer Support.
5142	Autorefresh is not allowed on cache groups with Oracle synonyms	Type of Message: Error Cause: You attempted to set AUTOREFRESH for a cache group that uses Oracle database synonyms. Impact: The operation fails. User Action: Avoid using Oracle Synonyms in the CREATE CACHE GROUP statement.
5144	The cache group contains a Oracle materialized view, cache operations are restricted.	Type of Message: Warning Cause: You attempted to create a restricted cache group on an Oracle database materialized view. Impact: Some operations are not allowed for this cache group. User Action: Avoid using Oracle Materialized views in the CREATE CACHE GROUP statement. For more information, see Create the cache groups in Oracle TimesTen In-Memory Database Cache Guide.
5146	owner_name.object_name is a public synonym which is not supported	Type of Message: Error Cause: You attempted to create an object owned by PUBLIC. Public synonyms are not supported in cache groups because the owner and object name on the Oracle database must be the same on TimesTen. Impact: TimesTen cannot complete the operation. User Action: Avoid using public synonyms in the CREATE CACHE GROUP statement.
5150	The statement handle is in an invalid state for the operation: operation_name	Type of Message: Error Cause: The statement handle is in invalid state. Impact: The severity of the impact is unknown and requires additional diagnosis. User Action: Contact TimesTen Customer Support.
5151	Passthrough is not supported for error_condition	Type of Message: Error Cause: You attempted to pass through an unsupported SQL statement or large output parameter values from TimesTen to the Oracle database. Impact: Statement execution stopped. User Action: Use a SQL statement that is supported for passthrough. Also, ensure that the SQL statement does not contain large output parameter values. For more information about the PassThrough attribute, see PassThrough in Oracle TimesTen In-Memory Database Reference.
5152	Could not determine what type of Oracle statement is being prepared. May be a possible syntax error.	Type of Message: Error Cause: You passed through a SQL statement with invalid syntax. Impact: OCI cannot identify the type of SQL statement. User Action: Verify that the syntax is correct and retry the operation.
5153	Operation_name is not allowed for this type of Oracle statement.	Type of Message: Error Cause: You called a fetch on a non-SELECT PASSTHROUGH statement. Impact: The operation fails. User Action: Contact TimesTen Customer Support.
5155	Wrong number of parameters	Type of Message: Error Cause: You set a number of parameters that does not match the number of input parameters. Impact: The operation fails. User Action: Ensure that the number of parameters is correct and retry the operation.
5156	Too many parameters. Maximum number of parameters allowed is number	Type of Message: Error Cause: You set a number of parameters that does not match the number of input parameters. Impact: The operation fails. User Action: Ensure that the number of input parameters is valid and retry the operation.
5158	Oracle compilation error:\nerror_message	Type of Message: Error Cause: The TimesTen Cache operation encountered an Oracle database compilation error. See the accompanying error message for more information. Impact: The TimesTen Cache operation fails. User Action: Contact TimesTen Customer Support.
5159	Index owner_name.index_name was converted to a non-unique index because table owner_name.table_name is a member of an autorefreshed cache group.	Type of Message: Warning Cause: You created a unique index on a table in an autorefresh cache group. Impact: Any unique index you create on a table in an autorefresh cache group is automatically converted to a non-unique index. User Action: None.
5160	Failed to prepare Oracle objects for database duplication: error_details	Type of Message: Error Cause: Some Oracle database objects are missing or are in use by another application. This error can occur during database duplication. Impact: TimesTen cannot complete the operation. User Action: Check the details of the error message for possible causes.
5162	Could not register Oracle failover callback function.	Type of Message: Error Cause: A connection failure may have occurred. Check other error messages for more information. Impact: A callback function to handle Oracle RAC failover was not registered. User Action: If you initiated the connection, manually reconnect to the TimesTen database and retry the operation.
5163	Oracle failover failed with event event_id. Retried for number minutes.	Type of Message: Error Cause: TimesTen was not able to reestablish the connection to an Oracle Database instance. Check other error messages for more details. Impact: TimesTen is no longer connected to the Oracle Database. User Action: Ensure that an Oracle Database instance is running.
5164	No matching foreign key with cascade action for table table_name on Oracle	Type of Message: Error Cause: You specified a CASCADE DELETE foreign key on a cache table that is specified as PROPAGATE, or belongs to a cache group that is specified as AWT or SWT, but there is not a matching CASCADE DELETE foreign key defined on the corresponding Oracle database table. Impact: The operation fails. User Action: Either remove the CASCADE DELETE foreign key on the cache table or add one to the Oracle database table.
5165	Autorefresh state state for cache_group_name is incompatible with replication scheme. Autorefresh state should be state.	Type of Message: Error Cause: You specified a cache group where the AUTOREFRESH state indicated in the messages is incompatible with the associated replication scheme. Impact: TimesTen cannot complete the operation. User Action: Either ALTER or CREATE the cache group with the compatible state indicated in the message.
5166	Autorefresh state state for store is incompatible with replication state state state. Autorefresh store should be state.	Type of Message: Error Cause: You specified a cache group where the AUTOREFRESH state indicated in the messages is incompatible with the associated replication store state. Impact: The operation fails. User Action: Either ALTER or CREATE the cache group with the compatible state indicated in the message.
5167	Deprecated type mapping for column column_name	Type of Message: Error Cause: You used a type of mapping that is not supported. Impact: TimesTen cannot complete the operation. User Action: Change the type of the column indicated in the error message and retry the operation. For more information, see Mappings Between Oracle Database and TimesTen Data Types in Oracle TimesTen In-Memory Database Cache Guide.
5168	Restricted cache groups are deprecated	Type of Message: Warning Cause: Restricted cache groups are supported in this release for backward compatibility. Impact: None. User Action: None.
5169	The database must be in Oracle data type mode (TypeMode=0) in order to use any of the Cache Connection features.	Oracle database type mode is required for the database that contains the cache group.
5170	Duplicate completed successfully but the cache metadata will be updated after the cache and replication agents have been started on the destination database because of the reasons stated below.	Type of Message: Error Cause: The metadata on Oracle was not updated during the Duplicate operation (maybe because a connection to the Oracle Database could not be established). Impact: The metadata stored on the Oracle database for cache groups is updated by the cache and replication agents after they are started and they are able to connect to the Oracle database. User Action: Ensure that the cache and replication agents are started on the destination database.
5171	lookup for username user_name failed on Oracle.	Type of Message: Error Cause: You attempted to perform a cache operation and specified a user name that was not found on the Oracle database. Impact: TimesTen cannot complete the operation. User Action: Ensure that the user name you specify exists on the Oracle Database.
5181	Oracle column maximum byte length is restricted to 4000 bytes for column column_name	Type of Message: Warning Cause: You specified a column length on the specified table that is greater than the maximum allowed length of 4000 bytes. Impact: TimesTen cannot complete the operation. User Action: Specify a value that does not exceed the allowed length of the column and retry the operation.
5182	TimesTen Cache is supported only with Oracle Database Server release 10.2 and later.	Type of Message: Error Cause: Your version of the Oracle database server is not supported. Impact: TimesTen cannot complete the operation. User Action: Check that the Oracle database server release is 10.2 or later.
5183	Function function_name was not in the library. The function will not be called.	Type of Message: Warning Cause: During the first cache connect operation within an application or during the startup of the replication agent, TimesTen discovered that a function was not a part of the library. Impact: Cache connect will not call the function. User Action: Check that the OCI client library version is 11.1 or later.
5184	owner_name.object_name cannot be cached. The Oracle synonym is owned by another user and cannot be cached by the current session user.	Type of Message: Error Cause: You attempted to create a cache group on an Oracle database synonym that is owned by another user in the Oracle database. Impact: The operation fails. User Action: Try one of the following actions: The owner of the synonym creates the cache group. Create another synonym to point to the other owner's synonym. The cache group then references the new synonym.
5185	Cache admin user user_name does not have privilege_name Oracle privileges on owner_name.object_name.	Type of Message: Error or Warning Cause: This is either an error or warning depending on the privilege that the cache administrator lacks and the type of cache group that is being created. Impact: TimesTen cannot complete the operation. User Action: Grant the appropriate Oracle database privileges to the cache administration user. For more information, see Required Privileges for Cache Administration User for Cache Operations in Oracle TimesTen In-Memory Database Cache Guide.
5186	The OCI client library in use does not contain required routines to support caching LOBs from Oracle.	Type of Message: Warning Cause: Your application is linked with an OCI library that was not shipped with TimesTen. Impact: TimesTen will not cache LOB datatypes from Oracle. User Action: Ensure you use the OCI Library that was shipped with TimesTen.
5187	Caching LOBs from Oracle requires using an OCI client library provided by the TimesTen installation, or other versions of OCI client supported by TimesTen.	Type of Message: Error Cause: Your application is linked with an OCI library that was not shipped with TimesTen. Impact: TimesTen cannot complete the operation. User Action: Ensure you use the OCI Library that was shipped with TimesTen.
5190	Table table_name not found. Error_condition	Type of Message: Warning Cause: The specified TimesTen table does not exist. Impact: The TimesTen Cache configuration parameters for the ttCacheConfig built-in procedure are set, but will not be applied until the specified TimesTen table is created. User Action: Ensure that the specified table exists on TimesTen.
5207	The cache admin uid cannot be changed while there are any cache groups in the database. Drop all cache groups and try again.	Type of Message: Error Cause: The cache administrator UID/PWD cannot be set if there are any AWT or autorefresh cache groups with state ON or PAUSED. Impact: TimesTen cannot complete the operation. User Action: Drop or alter the cache group and reset the UID/PWD and retry the operation.
5208	There are existing cache groups under the Cache Admin's schema on Oracle. Schema_name	Type of Message: Error or Warning Cause: This is an error if you are changing some Cache Configuration parameter. When TimesTen started tracking DDL changes on the Oracle database, there were already cache groups in the database. Since the corresponding Oracle database tables may have been altered before the tracking started, there may be an inconsistency between the cache schema and the Oracle database schema. This is a warning. Impact: If it is an error, the operation cannot be completed. If it is a warning, some Oracle database cached tables may not match the TimesTen cached tables. User Action: If it is an error, drop the cache groups and retry the operation. If it is a warning, verify if the TimesTen and Oracle database schema still match.
5209	Cannot start cache agent because no tns_admin specified during installation - use ttInstanceModify -tns_admin to fix.	Type of Message: Error Cause: You did not specify a value for TNS_ADMIN during the installation of TimesTen. You cannot start a cache agent without specifying the TNS_ADMIN variable. Impact: TimesTen cannot complete the operation. User Action: Specify the TNS_ADMIN variable and retry the operation.
5210	Oracle unique constraint violation error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: A unique constraint violation occurred in the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically. If the problem persists, ensure that the row that is being inserted/updated does not exist on the Oracle database table.
5211	Oracle out of resource error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: An out of resource error occurred on the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically. If the problem persists, ensure that you assign enough resources in the Oracle Database.
5212	No longer connected to Oracle error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: The connection to the Oracle database was lost. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically. If the problem persists, ensure that the Oracle database instance is up and retry the operation.
5213	Bad Oracle login error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: An Oracle database login error occurred. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically. If the problem persists, ensure you are using the correct Oracle credentials.
5214	Not connected to Oracle error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: You attempted to perform a call to Oracle when no connection was established. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically. If the problem persists, check if the Oracle database instance is up and retry the operation.
5215	Oracle resource timeout error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: An Oracle database resource timeout occurred on the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically. If the problem persists, check the accompanying Oracle database error message.
5216	Oracle resource busy error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: Oracle database resource busy. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically.
5217	Oracle deadlock error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: An Oracle database deadlock occurred on Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically.
5218	Bad parameter to Oracle error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: You specified a bad parameter for the named OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically.
5219	Temporary Oracle connection failure error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: A temporary TimesTen Cache failure occurred on the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically. If the problem persists, ensure that the Oracle database instance is up and retry the operation.
5220	Permanent Oracle connection failure error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: A permanent TimesTen Cache failure occurred in the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically. If the problem persists, ensure that the Oracle database instance is up and retry the operation.
5221	Oracle syntax error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: An Oracle database syntax error occurred in the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: If you entered the SQL statement, check the syntax of the statement and retry the operation. Otherwise, check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically.
5222	Oracle constraint violation error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: A constraint violation occurred in the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically.
5223	Oracle orphan violation error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: An orphan violation occurred in the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically.
5224	Oracle foreign key violation error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: A foreign key violation occurred in the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically.
5225	Oracle recovery in progress error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: A recovery in progress error occurred in the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically. If the problem persists, ensure that the Oracle database instance is up and retry the operation.
5226	Oracle data truncation error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: A data truncation error occurred in the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message. If the error message indicates that it is a transient error, the operation will be retried automatically.
5227	Insufficient privileges name occurred while performing an Oracle operation in function: error_message.	Type of Message: Error Cause: An error occurred while performing an Oracle operation because the user has insufficient privileges. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying error message. If the error message indicates that it is a transient error, the operation will be retried automatically. If the problem persists, grant the user the appropriate privileges and retry the operation
5228	A transient mode occurred while performing an Oracle operation in function: error_message.	Type of Message: Error Cause: A temporary error occurred while executing the indicated function. The details are in the error message. The mode is set to error. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying error message. If the error message indicates that it is a transient error, the operation will be retried automatically. If the problem persists, roll back the transaction.
5229	An oracle savepoint error occurred: error_message	Type of Message: Error Cause: You attempted to perform a cache operation that requires TimesTen to set a savepoint on the Oracle database. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying error message. If the error message indicates that it is a transient error, the operation will be retried automatically.
5230	A transient mode occurred while performing an Oracle operation in function: error_message.	Type of Message: Error Cause: A temporary loss of connection to the Oracle database server occurred while executing the indicated function. The details are in the error message. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying error message. If the error message indicates that it is a transient error, the operation will be retried automatically. If the problem persists, roll back the transaction.
5231	Oracle division by zero error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: A division by zero occurred on the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message to determine the cause, address the issue, and retry the operation.
5232	Oracle invalid Rowid error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: An operation using an invalid rowid was attempted on the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message to determine the cause, address the issue, and retry the operation.
5233	Oracle invalid number error/warning in OCI_function: Oracle_error_number	Type of Message: Error Cause: An operation using an invalid number was attempted on the Oracle database in the specified OCI function. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying Oracle database error message to determine the cause of the issue, address the issue, and retry the operation.
5243	The operation cannot be executed if the Replication Agent is not running. Please check the status of the agent.	Type of Message: Error Cause: You attempted to perform an operation, but the replication agent is not running. Impact: TimesTen cannot complete the operation. User Action: Check the status of the replication agent and if it is not running, restart it.
5244	Asynchronous WriteThrough will not be enabled until the Replication Agent for this database has been started.	Type of Message: Warning Cause: Asynchronous writethrough cache groups require the replication agent to be running. The replication agent appears to be stopped. Impact: TimesTen cannot complete the operation. User Action: Restart the replication agent if it is not running.
5245	The operation cannot be executed while the Replication Agent for this database is running.	Type of Message: Error Cause: You attempted to perform an operation while the replication agent for the database was running. Impact: TimesTen cannot complete the operation. User Action: Stop the replication agent and retry the operation.
5246	The Replication Agent for this database is currently running.	Type of Message: Warning Cause: Informational message. Impact: None. User Action: None.
5247	The operation cannot be executed while the cache agent for this database is running.	Type of Message: Error Cause: You attempted to perform an operation while the cache agent for the database was running. Impact: TimesTen cannot complete the operation. User Action: Stop the cache agent and retry the operation.
5249	Awt Initialization Failure: error_message	Type of Message: Error Cause: An error occurred while initializing the asynchronous writethrough thread in the replication agent. Impact: TimesTen cannot complete the operation. User Action: Check the error message for details.
5250	Awt Initialization Failure. Could not compile meta data SQL.	Type of Message: Error Cause: TimesTen attempted to get metadata from the Oracle database. One of TimesTen SQL statements did not compile. Impact: The operation will be retried automatically. User Action: If the problem persists, see other errors in the error log, address them, and then restart the replication agent.
5251	Cache admin uid and pwd must be set since there are awt cache groups in this database. Shutdown the replication agent and the cache agent, set the cache admin uid and pwd, and restart the agents.	Type of Message: Error Cause: You attempted to perform an asynchronous writethrough cache groups operation, but TimesTen does not have the required cache administration user Id and password set. Impact: TimesTen cannot complete the operation. User Action: Set the cache administration user ID and password. Stop the replication agent and the cache agent. Use either the ttCacheUidPwdSet procedure or ttAdmin -cacheUidPwdSet -cacheUid -cachePwd to set the cache administration user ID and password. Restart the agents. For more information, see ttCacheUidPwdSet or ttAdmin in Oracle TimesTen In-Memory Database Reference.
5252	Could not retrieve the cache admin user id and password.	Type of Message: Error Cause: TimesTen found a problem while retrieving the stored cache administration user ID and password. Impact: TimesTen cannot complete the operation. User Action: Review the error log for additional error messages, address them and retry the operation.
5254	Operation failed: Could not find AWT cache group information.	Type of Message: Error Cause: This error can occur during execution of ttAdmin -duplicate. Impact: Information about an asynchronous writethrough cache group could not be found in the TimesTen schema. User Action: Contact TimesTen Customer Support.
5256	Could not find runtime data for AWT	Type of Message: Error Cause: This error can occur during the creation of an asynchronous writethrough cache group. Impact: The replication information for the cache group could not be found. User Action: Retry the operation. If the problem persists, contact TimesTen Customer Support. For more information, see Permanent Oracle Database errors reported by TimesTen in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
5257	Cache admin user and/or password could not be found. Changes via AWT cannot be applied without them.	Type of Message: Error Cause: The cache administration user ID or password is not set or could not be found during the startup of an asynchronous writethrough cache group. Impact: TimesTen cannot complete the operation. User Action: Use ttCacheUidPwdSet to set the cache administration user ID and password, and then restart the replication agent. For more information, see ttCacheUidPwdSet in Oracle TimesTen In-Memory Database Reference.
5258	An update operation tried to update a row that does not exist on Oracle. Expecting number updates and number rows were affected.	Type of Message: Error Cause: You attempted to perform an update operation on rows that are not in the Oracle database tables. Impact: The transaction was rolled back. User Action: Ensure that the Oracle tables and the TimesTen tables are in sync before executing operations on the asynchronous writethrough cache group. For more information, see LOAD CACHE GROUP in Oracle TimesTen In-Memory Database SQL Reference.
5259	Failed to store Awt runtime information for database database_name on Oracle.	Type of Message: Error Cause: TimesTen could not store the state information for Asynchronous WriteThrough . Impact: TimesTen cannot complete the operation. User Action: If the error persists, check the state of the Oracle database server.
5260	Failed to store Awt runtime information for database database_name on Oracle. Wrong number of tuples updated. Should be 1 but number were updated.	Type of Message: Error Cause: The state information for Asynchronous WriteThrough is corrupt. Impact: TimesTen cannot complete the operation. User Action: If the problem persists, contact TimesTen Customer Support.
5261	Failed to read Awt runtime information for database database_name on the Oracle.	Type of Message: Error Cause: TimesTen could not read the state information for AWT Impact: TimesTen cannot complete the operation. User Action: Check the state of the Oracle database server. If the problem persists, contact TimesTen Customer Support.
5262	Could not store the autorefresh bookmarks because the autorefresh state should be 'state' but instead was 'state'.	Type of Message: Error Cause: The system is trying to store bookmarks for AUTOREFRESH when the AUTOREFRESH state is not appropriate. Impact: TimesTen cannot complete the operation. User Action: Specify the correct AUTOREFRESH state and retry the operation. If the problem persists, contact TimesTen Customer Support.
5263	owner_name.table_name is not an autorefresh cache group.	Type of Message: Error Cause: The cache or replication agent tried to store AUTOREFRESH bookmarks on a non-AUTOREFRESH cache group. Impact: TimesTen cannot complete the operation. User Action: If the problem persists, contact TimesTen Customer Support.
5264	Master database state not active or standby. State is state	Type of Message: Error Cause: You attempted to perform an operation without specifying the database ACTIVE or STANDBY state. Impact: TimesTen cannot complete the operation. User Action: Specify the ACTIVE or STANDBY state for the database and retry the operation.
5265	Internal error: error_details	Type of Message: Error Cause: An unknown internal error occurred. See provided message for details. Impact: The severity of the impact is unknown and requires additional diagnosis. User Action: Contact TimesTen Customer Support.
5266	Cache ddl lock request denied because of time-out\nOwner info: message	Type of Message: Error Cause: A timeout occurred while acquiring a lock required for the operation you executed. Impact: TimesTen cannot complete the operation. User Action: Review the specified message as it contains the lock owner information.
5267	The operation failed because the database is marked dead and option_name option is set to value	Type of Message: Error Cause: You attempted to perform an operation without recovering the autorefresh cache groups first. Impact: TimesTen cannot complete the operation. User Action: The autorefresh cache groups must be recovered before the operation can be performed. For more information about autorefresh cache group recovery, see Configuring recovery method for certain cache groups in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
5268	Changing the recovery method to none has caused recovering cache groups to be marked dead for all databases.	Type of Message: Error Cause: You changed the recovery method to none causing all cache groups that were being recovered to be marked as dead. Impact: Cache groups that were being recovered are now marked as dead. User Action: Drop and recreate the cache groups. For more information, see Impact of Failed Autorefresh Operations on TimesTen Databases in Oracle TimesTen In-Memory Database Cache Guide.
5269	owner_name.table_name is not an incrementally autorefresh cache group.	Type of Message: Error Cause: The status can only be shown on incrementally autorefreshed cache group. The indicated table is not an incrementally autorefreshed cache group. Impact: TimesTen cannot complete the operation. User Action: Ensure that the cache group of interest is an incrementally autorefreshed cache group.
5275	Asynchronous writethrough metadata not found string in object_name: error_details	Type of Message: Error Cause: The Asynchronous WriteThrough metadata cannot be found in the object you specified. Impact: TimesTen cannot complete the operation. User Action: Contact TimesTen Customer Support.
5276	Asynchronous writethrough role or state change occurred string in object_name: error_details	Type of Message: Error Cause: TimesTen found an unexpected Active/Standby Pair role or state while executing the current operation. Impact: TimesTen cannot complete the operation. User Action: Review the error details. If the problem persists, contact TimesTen Customer Support.
5277	Timeout while updating active standby metadata on oracle string in object_name: error_details	Type of Message: Error Cause: An error occurred while updating the active standby metadata on Oracle. Impact: TimesTen cannot complete the operation. User Action: Review the error details. If the problem persists, contact TimesTen Customer Support.
5278	Statement over 4000 bytes: statement	Type of Message: Error Cause: Your statement exceeds the maximum allowed size of 4000 bytes. Impact: TimesTen cannot complete the operation. User Action: Modify your statement and retry the operation.
5279	Statement is not allowed when transaction isolation level is set to serializable.	Type of Message: Error Cause: The CREATE, DROP and ALTER CACHE GROUP statements are not allowed with the serializable isolation level. Impact: TimesTen cannot complete the operation. User Action: Reset the transaction isolation level to read-committed isolation and retry the operation.
5280	Autorefresh state of owner_name.cache_group_name is state; autorefresh state must be state.	Type of Message: Error Cause: You specified a cache group that is in the incorrect autorefresh state for the operation you are attempting to perform. Impact: TimesTen cannot complete the operation. User Action: Use the ALTER CACHE GROUP ... SET AUTOREFRESH STATE command to set the autorefresh state as indicated.
5281	Autorefresh of specified cache group is already in progress.	Type of Message: Error Cause: You attempted to initiate a new autorefresh operation while a current autorefresh operation is in progress. This operation is not allowed. Impact: TimesTen cannot complete the operation. User Action: Wait for the current autorefresh operation to complete and retry the operation.
5282	ttCacheAutorefresh cannot be called from the standby of an A/S pair. Call it from the active instead.	Type of Message: Error Cause: You attempted to call the ttCacheAutorefresh built-in procedure from the standby node of an active/standby pair. This operation is not allowed. Impact: TimesTen cannot complete the operation. User Action: Call the ttCacheAutorefresh built-in procedure from the active node.
5283	Autorefresh did not complete within 24 hours	Type of Message: Error Cause: When called with SYNCHRONOUS >1, the ttCacheAutorefresh built-in procedure waits for the autorefresh operation to complete. In this case, the autorefresh operation did not complete within 24 hours. Impact: TimesTen cannot complete the operation. User Action: Check the error log for details.
5284	Error launching autorefresh, see daemon log	Type of Message: Error Cause: The ttCacheAutorefresh built-in procedure encountered an unexpected error while initiating the autorefresh operation. Impact: TimesTen cannot complete the operation. User Action: Check the error log for details.
5285	Autorefresh failed, see daemon log	Type of Message: Error Cause: The ttCacheAutorefresh built-in procedure encountered an unexpected error while initiating the autorefresh operation. Impact: The autorefresh failed. User Action: Check the daemon log for details.
5286	Autorefresh activity has occurred so rapidly that the history of the requested autorefresh has been overwritten by subsequent autorefreshes before it could be retrieved. There is not necessarily any problem. Check the daemon log for the status of the requested refresh.	Type of Message: Error Cause: The TimesTen cache agent keeps a history of the 10 most recent autorefresh operations. The autorefresh operation that you initiated with the ttCacheAutorefresh built-in procedure has completed. Before its status could be read from the autorefresh history, it was displaced by another autorefresh operation that occurred at an unusually high rate. Impact: The autorefresh operation you initiated may have completed successfully. User Action: Check the daemon log for the status of your autorefresh operation.
5287	Unexpected status returned by autorefresh, see daemon log	Type of Message: Error Cause: The ttCacheAutorefresh built-in procedure encountered an unexpected status return value from the autorefresh operation. Impact: TimesTen cannot complete the operation. User Action: Check the daemon log for details.
5288	Autorefresh failed due to contact lost with Oracle (dead cache group)	Type of Message: Error Cause: The connection to the Oracle database was lost. Impact: The autorefresh operation failed User Action: Check the status of the Oracle database and retry the operation.
5289	Operation failed because user_name lacks Oracle RDBMS privilege privilege_name. Message	Type of Message: Error Cause: You attempted to perform an operation with a user that does not have the RDBMS privilege privilege_name. Impact: TimesTen cannot complete the operation. User Action: Grant the user the appropriate privilege within the Oracle database.
5293	Propagation will be serialized for AWT cache table owner_name.table_name because the following Oracle unique indexes and constraints on this table contain cached columns that do not have corresponding unique indexes and constraints on TimesTen: constraints_list.	Type of Message: Warning Cause: The specified unique constraints and indexes on the cached Oracle database table do not have corresponding unique indexes and constraints on TimesTen. Impact: Transactions that contain DML to the specified table will not be propagated in parallel to the Oracle database. This will impact the throughput to the Oracle database. User Action: Ensure that the unique constraints and indexes on the cached Oracle database have corresponding unique indexes and constraints on the TimesTen table.
5294	For Oracle tables that are cached in an AWT cache group, propagation will be serialized because there are Oracle tables with unique indexes and constraints that do not have corresponding unique indexes and constraints on TimesTen.	Type of Message: Warning Cause: Some unique constraints and indexes on the cached Oracle database table do not have corresponding unique indexes and constraints on TimesTen. Impact: Transactions that contain DML will not be propagated in parallel to the Oracle database. This will impact the throughput to the Oracle database. User Action: Ensure that the unique constraints and indexes on the cached Oracle database have corresponding unique indexes and constraints on the TimesTen table.
5295	Propagation will be serialized on AWT cache table owner_name.table_name because the following Oracle foreign key constraints on this table contain cached columns that do not have corresponding foreign key constraints on TimesTen: fk_constraints_list.	Type of Message: Warning Cause: The specified foreign key constraints on the cached Oracle database table do not have corresponding foreign key constraints on TimesTen. Impact: Transactions that contain DML to the specified table will use serialized propagation to the Oracle database. This will impact the throughput to the Oracle database. User Action: To ensure the best throughput to the Oracle database, recreate the TimesTen cache group using the foreign key constraint. If you cannot recreate the TimesTen cache group, transactions will use serialized propagation to the Oracle database. For more information on dropping a TimesTen cache group, see Dropping a Cache Group in Oracle TimesTen In-Memory Database Cache Guide. For more information on creating a cache group, see Creating a Cache Group in Oracle TimesTen In-Memory Database Cache Guide.
5296	Propagation will be serialized on AWT cache table owner_name.table_name because the following Oracle unique indexes, unique or foreign key constraints on this table contain cached columns that do not have corresponding constraints on TimesTen: constraints_list.	Type of Message: Warning Cause: The specified unique indexes, unique constraints and foreign key constraints on the cached Oracle database table do not have corresponding constraints on TimesTen. Impact: Transactions that contain DML to the specified table will use serialized propagation to the Oracle database. This will impact the throughput to the Oracle database. User Action: Ensure that the unique constraints and indexes on the cached Oracle database have corresponding unique indexes and constraints on the TimesTen table. To ensure the best throughput to the Oracle database, recreate the TimesTen cache group using the foreign key constraint. If you cannot recreate the TimesTen cache group, transactions will use serialized propagation to the Oracle database. For more information on dropping a TimesTen cache group, see Dropping a Cache Group in Oracle TimesTen In-Memory Database Cache Guide. For more information on creating a cache group, see Creating a Cache Group in Oracle TimesTen In-Memory Database Cache Guide.
5297	The following Oracle foreign key constraints on AWT cache table owner_name.table_name contain cached columns that do not have corresponding foreign key constraints on TimesTen: constraint_name.	Type of Message: Informational Cause: The specified table on the cached Oracle database has a foreign key constraint that does not have corresponding foreign key constraint on TimesTen. Impact: None. User Action: None.
5298	Propagation will be serialized because there are Oracle tables with unique indexes, unique or foreign key constraints that are cached in an AWT cache group with parallel propagation enabled that do not have the corresponding constraint on TimesTen.	Type of Message: Warning Cause: Some unique indexes, unique constraints and foreign key constraints on the cached Oracle database table do not have corresponding constraints on TimesTen. Impact: Transactions that contain DML to the specified table will use serialized propagation to the Oracle database. This will impact the throughput to the Oracle database. User Action: Ensure that the unique constraints and indexes on the cached Oracle database have corresponding unique indexes and constraints on the TimesTen table. To ensure the best throughput to the Oracle database, recreate the TimesTen cache group using the foreign key constraint. If you cannot recreate the TimesTen cache group, transactions will use serialized propagation to the Oracle database. For more information on dropping a TimesTen cache group, see Dropping a Cache Group in Oracle TimesTen In-Memory Database Cache Guide. For more information on creating a cache group, see Creating a Cache Group in Oracle TimesTen In-Memory Database Cache Guide.
5299	There are Oracle tables with unique indexes, unique or foreign key constraints that are cached in an AWT cache group with parallel propagation enabled that do not have the corresponding constraint on TimesTen.	Type of Message: Informational Cause: Some Oracle database tables have unique indexes, unique constraints, or unique foreign key constraints that do not have corresponding on TimesTen. Impact: None. User Action: None.
5300	Parameter bindings are not allowed in the select statement	Type of Message: Error Cause: The Oracle database select query you specified for the built-in procedure or command contains parameter bindings. Parameter bindings are not supported by the ttTableSchemaFromOraQueryGet built-in procedure, the ttLoadFromOracle built-in procedure, and the createAndLoadfromOraQuery command. Impact: The call to the built-in procedure or command failed. User Action: Remove the parameter bindings from the Oracle database select query and call the built-in procedure or command. For more information on the ttTableSchemaFromOraQueryGet and ttLoadFromOracle built-in procedures and createAndLoadfromQuery command, see ttTableSchemaFromOraQueryGet, ttLoadFromOracle, and ttIsql, respectively, in the Oracle TimesTen In-Memory Database Reference.
5301	The Load From Oracle feature cannot be used to load cache group tables	Type of Message: Error Cause: The TimesTen table you specified for the built-in procedure or command is part of a cache group. The ttTableSchemaFromOraQueryGet built-in procedure, the ttLoadFromOracle built-in procedure, and the createAndLoadfromOraQuery command do not support Loading into TimesTen cache group tables. Impact: The call to the built-in procedure or command failed. User Action: Specify a table that is not part of a cache group and call the built-in procedure or command. For more information on the ttTableSchemaFromOraQueryGet and ttLoadFromOracle built-in procedures and createAndLoadfromQuery command, see ttTableSchemaFromOraQueryGet, ttLoadFromOracle, and ttIsql, respectively, in the Oracle TimesTen In-Memory Database Reference.
5302	The Load From Oracle feature cannot be used with passthrough level 3	Type of Message: Error Cause: The PassThrough attribute of the TimesTen Cache is set to 3. Impact: The call to the built-in procedure or command failed. User Action: Specify a PassThrough level that is not 3 for the TimesTen Cache and call the built-in procedure or command. For more information on PassThrough levels, see PassThrough in Oracle TimesTen In-Memory Database Reference. For more information on the ttTableSchemaFromOraQueryGet and ttLoadFromOracle built-in procedures and createAndLoadfromQuery command, see ttTableSchemaFromOraQueryGet, ttLoadFromOracle, and ttIsql, respectively, in the Oracle TimesTen In-Memory Database Reference.
5303	Create table statement generated is too long	Type of Message: Error Cause: The built-in procedure or command generated a CREATE TABLE statement that exceeds the maximum length for a SQL statement. The CREATE TABLE statement was generated by the ttTableSchemaFromOraQueryGet built-in, or the ttLoadFromOracle built-in, or the createAndLoadfromOraQuery command. Impact: The generated CREATE TABLE statement cannot be executed. User Action: Modify the Oracle database SQL statement to shorten the length of the generated CREATE TABLE statement and call the built-in procedure or command. For more information on system limits, see System Limits and Defaults in Oracle TimesTen In-Memory Database Reference. For more information on the ttTableSchemaFromOraQueryGet and ttLoadFromOracle built-in procedures and createAndLoadfromQuery command, see ttTableSchemaFromOraQueryGet, ttLoadFromOracle, and ttIsql, respectively, in the Oracle TimesTen In-Memory Database Reference.
5304	The Load From Oracle feature cannot be used to load LOB columns	Type of Message: Error Cause: The TimesTen table you specified for the built-in procedure or command contains LOB data types. TimesTen tables that contain LOB data types are not supported by the ttTableSchemaFromOraQueryGet built-in, the ttLoadFromOracle built-in, and the createAndLoadfromOraQuery command. Impact: The call to the built-in procedure or command failed. User Action: Remove or change the LOB data types to a supported type and call the built-in procedure or command. For more information on the ttTableSchemaFromOraQueryGet and ttLoadFromOracle built-in procedures and createAndLoadfromQuery command, see ttTableSchemaFromOraQueryGet, ttLoadFromOracle, and ttIsql, respectively, in the Oracle TimesTen In-Memory Database Reference.
5305	Oracle query does not match TimesTen table schema. Mismatched number of columns between the TimesTen table (number columns) and Oracle query (number columns)	Type of Message: Error Cause: The number of columns in the TimesTen table does not match the number in the Oracle database query result set. The mismatch was detected when you executed the ttTableSchemaFromOraQueryGet built-in, or the ttLoadFromOracle built-in, or the createAndLoadfromOraQuery command. Impact: The call to the built-in procedure or command failed. User Action: Examine the TimesTen table and the Oracle database query to resolve the mismatch. Then call the built-in procedure or command. For more information on the ttTableSchemaFromOraQueryGet and ttLoadFromOracle built-in procedures and createAndLoadfromQuery command, see ttTableSchemaFromOraQueryGet, ttLoadFromOracle, and ttIsql, respectively, in the Oracle TimesTen In-Memory Database Reference.
5306	The Oracle statement must be a valid select query.	Type of Message: Error Cause: The Oracle database statement you provided is not a valid select query. The Oracle database statement must be a valid select query to use the ttTableSchemaFromOraQueryGet built-in, or the ttLoadFromOracle built-in, or the createAndLoadfromOraQuery command. Impact: The call to the built-in procedure or command failed. User Action: Ensure that the Oracle database statement is a valid select query and call the built-in procedure or command. For more information on the ttTableSchemaFromOraQueryGet and ttLoadFromOracle built-in procedures and createAndLoadfromQuery command, see ttTableSchemaFromOraQueryGet, ttLoadFromOracle, and ttIsql, respectively, in the Oracle TimesTen In-Memory Database Reference.
5307	The Load From Oracle feature cannot be used to load materialized view tables or detail tables of views	Type of Message: Error Cause: You attempted to load data into a TimesTen materialized view or a detailed view using the built-in or command. Loading data into TimesTen materialized views and detailed views is not supported by the ttTableSchemaFromOraQueryGet built-in, the ttLoadFromOracle built-in, and the createAndLoadfromOraQuery command. Impact: The call to the built-in procedure or command failed. User Action: Loading data into TimesTen materialized views and detailed views is not supported by the ttTableSchemaFromOraQueryGet built-in, or the ttLoadFromOracle built-in, or the createAndLoadfromOraQuery command. For more information on the ttTableSchemaFromOraQueryGet and ttLoadFromOracle built-in procedures and createAndLoadfromQuery command, see ttTableSchemaFromOraQueryGet, ttLoadFromOracle, and ttIsql, respectively, in the Oracle TimesTen In-Memory Database Reference.
5308	The Load From Oracle feature cannot be used to load temporary tables	Type of Message: Error Cause: You attempted to load data into a TimesTen temporary table using the built-in or command. Loading data into TimesTen temporary tables is not supported by the ttTableSchemaFromOraQueryGet built-in, the ttLoadFromOracle built-in, and the createAndLoadfromOraQuery command. Impact: The call to the built-in procedure or command failed. User Action: Loading data into TimesTen temporary tables is not supported by the ttTableSchemaFromOraQueryGet built-in, or the ttLoadFromOracle built-in, or the createAndLoadfromOraQuery command. For more information on the ttTableSchemaFromOraQueryGet and ttLoadFromOracle built-in procedures and createAndLoadfromQuery command, see ttTableSchemaFromOraQueryGet, ttLoadFromOracle, and ttIsql, respectively, in the Oracle TimesTen In-Memory Database Reference.
5309	The Load From Oracle feature cannot be used to load dictionary tables	Type of Message: Error Cause: You attempted to load data into a TimesTen dictionary table. Loading data into TimesTen dictionary tables is not supported by the ttTableSchemaFromOraQueryGet built-in, the ttLoadFromOracle built-in, and the createAndLoadfromOraQuery command. Impact: The call to the built-in procedure or command failed. User Action: Loading data into TimesTen dictionary tables is not supported by the ttTableSchemaFromOraQueryGet built-in, or the ttLoadFromOracle built-in, or the createAndLoadfromOraQuery command. For more information on dictionary tables, see the Store Data Efficiently with Column-Based Compression of Tables in Oracle TimesTen In-Memory Database Operations Guide. For more information on the ttTableSchemaFromOraQueryGet and ttLoadFromOracle built-in procedures and createAndLoadfromQuery command, see ttTableSchemaFromOraQueryGet, ttLoadFromOracle, and ttIsql, respectively, in the Oracle TimesTen In-Memory Database Reference.
5311	AWT cache group with parallel propagation enabled constraint check: Object_type owner_name.table_name: status	Type of Message: Informational Cause: This informational message is in the daemon log while the constraint check is being performed. Impact: None. User Action: None.
5313	Load From Oracle Error: Data truncated for table table_name, column column_name, value value...	Type of Message: Error Cause: TimesTen encountered a truncation error while trying to insert data from the Oracle database into the specified TimesTen column. The specified value might be a partial value. Impact: The load operation is terminated. The load operation periodically commits and successful operations are not rolled back. Some data might have been imported into TimesTen before the operation terminated. User Action: Modify the Oracle database query, or the TimesTen table, or both to ensure that the Oracle database data can be loaded into the specified TimesTen table. To retry a failed parallel load operation, delete previously inserted rows from the TimesTen table to avoid duplicate rows.
5314	Load From Oracle Warning: Cannot check for truncation of char/nchar columns for this load.	Type of Message: Warning Cause: The Oracle database statement you specified could not be checked for truncation of CHAR and NCHAR values. Common causes for this are: The Oracle database statement you specified might contain an ORDER BY clause. The Oracle database statement you specified might exceed maximum query length once TimesTen rewrites the statement to be used by the ttLoadFromOracle built-in or the createAndLoadfromOraQuery command. Impact: CHAR and NCHAR column values may be truncated by the ttLoadFromOracle built-in or the createAndLoadfromOraQuery command. User Action: Review the daemon log for more details about the warning. If you require TimesTen to check for CHAR or NCHAR truncation, ensure that the column lengths in the Oracle database and TimesTen are the same. For more information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
5315	Error creating the tuple buffer queue	Type of Message: Error Cause: Failed to allocate memory to create tuple buffer queue Impact: Load failed User Action: Free up system memory on the host and try again.
5316	Error enqueuing a page into the tuple buffer queue	Type of Message: Error Cause: Failed to allocate memory to enqueue the tuple Impact: Load failed User Action: Free up system memory on the host and try again.
5319	The table definition for the Oracle table(s) are not old enough to perform a flashback query (Oracle Error - error_number). The TimesTen table may have been partially loaded.	Type of Message: Error Cause: The table definitions for the Oracle tables are not old enough to perform a flashback query. Impact: The TimesTen table may have been partially loaded. User Action: Wait at least 5 minutes after the tables have been created or altered on the Oracle database and retry the operation. Otherwise, you may re-run the load without a flashback query ('numFetchers=1', 'ResumeFromSCN' not specified).
5321	Could not get the maximum reclaim cache size configuration parameter	Type of Message: Error Cause: The cache agent could not retrieve the maximum reclaim cache size configuration parameter. Review the daemon log for any additional error messages to determine a cause for the failure. For more information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide. Impact: The cache agent will retry this operation later. Review the daemon log for any additional impacts. User Action: Review the daemon log for any how to proceed.
5322	Could not set the maximum reclaim cache size for the session	Type of Message: Error Cause: The cache agent could not set the maximum reclaim cache size for the session. Impact: The cache agent will retry this operation later. User Action: None.
5323	Maximum reclaim cache size set to number for receiver_thread_track_id	Type of Message: Informational Cause: The maximum reclaim cache size is now set to the specified value. Impact: None. User Action: None.
5324	There was an error while getting the statistics for interval numberms: error_message	Type of Message: Error Cause: An error occurred while retrieving the autorefresh statistics for the specified interval. A detailed error message follows this message. Impact: The autorefresh statistics are not returned. User Action: Review the error message for how to proceed.
5325	Deferring autorefresh because of unmarked records in log table table_name. (marked, unmarked, eoLog) = (number, number, end_of_log)	Type of Message: Informational Cause: Too many unmarked autorefresh change log records exist in the specified log table. Impact: The autorefresh operation for the TimesTen cache group is temporarily deferred. User Action: None.
5326	String setting must be less than the total temporary space size (numberMB)	Type of Message: Error Cause: You specified a maximum reclaim buffer size for the cache agent that is greater than the total temporary space size. Impact: The specified reclaim buffer size for the cache agent is not set. User Action: Use the CacheAgentCommitBufSize parameter of the ttDBConfig built-in procedure to specify a reclaim buffer size that is less than the total temporary space size. For more information about the ttDBConfig built-in procedure, see ttDBConfig in Oracle TimesTen In-Memory Database Reference.
5327	High number of unmarked records in change log table change_log_table. (marked, unmarked, eoLog) = (marked_number, unmarked_number, eoLog_number)	Type of Message: Warning Cause: You disabled marking in the refresher thread of the cache agent and a high number of rows have not been marked in the change log table. Impact: A possible reduced performance in autorefresh operations. User Action: Consider re-enabling the marking in the refresher thread of the cache agent.
5328	Invalid option passed to ttLoadFromOracle: error_message.	Type of Message: Error Cause: You attempted to call the ttLoadFromOracle built-in procedure while specifying an invalid option. Impact: TimesTen did not complete the loading operation. User Action: Review and modify the options specified and re-call the ttLoadFromOracle built-in procedure. For more information on ttLoadFromOracle built-in procedure, see ttLoadFromOracle in Oracle TimesTen In-Memory Database Reference.
5329	If the readers clause is specified, the parallel clause must also be specified.	Type of Message: Error Cause: You attempted to execute a LOAD or REFRESH CACHE GROUP statement and failed to specify the PARALLEL clause in conjunction with the READERS clause. Impact: TimesTen did not complete the load or refresh cache group operation. User Action: Specify a PARALLEL clause and retry the LOAD or REFRESH CACHE GROUP statement. For more information on the LOAD or REFRESH CACHE GROUP statement, see LOAD CACHE GROUP or REFRESH CACHE GROUP, respectively, in the Oracle TimesTen In-Memory Database SQL Reference.
5330	Readers value must be at least one	Type of Message: Error Cause: You attempted to execute a LOAD or REFRESH CACHE GROUP statement while specifying a value for the READERS clause that is lower than one. Impact: TimesTen did not complete the load or refresh cache group operation. User Action: Specify a value of at least one for the READERS clause and retry the LOAD or REFRESH CACHE GROUP statement. For more information on the LOAD or REFRESH CACHE GROUP statement, see LOAD CACHE GROUP or REFRESH CACHE GROUP, respectively, in the Oracle TimesTen In-Memory Database SQL Reference.
5331	At least one unique index must be defined on the table with option 'ignoreDuplicates=Y' or 'ResumeFromSCN=nnnn'.	Type of Message: Error Cause: You attempted to call the ttLoadFromOracle built-in procedure on a TimesTen table with no unique indexes defined and specified either of the following options. - ignoreDuplicates=Y - ResumeFromSCN Impact: TimesTen did no complete the loading operation. User Action: Retry the loading operation after either creating one or more unique indexes on the TimesTen table or removing both the ignoreDuplicates=Y and ResumeFromSCN options from the ttLoadFromOracle built-in procedure. For more information on ttLoadFromOracle built-in procedure, see ttLoadFromOracle in Oracle TimesTen In-Memory Database Reference.
5332	Refresher Lock: Threshold: threshold, number of autorefresh intervals in the grid: num_total_refreshers, number of running cache agents in the grid: num_active_agents, Number of refresh intervals handled by this cache agent: num_own_refreshers, Refresher Available: refresher_available.	Type of Message: Informational Cause: The refresher thread determines whether it should manage the refreshes for the readonly cache groups in its interval. These are some relevant numbers used in this calculation. Impact: None. User Action: None.
5333	Could not create a refresher lock environment.	Type of Message: Error Cause: TimesTen failed to create an internal structure for managing the refresher lock. Impact: Autorefresh cannot initiate. User Action: Review additional error messages and restart the cache agent.
5334	Could not prepare required sql statements for the refresher lock environment.	Type of Message: Error Cause: TimesTen failed to prepare the sql statements required for handling the refresher lock. Impact: Autorefresh cannot initiate. User Action: Review additional error messages and restart the cache agent.
5335	Invalid state in refresher lock environment. Interval: interval, current state: state.	Type of Message: Error Cause: A bad state was found in the refresher lock environment when trying to transition to another state. Impact: The operation using the refresher lock cannot continue. User Action: Review additional error messages and restart the cache agent if required.
5336	Could not acquire the refresher lock. Interval: interval, current state: state.	Type of Message: Error Cause: An error ocurred while trying to acquire the refresher lock for the mentioned interval. Impact: The operation using the refresher lock cannot continue. User Action: Review additional error messages and restart the cache agent if required.
5337	Could not release the refresher lock. Interval: interval, current state: state.	Type of Message: Error Cause: An error ocurred while trying to release the refresher lock for the mentioned interval. Impact: The operation using the refresher lock cannot continue. User Action: Review additional error messages and restart the cache agent if required.
5338	The refresher lock for interval interval is currently held by another agent.	Type of Message: Informational Cause: The refresher for the mentioned interval is currently held by another cache agent. Impact: The refresher will keep trying to acquire the lock automatically. User Action: None.
5339	The refresher lock for interval interval was successfully acquired. Active refreshers in this cache agent: num_active_refreshers.	Type of Message: Informational Cause: The refresher for the mentioned interval is currently held by this cache agent. Impact: None. User Action: None.
5340	Failed to set failover parameters in refresher lock environment. Interval: interval.	Type of Message: Error Cause: A problem was found while setting the failover parameters in the refresher lock environment. Impact: Autorefresh for the mentioned interval cannot proceed in this cache agent. User Action: Review additional error messages and restart the cache agent if required.
5341	Skipping load balancing calculation. Cache agents running: num_cache_agents_running, Refreshers running for this cache agent: num_refresher_threads_running.	Type of Message: Warning Cause: There are not enough cache agents running in the grid or refresher threads in this cache agent to perform the calculation of the load balancing threshold. Impact: The refresher thread emitting this message will not perform autorefresh. User Action: None.
5342	Refresher lock released for interval autorefresh_interval. Active refreshers in this cache agent: num_active_refreshers.	Type of Message: Informational Cause: The refresher lock for the interval was released. Impact: Another refresher thread will now be able to perform autorefresh for this interval. User Action: None.
5343	A refresher thread was spawned for interval autorefresh_interval. Number of refreshers in this cache agent: num_active_refreshers.	Type of Message: Informational Cause: A new refresher thread was spawned for the mentioned interval. Impact: The new refresher thread is a candidate for actively refreshing cache groups in the interval. User Action: None.
5344	The refresher thread for interval autorefresh_interval is about to exit. Number of refreshers in this cache agent: num_active_refreshers.	Type of Message: Informational Cause: The refresher thread that was spawned to handle the mentioned interval is about to exit. Impact: The cache agent that spawned the refresher thread will no longer be able to handle cache groups in the mentioned autorefresh interval. User Action: None.
5345	Another refresher lock is currently being released. Autorefresh for interval autorefresh_interval will still be handled by this refresher thread.	Type of Message: Warning Cause: Another refresher thread was releasing a refresher lock. Impact: Only one refresher lock can be released at a time. User Action: None.
5346	Handling Autorefresh for interval for interval autorefresh_interval ms.	Type of Message: Informational Cause: The indicated autorefresh interval is being handled by this autorefresh thread for the entire grid. Impact: None. User Action: None.
5347	Attempting to reacquire refresher lock for interval interval ms, current state: state, current number of active refreshers: num_active_refreshers.	Type of Message: Warning Cause: An Oracle database failover event ocurred while autorefresh was in progress. Impact: TimesTen will attempt to get the autorefresh lock again before continuing the current autorefresh. User Action: None.
5800	Could not allocate a statement handle.	Type of Message: Error Cause: The TimesTen cache agent was not able to allocate either an Oracle database or TimesTen statement handle. Impact: TimesTen cannot complete the operation. User Action: Check the user error log for more details.
5801	Could not get a column attribute.	Type of Message: Error Cause: The TimesTen cache agent was not able to get information about the columns in a table. Impact: The operation that the agent was performing failed. User Action: Check the user error log for more details.
5802	This cache group type is not supported in an Oracle Active Data Guard with Asynchronous Transport environment	Type of Message: Error Cause: You attempted to create a cache group that is currently not supported to work with an Oracle ADG environment. Impact: TimesTen cannot create the cache group. User Action: Consider using another type of cache group or another Oracle Database configuration.
5803	All cache groups must be created before creating the Active Standby scheme when using an Oracle Active Data Guard with Asynchronous Transport environment.	Type of Message: Error Cause: You attempted to create a cache group after having created the Active Standby Pair replication scheme. Impact: TimesTen cannot create the cache group. User Action: Drop the active standby pair replication scheme. Then, retry creating the cache group.
5804	Oracle transaction could not continue after Oracle Database failover.	Type of Message: Error Cause: An Oracle Database failover occurred while executing a transaction. Impact: TimesTen cannot execute the transaction. TimesTen rolls back and retries the transaction automatically. User Action: None.
5901	The Oracle refresh log table, table_name, for base table, owner_name.table_name, cannot be found.	Type of Message: Error Cause: The log table table_name for autorefresh of the table owner_name.table_name cannot be found. It may be that the cache administrator user does not have sufficient privileges to read the log table. Impact: TimesTen cannot complete the operation. User Action: Ensure that the cache administration user has the appropriate privileges and retry the operation.
5902	Internal error: The length of the name of the Oracle object has exceeded the expected length.	Type of Message: Internal Error Cause: The length of the name of the Oracle database object has exceeded the expected length. Impact: The severity of the impact is unknown and requires additional diagnosis. User Action: Contact TimesTen Customer Support.
5903	Autorefresh log table was truncated during incremental refresh. Full refresh will take place.	Type of Message: Error Cause: Rows in the autorefresh log table were deleted during an incremental refresh. Impact: TimesTen is performing a full refresh to recover the autorefresh log table. User Action: Do not delete rows from the TimesTen internal tables TT_XX_YYYY, where XX is the two digit version number and YYYY is the assigned TimesTen name.
5907	The cache admin user id was not set before performing the operation.	Type of Message: Error Cause: You attempted to perform an operation without setting the cache administrator user ID first. Impact: TimesTen cannot complete the operation. User Action: For TimesTen Classic, set the cache administrator user ID and password by using either the ttCacheUidPwdSet procedure or the ttAdmin utility and retry the operation. For TimesTen Scaleout, use the ttGridAdmin dbCacheCredentialSet command instead.
5911	Could not login into Oracle using the cache admin user id and password.	Type of Message: Error Cause: You provided an invalid cache administration user ID and password. Impact: The TimesTen cache agent was not able to login into the Oracle database. User Action: Check if the cache administration user ID and password are valid on the Oracle Net Service Name that you specified for the DSN.
5914	not found in Oracle.	Type of Message: Error Cause: You attempted to cache an Oracle database table that cannot be found. Impact: The TimesTen cache agent could not find the Oracle database table to be cached. User Action: Check if the table exists in the Oracle database. Also verify that the cache administration user ID has the privilege to access the table.
5917	Object id object_id not found or the user user_name does not have sufficient privilege to view the object	Type of Message: Error Cause: Possible causes for this error message are: The Oracle database table that was cached has been dropped in the Oracle database. If this error is returned in response to a CREATE CACHE GROUP statement, the specified Cache Agent account does not have the appropriate privileges. Impact: TimesTen cannot complete the operation. User Action: Verify that the Cache Agent account you specified has the appropriate privileges. See Grant Privileges to the Oracle Cache Administration User in Oracle TimesTen In-Memory Database Cache Guide for details.
5918	Log table table_name not found or the user user_name does not have sufficient privilege to view the log table	Type of Message: Error Cause: You specified an autorefresh log table that could not be found on the Oracle database or the specified cache agent account does not have the appropriate privileges. Impact: TimesTen cannot complete the operation. User Action: Check if you specified the correct table name and that the user user_name has the appropriate privileges. See Grant Privileges to the Oracle Cache Administration User in Oracle TimesTen In-Memory Database Cache Guide for details.
5919	The object_type object_name is different from when the cache was created or no longer exists. The cache group definition is no longer valid.	Type of Message: Error Cause: You specified an Oracle database object with name object_name that is different from when the cache was created or that no longer exists. Impact: TimesTen cannot complete the operation. User Action: Verify that the Oracle objects associated with the cache group have not been modified.
5921	Could not connect to Oracle. Please check the status of the Oracle instance.	Type of Message: Error Cause: The TimesTen cache agent could not connect to the Oracle database. Impact: TimesTen cannot complete the operation. User Action: Verify that the Oracle database instance exists and that it is up and running.
5922	The minimum stop timeout value is number which will be used instead of number.	Type of Message: Warning Cause: You specified a timeout value for the ttCacheStop procedure that is too small. The default value is used. Impact: Autorefresh does not start until able to connect. User Action: Check the user error log for any errors.
5923	Cache agent has deferred the create/alter cache group request because it is not connected to Oracle yet	Type of Message: Warning Cause: Your CREATE, ALTER or DROP CACHE GROUP statement cannot be completed because the cache agent is still waiting to connect to the Oracle database. Impact: TimesTen cannot complete the operation. User Action: Verify that the Oracle database instance is running and the network connection is also available. Check the user error log for any errors.
5925	Cache admin user does not have privilege to create trigger_name trigger. Grant CREATE ANY TRIGGER privilege or use ttCacheSqlGet built-in to manually create the trigger	Type of Message: Error Cause: The cache administrator does not have Oracle database CREATE TRIGGER privileges. Impact: The operation failed. User Action: Either grant the privilege to the cache administrator user ID or use the ttCacheSqlGet built-in procedure to manually execute the SQL statement. For more information on this procedure, see ttCacheSqlGet in Oracle TimesTen In-Memory Database Reference.
5926	An error occurred while processing a child table	Type of Message: Error Cause: TimesTen autorefreshed a child table before the parent table from a multi-table cache group causing a foreign key violation. Impact: The autorefresh cycle fails. TimesTen will retry the autorefresh operation. User Action: None.
5935	Could not validate Oracle login: uid = user_id, pwd = HIDDEN, OracleNetServiceName = service_name, TNS_ADMIN = \"path\", ORACLE_HOME= \"path\"	Type of Message: Error Cause: TimesTen Cache failed to verify the Oracle database login for named user ID.The common causes of this error are: The specified UID/PWD is incorrect. The OracleNetServiceName setting is incorrect. The Oracle database listener is down. The Oracle database is down. Impact: TimesTen cannot complete the operation. User Action: Troubleshoot the causes and then retry the operation.
5936	Need to specify both cache admin uid and pwd or neither of them when starting the cache agent.	Type of Message: Error Cause: You omitted the cache administration user ID or password when calling the deprecated built-in procedure ttOracleAgentStart. Impact: TimesTen cannot complete the operation. User Action: Provide the cache administration user ID or password when calling the deprecated built-in procedure ttOracleAgentStart, and then retry the operation.
5938	owner_name.object_name or owner_name.object_name table does not exist on Oracle. Oracle objects related to cache groups may not get cleaned up	Type of Message: Error Cause: TimesTen found that some oracle objects associated with the cache group are missing. Impact: TimesTen cannot complete the operation. User Action: Drop and recreate the cache groups in TimesTen.
5940	The operation failed because the cache admin uid could not be verified. Please reconnect and try again.	Type of Message: Error Cause: The cache group operation requires that you first start the cache with the assigned cacheUid and cachePwd. Impact: TimesTen cannot complete the operation. User Action: Restart the cache agent with the correct cache administration user ID and password, and reconnect the application.
5941	Cache admin uid has been changed from user_id to user_id. Switching over to the new uid.	Type of Message: Warning Cause: You changed the cache administration user ID. Impact: TimesTen switches over to the new administration user ID. User Action: Verify that the cache agent is started with a new cacheUid.
5942	The specified cache admin uid (user_id) and pwd (hidden) does not match the stored ones. Please use ttCacheUidPwdSet() to change the stored ones.	Type of Message: Error Cause: The cache administration user ID and password you provided do not match the stored cache administration user ID and password. Impact: TimesTen cannot complete the operation. User Action: Change the stored cache administration user ID and password with the ttCacheUidPwdSet procedure. For more information, see ttCacheUidPwdSet in Oracle TimesTen In-Memory Database Reference.
5943	The source database cache admin uid (user_id) is different from the destination database cache admin uid (user_id)	Type of Message: Error Cause: The source database cache administration user ID you provided is different from the destination database administration user ID. Impact: TimesTen cannot complete the operation. User Action: Ensure that the cache administration user ID is the same on the source database and the destination database.
5947	Cache admin UID and PWD need to be specified for database duplication because there are AUTOREFRESH or ASYNCHRONOUS WRITETHROUGH cache groups	Type of Message: Error Cause: You did not specify the cache administration user ID and password when duplicating a database that contains AUTOREFRESH or Asynchronous WriteThrough (AWT) cache groups. Impact: TimesTen cannot complete the operation. User Action: Specify the cache administration user ID and password and retry the operation.
5948	Subscribing databases in Active Standby schemes must specify -noKeepCg	Type of Message: Error Cause: When duplicating databases that contain Active Standby schemes, cache group tables cannot be maintained as cache group tables. Impact: TimesTen cannot complete the operation. User Action: Specify the -noKeepCG option with ttRepAdmin -duplicate. and retry the operation.
5949	Cache agent uid (user_id) is different from the database cache uid (user_id)	Type of Message: Error Cause: The cache agent user id is different from the database cache user name. Impact: The users involved in caching transactions between the TimesTen and Oracle databases must be identical. User Action: Ensure that the TimesTen cache agent user name is identical to the Oracle database cache user name. Make sure that you set the TimesTen cache administration user name and password with the ttCacheUidPwdSet built-in procedure. See Registering the Cache Administration User Name and Password in Oracle TimesTen In-Memory Database Cache Guide.
5950	Lack Oracle privileges to create metadata objects on Oracle. Either grant appropriate privileges to cache admin user and try again or install the objects manually.	Type of Message: Warning Cause: You do not have the appropriate privileges on the Oracle database to create the requested objects. Impact: Some objects required for Cache Connect feature may be missing. User Action: Either obtain the appropriate privileges or manually install the objects.
5952	Metadata objects on Oracle are missing. Either grant appropriate privileges to cache admin user to create the objects and re-execute ttCacheUidPwdSet or install the objects manually.	Type of Message: Error Cause: The cache administration user does not have the appropriate Oracle database privileges to create and store metadata information on the Oracle database server. Impact: TimesTen cannot complete the operation. User Action: Either grant the appropriate privileges to the cache administration user on the Oracle database server or manually install the metadata objects.
5953	The object_type object_id is different from when the cache was created or could not be found. Check if you have SELECT privileges to the table on Oracle Db. If you have privileges, then the cache group definition is no longer valid.	Type of Message: Error Cause: If you have SELECT privileges to the table on the Oracle database server, then the cache group is no longer valid. Impact: TimesTen cannot complete the operation. User Action: Recreate the cache group.
5954	Error while informing the agent_type agent of a configuration change: change	Type of Message: Warning Cause: You attempted to call the ttCacheConfig built-in procedure, but the specified agent is down. For more information on the ttCacheConfig built-in procedure, see ttCacheConfig in Oracle TimesTen In-Memory Database Reference. Impact: The specified configuration change cannot be passed to the specified agent. User Action: Start the specified agent. - Cache agent: Call the ttCacheStart built-in procedure to start the cache agent. For more information on the ttCacheStart built-in procedure, see ttCacheStart in Oracle TimesTen In-Memory Database Reference. - Replication agent: Call the ttRepStart built-in procedure to start the replication agent. For more information on the ttRepStart built-in procedure, see ttRepStart in Oracle TimesTen In-Memory Database Reference.
5955	Autorefresh log table space monitoring and management will not be done since the cache admin user's tablespace management setting on ORACLE is not AUTO	Type of Message: Warning Cause: The tablespace management setting for the Oracle database is set to AUTO. Impact: The monitoring and management feature for the autorefresh log tablespace on the Oracle database is not enabled. User Action: If you want to enable the monitoring and management feature for the autorefresh log tablespace on the Oracle database, see Specifying Segment Space Management in Locally Managed Tablespaces in Oracle Database Administrator's Guide.
5956	Autorefresh log table space monitoring and management will not be done since there are no autorefresh trigger log tables in cache admin user's schema	Type of Message: Informational Cause: No autorefresh change log tables exist in the schema of the cache administration user. A common cause for this is that the cache agent was started before the read-only cache groups were created. Impact: The monitoring and management feature for the autorefresh log tablespace on the Oracle database is not enabled. User Action: None.
5957	Failed to retrieve the upper bound of the SELECT statement.	Type of Message: Error Cause: The cache agent cannot retrieve the upper bound that is used by the query that retrieves the rows to be refreshed. Impact: The cache agent retries the autorefresh operations. User Action: None.
5958	Autorefresh_step duration time: number ms	Type of Message: Informational Cause: The cache agent completed a step from the autorefresh work flow. The duration of the step was recorded in the autorefresh change log table. Impact: None. User Action: None.
5959	Change log table: table_name, COUNT(logseq): number, MIN(logseq): bookmark, MAX(logseq): bookmark, curSOLog: bookmark, retrieved curSOLog: bookmark	Type of Message: Error Cause: The cache agent encountered an error while retrieving information from the autorefresh change log table. The statistics from the table are specified in the message. Impact: The cache agent rolls back and retries the autorefresh operation. User Action: If the error persists, contact TimesTen Customer Support.
5960	Change log table: table_name, curSOLog: bookmark was not found	Type of Message: Error Cause: The cache agent could not find the current autorefresh bookmark from the specified change log table. Impact: The cache agent rolls back and retries the autorefresh operation. User Action: If the error persists, contact TimesTen Customer Support.
5961	Successfully executed the following Oracle database SQL statement: statement	Type of Message: Informational Cause: TimesTen successfully executed the specified SQL statement in the Oracle database. Impact: None. User Action: None.
5962	You are setting ConnNoWait=1. To disable ConnNoWait after it has been enabled and applied requires restarting the TimesTen server.	Type of Message: Warning Cause: You set ConnNoWait to 1. Impact: None. User Action: To disable ConnNoWait, restart the TimesTen server after setting ConnNoWait to 0 with the ttCacheConnPoolSet built-in procedure. For more information on the ttCacheConnPoolSet built-in procedure, see ttCacheConnPoolSet in Oracle TimesTen In-Memory Database Reference.
5963	Error creating the cache connection pool.	Type of Message: Error Cause: There was a problem creating the cache connection pool. Impact: TimesTen did not create the cache connection pool. User Action: Review the user error log for additional error messages.
5964	Error altering the cache connection pool. Problem setting the parameter parameter.	Type of Message: Error Cause: A problem was found when modifying one of the cache connection pool parameters. Impact: TimesTen did not modify the cache connection pool settings. User Action: Review the user error log for additional error messages.
5965	Error retrieving the cache connection pool saved parameter parameter (invalid value).	Type of Message: Error Cause: An error was found when retrieving the cache connection pool parameters. Impact: Review the user error log for possible impacts. User Action: Review the user error log for how to proceed.
5966	Error destroying the cache connection pool.	Type of Message: Error Cause: An error was found when destroying the cache connection pool. Impact: TimesTen failed to destroy the cache connection pool. User Action: Review the user error log for how to proceed.
5967	Pool connection is currently busy.	Type of Message: Error Cause: Another thread is currently using the connection. Impact: TimesTen cannot continue the current operation. User Action: Retry the operation.
5968	Failed to disconnect pool connection.	Type of Message: Error Cause: The pool connection could not disconnect from the back-end database at this time. Impact: The pool will retry the operation in the background. User Action: None.
5969	Failed to add a new connection to the pool.	Type of Message: Error Cause: An error was found while adding a new connection to the cache connection pool. Impact: TimesTen failed to add a new connection to the cache connection pool. User Action: Review the user error log for how to proceed.
5970	Failed to execute maintenance task: task.	Type of Message: Error Cause: Review the user error log for additional information. Impact: Review the user error log for possible impacts. User Action: Review the user error log for how to proceed.
5971	Connection pool error: error_message.	Type of Message: Error Cause: Review the user error log for additional information. Impact: Review the user error log for possible impacts. User Action: Review the user error log for how to proceed.
5972	Could not find an available connection in pool.	Type of Message: Error Cause: All connections in the pool are currently busy. Impact: TimesTen failed to complete the operation. User Action: Retry the operation.
5973	Pool is being destroyed. Could not execute the requested operation.	Type of Message: Error Cause: The cache connection pool is currently being destroyed. Impact: The operation could not be completed. User Action: Create a cache connection pool and retry the operation.
5974	Cannot serve any connections at this time. Purging queue: purging_reason.	Type of Message: Error Cause: TimesTen is currently purging the enqueued requests for a pool connection. Impact: TimesTen failed to complete the operation. User Action: Review the user error log for additional error messages.
5975	Refresher Stats: details.	Type of Message: Informational Cause: See details for more details. Impact: See details for more details. User Action: None.
5976	Could not create autorefresh stats environment.	Type of Message: Error Cause: TimesTen failed to create an internal structure for managing autorefresh stats. Impact: TimesTen will not update any autorefresh stats. User Action: Review additional error messages and restart the cache agent.
5977	Could not prepare autorefresh stats sql statements.	Type of Message: Error Cause: TimesTen failed to prepare the sql statements required for updating the autorefresh stats. Impact: TimesTen will not update any autorefresh stats. User Action: Review additional error messages and restart the cache agent.
5978	Failed to purge autorefresh stats for cache group cache_group_owner.cache_group_name.	Type of Message: Error Cause: TimesTen failed to purge the autorefresh stats for the cache group. Impact: TimesTen will not update any autorefresh stats. User Action: Review additional error messages and restart the cache agent.
5979	Failed to purge autorefresh stats for interval: autorefresh_interval static: is_static.	Type of Message: Error Cause: TimesTen failed to purge the autorefresh stats for the interval. Impact: TimesTen will not update any autorefresh stats. User Action: Review additional error messages and restart the cache agent.
5980	Failed to purge autorefresh stats for cache groups.	Type of Message: Error Cause: TimesTen failed to purge cache group autorefresh stats. Impact: TimesTen will not update any autorefresh stats. User Action: Review additional error messages and restart the cache agent.
5981	Failed to purge interval autorefresh stats.	Type of Message: Error Cause: TimesTen failed to purge interval autorefresh stats. Impact: TimesTen will not update any autorefresh stats. User Action: Review additional error messages and restart the cache agent.
5982	Failed to allocate a connection for managing the autorefresh stats.	Type of Message: Error Cause: TimesTen found an error while allocating a connection to update the autorefresh stats. Impact: TimesTen will not update any autorefresh stats. User Action: Review additional error messages and restart the cache agent.
5983	Failed to update autorefresh stats for cache group cache_group_owner.cache_group_name.	Type of Message: Error Cause: TimesTen failed to update the autorefresh stats for the cache group. Impact: Some stats for the cache group will be missing. User Action: Review additional error messages.
5984	Failed to purge autorefresh stats for interval: autorefresh_interval static: is_static.	Type of Message: Error Cause: TimesTen failed to update the autorefresh stats for the interval. Impact: Some stats for the autorefresh interval will be missing. User Action: Review additional error messages.
5985	Failed to collect autorefresh stats for cache group cache_group_owner.cache_group_name.	Type of Message: Error Cause: TimesTen failed to collect the autorefresh stats for the cache group. Impact: Some stats for the cache group will be missing. User Action: Review additional error messages.
5986	Failed to collect autorefresh stats for interval: autorefresh_interval static: is_static.	Type of Message: Error Cause: TimesTen failed to collect the autorefresh stats for the interval. Impact: Some stats for the autorefresh interval will be missing. User Action: Review additional error messages.
5987	Could not free autorefresh stats environment.	Type of Message: Error Cause: TimesTen failed to free the internal structure for managing autorefresh stats. Impact: None. User Action: Review additional error messages.
5990	A fatal error occurred in the cache agent.	Type of Message: Error Cause: Cache agent reports an irrecoverable error during autorefresh. Impact: TimesTen cannot complete the operation. User Action: Contact TimesTen Customer Support and send the latest daemon/sys log.
5991	The refresh operation failed. The agent will try again to refresh the cache group.	Type of Message: Warning Cause: A nonfatal error, such as a lock timeout, occurred during autorefresh. Impact: TimesTen cannot complete the operation. User Action: None. The cache agent retries the autorefresh.
5992	Unable to cleanup orphaned Oracle objects because it could not lock the appropriate tables.	Type of Message: Warning Cause: When the cache agent starts, the agent removes any orphaned Oracle database objects that were used in a previous autorefresh process. Before dropping the orphaned object, the agent locks the FT_USER_COUNT table so that no other agent can create new or drop old Oracle database objects. This warning is triggered when the agent was unable to lock the FT_USER_COUNT table. Impact: The agent was unable to clean up orphaned objects. User Action: None.
5994	Existing user_name.tt_xx_user_count table is not compatible. Use TimesTen built in procedure ttCacheSqlGet to generate SQL to cleanup all autorefresh objects under user user_name	Type of Message: Error Cause: The USER_COUNT table on the Oracle database is not compatible with this version of TimesTen Cache. Impact: TimesTen cannot complete the operation. User Action: Manually uninstall and reinstall the Oracle database objects for autorefresh. For more information, see Manually Creating Oracle Database Objects for Cache Groups with Autorefresh in Oracle TimesTen In-Memory Database Cache Guide for details.
5995	cache agent is shutting down.	Type of Message: Informational Cause: This is an informational message. Impact: None. User Action: None.
5996	UseCacheConnPool is enabled. The transaction requires a commit/rollback before dynamic load.	Type of Message: Error Cause: There is transaction currently open in this connection. A dynamic load must be executed in its own transaction. Impact: TimesTen failed to complete the dynamic load operation. User Action: Commit or rollback the current transaction and then retry the dynamic load.
5997	The cache connection pool must run in a threaded client/server. Set MaxConnsPerServer>1 and connect using client/server.	Type of Message: Error Cause: The user tried to create a cache connection pool from a direct connection. Impact: TimesTen failed to create the cache connection pool. User Action: To create the cache connection pool, set MaxConnsPerServer to a value greater than 1 and connect using client/server.
5998	The cache connection pool does not exist. Create it with the ttCacheConnPoolApply built-in procedure, then retry.	Type of Message: Error Cause: You tried to execute a dynamic load operation but the cache connection pool had not been created. Impact: TimesTen failed to complete the operation. User Action: To create the cache connection pool, execute the ttCacheConnPoolApply built-in procedure. For more information on the ttCacheConnPoolApply built-in procedure, see ttCacheConnPoolApply in Oracle TimesTen In-Memory Database Reference.

Errors 6000-6999

Error number	Error or warning message	Details
6000	Bad locking level for database connection	Type of Message: Error Cause: You attempted to set an unsupported locking level. Impact: TimesTen cannot perform the operation. User Action: Set the LockLevel attribute to either row-level or database-level locking. For more information see, LockLevel in Oracle TimesTen In-Memory Database Reference.
6001	Lock request denied because of conflict on conditional request\nDetails: error_details	Type of Message: Error Cause: TimesTen is unable to grant the lock request due to a conflict on conditional request. Impact: TimesTen cannot perform the operation. User Action: Retry the lock request. If denied, roll back and restart the operation. For information on lock resources and modes indicated in this message, see ttXactAdmin in Oracle TimesTen In-Memory Database Reference.
6002	Lock request denied because of deadlock\nDetails: error_details	Type of Message: Error Cause: TimesTen is unable to grant the lock request because granting it would cause a deadlock situation. Impact: TimesTen cannot perform the operation. User Action: Roll back and restart the whole transaction. For information on lock resources and modes indicated in this message, see ttXactAdmin in Oracle TimesTen In-Memory Database Reference.
6003	Lock request denied because of time-out\nDetails: error_details	Type of Message: Error Cause: TimesTen is unable to grant the lock request because the lock is not available or a timeout occurred waiting for the lock to be released. If the lockwait interval is set to 0-2 seconds, this error may also result from a deadlock, as the deadlock detector runs only every 2 seconds. Impact: TimesTen cannot perform the operation. User Action: Retry the lock request. If denied, roll back and restart the operation. For information on lock resources and modes indicated in this message, see ttXactAdmin in Oracle TimesTen In-Memory Database Reference.
6004	Bad transaction isolation level	Type of Message: Error Cause: An ODBC application can never get this message. Impact: TimesTen cannot perform the operation. User Action: Contact TimesTen Customer Support.
6005	Lock request denied because of not enough temp space available: error_details	Type of Message: Error Cause: The lock manager ran out of memory in the temporary memory region. Impact: TimesTen cannot perform the operation. User Action: Either compact the database or increase the size of the temporary memory region. For information on how to modify the size of the temporary memory region, see Specifying the Memory Region Sizes of a Database in Oracle TimesTen In-Memory Database Operations Guide.
6006	Lock-wait interval must be between 0 and 1,000,000	Type of Message: Error Cause: You attempted to set a lock-wait interval that is out of the allowed range. Impact: TimesTen cannot perform the operation. User Action: Use the ttLockWait built-in procedure to set the lock-wait interval within the allowed range. See ttLockWait in Oracle TimesTen In-Memory Database Reference for more information.
6009	Active connection has conflicting isolation level	Type of Message: Error Cause: The non-blocking delete isolation level cannot be used concurrently with other isolation levels. If a connection has an open transaction using any other isolation level, then no transaction using non-blocking delete isolation can be started. Similarly, if a connection has an open transaction using non-blocking delete isolation, then no transaction using any other isolation can be started. Impact: TimesTen cannot perform the operation. User Action: Commit or roll back the conflicting transactions. A lock is used to wait for access, but it may time out if the conflicting transactions do not complete in the timeout interval.
6010	Lock request denied (db is invalid: database_name)	Type of Message: Error Cause: TimesTen is unable to grant the lock request because the database is not valid. Impact: TimesTen cannot perform the operation. User Action: See the description of error 994 for more information.
6011	Lock request denied (locksleep error error_number)	Type of Message: Error Cause: A different transaction is currently using the resource you are trying to lock. Impact: TimesTen cannot perform the operation. User Action: Commit or rollback the conflicting transactions. Alternatively, tune the LockWait general connection attribute and retry the operation.
6013	Bad value for checkOverride parameter, should be 0 or 1	Type of Message: Error Cause: You provided an invalid value for the checkOverride parameter of the ttGetIsolation built-in procedure. Impact: TimesTen cannot perform the operation. User Action: Provide an appropriate value for the checkOverride parameter, and retry the operation. Valid values are 0 or 1.
6014	Row list maintenance error. To avoid this please use prefetchcount of 1	Type of Message: Error Cause: A row list is not wide enough for storing rowids. The system underestimated the required memory size. Impact: The fetch failed. No invalidation should have occurred. User Action: Use a prefetch count of 1 and try to force the system not use these lists. Alternatively, use cursor stability isolation mode.
6015	Transaction priority value must be between 0 and 65535	Type of Message: Error Cause: You specified an invalid value for the priority assigned to this transaction. The priority must be in the range 0 through 65535. Impact: TimesTen cannot perform the operation. User Action: Assign a valid value to the transaction priority and retry the operation.
6016	Element elementid couldn't acquire a lock on system table (SYS.table_name) in TimesTen Scaleout (lineno=lineno,val=return_value)	Type of Message: Error Cause: The element failed to acquire a lock on a system table. There may be a lock conflict in one element of the grid. Impact: TimesTen failed to perform the operation. User Action: Retry the operation.
6101	Attempting operation beyond end of cursor	Type of Message: Error Cause: Application is trying to fetch rows beyond the end of cursor. Impact: TimesTen failed to perform the operation. User Action: Ensure that your application checks for an end-of-cursor indication and does not attempt to seek beyond the end-of-cursor.
6102	Cursor is not updatable	Type of Message: Error Cause: You attempted to open a cursor for updating a non-updatable SELECT. Impact: TimesTen cannot perform the operation. User Action: Ensure that the SELECT is updatable, and retry the operation.
6103	Cursor has no current row defined	Type of Message: Error Cause: You attempted a delete or update operation on a CURRENT OF cursor without defining the FETCH clause first. Impact: TimesTen cannot perform the operation. User Action: Ensure that you define the FETCH clause first, and retry the operation.
6104	Column is not updatable via this cursor	Type of Message: Error Cause: You attempted to open a cursor for updating a column that is not simple or does not exist. Impact: TimesTen cannot perform the operation. User Action: Ensure that the column is updatable, and retry the operation.
6105	Update conflict caused by open index cursor(s) on table	Type of Message: Error Cause: There is an update conflict between an open index scan and an insert or delete attempt on a row of the table. Impact: TimesTen cannot perform the operation. User Action: Retry the operation.
6106	Operation conflicts with open table cursor(s)	Type of Message: Error Cause: You attempted an operation that is not allowed with an open cursor on the table. Impact: TimesTen cannot perform the operation. User Action: Close any cursor on the table, and retry the operation.
6107	Invalid cursor	Type of Message: Error Cause: The cursor is invalid because it has not been opened or the structure of the table or index on which the cursor is defined has changed. Impact: TimesTen cannot perform the operation. User Action: Open the cursor and ensure that the structure of your table or index that the cursor references is valid.
6108	Cursor state made \"unpositioned\" by updates in the same transaction	Type of Message: Error Cause: Within the same transaction, an operation has deleted the page of the row that the cursor was positioned on. This error can occur when the following conditions are met: - Logging is turned off, and- A searched CREATE VIEW (DELETE FROM ... WHERE ...) is issued on a table on which this transaction also has an open cursor, and: - The transaction does the next fetch on the cursor and tries to fetch the rows it deleted with the searched delete. Impact: TimesTen cannot perform the operation. User Action: Review your transaction and perform any necessary fixes. Then, retry the operation.
6109	Cannot open cursor until updates are committed	Type of Message: Error Cause: There is an open index scan on the table, and the application attempts to delete CURRENT of cursor, or the application attempts to update CURRENT of cursor. One (or more) of the columns being updated is also the key for the index being used in the index scan. Impact: TimesTen cannot perform the operation. User Action: Commit any updates and retry the operation.
6110	Cursor update disallowed due to conflict with index	Type of Message: Error Cause: You attempted to use a cursor to delete from or update an index. Impact: TimesTen cannot perform the operation. User Action: None.
6111	SQL statement has reached its timeout limit [number] and has been terminated	Type of Message: Error Cause: The SQL statement exceeded the maximum allowed time by the SQL_QUERY_TIMEOUT option. Impact: TimesTen stopped the execution of the statement and removed its effects, if any. User Action: Retry the SQL statement.
6112	Ref cursor binds are not allowed in SQL statements executed from PL/SQL	Type of Message: Error Cause: A SQL statement from a PL/SQL block included a REF CURSOR bind. Impact: TimesTen cannot perform the operation User Action: Remove any REF CURSOR from the PL/SQL block, and retry the operation.
6113	SQL statement has been canceled	Type of Message: Informational Cause: The user requested to interrupt or cancel the currently executing SQL statement. Impact: TimesTen interrupted the operation. User Action: None.
6200	New value for permanent data region size ignored since smaller than current value of number megabytes	Type of Message: Warning Cause: You attempted to load a database with a value for the permanent data region that is smaller than its current value. Impact: TimesTen ignored the new value. User Action: To avoid this warning, increase the value of the PermSize attribute or set PermSize=0 to leave the permanent memory region size unchanged.
6203	Overflow in converting database or log file size from megabytes to bytes, or in converting log buffer size from kilobytes to bytes	Type of Message: Error Cause: You specified a value for either the PermSize, TempSize, LogBufMB, or LogFileSize attributes that caused an overflow when the value was converted to bytes. PermSize, TempSize, and LogBufMB are expressed in megabytes. LogFileSize is expressed in kilobytes. Impact: TimesTen ignored the new value. User Action: Specify smaller values for the PermSize, TempSize, LogBufMB, or LogFileSize attributes to avoid overflow.
6206	Heap is full	Type of Message: Error Cause: The heap is full. Impact: You may get a stack overflow error or operating system errors. User Action: Try freeing up memory with the ttCkptBlocking built-in procedure or compacting the database with the ttCompact built-in procedure. Also, attempt to disconnect all connections and reconnecting them to free up some space. See ttCkptBlocking and ttCompact in Oracle TimesTen In-Memory Database Reference.
6212	MemoryLock connection attribute not supported on this platform	Type of Message: Error Cause: The MemoryLock connection attribute is supported only on select platforms. Impact: TimesTen ignores the MemoryLock connection attribute. User Action: If you are using AIX, the MemoryLock attribute is not implemented. The shared memory segment is locked when you use large pages on AIX. You can lock the shared segment by using large pages.
6220	Permanent data region free space insufficient to allocate number bytes of memory	Type of Message: Error Cause: The error is returned following error 802 and indicates that memory from the permanent data region has been exhausted. Impact: The database cannot continue normal operations. User Action: Increase the size of the permanent memory region by modifying the set value for the PermSize attribute. You must unload the database from memory for changes in the PermSize attribute to take effect. For more information on how to unload the database from memory, see Unloading a Database from Memory for TimesTen Classic in Oracle TimesTen In-Memory Database Operations Guide. For more information on the PermSize attribute, see PermSize, in the Oracle TimesTen In-Memory Database Reference.
6221	Temporary data region free space insufficient to allocate number bytes of memory	Type of Message: Error Cause: The error is returned following error 802 and indicates that memory from the temporary data region has been exhausted. Impact: The database cannot continue normal operations. User Action: Increase the size of the temporary memory region by modifying the set value for the TempSize attribute. You must unload the database from memory for changes in the TempSize attribute to take effect. For more information on how to unload the database from memory, see Unloading a Database from Memory for TimesTen Classic in Oracle TimesTen In-Memory Database Operations Guide. For more information on the TempSize attribute, see TempSize, in the Oracle TimesTen In-Memory Database Reference.
6222	Permanent data region in use size has exceeded PermWarnThreshold	Type of Message: Warning Cause: Memory allocation in the permanent memory region caused the PermWarnThreshold threshold to be exceeded, and memory threshold warnings have been enabled by the ttWarnOnLowMemory built-in procedure. Impact: None. User Action: Increase the size of the permanent memory region by modifying the set value for the PermSize attribute. You must unload the database from memory for changes in the PermSize attribute to take effect. For more information on how to unload the database from memory, see Unloading a Database From Memory for TimesTen Classic in Oracle TimesTen In-Memory Database Operations Guide. For more information on the PermSize attribute, see PermSize, in the Oracle TimesTen In-Memory Database Reference.
6223	Temporary data region in use size has exceeded TempWarnThreshold	Type of Message: Warning Cause: Memory allocation in the temporary memory region caused the TempWarnThreshold threshold to be exceeded, and memory threshold warnings have been enabled by the ttWarnOnLowMemory built-in procedure. Impact: None. User Action: Increase the size of the temporary memory region by modifying the set value for the TempSize attribute. You must unload the database from memory for changes in the TempSize attribute to take effect. For more information on how to unload the database from memory, see Unloading a Database From Memory for TimesTen Classic in Oracle TimesTen In-Memory Database Operations Guide. For more information on the TempSize attribute, see TempSize, in the Oracle TimesTen In-Memory Database Reference.
6226	Ignoring value requested for first connection attribute 'attribute_name' -- value currently in use: value, requested value: value	Type of Message: Warning Cause: You attempted to connect to a database with a different value for the specified first connection attribute than the value given in the first connection to the database. Impact: TimesTen ignores the value not in use for the specified first connection attribute and connects to the database. User Action: Close all active connections to the database, unload the database from memory, and retry the operation. To unload the database from memory, you may need to set the RAM policy of the database to manual or inUse. For more information on setting the RAM policy to manual or inUse, see Specifying a RAM Policy in Oracle TimesTen In-Memory Database Operations Guide.
6228	Invalid value (value) for attribute_name connection attribute -- value must be value	Type of Message: Error Cause: You attempted to connect to a database with a different value for the specified connection attribute than the value given in the database creation process. Impact: TimesTen cannot connect to the database. User Action: To modify the specified connection attribute, destroy and recreate the database with the desired value for the specified connection attribute. For more information on connection attributes, see Connection Attributes in Oracle TimesTen In-Memory Database Reference.
6229	Fatal error: cannot rollback transaction. This is usually because an out-of-space condition prevents re-inserting old values into index(es). In most cases this can be resolved if you reconnect with a larger PermSize.	Type of Message: Error Cause: A transaction cannot rollback. This usually occurs when the database has run out of available memory. A common cause for this is that the PermSize attribute of the database is set too low. Impact: The database is invalidated. If the ramPolicy parameter of the ttRamPolicySet built-in procedure is set to always, automatic recovery may fail. For more information on the ttRamPolicySet built-in procedure, see ttRamPolicySet in Oracle TimesTen In-Memory Database Reference. User Action: Review the error messages that immediately precede this error message. If they mention that the database is running out of space, check and modify the values of PermSize and TempSize attributes so that the database has at least five percent of space available on each memory region. For more information on how to check the amount of memory in use by the database, see Check the amount of memory allocated to the database in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide. For more information on how to increase the values of PermSize and TempSize attributes, see Specifying the Memory Region Sizes of a Database in the Oracle TimesTen In-Memory Database Operations Guide. If the error persists after adjusting the values of the PermSize and TempSize attributes of the database, contact TimesTen Customer Support.
6230	Cannot perform DML such as update and DDL such as create index or alter table in same transaction when using DDLCommitBehavior=1	Type of Message: Error Cause: This error is returned when using DDLCommitBehavior=1. If DDLCommitBehavior=1, TimesTen allows multiple DML and DDL statements in the same transaction. However, some mixes of DML and DDL in the same transaction while using DDLCommitBehavior=1 are no longer allowed. For example, you will see this error when updating rows in a table and then creating an index on that same table (or updating rows in a table and then resizing that table's hash index with ALTER TABLE ... PAGES = n). Impact: TimesTen cannot perform the operation. User Action: To prevent this error, do not mix DML and DDL in the same transaction. Ensure that the DDL operation is in its own transaction.
6231	Invalid value (value) for attribute_name connection attribute in TimesTen Scaleout -- value must be value	Type of Message: Error Cause: You attempted to connect to a database with a value of the specified connection attribute that is not supported by TimesTen Scaleout. Impact: TimesTen could not establish the connection. User Action: Set the specified connection attribute to a value supported by TimesTen Scaleout and retry the operation. For more information on the specified connection attribute, see Connection Attributes in Oracle TimesTen In-Memory Database Reference. For more information on how to modify the value of a connection attribute in TimesTen Scaleout, see Modifying the Connection Attributes of a Database in the Oracle TimesTen In-Memory Database Scaleout User's Guide.
6232	Invalid value for the OPTIMIZERHINT connection attribute -- Reason: reason	Type of Message: Error Cause: You attempted to connect to a database with an invalid value for the OPTIMIZERHINT connection attribute. Impact: TimesTen cannot connect to the database. User Action: Specify a valid value for the OPTIMIZERHINT connection attribute and retry the operation. For more information on the OPTIMIZERHINT connection attribute, see OptimizerHint in Oracle TimesTen In-Memory Database Reference.

Errors 7000-7999

Error number	Error or warning message	Details
7000	SQL statement exceeds the limit of number table references	Type of Message: Error Cause: You exceeded the maximum number of tables that can be referenced in a SQL statement. Impact: TimesTen cannot perform the SQL operation. User Action: Rewrite your query so that no more than the limit number of tables provided in the message are referenced.
7001	User authentication failed	Type of Message: Error Cause: You attempted to perform a user authentication using an invalid user name and/or password. Impact: The current operation failed. User Action: Verify your user name and password information and retry the operation.
7002	No current user to use as default user_name	Type of Message: Error Cause: You attempted to use an invalid current user as default. Impact: TimesTen cannot find the user name. User Action: Verify the user name and retry the operation.
7003	Value is not a valid float	Type of Message: Error Cause: You provided an invalid floating-point value for a FLOAT column. Floating-point values provided for these columns can only contain an optional sign (+ or -), followed by the digits 0-9 and an optional decimal point or exponential notation character between the digits. Impact: TimesTen cannot perform the operation. User Action: Specify a valid value and retry the operation.
7004	Value is not a valid double	Type of Message: Error Cause: You provided an invalid floating-point value for a DOUBLE PRECISION column. Floating-point values provided for these columns can only contain an optional sign (+ or -), followed by the digits 0-9 and an optional decimal point or exponential notation character between the digits. Impact: TimesTen cannot perform the operation. User Action: Specify a valid value and retry the operation.
7005	Procedure `procedure_name' not found	Type of Message: Error Cause: You attempted to call an ODBC procedure that does not exist. Impact: TimesTen cannot perform the operation. User Action: Verify the procedure name and retry the operation.
7006	Bad argument supplied	Type of Message: Error Cause: You specified an invalid argument value to a built-in procedure. Impact: The current operation failed. User Action: Provide an appropriate argument to the built-in procedure and retry the operation. For more information, see Built-In Procedures in Oracle TimesTen In-Memory Database Reference.
7007	Required argument omitted	Type of Message: Error Cause: You omitted a required argument when calling a TimesTen built-in procedure. Impact: The current operation failed. User Action: Modify your query to include the required parameters and retry the operation. For more information, see Built-In Procedures in Oracle TimesTen In-Memory Database Reference.
7008	Statement forbidden for read-only connections	Type of Message: Error Cause: You attempted to use a statement that is forbidden on a read-only table. Impact: TimesTen cannot execute the SQL statement. User Action: If you need to execute the SQL statement, use read/write connections.
7009	Too many parameters for procedure `procedure_name'	Type of Message: Error Cause: You passed more parameters than expected when calling a TimesTen built-in procedure. Impact: The current operation failed. User Action: Modify your query to include the appropriate number of parameters and retry the operation. For more information, see Built-In Procedures in Oracle TimesTen In-Memory Database Reference.
7011	Procedure procedure_name failed	Type of Message: Error Cause: An error occurred while performing the indicated procedure. Impact: TimesTen failed to complete the current operation. User Action: Review the additional errors returned to determine the cause of the failure.
7012	Attempt to update system table table_name not permitted	Type of Message: Error Cause: You attempted to destroy, insert into, delete from, or update a system catalog table or index. You cannot perform these operations on system tables. Impact: TimesTen cannot perform the operation. User Action: Verify the table and owner name and retry the operation.
7013	Error while scanning SQL statement:statement	Type of Message: Error Cause: On a Windows or Linux system, the scanner detected an error in your SQL statement. Impact: TimesTen cannot complete the operation. User Action: Review the error message to determine the cause of the failure. An "input buffer overflow" error text indicates that the length of a string literal has exceeded a platform-dependent internal buffer limit. Any other error text indicates an unexpected internal error condition.
7014	Fixed size of command argument too large	Type of Message: Error Cause: You exceeded the maximum number of 8,400 in the length of the input argument row descriptor. Impact: TimesTen cannot perform the operation. User Action: Modify your command to use fewer (or shorter) arguments and retry the operation.
7015	System table cannot be used in index creation.	Type of Message: Error Cause: You attempted to use the CREATE INDEX statement with system tables. This statement cannot be used with system tables. Impact: TimesTen cannot perform the operation. User Action: Verify the table and owner name and retry the operation.
7017	Unknown optimizer flag flag_name	Type of Message: Error Cause: You specified an invalid name for the optimizer flag. Impact: TimesTen cannot perform the operation. User Action: Specify a valid flag name for the optimizer and retry the operation. For the complete list of flags, see ttOptSetFlag in Oracle TimesTen In-Memory Database Reference.
7018	Creation of user objects in system-user schemas is not allowed	Type of Message: Error Cause: You attempted to create a table with the owner name SYS, which is used for TimesTen system tables. Impact: TimesTen cannot perform the operation User Action: Verify the table and owner name and retry the operation.
7019	Index owner must match table owner owner_name	Type of Message: Error Cause: You attempted to create an index specifying a different owner than the owner of its underlying table. Impact: TimesTen cannot perform the operation. User Action: Ensure that the index owner matches the table owner and retry the operation.
7024	Bad sample string ('string'). Format is '<int> ROWS' or '<float> PERCENT'	Type of Message: Error Cause: You specified a string with incorrect format. Impact: The SQL statement is not executed. User Action: Modify your string to use the correct format and retry the operation.
7025	Invalid use of reserved keywordkeyword	Type of Message: Error Cause: You specified an identifier or user name that is a keyword reserved by TimesTen. Impact: TimesTen cannot perform the operation. User Action: Select a different identifier or user name and retry the operation. If you want to perform an operation with an already existing identifier or user name registered with the specified keyword, add quotation marks to the specified identifier or user name and retry the operation. For more information on reserved words, see Reserved Words in Oracle TimesTen In-Memory Database SQL Reference.
7026	Attempt to alter system table table_name not permitted	Type of Message: Error Cause: You attempted to alter a system table. System tables are identified by the owner SYS or TTREP. Impact: TimesTen cannot perform the operation. User Action: If you are attempting to alter a table that has a name similar to a TimesTen system table, explicitly specify the owner name.
7027	Unable to evaluate index key due to multiple warnings	Type of Message: Error Cause: Your index key expression's evaluation resulted in multiple warnings. Impact: TimesTen cannot insert the value into the index. User Action: Rewrite the expression to avoid warnings.
7028	Table names must contain at least one character	Type of Message: Error Cause: You attempted to create a table without a name. The name of a table must have at least one character. Impact: TimesTen cannot perform the operation. User Action: Rename the table and retry the operation.
7029	Index names must contain at least one character	Type of Message: Error Cause: You attempted to create an index without a name. The name of an index must have at least one character. Impact: TimesTen cannot perform the operation. User Action: Rename the index and retry the operation.
7030	Expression provided as argument for parameter_name parameter message	Type of Message: Error Cause: You provided an expression as an argument for a parameter_name. Impact: TimesTen cannot perform the operation. User Action: Rewrite the query using the 'Expression' such that argument is always a constant value.
7031	Bad argument supplied: reason	Type of Message: Error Cause: You provided a bad argument to a built-in procedure. Impact: The built-in procedure cannot perform the operation. User Action: Check the reason the error provides for more information, and retry the operation while providing an appropriate argument to the built-in procedure. For more information on the built-in procedure, see Built-In Procedures in Oracle TimesTen In-Memory Database Reference.
7032	Missing keyword keyword	Type of Message: Error Cause: A required keyword is missing. Impact: TimesTen cannot perform the operation. User Action: Retry the operation with the correct statement.
7050	Undefined trace component `component_name'	Type of Message: Error Cause: You specified a trace component that is not defined. Impact: TimesTen cannot perform the operation. User Action: Specify the correct trace components and retry the operation. For more information, see Using the ttTraceMon utility in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
7051	Error in setting-up TimesTen traces: `trace_names'	Type of Message: Error Cause: You specified an invalid trace command or function. Impact: TimesTen is unable to create the trace output file. User Action: Verify the trace command. For a description of the components available through this utility and a description of the information that ttTraceMon returns for each, see Using the ttTraceMon utility in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
7052	Cannot disable thread support after it has already been enabled	Type of Message: Error Cause: You attempted to disable multithreading support after it was already enabled. Impact: TimesTen cannot perform the operation. User Action: Rewrite the application to enable or disable thread support. An application cannot change the thread support mode after it has already enabled or disabled it.
7053	Cannot enable thread support after it has already been disabled	Type of Message: Error Cause: You attempted to enable multithreading support after it was already disabled. Impact: TimesTen cannot perform the operation. User Action: Rewrite the application to enable or disable thread support. An application cannot change the thread support mode after it has already enabled or disabled it.

Errors 8000-8999

Error number	Error or warning message	Details
8000	No primary or unique index on non-nullable column found for replicated table owner_name.table_name	Type of Message: Error Cause: The specified table does not have a unique index that can be used for replication. Impact: TimesTen cannot replicate the specified table. User Action: Ensure that every table has a unique index or a primary key. For more information, see Restrictions and Table Requirements for Classic Replication Schemes in Oracle TimesTen In-Memory Database Replication Guide.
8001	Attempt to read invalid LSN log record	Type of Message: Error Cause: You attempted to read an invalid LSN log record. Impact: TimesTen cannot read the LSN log record. User Action: Specify a valid log file number and retry the operation.
8002	Cannot drop replicated table, index, or sequence	Type of Message: Error Cause: You attempted to use a SQL UPDATE statement to drop a replicated table, index, or sequence. Impact: TimesTen cannot perform the update operation. User Action: To drop a table, index, or sequence that is part of a replication scheme, alter the replication scheme using the ALTER REPLICATION SQL statement. For more information, see ALTER REPLICATION in Oracle TimesTen In-Memory Database SQL Reference.
8003	Update older than TimeStamp of existing row	Type of Message: Error Cause: You attempted to perform an update that is older than the current timestamp for the row in the database. Impact: TimesTen cannot perform the update operation. If configured, TimesTen will generate a report of the conflict. For more information, see Reporting Conflicts to a Text File in Oracle TimesTen In-Memory Database Replication Guide. User Action: Ensure that your update operation is out of date. If that is the case, consider discarding the UPDATE operation.
8004	Column owner_name.table_name.column_name cannot be used for replication timestamp checking if in an index or added by ALTER TABLE or if it is columnar; and must be binary(8) with NULL values allowed	Type of Message: Error Cause: You attempted to use the specified column for replication timestamp conflict resolution. Impact: TimesTen cannot use the specified column to perform replication timestamp conflict resolution. User Action: Ensure that the specified timestamp column is not part of an index, is of type BINARY(8) NULL, and was not added as part of an ALTER TABLE statement. For more information, see Including a Timestamp Column in Replicated Tables in Oracle TimesTen In-Memory Database Replication Guide.
8005	Invalid update rule for timestamp-based conflict checking	Type of Message: Error Cause: You did not specify a valid SYSTEM or USER parameter for the UPDATE BY clause. Impact: TimesTen cannot complete the SQL ALTER REPLICATION or the SQL CREATE REPLICATION operation. User Action: Ensure that your UPDATE BY clause is correctly defined for the ALTER REPLICATION or CREATE REPLICATION statement. Then, retry the operation. For more information, see ALTER REPLICATION and CREATE REPLICATION in Oracle TimesTen In-Memory Database SQL Reference.
8006	Application must set timestamp column with 'UPDATE BY USER'	Type of Message: Error Cause: You are attempting to update a table that has enabled replication timestamp conflict resolution and contains an UPDATE BY USER clause. However, no timestamp value is defined. Impact: TimesTen cannot perform the update operation. User Action: Ensure that your replication timestamp conflict resolution column contains a valid timestamp value. Then, retry the operation. For more information, see Configuring the CHECK CONFLICTS Clause in Oracle TimesTen In-Memory Database Replication Guide.
8007	Cannot change hash pages, aging attributes or add/drop aging policy of replicated tables while replication Agent is running	Type of Message: Error Cause: You attempted to change the aging attributes, or add or drop an aging policy of replicated tables while the replication agent is running. Impact: TimesTen cannot perform the operation. User Action: Stop the replication agent and retry the operation. For more information about how to stop the replication agent, see Starting and Stopping the Replication Agents in theOracle TimesTen In-Memory Database Replication Guide.
8009	Transaction Log API Buffer size too small or too large	Type of Message: Error Cause: You specified a transaction log buffer size that is out of the supported range for XLA. This message is followed by another message that describes the details of the failure. Impact: TimesTen cannot perform the XLA operations. User Action: Check the accompanying error message and consider increasing the transaction log buffer size. For more information, see Increase Transaction Log Buffer Size When Using XLA in Oracle TimesTen In-Memory Database Operations Guide.
8010	Unable to attach to XLA segment	Type of Message: Error Cause: TimesTen cannot attach to the XLA segment due to an environment issue. This message is followed by another message that describes the details of the failure. Impact: TimesTen cannot perform the operation. User Action: Check the accompanying error messages in the log to determine a possible solution to the environment issue.
8011	Unable to re-configure active XLA segment	Type of Message: Error Cause: You attempted to change the transaction log buffer size in an active transaction. Impact: TimesTen cannot reconfigure the XLA segment. User Action: Contact TimesTen Customer Support.
8012	Table with given ID not found	Type of Message: Error Cause: Table with the user-specified ID does not exist in the database. Impact: TimesTen cannot correctly complete a full (non-incremental) autorefresh on the cache group. User Action: Check the accompanying error messages in the log and contact TimesTen Customer Support.
8013	Attempt to specify invalid version	Type of Message: Error Cause: You specified an invalid TimesTen release version. Impact: Applications that call the ttXlaSetVersion function cannot execute correctly. For more information on the ttXlaSetVersion function, see ttXlaSetVersion in Oracle TimesTen In-Memory Database C Developer's Guide. User Action: Ensure that your TimesTen XLA version is the same version (or an earlier version) as the actualVersion output from the ttXlaGetVersion function. For more information on the ttXlaGetVersion function, see ttXlaGetVersion in Oracle TimesTen In-Memory Database C Developer's Guide.
8016	No replication buffer configured	Type of Message: Error Cause: TimesTen does not have a replication buffer configured. Impact: The transaction log buffer cannot store updates. User Action: Contact TimesTen Customer Support.
8017	Foreign table has number columns while local table has number columns	Type of Message: Error Cause: The tables that TimesTen is comparing have a different number of columns. Impact: Table information received from the foreign table is not compatible with the local table definition. User Action: None.
8018	Foreign table indexed on different columns	Type of Message: Error Cause: The tables that TimesTen is comparing have different primary key definitions. Impact: TimesTen cannot execute the ttXlaApply function call and cannot update the target database. User Action: Ensure that the table definitions are the same for your source and target databases. For more information on the ttXlaApply function, see ttXlaApply in Oracle TimesTen In-Memory Database C Developer's Guide.
8019	Foreign and local table differ on column type type	Type of Message: Error Cause: The tables that TimesTen is comparing have different column data types. Impact: TimesTen cannot execute the ttXlaApply function call and cannot update the target database. User Action: Ensure that the table definitions are the same for your source and target databases. For more information on the ttXlaApply function, see ttXlaApply in Oracle TimesTen In-Memory Database C Developer's Guide.
8020	Inconsistent row in update description	Type of Message: Error Cause: The ttXlaGenerateSQL function is attempting to retrieve a tuple that is not valid. Impact: TimesTen cannot execute the ttXlaGenerateSQL function call. User Action: Ensure that the ttXlaGenerateSQL function is retrieving the tuple correctly. For more information on the ttXlaGenerateSQL function, see ttXlaGenerateSQL in Oracle TimesTen In-Memory Database C Developer's Guide.
8021	System table ID invalid	Type of Message: Error Cause: TimesTen cannot retrieve the table definition details for the specified table ID. Impact: The function call fails. User Action: Specify a valid table ID.
8023	Table row does not have expected value	Type of Message: Error Cause: The contents of the row do not match the expected values in the transaction log update. Impact: TimesTen cannot execute the ttXlaApply function call. User Action: Ensure that you specify a valid row structure for the ttXlaApply function. For more information on the ttXlaApply function, see ttXlaApply in Oracle TimesTen In-Memory Database C Developer's Guide.
8024	Invalid XLA record type	Type of Message: Error Cause: The XLA record is invalid or unsupported. Impact: TimesTen cannot execute the ttXlaApply function call. User Action: Specify a valid XLA record for the ttXlaApply function. For more information on the ttXlaApply function, see ttXlaApply in Oracle TimesTen In-Memory Database C Developer's Guide.
8025	Replication Log Threshold limit reached at master. The Replication state for this subscriber database is now set to FAILED. This database is not in sync with the master	Type of Message: Error Cause: A replication peer has set the replication state of this database to FAILED. This happens when the amount of logs that the peer is holding for the database exceeds a user configurable threshold. For more information, see Setting the Transaction Log Failure Threshold and Subscriber Failures in Oracle TimesTen In-Memory Database Replication Guide. Impact: The TimesTen database is out of sync with the master database. User Action: Recover the FAILED database and resume replication. For more information, see Recovering a Failed Database in Oracle TimesTen In-Memory Database Replication Guide.
8029	Persistent transaction log API bookmark already in use	Type of Message: Error Cause: You attempted to reuse or delete an XLA bookmark in more than one XLA connection. Impact: The replication agent cannot perform the operation. User Action: Close the connection using the bookmark or set up a new bookmark, and retry the operation.
8031	Persistent transaction log API log sequence number is invalid	Type of Message: Error Cause: You attempted to use a transaction log API log sequence number that is not valid. This number is either not provided by the API or it is in the range already acknowledged by the connection. Impact: The replication agent cannot perform the operation. User Action: Use a valid number and retry the operation.
8032	Stale post handle	Type of Message: Error Cause: The replication transmitter accessed a synchronization object used for return service processing, which no longer applies to this particular service request. This is an internal condition that is externalized only as a part of the user error log warning "Attempt to awaken connection connection_id failed." Impact: The replication agent cannot perform the operation. User Action: The operation will be retried automatically. If the replication agent cannot recover from a restart, contact TimesTen Customer Support.
8033	Invalid post handle	Type of Message: Error Cause: The replication transmitter accessed a synchronization object used for return service processing, which is no longer a valid synchronization object. Impact: The replication agent cannot perform the operation. User Action: The operation will be retried automatically. If the replication agent cannot recover from a restart, contact TimesTen Customer Support.
8034	Record cannot be expressed in SQL	Type of Message: Error Cause: You presented an XLA record that does not translate into SQL to ttXlaGenerateSQL. Impact: The replication agent cannot perform the operation. User Action: Modify your XLA record and retry the operation.
8036	Parameter parameter_name value not in valid range	Type of Message: Error Cause: You attempted to use a parameter that is not in the valid range. Impact: The current operation failed. User Action: Change the parameter and retry the operation.
8037	Table definition of record differs from the table definition in the database	Type of Message: Error Cause: The table definition of the record at the time of its creation differs from the table definition of the record in the database. Impact: The database cannot interpret the record. User Action: Ensure that the table definition matches the table definition of the record in the database.
8038	Operation not permitted on system table	Type of Message: Error Cause: You attempted to perform an operation that is not permitted on a SYS table. The operation is only permitted on a user-defined table. Impact: The current operation failed. User Action: Retry the operation on a user-defined table.
8039	Attempt to drop replication timestamp column from table table_name	Type of Message: Error Cause: You attempted to drop the replication timestamp column from a table. This column is used by TimesTen to resolve conflicts. Impact: The column cannot be dropped. User Action: You can try dropping a table fully.
8040	No free slots in replCTNArr	Type of Message: Error Cause: Either the dbheader is corrupt or another error occurred during the allocation. Impact: The replication agent fails to complete the operation until the allocation is successful. User Action: Contact TimesTen Customer Support.
8041	Invalid replCTNArr slot	Type of Message: Error Cause: Either the dbheader is corrupt or another error occurred during the allocation. Impact: The replication agent fails to complete the operation until the allocation is successful. User Action: Contact TimesTen Customer Support.
8042	ReplCTNArr slot is not allocated	Type of Message: Error Cause: Either the dbheader is corrupt or another error occurred during the allocation. Impact: The replication agent fails to complete the operation until the allocation is successful. User Action: Contact TimesTen Customer Support.
8043	Materialized views cannot be defined in a replication scheme	Type of Message: Error Cause: You attempted to replicate a materialized view. Impact: The replication agent cannot complete the operation. User Action: You can only replicate detail tables. For more information, see Views and Materialized Views in a Replicated Database in Oracle TimesTen In-Memory Database Replication Guide.
8044	To avoid data inconsistency, copy the database from a replication subscriber using 'ttRepAdmin -duplicate'. Use ForceConnect=1 in the connection string to override this restriction	Type of Message: Error Cause: You attempted to recover a failed master database by using the RETURN RECEIPT replication with the TRANSMIT NONDURABLE option. This operation allows the database to recover only by restoring its state from a subscriber database using the -duplicate option of the ttRepAdmin utility. Impact: The replication agent cannot complete the operation. User Action: Use the ForceConnect attribute to override this restriction and retry the operation.
8046	The input old value row does not match the database row	Type of Message: Error Cause: You attempted to perform an XLA update where the old value row does not match the value of the row in the database. Impact: The current operation failed. User Action: Ensure that the values match and retry the operation.
8047	Connection is currently dedicated to XLA exclusively	Type of Message: Error Cause: You attempted to perform a direct ODBC call on a connection that is in use by XLA. Impact: The current operation failed. User Action: Wait for the XLA connection to close and retry the operation.
8049	Commit ticket number will wrap around	Type of Message: Error Cause: You attempted to perform an operation where the commit ticket number for replication wraps around. Impact: None. Replication continues working. User Action: If replication does not work as expected, contact TimesTen Customer Support.
8051	The alter table operation on a replicated table cannot be in a two safe by request transaction	Type of Message: Error Cause: You attempted to alter replicated tables by using ALTER TABLE in a RETURN TWOSAFE BY REQUEST transaction. Impact: The replication agent cannot alter the tables. User Action: Roll back the transaction.
8052	Cannot commit transaction that involves commit to Oracle and TWOSAFE replication handling	Type of Message: Error Cause: You cannot commit RETURN TWOSAFE transactions on tables in a TimesTen cache group. Impact: The replication agent cannot complete the operation. User Action: Contact TimesTen Customer Support.
8055	Variable sized data of size number bytes exceeds maximum allowed by replication	Type of Message: Error Cause: The TimesTen replication agent encountered an out-of-line log record that has a data length that exceeds the maximum supported length for a replicated column. For more information on the maximum supported length for a replicated column, see System Limits and Defaults in Oracle TimesTen In-Memory Database Reference. Impact: TimesTen fails to replicate a transaction. The subscriber database is not synchronized with the master database. User Action: Run the ttXactLog -v 3 utility on the master database and contact TimesTen Customer Support. For more information on the ttXactLog utility, see ttXactLog in Oracle TimesTen In-Memory Database Reference.
8059	All DDLs on a replicated table need to be in a transaction of their own	Type of Message: Error Cause: You attempted to perform data definition language (DDL) operations on a replicated table and these operations are not present exclusively in a transaction of their own. Impact: The replication agent cannot complete the operation. User Action: Ensure that the DDL operations are present in a transaction of their own and retry the operation.
8060	Cannot specify replication timestamp column on a cached table	Type of Message: Error Cause: You cannot configure a timestamp-based conflict resolution for replication on a cached table. Impact: The replication agent failed to complete the operation as it is invalid. User Action: None.
8061	Operation not permitted when the connection attribute ForceConnect is set to 1	Type of Message: Error Cause: You attempted to use the connection attribute ForceConnect set to 1. Impact: The replication agent cannot complete the operation. User Action: Ensure that the connection attribute ForceConnect is set to 0 on any connections that attempt these replication operations.
8062	Local database not in ACTIVE state	Type of Message: Error Cause: The state of the local database is not in the ACTIVE state for a database that is part of an active standby replication scheme. Impact: The replication agent cannot complete the operation. User Action: Set the replication state to ACTIVE by using call ttrepstateset('active');.
8063	Local database not completely quiesced	Type of Message: Error Cause: You attempted to use an active database in an active standby replication scheme, which has pending updates that have not been replicated. Impact: The replication agent cannot complete the operation. User Action: Turn off local application updates and ensure that the replication agent has sent all pending updates to the standby database.
8064	Table is already subscribed	Type of Message: Error Cause: You cannot subscribe a table twice. Impact: The replication agent cannot complete the operation. User Action: Modify the operation that wants to subscribe it.
8065	Table is not subscribed	Type of Message: Error Cause: You attempted to unsubscribe an already unsubscribed table from the XLA bookmark. Impact: The replication agent cannot complete the operation until the table is subscribed. User Action: Subscribe the table and retry the operation.
8066	Cannot alter subscription when bookmark is in use	Type of Message: Error Cause: You attempted to alter a subscription when the XLA bookmark was in use. Impact: The replication agent cannot complete the operation. User Action: Ensure that the XLA bookmark is not in use before unsubscribing and retry the operation.
8067	Inconsistency detected in the COLUMN_HISTORY system table	Type of Message: Error Cause: The contents of the system table, COLUMN_HISTORY seem to be corrupted. Impact: The operation fails. User Action: Contact TimesTen Customer Support.
8068	Cannot drop a table or view that is subscribed by an XLA bookmark	Type of Message: Error Cause: You attempted to drop a table or view that is subscribed by an XLA bookmark. Impact: The replication agent cannot complete the operation. User Action: Unsubscribe the table from every XLA bookmark and retry the operation.
8069	Operation only supported when the character set of the database in which the record is generated matches that of the connected database	Type of Message: Error Cause: You attempted to perform an operation where the character set of the source database did not match that of the destination database. Impact: The replication agent cannot complete the operation. User Action: Ensure that the character set of the source database matches the character set of the destination database.
8070	The specified XLA bookmark does not exist	Type of Message: Error Cause: You specified an XLA bookmark that does not exist. Impact: TimesTen cannot complete the operation. User Action: Create a bookmark using the ttXlaBookmarkCreate built-in procedure. For more information, see ttXlaBookmarkCreate in Oracle TimesTen In-Memory Database Reference.
8071	A replicated bookmark can only be created on a database with Active/Standby Pair replication	Type of Message: Error Cause: You attempted to create a replicated bookmark on a database with Active/Standby Pair replication. Impact: TimesTen cannot complete the operation. User Action: Drop your current replication scheme and create an active standby pair replication scheme.
8072	Operation only permitted on an ACTIVE database	Type of Message: Error Cause: You attempted to perform and XLA operation that is only permitted on a database that is in the ACTIVE state. Impact: TimesTen cannot complete the operation. User Action: Retry the operation on the ACTIVE state or set the current store as the ACTIVE.
8073	Failed to update Xla bookmark :bookmark	Type of Message: Error Cause: You attempted to update an XLA bookmark on a standby database that is either unhealthy or has locks held on XLA tables. Impact: The standby update to the XLA bookmark failed. User Action: None. The agent will continue trying to update the XLA bookmark until the condition that caused the error is alleviated. However, if this is a recurring error, contact TimesTen Customer Support.
8074	Maximum number of bookmarks exceeded	Type of Message: Error Cause: You attempted to create more than the maximum number of replicated bookmarks per database. Impact: TimesTen cannot complete the operation. User Action: Specify a number of replicated bookmarks that does not exceed the maximum allowed and retry the operation.
8075	Error loading bookmark list	Type of Message: Error Cause: You attempted to load an XLA bookmark list on a standby database that is either unhealthy or has locks held on XLA tables. Impact: The replication agent failed reading the set of replicated bookmarks from the database. User Action: None. The agent will continue trying to load the list until the condition that caused the error is alleviated. If the problem persists, contact TimesTen Customer Support.
8076	Bookmark reset due to state change at database	Type of Message: Error Cause: The state of the database was recently changed, thus bookmarks may be stale. The bookmarks that were open at the time of the state change are reset and you can use them to read XLA updates. Impact: The bookmarks have been reset. User Action: Ensure that the bookmarks are in a sane place and that any changes are replicated or reported correctly.
8077	Error moving bookmark on the standby database	Type of Message: Error Cause: You attempted to move a bookmark on a standby database that is either unhealthy or has locks held on XLA tables. Impact: The replication agent failed updating the set of replicated bookmarks from the database. User Action: None. The agent will continue trying to load the list until the condition that caused the error is alleviated. If the problem persists, contact TimesTen Customer Support.
8078	The deletion of replicated xla bookmarks is not allowed while the replication agent is running.	Type of Message: Error Cause: You attempted to delete a replicated bookmark while the replication agent was running. Impact: TimesTen cannot complete the operation. User Action: Stop the replication agent and retry the operation.
8080	Variable data error information type information_type information	Type of Message: Error Cause: This error message provides additional information for error message 8055. Impact: None. User Action: Contact TimesTen Customer Support.
8081	The local host in the replication scheme hostname does not match this host hostname	Type of Message: Error Cause: The local host specified in the replication scheme does not match the current host. Impact: The replication agent cannot be initialized. User Action: Verify that the replication scheme has been defined correctly. You may use the ttHostNameSet built-in procedure to ensure that the host names match. For more information on the ttHostNameSet built-in procedure, see ttHostNameSet in Oracle TimesTen In-Memory Database Reference.
8082	Reached maximum subscriber limit number	Type of Message: Error Cause: Reached maximum subscriber limit Impact: Cannot create any more subscribers. User Action: Limit the number of subscribers to the maximum allowed amount
8083	Cannot set max subscribers as it has already been set to number. To change this setting drop all replication schemes and resubmit the command	Type of Message: Error Cause: You attempted to set the maximum number of replication subscribers, and a replication scheme already exists. Impact: TimesTen cannot perform the operation. User Action: Drop all replication schemes, and retry the operation.
8084	ALTER TABLE...set PAGES is not permitted on the standby when the replication agent is running	Type of Message: Error Cause: You attempted to resize the hash index of a replicated table on a standby or subscriber database while the replication agent is running. Impact: TimesTen cannot perform the operation. User Action: Stop the replication agent before making changes to the table.
8085	Could not retrieve the subscriber list for replication stats	Type of Message: Error Cause: An error occurred while trying to initialize the parallel replication statistics. Impact: The replication agent cannot initialize the parallel replication statistics. User Action: Restart the replication agent. For more information on how to restart the replication agent, see Set Replication Policies in Oracle TimesTen In-Memory Database Reference.
8093	The local replication agent needs to be running for this operation	Type of Message: Error Cause: You attempted to perform an operation while the local replication agent was not running. Impact: TimesTen cannot complete the operation. User Action: Start the local replication agent and retry the operation.
8094	Multiple concurrent executions of this built-in are not permitted	Type of Message: Error Cause: You attempted to call a built-in procedure more than once at the same time. Only one execution of the built-in is allowed at any time. Impact: The replication agent cannot complete the operation. User Action: Wait for the previous call to return and retry the operation.
8095	Truncate table not permitted when ttRepTransmitSet(0) has been invoked on the connection	Type of Message: Error Cause: You attempted to truncate a table when replication was disabled on this connection. Impact: The operation fails. User Action: Allow table truncation by calling the built-in procedure ttRepTransmitSet with argument 1.
8096	Alter table not permitted when ttRepTransmitSet(0) has been invoked on the connection	Type of Message: Error Cause: You attempted to alter a table when replication was disabled on this connection. Impact: The operation fails. User Action: To alter a table, call the built-in procedure ttRepTransmitSet with argument 1.
8097	Error getting parent table during autorefresh bookmark lookup	Type of Message: Error Cause: A table that is part of an autorefreshed cache group is missing. Impact: TimesTen cannot complete the operation. User Action: The operation is retried automatically. If the replication agent cannot recover, check for errors on the reported parent table.
8098	This built-in is not permitted in an active standby pair scheme	Type of Message: Error Cause: You attempted to call a built-in procedure that is not permitted in an active standby scheme. Impact: The replication agent cannot complete the operation. User Action: Drop the active standby pair scheme and retry the operation.
8099	TWOSAFE operation not permitted with AutoCommit = 1.	Type of Message: Error Cause: You attempted to perform a RETURN TWOSAFE transaction when AutoCommit=1. Impact: The replication agent cannot complete the operation. User Action: Set AutoCommit=0 in your current connection and retry the operation.
8100	Invalid parameter value passed in.	Type of Message: Error Cause: You specified an invalid parameter in a built-in procedure call. Impact: The operation fails. User Action: Verify the validity of the parameters passed into the built-in procedure and retry the operation.
8101	ELEMENT element_name specified more than once, is being ALTER'ed or DROP'ed with ADD, already exists, or its owner (MASTER or PROPAGATOR) is already the owner for another ELEMENT with the same database object.	Type of Message: Error Cause: You specified an element name that is not unique within the replication scheme. In addition, a database cannot be a MASTER or PROPAGATOR more than once for any elements with the same underlying database object. Impact: The operation fails. User Action: Ensure that the element name is unique within the replication scheme and retry the operation. For more information, see Defining Replication Elements in Oracle TimesTen In-Memory Database Replication Guide.
8102	STORE database_name specified more than once	Type of Message: Error Cause: You specified a database more than once in the STORE attributes clause of either a CREATE REPLICATION or an ALTER REPLICATION statement. Impact: The operation fails. User Action: Modify your statement and retry the operation. For more information, see Setting STORE Attributes in a Classic Replication Scheme in Oracle TimesTen In-Memory Database Replication Guide.
8103	Attribute_name specified more than once or already defined for STORE database_name	Type of Message: Error Cause: You specified a store attribute more than once in the STORE attributes clause of either a CREATE REPLICATION or an ALTER REPLICATION statement. Impact: The operation fails. User Action: Modify your statement and retry the operation. For more information, see Setting STORE Attributes in a Classic Replication Scheme in Oracle TimesTen In-Memory Database Replication Guide.
8104	ALTER or DROP ELEMENT for element_name following DROP	Type of Message: Error Cause: An ALTER ELEMENT clause cannot follow a DROP ELEMENT clause for the same element in an ALTER REPLICATION statement. Impact: The replication agent cannot perform the operation. User Action: Modify your SQL statement and ensure that the ALTER ELEMENT does not conflict with the DROP ELEMENT for the same element. For more information, see ALTER REPLICATION in Oracle TimesTen In-Memory Database SQL Reference.
8105	STORE database_name does not have a MASTER, PROPAGATOR, or SUBSCRIBER role for any ELEMENT	Type of Message: Warning Cause: You defined a STORE for a replication scheme without assigning it a replication role. This action evokes this warning. Impact: The current STORE is not involved in the declared replication scheme, therefore replication does not occur. User Action: Review your replication scheme and confirm if this is the action you want to perform.
8106	STORE database_name specified as both owner and SUBSCRIBER for replication ELEMENT element_name	Type of Message: Error Cause: You specified a STORE database as owner and SUBSCRIBER for a replication element. A database cannot subscribe to the same element for which it is either the MASTER or PROPAGATOR. Impact: TimesTen cannot perform the SQL operation. User Action: Modify your replication scheme SQL statement and retry the operation. For more information, see Database Names in Oracle TimesTen In-Memory Database Replication Guide.
8107	Cannot specify both ELEMENT DATASTORE and ELEMENT TABLE or SEQUENCE since the former already covers all objects in the database	Type of Message: Error Cause: You specified a table using the ELEMENT DATASTORE clause, which includes all tables in the statement. Impact: The replication agent cannot perform the operation. User Action: Specify a particular table or sequence by removing the ELEMENT DATASTORE clause and using the ELEMENT TABLE or ELEMENT SEQUENCE clause. For more information, see Defining Replication Elements in Oracle TimesTen In-Memory Database Replication Guide.
8108	For TRANSMIT NONDURABLE, must use the ELEMENT <elementname> DATASTORE clause	Type of Message: Error Cause: You attempted to set transmit durability without using an ELEMENT DATASTORE clause. Impact: The operation fails. User Action: Ensure that the nondurable transmits have ELEMENT DATASTORE clauses. For more information, see Setting Transmit Durability on DATASTORE Element in Oracle TimesTen In-Memory Database Replication Guide.
8109	ELEMENT element_name will not have any subscribers	Type of Message: Error Cause: You did not specify a subscriber for the element in the replication scheme. A replicated element must always have at least one subscriber. Impact: The replication agent cannot perform the operation. User Action: You can either remove the element from the scheme or specify a subscriber for the element.
8110	Connection not permitted. This database may require Master Catch-up.	Type of Message: Error Cause: You attempted to connect to a standby database that is ahead of the active database and requires a master catch-up. Impact: The operation fails. User Action: Start the replication agent for the standby database and wait for the master catch-up to complete, and then retry the operation.
8111	Connection not permitted. Master Catch-up in progress.	Type of Message: Error Cause: You attempted to connect to a standby database that is currently performing a master catch-up. Impact: The operation fails. User Action: Wait for the master catch-up to complete and retry the operation.
8112	Operation not permitted. Master Catch-up not complete.	Type of Message: Error Cause: You attempted to update, insert, delete or alter a replicated table on a standby database that is currently performing a master catch-up. Impact: The operation fails. User Action: Wait for the master catch-up to complete and retry the operation.
8113	Operation not permitted since replication DDL or a state change was attempted in the transaction. Please commit/rollback the transaction.	Type of Message: Error Cause: You attempted to replicate DDL in the same operation used to disallow an element. Replication DDL must be in a transaction of its own. Impact: The replication agent cannot complete the operation. User Action: Commit or rollback the transaction.
8114	Failure resetting replication catch-up status.	Type of Message: Error Cause: You attempted to perform a duplicate operation from a node in an active standby database to another and the source node is not in the correct state. Impact: TimesTen cannot complete the operation. User Action: Perform the duplicate operation from the correct database. Alternatively, set the state of the source database.
8118	Column column_name of table owner_name.table_name is longer than the maximum column size of number bytes when used with replication.	Type of Message: Error Cause: You specified a column that violates the maximum size limit for replicated columns. Impact: TimesTen cannot complete the operation. User Action: Review the error message for the maximum size limit for columns, specify the column and retry the operation.
8119	Set name operation skipped as the new name for the element (element_name) matches the current name.	Type of Message: Error Cause: You attempted to change an element name and the new name matches the existing name. Impact: TimesTen cannot complete the operation. User Action: Provide a unique name for the set operation.
8120	The TRANSMIT NONDURABLE clause can only be used with a DATASTORE element	Type of Message: Error Cause: The TRANSMIT NONDURABLE attribute can be specified only for database replication elements. Impact: TimesTen cannot complete the SQL operation. User Action: Modify the SQL statement accordingly and retry the operation.
8121	localhost, 127.0.0.1, ::1 or 0:0:0:0:0:0:0:1 cannot be used as a host identifier.	Type of Message: Error Cause: The IP address 'localhost' or any of its aliases cannot be used as a host identifier. Impact: TimesTen cannot complete the operation. User Action: Modify the SQL statement accordingly and retry the operation.
8122	The replication scheme name cannot begin with '_'	Type of Message: Error Cause: You attempted to create a replication scheme that begins with '_'. Impact: TimesTen cannot complete the operation. User Action: Rewrite the operation scheme name that does not start with '_' and retry the operation.
8123	An ACTIVE STANDBY PAIR scheme does not exist	Type of Message: Error Cause: You attempted to use an ALTER ACTIVE STANDBY PAIR or DROP ACTIVE STANDBY PAIR statement on a database without an active standby pair replication scheme. Impact: TimesTen cannot perform the operation. User Action: None. For more information on active standby pair replication schemes, see Defining an Active Standby Pair Replication Scheme in Oracle TimesTen In-Memory Database Replication Guide.
8124	Store database_name has been specified as an ACTIVE STANDBY PAIR node and a SUBSCRIBER	Type of Message: Error Cause: You attempted to use a CREATE ACTIVE STANDBY PAIR statement while attempting to designate the specified database as both a master database and a subscriber database. Impact: TimesTen cannot create the active standby pair replication scheme. User Action: Define the specified database as a master database or a subscriber database, and retry the operation. For more information on CREATE ACTIVE STANDBY PAIR, see CREATE ACTIVE STANDBY PAIR in Oracle TimesTen In-Memory Database SQL Reference.
8125	The database cannot be dropped from the ACTIVE STANDBY PAIR scheme because it is a MASTER node	Type of Message: Error Cause: You attempted to drop a master database that is part of an active standby pair. Impact: TimesTen cannot complete the operation. User Action: Modify the SQL statement accordingly and retry the operation.
8126	An ACTIVE STANDBY PAIR replication scheme already exists and must be the only replication scheme for the database.	Type of Message: Error Cause: You attempted to create an active standby pair using a database that is already in an active standby pair. A database cannot be in two active standby pairs. Impact: TimesTen cannot complete the operation. User Action: Drop the current active standby pair by using the DROP ACTIVE STANDBY PAIR command.
8127	Cannot create ACTIVE STANDBY PAIR scheme because another replication scheme already exists.	Type of Message: Error Cause: You attempted to create an active standby pair, but a replication scheme already exists. Impact: TimesTen cannot complete the operation. User Action: Modify the SQL statement accordingly and retry the operation.
8128	Store database_name is already in the ACTIVE STANDBY PAIR scheme.	Type of Message: Error Cause: You attempted to add a database using ALTER ACTIVE STANDBY PAIR and the database is already in the active standby pair. Impact: TimesTen cannot complete the operation. User Action: Modify the SQL statement accordingly and retry the operation.
8129	Store database_name: The \"attribute_name\" attribute cannot be set for database_name in an ACTIVE STANDBY PAIR scheme.	Type of Message: Error Cause: You attempted to set invalid attributes for a database in an ACTIVE STANDBY PAIR scheme. You can only set the PORT and TIMEOUT attributes for subscribers. Impact: TimesTen cannot complete the operation. User Action: Ensure you set the valid attributes and retry the operation.
8130	CREATE ACTIVE STANDBY PAIR must only be run on one of the MASTER nodes.	Type of Message: Error Cause: You attempted to run the CREATE ACTIVE STANDBY PAIR statement from an invalid node. You can run it only from one of the nodes on which a master database resides. For example, CREATE ACTIVE STANDBY PAIR rep1, rep2 SUBSCRIBER rep3 must be run from the node on which rep1 or rep2 resides. Impact: TimesTen cannot complete the operation. User Action: Ensure you are running the statement from a valid node.
8131	Object_type owner_name.object_name is already part of the replication scheme, or is in the process of being string.	Type of Message: Error Cause: You attempted to add an object to a replication scheme, but the object is already part of the replication scheme or is already in the process of being added to the replication scheme. Impact: TimesTen cannot complete the operation. User Action: Modify the SQL statement accordingly and retry the operation.
8132	Clause_name object_type cannot be used on TABLE element element_name. The operation is for DATASTORE level elements only.	Type of Message: Error Cause: You attempted to include or exclude a table-level element. Impact: TimesTen cannot complete the operation. User Action: Modify the SQL statement accordingly and retry the operation.
8133	You cannot clause_type table owner_name.table_name because it is part of a cache group. Use clause_type CACHE GROUP instead.	Type of Message: Error Cause: You attempted to include or exclude a cache group table. Impact: TimesTen cannot complete the operation. User Action: Retry the operation using clause_type CACHE GROUP.
8134	Store database_name is not a MASTER for any DATASTORE element.	Type of Message: Error Cause: The ALTER ELEMENT statement did not find a matching element name in the database. Impact: TimesTen cannot complete the operation. User Action: Modify the SQL statement accordingly and retry the operation.
8135	Object_type owner_name.table_name is not part of DATASTORE element element_name, or is in the process of being excluded.	Type of Message: Error Cause: You attempted to exclude a table or sequence that is not in the replication scheme or that is already in the process of being excluded. Impact: TimesTen cannot complete the operation. User Action: Modify the SQL statement accordingly and retry the operation.
8136	All tables, cache groups, or sequences cannot be excluded from element element_name. Use DROP ELEMENT instead.	Type of Message: Error Cause: You attempted to exclude all tables or cache groups from an element. Impact: TimesTen cannot complete the operation. User Action: Either ensure that there is at least one object in an element when dropping another or use the DROP ELEMENT command.
8137	Cannot exclude object_type owner_name.object_name because it is not in the ACTIVE STANDBY PAIR scheme.	Type of Message: Error Cause: You attempted to exclude a table or sequence from the databases by using an ALTER ACTIVE STANDBY PAIR...EXCLUDE statement, but the table or sequence is not in the active standby pair. Impact: TimesTen cannot complete the operation. User Action: Run the ttIsql repschemes command to verify if the object you want to exclude is part of the replication scheme. The element might already be excluded. Otherwise, contact TimesTen Customer Support.
8138	All tables, cache groups, or sequences cannot be excluded from the ACTIVE STANDBY PAIR scheme.	Type of Message: Error Cause: You attempted to exclude all tables and cache groups from the databases in an ALTER ACTIVE STANDBY PAIR...EXCLUDE statement. Impact: TimesTen cannot complete the operation. User Action: At least one object must be replicated by an active standby pair. If you do not want to replicate anything, use the DROP ACTIVE STANDBY PAIR SQL statement.
8139	The specified peer database is not in the STANDBY state	Type of Message: Error Cause: You attempted to perform an operation for a database that was not in a standby state. The operation is only permitted on databases that are in the standby state. Impact: TimesTen cannot complete the operation. User Action: Use the ttRepStateGet built-in procedure to check the replication state of the database. If the TimesTen replication agent has been started and the replication state of the database remains IDLE, contact TimesTen Customer Support. For more information on the ttRepStateGet procedure, see ttRepStateGet in Oracle TimesTen In-Memory Database Reference.
8140	Scheme does not exist or inconsistency detected in the local ACTIVE STANDBY PAIR scheme	Type of Message: Error Cause: Error returned for a database with an inconsistent or corrupted active standby replication scheme. Impact: TimesTen cannot complete the operation. User Action: Contact TimesTen Customer Support.
8141	Local database not eligible to be set to the ACTIVE state	Type of Message: Error Cause: You attempted to set to the ACTIVE state a local database that is part of an active standby pair . Impact: TimesTen cannot complete the operation. User Action: Check your replication scheme as this store is not allowed to take the ACTIVE state.
8142	Error checking on database header attributes	Type of Message: Error Cause: An error occurred while reading the database header for attributes related to the active standby replication scheme. Impact: TimesTen cannot complete the operation. User Action: Contact TimesTen Customer Support.
8143	The STANDBY can only be duplicated from the ACTIVE	Type of Message: Error Cause: You attempted to duplicate from a store that is not in the ACTIVE state. A database that is in the STANDBY state for an active standby pair can be duplicated only from the active database. Impact: TimesTen cannot complete the operation. User Action: Use the ttRepStateGet built-in procedure to check the replication state of the database. If it is not in the ACTIVE state, ensure that you are connected to the correct store and that the state of the database is set to ACTIVE by using the CALL ttRepStateSet('ACTIVE'); procedure. For more information on the ttRepStateGet and ttRepStateSet procedures, see ttRepStateGet and ttRepStateSet, respectively, in the Oracle TimesTen In-Memory Database Reference.
8144	Duplicate not permitted. Reason: error_message. Duplicate is only permitted from the ACTIVE database to the STANDBY database, from the STANDBY database to a SUBSCRIBER, or from the ACTIVE database to a SUBSCRIBER if the STANDBY database has failed	Type of Message: Error Cause: You attempted to duplicate a subscriber database from a database that is not the standby. Subscriber databases in a active standby pair can be duplicated only from the standby database or from the active database when the standby database is in a FAILED state. Impact: TimesTen cannot complete the operation. User Action: Ensure you are on the standby database and use the ttRepStateGet built-in procedure to check the replication state of the database. If the database is in the FAILED state, set the standby database to FAILED by calling ttRepSubscriberStateSet('FAILED') on the active database. Then, retry the operation from the active database. For more information on the ttRepStateGet and ttRepStateSet procedures, see ttRepStateGet in Oracle TimesTen In-Memory Database Reference.
8145	The local database needs to be in the ACTIVE state for this operation	Type of Message: Error Cause: You attempted to perform an operation in a database that is part of an active standby pair and that is not in the ACTIVE state. Impact: TimesTen cannot complete the operation. User Action: Set the state of the database to ACTIVE and retry the operation.
8146	There can be only one INCLUDE or EXCLUDE clause for object_type.	Type of Message: Error Cause: You attempted to perform an operation that included more than one INCLUDE or EXCLUDE clause for an object type (cache group or table). This is an example of an invalid clause: ALTER ACTIVE STANDBY PAIR INCLUDE TABLE t EXCLUDE table u. Impact: TimesTen cannot complete the operation. User Action: Separate the SQL statements and retry the operations. Ensure that only one INCLUDE or EXCLUDE clause is present when performing ALTER ACTIVE STANDBY PAIR.
8147	INCLUDE and EXCLUDE can only be used on DATASTORE level elements.	Type of Message: Error Cause: You attempted to use an INCLUDE or EXCLUDE clause with a table element definition in a CREATE TABLE or CREATE ACTIVE STANDBY PAIR statement. Impact: TimesTen cannot complete the operation. User Action: Modify your SQL statement and retry the operation.
8148	Host name exceeds limit of number characters	Type of Message: Error Cause: You specified a host name that exceeds the maximum number of characters permitted. The message indicates the character limit. Impact: TimesTen cannot complete the operation. User Action: Review the error message for the maximum number of characters permitted, modify the host name and retry the operation.
8149	Data store name exceeds limit of number characters	Type of Message: Error Cause: You specified a data store name that exceeds the maximum number of characters permitted. The message indicates the character limit. Impact: TimesTen cannot complete the operation. User Action: Review the error message for the maximum number of characters permitted, modify the data store name and retry the operation.
8150	This change is not allowed while the replication agent for database database_name is running. Please stop the replication agent to perform this change.	Type of Message: Error Cause: You attempted to use an ALTER REPLICATION statement that is not allowed while the replication agent for the database is running. Impact: TimesTen cannot perform the specified ALTER REPLICATION statement. User Action: Use the ttRepStop built-in procedure or the ttAdmin -repStop utility to stop the replication agent for the master and subscriber databases. Then, retry the ALTER REPLICATION statement on both master and subscriber databases. You can restart the replication agent with the ttRepStart built-in procedure or the ttAdmin -repStart utility. For more information on replication scheme changes, see Altering a Classic Replication Scheme in Oracle TimesTen In-Memory Database Replication Guide. For more information on the ttRepStop built-in procedure, see ttRepStop in the Oracle TimesTen In-Memory Database Reference. For more information on the ttAdmin utility, see ttAdmin in the Oracle TimesTen In-Memory Database Reference.
8151	Owner_name.table_name's replication role disallows the requested operation	Type of Message: Error Cause: You requested an operation that is not allowed. Replication denies write access to a database object underlying a replication element for which it is a subscriber or propagator, provided that the local database is not the master for any other element with the same underlying database object. A subscriber cannot modify any tables if it is not a master for another store. Impact: TimesTen cannot complete the operation. User Action: Ensure that you are connected to the database. Alternatively, run the ttIsql repschemes command to check the replication schema and modify it accordingly. For more information about the ttIsql repschemes command, see Display Configuration Information with the ttIsql repschemes Command in Oracle TimesTen In-Memory Database Replication Guide.
8152	No ODBC type for column owner_name.table_name.column_name	Type of Message: Error Cause: The type for a column in a replicated table could not be mapped to a known ODBC data type. Impact: TimesTen cannot complete the operation. User Action: Check the compatibility of the data types that are being converted. For more information, see Data Types in Oracle TimesTen In-Memory Database SQL Reference.
8153	STORE database_name is already role_type of the specified ELEMENT(s)	Type of Message: Error Cause: You used ALTER REPLICATION ALTER ELEMENT SET OWNER to reassign an element to its current owner (MASTER or PROPAGATOR). This action is allowed but it evokes this warning. Impact: None. User Action: None.
8154	REPLICATION scheme owner_name.scheme_name already exists	Type of Message: Error Cause: You specified a replication scheme that already exists. The CREATE REPLICATION statement requires that each new replication scheme specified to a database have a different owner_name.scheme_name from any replication scheme already defined there. Impact: TimesTen cannot complete the operation. User Action: Specify a replication scheme with a different owner and/or name and retry the operation.
8155	ELEMENT element_name already has SUBSCRIBER subscriber_name	Type of Message: Error Cause: You specified subscription that already exists. A database can subscribe to a replication element only once. Impact: TimesTen cannot complete the operation. User Action: None. For more information, see Defining Replication Elements in Oracle TimesTen In-Memory Database Replication Guide.
8156	Internal error: Column column_name for ELEMENT element_name already defined for SUBSCRIBER subscriber_name	Type of Message: Internal Error Cause: The replication agent attempted to re-add column information for a replicated table. Common causes for this are: - Table definitions are out of synchronization. - An ALTER TABLE statement was applied concurrently to both sides of the replication scheme. Impact: None. User Action: Check the specified table definitions on both sides of the replication scheme for the listed causes. For additional help, contact TimesTen Customer Support.
8157	No ELEMENT element_name found for REPLICATION owner_name.scheme_name	Type of Message: Error or Warning Cause: A replication element cannot be found for the requested operation. This is a warning when the request is for an indefinite number of elements (* IN database_name). It is an error when the statement specifies one particular element. Impact: None. User Action: Ensure that your REPLICATION statement contains a valid element name and a definite number of elements.
8158	Failed to retrieve LSN data for initializing PEER	Type of Message: Error Cause: A MASTER or PROPAGATOR database could not get its local LSN to initialize a (subscribing) peer database. Impact: The operation failed. User Action: Retry the operation.
8159	No SUBSCRIBER PEER information found in REPLICATION owner_name.scheme_name for MASTER or PROPAGATOR database database_name	Type of Message: Error Cause: You requested a DROP REPLICATION in a replication scheme that does not have subscriber peers to delete. This operation is allowed, but it evokes a warning. Impact: The operation evokes this warning. User Action: Review the operation you attempted to perform and, if needed, retry it with the proper arguments.
8160	REPLICATION owner_name.scheme_name not found	Type of Message: Error Cause: You specified a replication scheme in an ALTER REPLICATION or DROP REPLICATION request, which is not registered in the TTREP.REPLICATIONS table. Impact: The local database cannot find the replication scheme specified in the request. User Action: Verify that you specified the correct replication owner and scheme name in your request.
8161	No STORE database_name found for REPLICATION owner_name.scheme_name	Type of Message: Error Cause: You specified a database for the STORE in an ALTER REPLICATION ALTER STORE or DROP REPLICATION request that cannot be found. Impact: TimesTen cannot find the database specified in the request. User Action: Verify that you specified the correct database name in your request.
8162	No subscriptions found for ELEMENT element_name in REPLICATION owner_name.scheme_name	Type of Message: Error Cause: No subscriptions could be found for an element in an ALTER REPLICATION DROP ELEMENT, ALTER REPLICATION ALTER ELEMENT DROP SUBSCRIPTION, ALTER REPLICATION ALTER ELEMENT SET OWNER or DROP REPLICATION request. Impact: TimesTen cannot find the subscriptions for the element. User Action: Verify that you specified the correct arguments in your statement.
8163	Failed to retrieve table or column descriptor for table owner_name.table_name	Type of Message: Error Cause: You attempted to create a replication element for CREATE REPLICATION or ALTER REPLICATION ADD ELEMENT and the information about the table could not be retrieved. Impact: Information about the underlying table could not be retrieved. User Action: Verify the arguments in the statement you attempted to execute. If there should be information about the table, contact TimesTen Customer Support. You can also manually check the TTREP tables for any possible problems.
8165	Replication schema is inconsistent	Type of Message: Internal Error Cause: The replication agent has detected an inconsistency in its schema. Impact: The replication schema may not work correctly. User Action: Contact TimesTen Customer Support.
8166	Log not writable or transaction not initiated by system	Type of Message: Error Cause: You requested a replication DDL, but transaction logging was disabled for transaction rollback. Impact: TimesTen cannot complete the operation. User Action: Enable transaction logging and retry the operation.
8167	Cannot determine system table attributes (e.g. REPACCESS) for table_name from replication role	Type of Message: Error Cause: Internal error. Impact: TimesTen cannot complete the operation. User Action: Contact TimesTen Customer Support.
8168	Cannot set system table attributes (e.g. REPACCESS) for table_name from replication role	Type of Message: Error Cause: Internal error. Impact: TimesTen cannot complete the operation. User Action: Contact TimesTen Customer Support.
8169	Database database_name already transmits to database database_name; at most one path allowed from one database to another	Type of Message: Error Cause: You attempted to configure a replication scheme with an element that has the same master or propagator and subscriber as an element in another replication scheme. Two such elements must reside in the same replication scheme. Impact: TimesTen cannot complete the operation. User Action: Verify the statement you attempted to execute and modify it accordingly. Either include any new elements in the existing replication scheme or drop it to create a new one. For more information, see Defining Replication Elements in Oracle TimesTen In-Memory Database Replication Guide.
8170	Receipt or commit acknowledgment not returned in the specified timeout interval for XID:connection_id.counter	Type of Message: Error Cause: A subscriber with RETURN RECEIPT or RETURN TWOSAFE service did not receive a commit acknowledgment within the current connection time limit. This can occur when the subscriber Replication Agent is not running or the standby replication state is set to STOPPED. For an active standby pair, this can occur when the standby replication agent is not running and the standby has not been declared as "failed" on the active. Impact: TimesTen cannot complete the operation. User Action: Adjust the connection time limit with a call to ttRepSyncGet, as described in Managing return service timeout errors and replication state changes in Oracle TimesTen In-Memory Database Replication Guide.
8171	Replicating a system table (owner_name.table_name) is not permitted	Type of Message: Error Cause: You attempted to specify one of the SYS.* or TTREP.* tables that the system creates and maintains as a replicated object. These tables cannot be replicated. Impact: TimesTen cannot complete the operation. User Action: Do not specify SYS.* or TTREP.* tables as replicated objects.
8172	The database database_name is already specified with an equivalent host name as database_name	Type of Message: Error Cause: You used two different forms of host name to refer to one particular database in a replication scheme. Impact: TimesTen cannot complete the operation. User Action: Use the same form of host name consistently to refer to any one database.
8173	Replication may not be configured while XA transactions are active	Type of Message: Error Cause: You attempted to configure replication while XA transactions are active. TimesTen Replication is not supported with XA transactions. Impact: TimesTen cannot complete the operation. User Action: Do not use TimesTen Replication while XA transactions are active.
8174	Attribute_name specified more than once	Type of Message: Error Cause: You specified more than one value for an attribute. Impact: TimesTen cannot complete the operation. User Action: Remove one of the instances of the attribute specification and retry the operation.
8175	Report file name 'file_name' cannot be resolved	Type of Message: Error Cause: You attempted to configure a conflict resolution report file to a non-existent directory. Impact: TimesTen cannot complete the operation. User Action: Use a valid path to the report file and retry the operation.
8176	Conflict checking configuration conflict between elements element_name and element_name with the same underlying table	Type of Message: Error Cause: You attempted to configure a partial database replication, but a replication scheme that covers the entire database already exists. Impact: TimesTen cannot complete the operation. User Action: Drop the existing replication scheme using DROP REPLICATION, and then create a new replication scheme using the CREATE REPLICATION statement.
8177	Executing database (database_name) not permitted to operation_name	Type of Message: Error Cause: You attempted to drop a replicating element, but the replication scheme you specified covers the entire database and the TRANSMIT NONDURABLE option is set. Impact: TimesTen cannot drop the replicating element. User Action: If needed, drop the replication scheme, and then create a new replication scheme using the CREATE REPLICATION statement.
8178	Cannot set a subscriber to state code number	Type of Message: Error Cause: TimesTen cannot specify the TRANSMIT NONDURABLE option for the replication scheme because the scheme does not cover the entire database. The NONDURABLE option must apply to the entire database. Impact: TimesTen cannot complete the operation. User Action: If needed, drop the replication scheme, and then create a new replication scheme using the CREATE REPLICATION statement. Use the ELEMENT DATASTORE clause with the TRANSMIT NONDURABLE option. See Setting Transmit Durability on DATASTORE Element in Oracle TimesTen In-Memory Database Replication Guide.
8179	Cannot create duplicate database : database already exists	Type of Message: Error Cause: You attempted to overwrite an existing database during an operation to duplicate databases. Impact: TimesTen cannot complete the operation. User Action: Verify the database that you are attempting to duplicate. If you do not need the one that is already created, destroy it using ttDestroy, and then retry the duplicate operation. For more information about ttDestroy, see ttDestroy in Oracle TimesTen In-Memory Database Reference.
8180	Full versus partial replication conflict with an existing replication scheme on database database_name	Type of Message: Error Cause: When a DATASTORE element is used on a particular database for replication, no other element type can be used either in the same scheme or in any other scheme. Impact: TimesTen cannot complete the operation. User Action: Do not use other element type when a DATASTORE element is used on a particular database for replication. See Defining the DATASTORE Element in Oracle TimesTen In-Memory Database Replication Guide.
8182	Cannot configure conflict checking on DATASTORE element	Type of Message: Error Cause: You attempted to configure conflict resolution for replication using the DATASTORE element. This element cannot not be used for the operation. Impact: TimesTen cannot complete the operation. User Action: Configure Replication for each individual table. See Resolving Replication Conflicts in Oracle TimesTen In-Memory Database Replication Guide.
8183	Cannot alter element because it is owned and managed by the system	Type of Message: Error Cause: You attempted to run ALTER REPLICATION on elements created as part of the DATASTORE element configuration. Impact: TimesTen cannot complete the operation. User Action: Run ALTER REPLICATION on the DATASTORE element itself.
8184	Attempt to configure replication_type replication for a database with no permanent objects	Type of Message: Error Cause: You attempted to configure database-level replication or active standby replication with an empty database. Impact: TimesTen cannot complete the operation. User Action: Before configuring a replication scheme, create at least one object, such as a table.
8185	Attempt to exceed limit for return receipt subscribers	Type of Message: Error Cause: The number of subscribers to receive RETURN RECEIPT replication updates exceeds the system specified limit. Impact: TimesTen cannot complete the operation. User Action: Specify a number of subscribers that does not exceed the limit.
8187	A Return receipt transaction has not been executed on this connection	Type of Message: Error Cause: A transaction with return receipt replication updates has not been run on the connection. Impact: TimesTen cannot complete the operation. User Action: Verify that you are in a transaction with return receipt on.
8188	Transaction handle not valid	Type of Message: Error Cause: You specified a handle that is not valid for examining the status of a transaction with RETURN RECEIPT replication. Impact: TimesTen cannot complete the operation. User Action: Specify a valid transaction handle and retry the operation.
8189	Transaction token subscriber information not available	Type of Message: Error Cause: The replication subscriber cannot be found in the replication scheme. Impact: TimesTen cannot complete the operation. User Action: Verify that the replication scheme contains the subscriber. If it does, contact TimesTen Customer Support.
8190	Host name host_name could not be resolved	Type of Message: Error Cause: You specified a host name that cannot be resolved on this host. Impact: TimesTen cannot complete the operation. User Action: Check the host name and make changes to the network host name lookup if it is not correct. See Configuring Network Interfaces When Not Using the ROUTE Clause in Oracle TimesTen In-Memory Database Replication Guide.
8191	This database (database_name on host_name) is not involved in a replication scheme	Type of Message: Error Cause: Possible causes for this error message are: The replication agent does not start if the database does not participate in any replication scheme. Either no replication scheme is defined on this database or the database is not part of any replication scheme. The replication agent cannot determine that the current running host is involved in the specified replication scheme. Impact: TimesTen cannot complete the operation. User Action: Possible solutions for this error message are: If a replication scheme is defined, verify that the name of each database involved in replication matches the names specified in the DataStore attribute in their respective DSN definitions. This name may be different from the names specified for the Data Source Name attribute in the DSNs. Confirm that you identified your database hosts correctly, as described in Configuring Network Interfaces When Not Using the ROUTE Clause in Oracle TimesTen In-Memory Database Replication Guide.
8192	Dropping/adding a foreign key that references a replicated table is not allowed while the replication agent for database database_name is running. Please stop the replication agent to perform this operation.	Type of Message: Error Cause: You attempted to add or drop a foreign key in a table that references a replicated table. This operation is not allowed. Impact: TimesTen cannot complete the operation. User Action: Stop the replication agents, add or drop the foreign key in the table that references the replicated table, and restart the replication agents. See Starting and Stopping the Replication Agents in Oracle TimesTen In-Memory Database Replication Guide for details on how to stop and restart the replication agents.
8193	The TWOSAFE subscriber attribute is only permitted on a DATASTORE element.	Type of Message: Error Cause: You attempted to configure RETURN TWOSAFE with a table element. Impact: TimesTen cannot complete the operation. User Action: Change the ELEMENT type to DATASTORE or remove RETURN TWOSAFE from the replication scheme. For more information, see Return Twosafe Replication in Oracle TimesTen In-Memory Database Replication Guide.
8194	The TWOSAFE subscriber attribute is not permitted on a propagator element.	Type of Message: Error Cause: You attempted to configure RETURN TWOSAFE for a propagator database. Impact: TimesTen cannot complete the operation. User Action: Do not use the RETURN TWOSAFE service in a propagation scheme. See Return Twosafe Replication in Oracle TimesTen In-Memory Database Replication Guide for details.
8195	The TWOSAFE subscriber attribute requires an exclusive bi-directional configuration.	Type of Message: Error Cause: You attempted to configure RETURN TWOSAFE in an invalid replication scheme. Impact: TimesTen cannot complete the operation. User Action: Use RETURN TWOSAFE only in a bi-directional scheme between a master and a single subscriber database. See Return Twosafe Replication in Oracle TimesTen In-Memory Database Replication Guide for details.
8196	Remote application of the transaction ran into error : error_details Please rollback the transaction.	Type of Message: Error Cause: The RETURN TWOSAFE transaction ran into an error when it was applied on the subscriber. Impact: The transaction was not applied to the subscriber. User Action: Roll back the transaction on the master.
8197	Operation not permitted once commit processing has begun	Type of Message: Error Cause: A commit call has already been issued for this RETURN TWOSAFE transaction. Therefore, the operation is not permitted. Impact: TimesTen cannot complete the operation. User Action: Retry the commit operation before starting a new operation. If the commit cannot be completed and a rollback is not possible, contact TimesTen Customer Support. For more information on local commit for return services, see Using a Return Service in Oracle TimesTen In-Memory Database Replication Guide.
8198	A 2-safe transaction has not been executed on this connection	Type of Message: Error Cause: You attempted to get the replication status of a RETURN TWOSAFE transaction when no RETURN TWOSAFE transaction has been executed. Impact: TimesTen cannot complete the operation. User Action: Execute a RETURN TWOSAFE transaction on this connection and retry the operation.
8199	A 2-safe or return receipt transaction has not been executed on this connection	Type of Message: Error Cause: You attempted to get the replication status of a RETURN TWOSAFE or RETURN RECEIPT transaction when no transaction has been executed. Impact: TimesTen cannot complete the operation. User Action: Execute a RETURN TWOSAFE or RETURN RECEIPT transaction on this connection and retry the operation.
8200	Attempt to drop all columns in table	Type of Message: Error Cause: You attempted to drop all columns in a table. Impact: TimesTen cannot complete the operation. User Action: Consider using DROP TABLE to drop the table instead.
8201	Column is part of the table's primary key	Type of Message: Error Cause: You attempted to drop a column that is part of a primary key. Impact: TimesTen cannot complete the operation. User Action: Consider dropping and re-creating the table.
8202	Column is part of a foreign key	Type of Message: Error Cause: You attempted to drop a column that is part of a foreign key. Impact: TimesTen cannot complete the operation. User Action: Consider dropping and re-creating the table.
8203	Attempt to drop indexed column	Type of Message: Error Cause: An application attempted to drop an indexed column in a table. Impact: TimesTen cannot complete the operation. User Action: Consider dropping the index, and then dropping the column.
8204	Columns have been added to table too many times	Type of Message: Error Cause: The operation is not permitted because the table would have more than the maximum number of partitions. For more information, see System Limits and Defaults in Oracle TimesTen In-Memory Database Reference. Impact: TimesTen cannot complete the operation. User Action: Consider rebuilding the table, either using INSERT...SELECT or the ttBulkCp utility. For more information about the INSERT...SELECT SQL statement, see INSERT...SELECT in Oracle TimesTen In-Memory Database SQL Reference. For more information about the ttBulkCp utility, see ttBulkCp in the Oracle TimesTen In-Memory Database Reference.
8206	Invalid parameter value value passed in.	Type of Message: Error Cause: You passed an invalid input parameter into an active standby pair. Impact: TimesTen cannot complete the operation. User Action: Pass a valid input parameter and retry the operation.
8207	Replicating a system sequence (owner_name.sequence_name) is not permitted	Type of Message: Error Cause: Objects owned by SYS and TTREP are system objects. You cannot perform operations on these items, including involving them in a replication scheme. Impact: TimesTen cannot complete the operation. User Action: Remove the sequence from your replication scheme.
8208	Replication FailThreshold exceeded: error_message	Type of Message: Error Cause: You are attempting to create an active standby pair replication scheme on a database that already contains AWT cache groups. There is an existing propagation backlog between TimesTen and the Oracle database for the AWT cache group(s) which is greater than the FAILTHRESHOLD parameter value you specified for the CREATE ACTIVE STANDBY PAIR command. Impact: TimesTen cannot create the active standby pair replication scheme. User Action: Wait for the existing propagation backlog to propagate from TimesTen to the Oracle database, then retry the CREATE ACTIVE STANDBY PAIR command. Alternatively, you can specify a higher FAILTHRESHOLD parameter value for the CREATE ACTIVE STANDBY PAIR command. For more information about the CREATE ACTIVE STANDBY PAIR command, see CREATE ACTIVE STANDBY PAIR in Oracle TimesTen In-Memory Database SQL Reference.
8209	Cannot drop a primary key	Type of Message: Error Cause: You attempted to drop a primary key. Impact: TimesTen cannot drop the primary key. User Action: None.
8210	Table reference of table_name is ambiguous	Type of Message: Error Cause: You referenced a table and more than one table with a matching foreign key constraint was found. Impact: TimesTen cannot complete the operation. User Action: Qualify all references to other tables with an owner name.
8211	Table table_name is not a member of the cache group	Type of Message: Error Cause: You referenced a table that is not a member of the cache group. Impact: TimesTen cannot complete the operation. User Action: Ensure that a foreign key constraint from within the cache group does not reference tables external to the cache group. See Cache Groups and Cache Tables in Oracle TimesTen In-Memory Database Cache Guide.
8212	Multiple foreign keys defined for table table_name	Type of Message: Error Cause: Foreign keys for a cache group table have been found to refer to more than one table. Impact: TimesTen cannot complete the operation. User Action: Ensure that all foreign keys for a cache group table only refer to a single table within the same cache group. See Cache Groups and Cache Tables in Oracle TimesTen In-Memory Database Cache Guide.
8213	Cache group tables must have a primary key.	Type of Message: Error Cause: The cache group table does not have a primary key. Impact: TimesTen cannot complete the operation. User Action: Ensure that all tables within a cache group have a primary key. See Cache Groups and Cache Tables in Oracle TimesTen In-Memory Database Cache Guide.
8214	Cache source cache_group_name is not supported	Type of Message: Error Cause: You attempted to use cache group tables, which currently work only with Oracle database data sources. Impact: TimesTen cannot complete the operation. User Action: Do not use cache group table for this operation.
8217	Invalid duration value	Type of Message: Error Cause: You specified an invalid cache group duration value. Impact: TimesTen cannot complete the operation. User Action: Ensure that the cache group duration value is a positive integer and retry the operation.
8220	Table table_name is both read only and propagated	Type of Message: Error Cause: You attempted to mark a cache group table as READONLY and PROPAGATE simultaneously. Impact: TimesTen cannot complete the operation. User Action: Ensure that cache group tables are not simultaneously marked as both READONLY and PROPAGATE. See PROPAGATE Cache Table Attribute in Oracle TimesTen In-Memory Database Cache Guide.
8221	No parent table found	Type of Message: Error Cause: No table in the cache group was found to be a root table. Impact: TimesTen cannot complete the operation. User Action: Ensure that only one table in a cache group has any foreign key constraints. All other tables in a cache group must refer to a single table within the same cache group. See Cache Groups and Cache Tables in Oracle TimesTen In-Memory Database Cache Guide.
8222	Multiple parent tables found	Type of Message: Error Cause: Multiple potential root tables were found within the cache group. Impact: TimesTen cannot complete the operation. User Action: Ensure that only one table in a cache group has foreign key constraints. All other tables in a cache group must refer to a single table within the same cache group. See Cache Groups and Cache Tables in Oracle TimesTen In-Memory Database Cache Guide.
8223	A referenced primary key is not found in the associated parent table	Type of Message: Error Cause: You referenced a primary key that was not found in the cache group. Impact: TimesTen cannot complete the operation. User Action: Verify the primary key reference. See Cache Groups and Cache Tables in Oracle TimesTen In-Memory Database Cache Guide.
8224	Cache group cache_group_name already exists	Type of Message: Error Cause: You attempted to create a cache group that already exists. Impact: TimesTen cannot complete the operation. User Action: If you want to create a new cache group, specify a unique name and retry the operation.
8225	Table table_name is read only	Type of Message: Error Cause: You attempted to update a table marked as READONLY. Impact: TimesTen cannot complete the operation. User Action: Do not update tables within a cache group that are marked as READONLY.
8226	Column column_name is read only	Type of Message: Error Cause: Internal error. Impact: TimesTen cannot complete the operation. User Action: Contact TimesTen Customer Support.
8227	Cache group cache_group_name not found	Type of Message: Error Cause: You referenced a cache group that does not exist. Impact: TimesTen cannot complete the operation. User Action: Reference a cache group that exists and retry the operation.
8228	Cannot drop cache group table table_name; please use DROP CACHE GROUP instead	Type of Message: Error Cause: You attempted to drop tables within a cache group using the DROP TABLE statement. Impact: TimesTen cannot complete the operation. User Action: Use the DROP CACHE GROUP statement to drop tables within a cache group.
8229	Memory threshold value must be between 0 and 100	Type of Message: Error Cause: You specified an invalid value for the cache group aging memory threshold. Impact: TimesTen cannot complete the operation. User Action: Specify a percentage value between zero and 100 for the cache group aging memory threshold.
8230	Aging interval value must be greater than zero	Type of Message: Error Cause: You specified an invalid value for the cache group aging interval. Impact: TimesTen cannot complete the operation. User Action: Specify a value greater than zero for the cache group aging interval.
8231	Cache groups are not supported on this platform	Type of Message: Error Cause: You attempted to use cache groups, but they are not supported in this version of the product. Impact: TimesTen cannot complete the operation. User Action: For a list of supported platforms, see "Platforms and compilers" in the Oracle TimesTen In-Memory Database Release Notes (README.html) in your installation directory.
8232	Oracle PassThrough not supported on this platform. PassThrough value must be set to 0	Type of Message: Error Cause: You attempted to use the PassThrough attribute, which is not supported on this platform. Impact: TimesTen cannot complete the operation. User Action: For a list of supported platforms, see "Platforms and compilers" in the Oracle TimesTen In-Memory Database Release Notes (README.html) in your installation directory.
8233	PassThrough value must be between 0 and 3	Type of Message: Error Cause: You specified an incorrect value for the PassThrough attribute. Impact: TimesTen cannot complete the operation. User Action: Reset the PassThrough attribute to a value between 0 and 5, as described in Setting a Passthrough Level in Oracle TimesTen In-Memory Database Cache Guide.
8234	PassThrough command is no longer valid. One possible cause is creation of a new table on the TimesTen database	Type of Message: Error Cause: After creating a table in TimesTen, including a cache group table, all prepared passthrough statements are invalidated, until reprepared. This error indicates that the application is trying to use an invalidated statement. The application must prepare the passthrough statement after creating a table or cache group. Impact: TimesTen cannot complete the operation. User Action: Reprepare the PASSTHROUGH statement and retry the operation.
8235	Number of WITH ID keys values does not match the primary key columns for cache group cache_group_name	Type of Message: Error Cause: The number of values you specified in the WITH ID clause does not match the number of primary key columns defined on the root table of the cache group. Impact: TimesTen cannot complete the operation. User Action: Ensure that the number of values in the WITH ID clause matches the number of primary key columns defined on the root table of the cache group.
8236	Invalid commit value	Type of Message: Error Cause: You set the commit interval of a LOAD CACHE GROUP or MERGE statement on a cache group to an invalid value. Impact: TimesTen cannot complete the operation. User Action: Reset the commit interval for a LOAD CACHE GROUP or MERGE statement on a cache group to a positive integer value.
8237	Cache group WHERE clauses must be less than number bytes long	Type of Message: Error Cause: Your WHERE clause exceeds the maximum byte length allowed. Impact: TimesTen cannot complete the operation. User Action: Ensure that each WHERE clause of a cache group does not exceed the maximum byte length specified in the error message.
8238	Cannot truncate cache group table table_name; please use DROP/REFRESH/UNLOAD CACHE GROUP instead	Type of Message: Error Cause: You attempted to use a TRUNCATE statement on a cache group table. This operation is not allowed. Impact: TimesTen cannot complete the operation. User Action: Use the DROP, REFRESH, or UNLOAD CACHE statement.
8239	PROPAGATE syntax can only be used once in statement	Type of Message: Error Cause: This is a syntax error for the CREATE CACHE GROUP statement. You specified a PROPAGATE or NOT PROPAGATE clause on a cache table that already has been specified as either PROPAGATE or NOT PROPAGATE. Impact: TimesTen cannot complete the operation. User Action: Check the syntax and remove the redundant or contradictory PROPAGATE or NOT PROPAGATE clause.
8240	READONLY syntax can only be used once in statement	Type of Message: Error Cause: This is a syntax error for the CREATE CACHE GROUP statement. You specified the READONLY keyword twice for the same cached table. Impact: TimesTen cannot complete the operation. User Action: Remove one of the instances of READONLY.
8242	Index on column_name column not supported	Type of Message: Error Cause: You attempted to create an index on column column_name. This operation is not allowed as it is a system-created column. Impact: TimesTen cannot complete the operation. User Action: Do not attempt to create an index on system-created columns.
8243	Invalid autorefresh interval value	Type of Message: Error Cause: You specified an invalid AUTOREFRESH INTERVAL. Impact: TimesTen cannot complete the operation. User Action: Specify a positive integer for AUTOREFRESH INTERVAL.
8244	Cannot alter autorefresh status of a cache group which was not initially created with autorefresh	Type of Message: Error Cause: You attempted to alter the autorefresh status of a cache group that was created without an AUTOREFRESH clause. To alter a cache group's AUTOREFRESH setting, it must be created with the AUTOREFRESH clause. Impact: TimesTen cannot complete the operation. User Action: Ensure that you are executing the ALTER statement on an autorefresh cache group.
8247	The ttCacheSqlGet built-in procedure requires that the cache group was initially created with AUTOREFRESH	Type of Message: Error Cause: You attempted to call the ttCacheSqlGet built-in procedure on a cache group that was created without an AUTOREFRESH clause. Impact: TimesTen cannot complete the operation. User Action: Ensure that you are calling the built-in procedure passing as argument an Autorefresh cache group.
8248	Cache group cache_group_name is not currently being autorefreshed	Type of Message: Error Cause: This error indicates that either the AUTOREFRESH state is off or AUTOREFRESH has been stopped because of a fatal error during refresh. Impact: TimesTen cannot complete the operation. User Action: Check user error log to find the cause for the refresh failure.
8249	cache agent is shutting down autorefresh for cache group cache_group_name. Please try again	Type of Message: Error Cause: When AUTOREFRESH is deactivated either by dropping the cache group or by altering the state to off, the TimesTen cache agent takes some time before the AUTOREFRESH is completely shutdown. An application may not be able to reactivate (create the same cache group or alter the state to ON/PAUSE) that cache group while it is being shut down. Impact: TimesTen cannot complete the operation. User Action: Wait for AUTOREFRESH to shut down completely before reactivating it.
8252	Table table_name is both read only and not propagated	Type of Message: Error Cause: You attempted to create a READONLY cache group that contains a table that is specified as NOT PROPAGATE. The cache group table, table_name, cannot be specified as both READONLY and NOT PROPAGATE. Impact: TimesTen cannot complete the operation. User Action: If you are creating a READONLY cache group, ensure that the cache tables are not specified as NOT PROPAGATE.
8253	Table table_name cannot have same name as an existing cache group or the cache group containing this table.	Type of Message: Error Cause: You attempted to create a cache group or a table that has the same name as another table or cache group. Cache groups and tables cannot have the same name. Impact: TimesTen cannot complete the operation. User Action: Use a different name in the CREATE CACHE GROUP/TABLE statement.
8254	Flush fails; all tables are either propagated or read only	Type of Message: Error Cause: You used FLUSH CACHE GROUP on a cache group that has all of its tables configured with PROPAGATE or READONLY, and are not flushable. Impact: TimesTen cannot complete the operation. User Action: Flush a table that is marked PROPAGATE by using the ttCachePropagateFlagSet built-in procedure.
8255	Attempt to bi-directionally propagate multiple copies of cache group cache_group_name	Type of Message: Error Cause: You can create any number of cache groups that are bi-directionally propagated as long as the names of the cache groups are different and no bi-directionally propagated table appears in more than one cache group. TimesTen Cache has this restriction to avoid update conflict anomalies. In very rare instances, TimesTen Cache falsely reports this error. The cause is most likely that there are some residual Oracle database objects that were created by the TimesTen Cache, but were not dropped when the cache group was dropped or the cache agent was shutdown. For more information on the Oracle database objects created by TimesTen Cache, see Managing a Cache Environment with Oracle Database Objects in Oracle TimesTen In-Memory Database Cache Guide. Impact: TimesTen cannot complete the operation. User Action: Choose a different name for one of the cache group.
8256	Subquery used in CREATE CACHE GROUP statement WHERE clause	Type of Message: Error Cause: You attempted to use subqueries in the WHERE clause of the CREATE CACHE GROUP statement. This operation is not allowed. Impact: TimesTen cannot complete the operation. User Action: Remove the subquery. For more information, see Using a WHERE Clause in Oracle TimesTen In-Memory Database Cache Guide.
8257	Parameters are not supported in Oracle WHERE clauses	Type of Message: Error Cause: You attempted to use a parameter binding ("?") in the WHERE clause of LOAD CACHE GROUP and MERGE statements. This operation is not allowed. Impact: TimesTen cannot complete the operation. User Action: Use SQL literals instead. For more information, see Using a WHERE Clause in Oracle TimesTen In-Memory Database Cache Guide.
8259	Where clause does not match	Type of Message: Error Cause: You specified different WHERE clauses in cache group definitions for replicating cache groups. The WHERE clauses must be identical. Impact: TimesTen cannot complete the operation. User Action: Stop replication, delete the replication definitions and drop the cache groups, then recreate the cache group definitions with the same WHERE clauses. After that, recreate replication definitions and restart replication. For more information, see Cache Groups and Replication in Oracle TimesTen In-Memory Database Replication Guide.
8260	Join predicate does not match	Type of Message: Error Cause: The root/child tables in one cache group are not joined in the same manner as the root/child tables in that cache group's replicated counterpart. You must specify identical JOIN predicates in the cache group definitions for replicating cache groups. Impact: TimesTen cannot complete the operation. User Action: Stop replication, delete the replication definitions and drop the cache groups, then recreate the cache group definitions. After that, recreate replication definitions and restart replication. See Cache Groups and Replication in Oracle TimesTen In-Memory Database Replication Guide.
8261	Cache groups operations may not be performed while XA transactions are active	Type of Message: Error Cause: There is an active XA transaction. No cache operations are allowed when there is an XA transaction accessing the database. Impact: TimesTen cannot complete the operation. User Action: Do not use these two TimesTen features at the same time. The XA and JTA APIs described in the TimesTen developer guides are not supported in cache groups. See Summary of Compatibility Issues in Oracle TimesTen In-Memory Database Cache Guide.
8262	A READONLY or WRITETHROUGH cache group can only replicate to a cache group of the same type	Type of Message: Error Cause: You attempted to replicate a read-only or writethrough cache group to a database with another type of cache group. Impact: TimesTen cannot complete the operation. User Action: When replicating between cache groups, specify only one cache group as AUTOREFRESH. In addition, the other cache groups must be marked READONLY. For more information, see Cache Groups and Replication in Oracle TimesTen In-Memory Database Replication Guide.
8263	If a replicating cache group has AUTOREFRESH specified than the remote cache group must also specify AUTOREFRESH	Type of Message: Error Cause: You did not specify AUTOREFRESH for one of the replicating cache groups. Impact: TimesTen cannot complete the operation. User Action: Ensure that both replicated cache groups have AUTOREFRESH set, though the subscriber must have the AUTOREFRESH STATE OFF. See Cache Groups and Replication in Oracle TimesTen In-Memory Database Replication Guide.
8264	Transaction commit/rollback succeeded on Oracle but failed on TimesTen	Type of Message: Error Cause: If a commit or rollback succeeds on the Oracle database but fails on TimesTen, the data in the TimesTen cache group may no longer be synchronized with the data in the Oracle database. Impact: Updates were successfully propagated to the Oracle database but failed on TimesTen. User Action: After clearing up the cause of the TimesTen failure, it may be necessary to re-apply the failing transaction in TimesTen. For more information about propagation, see PROPAGATE Cache Table Attribute in Oracle TimesTen In-Memory Database Cache Guide.
8265	To use AUTOREFRESH, all the tables in the cache group must be READONLY or all the tables in the cache group must be PROPAGATE	Type of Message: Error Cause: You cannot specify AUTOREFRESH with propagation disabled (NOT PROPAGATE). A cache group that is using AUTOREFRESH must be marked either PROPAGATE or READONLY. By default, cache tables are marked NOT PROPAGATE. Impact: TimesTen cannot complete the operation. User Action: If the cache group is not READONLY, you must explicitly mark each table either PROPAGATE or READONLY. This is to avoid overwriting changes during the next C operation. For more information about propagation, see PROPAGATE Cache Table Attribute in Oracle TimesTen In-Memory Database Cache Guide. For more information about AUTOREFRESH cache groups, see Automatically Refreshing a Cache Group in the Oracle TimesTen In-Memory Database Cache Guide.
8268	Asynchronous or Synchronous Writethrough cache group cannot have a WHERE clause	Type of Message: Error Cause: The CREATE SYNCHRONOUS WRITETHROUGH CACHE GROUP statement or the CREATE ASYNCHRONOUS WRITETHROUGH CACHE GROUP specifies a WHERE clause on at least one of its tables, which is not allowed. This is a compile time error message. Impact: TimesTen cannot complete the operation. User Action: Ensure that Asynchronous or Synchronous Writethrough cache groups do not have a WHERE clause. See Cache Group Types in Oracle TimesTen In-Memory Database Cache Guide for a description of asynchronous writethrough cache groups and synchronous writethrough cache groups.
8270	Table level READONLY/NOT PROPAGATE/PROPAGATE flags are not allowed in a system managed cache group	Type of Message: Error Cause: The table-level READONLY and PROPAGATE attributes cannot be used in system-managed cache groups. This is a compile time error. Impact: TimesTen cannot complete the operation. User Action: Do not use table-level READONLY and PROPAGATE attributes in system-managed cache groups. See Cache Group Types in Oracle TimesTen In-Memory Database Cache Guide.
8271	Manual FLUSH operations are not allowed on cache group cache_group_name because it is system managed	Type of Message: Error Cause: You attempted to perform a manual FLUSH operation that is not allowed on system-managed cache groups. This is a runtime error. Impact: TimesTen cannot complete the operation. User Action: Do not use LOAD CACHE GROUP, UNLOAD CACHE GROUP, MERGE, and FLUSH CACHE GROUP statements on system-managed cache groups. See Cache Group Types in Oracle TimesTen In-Memory Database Cache Guide.
8273	The cache group on the subscriber must have autorefresh STATE set to OFF or PAUSED	Type of Message: Error Cause: You attempted to replicate to a cache group, but the AUTOREFRESH state of the cache group was not set to OFF. Impact: TimesTen cannot complete the operation. User Action: Set the AUTOREFRESH state of the cache group to OFF and retry the operation.
8274	If a replicating cache group has PROPAGATE then the remote cache group must set autorefresh STATE to OFF	Type of Message: Error Cause: When replicating from a user managed cache group that is specified as both AUTOREFRESH and PROPAGATE to another cache group that is specified with AUTOREFRESH only, the second cache group must have the AUTOREFRESH STATE set to OFF. Impact: TimesTen cannot complete the operation. User Action: To enable replication, you must first set ALTER CACHE GROUP and set AUTOREFRESH STATE OFF on the cache group that currently has AUTOREFRESH set to ON or PAUSED. See Cache Groups and Replication in Oracle TimesTen In-Memory Database Replication Guide.
8275	Manual FLUSH operations are not allowed on cache group cache_group_name because it uses AUTOREFRESH	Type of Message: Error Cause: You attempted to perform a manual FLUSH operation, but it failed because the cache group is specified with AUTOREFRESH. This operation is not allowed. Impact: The current operation failed. User Action: Do not use LOAD CACHE GROUP, UNLOAD CACHE GROUP or FLUSH CACHE GROUP statement on cache groups that use AUTOREFRESH.
8277	If a cache group on the receiver has AUTOREFRESH specified then the corresponding cache group on the transmitter must also specify AUTOREFRESH	Type of Message: Error Cause: You attempted replicate to a subscriber cache group, but the corresponding cache group does not have AUTOREFRESH specified. Impact: TimesTen cannot complete the operation. User Action: When replicating to a subscriber cache group with AUTOREFRESH STATE OFF, the master cache group must specify the AUTOREFRESH attribute with either the STATE ON or OFF. See Cache Groups and Replication in Oracle TimesTen In-Memory Database Replication Guide.
8278	Cache groups with AUTOREFRESH and PROPAGATE can only be replicated if both the transmitter and receiver cache groups have autorefresh STATE set to OFF	Type of Message: Error Cause: You attempted to replicate a cache group that does not have AUTOREFRESH STATE OFF. Impact: TimesTen cannot complete the operation. User Action: Ensure that the subscriber cache group has AUTOREFRESH STATE OFF. See Cache Groups and Replication in Oracle TimesTen In-Memory Database Replication Guide.
8279	If a transmitting cache group has AUTOREFRESH and the receiving cache group has PROPAGATE then transmitting cache group must also have PROPAGATE	Type of Message: Error Cause: You attempted to replicate from a cache group with AUTOREFRESH specified, but PROPAGATE not specified to a cache group with PROPAGATE specified. Impact: TimesTen cannot complete the operation. User Action: For details on how to replicate cache groups, Replicating Cache Tables in TimesTen Classic in Oracle TimesTen In-Memory Database Cache Guide and Cache Groups and Replication in the Oracle TimesTen In-Memory Database Replication Guide.
8287	Manual LOAD/REFRESH operations with WHERE or WITHID clauses are not allowed on cache group cache_group_name because it is specified as AUTOREFRESH	Type of Message: Error Cause: You attempted to perform a LOAD or REFRESH cache group operation with WHERE or WITH ID clauses on an autorefresh cache group. Impact: TimesTen cannot complete the operation. User Action: Ensure that a LOAD or REFRESH operation does not have a WHERE clause or WITH ID clause for an autorefresh cache group.
8288	Manual LOAD of cache group cache_group_name is not allowed because it is specified as AUTOREFRESH and it is not empty	Type of Message: Error Cause: This error is issued during a LOAD CACHE GROUP operation on an AUTOREFRESH cache group. A LOAD CACHE GROUP operation cannot be performed on a non-empty AUTOREFRESH cache group. Impact: TimesTen cannot complete the operation. User Action: Use a REFRESH cache group.
8289	Manual LOAD/REFRESH of cache group requires AUTOREFRESH STATE to be PAUSED, but the STATE of cache_group_name is state. The LOAD is not allowed	Type of Message: Error Cause: This error is issued during a LOAD or REFRESH CACHE GROUP operation on an AUTOREFRESH cache group. Impact: TimesTen cannot complete the operation. User Action: Set AUTOREFRESH STATE to PAUSED when issuing LOAD or REFRESH cache group statements.
8290	Manual LOAD/REFRESH must have the COMMIT EVERY N ROWS clause	Type of Message: Error Cause: This error is issued during a LOAD or REFRESH CACHE GROUP operation. Impact: TimesTen cannot complete the operation. User Action: Specify a COMMIT EVERY N ROWS clause in the statement and retry the operation.
8291	Manual LOAD/REFRESH/UNLOAD WITH ID statement cannot have the COMMIT EVERY N ROWS clause	Type of Message: Error Cause: This error is issued during a LOAD or REFRESH CACHE GROUP operation. Impact: TimesTen cannot complete the operation. User Action: Do not specify a COMMIT EVERY N ROWS clause when a WHERE or WITH ID clause is used.
8292	The cache group where clause contains a subquery. Changes of the subquery result may not be tracked by INCREMENTAL AUTOREFRESH	Type of Message: Error Cause: An autorefresh cache group has a subquery in the WHERE clause. Incremental AUTOREFRESH does not track any changes of the subquery result list. Impact: TimesTen Cache may not cache the result rows as specified by the cache group WHERE clause. User Action: Verify that the cache group you are creating does not contain a WHERE clause.
8293	Autorefresh interval should be at least number milliseconds	Type of Message: Error Cause: You specified an invalid AUTOREFRESH interval. Impact: TimesTen cannot complete the operation. User Action: Specify an AUTOREFRESH interval of at least num milliseconds. Currently the minimum number of milliseconds allowed for the AUTOREFRESH interval is 10.
8294	Replication not allowed from a non-cache group table to a READONLY cache group table	Type of Message: Error Cause: You attempted to replication operation that is not allowed. Impact: TimesTen cannot complete the operation. User Action: Do not replicate from a non-cache group table to a table in a READONLY cache group.
8295	To use NCHAR/NVARCHAR values through Cache Connect, Oracle database national character set must be AL16UTF16	Type of Message: Error Cause: To use NCHAR/NVARCHAR2 types in a a cache group table column or a passthrough statement, the Oracle database national character set must be AL16UTF16. Impact: TimesTen cannot complete the operation. User Action: You can use SQL*Plus to connect to the Oracle database and issue the following query to check the database national character set: SELECT VALUE FROM v$nls_parameters WHERE PARAMETER = 'NLS_NCHAR_ CHARACTERSET';
8296	TimesTen and Oracle database character sets do not match. TimesTen: character_set, Oracle: character_set	Type of Message: Error Cause: You specified a character set for the TimesTen database that does not match the one from the Oracle database. Impact: TimesTen cannot complete the operation. User Action: Ensure that TimesTen databases that use cache groups or that provide passthrough have the same database character set as the Oracle database. The DatabaseCharacterSet of the database cannot be changed after its creation.
8297	The session parameter <parameter_name> cannot be altered through a PassThrough statement	Type of Message: Error Cause: TimesTen does not support the execution of the statement using PASSTHROUGH. Impact: TimesTen cannot complete the operation. User Action: Consider executing the transaction requiring these session settings using a connection to the Oracle Database.
8298	Table in autorefresh cache group cannot have more than number columns	Type of Message: Error Cause: Your table in autorefresh cache group exceeds the number of columns allowed. Impact: TimesTen cannot complete the operation. User Action: The maximum number of columns in an autorefresh cache group table is 999. Generally TimesTen supports tables that contain up to 1000 columns.
8299	Cache Connect database character set cannot be TimesTen8	Type of Message: Error Cause: You specified the TIMESTEN8 database character set for databases that are used with cache groups. This operation is not allowed. Impact: TimesTen cannot complete the operation. User Action: Do not specify the TIMESTEN8 database character set for databases that are used with cache groups.
8302	Autorefresh state of cache group cache_group_name is off	Type of Message: Error Cause: You attempted to perform AUTOREFRESH operations on cache groups that have AUTOREFRESH state set to OFF. Impact: TimesTen cannot complete the operation. User Action: To perform AUTOREFRESH operations, set the state to ON.
8303	Sequence number must be non-negative and end sequence must be greater than or equal to start sequence	Type of Message: Error Cause: You specified an invalid sequence number. Impact: TimesTen cannot complete the operation. User Action: Ensure that the sequence number is positive and greater than or equal to the first number in the sequence.
8304	Manual REFRESH operation with WHERE clause is not allowed on cache group cache_group_name because it is specified as dynamic AUTOREFRESH	Type of Message: Error Cause: Refresh operations are automated on the dynamic autorefresh cache group. You attempted to perform a manual refresh operation. This operation is not supported. Impact: TimesTen cannot complete the operation. User Action: Do not perform manual refresh operations with WHERE clause on cache groups that have AUTOREFRESH specified as dynamic.
8305	Manual LOAD/REFRESH on cache group failed because dynamic counter update failed.	Type of Message: Error Cause: This error can occur when another operation is holding a lock on the row for this cache group in the SYS.CACHE_GROUP table. Impact: The manual load or refresh of a dynamic cache group failed because of the failure in updating the internal dynamic counter. User Action: Retry the operation.
8306	A cache group cannot be created as dynamic if it is defined as autorefresh and propagate	Type of Message: Error Cause: You attempted to create a cache group as dynamic, but it was defined as AUTOREFRESH and PROPAGATE. Impact: TimesTen cannot complete the operation. User Action: Ensure that the dynamic user managed cache group does not use both the AUTOREFRESH cache group attribute and the PROPAGATE cache table attribute.
8307	Autorefresh interval cannot exceed 99 days	Type of Message: Error Cause: You specified an invalid AUTOREFRESH interval when creating a cache group. Impact: TimesTen cannot complete the operation. User Action: Create the cache group with an AUTOREFRESH interval that is less than or equal to 99 days.
8308	All replicated autorefresh cache groups should have autorefresh state PAUSED before calling ttRepDeactivate.	Type of Message: Error Cause: This error can occur when you call the ttRepDeactivate built-in procedure. The error is triggered when there are some replicated autorefresh cache groups where state is ON and the cache agent is running. Impact: TimesTen cannot complete the operation. User Action: Alter the replicated autorefresh cache groups on the active node (to be deactivated) to the PAUSED state.
8309	Manual REFRESH with PARALLEL clause is not allowed for dynamic readonly cache groups	Type of Message: Error Cause: You attempted to use the REFRESH CACHE GROUP statement with the PARALLEL clause for a dynamic read-only cache group. This operation is not allowed. Impact: TimesTen cannot complete the operation. User Action: Do not use the REFRESH CACHE GROUP statement with the PARALLEL clause for a dynamic read-only cache group.
8311	To set the number of parallel AWT applier threads, ReplicationParallelism must be set to > 0	Type of Message: Error Cause: You attempted to configure CacheAWTParallelism to be greater than 1, but ReplicationParallelism is 0. Impact: TimesTen cannot complete the operation. User Action: Set ReplicationParallelism to > 0 and retry the operation.
8312	CacheAwtParallelism value of number must be greater than or equal to ReplicationParallelism value of number	Type of Message: Error Cause: You specified an incorrect value for CacheAWTParallelism. Impact: TimesTen cannot complete the operation. User Action: Ensure that the value of CacheAWTParallelism is always greater than or equal to the value of ReplicationParallelism.
8313	Cannot use parallel replication or parallel AWT with SMPOptLevel=0	Type of Message: Error Cause: You attempted to configure Parallel Replication or Parallel AWT for a database with SMPOptLevel set to 0. This operation is not allowed. Impact: TimesTen cannot complete the operation. User Action: Set SMPOptLevel to the default.
8314	ReplicationParallelism cannot be greater than 1 with ReplicationApplyOrdering set to 0	Type of Message: Error Cause: You attempted to set ReplicationParallelism to a value greater than 1, but ReplicationApplyOrdering is set to 0. Impact: TimesTen cannot complete the operation. User Action: Provide a correct value and retry the operation.
8315	Timeout in commit wait for parallel AWT thread	Type of Message: Error Cause: The parallel asynchronous writethrough (AWT) applier thread timed out while waiting for a dependent AWT applier to commit. Impact: The Replication Agent cannot complete the AWT Apply operation. User Action: The Replication Agent will retry the operation automatically.
8316	Creation of AWT cache groups is disabled with ReplicationApplyOrdering set to 1	Type of Message: Error Cause: You attempted to create an asynchronous writethrough cache group (AWT) cache group when ReplicationApplyOrdering is set to 1. This operation is not supported. Impact: TimesTen cannot complete the operation. User Action: To create an asynchronous writethrough cache group, set ReplicationApplyOrdering to 0 or 2.
8318	Dynamic read-only cache groups do not use the Autorefresh Select Every N Rows feature	Type of Message: Warning Cause: You attempted to create a dynamic read-only cache group but the specified interval uses the Autorefresh Select Every N Rows feature. Impact: The cache group is created but it does not use the Autorefresh Select Every N Rows feature. User Action: None.
8319	The Autorefresh Select Every N Rows feature does not allow more than one table per cache group	Type of Message: Error Cause: You attempted to create a cache group that references more than one table and has an interval that uses the Autorefresh Select Every N Rows feature. Impact: The cache group cannot be created. User Action: Ensure that there is only a single table in the cache group or disable the Autorefresh Select Every N Rows feature for the specified interval.
8320	The Autorefresh Select Every N Rows feature does not allow more than one static read-only cache group per interval	Type of Message: Error Cause: You attempted to create a second cache group in an interval that uses the Autorefresh Select Every N Rows feature. Impact: The cache group cannot be created. User Action: Ensure that there is no other cache group in the same interval or disable the Autorefresh Select Every N Rows feature for the specified interval.
8321	The Autorefresh Select Every N Rows feature does not allow user managed cache groups	Type of Message: Error Cause: You attempted to create a user managed cache group in an interval that uses the Autorefresh Select Every N Rows feature. Impact: The user managed cache group cannot be created. User Action: Consider using a different type of cache group or disable the Autorefresh Select Every N Rows feature for the specified interval.
8322	To set the batch size for parallel propagation for AWT cache groups (CacheParAwtBatchSize), you must set either ReplicationParallelism or CacheAwtParallelism greater than zero	Type of Message: Error Cause: You attempted to configure the CacheParAWTBatchSize parameter, but parallel propagation is not enabled for the AWT cache groups. Impact: The CacheParAWTBatchSize parameter is not modified. User Action: Enable parallel propagation for AWT cache groups before attempting to configure the CacheParAWTBatchSize parameter. To enable parallel propagation set the ReplicationParallelism or CacheAWTParallelism connection attribute to a value greater than zero. These connection attributes cannot be modified once the database is created. To set these connection attributes, follow these steps: Create a migrate object of your TimesTen database with the ttMigrate -c utility. For more information, see ttMigrate in Oracle TimesTen In-Memory Database Reference. Destroy your database with the ttDestroy utility. For more information, see ttDestroy in the Oracle TimesTen In-Memory Database Reference. Recreate the TimesTen database and set the ReplicationParallelism or CacheAWTParallelism connection attribute to a value greater than zero. For more information, see Managing TimesTen Databases in the Oracle TimesTen In-Memory Database Operations Guide. Restore the migrate object into the new TimesTen database with the ttMigrate -r utility. For more information, see ttMigrate in the Oracle TimesTen In-Memory Database Reference. Retry setting the CacheParAWTBatchSize parameter with the ttDBConfig built-in procedure. For more information, see ttDBConfig in the Oracle TimesTen In-Memory Database Reference.
8323	Autorefresh for interval number will use Select Every number Rows	Type of Message: Informational Cause: TimesTen is starting autorefresh for the specified interval. The specified interval uses the autorefresh select every n rows feature. Impact: The autorefresh thread for the specified interval will select the specified number of rows from the Oracle database change log table. User Action: None.
8324	Creation of AWT cache groups is disabled with ReplicationApplyOrdering set to 2	Type of Message: Error Cause: You attempted to create an asynchronous writethrough (AWT) cache group in a replication scheme using automatic replication with disabled commit ordering (ReplicationApplyOrdering=2). Impact: TimesTen cannot perform the operation. User Action: Set the ReplicationApplyOrdering attribute to 0 or 1 and retry the operation. For more information on AWT cache groups, see Asynchronous WriteThrough (AWT) Cache Group in Oracle TimesTen In-Memory Database Cache Guide. For more information on parallel replication and the ReplicationApplyOrdering attribute, see Configuring Parallel Replication in the Oracle TimesTen In-Memory Database Replication Guide and ReplicationApplyOrdering in the Oracle TimesTen In-Memory Database Reference.
8325	Invalid hybrid cache group: error_details	Type of Message: Error Cause: The hybrid cache group specification is invalid. Impact: TimesTen cannot create the cache group. User Action: Review the accompanying error details to determine the issue. Then, address the issue and retry the statement.
8400	System catalog creation failed: error_message	Type of Message: Error Cause: When a TimesTen database is created, a number of predefined tables and views are defined in the new database. An error occurred in the process of defining these objects. Impact: TimesTen cannot complete the operation. User Action: Review the accompanying error message, make the suggested corrections, and retry the operation.
8500	PL/SQL feature not installed in this TimesTen instance	Type of Message: Error Cause: You attempted to use a PL/SQL feature, but PL/SQL is disabled in the TimesTen instance. Impact: TimesTen cannot perform the operation. User Action: Try one of the following actions: Enable PL/SQL using the ttInstanceModify utility. Then, retry the operation. Reinstall TimesTen and enable PL/SQL at install time. Then, retry the operation. For more information, see TimesTen installations in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.
8501	PL/SQL feature not installed in this TimesTen database	Type of Message: Error Cause: You attempted to use a PL/SQL feature, but PL/SQL is not enable for the TimesTen database. Impact: TimesTen cannot perform the operation. User Action: Try one of the following actions: Specify PL/SQL=0 as a connection attribute. Then, retry the operation. For more information, see PL/SQL Connection Attributes in Oracle TimesTen In-Memory Database PL/SQL Developer's Guide. Reinstall TimesTen and enable PL/SQL at install time. Then, retry the operation. For more information, see TimesTen installations in the Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.
8502	Error error_number initializing PLSQL_MEMORY string	Type of Message: Internal Error Cause: A problem occurred while loading the database into memory. This problem should not have occurred. Impact: The database is not loaded into memory. The application is not connected to the database. User Action: Contact TimesTen Customer Support.
8503	Error_message	Type of Message: Error Cause: The PL/SQL compiler detected an error from the Oracle database while compiling the program block you submitted. Impact: The PL/SQL compiler cannot compile the program block you submitted. User Action: Review the referenced ORA error number from the Oracle database error documentation and correct your application code. In general, diagnosis is the same for PL/SQL in TimesTen and for PL/SQL in the Oracle database, though there are known differences between PL/SQL in these two environments. Then, retry the operation. For more information, see the Oracle Database Error Messages.
8504	PL/SQL object_type object_name created with compilation warnings	Type of Message: Warning Cause: During compilation, one or more PL/SQL units generated compiler warnings. Impact: The compiled PL/SQL unit or units may not work correctly. User Action: Examine the warnings and correct your application. You can use the show errors command of ttIsql utility to view the generated warnings. For more information, see ttIsql in Oracle TimesTen In-Memory Database Reference.
8505	PL/SQL object_type object_name created with compilation errors	Type of Message: Error Cause: You specified a PL/SQL program unit that contains errors. Impact: TimesTen cannot execute the PL/SQL program unit. User Action: Review the application errors by running the show errors command in ttIsql and correct them. Then, retry the operation. For more information about the show errors command, see Showing Errors in ttIsql in Oracle TimesTen In-Memory Database PL/SQL Developer's Guide.
8506	Error_message	Type of Message: Internal Error Cause: The main causes for this error are: An attempted operation, such as COMMIT, ROLLBACK, or other DDL statement, cannot proceed because of a conflict with an existing PL/SQL object. An unexpected error occurred while attempting to manage memory or locks in the PL/SQL memory area. Impact: TimesTen cannot perform the operation. User Action: Contact TimesTen Customer Support.
8507	Error_message	Type of Message: Error Cause: The execution of a PL/SQL program unit encountered an error from the Oracle database. Impact: TimesTen cannot finish executing the PL/SQL program unit. User Action: Review the referenced ORA error number from the Oracle database error documentation and correct your application code. In general, diagnosis is the same for PL/SQL in TimesTen and for PL/SQL in the Oracle database, though there are known differences between PL/SQL in these two environments. Then, retry the operation. For more information, see the Oracle Database Error Messages.
8508	Question mark parameter markers are not allowed in PL/SQL blocks	Type of Message: Error Cause: You provided a question mark as a parameter marker in a PL/SQL program unit. Impact: TimesTen cannot execute the PL/SQL program unit. Parameter marker names beginning with _QMARK_ are reserved for system use. User Action: Specify a valid parameter marker, using the :var notation for bind variables. Then, retry the operation. For more information, see Using bind variables from an application in Oracle TimesTen In-Memory Database PL/SQL Developer's Guide.
8509	PL/SQL execution terminated; PLSQL_TIMEOUT exceeded	Type of Message: Error Cause: A PL/SQL program unit exceeded the maximum time specified in the PLSQL_TIMEOUT attribute. Impact: TimesTen terminated the execution of the PL/SQL program unit. User Action: Examine if the program unit contains loops or never-ending execution. If the PL/SQL program unit is running but needs more time to complete, increase the PLSQL_TIMEOUT attribute value. Then, retry the operation. For more information, see PL/SQL Connection Attributes in Oracle TimesTen In-Memory Database PL/SQL Developer's Guide.
8510	Error loading PL/SQL system package file file_name: error_message	Type of Message: Internal Error Cause: You attempted to create a new TimesTen database. When a TimesTen database is created, a number of predefined PL/SQL packages are defined in the new database. An error occurred during this process. Impact: TimesTen cannot create the database. User Action: Contact TimesTen Customer Support.
8511	PL/SQL can only be enabled during database creation or at first connect	Type of Message: Error Cause: You attempted to enable PL/SQL on an existing database. Impact: TimesTen cannot enable PL/SQL. User Action: Enable PL/SQL at the time you create a database.
8514	Invalid PL/SQL compiler parameter parameter_name	Type of Message: Error Cause: You attempted to pass a parameter that is not persistent. The PL/SQL persistent parameters are PLSQL_OPTIMIZE_LEVEL, PLSQL_CODE_TYPE, PLSQL_DEBUG, PLSQL_WARNINGS, PLSQL_CCFLAGS and NLS_LENGTH_SEMANTICS. Impact: The current operation failed. User Action: Modify your query to use a PL/SQL persistent parameter and retry the operation.
8515	Duplicate setting for PL/SQL compiler parameter parameter_name	Type of Message: Error Cause: You specified a parameter more than once in a statement. You can only specify each parameter once in each statement. Impact: The current operation failed. User Action: Modify your statement to use each parameter only once and retry the operation.
8517	Cannot attach PL/SQL shared memory; PLSQL_MEMORY_ADDRESS not valid or already in use	Type of Message: Error Cause: Either you specified a virtual memory for PLSQL_MEMORY_ADDRESS that is already in use, or a shared memory segment cannot be created. Impact: The current operation failed. User Action: Specify a virtual address that is free in all processes that can connect to the database. Alternatively, check if you have space to create more shared memory segments.
8518	The preceding error occurred during the execution of an internal SQL statement	Type of Message: Error Cause: This is a warning message. Impact: None. User Action: None.
8519	Invalid PLSQL_MEMORY_ADDRESS specified	Type of Message: Error Cause: You specified an invalid value for PLSQL_MEMORY_ADDRESS. For example, 0. Impact: TimesTen cannot perform the operation. User Action: Specify a valid value and retry the operation.
8521	Cannot attach PL/SQL shared memory; virtual memory at PLSQL_MEMORY_ADDRESS already in use by TimesTen	Type of Message: Error Cause: Your application has connected to two different TimesTen databases that have the same PLSQL_MEMORY_ADDRESS value. Impact: TimesTen cannot perform the operation. User Action: Specify a different PLSQL_MEMORY_ADDRESS value for one of the databases. For more information about the PLSQL_MEMORY_ADDRESS, see PLSQL_MEMORY_ADDRESS in Oracle TimesTen In-Memory Database Reference.
8522	PLSQL_MEMORY_SIZE too small	Type of Message: Error Cause: The memory size for PL/SQL is too small. The PL/SQL shared memory minimum size is 2 MB. Impact: The current operation failed. User Action: Ensure that the memory size for PL/SQL is appropriate and retry the operation. For more information about the appropriate PL/SQL memory size for your operating system, see PLSQL_MEMORY_SIZE in Oracle TimesTen In-Memory Database Reference.
8523	No data found	Type of Message: Error Cause: You attempted to execute a SELECT statement inside a PL/SQL block and no rows were found. Impact: The block execution ends. User Action: You can handle the NO_DATA_FOUND exception in your PL/SQL block so that your program completes running. For more information about exceptions, see Understanding Exceptions in Oracle TimesTen In-Memory Database PL/SQL Developer's Guide.
8524	The call statement was converted to this anonymous block [anonymous_block]; executing this anonymous block resulted in the next error on the stack	Type of Message: Error Cause: TimesTen internally converts call statements into anonymous blocks. The execution of the resulting anonymous block returned the next error on the stack. Impact: The PL/SQL compiler cannot compile the program block you submitted. User Action: Review the referenced ORA error number in the Oracle Database documentation and modify your application code accordingly. In general, diagnosis is the same for PL/SQL in TimesTen than for PL/SQL in Oracle Database, though there are known differences between PL/SQL in these two environments. You may want to run the call statement on a previous TimesTen release to get better error information. A change between the current release and a previous release may have affected how PL/SQL executes the call statement. For more information on Oracle Database error message, see the Oracle Database Error Messages.
8525	dbExport and dbImport must be run before upgrading or downgrading when using TimesTen ScaleOut	Type of Message: Error Cause: Database patching on TimesTen 18.1.4.1.0 is required due to catalog changes for password management enhancements and also due to changes in the PL/SQL library. This requirement applies if the TimesTen databases were created on a TimesTen version earlier than 18.1.4.1.0 and patching to a TimesTen version greater than or equal to than 18.1.4.1.0. It also applies if the databases were created on a TimesTen version greater than or equal to 18.1.4.1.0 and then patching to a TimesTen earlier than 18.1.4.1.0. Impact: Upgrade or downgrade cannot be done without running dbExport and dbImport on TimesTen Scaleout. User Action: Run dbExport and dbImport before upgrading or downgrading TimesTen Scaleout.
8526	You cannot use PLSQL=0 when duplicating from a Database with PLSQL=1	Type of Message: Error Cause: You cannot set PLSQL=0 in a ttRepAdmin -duplicate operation on a database which has PLSQL=1 set. Impact: TimesTen failed to perform the operation. User Action: Change the PLSQL attribute to 1 for the target of the ttRepAdmin -duplicate command and resubmit.
8527	Function function_name not found	Type of Message: Error Cause: An invalid function name was specified. Impact: TimesTen cannot perform the operation. User Action: Use a valid function name.
8528	Invalid argument for function specified in PASSWORD_COMPLEXITY_CHECKER function_name	Type of Message: Error Cause: The PASSWORD_COMPLEXITY_CHECKER function does not have the required number or type of arguments. Impact: TimesTen cannot perform the operation. User Action: See CREATE PROFILE in Oracle TimesTen In-Memory Database SQL Reference for the arguments required by the PASSWORD_COMPLEXITY_CHECKER function.
8529	Invalid password complexity checker function function_name	Type of Message: Error Cause: An invalid function name was specified for the PASSWORD_COMPLEXITY_CHECKER function. Impact: TimesTen cannot perform the operation. User Action: Use a valid function name for the PASSWORD_COMPLEXITY_CHECKER function.

Errors 9000-9999

Error number	Error or warning message	Details
9991	Invalidation of database in progress	Type of Message: Error Cause: You attempted to connect an application to a database while it was being invalidated. Impact: The current operation failed. User Action: Wait for the invalidation of the database to complete, and retry the operation.
9992	Daemon reports error error_code (error_message)	Type of Message: Error Cause: The TimesTen daemon encountered a problem when executing an administrative request, such as starting or stopping the cache agent or the replication agent. Impact: The TimesTen daemon failed to execute the request. User Action: Review the accompanying error message to determine the cause of the failure.
9993	Final checkpoint of database from RAM onto disk in progress	Type of Message: Error Cause: The database is being unloaded from RAM and a final checkpoint is in-progress. Impact: Some operations cannot be performed in the database at this moment. For example, destroying or connecting to the database. User Action: Wait for the final checkpoint and database unload to complete, and retry the database operation.
9994	Loading database from disk into RAM in progress	Type of Message: Error Cause: The database is being loaded into RAM. Impact: Some operations cannot be performed in the database at this moment. For example, destroying or connecting to the database. User Action: Wait for the database load to complete, and retry the database operation.
9996	Process recovery in progress: examining health of in-RAM database	Type of Message: Error Cause: The main daemon is performing integrity checks in the database. This occurs when an application process crashes or is killed. It can also happen if a death process cleanup is taking place and a new application with the same process ID tries to connect. Impact: The database cannot be destroyed at this moment. If the application has the same process ID as the previously crashed connection, the current application cannot connect at this moment. User Action: Wait for the daemon to complete the health checks or until the death process cleanup finishes, and retry the database operation.
9998	Cannot perform requested operation because TimesTen service is being quiesced.	Type of Message: Error Cause: You attempted to connect or destroy a database while the TimesTen daemon was shutting down. Impact: TimesTen cannot perform the operation. User Action: Wait for the TimesTen daemon to restart and retry the operation.
9999	Subdaemon exited unexpectedly	Type of Message: Internal Error Cause: An internal error occurred in the TimesTen subdaemon during a connection attempt. Impact: The database is unloaded from memory. User Action: Try reconnecting to the database. If you still receive this error, contact TimesTen Customer Support.

Errors 10000-10999

Error number	Error or warning message	Details
10002	No record of a database located in 'path'	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.
10003	Unexpected database file exists for new database: error_details.	Type of Message: Error Cause: When connecting to a database, checkpoint, or transaction log files exist that are incompatible or should not exist. The description field provides more information. Impact: The operation fails. User Action: You can destroy the existing database and replace it with a new one by specifying Overwrite=1 in your connect string. For example: ttisql -connStr "dsn=myDSN; overwrite=1"
10004	Unable to connect to daemon: error_details	Type of Message: Error Cause: A communication protocol error occurred when a process was initiating communication with the TimesTen daemon. This is most likely due to some process other than a TimesTen daemon running on the TimesTen daemon port. Impact: TimesTen cannot complete the operation. User Action: Use ttStatus to check whether the TimesTen daemon is running, and on which port.
10006	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.
10007	Could not wait for not-in-flux	Type of Message: Error Cause: A flux is a semaphore used to serialize certain operations on a TimesTen database. This message is written to the log when a user process dies while waiting as multiple processes or threads are trying to connect, disconnect, recover, load, or unload the same database at the same time. Impact: The operation fails. User Action: Retry the operation. If the problem persists, contact TimesTen Customer Support.
10008	Database 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.
10009	RAM load ignored due to ramPolicy setting	Type of Message: Error Cause: You attempted to load a database into memory when the RAM policy for the database is not set to manual. Impact: TimesTen cannot perform the operation. User Action: Use the ttAdmin -ramPolicy utility to change the RAM policy of the database to manual and retry the operation. For more information on the ttAdmin utility, see ttAdmin in Oracle TimesTen In-Memory Database Reference.
10010	RAM unload ignored due to ramPolicy setting	Type of Message: Error Cause: You attempted to unload a database from memory when the RAM policy for the database is not set to manual. Impact: TimesTen cannot perform the operation. User Action: Use the ttAdmin -ramPolicy utility to change the RAM policy of the database to manual and retry the operation. For more information on the ttAdmin utility, see ttAdmin in Oracle TimesTen In-Memory Database Reference.
10011	Database is currently not being managed	Type of Message: Error Cause: There are two possible causes for this error message. A process has attempted to unload a database from RAM, but there is no TimesTen subdaemon currently managing the database. You are attempting to perform an operation on a database that is not loaded. The operation you are trying to perform requires authentication and you are not connecting as the instance administrator. Impact: Depending on the cause, the impact is either of the following. You cannot run ttAdmin -ramUnload on a database that is not loaded. Your user information cannot be verified because no subdaemon is connected to the database User Action: Depending on the cause, you should do either of the following. Do not run ttAdmin -ramUnload on a database that is not loaded. For more information, see ttAdmin in Oracle TimesTen In-Memory Database Reference. Connect as the instance administrator or load the database and then connect as another user.
10012	Replication Agent was not started due to repPolicy setting	Type of Message: Error Cause: You attempted 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. Impact: TimesTen cannot perform the operation. User Action: Use ttAdmin -repPolicy to change the replication policy to "manual" to control manually whether the replication agent is active. See Starting and Stopping the Replication Agents in Oracle TimesTen In-Memory Database Replication Guide for details.
10013	Could not start Replication Agent for the requested database	Type of Message: Error Cause: A replication agent failed during its initialization. Impact: TimesTen cannot perform the operation. User Action: Check the user error log for more details.
10014	Could not spawn Replication Agent for the requested database	Type of Message: Error Cause: The TimesTen daemon could not spawn a replication agent. Impact: TimesTen cannot perform the operation. User Action: Ensure that you are not out of memory or process table space.
10015	Could not stop Replication Agent for the requested database. Please check the TimesTen user error log for further information	Type of Message: Error Cause: An attempt to stop the replication agent failed. Impact: TimesTen cannot perform the operation. User Action: Ensure that the database still exists and the replication agent is still running.
10016	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 Oracle TimesTen In-Memory Database Replication Guide for information on setting the replication policy.
10017	OracleNetServiceName not set	Type of Message: Error Cause: An attempt was made to start the cache agent for a database, but the OracleNetServiceName connection string value was not set. Impact: TimesTen cannot perform the operation. User Action: Ensure that the OracleNetServiceName attribute is correctly defined in the DSN.
10018	ORACLE_HOME not set	Type of Message: Error Cause: You attempted to start the cache agent for a database, but ORACLE_HOME was not set in the user environment. Impact: TimesTen cannot perform the operation. User Action: Ensure that the ORACLE_HOME environment variable is set properly. See Environment variables in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide for more information.
10019	ORACLE_HOME path too long	Type of Message: Error Cause: The value of the ORACLE_HOME environment variable is too long. Impact: TimesTen cannot perform the operation. User Action: Ensure that the ORACLE_HOME environment variable is set correctly, and use symbolic links if needed See Environment variables in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.
10020	Could not stop cache agent for the requested database. Please check the TimesTen user error log for further information	Type of Message: Error Cause: You attempted to stop the cache agent, but it failed. Impact: TimesTen cannot perform the operation. User Action: Use ttStatus to ensure that the database still exists and the cache agent is still running.
10021	Cache agent was not stopped due to cache agent policy setting	Type of Message: Error or Warning Cause: An attempt has been made to stop a 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. Impact: None. User Action: Use ttAdmin -cachePolicy to change the cache agent policy to "manual" to manually control whether the cache agent is active. For more information, see Set a Cache Agent Start Policy in TimesTen Classic in Oracle TimesTen In-Memory Database Cache Guide.
10022	Failed to set ORACLE_HOME	Type of Message: Error Cause: The TimesTen daemon was unable to set the ORACLE_HOME environment variable. Impact: TimesTen cannot perform the operation. User Action: Ensure that you are not out of memory. See Environment variables in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide for information on setting ORACLE_HOME.
10023	Failed to set LD_LIBRARY_PATH	Type of Message: Error Cause: The TimesTen daemon was unable to set the LD_LIBRARY_PATH environment variable. Impact: TimesTen cannot perform the operation. User Action: Ensure that you are not out of memory. See Shared library path environment variable in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide for information on setting LD_LIBRARY_PATH.
10024	Could not start cache agent for the requested database	Type of Message: Error Cause: A Cache Agent failed during its initialization. Impact: TimesTen cannot perform the operation. User Action: Check the user error log for more details.
10025	Could not spawn cache agent for the requested database	Type of Message: Error Cause: The TimesTen daemon could not spawn an Cache Agent. Impact: TimesTen cannot perform the operation. User Action: Ensure that you are not out of memory or process table space.
10026	Some cache groups that hold triggers and other objects in Oracle may exist in the database, drop all the cache groups before destroying the database	Type of Message: Error Cause: A ttDestroy operation may not destroy the database if it contains cache groups that hold triggers and other objects on the Oracle database. Impact: TimesTen cannot perform the operation. User Action: Drop the cache groups and attempt the destroy operation again.
10028	Attempted stop of TimesTen daemon while being managed by Clusterware	Type of Message: Error Cause: If a TimesTen installation is managed by Oracle Clusterware and you attempt to gracefully stop the daemon directly using ttDaemonAdmin -stop, the daemon refuses to stop. Impact: TimesTen cannot perform the operation. User Action: You can only stop the daemon if the Cluster agent and the daemon monitor are first stopped with ttCWAdmin -shutdown -hosts localhost.
10031	Could not spawn grid agent for the requested data store	Type of Message: Error Cause: TimesTen daemon failed to spawn a worker process. Host may be out of resources. Impact: The daemon operation failed, possibly to create, backup, restore, or duplicate a database element. User Action: Increase the process limit on the host.
10034	TimesTen Scaleout requires an explicit value for 'Connections' attribute	Type of Message: Error Cause: You attempted to load a TimesTen Scaleout database without explicitly setting a value for the Connections first connection attribute. Impact: TimesTen cannot load the database. User Action: Ensure that you use the ttGridAdmin utility on the active management instance to load a TimesTen Scaleout database. For more information, see Load a Database into Memory (dbLoad) in Oracle TimesTen In-Memory Database Reference.
10035	Grid mode mismatch. Database: grid_mode; Daemon: grid_mode	Type of Message: Error Cause: You attempted to load or connect to a database with a TimesTen daemon that does not match with the checkpoint files of the database. Impact: TimesTen cannot connect to the database. User Action: Ensure that you use the active management instance to load a database in TimesTen Scaleout or a regular instance to load or create a direct connection to a non-distributed database.
10036	Feature not supported in TimesTen Scaleout: feature_name	Type of Message: Error Cause: TimesTen Scaleout does not support the specified feature. Impact: TimesTen Scaleout cannot complete the operation. User Action: None.
10042	Operation not allowed, database is scheduled to be destroyed.	Type of Message: Error Cause: You attempted to perform an operation on a database that is scheduled to be destroyed. Impact: TimesTen cannot perform the operation. User Action: None.
10044	Feature only supported in TimesTen Scaleout: feature_name	Type of Message: Error Cause: The specified feature is only supported by TimesTen Scaleout. Impact: TimesTen cannot complete the operation. User Action: None.
10047	Operation canceled due to TimesTen Scaleout cleanup	Type of Message: Error Cause: A TimesTen Scaleout Cancel request was received. Impact: TimesTen aborted the execution of the operation. User Action: Retry the operation.
10049	Dropping a hash distribution key is not permitted.	Type of Message: Error Cause: You attempted to drop one of the columns that is part of the distribution key columns list of the table. Impact: TimesTen cannot perform the operation. User Action: Drop the table and re-create it without the column you wish to drop.
10051	Grid startup has not finished	Type of Message: Error Cause: You attempted an operation on an instance that is still in its startup process. Impact: TimesTen cannot perform the operation. User Action: Wait for the instance to complete its startup process and retry the operation.
10053	Database is not open for connections	Type of Message: Error Cause: You attempted to connect to a database that is not open for user connections. Impact: TimesTen cannot establish the connection to the database. User Action: Either connect to the database as the instance administrator or open the database for user connections. For more information on how to open a database for user connections, see Open the Database for User Connections in Oracle TimesTen In-Memory Database Scaleout User's Guide.
10054	Feature only supported in TimesTen Scaleout: feature_name	Type of Message: Error Cause: You attempted to use a feature that is only supported by TimesTen Scaleout. Impact: TimesTen cannot perform the operation. User Action: None.
10056	Invalid argument	Type of Message: Error Cause: An error occurred while trying to execute a distribution map operation with corrupt metadata. Impact: TimesTen failed to perform the operation. User Action: Retry the operation after executing the ttGridAdmin dbDistribute -reset command. For more information on the ttGridAdmin dbDistribute command, see Set or Modify the Distribution Scheme of a Database (dbDistribute) in Oracle TimesTen In-Memory Database Reference.
10057	Transaction failed to acquire distribution lock	Type of Message: Error Cause: The transaction failed to acquire the distribution lock. A concurrent distribution operation may be in progress. Impact: TimesTen failed to perform the operation. User Action: Run only one distribution operation at once.
10058	Feature feature_name is only supported in TimesTen Scaleout	Type of Message: Error Cause: You attempted to use a feature that is only supported by TimesTen Scaleout. Impact: TimesTen cannot perform the operation. User Action: None.
10059	Not supported in TimesTen Scaleout	Type of Message: Error Cause: You attempted to use a feature that is not supported by TimesTen Scaleout. Impact: TimesTen cannot perform the operation. User Action: None.
10060	Daemon request failed: error_message	Type of Message: Error Cause: The TimesTen daemon encountered an issue while executing an administrative request. Impact: The TimesTen daemon failed to execute the request. User Action: Review the accompanying error message to determine the cause of the failure.

Errors 11000-11999

Error number	Error or warning message	Details
11000	XA internal error	Type of Message: Error Cause: An unexpected XA-specific internal error has occurred. Impact: TimesTen cannot complete the operation. User Action: Contact TimesTen Customer Support.
11002	XA asynchronous operation error	An asynchronous XA operation was attempted. TimesTen does not support asynchronous XA calls.
11003	XA Resource Manager error	Type of Message: Error Cause: 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. Impact: TimesTen cannot complete the operation. User Action: Check the accompanying error for more details.
11004	XA invalid XID	The XID specified for an XA operation cannot be found in the list of currently active XA transactions.
11005	XA invalid argument	Type of Message: Error Cause: An invalid argument was passed to an XA function. Impact: TimesTen cannot complete the operation. User Action: Refer to the XA specification for a description of the valid arguments supported for each XA function.
11006	XA protocol error	Type of Message: Error Cause: An XA function was called out of sequence. Impact: TimesTen cannot complete the operation. User Action: Refer to the XA specification for a description of the valid function transition states.
11007	XA Resource Manager failure	A TimesTen error has occurred resulting in the invalidation of the database. All applications must reconnect.
11008	XA duplicate XID	The XID specified for a new XA transaction is already associated with another XA transaction.
11009	XA Resource Manager doing work outside a global transaction	A local transaction must be committed before starting work on an XA transaction.
11013	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.
11014	Request ignored due to blocking condition	Type of Message: Error Cause: An XA request was denied to a temporary resource conflict. Impact: TimesTen cannot complete the operation. User Action: Retry the operation.
11016	Transaction has been heuristically rolled back	An XA transaction was rolled back outside the control of a transaction manager.
11017	Transaction has been heuristically committed	An XA transaction was committed outside the control of a transaction manager.
11020	Transaction 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.
11030	Autocommit must be turned off when working on global (XA) transactions	Autocommit is not supported with XA transactions. See Distributed Transaction Processing: XA in Oracle TimesTen In-Memory Database C Developer's Guide.
11031	Invalid combination of local transaction and global (XA) transaction	Use of SQLTransact to commit an XA transaction is not allowed. XA transactions may only be committed through the use of xa_commit. See Distributed Transaction Processing: XA in Oracle TimesTen In-Memory Database C Developer's Guide.
11035	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.
11036	XA transactions may not be started while replication is configured	TimesTen Replication is not supported with XA transactions.
11037	XA transactions may not be started while the cache agent is running	TimesTen Cache is not supported with XA transactions.
11038	XA transaction cannot be reconstructed because begin record (txn_file_number.txn_file_offset) not found	Type of Message: Error Cause: A transaction log record needed to recover an XA transaction could not be found in the existing transaction log files. Impact: TimesTen cannot complete the operation. User Action: Contact TimesTen Customer Support.
11039	XA reconstruct of xcb number/number failed	Type of Message: Error Cause: Recovery of an XA transaction failed due to an Internal error. Impact: TimesTen cannot complete the operation. User Action: Contact TimesTen Customer Support.
11040	DDL statements are not allowed in XA transactions when DDLCommitBehavior is set to 0	Type of Message: Error Cause: XA transactions require explicit commits after DDL statements. Impact: TimesTen cannot complete the operation. User Action: Set the DDLCommitBehavior attribute to 1, if your application uses XA.
11042	Too many checkpoint file holds	Type of Message: Error Cause: Too many backups running on the TimesTen database Impact: The backup operation cannot begin. User Action: Wait until one or more existing backups complete.
11043	Checkpoint file hold not found	Type of Message: Error Cause: Checkpoint file hold GUID not found Impact: A backup failed due to accumulation of too many log files User Action: Resolve network throughput issues or increase backupfailthreshold connection attribute
11044	No usable checkpoint for backup	Type of Message: Error Cause: There are no valid checkpoints to use for backup Impact: A backup failed due to lack of a valid checkpoint file User Action: Take a checkpoint before retrying backup
11045	Can't create symbolic link	Type of Message: Error Cause: The symlink name already exists or permissions disallow creation. Impact: A backup failed due to inability to symlink a checkpoint or log file User Action: Check file permissions and try again
11046	Delaying checkpoint for WAN backup	Type of Message: Error Cause: WAN backup is delaying checkpoints Impact: A checkpoint can't be taken until the backup completes User Action: Wait for WAN backup to complete before requesting checkpoint again

Errors 12000-13999

Error number	Error or warning message	Details
12001	Specified DSN is NULL or of 0-length	The DSN argument is either NULL or an empty string. You must specify a valid DSN name.
12002	User and system odbc.ini file not found	Linux and UNIX only. TimesTen could not locate the user or system odbc.ini file. The search order for locating an odbc.ini file is: The file pointed to by the ODBCINI environment variable, if set $HOME/.odbc.ini The odbc.ini file located in the user's home directory The file pointed to by the SYSODBCINI environment variable, if set /var/TimesTen/instance/ sys.odbc.ini See ODBCINI environment variable in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide for more information.
12003	Cannot open user/system odbc.ini file	Linux and UNIX only. TimesTen could not open either the user or system odbc.ini file.
12004	Syntax error in odbc.ini file	Linux and UNIX only. TimesTen encountered a syntax error while parsing the user or system odbc.ini file.
12005	Environment variable specified in the attribute is not set	Linux and UNIX only. In either the user or system odbc.ini file, you have specified an attribute of the DSN with an environment variable that has not been set.
12006	Invalid attribute name	The specified DSN attribute name is NULL, an empty string or not a valid attribute for a TimesTen data manager DSN. This error is also returned if the user or system odbc.ini file contains an invalid attribute_name=value pair.
12007	The value of the attribute in the ini file is empty. It should not be empty	Linux and UNIX only. TimesTen DSN attributes are defined in the user or system odbc.ini file using a attribute_name=value pair. The value specified is either an empty string or whitespace.
12008	The length of the value-string in the ini file is too long for this attribute	Linux and UNIX only. TimesTen DSN attributes are defined in the user or system odbc.ini file using a attribute_name=value pair. The length of the value specified exceeds the maximum length allowed for the attribute.
12009	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 Linux or UNIX, the DSN is not defined as a user or system DSN in a odbc.ini file.
12010	Specified buffer is NULL or of 0-length	The buffer specified for returning a value is either NULL or the length of the buffer is 0.
12011	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.
12012	malloc() failed	Unable to allocate memory for TimesTen internal data structures.
12013	Specified data store name is NULL or of zero length, or a client DSN was used	The specified database name is either NULL or an empty string. You must specify a valid database name.
12014	Internal error in TimesTen utility library. Could not get current context	Internal error. Contact TimesTen Customer Support.
12015	Internal error in TimesTen utility library. Could not set current context	Internal error. Contact TimesTen Customer Support.
12016	The number of seconds must be > 0	The number of seconds for the RAM Grace Period must be greater than 0 seconds.
12017	Failed to allocate environment handle	A call to the ODBC SQLAllocEnv function failed.
12018	Failed to allocate connection handle	A call to the ODBC SQLAllocConnect function failed.
12019	Failed to locate database files	TimesTen cannot determine the path and names of the database files for the specified database.
12020	Failed to connect to database	A call to the ODBC SQLDriverConnect function failed to connect to the database using the specified connection string.
12021	Failed to disconnect from database	A call to the ODBC SQLDisconnect function failed.
12022	Failed to free connection handle	A call to the ODBC SQLFreeConnect function failed.
12023	Failed to free environment handle	A call to the ODBC SQLFreeEnv function failed.
12024	Database already loaded into RAM and being managed	Type of Message: Error Cause: You attempted to load a database into memory that is already loaded into memory. Impact: TimesTen cannot perform the operation. User Action: None. For more information on the -ramLoad option of the ttAdmin utility, see ttAdmin in Oracle TimesTen In-Memory Database Reference.
12025	Database already manually unloaded from RAM	Type of Message: Error Cause: You attempted to unload a database from memory that has already been manually unloaded from memory. Impact: TimesTen cannot perform the operation. User Action: None. For more information on the -ramUnload option of the ttAdmin utility, see ttAdmin in Oracle TimesTen In-Memory Database Reference.
12026	The agent is already running for the database	Type of Message: Error Cause: You attempted to start the cache agent or replication agent for the database when the agent is already running. Impact: TimesTen cannot perform the operation. User Action: None. For more information on the -cacheStart or -repStart option of the ttAdmin utility, see ttAdmin in Oracle TimesTen In-Memory Database Reference. For more information on the ttCacheStart built-in procedure, see ttCacheStart in Oracle TimesTen In-Memory Database Reference. For information on the ttRepStart built-in procedure, see ttRepStart in Oracle TimesTen In-Memory Database Reference.
12027	The agent is already stopped for the database	Type of Message: Error Cause: You attempted to stop the cache agent or replication agent for the database when the agent is not running. Impact: TimesTen cannot perform the operation. User Action: None. For more information on the -cacheStop or -repStop option of the ttAdmin utility, see ttAdmin in Oracle TimesTen In-Memory Database Reference. For more information on the ttCacheStop built-in procedure, see ttCacheStop in Oracle TimesTen In-Memory Database Reference. For more information on the ttRepStop built-in procedure, see ttRepStop in Oracle TimesTen In-Memory Database Reference.
12028	No record of a database in the location specified by the DataStore attribute of the DSN. Specified DSN may be a temporary database	The database does not exist in the location specified by the DataStore attribute of the DSN.
12030	Database is in use	Type of Message: Error Cause: You attempted to unload a database from memory that is in use or has an active connection. Impact: TimesTen cannot perform the operation. User Action: To unload the database from memory, you must close all active connections to the database and set the RAM policy of the database to manual or inUse. For more information, see Unloading a Database From Memory for TimesTen Classic in Oracle TimesTen In-Memory Database Operations Guide.
12032	Invalid RamPolicy specified	The valid RAM Policy values are: TT_RAMPOL_MANUAL TT_RAMPOL_ALWAYS TT_RAMPOL_INUSE
12034	RamPolicy cannot be set for temporary databases	Type of Message: Error Cause: You attempted to set a RAM policy for a temporary database. Impact: TimesTen cannot perform the operation. RAM policy can only be set for permanent databases. User Action: Ensure that the Temporary attribute is set to 0 and retry the operation. For more information on the Temporary attribute, see Temporary in Oracle TimesTen In-Memory Database Reference.
12035	Could not initialize winsock	Windows only. A call to WSAStartup failed.
12036	No winsock.dll (that supports version 1.1) found	Windows only. A call to WSAStartup could not locate a winsock.dll that supports version 1.1.
12037	Could not terminate winsock	Windows only. A call to WSACleanup failed.
12038	Could not connect to TimesTen daemon on remote host host_name	Ensure that the TimesTen daemon is running on the remote host.
12039	Could not get port number of TimesTen replication agent on remote host for the name provided.	Type of Message: Error Cause: The replication agent was not started, or it was just started and has not communicated its port number to the TimesTen daemon. The replication agent could also be having a port conflict or, for ttRepAdmin -duplicate, check the value for the -name parameter could be incorrect Impact: The replication agent cannot establish a connection to continue operations. User Action: Ensure that the replication agent for the specified database is running on the remote host and that port numbers do not collide. For ttRepAdmin -duplicate, check the value for the -name parameter is correct.
12040	Could not connect to TimesTen replication agent on remote host	Internal error. Contact TimesTen Customer Support.
12041	Host not found	TimesTen failed to determine the IP addresses associated with the specified host name in the system's /etc/hosts file. Verify that you have correctly identified the host name, as described in Configuring Network Interfaces When Not Using the ROUTE Clause in Oracle TimesTen In-Memory Database Replication Guide.
12042	Cannot start transaction to perform this operation	Internal error. Contact TimesTen Customer Support.
12043	Unable to create temporary file name	Internal error. Contact TimesTen Customer Support.
12044	Transmission failure sending	TimesTen failed to transmit data to the remote TimesTen replication agent.
12045	Cannot create temporary file	Internal error. Contact TimesTen Customer Support.
12046	Transmission failure receiving	TimesTen failed to receive data from the remote TimesTen replication agent.
12047	Data transmitted corrupt	The type of response received from the remote TimesTen replication agent does not match the expected response type.
12048	Error performing backup at source. More information can be found in the source's message log	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.
12049	Cannot write to temporary file	Internal error. Contact TimesTen Customer Support.
12050	Transaction commit for the swap operation failed	Internal error. Contact TimesTen Customer Support.
12052	Replication scheme name too long	Maximum length is 30 characters.
12053	Replication scheme owner too long	Maximum length is 30 characters.
12054	Internal Error: Cannot determine userid	Internal error. Contact TimesTen Customer Support.
12055	No changes were 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.
12056	Size values of local database must match that of the remote database	The PermSize, TempSize and LogBuffSize attributes of the local database do not match those of the remote database.
12057	Error creating temporary database	Failed to create a local database.
12058	Failed to read replication backup CTN	Failed to read replication backup Commit Ticket Number.
12059	Deadlock/Timeout	Either the operation caused a deadlock or the operation timed out.
12060	Invalid remote host specified	A call to gethostbyname with the specified remote host name failed.
12061	Invalid local host specified	A call to gethostbyname with the specified local host name failed.
12062	Failed to upgrade from unsupported version.	Upgrade from this previous replication schema version is not supported.
12063	Cannot read from temporary file	Internal error. Contact TimesTen Customer Support.
12064	Failed to execute SQL command during update	Internal error. Contact TimesTen Customer Support.
12065	Multiple records of replication schema version	Internal error. Contact TimesTen Customer Support.
12066	Failed to compile command	Internal error. Contact TimesTen Customer Support.
12067	Failed to open cursor	Internal error. Contact TimesTen Customer Support.
12068	Failed to get next row	Internal error. Contact TimesTen Customer Support.
12069	Failed to get format handle of the SQL command	Internal error. Contact TimesTen Customer Support.
12070	Failed to get column information	Internal error. Contact TimesTen Customer Support.
12071	Failed to get column value	Internal error. Contact TimesTen Customer Support.
12072	Multiple definitions of replication store id for the specified database	Internal error. Contact TimesTen Customer Support.
12073	Cannot determine my own store name	Internal error. Contact TimesTen Customer Support.
12074	Cannot determine my own hostname	Internal error. Contact TimesTen Customer Support.
12075	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.
12076	Replication schema is later than TimesTen utility library	The specified operation is not allowed on replication schemes for new versions of TimesTen.
12077	Hostname is not set on this machine	Internal error. Contact TimesTen Customer Support.
12078	Failed to reset is_local_store	Internal error. Contact TimesTen Customer Support.
12079	Failed to set is_local_store	Internal error. Contact TimesTen Customer Support.
12080	No subscriber found to swap with	Internal error. Contact TimesTen Customer Support.
12081	Unsupported column type in upgrade	Internal error. Contact TimesTen Customer Support.
12082	Failed to reset subscriber CTN	TimesTen failed to reset receiver Commit Ticket Number.
12083	Found no source store ID in TTREP.REPLICATIONS	Internal error. Contact TimesTen Customer Support.
12084	Call to gethostname() failed	Internal error. Contact TimesTen Customer Support.
12085	No table found for table id	Internal error. Contact TimesTen Customer Support.
12086	Cannot get information on table	Internal error. Contact TimesTen Customer Support.
12087	Cannot get format of table	Internal error. Contact TimesTen Customer Support.
12088	Multiple definitions of source store id	Internal error. Contact TimesTen Customer Support.
12089	Cannot get column information of table	Internal error. Contact TimesTen Customer Support.
12090	Cannot get type mapping for column	Internal error. Contact TimesTen Customer Support.
12091	Cannot determine if version 2 replication tables exist	Internal error. Contact TimesTen Customer Support.
12092	Replication schema is not empty; cannot upgrade	Replication schema must be empty for the upgrade operation.
12093	No count information returned from upgrade's scan of TTREP.TABLES	Internal error. Contact TimesTen Customer Support.
12094	Cannot get count information from TTREP.TABLES	Internal error. Contact TimesTen Customer Support.
12095	Cannot update object id	Internal error. Contact TimesTen Customer Support.
12096	Cannot set object id	Internal error. Contact TimesTen Customer Support.
12097	Cannot get column values from TTREP.PEER	Internal error. Contact TimesTen Customer Support.
12098	Failed to determine current write LSN for TTREP.REPPEERS.SENDLSN	Internal error. Contact TimesTen Customer Support.
12099	Multiple schemes found. Must specify -scheme to identify which replication scheme to use	Multiple replication schemes found.
12100	Cannot create replication table definition	Internal error. Contact TimesTen Customer Support.
12101	Cannot start transaction to check replication schema version	Internal error. Contact TimesTen Customer Support.
12102	Failed to commit transaction for checking replication schema version	Internal error. Contact TimesTen Customer Support.
12103	Cannot get column value from TTREP.REPELEMENTS table	Internal error. Contact TimesTen Customer Support.
12104	Cannot find write LSN	Internal error. Contact TimesTen Customer Support.
12105	Failed to update LSN	Internal error. Contact TimesTen Customer Support.
12106	Cannot set new replication hold LSN	Internal error. Contact TimesTen Customer Support.
12107	Deleting table definition info failed	Internal error. Contact TimesTen Customer Support.
12108	Invalid policy 'policy' specified. Must be policy_list	You did not specify a valid policy value for a built-in procedure used to configure daemon policies. For example, ttCachePolicySet, ttRamPolicySet and ttRepPolicySet. For information about correct policy values, see the description of the particular procedure in the Built-In Procedures chapter in the Oracle TimesTen In-Memory Database Reference.
12109	Syntax error in connection string	There is a syntax error in the specified connection string. Correct the connection string and try connecting again.
12110	Neither DSN= nor DRIVER= attributes are present in the connection string	The connection string must contain either a DSN or DRIVER attribute.
12111	Signal signal_name received	The application received a signal and terminated.
12114	Version mismatch between backed-up files and ttRestore. 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.
12116	Cannot create database for restore	Internal error. Contact TimesTen Customer Support.
12117	Disconnect from newly created database failed	Internal error. Contact TimesTen Customer Support.
12119	Cannot open destination file	Failed to open database file while restoring from stream input.
12120	Insufficient bytes read from input stream	Internal error. Contact TimesTen Customer Support.
12125	Bad database file header read from input stream	Verify that the stream input is valid.
12132	Error forming basename of database	Failed to create a file name from the DataStore attribute of the DSN.
12133	Database file already exists	A database file with the same name as indicated by the DataStore attribute of the DSN already exists.
12134	Log file(s) already exist	Log file(s) with the same name as indicated by the DataStore attribute of the DSN already exists.
12135	Failed to delete database files; OS-detected error: error_details	Internal error. Contact TimesTen Customer Support.
12136	Error while deleting log files	Internal error. Contact TimesTen Customer Support.
12148	Specified connection string is NULL or of 0-length	The connection string argument passed is either NULL or an empty string. You must specify a valid connection string argument.
12150	Cannot start transaction to update subscriber CTN in ttrep.reppeers	Internal error. Contact TimesTen Customer Support.
12151	Failed to commit TimesTen transaction for updating subscriber CTN	Internal error. Contact TimesTen Customer Support.
12152	Cannot set timestamp column for table.	Internal error. Contact TimesTen Customer Support.
12153	Cannot get DS_OBJ_ID value from TTREP.REPELEMENTS	Internal error. Contact TimesTen Customer Support.
12154	Cannot get TBLID value from SYS.TABLES	Internal error. Contact TimesTen Customer Support.
12155	Cannot get row id for row in TTREP.REPELEMENTS	Internal error. Contact TimesTen Customer Support.
12156	Too many tables found on second pass	Internal error. Contact TimesTen Customer Support.
12157	Failed to update the table ID's from the mapping we've created	Internal error. Contact TimesTen Customer Support.
12158	Cannot set replication fields in SYS.TABLES	Internal error. Contact TimesTen Customer Support.
12159	NULL passed for a pointer argument	The pointer argument must be a non-NULL value.
12160	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.
12161	Cannot backup temporary database	Backup is not allowed for temporary databases.
12164	RamGrace cannot be set for temporary databases	ttAdmin -ramGrace can only be set on a permanent database.
12166	Failed to start Backup	The replication agent ran into an error while running the ttBackup utility on the subscriber database or when running ttRepAdmin -duplicate concurrently on more than one database. Run the ttBackup utility on the subscriber with replication disabled, or avoid running two duplicate operations concurrently.
12184	Could not initialize connection to TimesTen daemon.	Internal error. Contact TimesTen Customer Support.
12185	No definitions of replication store id for the specified database. Ensure that the host name of this machine, or the name specified if -localhost was used, matches the host name specified in the replication scheme	Internal error. Contact TimesTen Customer Support.
12186	fstat() system call failed for user/system odbc.ini file	Internal error. Contact TimesTen Customer Support.
12187	read() system call failed for user/system odbc.ini file	Internal error. Contact TimesTen Customer Support.
12188	close() system call failed for user/system odbc.ini file	Internal error. Contact TimesTen Customer Support.
12189	Scan stopped for user/system odbc.ini file	Internal error. Contact TimesTen Customer Support.
12190	Attribute name is too long	Maximum length of attribute names is 30 characters.
12191	Invalid length for connection string	The value specified for the length of the connection string to the SQLDriverConnect ODBC call is less than 0 and not equal to SQL_NTS.
12192	Invalid backup type	An invalid value was passed as the type parameter of the ttBackup utility library function. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12193	No backup directory specified.	A null pointer or empty string was passed as the backupDir parameter of the ttBackup utility library function. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12194	Failed to retrieve database information	Internal error. Contact TimesTen Customer Support.
12195	Basename contains invalid characters	An invalid value was passed as the baseName parameter of the ttBackup utility library function. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12196	Backup status file file_name not found	No backup status file was found for the given backup directory or base name. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12197	Existing backup files do not match database	The backup files indicated by the given backup directory 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 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.
12198	One or more files missing from backup directory	One or more backup files are missing from the backup indicated by the given backup directory or base name. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12199	Cannot read directory contents; OS-detected error: error_details	The contents of the backup directory could not be read due to an operating system error. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12200	Failed to open backup status file: OS-detected error: error_details	The backup status file for the backup indicated by the backup directory or base name could not be opened due to an operating system error. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12201	Failed to read backup status record: OS-detected error: error_details	The backup status file for the backup indicated by the backup directory or base name could not be read due to an operating system error. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12202	Failed to write backup status record: OS-detected error: error_details	The backup status file for the backup indicated by the backup directory or base name could not be written due to an operating system error. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12203	Failed to close backup status file: OS-detected error: error_details	The backup status file for the backup indicated by the backup directory or base name could not be closed due to an operating system error. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12204	Invalid or corrupted backup status file	The backup status file for the backup indicated by the backup directory or base name is invalid or corrupt. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12205	Backup is incomplete	The backup status file for the backup indicated by the backup directory or base name is incomplete. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12206	Backup control information corrupted or incomplete (may indicate TimesTen version mismatch)	The backup status information for the backup indicated by the backup directory or base name is corrupted or incomplete. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12207	Failed to write backup status record; OS-detected error: error_details	Backup status information for the backup indicated by the given backup directory or base name could not be written due to an operating system error. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12208	Failed to retrieve file information; OS-detected error: error_details	An attempt to retrieve information about one or more of the backup files indicated by the backup directory or base name failed due to an operating system error. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12209	Failed to open file file_name; OS-detected error: error_details	One or more of the backup files indicated by the backup directory or base name could not be opened due to an operating system error. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12210	Failed to read backup file; OS-detected error: error_details	One or more of the backup files indicated by the backup directory or base name could not be read due to an operating system error. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12211	Backup file is shorter than expected	One or more of the backup files indicated by the given backup directory or base name have been truncated. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12212	Failed to write backup file; OS-detected error: error_details	One or more of the backup files indicated by the backup directory or base name could not be written due to an operating system error. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12213	Failed to close backup file; OS-detected error: error_details	One or more of the backup files indicated by the backup directory or base name could not be closed due to an operating system error. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12214	Failed to rename backup file; OS-detected error: error_details	One or more of the backup files indicated by the backup directory or base name could not be renamed due to an operating system error. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12215	Backup terminated because database connection invalidated	The requested backup operation was terminated because the database connection was terminated. See ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12216	Invalid restore type	An invalid value was passed as the type parameter of the ttRestore utility library function. See ttRestore in Oracle TimesTen In-Memory Database C Developer's Guide.
12217	Cannot restore into a temporary database	A temporary database cannot be the target of a database restore operation. See ttRestore in Oracle TimesTen In-Memory Database C Developer's Guide.
12218	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.
12219	Failed to connect to TimesTen Server. Make sure that it is running. Otherwise refer to server log for further details	A socket connection to the TimesTen server failed. Refer to the daemon/server log for further details.
12220	Failed to send request to TimesTen Server	A socket send call failed. Normally, this is accompanied with a description of the OS error.
12221	Platform mismatch between backed-up files and ttRestore. Backed-up files are platform_name; ttRestore is platform_name	Files can only be restored on the same platform type where they were backed up.
12222	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.
12226	Not implemented in Client/Server mode	Type of Message: Error Cause: Feature is not available in client/server mode. Impact: TimesTen failed to perform the operation. User Action: Connect to the database in direct mode and retry the operation.
12231	Failed to truncate tables	Type of Message: Error Cause: You attempted to truncate a table that does not exist, is part of a replication scheme, or is a cache group object. Impact: TimesTen unsuccessfully completed the duplicate operation. User Action: Destroy the destination database and retry the operation. Ensure that the table you want to truncate exists and is not part of a replication scheme or a cache group object. For more information on the ttRepAdmin utility or how to duplicate a database, see ttRepAdmin in Oracle TimesTen In-Memory Database Reference.
12232	Failed to drop objects	Type of Message: Error Cause: TimesTen cannot drop an object that does not exist, is part of a replication scheme, or is a cache group object. Impact: TimesTen unsuccessfully completed the duplicate operation. User Action: Destroy the destination database and retry the operation. Ensure that the object you want to drop exists and is not part of a replication scheme or a cache group object. For more information on the ttRepAdmin utility or how to duplicate a database, see ttRepAdmin in Oracle TimesTen In-Memory Database Reference.
12233	Failed to truncate table	Specifies the table that had the problem referred to in error 12231.
12234	Failed to drop table	Specifies a table that was referred to in error 12232.
12235	There are identifiers supplied for the drop option which are also quoted for the truncate option.	Type of Message: Error Cause: You specified the same object to be dropped and truncated while running the ttRepAdmin -duplicate utility. Impact: TimesTen cannot perform the operation. User Action: Ensure that any object specified in the ttRepAdmin -duplicate utility is not specified for the -drop option and -truncate option at the same time and retry the operation. For more information on the ttRepAdmin utility, see ttRepAdmin in Oracle TimesTen In-Memory Database Reference.
12236	There are duplicate identifiers specified in the drop option.	Type of Message: Error Cause: You specified the same object to be dropped at least twice while running the ttRepAdmin -duplicate utility. Impact: TimesTen cannot perform the operation. User Action: Only specify the objects that you want to drop once for the -drop option of the ttRepAdmin -duplicate utility. Then retry the operation. For more information on the ttRepAdmin utility, see ttRepAdmin in Oracle TimesTen In-Memory Database Reference.
12237	There are duplicate identifiers specified in the truncate option.	Type of Message: Error Cause: You specified the same object to be truncated at least twice while running the ttRepAdmin -duplicate utility. Impact: TimesTen cannot perform the operation. User Action: Only specify the objects that you want to drop once for the -truncate option of the ttRepAdmin -duplicate utility. Then retry the operation. For more information on the ttRepAdmin utility, see ttRepAdmin in Oracle TimesTen In-Memory Database Reference.
12238	For -truncate or -drop you can specify \"ALL\" or a list of tables, not both.	Type of Message: Error Cause: You specified ALL and one or more objects for the -drop or -truncate option of the ttRepAdmin -duplicate utility. Impact: TimesTen cannot perform the operation. User Action: Ensure that you specify ALL or a list of objects, not both, for the -drop or -truncate option of the ttRepAdmin -duplicate utility and retry the operation. For more information on the ttRepAdmin utility, see ttRepAdmin in Oracle TimesTen In-Memory Database Reference.
12245	No definitions of replication store id for the database database_name on host_name	Arguments passed during database duplication are not consistent with database definitions on the source database.
12246	DSN database_name exceeds the maximum length of number characters	A database name cannot exceed 32 characters.
12247	A sequence cannot be truncated	Occurs when the name of a sequence is supplied to the -truncate option of ttRepAdmin -duplicate or to ttRepDuplicateEx.
12248	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 the inUse policy.
12249	The remoteDaemonPort can only be 0 or between 1024 and 65535	Reset the value of the ttRepAdmin -duplicate -remoteDaemonPort option to a value specified in the error message.
12250	The duplicate verbosity level must be 0, 1, or 2	Acceptable values for the ttRepAdmin -duplicate -verbosity option are 0, 1 or 2.
12251	The duplicate verbosity level must be 0, 1, or 2	Acceptable values for the ttRepAdmin -duplicate -verbosity option are 0, 1 or 2.
12252	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.
12253	The Active Standby Oracle Database is the same as the DR Oracle Database	When the ttRepAdmin -duplicate -initCacheDR option is used, the disaster recovery Oracle database cannot be the same database as the active standby Oracle subscribing database. The check has identified a tt_03_reppeers entry which is from one of the Active Standby master databases to the disaster recovery Oracle database. Reconfigure the data recovery to resolve this conflict.
12254	Remote peer does not support parallel replication.	There is a mismatch in the parallel replication configuration between two databases involved in a replication scheme, where one database is enabled for parallel replication and the other is not.
12255	ACTIVE STANDBY PAIR replication schemes cannot be created when ReplicationApplyOrdering=1	Type of Message: Error Cause: You attempted to create an active standby pair replication scheme while the ReplicationApplyOrdering attribute is set to 1. Impact: TimesTen cannot create the active standby pair replication scheme. User Action: Set the ReplicationApplyOrdering attribute to 0. Then, retry the operation. For more information on the ReplicationApplyOrdering attribute, see ReplicationApplyOrdering in Oracle TimesTen In-Memory Database Reference.
12257	Error creating bookmarks for the parallel tracks.	Internal error. Tried to create entries in TTREP.REPPEERS for 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 the ReplicationParallelism parameter.
12258	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 the ReplicationApplyOrdering attribute is greater than 0.
12259	A database cannot be defined as a PROPAGATOR when parallel mode replication is configured.	Propagator databases are not supported when the database has been created with parallel replication attributes, where the ReplicationApplyOrdering attribute is greater than 0.
12260	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 the ReplicationApplyOrdering attribute is greater than 0.
12261	ALTER TABLE is not permitted on a replicated table when parallel mode replication is configured.	ALTER TABLE is not allowed when the database has been created with parallel replication attributes, where the ReplicationApplyOrdering attribute is greater than 0. This error is raised at application time.
12262	Error setting track for connection.	Internal Error. The replication agent cannot use a specific track for its database connection.
12263	Aging is not permitted on a table when parallel mode replication is configured.	In 11.2.1.6.0, aging on tables was allowed when ReplicationApplyOrdering was set to 1. Currently, aging is disabled when ReplicationApplyOrdering is set to 1. When a database with ReplicationApplyOrdering set to 1 is upgraded from 11.2.1.6.0, aging will be disabled.
12264	ALTER TABLE cannot be replicated to a database with parallel mode replication enabled.	This error occurs if the replication agent detects ALTER TABLE when parallel mode replication is enabled.
12274	Failed to read track entries for peer.	This is an internal error that is returned if the transmitter could not read metadata from ttrep.reppeers. Contact TimesTen Customer Support.
12275	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.
12276	RamPolicyAutoReload value must be 0 or 1.	Type of Message: Error Cause: You specified an incorrect value for the parameter of the ttRamPolicyAutoReloadSet built-in procedure. Impact: TimesTen cannot call the ttRamPolicyAutoReloadSet built-in procedure. User Action: Call the ttRamPolicyAutoReloadSet built-in procedure and pass either 0 or 1 as a parameter. For more information on the ttRamPolicyAutoReloadSet built-in, see ttRamPolicyAutoReloadSet in Oracle TimesTen In-Memory Database Reference.
12277	Required attribute missing	Type of Message: Error Cause: You attempted to create a database or database definition without defining one of the required connection attributes in the odbc.ini file or database definition object. Impact: TimesTen cannot create the database. User Action: Ensure that you assign a value for the DataStore connection attribute and retry the operation. For more information on the DataStore connection attribute, see DataStore in Oracle TimesTen In-Memory Database Reference. For more information on how to modify the values of the connection attributes in a database definition, see Modify the Connection Attributes in a Database Definition in Oracle TimesTen In-Memory Database Scaleout User's Guide.
12278	Failed to acquire epoch latch on file: file_name	Type of Message: Error Cause: Latch contention occurred on the epoch latch due to concurrent epochs. The backup epoch file for the checkpoint could not be written due to the latch contention. Impact: The backup failed to copy the epoch file. User Action: Retry the backup operation. If the problem persists and you find information for this failure in the daemon logs, contact TimesTen Customer Support. For more information, see ttBackup in Oracle TimesTen In-Memory Database C Developer's Guide.
12325	Specified local IP address could not be looked up	Type of Message: Error Cause: The IP address you specified with the ttRepAdmin -duplicate -localIPAddress option cannot be resolved by the target host. Impact: ttRepAdmin -duplicate failed because a connection from the local network interface device to the target host cannot be established. User Action: Ensure that the alias or IP address you specified for the local network interface device is correct. Also, ensure that the local network interface device you specified has access to the target host.
12326	Specified remote IP address could not be looked up	Type of Message: Error Cause: The IP address you specified with the ttRepAdmin -duplicate -remoteIPAddress option cannot be resolved by the target host. Impact: ttRepAdmin -duplicate failed because a connection from the remote network interface device to the target host cannot be established. User Action: Ensure that the alias or IP address you specified for the remote network interface device is correct. Also, ensure that the remote network interface device you specified has access to the target host.
12327	Could not connect to the remote replication agent by binding to the specified local address	Type of Message: Error Cause: The ttRepAdmin utility cannot bind to the local address you specified in order to connect to the remote replication agent. Impact: ttRepAdmin -duplicate failed because the utility cannot bind to the local address you specified. User Action: Ensure that the alias or network address you specified is correct. Also, ensure that the remote replication agent you specified has access to the local network interface device.
12328	Could not fix the subscriber state during duplicate	Type of Message: Error Cause: Duplicate fix-up processing failed while trying to adjust transmission states. Impact: TimesTen did not complete the duplicate operation. User Action: Review associated error messages to determine the cause of the problem.
12329	Error while deleting epoch files	Type of Message: Error Cause: TimesTen failed to delete an epoch file. Impact: TimesTen is unable to restore the database. User Action: Contact TimesTen Customer Support.
12330	Invalid disconnection arguments specified	Type of Message: Error Cause: You attempted a disconnect operation while providing invalid arguments. Impact: TimesTen failed to the perform the operation. User Action: Retry the disconnect operation while providing valid arguments.
12331	Feature not supported on this operating system.	Type of Message: Error Cause: This feature is not supported on this operating system. Impact: TimesTen failed to perform the operation. User Action: See Platforms and Configurations in Oracle TimesTen In-Memory Database Release Notes for a list of the supported platforms or operating systems.
12332	Database already open	Type of Message: Error Cause: You attempted to open a database that is already open. Impact: None. This is an informational message. User Action: None. For more information, see Opening and Closing the Database for User Connections in Oracle TimesTen In-Memory Database Operations Guide.
12333	Database already closed	Type of Message: Error Cause: You attempted to close a database that is already closed. Impact: None. This is an informational message. User Action: None. For more information, see Opening and Closing the Database for User Connections in Oracle TimesTen In-Memory Database Operations Guide.
12334	SSL initialization failed	Type of Message: Error Cause: An error occurred while setting up an SSL connection. Impact: TimesTen is unable to establish SSL communication. User Action: Review any associated error information to determine the cause of the error.
12335	Detaching from the shared memory segment failed	Type of Message: Error Cause: An error occurred during the ttAdmin -shmDetach operation. Impact: The database is still managed by the subdaemon. User Action: Review any associated error information to determine the cause of the error. See ttAdmin in Oracle TimesTen In-Memory Database Reference.
12336	Attaching to the shared memory segment failed	Type of Message: Error Cause: An error occurred during the ttAdmin -shmAttach operation. Impact: The existing shared memory segment for the database is not usable. User Action: Run the ttAdmin -shmFree command and reload the database.
12337	Cannot destroy an unmanaged database.	Type of Message: Error Cause: An error occured during the ttDestroy operation. Impact: TimesTen cannot destroy a database that is not being managed. User Action: Run the ttAdmin -shmFree command and then destroy the database.
12338	Cannot change ram policy of an unmanaged database.	Type of Message: Error Cause: An error occured during the ttAdmin -ramPolicy operation. Impact: TimesTen change the ram policy of a database that is not being managed. User Action: Run the ttAdmin -shmAttach command and then change the ram policy.
12339	Cannot free the shared memory segment.	Type of Message: Error Cause: An error occured during the ttAdmin -shmFree operation. Impact: TimesTen failed to free she shared memory segment. User Action: Make sure the database is unmanaged before trying to free the shared memory segment.
12340	ttXactLog failed to read log cursor.	Type of Message: Error Cause: An error occured reading the transaction log. Impact: ttXactLog could not print the complete transaction log. User Action: Retry the command and make sure the input parameters are correct.
12341	Invalid Checksum Info reference	Type of Message: Error Cause: Internal Issue Impact: Duplicate will fail User Action: Retry the command
12700	NLSRTL environment could not be initialized (Check the value of TIMESTEN_HOME)	The NLS data files could not be located. Check the value of the TIMESTEN_HOME environment variable. The installation directory may have been corrupted or become unreadable.
12701	DatabaseCharacterSet attribute required for database creation. Refer to the TimesTen documentation for information on selecting a character set.	You must specify a value for the DatabaseCharacterSet attribute 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 Oracle TimesTen In-Memory Database Operations Guide.
12702	Unable to load NLS data data from NLS_data_item (check the value of TIMESTEN_HOME)	A particular NLS data file could not be located. Check the value of the TIMESTEN_HOME environment variable. The installation directory may have been corrupted or become unreadable. NLS_data_item could be a character set name or a sort name.
12705	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
12706	Invalid session parameter value	The value supplied for the session parameter is unknown or unsupported by TimesTen. For example: ALTER SESSION SET NLS_SORT='bogus'; returns: 12706: Invalid NLS session parameter value
12707	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.
12708	Conversion of TIMESTEN8 character set data is not allowed	An operation either explicitly or implicitly tried to convert TIMESTEN8 data to another character set. Conversion of TIMESTEN8 character data is undefined and therefore not allowed.
12713	Character data loss in NCHAR/CHAR conversion	NLS_NCHAR_CONV_EXCP was set to TRUE and a conversion was attempted for an NCHAR character having no corresponding mapping in the database character set.
12714	NLSSORT computation failed due to invalid characters in string	The string passed to the NLSSORT function contained invalid characters for the given character set. A meaningful NLSSORT result value could not be computed. Character data containing invalid characters is of dubious usefulness and should be eliminated from the database.
12715	NLS_SORT value must be BINARY when database character set is TIMESTEN8	When the database character set is TIMESTEN8, the only setting allowed for NLS_SORT is BINARY. Non-binary comparison rules for TIMESTEN8 data are undefined.
12716	For the UNISTR SQL function, '\\' must be followed by four hexadecimal characters or another '\\'	The UNISTR function argument allows the back-slash character only as an escape for a hexadecimal Unicode character or itself. For example: UNISTR('\0041') UNISTR('abc\\nop')
12717	Character data loss in character set conversion	Type of Message: Warning Cause: During character set conversion of data, a character was encountered for which no valid conversion exists. Impact: TimesTen substituted a replacement character in its place. User Action: You should change your connection character set to one that is compatible with the database character set in use. For more information, see ConnectionCharacterSet in Oracle TimesTen In-Memory Database Reference.
12718	Error setting default date/timestamp format 'string'	Contact TimesTen Customer Support.
12719	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.

Errors 14000-14999

Error number	Error or warning message	Details
14000	TimesTen daemon internal error: error_details	Internal error. Contact TimesTen Customer Support.
14001	TimesTen daemon out of memory error_details	Type of Message: Error Cause: The TimesTen daemon has run out of swap space. Impact: Unknown. User Action: None.
14002	TimesTen daemon port in use port_number	The TimesTen daemon cannot listen on its specified port because the port is already in use.
14003	TimesTen daemon thread creation failed: error_message	TimesTen daemon thread creation failed.
14004	TimesTen daemon creation failed: error_message	TimesTen daemon could not create database for specified reason.
14005	TimesTen daemon connection failed: error_message	TimesTen daemon could not make new database connection for specified reason.
14006	TimesTen daemon disconnect failed: error_message	TimesTen daemon could not do database disconnect for specified reason.
14007	TimesTen daemon destroy failed: error_message	TimesTen daemon could not destroy the database for specified reason.
14008	TimesTen daemon association table full (number entries)	Too many simultaneous connections have been made.
14009	TimesTen daemon startup failed: error_message	Startup of TimesTen daemon failed for the specified reason.
14010	TimesTen daemon spawn failed: error_message	TimesTen daemon could not spawn a subprocess.
14011	TimesTen daemon operation failed due to invalidation: error_message	Specified operation failed due to a database invalidation.
14012	TimesTen daemon subdaemon failed: error_message	A TimesTen subdaemon failed to perform the requested operation.
14013	TimesTen daemon out of subdaemons: error_message	The TimesTen daemon could not spawn a subdaemon to perform some operation, such as managing a database or rolling back transactions for a terminated process.
14014	TimesTen daemon policy request failed: error_message	A ttAdmin request failed for the specified reason.
14015	User user_name, not instance admin, trying to start TimesTen daemon as setuid root	A user other than the instance administrator attempted to start the main TimesTen daemon.
14016	Daemon could not get membership information from membership service: error_message	Check whether membership service is running and properly configured
14017	Daemon could not add or change information in membership service: error_message	Check whether membership service is running and properly configured
14018	Write to socket connected to TimesTen daemon failed: error_message	Type of Message: Error Cause: An attempt to write to the socket connected to the TimesTen daemon failed. The accompanying message provides further details on the cause of the error. Impact: TimesTen may have failed to complete the operation. User Action: Use the ttStatus utility to check the status of the TimesTen daemon. For more information on the ttStatus utility, see Using the ttStatus utility in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.

Errors 15000-15999

Error number	Error or warning message	Details
15000	Password is incorrect	Incorrect password given.
15002	No such user	Attempt to modify or remove a user which does not exist.
15003	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 -maxusers option specified in the ttendaemon.options file.
15004	User user_name already exists	Type of Message: Error Cause: You attempted to create a user that already exists. Impact: TimesTen cannot perform the operation. User Action: Select a different user name and retry the operation.
15006	Cannot delete the instance administrator or other predefined users	Attempt to remove the instance administrator user.
15007	Access control not enabled	Attempt to perform authorization functions when access control has not been enabled.
15008	User name exceeds limit of 30 characters	Specified user name is too long. Must be 30 characters or less.
15009	Password required for user_name	A PWD or PWDCrypt attribute must be specified for the given user name.
15010	Cannot convert user from 'identified externally' to internal or vice versa	Cannot give a password to a user defined as IDENTIFIED EXTERNALLY, or remove a password for a user defined as an internal TimesTen user.
15011	Password exceeds limit of number characters	Type of Message: Error Cause: You specified a password that exceeds the maximum allowed number of characters. Impact: TimesTen cannot perform the operation. User Action: Select a password that is within the maximum allowed number of characters and retry the operation.
15012	Encrypted password must have exactly number characters	PWDCrypt attribute is not the correct length.
15013	Cannot alter privileges for the instance administrator or other predefined users	Must be logged into administrator account to alter administrator privileges.
15014	Only the instance administrator user can perform this command	Insufficient privileges to execute command restricted to the administrator.
15015	Cannot alter password for predefined users	Type of Message: Error Cause: You cannot alter the password for a user that was created during TimesTen database creation, including the instance administrator. Impact: TimesTen cannot perform the operation. User Action: None.
15016	Unsupported use of an internal system-user account	One of the predefined users ('PUBLIC', 'SYS', 'TTREP') is being used in an unsupported operation.
15017	ADMIN privilege required to alter attribute_name attribute	When Access Control is in use, changing first-connection attributes from their previous values requires the ADMIN privilege.
15018	Password is invalid. Either it is empty, has leading or trailing whitespace characters, or contains carriage-return, newline or semi-colon characters.	Type of Message: Error Cause: You specified a password with one or more of the listed restrictions. Impact: TimesTen cannot perform the operation. User Action: Specify a password that does not contain any of the listed restrictions and retry the operation.
15019	Only the instance admin may alter the attribute_name 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.
15020	UID not specified	The UID was not specified when executing a ttRepAdmin -duplicate operation. The user must provide the UID and rerun the ttRepAdmin -duplicate operation.
15021	PWD or PWDCrypt not specified	The PWD or PWDCrypt were not specified when executing a ttRepAdmin -duplicate operation. The user must provide a password or a value for the PWDCrypt attribute and rerun the ttRepAdmin -duplicate operation.
15022	OraclePwd connection attribute needs to be specified and has to be non-empty for using TimesTen Cache features	Type of Message: Error Cause: The OraclePWD connection attribute is not specified. Impact: Your application cannot use TimesTen Cache features if you do not specify a value for the OraclePWD connection attribute. For more information on TimesTen Cache features, see Methods for Transmitting Changes Between TimesTen and Oracle Databases in Oracle TimesTen In-Memory Database Cache Guide. User Action: Specify the OraclePWD connection attribute for the TimesTen connection. Also, ensure that your OraclePWD is non-empty. For more information on specifying the OraclePWD connection attribute, see OraclePWD in Oracle TimesTen In-Memory Database Reference.
15100	User user_name lacks privilege privilege_name	Type of Message: Error Cause: The specified user does not have the required privileges to perform the operation. Impact: TimesTen cannot perform the operation. User Action: The instance administrator or a user with the ADMIN privilege must GRANT the required privilege to the specified user. For more information on user privileges, see Privileges in Oracle TimesTen In-Memory Database SQL Reference.
15102	Statement compilation failed. During privilege checking for statement, could not allocate number bytes on the compilation heap	Internal error. Contact TimesTen Customer Support.
15103	System-defined users and roles cannot be dropped	Type of Message: Error Cause: You cannot DROP system-defined users and roles. Impact: TimesTen cannot DROP the specified user or role. User Action: None.
15104	Only the instance administrator can destroy a database	Type of Message: Error Cause: You attempted to destroy a database. Impact: You cannot destroy a database while you are connected as the specified user. Only the instance administrator can destroy the database. User Action: Connect as the instance administrator and destroy the database. For more information on the instance administrator, see Instance administrator in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.
15105	User user_name requesting database creation is not the instance administrator. Please verify user id and password. Only the instance administrator can create a database.	Type of Message: Error Cause: You attempted to create a database. Impact: You cannot create a database while you are connected as the specified user. Only the instance administrator can create a database. User Action: Connect as the instance administrator and create the database. For more information on the instance administrator, see Instance administrator in Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide.
15106	Database users cannot invoke internal built-in procedures	You attempted to call a TimesTen built-in procedure that is reserved for internal use only.
15107	User lacks CREATE SESSION privilege; logon denied	Type of Message: Error Cause: You attempted to connect to a database with a user that does not have the CREATE SESSION privilege. Impact: The specified user cannot connect to the database. User Action: The instance administrator or an user with the ADMIN privilege must GRANT the CREATE SESSION privilege to the specified user. For more information on user privileges, see Privileges in Oracle TimesTen In-Memory Database SQL Reference.
15109	The system privilege SYSDBA is not supported. The system privilege ADMIN can be used for most administrative tasks.	Type of Message: Error Cause: SYSDBA is not a valid privilege. Impact: TimesTen cannot GRANT the SYSDBA privilege to the specified user. User Action: Consider granting the ADMIN privilege to the specified user. For more information on the ADMIN privilege, see Administrative Privileges in Oracle TimesTen In-Memory Database Security Guide.
15110	Object_name does not exist	This message displays in cases where the lack of existence should have been caught prior to privilege computation.
15111	Invalid privilege: privilege_name. Roles are not supported.	Type of Message: Error Cause: The privilege you attempted to GRANT does not exist. Impact: TimesTen cannot GRANT the specified privilege. User Action: Check the name or spelling of the privilege and retry the operation. For more information on user privileges, see Privileges in Oracle TimesTen In-Memory Database SQL Reference
15140	GRANT failed: User user_name already has system privilege privilege_name	Type of Message: Error Cause: The specified user already has the system privilege you attempted to GRANT. Impact: TimesTen cannot perform the operation. User Action: Ensure that your SQL statement is correct. If necessary, retry the operation. For more information on system privileges, see System Privileges in Oracle TimesTen In-Memory Database SQL Reference. For more information on granting system privileges, see System Privileges in the Oracle TimesTen In-Memory Database Security Guide.
15141	GRANT failed: User user_name already has object privilege privilege_name on object_name	Type of Message: Error Cause: The specified user already has the object privilege you attempted to GRANT. Impact: TimesTen cannot perform the operation. User Action: Ensure that your SQL statement is correct. If necessary, retry the operation. For more information on object privileges, see Object privileges in Oracle TimesTen In-Memory Database SQL Reference. For more information on granting object privileges, see Privileges for SQL Objects in the Oracle TimesTen In-Memory Database Security Guide.
15142	REVOKE failed: User user_name does not have system privilege privilege_name	Type of Message: Error Cause: The specified user does not have the system privilege you attempted to REVOKE. Impact: TimesTen cannot perform the operation. User Action: Ensure that your SQL statement is correct. If necessary, retry the operation. For more information on system privileges, see System privileges in Oracle TimesTen In-Memory Database SQL Reference. For more information on revoking system privileges, see System Privileges in the Oracle TimesTen In-Memory Database Security Guide.
15143	REVOKE failed: User user_name does not have object privilege privilege_name on object_name	Type of Message: Error Cause: The specified user does not have the object privilege you attempted to REVOKE. Impact: TimesTen cannot perform the operation. User Action: Ensure that your SQL statement is correct. If necessary, retry the operation. For more information on object privileges, see Object privileges in Oracle TimesTen In-Memory Database SQL Reference. For more information on revoking object privileges, see Privileges for SQL Objects in the Oracle TimesTen In-Memory Database Security Guide.
15144	REVOKE failed: Cannot revoke system-generated object privilege privilege_name on object_name from user_name	Type of Message: Error Cause: You attempted to REVOKE an object privilege from PUBLIC that was system-granted during database creation. Impact: TimesTen cannot perform the operation. User Action: You can only REVOKE privileges granted to the PUBLIC role after database creation. For more information on the PUBLIC role, see Overview of the PUBLIC Role in Oracle TimesTen In-Memory Database Security Guide.
15150	Operation_name failed: (internal error) error_message	The specified operation failed for the reason indicated in the error message.
15151	Operation_name failed: User user_name does not exist	Type of Message: Error Cause: The specified user does not exist. Impact: TimesTen cannot perform the operation. User Action: Check the name or spelling of the user and retry the operation.
15152	Operation_name failed: Object object_name does not exist	Type of Message: Error Cause: The specified object does not exist. Impact: TimesTen cannot perform the operation. User Action: Check the name or spelling of the object and retry the operation.
15154	Operation_name failed: Invalid privilege privilege_name for object object_name type object_type	The operation failed because there is a mismatch between the specific privilege and the object.
15155	Operation_name failed: You do not have rights to grant or revoke privilege privilege_name	Type of Message: Error Cause: You do not have the adequate privileges necessary to GRANT or REVOKE the specified privilege. Impact: TimesTen cannot perform the operation. User Action: The instance administrator or an user with the ADMIN privilege must GRANT or REVOKE the specified privilege. For more information on user privileges, see Privileges in Oracle TimesTen In-Memory Database SQL Reference.
15156	Operation_name failed: You do not have rights to grant or revoke privilege privilege_name on object_name	Type of Message: Error Cause: You do not have the rights necessary to GRANT or REVOKE the specified privilege to the specified object. Impact: TimesTen cannot perform the operation. User Action: The instance administrator, an user with the ADMIN privilege, or the owner of the specified object must GRANT or REVOKE the specified privilege. For more information on object privileges, see Privileges Overview in Oracle TimesTen In-Memory Database Security Guide.
15157	Operation_name failed: User user_name is the owner of object_name	Type of Message: Error Cause: You attempted to GRANT or REVOKE privileges for the owner of the specified object. Impact: TimesTen cannot perform the operation. User Action: Ensure that your SQL statement is correct. If necessary, retry the operation. For more information on object privileges, see Privileges for SQL Objects in Oracle TimesTen In-Memory Database Security Guide.
15158	Operation_name failed: Cannot grant or revoke privileges from instance admin user_name	You do not have adequate privileges to grant or revoke privileges to/from the instance administrator.
15159	Operation_name 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.
15160	Operation_name failed: privilege_name on object_name listed more than once in privilege list	You must indicate a privilege only once for a specific object in the SQL statement when attempting to GRANT or REVOKE it.
15161	Operation_name failed: privilege_name is redundant with ALL	You issued a GRANT ALL or REVOKE ALL statement, while attempting to grant or revoke other specific privileges. Adding additional privileges to the GRANT ALL (or REVOKE ALL) statement is redundant. Attempt the operation again and specify either ALL or the specific privileges that you want to GRANT or REVOKE.
15162	Operation_name failed: privilege_name on object_name is redundant with ALL on object_name	Type of Message: Error Cause: You attempted to GRANT ALL or REVOKE ALL privileges for the specified object, while attempting to add additional privileges that make the SQL statement redundant. Impact: TimesTen cannot perform the operation. User Action: Specify either ALL or the specific privileges you want to GRANT or REVOKE, and retry the operation. For more information, see Privileges for SQL Objects in Oracle TimesTen In-Memory Database Security Guide.
15163	Operation_name failed: user_name listed more than once in user list	You must list the user name only once in a SQL statement.
15164	Operation_name failed: Cannot grant or revoke privileges from internal system-user user_name	Type of Message: Error Cause: You attempted to GRANT or REVOKE a privilege to or from an internal TimesTen user. Impact: TimesTen cannot perform the operation. User Action: None.
15165	Invalid system privilege privilege_name	The user specified an invalid privilege in a GRANT or REVOKE statement when a system privilege was expected. For more information about valid system privileges, see System Privileges in Oracle TimesTen In-Memory Database Security Guide.
15166	Invalid object privilege privilege_name	The user specified an invalid privilege in a GRANT or REVOKE statement when an object privilege was expected. For more information about valid system privileges, see System Privileges in Oracle TimesTen In-Memory Database Security Guide.
15167	Cannot drop a user that is currently connected (message)	Type of Message: Error Cause: You attempted to DROP a user that has an active connection to the database. Impact: TimesTen cannot perform the operation. User Action: Disconnect the specified user from the database and retry the operation. Use the utility ttXactAdmin -connections to identify the process associated to the specified user. For more information on the ttXactAdmin utility, see ttXactAdmin in Oracle TimesTen In-Memory Database Reference.
15168	Cannot drop a user that owns database objects (object_type object_name)	Type of Message: Error Cause: You attempted to DROP a user that owns one or more objects in the database. Impact: TimesTen cannot perform the operation. User Action: DROP all objects owned by the user and retry the operation. For more information on dropping a SQL object, see the respective sections in the Oracle TimesTen In-Memory Database SQL Reference.
15169	IDENTIFIED BY must be specified for CREATE USER	Type of Message: Error Cause: Cannot create a user without specifying a password or "IDENTIFIED EXTERNALLY". Impact: TimesTen cannot perform the operation. User Action: Specify one of the password clauses.
15170	Profile profile_name cannot be assigned to user user_name	Type of Message: Error Cause: Cannot alter a user to assign a restricted profile, which can only be specified during create user. Impact: TimesTen cannot perform the operation. User Action: Specify a profile that can be assigned using alter user clause.
15171	Redundant resource	Type of Message: Error Cause: You attempted to create or alter a profile/user which try to specify same resource twice. Impact: TimesTen cannot perform the operation. User Action: Do not specify a resource more than once.
15172	Duplicate resource name resource_name	Type of Message: Error Cause: You attempted to create or alter a profile/user which specify duplicate resource name. Impact: TimesTen cannot perform the operation. User Action: Do not specify duplicate resource name.
15173	Invalid resource limit for resource_name	Type of Message: Error Cause: You specified an invalid resource limit value of 0 or less than 0 or 9223372036854775807. Impact: TimesTen cannot accept invalid resource limit values. User Action: Do not specify invalid resource limit values.
15174	Profile profile_name already exists	Type of Message: Error Cause: Unable to create a profile because it already exists. Impact: TimesTen cannot create a profile. User Action: Create a profile with a different name which does not exist.
15175	Profile profilename does not exist	Type of Message: Error Cause: Unable to alter or drop a profile which does not exist. Impact: TimesTen cannot alter or drop a profile. User Action: Alter or drop a profile which already exists.
15176	Profile profilename cannot be altered	Type of Message: Error Cause: Profile cannot be altered. Impact: TimesTen cannot alter the profile. User Action: Alter a profile which is not meant for internal use.
15177	Profile profilename cannot be dropped	Type of Message: Error Cause: Profile cannot be dropped. Impact: TimesTen cannot drop the profile. User Action: Drop a profile which is not internal or default.
15178	Profile profilename has users assigned, cannot drop without CASCADE	Type of Message: Error Cause: Profile has users assigned. Impact: TimesTen cannot drop a profile that has users assigned. User Action: Drop the profile using CASCADE option.
15179	the account is locked	Type of Message: Error Cause: The user has entered wrong password consequently for maximum number of times specified by the user's profile parameter FAILED_LOGIN_ATTEMPTS, or the DBA has locked the account. Impact: User cannot logon to the account. User Action: Wait for PASSWORD_LOCK_TIME or contact DBA
15180	the password has expired	Type of Message: Error Cause: The user's account has expired and the password needs to be changed. Impact: User cannot logon to the account without changing the password. User Action: change the password or contact the DBA.
15181	cannot expire password for external accounts	Type of Message: Error Cause: If a user account is created as IDENTIFIED EXTERNALLY, this account cannot be expired. Impact: TimesTen cannot expire password for user accounts created as IDENTIFIED EXTERNALLY. User Action: Try to expire the password of the user that has database password.
15182	Password will expire within string days	Type of Message: Warning Cause: Password is in grace period Impact: Password will expire if not changed within the grace period User Action: Change the password within the grace period.
15183	Password cannot be reused	Type of Message: Error Cause: Password has been already used Impact: Password cannot be used User Action: Use a password that has been not used
15184	Profile cannot have a schema name	Type of Message: Error Cause: Profile cannot have a schema name. Impact: Profile cannot be created. User Action: Do not specify a schema name when creating a profile.
15185	Cannot alter profile for predefined users	Type of Message: Error Cause: You cannot alter the profile for a user that was created during TimesTen database creation, including the instance administrator. Impact: TimesTen cannot perform the operation. User Action: None.
15186	Password complexity check for the specified password failed	Type of Message: Error Cause: The new password did not meet the necessary complexity specifications and the password complexity check failed. Impact: TimesTen cannot perform the operation. User Action: Enter a different password. Contact a user with ADMIN privileges to determine the rules used for the PASSWORD_COMPLEXITY_CHECKER function.
15187	Cannot specify schema name for password complexity checker function	Type of Message: Error Cause: A schema name cannot be specified for a PASSWORD_COMPLEXITY_CHECKER function. Impact: Profile cannot be created User Action: Do not specify a schema name for the PASSWORD_COMPLEXITY_CHECKER function.
15188	string	Type of Message: Error Cause: The execution of a password complexity check encountered an error. Impact: TimesTen cannot perform the operation. User Action: Review the error and execute the modified statement.

Errors 16000-16999

Error number	Error or warning message	Details
16001	TimesTen Replication Agent (version number.number.number) started	Informational message. No action required.
16002	TimesTen Replication Agent termination begun	Informational message. No action required.
16003	Replication Agent will not be re-started automatically	Informational message. No action required.
16004	Failed to connect to database 'database_name' for 'thread_name' thread	The specified thread was unable to connect to the named database.
16005	Failed to disconnect from database 'database_name' for 'thread_name' thread	The specified thread was unable to disconnect from the named database.
16006	Failed to create DB context for 'thread_name' thread	Creation of the structure that maintains status information for a specific thread failed.
16007	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.
16008	Failed to retrieve database info	Fetching the database information block failed.
16011	To avoid data inconsistency, copy the database from a replication subscriber using 'ttRepAdmin -duplicate'. Use ForceConnect=1 in the connection string to override this restriction	Attempt to reconnect to the master database without first performing the duplicate operation. Set the ForceConnect attribute as described in Recovering Nondurable Databases in Oracle TimesTen In-Memory Database Replication Guide for more information.
16012	Database 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.
16014	Current replication schema version is number; we require number	The version of the SQL schema that contains the replication schema is incompatible with the version of TimesTen that is currently operating.
16015	Failed to determine replication schema version	The replication agent was unable to determine the version of the SQL schema that contains the replication schema.
16016	Internal Error. Error from TimesTen daemon: error_message	A request to the TimesTen daemon failed with the specified error message.
16017	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.
16018	Failed to connect to TimesTen daemon for socket_name socket; port: port_number; id: subdaemon_id	The replication agent was unable to initiate a connection to the TimesTen daemon.
16019	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.
16020	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.
16021	TimesTen daemon appears to be vanished. Terminating Replication Agent	TimesTen daemon appears to have terminated. Terminating replication agent.
16022	Received a 'command_name' command	Informational message. No action required.
16023	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.
16024	Not enough memory to start 'thread_name' thread	A memory allocation failed for a TimesTen data structure that is used to manage threads.
16025	Thread 'thread_name' (context pointer) starting	Informational message. No action required.
16026	Thread 'thread_name' (context pointer; return code 'code_name') exiting	Informational message. No action required.
16027	All replication service threads have finished	Informational message. No action required.
16028	Number replication service threads did not finish	The replication agent is exiting, but some threads are not properly terminated.
16029	Waiting for 'thread_name' thread to finish	Informational message. No action required.
16030	*** CANNOT PERFORM ANY REPLICATION WORK *** The replication schema has no information about the local database. The schema may be empty or incomplete, or the local database incorrectly represented. Monitoring the schema for changes...	Informational message. No action required.
16031	Failed to allocate number bytes	Memory allocation failure.
16032	Call to function_name() failed. System Error: error_number	Type of Message: Error Cause: The specified operating system call failed with the operating system error that is displayed. Impact: Review the man pages of the failed operating system call for possible impacts. User Action: The man pages of the failed system call lists the possible causes for the failure. Diagnose and troubleshoot the operating system error. Then run the ttCWAdmin utility command that failed. If you are unable to troubleshoot the operating system error or still receive this error, contact TimesTen Customer Support.
16033	Waiting for resolution of in-doubt transactions	XA transaction has been prepared but not committed. Informational message. No action required.
16034	Invalid special purpose debug options entry in debug.options file	An unrecognized debug option was specified.
16035	Special Purpose. Repagent enabled for checkdebugging_option	Informational message. No action required.
16036	A transmitter thread already exist for peer 'database_name' on 'host_name'	Internal error. Two master threads are started for the same subscriber.
16037	Internal Error. Nested transaction started by function_name()	Unexpected nested internal query.
16038	Failed to begin transaction for caller: function_name()	The replication agent was unable to start a transaction.
16039	Failed to commit transaction for caller: function_name()	The replication agent was unable to commit a transaction.
16040	Failed to rollback transaction for caller: function_name()	Replication agent requested that a completed transaction be rolled back, but the request failed.
16041	Failed to compute a new replication hold LSN in function_name()	The replication agent was unable to set the HOLD log sequence number. The hold log is the oldest record held in the log for possible transmission to a subscriber. This error usually occurs due to a locking issue that is caused by either a long commit on the receiving side or an application blocking the replication agent. When this error is encountered, TimesTen will retry in 10 seconds. Check to ensure that you do not directly access the TTREP tables especially if you are using serializable isolation. Also, ensure that your transactions are not too large.
16042	Failed to awaken log readers (TRANSMITTER threads)	A keep-alive message to a replication master failed.
16043	Failed to retrieve replication LSN from datatabase	Reading the log sequence number failed.
16044	Failed to retrieve my store ID from database	The replication agent could not determine the ID of the connected database.
16045	Failed to retrieve peer store ID for the provided database name 'database_name' ON host 'host_name'. error_code. error_message	The replication agent failed to get a store ID for a specific database name and host name.
16046	Failed to force log	A full flush of the replication log to the subscriber failed.
16048	Mismatch in TimesTen version for source and destination instances	Type of Message: Error Cause: There is a mismatch between the version of TimesTen for the source and destination instances. Impact: TimesTen cannot perform the replication operation. User Action: Ensure that the source and destination instances use the same version of TimesTen and retry the operation.
16049	Failed to update CTN for peer 'database_name'	An attempt to update a Commit Transaction Number in the database failed.
16050	Failed to update replication hold LSN	An attempt to update the HOLD Log Sequence Number failed.
16051	Failed to update replication state	An attempt to update a log sequence number failed during a backup.
16052	Failed to set DB-level locking	Attempt to set the data-store-level lock failed.
16053	Failed to open temporary file needed for this operation. OS-detected error: error_details	A temporary file could not be opened during a backup. The operating system error is displayed.
16054	Failed to perform file seek in the temporary file needed for this operation. OS-detected error: error_details	A seek on a temporary file failed during a backup. The operating system error is displayed.
16055	Failed to read from the temporary file needed for this operation. OS-detected error: error_details	A read on a temporary file failed during a backup. The operating system error is displayed.
16056	Failed to backup database. Error_message	Database backup operation failed. The error message provides details.
16057	Failed to perform Network Checkpoint	Database checkpoint over a network connection failed.
16058	Failed to execute table renewal. error_code. error_message	An attempt to create a list of tables on the subscriber failed.
16059	Failed to send request/response to peer. error_message	Sending a message to the peer failed. The error message is displayed.
16060	Failed to read data from the network. Error_message isAwt (boolean) parallelism (number) trackId (number) socket (socket_name)	A read on a socket failed. This is often the result of network problems.
16062	Failed to compile command: sql_statement	Compilation of a SQL statement that is used by the replication agent failed.
16063	Failed to execute command: sql_statement	Execution of a SQL command used by the replication agent failed.
16064	Failed to execute prepared command in function_name()	Execution of a SQL command in the specified function failed.
16065	Failed to open cursor for command: sql_statement	Opening a cursor during execution of a SQL statement used by the replication agent failed. The SQL statement is specified.
16066	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.
16067	Failed to retrieve next row for command: sql_statement	Opening a cursor during execution of a SQL statement used by the replication agent failed. The SQL statement is specified.
16068	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.
16069	Failed to find a row for command: sql_statement	The replication agent on the subscriber could not find replication information about a peer.
16070	Internal Error. Failed to get format from command arguments for 'sql_statement'	Command argument substitution failed for a SQL statement used by the replication agent.
16071	Internal Error. Failed to get format from command results for 'sql_statement'	Command result substitution failed for a SQL statement used by the replication agent.
16072	Failed to delete command	Attempt to delete a compiled SQL command failed.
16073	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.
16074	No table found with id table_id	A specified table cannot be found. This can occur when the SQL schema is updated.
16075	Failed to lookup table table_name	Given an owner and table name, the table could not be found in the database.
16076	Failed to retrieve version information of table table_name	The version of a table could not be determined.
16077	Failed to retrieve format of table table_name	The format of a table could not be determined.
16078	Table definition for ID table_id is invalid (Original failure timestamp failure_details)	A specified table cannot be found. This can occur when the SQL schema is updated.
16079	Failed to retrieve information for column number of table table_name	The replication agent could not obtain description information for some column.
16080	Table: table_name. Failed to lookup row row_pointer from master database_name for 'operation_details'	A specific row was not found in a SQL table. This can occur during conflict resolution.
16081	Table: table_name. Failed to update row	A row of a table could not be updated.
16082	Table: table_name. Failed to update row row_pointer from master database_name for 'operation_details'	A row of a table could not be updated.
16083	Table: table_name. Failed to delete row for 'operation_details'	A row of a table could not be deleted.
16084	Table: table_name. Failed to insert row for 'operation_details'	A row of a table could not be inserted. This can occur during conflict resolution.
16085	Table: table_name. Failed to truncate table	An attempt to make a table empty failed.
16086	Wrong number (number) of peers updated	An attempt to update the peer in the database returned an unexpected number of results.
16087	Failed to read duplicate options	An attempt to determine the options given for a duplicate operation failed.
16088	Unique constraint violation	A uniqueness constraint failed on update or insert.
16089	Foreign Key constraint violation	A foreign key constraint failed on an update or insert.
16090	Failed to check constraints for table table_name	A constraint check failed on an update or insert.
16091	Failed to retrieve constraints information for table table_name	A table constraint failed on a update or insert.
16092	Unexpected log record type number	An unrecognized record type was found in the log.
16093	Invalid column type: number	An unrecognized column type was encountered in a log entry.
16094	Failed to execute SQL: statement	A SQL statement failed to execute for a command generated by the replication agent. The SQL string is displayed.
16095	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.
16096	Failed to retrieve information on index owner_name.index_name for table table_name	The replication agent was unable to determine information about an index.
16097	Failed to retrieve inline partition widths for table table_name	Internal error. Contact TimesTen Customer Support.
16098	Invalid replication schema. More than one entry for element element_name in replication scheme owner_name.scheme_name. Continuing...	More than one replication element has been found for a specific element such a table.
16099	Invalid replication schema. More than one master transmits table owner_name.table_name to me in replication scheme owner_name.scheme_name. Continuing...	Multiple tables with a particular owner and name were found in a replication schema.
16100	More than one host has peer 'database_name'	Multiple hosts have been identified as masters by a replication agent acting in a subscriber role.
16101	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.
16102	Count of zero return by request subscribers disagrees with having a return by request peer for table id table_id	The Return Receipt by Request attribute is inconsistent between two peers.
16103	Failed look up cache group owner_name.cache_group_name	Named cache group was not found.
16104	Incompatible cache group definition. Length of join predicate/where clause does not match for cache group owner_name.cache_group_name	Cache group definitions are inconsistent.
16105	Incompatible definition for cache group owner_name.cache_group_name	The cached group on the two peers is incompatible.
16106	Table table_name of cache group cache_group_name is not subscribed	There is an inconsistency in defining which tables are in a cache group.
16107	Failed to check cache group subscription for cache_view_id	Failed to check whether all tables of a cache view are subscribed to by a specific peer.
16108	Failed to retrieve local database information	The replication agent was unable to locate the TTREP.REPLICATIONS table.
16109	Failed to update send LSN (operation: operation_name)	The SEND Log Sequence Number could not be updated in the database.
16110	Failed to update return-receipt send LSN	Update of return-receipt Log Sequence Number in the database failed.
16111	Failed to initialize send LSN (operation: operation_name)	The data structure used to read the SEND Log Sequence Number could not be initialized.
16112	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.
16113	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.
16114	Attempting to connect to database_name on host_name (ip_address); port: number	Informational message. No action required.
16115	Connected to database_name (host_name); socket: number; port: number	Informational message. No action required.
16116	Added definition for column column_name (in table owner_name.table_name) into TTREP.REPTABLES	Informational message. No action required.
16117	Dropped definition for column column_name (in table owner_name.table_name) from TTREP.REPTABLES	Informational message. No action required.
16118	Failed to get replication hold value	An attempt to read the log sequence number for the hold log failed.
16119	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.
16120	Failed to update transaction statistics for peer database_name	The replication master attempted by update statistics about a peer, but the attempt failed.
16121	Failed to flush transaction queue. Restarting log read loop	Flush of the transaction log failed. Restarting read from the initial read LSN.
16122	Failed to send heartbeat to peer. Restarting log read loop	The replication agent was unable to send its heartbeat message to its peer.
16123	Transaction (connection_id.counter) 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.
16124	Failed to retrieve subscription information for table id table_id	A query of the replication schema information about subscribers failed.
16125	Inline data length for partitioned tuple (number bytes) exceeds maximum of number	Inline data for row is too long.
16126	Failed to initialize buffer for transaction log read	Transaction log failed to open.
16127	Failed to read transaction logs	A read of an entry from the transaction log failed.
16128	Log seek operation failed at LSN log_file_number/log_file_offset(caller line: number)	A seek (setting position) on the transaction log failed.
16129	Starting log read at LSN log_file_number.log_file_offset (caller line: number)	Informational message. No action required.
16130	Update record does not contain old values	An internal consistency check for the TimesTen engine shows that an update does not include old values.
16131	Internal Error. Bad copy to action ends at log_field not log_field with nbuf buffer primkeylen number	A log record has field lengths that are inconsistent.
16132	Internal Error. Buffer number addr pointer, size number	This message provides details for message 16131: Internal Error. Bad copy to action ends at log_field not log_field with nbuf buffer primkeylen primary_key_length.
16133	Peer signals change in its configuration	The peer configuration has changed.
16134	Received a packet of type: number	The type of network packet from a peer is not a recognized type.
16135	Failed to retrieve column information for table owner_name.table_name	An attempt to query the database for information about a table in the replication scheme failed.
16136	Sending definition for table owner_name.table_name (number columns)	Informational message. No action required.
16137	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.
16138	Propagation cannot co-exist with Master Catch-up	Catch-up mode on a propagating replication agent has occurred due to corruption in the database.
16139	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.
16140	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.
16141	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.
16142	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.
16143	Failed to retrieve any timeout information	Internal information about the replication scheme was not found.
16144	Failed to get a slot in the return-receipt buffer	Failed to allocate the buffer used by RETURN RECEIPT. Details in other error messages.
16145	Failed to update state in return-receipt buffer	The return receipt updated failed in the database.
16148	Reinitialize due to changes in replication schema	Informational message. No action required.
16149	Current state is FAILED for peer database_name	While reading the transaction log, the transmitter notices that its state is "peer failed."
16150	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.
16151	Log record type number, data size number, LSN log_file_number.log_file_offset	Internal error. Contact TimesTen Customer Support.
16152	Failed to determine whether replication state is FAILED	An attempt by the subscriber replication agent to determine if it has been marked Failed has failed.
16153	Failed to initialize return-receipt buffer	The subscriber replication agent was unable to initialize its RETURN RECEIPT state.
16154	Failed to check for replication schema changes	An attempt to mark a replication schema as changed has failed.
16155	Temporary failure to access replication configuration	The agent cannot access configuration information about replication. The agent can recover and continue.
16156	Failed to access replication configuration. Restarting replication agent	An attempt by the replication agent to access the replication schema failed.
16157	REPLISTENER thread waiting for number RECEIVER thread(s) to exit	Informational message. No action required.
16158	Failed to retrieve peer list	Query of the replication schema to determine subscribers failed.
16159	Starting new transmitter for 'database_name' on 'host_name'	Informational message. No action required.
16160	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.
16161	Listening on configured port: number (assigned port: number)	Informational message. No action required.
16162	Call to setsockopt(option) failed. System Error: error_number	A "Set Socket Options Failed" networking OS call failed. The details are included in this message.
16163	RECEIVER thread terminating due to certain error already recorded in the system log	The subscriber replication agent is exiting due to an error.
16164	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."
16165	Failed to perform backup operation	A subscriber backup operation failed. Details in other error messages.
16166	Failed to perform memory copy operation	Memory copy operation failed.
16167	Failed to check catch-up status	Automatic catch-up operation for a failed master database has failed.
16168	Master Catch-up started for 'database_name' from CTN timestamp sequence_number to timestamp sequence_number	Informational message. No action required.
16169	TimesTen Replication Agent termination begun because of permanent failure during Master Catch-up	Internal error. Contact TimesTen Customer Support.
16170	Master Catch-up completed for 'database_name'	Informational message. No action required.
16171	Confirm Name packet with unreasonable name length number	Internal error. Contact TimesTen Customer Support.
16172	Confirm Name packet for database_name received, but I am database_name	Internal error. Contact TimesTen Customer Support.
16173	Accepting messages from a peer that 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.
16174	Found more than one peer; cannot determine default	A subscriber discovered more than one peer with the same replication name and owner.
16175	Defaulted connection to peer store id store_id; protocol: number	Informational message. No action required.
16176	Signon message after transmitting peer assigned	A subscriber replication agent is reporting that the master requesting to sign on is already signed on.
16177	Lookup of transmitting peer database_name (host_name, replication_scheme_owner, replication_scheme_name) failed with signon error: error_number	A subscriber got a sign on request from a master, but there is no appropriate information about that master in the replication schema.
16178	Found transmitting peer database_name 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.
16179	Transmitting peer database_name 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.
16180	Transmitting peer database_name ON host_name has the same store id (store_id) as me	The peer ID found by a replication agent was its own ID. Possible cause is corrupt TTREP.REPNETWORK table.
16181	Replication reserve slot failed	Query to reserve a "commit transaction number" slot failed (and logged its own error message).
16182	Replication ctnlist (CTN: number) value read failed	The replication agent was unable to read the Commit Transaction Number from the database.
16183	Failed to set replication status for this connection	Query to set replication status failed (and logged its own error message).
16184	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.
16185	RECEIVER thread noticed replication configuration change	Informational message. No action required.
16186	RECEIVER thread disconnects due to superseded connection from peer (internal version was number, now 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.
16187	Transaction: " transaction "; Error: transient error_number, permanent error_number state state error message : error_message	The commit of a block of transactions had errors. Details in other error messages for the individual failures. Some failures may be temporary.
16188	rxCommitTx() failed to commit	The commit of a block of transactions failed.
16189	Failed to begin transaction. Subscriber state is number	Type of Message: Internal Error Cause: The replication agent is beginning a transaction, but it is not in the idle state. Impact: The replication receiver is delaying the process and will retry the transaction. User Action: Restart the replication agent. If you still receive this error after restarting the replication agent, contact TimesTen Customer Support.
16190	Failed to push propagation loop	A propagation path could not be stored, usually because it is a loop.
16191	Replacing old table definition (definition) with the one received from peer (database_name)	A SQL table that has already been seen in the replication stream has been encountered. This can occur if there are SQL schema changes.
16192	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.
16193	Adding definition for table: table_name	Informational message. No action required.
16194	Subscriber return service attribute conflict for element element_name (table table_name) in replication scheme owner_name.scheme_name. Transmitting peer database_name ON host_name says 'return_service'; local schema says 'return_service'. Transmitter's value will be used	The return attribute on this replication element is different for each peer.
16195	Failed to find owner for element element_name (table table_name) in replication scheme owner_name.scheme_name (received from peer database_name ON host_name). Continuing ...	Failed to find owner for this table element in the replication scheme on the named replication peer.
16196	Master/subscriber conflict with peer database_name on host_name for element element_name (object object_name) in replication scheme owner_name.scheme_name.	The owner of this table element conflicts on the two replication peers.
16197	Failed to add element element_name (table table_name) for transmitting peer database_name ON host_name	Attempt to add a replication element has failed, probably due to a duplicate. This is a rare condition where something happens between when a check is made and the attempt to add the element.
16198	Table definition mismatch on number of columns for table table_name. Local definition: number; transmitting peer: number	"Table Definition Mismatch" between the two peers. Some differences are tolerated, but others are not.
16199	Table definition mismatch on failure_type for column column_number in table table_name. Local definition: number; transmitting peer: number	"Table Definition Column Mismatch" between the two peers.
16200	Table definition mismatch on timestamp column in table table_name. Local definition: timestamp; transmitting peer: timestamp. Continuing with transmitter's value	The TIMESTAMP column on one peer is not the same as the TIMESTAMP column on another peer. This can occur during conflict resolution based on timestamps.
16201	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.
16202	No cache group entry for table table_name	A subscriber replication agent could not find a cache group associated with a particular table sent by the master.
16203	Passed extended comparison for table table_name	Informational message. No action required.
16204	Table table_name marked invalid. Will not apply transactions received for it until a valid definition is received	A replicated table was marked invalid.
16205	Skipping definition received for cache group cache_group_name. Part of previously processed transaction	Informational message. No action required.
16206	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.
16207	Internal error. Table ID mismatch	Internal error. Contact TimesTen Customer Support.
16208	Failed to open file file_name for Timestamp report	Could not open the replication agent report file.
16210	Varying length part of key tuple > number bytes	The size of a primary key caused an overflow of a data packet.
16211	No matching V* value found for Table: table_name; column: column_name; offset: column_offset; ID: numberInsert LSN from peer (database_name) was log_file_number.log_file_offset string	Type of Message: Internal Error Cause: There is an inconsistency between the master and subscriber in the area of VARCHAR or VARBINARY columns in a replicated table. Impact: There is a divergence of data between the master and the subscriber because a transaction did not replicate correctly. User Action: Contact TimesTen Customer Support.
16212	Failed to set column number of table table_name	Subscriber replication could not set a column value.
16213	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.
16214	Table: table_name. Failed to delete row. Error_message	Subscriber replication agent could not delete a row due to a timestamp conflict.
16215	Table: table_name. Failed to update row. Error_message	Subscriber replication agent could not update a row due to a timestamp conflict.
16216	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.
16217	Connection connection_id awakened	Replication transactions have been halted, but the peers are connected again.
16219	Failed to retrieve any compression information	The replication agent cannot find information to complete compression.
16220	Replication is not supported with an agent using the protocol protocol_type	Incompatible versions of the replication protocol between the two peers.
16221	Table table_name not found	Table specified by master not found on receiver.
16222	The call gettimeofday failed	The system call to get time of day failed.
16223	Transmitter thread failure due to high latency number with peer database database_name	The network latency between the databases is higher than permitted for an active standby pair.
16224	Transmitter thread failure due to high clock skew number with peer database database_name	The clock slew between the databases is higher than permitted for an active standby pair.
16225	Transmitter thread failure due to lack of scheme consistency with peer database	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 databases match.
16226	Receiver thread failure due to scheme read failure	The local database was unable to read the replication scheme.
16227	Standby database has replicated transactions not present on the active. Local CTN=" commit_ticket_number ", Backup CTN=" commit_ticket_number ", Received CTN=" commit_ticket_number ".	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.
16228	Transmitter thread failure due to lack of state consistency between active and standby databases	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 databases match.
16229	Transmitter thread failure due to lack of state consistency at subscriber database database_name	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 databases match.
16230	Store not in standby state	An error returned by the replication agent that indicates a transitory condition. No user action is necessary.
16231	The duplicate operation on this database 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.
16232	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 database.
16233	The subscriber database has updates not present on the active database	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.
16234	The standby database has been classified as failed by the active	The databases 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 databases match.
16235	Failed to update CTNs for standby 'database_name'	Error updating replication bookmark information (Commit Ticket Number) in the replication agent.
16236	Failed to update CTN for the subscriber database	Error updating replication bookmark information (Commit Ticket Number) in the replication agent.
16237	Awt thread initialized for OracleNetServiceName=service_name, CacheUid=user_id, BatchCommitSize=number, AwtErrorFile=file_name, AwtBufSize=number KB	This message appears in the user error log. It is informational. No action is necessary.
16242	Failed to retrieve subscription information for sequence id sequence_id	A failure occurred while retrieving subscription information for a sequence.
16243	No sequence found with id sequence_id	A sequence with the specified ID was not found.
16244	Skipping definition received for already-defined sequence sequence_name. Part of previously processed transaction	A subscriber received information about a sequence but already has the information.
16245	Adding definition for sequence: sequence_name	Generated when information about a replicated sequence on the subscribing side is added to the list of sequence information.
16246	Sequence definition mismatch for sequence sequence_name. 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.
16247	Sequence sequence_name 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.
16248	Sequence sequence_name not found	A subscriber database received a definition for a sequence that does not exist on the subscribing side.
16249	Failed to add sequence to transmit queue	This error occurs a sequence update message from the master database was not added to the queue.
16250	Failed to update sequence sequence_name	Failed to apply a sequence update to the subscriber database.
16251	Sending definition for sequence owner_name.sequence_name	Informational message from master database.
16252	Table definition mismatch on cascade delete configuration for table table_name. Local definition: fk_string; transmitting peer: fk_string	The foreign key cascade delete constraints for the table do not match between the master and subscriber databases.
16253	Failed to retrieve cascade delete configuration for table table_name	Type of Message: Internal Error Cause: The ON DELETE CASCADE definition on the master and subscriber may not be the same. Impact: Replication for this table cannot work until the ON DELETE CASCADE definition is the same on the master and subscriber. User Action: Ensure that the ON DELETE CASCADE definition is the same on the master and subscriber. For more information on using ON DELETE CASCADE in a replication scheme, see Replicating Tables With Foreign Key Relationships in a Classic Replication Scheme in Oracle TimesTen In-Memory Database Replication Guide. For additional help, contact TimesTen Customer Support.
16254	Master has not been assigned an Active or Standby Role	This message could occur when a replication agent for a master database in an ACTIVE STANDBY scheme has been started but has not been classified as either master or standby. The thread attempts to restart until a state has been determined.
16255	Invalid replication schema. More than two _ORACLE databases found in scheme	Type of Message: Internal Error Cause: A sanity check has failed in an ACTIVE STANDBY scheme that includes autorefresh cache groups. Impact: Replication cannot work. User Action: Contact TimesTen Customer Support.
16256	Invalid replication schema. No _ORACLE databases found	Type of Message: Internal Error Cause: A sanity check has failed in an ACTIVE STANDBY scheme that includes autorefresh cache groups. Impact: Replication cannot work. User Action: Contact TimesTen Customer Support.
16257	The ID for this database does not match either of the master Ids	Type of Message: Internal Error Cause: A sanity check has failed after a ttRepAdmin -duplicate operation on an ACTIVE STANDBY scheme that includes autorefresh cache groups. Impact: You cannot duplicate the database. User Action: Contact TimesTen Customer Support.
16258	Failed to retrieve heartbeat factor information	Internal error. Contact TimesTen Customer Support.
16259	Wrong number of rows (number) affected on Oracle when updating Active Standby Information	Type of Message: Internal Error Cause: A sanity check failed in an ACTIVE STANDBY scheme when information was updated on an Oracle database subscriber. Impact: Replication cannot work correctly. User Action: Contact TimesTen Customer Support.
16260	Failed to update autorefresh bookmark	The replication operation was unable to update the autorefreshed cache group bookmark on the subscriber database at runtime. This may occur because the cache group does not exist on the subscriber.
16261	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 database.
16262	Failed to retrieve subscription information for cache bookmark id table_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 database.
16263	Secure protocol violation	There was a connection attempt from another replication agent that violated the security challenges presented on the protocol.
16264	Awt Ctn initialized to timestamp=timestamp SeqNum=sequence_number	Informational message. No action required.
16265	This database is currently the STANDBY. Change to owner_name.table_name not permitted.	When an active standby master is in STANDBY mode you cannot update the database directly. Operations such as adding or dropping a column, INSERT, UPDATE, TRUNCATE, or DELETE are prohibited.
16266	The -remoteDaemonPort cannot be used for this -duplicate operation because the master database has subscriber databases 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 -remoteDaemonPort option in the duplicate operation or supply a value of 0 for the operation.
16267	The host name list is not available from ttrep.ttnetwork.	An error occurred in performing a query on TTREP.REPNETWORK table. 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.
16268	Failed to retrieve aging configuration for table owner_name.table_name	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.
16269	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 the ttCacheAWTMonitorConfig built-in procedure automatically enables monitoring the AWT statistics.
16270	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 the ttCacheAWTMonitorConfig built-in procedure to disable monitoring the AWT statistics.
16271	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 the ttCacheAWTMonitorConfig built-in procedure again, with the state parameter set to "ON."
16272	Operation not permitted on a database 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.
16273	Error updating standby database.	A failure occurred while trying to get the latest status for an active standby pair standby.
16274	Failed to modify active standby data. caller: function_name()	After a duplicate operation, some data on TimesTen system tables must be modified for the destination database on both TimesTen and the Oracle database. This operation has failed, but the replication agent retries the operation.
16275	RECEIVER network helper thread terminating due to certain error already recorded in the system log	Type of Message: Error Cause: Review the user error log for error messages relating to the RECEIVER network helper thread for possible causes. Impact: TimesTen terminates the RECEIVER network helper thread. User Action: None.
16276	RECEIVER restarting daemon because helper thread failed to spawn	Type of Message: Error Cause: Review the user error log for error messages relating to the RECEIVER network helper thread for possible causes. Impact: The replication agent recycles the helper thread. User Action: None.
16277	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 running ttRepAdmin -duplicate or ttRepDuplicateEx.
16278	Failed to get Cache AWT method	Unable to get the attribute value for use in the replication agent. An invalidation was most likely detected.
16279	Cannot start AWT propagation because replication agent cannot connect to Oracle RDBMS database: OracleNetServiceName = \"service_name\", uid = \"user_id\", pwd is hidden, TNS_ADMIN = \"path\", Error Msg= \"error_message\"	Replication agent is not able to connect to the Oracle database. Check to see that TNS_ADMIN is configured properly and ensure that the Oracle database is reachable.
16280	Parallel AWT requested restart of the worker threads	Parallel AWT thread encountered an error and restarting of the threads was necessary.
16281	Replication receiver track track_id waiting for receiver track track_id to initialize	This is an informational start up message.
16282	Replication receiver track track_id waiting for receiver track track_id to finish	This is an informational shut down message.
16287	Replication receiver with local store id: store_id on: host_name; remote store name: store_name(id store_id) on hostname: host_name; trackId: track_id still finds a previous track 0 receiver running.	A master thread running on the receiver was detected and should not have been.
16288	Replication receivers are stopping.	This is an informational shut down message.
16289	Replication receivers face dependency error.	There was an internal error during a replication dependency wait for parallel processing.
16290	Replication transmitters are stopping.	This is an informational shut down message on the transmitter. The group of threads for a particular subscriber are stopping.
16291	Replication receivers are starting serial commit mode	Type of Message: Error Cause: TimesTen detected a problem with parallel replication. TimesTen is reprocessing the transactions in serial mode. Impact: Replication throughput is momentarily decreased. User Action: Contact TimesTen Customer Support.
16292	Replication receivers are stopping serial commit mode	This is an informational message indicating that the replication receivers are stopping serial commit mode.
16294	Transmitter waiting on AWT appliers.	Type of Message: Warning Cause: Propagation from TimesTen to the Oracle database is slow, causing transmitter threads to stall. Impact: This can result in LOG_FS_READS that may cause performance degradation of replication throughput. This may also increase workload on the I/O subsystem. For more information on LOG_FS_READS, see SYS.MONITOR in Oracle TimesTen In-Memory Database System Tables and Views Reference. User Action: Contact TimesTen Customer Support.
16295	Failure updating Active Standby role/state information on the Oracle database	Type of Message: Error Cause: The replication agent cannot update the indicated information on the Oracle database. Impact: Review the error message for possible impacts. User Action: Review the error message for possible fixes.
16296	Receiver for database_name on host_name port port_number completed handshake with Transmitter for database_name on host_name	Type of Message: Informational Cause: A receiver for the specified subscriber database completed a handshake with a transmitter of the specified master database. Impact: None. User Action: None.
16297	Failed to set transparent load	Type of Message: Error Cause: The transmitter cannot set transparent load. Impact: The transmitter will retry to set transparent load. Also, the threads will attempt to recycle and self-correct the error. Review the error message for any additional impacts. User Action: Review the error message for possible fixes.
16298	Waiting for the AWT receiver to complete propagation. Current sleep iteration number	Type of Message: Informational Cause: The replication agent is waiting for the AWT receiver to complete the propagation of a long running AWT transaction. Impact: The replication agent cannot timeout while the AWT transaction is being propagated to the Oracle database. User Action: None.
16299	Finished with received request command_name	Type of Message: Informational Cause: The replication agent completed the specified request. Impact: None. User Action: None.
16300	Failed materialized view info: info additional_info	Type of Message: Error Cause: The replication agent failed to update a base table for a materialized view. Impact: The replication agent cannot update the base table for the materialized view. If this is a transient error, the replication agent tries the transaction again. If this is a permanent error, the transaction is lost. User Action: Review the daemon log for any additional error messages to determine a cause for this error. For more information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide. For more information on materialized views, see Understanding Materialized Views in the Oracle TimesTen In-Memory Database Operations Guide.
16301	Table: table_name. Failed to bulk insert row number from master database_name	Type of Message: Error Cause: The replication agent failed to insert the specified row into the specified table of the standby or subscriber database. Impact: If this is a transient error, the replication agent tries the operation again. If this is a permanent error, there may be differences in the data contained by the databases that are part of the replication scheme. User Action: Review the daemon log for any additional error messages to determine a cause for this error. Also, verify that the data contained in the specified table in the databases that are part of the replication scheme is consistent. For more information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
16302	Failed to retrieve Replication Stats subscriber ID for store id store_id	Type of Message: Informational Cause: Failed to retrieve replication stats subscriber ID Impact: None. User Action: None.
16303	Backing out of wait and retrying transaction	Type of Message: Internal Error Cause: The replication agent detected a parallel replication deadlock and is retrying the operation. This message is preceded by another message that describes the details of the error. Impact: None. User Action: Review the daemon log for any additional error messages to determine a cause for this error. For more information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
16304	Flagging transaction timestamp.sequence_number on track track_id to rollback and retry. Currently waiting on timestamp.sequence_number track track_id	Type of Message: Informational Cause: This is an accompanying error message to error 16303. The specified transaction is flagged for retry. Impact: None. User Action: None.
16305	Constraint Check Fail table table_name Optype operation_type tuple key tuple_key	Type of Message: Error Cause: The replication agent encountered an error while checking constraints on an operation. Impact: If this is a transient error, the replication agent tries the operation again. If this is a permanent error, there may be differences in the data contained by the databases that are part of the replication scheme. User Action: Review the daemon log for any additional error messages to determine a cause for this error. Also, verify that the data contained in the specified table in the databases that are part of the replication scheme is consistent. For more information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
16306	DepCTN[track_id] = timestamp.sequence_number	Type of Message: Informational Cause: The replication agent is printing the dependency information on a transaction because of a failed operation. This message is followed by another messages that describe the details of the failure. Impact: None. User Action: Review the daemon log for any additional error messages to determine a cause for this error. For more information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
16307	rxWaitCTN waiting for timestamp.sequence_number on track track_id currently at timestamp.sequence_number stalled for number seconds. Check if a replication track is falling behind and, if so, consider using ttDbConfig('ParReplMaxDrift'...)	Type of Message: Internal Error Cause: TimesTen is experiencing a performance issue. This message is followed by another message that describe the details of the issue. Impact: TimesTen is stalling the transaction. User Action: Use the ttXactAdmin utility to verify the status of the specified transaction. Also, review the message log for any additional error messages to determine a cause for this error. For more information on the ttXactAdmin utility, see ttXactAdmin in Oracle TimesTen In-Memory Database Reference and Using the ttXactAdmin utility in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide. For more information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
16308	Error while initializing context ctn array.	Type of Message: Error Cause: TimesTen cannot allocate memory from the heap for the CTN array in the context. Impact: The database cannot continue normal operations. User Action: Increase the value for the PermSize or TempSize attribute, or both. For more information on how to increase the values of PermSize and TempSize, see Specifying the Memory Region Sizes of a Database in Oracle TimesTen In-Memory Database Operations Guide.
16309	Error requesting sync point for drift correction	Type of Message: Internal Error Cause: This message is preceded by another message that describes the details of the error. Impact: TimesTen cannot perform the operation. User Action: Retry the operation. If the error persists, review the daemon log for any additional error messages to determine a cause for this error. For more information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
16310	Replication listener thread initialization complete.	Type of Message: Informational Cause: The replication agent initialized the listener thread. Impact: None. User Action: None.
16311	Received CTN=" commit_ticket_number " Local CTN=" commit_ticket_number " Backup CTN=" commit_ticket_number ".	Type of Message: Informational Cause: The replication agent confirmed the received CTN information. Impact: None. User Action: None.
16312	rxWaitTrackSync counter number rxp->timeout number IsRcvrStopping status IsDaemonStopping status	Type of Message: Informational Cause: The replication agent set and synchronized all of the replication tracks. Impact: None. User Action: None.
16313	Batch processing exceeds timeout: batch_info	Type of Message: Error Cause: The time taken to replay a batch of transactions exceeded the replication timeout. Impact: Replication could potentially stall. User Action: Consider reducing the size of transactions or increasing the replication timeout. For more information, see Setting Wait Timeout for Response from Remote Replication Agents in Oracle TimesTen In-Memory Database Replication Guide.
16314	Parallel replication waited for too long	Type of Message: Error Cause: The replication agent waited too long for a dependency to resolve. Impact: The replication agent restarts and retries the operation. User Action: Contact TimesTen Customer Support.
16315	Could not set lock wait to lock_wait	Type of Message: Error Cause: The replication agent failed to adjust the lock wait. Impact: TimesTen could not adjust lock timeout. User Action: Review the associated error message to determine a cause for this error.
16316	Invalid connection message	Type of Message: Error Cause: Invalid message received from peer. Impact: The replication agent retries the operation. User Action: Contact TimesTen Customer Support.
16317	Skipping operation as it predates table creation: skip_info	Type of Message: Informational Cause: The replication transmitter found an operation for a table that has been dropped. Impact: The replication agent ignores the operation because it predates the time that the table was created. User Action: None.
16319	Replication Agent cannot start due to network errors and has shut down. Please restart.	Type of Message: Error Cause: The replication agent cannot start due to network errors and has shut down. Impact: The replication agent has stopped due to repeated network errors on start up. User Action: Check the message log for the specific problem and restart the replication agent after it has been addressed.
16321	DynamicLoadReduceContention setting (local_setting) mismatch with peer peer_name setting (peer_setting) signon error: signon_error. Consider using ttDbConfig to match the setting with the peer	Type of Message: Informational Cause: There is a configuration mismatch between local and remote databases. Impact: None. User Action: Use the ttDBConfig('ArDlReduceContention') built-in procedure to check the settings on both databases and ensure that the settings match.
16322	Problem in SSL communication : ssl_error_details	Type of Message: Informational Cause: There is a problem in SSL communication between replication peers or utilities. Impact: None. User Action: Review the accompanying message to determine the cause of the failure.
16323	Connection rejected because the ttDbConfig option 'receiverrestrict' has been enabled and larger number of replication receiver threads (max_receivers) have been started than expected (receiver_count).	Type of Message: Error Cause: There is a potential problem with the number of connect requests being sent to the Replication Agent. Impact: No new connections will be accepted until the number of receiver threads falls below the expected number. User Action: Review the message log to determine the cause of the problem.
16324	Problem in SSL configuration : ssl_error_details	Type of Message: Warning Cause: There is a problem with an SSL parameter for Replication. Impact: None. User Action: Review the error message to determine the cause of the problem and correct the parameter value.
16325	CacheAdminWallet setting (local_setting) mismatch with peer peer_name setting (peer_setting) signon error: signon_error	Type of Message: Informational Cause: There is a configuration mismatch between local and remote databases. Impact: None. User Action: Ensure that the settings for the CacheAdminWallet connection attribute match on both the local and remote databases.
16326	Failed to truncate table_owner.table_name error code TTerror_code attempting DELETE FROM instead.	Type of Message: Warning Cause: TimesTen failed to perform a TRUNCATE TABLE operation on the specified table. TimesTen attempts a DELETE FROM operation instead. Impact: None. User Action: Check why the TRUNCATE TABLE operation could not be performed and modify the configuration of the database to avoid this issue in the future.
16999	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
17000	Object_type owner_name.object_name was quoted in an clause_name clause but does not exist.	The table or cache group specified in an INCLUDE or EXCLUDE clause does not exist.
17001	The clause_name object_type clause has the same name (object_name) mentioned more than once.	The INCLUDE or EXCLUDE clause mentions the same table name or cache group name more than once.
17002	You cannot exclude everything from being replicated.	All objects in the database were excluded in the CREATE REPLICATION statement. There must be at least one object in the database.
17003	Maximum number of peers (number) exceeded for store_id.	The limit on the maximum number of peer databases was exceeded. The message indicates the maximum limit.
17004	Table owner_name.table_name of cache group owner_name.cache_group_name cannot be part of a replication subscription if the cache group is using autorefresh with state ON.	A table that is part of an autorefresh cache group, whose autorefresh state is on, cannot be a subscriber in a replication scheme. Turn the AUTOREFRESH STATE to OFF.
17005	Cannot configure conflict checking on a object_type element	Conflict checking cannot be configured on a SEQUENCE element, for example.
17006	Cannot configure return service on a object_type element	Return service cannot be configured on a SEQUENCE element, for example.
17007	Sequence owner_name.sequence_name cannot be replicated because it was created with CYCLE specified	TimesTen does not support the replication of sequences that were defined with CYCLE specified. If a replication element is created (either by CREATE REPLICAION or ALTER REPLICATION...ADD ELEMENT) and an INCLUDE or EXCLUDE clause is used or a ELEMENT SEQUENCE clause is used, and if the element involves a cycling sequence, then this error is generated.
17008	Sequence owner_name.sequence_name 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 by CREATE REPLICATION or ALTER REPLICATION...ADD ELEMENT) and a cycling sequence is involved, then the cycling sequence is not replicated.
17009	Stores database_name and database_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 databases conflict. Master and subscriber port numbers in a replication scheme must be the same.
17010	Store database_name has been configured with a timeout of number. This is lower than the recommended minimum of number and could lead to unnecessary replication timeouts.	The replication connection timeout is below the recommended value. This may lead to many unnecessary connects and disconnects, thereby flooding the syslog and slowing down replication. The message indicates the minimum limit.
17011	The RELEASE attribute has been specified for store database_name. This feature has been deprecated and the value supplied has been ignored.	This feature has been deprecated.
17012	All AWT cache groups must be part of the Active Standby scheme. The AWT cache group for table owner_name.table_name has been quoted in an EXCLUDE CACHE GROUP clause.	AWT cache groups cannot be excluded from an ACTIVE STANDBY scheme. Redefine your ACTIVE STANDBY scheme in such a way that these cache groups are included in the scheme.
17013	The default hostname cannot be set to host_name because a local host of host_name is currently in use.	Using the built-in procedure ttHostNameSet you have specified a host name for a replication subscribe to a value that differs from the default host name already in use by a replication scheme. The host name is not changed. To view the current host name specified in the scheme, use the procedure ttHostNameGet.
17014	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 database attribute.
17015	The aging policy for table table_name differs from its peer: error_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
17016	Error getting dbcharset id	Type of Message: Internal Error Cause: A sanity check between the master and subscriber of a replication scheme failed to identify the character set used in the database. Impact: The replication agent cannot start correctly. User Action: Check the additional error messages to identify a possible cause as to why the character set used in the database could not be identified. For additional help, contact TimesTen Customer Support.
17017	The database character set differs from its peer	Type of Message: Internal Error Cause: The database character set used by a master in a replication scheme is different than that used by the subscriber. Impact: The replication agent cannot start correctly. User Action: Check the character sets defined by the databases in your replication scheme. If the character sets differ, make the appropriate changes so that all databases are using the same character set. If the character sets are the same, contact TimesTen Customer Support. For more information, see Choosing a Database Character Set in Oracle TimesTen In-Memory Database Operations Guide.
17018	Cannot replicate to peer because it is a pre-7.0 database and this database does not have the DatabaseCharacterSet attribute set to 'TIMESTEN8'	For TimesTen to be able to replicate NCHAR type columns between this release and pre-7.0 releases of TimesTen the database in this release must have the DatabaseCharacterSet attribute set to TIMESTEN8.
17019	Store database_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 database. Use a port number for the replication database that does not clash with the main daemon port.
17020	Failed to check CG state for duplicate	TimesTen failed to check the state of cache groups in the source database. See the message log for the cause of the failure.
17021	Failed to reset Autorefresh bookmark	As part of the -duplicate initialization, the autorefresh bookmarks for cache groups in the database could not be reset. See the message log for the cause of the failure.
17022	The same attribute (attribute_name) has been set multiple times for the same subscriber (database_name) for element element_name	An ALTER REPLICATION statement has altered the return service attribute more than once for the same database.
17023	Store database_name is used in a route clause but does not exist	A ROUTE clause quoted a non-existent database. Retry the operation with a different ROUTE name.
17024	ROUTE master database_name subscriber database_name hostname host_name not found	A non-existent ROUTE name was specified in a statement that is attempting to ADD or DROP a route to a scheme. Retry the operation with a different ROUTE name.
17025	ROUTE master database_name subscriber database_name route_info cannot be created because a Master->Subscriber relationship does not exist between these databases	An attempt was made to set up a replication ROUTE for a non-existent master/subscriber relationship. Retry the operation with a different ROUTE name.
17026	ROUTE master database_name subscriber database_name route_info cannot be created because an entry for this route already exists with priority priority_level, or is in the process of being created	The ROUTE name already exists. Retry the operation with a different ROUTE name or wait for the process that uses the specified ROUTE name to complete.
17027	ROUTE master database_name subscriber database_name route_info cannot be created because an entry for this route already exists using interface host_name, or is in the process of being created	The ROUTE name already exists. Retry the operation with a different ROUTE name or wait for the process that uses the specified ROUTE name to complete.
17028	The PRIORITY attribute must be between 1 and 99	The specified PRIORITY value is out of range.
17029	This store (database_name on host_name) is not involved as a local store in replication scheme owner_name.scheme_name	A scheme is attempting to be created on a database that is not involved in the scheme. Retry the operation with the correct database name, or involve the database in the specified scheme.
17031	CONFLICT REPORTING RESUME must be less than CONFLICT REPORTING SUSPEND for STORE database_name	The RESUME value must be less than the SUSPEND value for conflict reporting. Retry the operation with a smaller value.
17032	CONFLICT REPORTING RESUME cannot be set without a CONFLICT REPORTING SUSPEND value for STORE database_name	You cannot resume conflict reporting without specifying a SUSPEND value. Retry the operation after specifying a SUSPEND value.
17033	CONFLICT REPORTING RESUME or SUSPEND cannot be set for databases 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.
17034	ASYNCHRONOUS WRITETHROUGH Cache groups cannot co-exist with a replication scheme that uses RETURN TWOSAFE	You cannot have ASYNCHRONOUS WRITETHROUGH cache groups in a replication scheme that uses RETURN TWOSAFE.
17035	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.
17036	SYNCHRONOUS WRITETHROUGH cache groups cannot be replicated in an ACTIVE STANDBY scheme. Either DROP or EXCLUDE the cache group for table owner_name.table_name	SYNCHRONOUS WRITETHROUGH cache groups cannot be replicated in an ACTIVE STANDBY scheme.
17037	The receiver state in an ACTIVE STANDBY scheme cannot be set to STOP	When the database is involved in an active standby scheme, you cannot call ttrepsubscriberstateset(,,,,2) or specify the utility operation ttRepAdmin -receiver -name rep2 -host somemachine -dsn rep1 -state stop.
17038	The database is not a valid peer	The peer specified is not valid in the replication scheme.
17039	Failed to bind host_name (ip_address); socket: socket_number	Type of Message: Informational Cause: The replication agent cannot bind to the specified host and IP address. Impact: The replication agent will try connecting using other network interfaces. If the replication agent cannot connect using the other network interfaces, replication for the peer will not work. User Action: Check the error messages to identify a possible cause as to why the bind failed.
17040	Trying to create socket for database_name on ip_address	Trying to create socket on an IP address for the indicated database.
17041	Failed to create Oracle DR scheme	This is a generic error, there is an additional detailed error message concerning the actual failure. Review that message to determine the problem and the fix.
17042	A Cache DR scheme can only be created on an ACTIVE STANDBY SUBSCRIBER	The ttRepAdmin -duplicate -initCacheDR option 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.
17043	Failed to initialize Oracle DR tables	The initialization of the Oracle database 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.
17044	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.
17045	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.
17046	Could not flush data to Oracle DR site	During disaster recovery, the replication agent could not flush data to the Oracle database. 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.
17047	Could not commit data to the Oracle DR site	During disaster recovery, the replication agent could not commit data to the Oracle database. 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.
17048	Could not create thread to initialize the Oracle DR site	During disaster recovery, the replication agent could not create the thread to initialize the Oracle database. 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.
17049	Error invalidating database due to scheme inconsistency	To correct this problem, verify that the schemes involved in this operation are identical.
17050	Conflict Replication Reporting Starting	Type of Message: Informational Cause: Replication conflict reporting suspend/resume is configured on your system and the conflict rate has fallen below the resume value. Impact: Replication conflict reports are now being sent. User Action: None. For more information on how to configure suspend and resume values for replication conflict reporting, see Suspending and Resuming the Reporting of Conflicts in Oracle TimesTen In-Memory Database Replication Guide.
17051	Conflict Replication Reporting Stopping	Type of Message: Informational Cause: Replication conflict reporting suspend/resume is configured on your system and the conflict rate exceeds the suspend value. Impact: Replication conflict reports are now suspended. User Action: None. For more information on how to configure suspend and resume values for replication conflict reporting, see Suspending and Resuming the Reporting of Conflicts in Oracle TimesTen In-Memory Database Replication Guide.
17052	System table owner_name.table_name cannot be excluded from replication	System tables cannot be modified by users and must be included in the replication process.
17053	Table table_name is replicating in relaxed mode	Type of Message: Informational Cause: The master table being replicated is structurally different than the subscriber. Impact: Extra performance overhead is required to achieve replication for this table. User Action: You can improve replication performance if the table structure on both sides of the replication scheme is the same. Adjust the table structure on one side of the replication scheme so that it matches the table structure of its peer. For more information, see Altering a Replicated Table in a Classic Replication Scheme in Oracle TimesTen In-Memory Database Replication Guide.
17055	Asynchronous Materialized View Log Table owner_name.table_name cannot be included in a Replication Scheme	An explicit ALTER replication include table was used on an Asynchronous materialized view log table.
17056	Dynamic Cache Group Table owner_name.table_name 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.
17057	PROPAGATE cache groups cannot be replicated in an ACTIVE STANDBY scheme. Either DROP or EXCLUDE the cache group for table owner_name.table_name	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.
17058	Table owner_name.table_name 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 and ReplicationApplyOrdering=1.
17059	Replicated INCLUDE TABLE failed for (owner_name.table_name) because the table is not empty	You attempted a replicated ALTER STANDBY PAIR...INCLUDE TABLE and the table is not empty.
17060	DDLReplicationAction can only be set to INCLUDE or EXCLUDE on the ACTIVE database in an ACTIVE STANDBY PAIR replication scheme	You attempted ALTER SESSION...SET DDL_REPLICATION_ACTION on a database that is not active in the active standby pair replication scheme.
17061	When DDLReplicationAction='INCLUDE' tables must be created with a primary key or a unique constraint on non-nullable column(s)	You specified a DDL_REPLICATION_ACTION that requires the table(s) to be created with an index.
17062	DDLReplicationAction and DDLReplicationLevel can only be set on a database with an ACTIVE STANDBY PAIR scheme	You attempted to use the ALTER SESSION statement to set DDLReplicationAction and DDLReplicationLevel on a database that is not part of an active standby pair scheme.
17063	CREATE INDEX can only refer to empty tables when DDLReplicationLevel > 1	When DDLReplicationLevel is greater than 1, CREATE INDEX is replicated. However, your tables must be empty.
17064	CREATE AS SELECT cannot be used when DDLReplicationLevel > 1	When DDLReplicationLevel is greater than 1, CREATE TABLE is configured for replication. However, CREATE TABLE AS SELECT is not supported.
17065	Action not permitted because DDLReplicationLevel > number and the database is not ACTIVE	DDL action is not permitted because DDLReplicationLevel is greater than 1 and the database is not active.
17066	Create Table not permitted without ADMIN privilege when DDLReplicationLevel > 1 and DDLReplicationAction is INCLUDE	When DDLReplicationLevel is greater than 1 and when DDLReplicationAction is set to INCLUDE, then ADMIN privilege is required when replicating CREATE TABLE statements.
17067	Table table_name was truncated before inclusion in to the ACTIVE STANDBY PAIR replication scheme	When ALTER ACTIVE STANDBY PAIR...INCLUDE is executed, the table contents are truncated on the standby and subscriber(s) databases.
17068	Invalid value (number) for ttDurableWhenAgentStoppedSet. Valid values are 0 and 1.	You specified an invalid value for ttDurableWhenAgentStoppedSet.
17069	Statement is not permitted on the standby or subscribers in an ACTIVE STANDBY PAIR scheme	Type of Message: Error Cause: The CREATE SYNONYM, DROP SYNONYM, GRANT, REVOKE, CREATE USER, ALTER USER, or DROP USER statements are not permitted on the standby database in an active standby pair replication scheme. Impact: TimesTen was unable to perform the operation. User Action: Avoid these statements on the standby or subscribers in an active standby pair replication scheme.
17071	XLA encountered an error during start-up: error_number	Type of Message: Error Cause: The replication agent cannot correctly start the XLA thread because an error was encountered. Impact: The replication agent will periodically try to start the XLA thread until the specified error is fixed. User Action: Diagnose and troubleshoot the specified TimesTen error.
17072	Failed to read Sync CTN Reset value	Type of Message: Error Cause: The state of the transmitter has changed. The active node is invalid, causing the standby node to become the new active node, but the replication agent of the original active node is still running. The original active node switches to a standby state and no new transactions are being issued on the new active node. Impact: If the blocking situation persists, the new standby node can get stuck in a disconnection and reconnection cycle. The threads will attempt to recycle and self-correct the error. User Action: Review the error message for possible fixes.
17073	Restarting subscriber transmitters due to Sync CTN Reset	Type of Message: Informational Cause: The state of the transmitter has changed, but the commit ticket number sync reset value has been properly recycled. Impact: The replication agent is restarting the subscriber transmitter threads. User Action: None.
17075	Read-write lock object not initialized	Type of Message: Warning Cause: A timeout occurred while trying to acquire a read-write lock. Impact: The user error log may contain an additional error message. User Action: Review the user error log for error messages indicating a possible replication agent failure in acquiring a resource. Attempt the fixes for the replication agent failure error messages.
17076	Timeout while retrieving peer information	Type of Message: Warning Cause: A lock could not be acquired before the timeout expired. Impact: Peer information cannot be obtained. The user error log may contain an additional error message. User Action: Review the user error log for error messages indicating a possible replication agent failure in acquiring a resource. Attempt the fixes for the replication agent failure error messages.
17077	DeadLock while retrieving peer information	Type of Message: Warning Cause: A deadlock occurred while trying to acquire a lock. Impact: Peer information cannot be obtained. The user error log may contain an additional error message. User Action: Review the user error log for error messages indicating a possible replication agent failure in acquiring a resource. Attempt the fixes for the replication agent failure error messages.
17078	Mutex abandoned while retrieving peer information	Type of Message: Warning Cause: Mutual exclusion was abandoned while attempting to acquire a lock. Impact: Peer information cannot be obtained. The user error log may contain an additional error message. User Action: Review the user error log for error messages indicating a possible replication agent failure in acquiring a resource. Attempt the fixes for the replication agent failure error messages.
17079	Invalid SQL command at :function_name	Type of Message: Error Cause: The replication agent attempted to execute an invalid SQL command. Impact: The replication agent cannot update the metadata. The replication agent will retry the operation. User Action: None.
17080	Read Only Cache Group cache_group_name must first be excluded from the A/S pair replication scheme before executing this operation.	Type of Message: Error Cause: You attempted to drop a read-only cache group that is part of a replication scheme. Impact: TimesTen cannot drop the read-only cache group. User Action: Exclude the read-only cache group from the replication scheme by using the EXCLUDE parameter of the ALTER ACTIVE STANDBY PAIR SQL statement. Then, retry dropping the read-only cache group. For more information on the ALTER ACTIVE STANDBY PAIR SQL statement, see ALTER ACTIVE STANDBY PAIR in Oracle TimesTen In-Memory Database SQL Reference.
17081	Failover message sent to client connection_info	Type of Message: Informational Cause: An application requested failover support from the replication agent for an active standby pair replication scheme. Once the replication agent determines that the application is connected to a database other than the active master database, the replication agent sends a client failover message to the application. Impact: None. User Action: None. For more information on active standby pair replication schemes, see Active Standby Pair With Read-Only Subscribers in Oracle TimesTen In-Memory Database Replication Guide.
17083	XLA is not permitted with ReplicationApplyOrdering = 2	Type of Message: Error Cause: You attempted to create a XLA bookmark in a replication scheme using automatic replication with disabled commit ordering (ReplicationApplyOrdering=2). Impact: TimesTen cannot perform the operation. User Action: Set the ReplicationApplyOrdering attribute to 0 or 1 and retry the operation. For more information on XLA bookmarks, see About XLA Bookmarks in Oracle TimesTen In-Memory Database C Developer's Guide. For more information on parallel replication and the ReplicationApplyOrdering attribute, see Configuring Parallel Replication in the Oracle TimesTen In-Memory Database Replication Guide and ReplicationApplyOrdering in the Oracle TimesTen In-Memory Database Reference.
17084	Only ACTIVE STANDBY pair replication schemes are permitted with ReplicationApplyOrdering = 2	Type of Message: Error Cause: You attempted to create a replication scheme that is not supported while using automatic replication with disabled commit ordering (ReplicationApplyOrdering=2). Impact: TimesTen cannot perform the operation. User Action: Set the ReplicationApplyOrdering attribute to 0 or 1 and retry the operation. For more information on parallel replication and the ReplicationApplyOrdering attribute, see Configuring Parallel Replication in Oracle TimesTen In-Memory Database Replication Guide and ReplicationApplyOrdering in the Oracle TimesTen In-Memory Database Reference.
17085	No return services are permitted with ReplicationApplyOrdering = 2.	Type of Message: Error Cause: You attempted to create a replication scheme with return services enabled while using automatic replication with disabled commit ordering (ReplicationApplyOrdering=2). Impact: TimesTen cannot perform the operation. User Action: Set the ReplicationApplyOrdering attribute to 0 or 1 and retry the operation. For more information on parallel replication and the ReplicationApplyOrdering attribute, see Configuring Parallel Replication in Oracle TimesTen In-Memory Database Replication Guide and ReplicationApplyOrdering in the Oracle TimesTen In-Memory Database Reference.
17086	ASYNCHRONOUS WRITETHROUGH Cache groups are only permitted with ACTIVE STANDBY PAIR replication schemes.	Type of Message: Error Cause: You attempted to create an asynchronous writethrough (AWT) cache group in a replication scheme that does not support AWT cache groups. Impact: TimesTen cannot perform the operation. User Action: Set an active standby pair replication scheme and retry the operation. For more information on AWT cache groups, see Asynchronous WriteThrough (AWT) Cache Group in Oracle TimesTen In-Memory Database Cache Guide. For more information on active standby pair replication schemes, see Active Standby Pair With Read-Only Subscribers in the Oracle TimesTen In-Memory Database Replication Guide.
17087	CTN Wait Error wait_type	Type of Message: Informational Cause: The replication agent aborted a parallel replication wait. This message is followed by another message that describes the details of the error. Impact: Depending on the cause, the impact may vary. User Action: Review the daemon log for any additional error messages to determine a cause for this error. For more information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
17088	Failed to obtain internal receiver lock	Type of Message: Error Cause: The replication agent failed to obtain the lock on the receiver state structure. Impact: The replication agent receiver will recycle and retry. User Action: None.
17089	All read only cache groups must be part of the Active Standby scheme when using an Oracle Active Data Guard with Asynchronous Transport environment.	Type of Message: Error Cause: You attempted to create an A/S pair replication scheme that did not include read-only cache groups on an Oracle ADG with Asynchronous Transport environment. Impact: TimesTen cannot create the replication scheme. User Action: Create a replication scheme that includes read-only cache groups.
17090	Only read only cache groups can be part of the Active Standby scheme when using an Oracle Active Data Guard with Asynchronous Transport environment.	Type of Message: Error Cause: You attempted to create an A/S pair replication scheme that did not exclude non-read-only cache groups on an Oracle ADG with Asynchronous Transport environment. Impact: TimesTen cannot create the replication scheme. User Action: Create a replication scheme that excludes non-read-only cache groups.
17091	Receipt or commit wait for XID:xcb.counter returned prematurely.	Type of Message: Error Cause: A commit call using RETURN TWOSAFE or RETURN RECEIPT returned before the full return wait time was observed and no notification had been received from the subscriber. Impact: The apply state of the transaction is unknown. User Action: Check that the database has not invalidated. Retry the commit if appropriate.
19000	Open of document document_name failed	The TimesTen Web server 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.
19001	Send of number bytes to browser failed, error error_number	The TimesTen Web server received an error while sending data to the browser. The error referenced in this message provides more details on the problem.
19002	Spawn of CGI script failed, error error_number	The TimesTen Web server received an error while spawning a CGI script. The error referenced in this message provides more details on the problem.
19003	Write of POST data failed	The TimesTen Web server received an error while sending POST parameters to a CGI process.
19004	CGI script script_name not executable	A CGI script requested of the TimesTen Web server is not executable. Check your installation to verify that the script is in the correct location and has the appropriate privileges.
19005	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.
19006	Cannot find perl in path	The TimesTen Web server was unable to find the version of PERL with the product. Check your installation.
19007	Web server system_call failed, error error_number	The TimesTen Web server was unable to get the host name of the client.
19008	Invalid HTTP date from client (string)	A date sent to the TimesTen server is in an invalid format.
19009	Stat of file_name failed, error error_number	The TimesTen Web server was unable to determine file information for an HTTP document.
19010	Web server denying connection from host_name (ip_address)	The TimesTen Web server is denying access from the indicated host. The Web server configuration file can be used to control access.
19011	Authorization failure from file_name	The TimesTen Web server 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.
19012	Cannot open password file file_name	The TimesTen Web server is unable to open its password file. Check your installation.
19013	Bad entry in password file file_name	There is a bad entry in the TimesTen Web server's password file. Correct the entry and try again.
19014	TimesTen web server internal error	The TimesTen Web server has encountered an internal error. See the TimesTen user error log for more information.

Errors 20000-39999

Error number	Error or warning message	Details
20000	Use of a deprecated feature: feature_details	This warning indicates use of a feature that is being supported only for backward compatibility. The feature may be removed in a future release. The feature_details text indicates the feature being used and suggests the appropriate course of action.
20001	feature_type: feature_details has been removed and cannot be used.	Type of Message: Error Cause: You attempted to use a feature that is no longer supported. Impact: TimesTen cannot perform the operation. User Action: None.
20100	This connection required recovery due to an improper shutdown	When a connection is made after an improper shutdown, a recovery process replays the logs to restore the database to its most current state. This recovery process can be time-consuming. To avoid it, cleanly disconnect from the database when possible. For example, do not exit from a TimesTen application without first waiting for all connections to disconnect. Use signal handlers to catch signals that set a variable indicating that all connections must disconnect.
20101	Data loss because redo logging was disabled. Connect with ttAdmin -ramLoad -force.	Type of Message: Error Cause: The connection attempt failed because an irrecoverable error occurred while redo logging was disabled. Impact: Any changes made to the database while redo logging was disabled have been lost. User Action: To permit new connections, explicitly load the database into memory. Load the database into memory using ttAdmin -ramLoad -force. For more information, see ttAdmin in Oracle TimesTen In-Memory Database Reference.
30103	SQLParamOptions is not supported with result-set returning statements	An attempt was made to execute a SELECT statement using an array of parameters as indicated by SQLParamOptions. Batch execution using arrays of parameters is supported only with INSERT, UPDATE and CREATE VIEW statements.
30104	SQLBindParameter must be called because the ConnectionCharacterSet attribute was changed	Type of Message: Error Cause: The ConnectionCharacterSet value was changed after the parameters were bound to the statement. Impact: If execution continues, incorrect data could be passed in the parameter values due to character set mismatch. User Action: To allow correct character set conversion, rebind the statement parameters using the SQLBindParameter function. For more information, see SQLBindParameter Function in Oracle TimesTen In-Memory Database C Developer's Guide.
30105	Transaction must roll back	Type of Message: Error Cause: A TimesTen client server failover to the new active (original standby node) occurred. Impact: The current transaction must be rolled back or committed before further operations can be done. User Action: Call ROLLBACK on the current connection handle with the SQLTransact call. For more information, see Committing Changes to the Database in ODBC in Oracle TimesTen In-Memory Database C Developer's Guide.
30106	Transaction status unknown	Type of Message: Error Cause: The current transaction cannot be committed for unknown reasons. Impact: The current transaction is assumed to have rolled back and that the operations from the transaction are lost. User Action: Open a new transaction to complete new operations.
30107	ECONNRESET: The connection has been broken during a network send or read operation. Probably the server exited unexpectedly.	Type of Message: Error Cause: Client connection to server lost. Impact: The current connection is lost. The transaction is assumed to have rolled back and that the operations from the transaction are lost. User Action: Open a new transaction to complete new operations.
30108	This operation has Timed Out.	Type of Message: Error Cause: Client network operation timed out. Impact: The current connection is lost. The transaction is assumed to have rolled back and that the operations from the transaction are lost. User Action: Try increasing your ODBC timeout attribute.
30200	Unable to allocate memory	Type of Message: Error Cause: The TimesTen driver manager was unable to allocate memory. Impact: TimesTen did not perform the operation. User Action: Determine why there was no available memory and resolve the situation.
30201	Unable to load TimesTen native driver	Type of Message: Error Cause: The TimesTen driver manager was unable to load a required TimesTen native driver. Impact: TimesTen did not perform the operation. User Action: Check your TimesTen instance type and the environment of the application (LD_LIBRARY_PATH).
30202	Handle is currently connected	Type of Message: Error Cause: The SQLFreeConnect or SQLFreeHandle operation failed because the handle is currently in a connected state. Impact: The handle is not freed. User Action: Ensure that you disconnect the handle (SQLDisconnect function) before trying to free it.
30203	Invalid argument	Type of Message: Error Cause: The application passed an invalid argument to a TimesTen driver manager function. Impact: The requested operation was not performed. User Action: Fix the application code and retry the operation.
30204	Function not supported by this version of TimesTen	Type of Message: Error Cause: The application called a function that is not supported by this version of TimesTen. Impact: The requested operation was not performed. User Action: Fix the application code or use an appropriate version of TimesTen.

Errors 40000-49999

Error number	Error or warning message	Details
40005	sbHttpListParse returned NULL	Internal error. Daemon cannot honor a request from the cache agent. The reply message cannot be parsed. Contact TimesTen Customer Support.
40006	Could not connect to TimesTen. Cache timer thread exit.	The cache agent cannot connect to TimesTen. The timer thread used by cache aging is exiting. Review the connection settings and restart the cache agent to begin aging.
40007	Could not connect to TimesTen. Cache aging thread exit.	The cache agent cannot connect to TimesTen. The timer thread used by cache aging is exiting. Review the connection settings and restart the cache agent to begin aging.
40008	Could not do aging, Cache aging thread will try to reconnect in 1 minute.	The cache aging operation was unable to complete, the cache agent disconnects and then reconnects and retries in one minute. If the problem does not resolve itself after several retries, review the user error log to find the cause of the aging failure.
40009	Error reading from deadman socket	The cache agent failed to read from the daemon socket. Cache agent is shutting down. If the cache agent does not restart automatically, restart it manually. If that does not work, then restart the main TimesTen daemon and then restart the cache agent manually if the cache agent policy requires it to be restarted manually.
40010	Data read, fatal internal error	Internal error. The cache agent failed to read from the daemon socket. Cache agent is shutting down. If the cache agent does not restart automatically, restart it manually. If that does not work, then restart the main TimesTen daemon and then restart the cache agent manually if the cache agent policy requires it to be restarted manually.
40011	Cache agent exiting, main daemon gone	The cache agent detected that the TimesTen daemon is down. The cache agent is shutting down. To continue, restart the main TimesTen daemon. Then, restart the cache agent, if it does not restart automatically.
40012	Error number setting synchronous sockets	The cache agent cannot set a synchronous socket during startup. The operating system error code is displayed in the message. Remove the cause of OS error and restart the cache agent.
40013	Connect fail from connectToDaemon port port_number id cache_agent_id. Error: error_number - error_message	Type of Message: Error Cause: The cache agent failed to connect to the TimesTen daemon at the specified port number. Impact: The cache agent did not start. User Action: Check the status of the main TimesTen daemon and review the included error message to determine the cause of the failure.
40015	Could not initialize connection to daemon	The cache agent cannot initialize the connection to daemon at startup. The cache agent is shutting down. The TimesTen daemon may have died unexpectedly. Check the status of the main TimesTen daemon.
40016	Daemon did not accept port setting. Message: message, Error Code: number	Internal error. Daemon did not accept cache agent port setting. The details are included in this message.
40017	Daemon did not accept port setting. Return code: number, Request Return code: number	Internal error. Daemon did not accept cache agent port setting. The details are included in this message.
40018	TimesTen error code:error_number, msg error_message	The cache agent has generated a Native TimesTen error. For more information see the description for that error in this chapter.
40019	Unable to allocate an ODBC environment handle	The cache agent failed to allocate an ODBC environment handle. Refer to ODBC documentation to find the cause of failure.
40021	Could not create an event object, agent will be restarted	The cache agent cannot create an object that is used internally at startup. There may be insufficient memory or other a shortage of another system resource to initialize a condition variable. Stop the cache agent, free up the resources and restart the cache agent.
40022	Could not create thread_name thread, agent will be restarted	The cache agent could not create the indicated thread. This may be caused by a lack of system resources to create another thread or the system limit on the total number of threads in a process may have been exceeded. Stop the agent, free up resources or adjust the system limit and restart the cache agent.
40026	Could not initialize internal structure for scheduler, agent will be restarted	The cache agent could not initialize an internal structure for the scheduler. The cache agent is restarting automatically. This message usually follows another message that describes the details about the failure.
40030	Cache agent has exceeded the maximum TimesTen connection limit of number	The cache agent has too many connections to TimesTen. This is often caused by a lot of autorefresh attempts. Alter the autorefresh intervals on your cache groups to be less frequent and so that they are similar on most of your cache groups.
40031	Connect failed (message)	The cache agent failed to connect either to the TimesTen main daemon or to the Oracle database. The message included in this error may give more details. In addition, this message usually follows another message that describes the details about the failure.
40034	Last number autorefreshes failed for cache groups with interval number ms. Autorefresh will be retried silently	The latest indicated number of have failed. The autorefresh operation is retried without writing new messages to the user error log. This message usually follows another message that describes the details about the failure.
40035	Autorefresh number number failed for cache groups with interval number ms after number retries.	An autorefresh for the indicated interval has failed. This message usually follows another message that describes the details about the failure. The autorefresh operation is being retried automatically.
40036	Create/alter cache group failed because autorefresh for cache group cache_group_name is in the middle of shutting down	CREATE CACHE GROUP and ALTER CACHE GROUP statements cannot be processed while the cache agent is shutting down the autorefresh thread for the cache group. Wait for the thread to finish shutting down and retry your DDL operation.
40037	Could not allocate a new cache group structure. Scheduler thread exiting	The cache agent failed to allocate a new cache group structure. This may happen in response to CREATE CACHE GROUP or ALTER CACHE GROUP operation when there is a lack of memory or other system resource. One of the service threads (scheduler) is shutting down and autorefresh for all cache groups is stopped. Make the resource available and restart the cache agent.
40038	Could not allocate a new refresher structure. Scheduler thread exiting	The cache agent failed to allocate a new refresh structure. Cache agent fails to allocate a new refresh structure. This may happen in response to CREATE CACHE GROUP or ALTER CACHE GROUP operation when there is a lack of memory or other system resource. One of the service threads (scheduler) is shutting down and autorefresh for all cache groups is stopped. Make the resource available and restart the cache agent.
40042	Join of refresher-thread_name failed	A thread join with a refresher thread failed during cache agent shutdown.
40043	ODBC error from API call: api_name	The specified ODBC call failed. Refer to the ODBC documentation for details.
40044	No data source or driver specified; dialog prohibited. Check the DSN definition in the ODBC system administrator. The DSN must be a system DSN.	This error only occurs on Windows systems. The cache agent could not connect to the TimesTen database because the data source or driver was not specified. Check the system DSN settings for this database.
40045	No data source or driver specified; dialog prohibited. Check the DSN definition in the sys.odbc.ini file. The DSN must be a system DSN.	This error only occurs on Linux or UNIX systems. The cache agent could not connect to the TimesTen database because the data source or driver was not specified. Check the system DSN settings for this database.
40046	Error: message, ODBC SQL state = sql_state, Additional Warning = number	The specified ODBC call failed with the indicated details.
40047	Call to SQLError failed with SQL_SUCCESS_WITH_INFO. Need to increase size of message buffer.	Internal Error, the cache agent's internal error buffer is too small for SQLError ODBC API call. Contact TimesTen Customer Support.
40048	Call to SQLError failed with SQL_INVALID_HANDLE.	Internal Error, the ODBC statement, connection, or environment handle passed to SQLError was invalid. Contact TimesTen Customer Support.
40049	Call to SQLError failed with SQL_ERROR.	Internal error, the call to SQLError fails to get more diagnostic information after a failed ODBC operation. Contact TimesTen Customer Support.
40050	Detected invalid database.	TimesTen database has been invalidated, Cache agent shuts down, then restarts. Try the operation again.
40051	Cannot attach to Oracle Server (Oracle error ORA-number). OracleNetServiceName = service_name, ORACLE_HOME = path	The cache agent cannot connect to the Oracle database. The Oracle database error code is included in the message. Refer to Unable to resolve Oracle Service Name and Unable to validate the Oracle database user name and password in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40052	Cannot start an Oracle session (Oracle error ORA-error_number). uid = user_name, pwd is hidden, TNS_ADMIN = \"path\", ORACLE_HOME= \"path\"	Cannot start an Oracle database session. The Oracle database error code and the intended user name are included in the message. The password is hidden for security reasons. Refer to Unable to resolve Oracle Service Name and Unable to validate the Oracle database user name and password in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40053	OCIEnvCreate failed. Return code code_number	Calling OCIEnvCreate fails. The return code is included in the message. Verify the Oracle database client installation. Refer to Unable to resolve Oracle Service Name and Unable to validate the Oracle database user name and password in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40054	Could not login to Oracle. TNS timeout occurred.	Received a TNS timeout error while trying to login to the Oracle database. Check the Oracle database client/server setting and the network health. If the problem does not get fixed after an automatic restart, check the connection and restart cache agent. Refer to Unable to resolve Oracle Service Name and Unable to validate the Oracle database user name and password in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40055	Delete query too long during unload.	The system generated a query overflow in the system buffer, while executing an unload statement. This is usually caused by very a long WHERE clause in the UNLOAD CACHE GROUP statement, a large number of tables in the cache group, or very long WHERE clause in the cache group definition.
40056	Not connected to Oracle during load	Internal error. A connection to the Oracle database was not established before the loading operation. Contact TimesTen Customer Support.
40057	Table name too long: table_name.	Internal error. The table name is too long. A table name cannot exceed 30 characters.
40058	Select query too long during load.	While executing a load statement, the system generated SELECT query overflowed a system buffer. This is usually caused by a very long WHERE clause in the LOAD statement, a large number of tables in the cache group, or very long WHERE clause in the cache group definition.
40059	Select list too long during load.	While executing a load statement, the system generated SELECT query overflowed a system buffer. This is usually caused by a very long WHERE clause in the LOAD statement, a large number of tables in the cache group, or very long WHERE clause in the cache group definition.
40060	Error preparing Oracle statement: statement	There was an error while preparing the specified SQL statement on the Oracle database.
40061	Error executing Oracle statement: statement	There was an error while executing the specified SQL statement on the Oracle database.
40062	Column count does not match for cached table	The Oracle database table columns do not match the cached table columns. Check to determine if the Oracle database table schema has been changed since the cache group was created.
40064	Rowid descriptor alloc failure	The call to OCIDescriptorAlloc failed.
40066	Internal buffer overflow during autorefresh initialization	Autorefresh initialization failed because an internal buffer has overflowed. The required buffer size is proportional to the number of tables in the cache group, the number of columns, the number of columns in the primary key or foreign key, and the length of the WHERE clause of the cache group.
40067	Errors encountered during restarting autorefresh	Failed to restart autorefresh for some cache groups during cache agent startup. This message usually follows another message that describes the details about the failure.
40068	Failed to prepare the TimesTen SQL statement: statement	The cache agent encountered an error while preparing a TimesTen SQL statement. This message usually follows another message that describes the details about the failure.
40069	Failed to retrieve from Oracle change log. query = query, curSOLog=bookmark	The cache agent failed to retrieve rows from the Oracle database change log for autorefresh. The failing query and the current log content are specified in this message. Ensure that the Oracle database table objects for autorefresh have not been removed and the autorefresh user has not been changed since the creation of the cache group.
40070	Timeout while dropping an Oracle table. The query is query	A timeout occurred while dropping an Oracle database table. The optional failed query is specified in the message. This may occur in response to either a ALTER CACHE GROUP or a DROP CACHE GROUP operation when the table is busy. The drop is retried when the cache agent gets restarted. If necessary, restart the cache agent to drop the table immediately.
40071	Table is not found in Oracle: owner_name.table_name	The specified table cannot be found in the Oracle database.
40072	Failed in checkAutorefreshConnections, bad argument	Internal error. The autorefresh connection is bad. Contact TimesTen Customer Support.
40073	Could not drop the Oracle objects. Either an autorefresher uid was not provided or the uid was invalid.	Failed to drop Oracle database objects for autorefresh because either the cache administration user ID was not given or the UID was incorrect. Ensure that the cache administration user ID provided at cache agent startup time is correct.
40076	Failed calling OCI function: function_name	The cache agent failed while calling the specified OCI API function. This message is usually followed by another message that describes the details about the failure.
40077	Oracle native error code = error_code, msg = message	The cache agent encountered a native Oracle database error while calling an OCI function. The details are included in this message.
40078	Assertion failed: message	Internal error. A cache agent internal consistency check failed. Contact TimesTen Customer Support.
40079	Failed to malloc size memory_size. Please free system resources.	Failed to malloc memory of the indicated size.
40081	Failed to get Oracle username and password: error_number	Failed to get the Oracle database user name and password, the details are included in this message.This may happen during the cache agent startup. This message usually follows another message which describes the details about the failure. The cache agent gets automatically restarted when this error occurs.
40083	Cache agent startup command line value missing for flag flag	Internal error. The main TimesTen daemon started the cache agent with missing values for the indicated flag. Contact TimesTen Customer Support.
40084	Cache agent startup command line flag flag has incorrect value value	Internal error. The main TimesTen daemon started the cache agent with incorrect values for the specified flag. Contact TimesTen Customer Support.
40086	Could not allocate Oracle statement handle	Error allocating Oracle database statement handle. Contact TimesTen Customer Support.
40087	Could not allocate TimesTen statement handle	Error allocating a TimesTen statement handle. Contact TimesTen Customer Support.
40088	Log reader " TTC_FT_OBJECT_PREFIX "getMinSCN returned OCI_NO_DATA	Internal error. getMinSCN should have returned at least one row, but was unable to do so. Contact TimesTen Customer Support.
40089	Log reader getLmLock returned OCI_NO_DATA	Internal error. getLmLock should have returned at least one row, but was unable to do so. Contact TimesTen Customer Support.
40090	Log reader getLmUserCount returned OCI_NO_DATA	Internal error. getLmUserCount should have returned at least one row, but was unable to do so.Contact TimesTen Customer Support.
40091	Log reader getLmUserCount returned OCI_NO_DATA	Internal error. getLogLimit should have returned at least one row, but was unable to do so. Contact TimesTen Customer Support.
40092	Oracle type type not supported	Internal error. Oracle database type for the primary key is not supported. Contact TimesTen Customer Support.
40093	Could not parse redo SQL cscn:cscn_name, SQL: statement	Internal error. Parsing of redo SQL statement failed. Contact TimesTen Customer Support.
40094	Unable to get primary key metadata for base table table_name, log table table_name	Internal error. Unable to get metadata for primary keys for the indicated base and log tables. Contact TimesTen Customer Support.
40096	Log reader initialization failed	Log reader allocation failed. Contact TimesTen Customer Support.
40108	Could not derive the database file name. DataStore path = path	Internal Error. TimesTen could not derive the database name from the provided database input parameter to cache agent. Contact TimesTen Customer Support.
40114	Connection to Oracle has not succeeded for last number minutes. Number of failed attempts: number. Initiating cache agent restart.	At cache agent startup time, the cache agent cannot connect to the Oracle database. A CREATE CACHE GROUP or an ALTER CACHE GROUP statement can encounter this error because the operation was attempted too soon after the cache agent was started or because the cache agent was unable to establish a connect to the Oracle database. Messages in the user error log may provide details on the connection failures. If the problem does not resolve itself after several attempts, manually restart the cache agent. For more details see Unable to resolve Oracle Service Name and Unable to validate the Oracle database user name and password in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40115	No cache groups will be autorefreshed until a connect to Oracle can be established. Will try to connect to Oracle silently every number seconds. Additional error information:message.	At cache agent startup time, the cache agent cannot connect to the Oracle database. The cache agent keeps trying to connect to the Oracle database.
40116	Fatal error occurred while trying to connect to Oracle. Check the Oracle Id, UID, PWD & the status of Oracle instance. No autorefreshing will occur until the problem is resolved and cache agent has be restarted.	At cache agent startup time, the cache agent cannot connect to the Oracle database. The cache agent automatically shuts down and restarts. If the problem does not get fixed after this automatic restart, you should stop the cache agent, check the OracleID, UID, PWD, and the status of the Oracle database instance and restart cache agent.
40117	AUTOREFRESH LOGSEQ ERROR: LogSeq(number) = error_number considered not valid. It will not be stored in the database.	Internal Error. TimesTen saw an invalid bookmark when trying to store the log sequence into TimesTen. The autorefresh cannot move forward. It resumes from the last valid LogSeq number.
40119	An error occurred while preparing or executing the following Oracle SQL statement: statement	This message usually follows another message that describes the details about the failure.
40120	Autorefresh has not succeeded for cachegroups with interval number ms for last number minutes. Number of failed attempts: number. Initiating cache agent restart.	Autorefresh for the specified interval has failed in the indicated minutes, after the indicated number of attempts. The cache agent is restarting.
40121	Auto-Refresh failed (Could not turn on table locking)	Table-level locking could not be turned on for this autorefresh transaction. This autorefresh is being terminated and retried.
40122	Could not parse full name, cache_group_name, in owner and name.	TimesTen was unable to parse the cache group name during the autorefresh object validation for the specified cache group. Contact TimesTen Customer Support.
40123	Autorefresh trigger trigger_name is not enabled for table table_name. The cache group cache_group_name in database database_name will not be refreshed.	Autorefresh Oracle database object validation for cache groups finds that the Oracle database trigger trigger_name on the indicated table is not enabled. Autorefresh cannot work for the table. Either ALTER the AUTOREFRESH state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40124	Could not find autorefresh trigger trigger_name. The cache group owner_name.cache_group_name in database database_name will not be refreshed.	Autorefresh Oracle database object validation for cache groups finds that the Oracle database trigger trigger_name on the indicated table of the cache group was not found on the Oracle database. Autorefresh cannot work for the cache group. Either alter the AUTOREFRESH state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40125	Could not find the Oracle autorefresh object_type object_name for table table_name. The cache group cache_group_name cannot be refreshed in any database.	A table in the cache group cache_group_name did not find the autorefresh object on the Oracle database. Autorefresh cannot work for the cache group. Either alter the Autorefresh state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40126	Autorefresh object_type object_name for table table_name is not valid on Oracle. The cache group cache_group_name will not be refreshed.	Autorefresh Oracle database object validation for a cache group table found an invalid status for an autorefresh object on the Oracle database. Autorefresh cannot work for the cache group. Either alter the Autorefresh state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40127	Internal error: could not compute the difference of two dates.	Autorefresh object validation could not complete because of this error.
40128	Oracle object id is different - Oracle table table_name has been recreated since the cache group cache_group_name in database database_name was created. The cache group will not be refreshed	Autorefresh object validation for the cache group found an incompatibility between the cache group objectID and the objectID on the Oracle database. This could have been caused when a table was created on the Oracle database after the cache group was created. Autorefresh cannot work for the cache group. Either alter the Autorefresh state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40129	Oracle create date changed - Oracle table table_name has been recreated since the cache group cache_group_name in database database_name was created. The cache group will not be refreshed	Autorefresh object validation for the cache group found an incompatibility between the create date for the specified table in a TimesTen database and that on the Oracle database. This could have been caused when a table was created on the Oracle database after the cache group was created. Autorefresh cannot work for the cache group. Either alter the Autorefresh state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40130	AutoRefresh log table is older than base table - Oracle table table_name has been recreated since the cache group cache_group_name in database database_name was created. The cache group will not be refreshed	The error occurs when autorefreshing Oracle database object validation for the cache group. A change log table for table table_name is older than the table itself. This could have been caused when a table was created on the Oracle database after the cache group was created. Autorefresh cannot work for the cache group. Either alter the autorefresh state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40131	Could not parse table names for cache group owner_name.cache_group_name.	Internal Error. The cache agent was unable to parse the tables names during the autorefresh object validation for the specified cache group. Autorefresh object validation could not complete because of this error.
40132	Could not find user count row for table table_name in cache_group_name. Any autorefreshed cache group containing table table_name will not be refreshed.	An autorefresh validation check could not find the Oracle database user count row for the indicated table in user_count_table_name. Any autorefresh cache group containing the specified table is not refreshed. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40133	The user count in the user count table table_name for table table_name in cache group owner_name.cache_group_name is NULL. The cache group may not be refreshed.	An autorefresh validation check found user count to be NULL in the in the user_count_table_name for the specified cache group table. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40134	The user count for table table_name in cache group owner_name.cache_group_name is less than 0.	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40135	The user count for table table_name in cache group owner_name.cache_group_name is equal to 0.	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40136	The log sequence number in the user count table table_name for table table_name in cache group owner_name.cache_group_name is NULL. The cache group may not be refreshed.	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40137	The log sequence number in the user count table table_name for table table_name in cache group cache_group_name is not equal to the largest logseq in the autorefresh log table table_name. The cache group may not be refreshed for all databases.	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40138	The previous log sequence number is greater than the recorded refresh bookmark for table table_name in cache group cache_group_name in database owner_name. database_name	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40139	The user count table table_name on Oracle instance instance_name was not found. The autorefresh will not work for all database for this instance.	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40140	The sequence number for table table_name had changed but the table was not refreshed. cache_group_name cache group in database database_name is out of sync.	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40141	The sequence number for table owner_name.table_name had changed but the table was not refreshed. The cache group in database database_name is out of sync.	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40143	Could not find table table_name for cache group cache_group_name in Oracle. User user_name may not have privileges. The cache group will not be refreshed.	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40144	Table owner_name.table_name in cache group owner_name.cache_group_name is not valid on Oracle. The cache group will not be refreshed.	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40145	An internal autorefresh structure has not been initialized. Cache group cache_group_name in database database_name will not be refreshed.	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40146	An internal autorefresh structure has not been initialized.	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40147	The id for cache group cache_group_name in database database_name is invalid.	A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40148	Could not generate hash of host and database name	Internal error. A bi-propagated cache group operation failed to generate a hash of host and database name. Contact TimesTen Customer Support.
40149	Was not able to initialize an internal autorefresh structure. The refresher will try to reinitialize the structure later.	The cache agent failed to initialize an internal data structure used by autorefresh. This message usually follows another message that describes the details about the failure. TimesTen is retrying the initialization.
40157	OCIHandleFree() failed.	Check the health of the Oracle database connection.
40158	sb_dbSetSessionAuthorization() failed. uid user_id.	Internal error. The cache agent failed to set the user ID of the session. Contact TimesTen Customer Support.
40159	Could not initialize OCI function pointers. Error: message	This is a cache agent initialization error. The OCI functions cannot be set up to be used with the cache agent. The specific error is included in the message and may provide a suggestion to solve the problem. Check both the Oracle database and TimesTen installations. On Linux or UNIX systems, ensure that the ORACLE_HOME environment variable is set correctly.
40160	Clean up of autorefresh Oracle objects failed. snprintf returned value with buffer length number.	This is an internal error that occurred during clean up of autorefresh Oracle database objects. Contact TimesTen Customer Support.
40162	ODBC call failed with SQL_INVALID_HANDLE	This is an internal error indicating that an ODBC handle used by the cache agent is invalid. Contact TimesTen Customer Support.
40163	OCI call failed with OCI_INVALID_HANDLE	This is an internal error indicating that an ODBC handle used by the cache agent is invalid. Contact TimesTen Customer Support.
40164	OCIErrorGet failed with OCI_INVALID_HANDLE	This is an internal error. The OCIErrorGet call failed to get more diagnostic information after an OCI call failed. The OCI handle is invalid. Contact TimesTen Customer Support.
40165	Unique constraint is violated while loading: error_message	Type of Message: Error Cause: The unique constraint has been violated in TimesTen during a LOAD CACHE GROUP, MERGE or AUTOREFRESH operation on the indicated table. Impact: The update to the TimesTen database may fail. User Action: Unload the cache group and then reload it. For more information, see Unloading a Cache Group in Oracle TimesTen In-Memory Database Cache Guide. If the error still occurs, contact TimesTen Customer Support.
40166	Required table table_name does not exist on Oracle	Autorefresh Oracle database object validation detected that the indicated table does not exist. The log table garbage collector cannot work. To recreate the tables, recreate the autorefresh cache group. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40167	owner_name.table_name table on Oracle does not have required lock rows	Autorefresh Oracle database object validation detected that the indicated table does not exist. The log table garbage collector cannot work. To recreate the rows, recreate the autorefresh cache group. For details on fixing this problem, refer to the Validate autorefresh for the Oracle database objects section in the Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
40168	There might be problems during autorefresh operation of cache group cache_group_name because owner_name.table_name table on Oracle does not have required rows. Row Search Criteria:search_criteria	Type of Message: Error Cause: The autorefresh Oracle database object validation detected that the indicated table does not have the required rows. The most likely cause for this error is a hash collision while inserting the required rows into the table. Impact: Incremental refresh may run into issues like performing a full refresh on a incremental cache group. User Action: Either, change the location specified in the DataStore connection attribute, which requires destroying and re-creating the TimesTen database, or use a different cache administration user for the cache group operations. For more information on how to change the cache administration user, see Changing Cache User Names and Passwords in Oracle TimesTen In-Memory Database Cache Guide.
40169	Can't initialize bookmark reporter	The Cache agent failed to initialize a new data structure used by the bookmark reporter. This may happen in response to a CREATE CACHE GROUP or ALTER CACHE GROUP statement due to a lack of memory or other system resource. The operation cannot continue successfully. Free up the necessary resources and reissue the DDL statement.
40173	Can't initialize log table marker	The Cache agent failed to initialize a new data structure used by the log table marker. This may happen in response to a CREATE CACHE GROUP or ALTER CACHE GROUP statement due a lack of memory or other system resource. The operation cannot continue successfully. Free up the necessary resources and reissue the DDL statement.
40175	Failover stopped. Failover will not take place.	The cache agent detected an Oracle database OCI_FO_ABORT failover event. The failover was unsuccessful. If the cache agent does not restart automatically, restart it manually.
40176	Bad Failover Event: number.	Internal error. The cache agent does not recognize the Oracle database failover event. Contact TimesTen Customer Support.
40177	Could not re-establish a connection in number minutes. Failover will not take place.	The connection to one of the Oracle RAC nodes failed and the cache agent could not failover to another Oracle RAC node. It timed out and the failover was unable to continue. If the cache agent does not restart automatically, restart it manually.
40178	Failed to register failover callback for server handle number.	The cache agent failed to register the Oracle RAC failover callback function. No action is needed if the application is not running against an Oracle RAC server. If you are running against an Oracle RAC server, verify that the OCI client is the latest 9i or 10g client and that TAF is enabled.
40179	OCIHandleAlloc() failed.	The cache agent may have run out of memory or another system resource. Contact TimesTen Customer Support if the problem persists.
40180	Unexpected row count. Expecting number. Got number.	Oracle database objects required for autorefresh operations could not be uninstalled because a DDL lock could not be acquired. Restart the cache agent. If the error persists, contact TimesTen Customer Support.
40181	Object_name could not be found on Oracle. Check that user_name has privilege_name on object_name	The Oracle database object could not be found. Verify that the specified Oracle database user has the correct privileges on the object.
40182	Timestamp descriptor alloc failure	The call to OCIDescriptorAlloc failed.
40183	Could not retrieve aging lifetime for cache group with cgID number	Internal error. The cache agent could not retrieve the aging lifetime for cache group from the TimesTen database. This message usually follows another message that describes the details about the failure. Load/refresh cache group fails.
40185	Can't initialize marker structure for autorefresh thread	The cache agent failed to initialize a new data structure used by the log table marker for the autorefresh thread.
40186	Can't initialize tablespace full alert writer structure	The cache agent failed to initialize a new data structure used by tablespace full alert writer.
40187	Can't initialize tablespace full alerter structure	The cache agent failed to initialize a new data structure used by tablespace full alerter.
40188	No cache groups will be autorefreshed since the database is marked 'not alive' and the recovery method is 'none'.	The database is dead and cannot be refreshed.
40189	Failure_msg_Optional_msg Cache Agent for database database_name will be restarted.	Type of Message: Error Cause: Failure_msg is a message that details the type of failure and where the failure occurred. Optional_msg is an optional error message that further describes the problem. Impact: TimesTen attempts to restart the Cache Agent for the database. User Action: None.
40190	Failure_msg_Optional_msg Cache Agent for database database_name cannot be started.	Type of Message: Error Cause: Failure_msg is a message that details the type of failure and where the failure occurred. Optional_msg is an optional error message that further describes the problem. Impact: The cache agent for the database cannot be started. User Action: Fix the problem described by failure_msg and optional_msg before the cache agent for the database can be started.
40191	Can't retrieve log space statistics from the user_count table	Type of Message: Error Cause: The schema of the TT_version_USER_COUNT table is incorrect. Impact: The cache agent cannot retrieve log space monitoring statistics. User Action: Contact TimesTen Customer Support.
40192	Could not find entry for table table_name (object_id) in string. Log space monitoring will not be performed.	Type of Message: Error Cause: The cache agent cannot find any information about the specified cached table in the TT_STRING_LOG_SPACE_STATS table. Impact: The cache agent cannot perform log Space monitoring for objects related to the specified cached table. User Action: Contact TimesTen Customer Support.
40193	The log space stats table string on Oracle database instance instance_name was not found. Log space monitoring will not be performed.	Type of Message: Error Cause: The cache agent cannot find the TT_STRING_LOG_SPACE_STATS table in the Oracle database. Impact: The cache agent cannot perform log Space monitoring. User Action: Contact TimesTen Customer Support.
44000	Warning: Statement statement	The TimesTen ODBC driver returns the SQL warning included in the message.
44001	Warning: warning_message, ODBC SQL state = state, Additional Warning = warning_message	The TimesTen ODBC driver returns the SQL warning included in the message.
44002	Table loading warning summary: number data truncations	This message reports the number of data truncations that occurred during a LOAD CACHE GROUP statement.
44003	Table loading warning: Data truncated for table table_name, row number, column number	Warning: A data truncation occurred at the specified row and column while loading the specified table.
44004	OCIDescriptorFree : RowId descriptor was not freed. i=number, error=error_number	Internal warning, the OCIDescriptorFree call did not succeed for specified row with the OCI error code that is included in this message.
44005	Table loading warning summary: number column values truncated	The specified number of column values were truncated during a LOAD CACHE GROUP statement.
44007	Table refresh warning: Data truncated for table table_name, row number, column number	The specified number of data truncations occurred for the specified table, row and column.
44009	Warning: Oracle object cleanup failed.	The cache agent may not have cleaned up all the Oracle database objects. If necessary, clean up the objects manually.
44010	Warning: cmd: command_string	The cache agent encountered an OCI warning while processing the specified command.
44011	Oracle warning i = warning_number: warning_message	The cache agent encountered one or more warning(s) while executing an OCI call. The details are included in this message.
44017	A full autorefresh will be performed for Incremental autorefresh table table_name.owner_name because change log table table_name on Oracle has been truncated	The specified table must be fully refreshed because log table was truncated. For details on fixing this problem, see Incremental autorefresh becomes full autorefresh in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
44022	The cache agent has not been able to established a connection to Oracle. No cache groups will be refreshed until a connection is made. Please check the status of the Oracle instance.	The cache agent encountered this error after either a CREATE CACHE GROUP or ALTER CACHE GROUP statement because the operation came too soon after the cache agent started or the cache agent could not establish a connection to the Oracle database. Other error messages in the user error log may provide details on connection failures. Resolve the connection problem manually if does not resolve after several retries, and restart the cache agent. Refer to the Unable to resolve Oracle Service Name and Unable to validate the Oracle database user name and password in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
44023	Cache agent was successfully able to connect to Oracle after number failed attempts	The cache agent was initially having trouble connecting to the Oracle database but it succeeded after the indicated number of retries.
44024	Could not find the object id for table owner_name.table_name in the autorefresh structure. The cache agent may be lagging behind.	This is a warning message.
44025	Could not find the cache group owner_name.cache_group_name in database database_name. The cache agent may be lagging behind. The cache group will not be validated.	This is a warning message.
44026	The autorefresh mode for cache group owner_name.cache_group_name in database database_name is different from refresher. The cache agent is lagging behind.	This is a warning message.
44027	The autorefresh state for cache group owner_name.cache_group_name in database database_name is different from refresher. The cache agent is lagging behind.	This is a warning message.
44028	Cache group cache_group_name in database database_name has number tables yet the refresher has number tables.	Internal error. Contact TimesTen Customer Support.
44029	Cache group cache_group_name in database database_name has table table_name yet the refresher has table table_name	Internal error. Contact TimesTen Customer Support.
44030	Autorefresh log table table_name is empty. The autorefresher will perform a full refresh on all databases in order to recovery.	For details on fixing this problem, see Incremental autorefresh becomes full autorefresh in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
44031	The log sequence number has changed but the table table_name in cache group owner_name.cache_group_name was not refreshed. Will check if it is refreshed during the next validation cycle.	For details on fixing this problem, see Incremental autorefresh becomes full autorefresh in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
44032	The current log sequence number is greater than the recorded bookmark for the table table_name in cache group owner_name.cache_group_name in database database_name. The table should have been refreshed but was not. Will check if it is refreshed during the next validation cycle.	For details on fixing this problem, see Incremental autorefresh becomes full autorefresh in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
44033	The cache agent for database database_name shows that the cache group owner_name.cache_group_name is an incremental autorefresh cache group yet the system table shows that it is not. The cache agent may be lagging behind.	This error could occur after the mode was altered from INCREMENTAL to FULL. Contact TimesTen Customer Support if the problem does not fix itself by the next validation cycle.
44034	The cache agent indicates that cache group cache_group_name is active, incrementally refreshed and has interval numberms for database database_name. But the TimesTen system tables indicate that the cache group should not be incrementally refresh in this interval. The cache agent may be lagging behind.	This error could occur after an ALTER CACHE GROUP operation.Contact TimesTen Customer Support if the problem does not fix itself by the next validation cycle.
44035	The TimesTen system tables indicate that cache group owner_name.cache_group_name is active, incrementally refreshed and has interval numberms for database database_name. But the cache agent is not currently incrementally refreshing it in this interval. The cache agent may be lagging behind.	This error could occur after an ALTER CACHE GROUP operation.Contact TimesTen Customer Support if the problem does not fix itself by the next validation cycle.
44036	The log table table_name has been truncated and will result in a full refresh of the table table_name in database database_name.	For details on fixing this problem, see Incremental autorefresh becomes full autorefresh in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
44037	The table table_name on database database_name is currently out of sync with Oracle. The bookmark for the table is bookmark_name. If this warning appears again with the same bookmark, then the cache agent is not making any progress refreshing this table. Otherwise if the warning does not appear again with the same bookmark, the cache agent was only temporarily behind.	For details on fixing this problem, see Incremental autorefresh becomes full autorefresh in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
44038	The last recorded log sequence number is larger than the current log sequence number for table table_name for cache group owner_name.cache_group_name. Updates might get lost.	Internal error. Contact TimesTen Customer Support.
44040	The log table marker is not making progress for tables in refresh interval number ms in database database_name. New records are being autorefreshed but bookmark is not moving ahead, causing duplicate work	Internal error. Contact TimesTen Customer Support.
44041	Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried number times without waiting for next autorefresh interval	Ensure that there are no open DDL transactions on the cache group.
44042	Two-safe transaction was committed locally because the commit on the remote node did not complete within timeout interval of number seconds.	The cache agent forced a commit of a TWOSAFE transaction because it did not receive an acknowledgment. This causes replication subscribers to be behind.
44043	Entry for object id object_name exists in " TTC_FT_OBJECT_PREFIX "agent_status but missing from " TTC_FT_OBJECT_PREFIX "user_count table	For details on fixing this problem, see Validate autorefresh for the Oracle database objects in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
44044	Last autorefresh for interval number ms has not finished after number ms	An autorefresh transaction is taking significantly longer than the specified autorefresh interval. The first parameter of this message indicates the specified autorefresh interval. The second parameter indicates how long the transaction has been in progress. For details on fixing this problem, see Incremental autorefresh not progressing in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
44045	pthread_cond_timedwait failed with return value number	Internal error. An operating system call failed.
44046	Failover error. Retrying...	Type of Message: Error Cause: A TimesTen operation meant to handle Oracle database failover was unsuccessful. Impact: The cache agent is retrying the operation. User Action: None.
44047	Operation is aborted because cache agent is shutting down	Warning. The cache agent is shutting down.
44048	OCIDescriptorFree failed	Internal warning. The OCIDescriptorFree call did not succeed.
44049	Could not get LockTruncator lock because the SYNC_OBJS table or LockTruncator row does not exist. Will try again after 1 minute	For details on fixing this problem, see Validate autorefresh for the Oracle database objects in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
44051	Binding the database column with the output C type + precision can result in overflow errors or truncation warnings.	Internal error.
44053	OCI function pointers initialization warning: warning_message. No action needed.	This warning can occur during cache agent initialization when a function was not found in the client library. No action is needed as the system will not use that function. Check that the OCI client library version is 11.1 or later.
44055	Load from Oracle warning: Data Conversion involving columns of type TT_TIMESTAMP may result in truncated data	Type of Message: Warning Cause: You attempted to load data from an Oracle database column that uses a TIMESTAMP data type with precision greater than 6 into a TimesTen database column that uses a TT_TIMESTAMP data type. Impact: TimesTen may truncate the data. User Action: Ensure that the Oracle database column uses a TIMESTAMP data type with precision no greater than 6.
47000	TimesTen cache agent Version version_number, build_time build_date	This message indicates the version of the cache agent. The version is of the format major.minor.patch.build_time.build_date.
47001	Watching for main daemon termination	Informational message. The agent thread that detects TimesTen daemon shutdown event is up running.
47002	Registered with daemon: Port port_number, id cache_agent_id	Informational message. The cache agent has registered itself with daemon.
47003	Starting up cache agent for database database_name	Informational message. The cache agent is reporting the database name that it is managing.
47006	Received request command_name	Informational message. The cache agent received a request. The request format is internal.
47007	Replied OK	Informational message. The cache agent replied to a request by sending an OK message.
47008	Replied Missing type	Informational message. The cache agent received a request but the message type was not specified.
47009	The request was denied because it was not sent by an authorized process	Informational message. The cache agent rejected a request because the request was not sent by an authorized process.
47010	Refreshed cache group: cache_group_name	Informational message. A manual refresh statement has been done through the Cache agent on the indicated cache group.
47011	Loaded cache group: cache_group_name	Informational message. A manual load statement has been done through the cache agent on the indicated cache group.
47012	Stopped autorefresh for cache group: cache_group_name	Informational message. The stop autorefresh request for the specified cache group has been received and queued.
47013	Bad request	Informational message. The requested message cannot be handled by the cache agent.
47016	Logging off of Oracle. Inst: instance_name, Role: database_role	Informational message. Logging off from the Oracle database.
47017	Disconnected from Oracle. Inst: instance_name, Role: database_role	Informational message. Disconnected from the Oracle database.
47018	Process_name pid: Trying to free orphan cache group cache_group_name	Cache groups that no longer belong to any autorefresh intervals are orphan cache groups. Cache agent is cleaning up the specified orphan cache group from its internal data structure.
47029	refresher started for interval number milliseconds	Informational message. The autorefresh handler thread for the specified interval has started.
47030	refresher for interval number milliseconds is about to exit	Informational message. The autorefresh handler thread for the specified interval is about to exit.
47037	Disabled autorefresh for cache group: cache_group_name	Informational message. The scheduler has disabled autorefresh for the specified cache group.
47038	Enabled autorefresh for cache group: cache_group_name	Informational message. The scheduler has enabled autorefresh for the specified cache group.
47043	OracleNetServiceName not specified. Will not be able to perform autorefreshes.	Informational message. The OracleNetServiceName attribute is not specified on the DSN. The cache agent cannot perform any autorefresh tasks.
47044	Logging into Oracle. Inst: instance_name, Role: database_role	Informational message. Cache agent is logging into the Oracle database.
47045	Connected to Oracle. Inst: instance_name, Role: database_role	Informational message. The cache agent has connected to the Oracle database.
47046	Already connected for caching for database_name	Informational message. The cache agent is using an existing connection to the Oracle database to operate on database.
47048	Processing Oracle SQL: statement	Informational message. This message follows an error message. It indicates the error occurred while the cache agent was processing the specified Oracle database SQL statement.
47049	Performing a full refresh with cache group root table: owner_name.table_name	Informational message. The cache agent is performing a full refresh on the specified table.
47050	Performing a full refresh	Informational message. The cache agent is performing a full refresh.
47051	restarting autorefresh for cache group: cache_group_name	Informational message. The cache agent is restarting the autorefresh for the specified cache group. This happens during cache agent startup.
47052	re-started autorefresh for cache_group_name cache groups	Informational message. The cache agent is restarting the autorefresh for the specified cache groups. This happens during cache agent startup.
47053	Error executing the following Oracle SQL statement: statement	Informational message. The Oracle database returned an error while executing the specified SQL statement. This may not be an error condition for the cache agent.
47054	TimesTen transaction committed.	Informational message. A TimesTen transaction has been committed.
47055	Autorefresh rolled back.	Informational message. An autorefresh operation has been rolled back.
47056	Incremental autorefresh started for table: owner_name.table_name. soLog(first_row), eoLog(last_row).	Informational message. The cache agent is performing an incremental autorefresh on the specified table.
47057	Oracle object busy. Will retry: message	Informational message. The Oracle database object is being used by other user. The operation is retried in the indicated number of milliseconds.
47058	Executing Oracle statement: statement	Informational message. The indicated statement is being executed on the Oracle database.
47059	Successfully executed Oracle SQL statement: statement	Informational message. The Oracle database SQL statement has been successfully executed.
47060	Performing a full refresh on subtree with root: owner_name.table_name	Informational message. The cache agent is performing a full refresh on a subtree of cache group with the specified root table.
47064	Starting cleanup of the Oracle objects	Informational message. The cache agent has begun cleaning up Oracle database objects that were used by autorefresh.
47066	Cleanup of the Oracle objects completed	Informational message. The cache agent has finished cleaning up Oracle database objects that were used by autorefresh.
47067	Lost connection to Oracle -- shutting down the cache agent, cmd: command_string	Type of Message: Informational Cause: The Oracle database connection was lost while executing the indicated command. Impact: The cache agent is shutting down and restarting. User Action: If the cache agent does not start automatically, restart it manually. For more information, see Starting the Cache Agent in Oracle TimesTen In-Memory Database Cache Guide.
47070	No new connection during shutdown	Informational message. A request of a new TimesTen/Oracle database connection was denied because the cache agent is in the shutdown process. Wait for the cache agent to completely shutdown and then restart the agent and attempt the connection.
47071	Warning Ignored: message, ODBC SQL state = state, Additional Warning = warning_code	Informational message. The cache agent has purposely ignored the TimesTen ODBC warning, the SQL state and the TimesTen warning code indicated in the message.
47072	Error Ignored: message, ODBC SQL state = state, Additional Error = error_code	Informational message. The cache agent has purposely ignored the TimesTen ODBC error, the SQL state and the TimesTen error code indicated in the message.
47073	Cannot connect to Oracle while the cache agent is during shutdown	Informational message. The cache agent cannot connect to the Oracle database while the cache agent is shutting down.
47074	Cache agent is shutting down all service threads	Informational message. The cache agent is shutting down all service threads.
47075	Cache agent is in final shutdown stage	Informational message. The cache agent has shutdown all service threads and is in final shutdown mode.
47076	Cache agent has started all service threads.	Informational message. The cache agent has started all service threads during startup.
47077	Cache agent for database database_name is shutting down	Informational message. The cache agent is shutting down.
47078	Autorefresh number number succeeded for interval number milliseconds	Informational message. Autorefresh for interval msecs succeeded.
47084	ftSchedulerGetRefreshStats: cannot find cache group with cgID cache_group_id	Internal Error. TimesTen cannot find the indicated cache group.
47085	AUTOREFRESH advances to new LOG SEQ Log Seq(number) = table_name in cache group cache_group_name	The autorefresh bookmark for indicated table has been advanced to the indicated log sequence. This indicates the autorefresh has brought in some new changes to TimesTen.
47086	Retry timeout is number minutes.	The cache agent is waiting for an Oracle database object to come active. The cache agent retries the operation in the indicated number of minutes.
47087	Cache agent refreshed cache group owner_name: cache_group_name	Informational message. The cache agent refreshed the root table rows in the specified cache group.
47088	Cache agent refreshed number root table rows for this interval	Cache agent refreshed the indicated number of root table rows for this interval.
47090	DDL on base table after creating trigger - DDL has been executed on table owner_name.table_name after the cache group cache_group_name in database database_name was created. The cache group may not be refreshed or may be out of sync.	The cache agent has noticed that the Oracle database table has been altered after an autorefresh cache group has been defined on it. As a result, the cache group may not refresh correctly.
47092	Cache group cache_group_name in database database_name does not have autorefresh mode set to incremental. No validation is required.	Informational message. Autorefresh is not set for the specific cache group.
47093	Validation starting: Starting validation check for cache group cache_group_name in database database_name.	Informational message. The cache agent is validating the Oracle database objects for tracking changes for the indicated cache group.
47094	StatusAnomalies were found in the objects used to autorefresh the cache group cache_group_name in database database_name.	Informational message. The cache agent has found anomalies in autorefresh tracking objects for the indicated cache group.
47095	StatusAnomalies were found in the objects used to autorefresh cache groups in refresh interval number for database database_name.	Informational message. The cache agent has found anomalies in autorefresh tracking objects for the cache groups with the specified refresh interval.
47096	StatusNo anomalies were found in the objects used to autorefresh the cache group cache_group_name in database database_name.	Informational message. Autorefresh validation has successfully completed.
47097	Validation aborted: A fatal error occurred while validating cache groups in refresh interval number for database database_name.	Informational message. The cache agent encountered an error while validating the autorefresh objects for the specified interval.
47098	Number of bipropagate rows deleted: number	Informational message. The cache agent is tracking an operation on cache groups using both the autorefresh and propagate feature.
47100	The cache agent will wait at least number minutes before validating cache groups.	Informational message. The cache agent is waiting for at least the specified number of minutes before validating the autorefresh objects.
47108	Autorefresh state for this cache group cache_group_name is no longer ON. Autorefresh will be retried after refreshing the new state	Informational message. The current autorefresh state for this cache group is not ON.
47109	Autorefresh mode for this cache group cache_group_name is no longer incremental. Autorefresh will be retried after refreshing the new mode	Informational message. The autorefresh mode has changed for this cache group.
47110	object_id object_id, bookmark bookmark_name	Informational message. The autorefresh bookmark for the specified table.
47111	Cache agent successful in getting oneTruncator lock for garbage collection	Informational message. The cache agent has locked the oneTruncator autorefresh object successfully.
47112	Garbage collector deleted number rows from " TTC_FT_OBJECT_PREFIX "object_id_L where logseq < log_sequence (Min logseq was log_sequence)	Informational message. The garbage collector deleted said number of rows.
47113	Log Table Marker marked number rows of log table " TTC_FT_OBJECT_PREFIX "object_id_L with logseq log_sequence through log_sequence	Informational message. The progress of log marking for autorefresh.
47116	Detect Environment Variable: variable_name, Value: value	Informational message. The cache agent obtained a value from the indicated environment variable.
47117	Autorefresh thread for interval numberms is connected to instance instance_name on host host_name. Server handle handle_number	Informational message. The cache agent thread for autorefresh of cache groups with the specified autorefresh interval has connected to the Oracle database.
47118	Starting autorefresh number number for interval numberms	Informational message. The cache agent is starting an autorefresh with the specified autorefresh interval.
47119	Autorefresh number number finished for interval numberms status	Informational message. Autorefresh has completed.
47120	Failing over connection. Failover type is type.	Informational message. The cache agent is starting an Oracle RAC failover of the indicated type, where type is one of: SESSION, SELECT or unknown.
47121	Failover completed.	Informational message. The failover has completed.
47122	Failover callback function called.	Informational message. The cache agent's registered Oracle RAC failover callback function has been called.
47123	Failover callback function registered for server handle handle_number.	Informational message. The cache agent has registered an Oracle RAC callback function for failover
47125	Autorefresh thread for interval numberms is connected to instance id instance_id. Server handle handle_number	Informational message. The autorefresh thread for cache groups with the specified autorefresh interval has connected to the Oracle database.
47126	Failover stopped. Cache agent shutting down.	Informational message. The cache agent cannot do an Oracle RAC failover since the cache agent is already in shutdown mode.
47127	Autorefresh marker thread exiting.	Informational message. The autorefresh marker thread is exiting.
47128	Autorefresh garbage collector thread exiting.	Informational message. The autorefresh garbage collector thread is exiting.
47129	Autorefresh mode for this cache group cache_group_name is no longer full. Autorefresh will be retried after refreshing the new mode	Informational message. Autorefresh mode has changed for this cache group.
47130	Full autorefresh will be performed on the table owner_name.table_name because an initial load was not performed	Informational message. The application did not load the cache group after it was created. As a result, the first autorefresh is a full refresh.
47131	Lock info message: lock_info	Informational message. This is an internal message tracking locks on cache agent synchronization objects.
47132	Skipped reporting bookmark for object_id object_id	Informational message. The cache agent skipped a reporting bookmark for the table with the specified object ID.
47133	Error freeing odbc handle	Informational message. The cache agent encountered an error when it tried to free a TimesTen ODBC handle.
47135	Thread thread_id encountered an invalid value for argument argument while adding a cache group to the cache agent scheduler. Cache group cache_group_name will not be autorefreshed.	One of the arguments passed to a routine to add a cache group to the scheduler did not pass a validity check. The cache group is not added to the scheduler and therefore is not autorefreshed.
47136	The cache agent hasn't fully initialized yet. The cache group cache_group_name will be refreshed after initialization is complete.	Type of Message: Informational Cause: A CREATE or ALTER CACHE GROUP statement was issued before the cache agent had a chance to initialize. Impact: The CREATE or ALTER operation takes effect after the initialization completes. User Action: None.
47137	Handle invalid due to client failover.	Re-initiate the handle. An automatic failover has occurred.
47138	DDL Lock: statuslock_info	This is an information message. A DDL lock has been created.
47139	DDL Lock: statuslock_info	This is a warning message. A DDL lock may interfere with operations.
47140	The cache agent information message: Cache group pointer pointer ; name cache_group_name ; state state_number ; next pointer pointer	There is an internal cache group INFO message in the daemon log.
47141	Refresher thread with id thread_id and interval numberms will be joined	There is an internal cache group INFO message in the daemon log.
47142	String interval: numberms, isDead: number, first cg: cache_group_name	There is an internal cache group INFO message in the daemon log.
47143	String threadId: thread_id, isDead: number, first cg: cache_group_name	There is an internal cache group INFO message in the daemon log.
47144	Rolling back serializable transaction in Oracle RDBMS for interval numberms because a concurrent DDL operation was found to have been active (lastDDLTime for relevant change log tables = string ). The autorefresh will be retried immediately	Type of Message: Informational Cause: A DDL operation ended since the last serializable transaction started for autorefresh. Impact: TimesTen will restart autorefresh automatically with a new serializable transaction. User Action: None.
47150	Heartbeat thread initialization failed	Cache agent heartbeat thread allocation failed.
47151	Heartbeat thread started. Freq: number seconds.	Informational message that the heartbeat thread has started.
47152	Heartbeat thread has exited.	Informational message that the heartbeat thread has exited.
47153	DeadDsMonitor thread initialization failed	Cache Agent dead database monitor thread allocation failed.
47154	Dead database monitor thread started. Freq: number seconds.	Informational message that the dead database monitor thread has started.
47155	Dead database monitor thread has exited.	Informational message that the dead database message has exited.
47156	Message: database_name	Informational generic dead database message.
47157	No cache groups will be autorefreshed since recovery method is manual. Deadcount=number, NumActiveCgs=number	You must manually refresh the indicated cache groups.
47158	Cache groups will undergo manual recovery. Deadcount=number, NumActiveCgs=number	You must manually recover the indicated cache groups.
47159	LogTblMarker thread initialization failed	Cache agent dead database monitor thread allocation failed.
47160	LogTblGC thread initialization failed	There is an internal cache group INFO message in the daemon log.
47161	Tablespace full alerter started for with polling period number seconds	Informational message. The thread to monitor the Oracle database tablespace has started.
47162	Tablespace full alerter exited	Near tablespace full alerter exited message.
47163	Percent%% of the tablespace quota has been used. This exceeds your threshold value of percent%%.	Tablespace used above threshold.
47164	Percent%% of the tablespace has been used. This exceeds your threshold value of value%%.	Tablespace used above threshold.
47165	The tablespace full alerter requires privileges privileges. Alerter is shutting down.	Alerter lacks appropriate Oracle database privileges.
47166	Log Table Marker marked number rows of log table " TTC_FT_OBJECT_PREFIX "table_name_L with logseq log_sequence through log_sequence	This is an informational message indicating the progress of the autorefresh log marker.
47167	Tablespace full alert writer started for with polling period number seconds	Near tablespace full alerter writer started message.
47168	Tablespace full alert writer exited	Near tablespace full alerter writer exited message.
47169	The tablespace full alert writer requires privileges privileges. Will shutdown the alerter.	Alerter writer lacks appropriate Oracle database privileges.
47170	Could not determine the size of the Oracle tablespace	Alerter writer could not determine the size o the Oracle database tablespace.
47171	Tablespace full alert writer updated cache statistics table. Tablespace used percentage=percent	This is an informational message from the progress thread monitoring the Oracle database tablespace. The message indicates how much tablespace is in use.
47172	Heartbeat updated	Informational daemon message.
47173	Bad Oracle agent tuning parameter read by thread_name thread. P1=value, P2=value, P3=value	Informational daemon message.
47174	Autorefresh of cache group cache_group_name, failed number time(s) due to lock conflicts.	For this dynamic cache group, autorefresh was unable to complete due to lock conflicts with another application. Indicates the number of times failed due to lock conflicts.
47175	Autorefresh of cache group cache_group_name has escalated locks, after number roll backs.	For this dynamic cache group, a threshold count of autorefresh lock conflict failures was reached. Autorefresh will now escalate its locks and priority to improve its chances of completion.
47176	Autorefresh Garbage Collector chunk size is number.	Type of Message: Informational Cause: The cache agent is starting scheduled garbage collection of autorefresh change log records. Impact: Log records representing rows that have been applied from the Oracle database to the TimesTen database are being removed from the change log tables. For more information on log tables, see Managing a Cache Environment with Oracle Database Objects in Oracle TimesTen In-Memory Database Cache Guide. User Action: None.
47177	LogSpaceMon thread started. threshold : number seconds action : action_setting.	Type of Message: Informational Cause: The monitoring and management thread for the autorefresh log space started with the specified threshold value and action setting. Impact: None. User Action: None.
47178	LogSpaceMon thread has exited.	Type of Message: Informational Cause: The monitoring and management thread for the autorefresh log space exited. Impact: None. User Action: None.
47179	logSpaceMon thread initialization failed	Type of Message: Error Cause: The monitoring and management thread for the autorefresh log space failed to start. Review the daemon log for any additional error messages to determine a cause for the error message. For more information on how to review the daemon log, see Using the logs generated by the TimesTen daemon in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide. Impact: Review the daemon log for any possible impacts. User Action: Review the daemon log for any possible fixes.
47180	LogSpaceMon: LogSpaceMon_statusstatus_details	Type of Message: Informational Cause: General informational message for the monitoring and management thread for the autorefresh log space. Impact: None. User Action: None.
47189	Cache group cache_group_name will not be autorefresh because the cache group is marked not alive and the recovery method is manual.	Type of Message: Warning Cause: The specified cache group has been marked dead because the cache agent has been down too long. You have configured the cache group in a way that requires a full manual refresh to recover the cache group. Impact: The data in the autorefresh cache group is out of date. User Action: Perform a full manual refresh on the specified cache group. For more information on how to perform a full manual refresh of a cache group, see Manually Loading and Refreshing a Cache Group in Oracle TimesTen In-Memory Database Cache Guide.
47190	Autorefresh commit every n operations feature is enabled for autorefresh interval numberms and autorefresh number number. Autorefresh will commit after every number operations.	Type of Message: Informational Cause: The ttCacheAutorefreshXactLimit built-in is enabled with the specified settings. Impact: The autorefresh cycles will be performed as several small transactions instead of one large transaction. User Action: None. For more information on the ttCacheAutorefreshXactLimit built-in, see ttCacheAutorefreshXactLimit in Oracle TimesTen In-Memory Database Reference.
47192	Autorefresh for interval numberms and number number will apply changes to TimesTen using a single transaction.	Type of Message: Informational Cause: The ttCacheAutorefreshXactLimit built-in is not enabled. Impact: The autorefresh cycles will be performed as single transactions. User Action: None. For more information on the ttCacheAutorefreshXactLimit built-in, see ttCacheAutorefreshXactLimit in Oracle TimesTen In-Memory Database Reference.
47193	Could not find refresher_type refresher with interval numberms.	Type of Message: Error Cause: An internal structure that contains the autorefresh information for the specified interval was not found. Impact: The operation failed. User Action: If you receive this error message while using the ttCacheAutorefIntervalStatsGet built-in, retry the operation. If you receive this error message for any other reason, the autorefresh operation will be attempted later.
47194	Incremental autorefresh encountered an error for table: owner_name.table_name. soLog(first_row), eoLog(last_row).	Type of Message: Error Cause: The incremental autorefresh operation encountered an error for the specified table. A detailed error message follows this message. Impact: The incremental autorefresh operation cannot be performed and will be attempted again later. Review the error message for any additional impacts. User Action: Review the error message for possible fixes.
47195	Incremental autorefresh ended for table: owner_name.table_name. soLog(first_row), eoLog(last_row).	Type of Message: Informational Cause: The incremental autorefresh operation for the specified table completed. Impact: None. User Action: None.
47196	Load table started for table: table_name	Type of Message: Informational Cause: The specified table is starting to load. Impact: None. User Action: None.
47197	Load table encountered an error for table: table_name	Type of Message: Error Cause: The load table operation encountered an error for the specified table. A detailed error message follows this message. Impact: The load table operation cannot be performed. Review the error message for any additional impacts. User Action: Review the error message for possible fixes.
47198	Load table ended for table: table_name	Type of Message: Informational Cause: The specified table finished loading. Impact: None. User Action: None.
47199	Subtree load started for root table: owner_name.table_name	Type of Message: Informational Cause: The subtree of the specified root table is starting to load. Impact: None. User Action: None.
47200	Subtree load encountered an error for root table: owner_name.table_name	Type of Message: Error Cause: The subtree load operation encountered an error for the root table. A detailed error message follows this message. Impact: The subtree load operation cannot be performed and will be attempted again later. Review the error message for any additional impacts. User Action: Review the error message for possible fixes.
47201	Subtree load ended for root table: owner_name.table_name	Type of Message: Informational Cause: The subtree of the specified root table finished loading. Impact: None. User Action: None.
47202	Root load started for root table: table_name	Type of Message: Informational Cause: The specified root table is starting to load. Impact: None. User Action: None.
47203	Root load encountered an error for root table: table_name	Type of Message: Error Cause: The load table operation encountered an error for the specified root table. A detailed error message follows this message. Impact: The load table operation cannot be performed and will be attempted again later. Review the error message for any additional impacts. User Action: Review the error message for possible fixes.
47204	Root load ended for root table: table_name	Type of Message: Informational Cause: The specified root table finished loading. Impact: None. User Action: None.
47205	Prepared oracle stmt: statement	Type of Message: Informational Cause: The specified Oracle database statement has been prepared. Impact: None. User Action: None.
47206	Log Table Marker marked number rows of log table " TTC_FT_OBJECT_PREFIX "object_id_L with logseq log_sequence through log_sequence	Type of Message: Informational Cause: The log table marker marked the specified amount of rows within the specified range from the specified log table. Impact: None. User Action: None.
47207	Log Table Marker marked number rows of log table " TTC_FT_OBJECT_PREFIX "object_id_L	Type of Message: Informational Cause: The log table marker marked the specified amount of rows from the specified log table. Impact: None. User Action: None.
47209	Log Table Marker skipped marking of log table " TTC_FT_OBJECT_PREFIX "object_id_L	Type of Message: Informational Cause: Log Table Marker skipped marking log table. Impact: The log file is missing some markings and it may take longer to recover if needed. User Action: None.
47210	AR STATS: autorefresh_stats	Type of Message: Informational Cause: This is a diagnostic message that shows the autorefresh statistics. Impact: None. User Action: None.
47211	TAF callback re-establishing session settings.	Type of Message: Informational Cause: This is a progress message indicating that Transparent Application Failover (TAF) is executing during a Real Application Clusters (Oracle RAC) failover. Impact: TAF callback is reestablishing session settings. User Action: None.
47212	TAF callback re-establishing nls settings.	Type of Message: Informational Cause: This is a progress message indicating that Transparent Application Failover (TAF) is executing during a Real Application Clusters (Oracle RAC) failover. Impact: TAF callback is reestablishing NLS settings. User Action: None.
47213	Marked cache group with id=cache_group_id(ts=timestamp) for delete	Type of Message: Informational Cause: The cache agent marked the specified cache group to be removed from the internal structure of the refresher. Impact: The cache agent will not consider the specified cache group in subsequent autorefresh operations. User Action: None.
47214	Dropped Oracle database objects	Type of Message: Informational Cause: The cache agent is dropping the cache group Oracle database metadata objects that are no longer needed. Impact: The cache group metadata objects are no longer available on the Oracle database. User Action: None.
47215	Removed cache group: id=cache_group_id, name=cache_group_name, mode=autorefresh_mode, state=autorefresh_state, ts=timestamp, interval=number from list	Type of Message: Informational Cause: The cache agent is deleting the specified cache group from the internal structure of the refresher. Impact: The refresher thread for the specified interval will no longer manage the specified cache group. User Action: None.
47216	Added cache group: id=cache_group_id, name=cache_group_name, mode=autorefresh_mode, state=autorefresh_state, ts=timestamp, interval=number to list	Type of Message: Informational Cause: The cache agent is adding the specified cache group to the internal structure of the refresher. Impact: The refresher thread for the specified interval will start managing the specified cache group. User Action: None.
47217	Error retrieving data from Oracle database: error_message	Type of Message: Error Cause: There was an error while retrieving information from the Oracle database. The included error message describes the details of the failure. Impact: TimesTen did not complete the operation. User Action: Review the included error message to determine the cause of the failure.
47218	Retrieved SCN: scn, Instance: oracle_instance.	Type of Message: Informational Cause: TimesTen retrieved the specified SCN from the Oracle database. Impact: None. User Action: None.
47219	Failed to flashback to SCN. SCN: scn	Type of Message: Error Cause: The client was unable to flashback to the specified SCN Impact: TimesTen did not complete the operation. User Action: Review the accompanying error messages to determine the cause of the failure.
47220	Failed to disable flashback on Oracle database.	Type of Message: Error Cause: The client was unable to disable flashback on Oracle database Impact: TimesTen did not complete the operation. User Action: Review the accompanying error messages to determine the cause of the failure.
47221	Oracle database user lacks privilege privilege_name	Type of Message: Error Cause: The Oracle database user requires the specified privilege to execute the operation. Impact: TimesTen cannot complete the operation. User Action: Assign the specified privilege to the Oracle Database user and retry the operation.
47222	Attempted operation is not valid with the current Oracle database configuration. Operation: operation_details, Configuration: configuration_details	Type of Message: Error Cause: The attempted operation is not supported by the configuration of the Oracle database. Impact: TimesTen cannot complete the operation. User Action: Review and modify the Oracle database and TimesTen database configurations as appropriate and retry the operation.
47223	Instance instance_name has role: database_role	Type of Message: Informational Cause: Oracle database role was retrieved. Impact: None. User Action: None.
47224	Instance with role database_role has been marked as: database_state	Type of Message: Informational Cause: The state of the Oracle database has been changed either by the user or by the cache agent. Impact: None. User Action: None.
47225	The cache group is being created or recovered. Autorefresh cannot be performed.	Type of Message: Informational Cause: The cache agent is trying to refresh a cache group that is not ready to be refreshed. Impact: None. User Action: None.
47226	Log Table Marker skipped marking of log table " TTC_FT_OBJECT_PREFIX "object_id_L. details	Type of Message: Informational Cause: Log Table Marker skipped marking the specified log table. Impact: The log file is missing some markings and it may take longer to recover if needed. User Action: None.
48001	Could not obtain host list from Oracle Clusterware found in crs_home.	Type of Message: Error Cause: The ttCWAdmin utility cannot retrieve the list of hosts used for the Oracle Clusterware cluster. Impact: The ttCWAdmin utility failed. User Action: Run the ttInstanceModify -crs utility option to verify and change any values used to manage TimesTen hosts within an Oracle Clusterware cluster. For more information on using ttInstanceModify -crs, see Install TimesTen on Each Host in Oracle TimesTen In-Memory Database Replication Guide.
48002	CRS home was not found in the ttcrsagent.options file.	Type of Message: Error Cause: The Oracle Clusterware location is not specified in the ttcrsagent.options file. Impact: The ttCWAdmin utility failed. User Action: Run the ttInstanceModify -crs utility option and verify that all the values are correct. For more information on using ttInstanceModify -crs, see Install TimesTen on Each Host in Oracle TimesTen In-Memory Database Replication Guide.
48003	Failed to load Clusterware API libaray.	Type of Message: Error Cause: A TimesTen Clusterware utility was unable to load the Clusterware API library from Oracle Clusterware. Impact: The TimesTen Clusterware utility failed. User Action: An operating system error may precede this message and may be found in the ttcwerrors.log file. Diagnose and troubleshoot the operating system error. Run the ttInstanceModify -crs utility option and verify that all the values are correct. Also, ensure that the API libraries are located in the CRS_HOME/lib, directory. For more information on the ttcwerrors.log file, see Message Log Files in Oracle TimesTen In-Memory Database Replication Guide. For more information on using ttInstanceModify -crs, see Install TimesTen on Each Host in the Oracle TimesTen In-Memory Database Replication Guide.
48004	Clusterware_function failed with status = error_number.	Type of Message: Error Cause: A call to an Oracle Clusterware API failed. Impact: TimesTen cannot perform the operation. User Action: Review the specified error message for possible fixes.
48005	One or more clusters are currently active on the host host_name.	Type of Message: Error Cause: You attempted to shut down one or more cluster agents that are currently active on the specified host. Impact: TimesTen cannot run the ttCWAdmin -shutdown utility command User Action: Perform the following steps: - Identify the active cluster agents by executing the ttCWAdmin -status command. - Drop the existing cluster agents by executing the ttCWAdmin -drop command. For more information about the ttCWAdmin utility, see ttCWAdmin in Oracle TimesTen In-Memory Database Reference.
48006	The cluster configuration file attribute attribute_name for DSN database_name in the cluster configuration file file_name does not have an assigned value.	Type of Message: Error Cause: You did not assign a value to the specified cluster configuration file attribute in the cluster.ora.ini file. Impact: TimesTen cannot run the ttCWAdmin -create utility command User Action: Assign a value to the specified cluster configuration file attribute. Then, retry the operation. For more information, see Configuring Oracle Clusterware Management with the cluster.oracle.ini File in Oracle TimesTen In-Memory Database Replication Guide.
48007	Virtual IP resources do not exist in the cluster for DSN database_name.	Type of Message: Error Cause: The TimesTen virtual IP resources do not exist in the Oracle Clusterware for the specified DSN. Impact: TimesTen cannot run the ttCWAdmin -create utility command. User Action: Use the ttCWAdmin -createVIPS utility command to create the TimesTen virtual IP resources. For more information about the ttCWAdmin utility, see ttCWAdmin in Oracle TimesTen In-Memory Database Reference.
48008	A cluster for the DSN database_name has already been registered.	Type of Message: Error Cause: You attempted to create a cluster that already exists for the specified DSN. Impact: TimesTen cannot run the ttCWAdmin utility command. User Action: If you want to create a new cluster with the specified name, perform the following steps: - Drop the existing cluster using the ttCWAdmin -drop utility command. - Then, create the new cluster using the ttCWAdmin -create utility command. For more information about the ttCWAdmin utility, see ttCWAdmin in Oracle TimesTen In-Memory Database Reference.
48009	Private hostname not found for the host host_name.	Type of Message: Error Cause: The private hostname for the indicated host name was not returned by Oracle Clusterware. Impact: Oracle Clusterware cannot start. User Action: Verify the cluster configuration by calling crsctl check cluster. If the host is not listed, follow the procedure in the Oracle Clusterware documentation. If the host is listed, contact TimesTen Customer Support.
48010	Connection to TimesTen Cluster agent on host host_name failed.	Type of Message: Error Cause: The TCP connection to the TimesTen Cluster agent failed on the specified host. Impact: Oracle Clusterware cannot start. If Oracle Clusterware is already running, the Oracle Clusterware services will failover to another host. User Action: Check the ttcwerrors.log file on the indicated host for any errors occurring before this error. Diagnose and troubleshoot the errors. If no network error is detected, contact TimesTen Customer Support. For more information on the ttcwerrors.log file, see Message Log Files in Oracle TimesTen In-Memory Database Replication Guide.
48011	Could not successfully send cluster configuration model for DSN database_name to TimesTen Cluster agent on host host_name.	Type of Message: Error Cause: This error may occur as the result of an incorrect input to a ttCWAdmin utility command, an incorrect value in the TimesTen cluster configuration file, or due to network errors. Impact: The cluster may not be fully started, or may exclude the specified host, or both. User Action: - Ensure that your input to the ttCWAdmin utility command is correct. For more information, see ttCWAdmin in Oracle TimesTen In-Memory Database Reference. - Check the TimesTen cluster configuration file for any errors. For more information, see TimesTen Configuration Attributes for Oracle Clusterware in the Oracle TimesTen In-Memory Database Replication Guide. - Check the ttcwerrors.log file on the indicated host for errors that occurred before this error. Diagnose and troubleshoot the errors. If no network error is detected, contact TimesTen Customer Support. For more information on the ttcwerrors.log file, see Message Log Files in the Oracle TimesTen In-Memory Database Replication Guide.
48012	Could not successfully verify user ID and password(s) for DSN database_name on host host_name.	Type of Message: Error Cause: You specified an invalid user ID or password for the TimesTen database. Impact: TimesTen cannot run the ttCWAdmin -create utility command. User Action: Ensure that the specified database exists. Also, ensure that you specify a correct user ID and password for the TimesTen database. If TimesTen Cache is enabled, verify the Oracle database password. For more information, see UID and PWD in Oracle TimesTen In-Memory Database Reference.
48013	Failed to create ACTIVE STANDBY PAIR scheme for DSN database_name on host host_name.	Type of Message: Error Cause: The active standby pair cannot be created. Impact: Oracle Clusterware cannot start. User Action: Check for errors in the ttcwerrors.log and the ttmesg.log files. Diagnose and fix the errors. Then run the ttCWAdmin utility command that failed. If the same replication scheme can be created manually without using the ttCWAdmin utility, contact TimesTen Customer Support. For more information on the message log files, see Message Log Files in Oracle TimesTen In-Memory Database Replication Guide.
48014	Failed to register the cluster for DSN database_name with Oracle Clusterware.	Type of Message: Error Cause: TimesTen cannot register the cluster for the specified DSN. Impact: TimesTen cannot run the ttCWAdmin -create utility command. User Action: Review the ttcwerrors.log and ttcwmsg.log error message log files for possible fixes. For more information on the message log files, see Message Log Files in Oracle TimesTen In-Memory Database Replication Guide.
48015	Failed to register resource resource_name with Oracle Clusterware.	Check the ttcwmesg.log and ttcwerrors.log files for errors that occurred before this error. Verify that Oracle Clusterware is running by running the command crsctl check crs. Verify that attribute values specified in the TimesTen cluster configuration file are correct.
48016	TimesTen Cluster agent received NULL Oracle password for DSN database_name.	Type of Message: Error Cause: You did not specify an Oracle database password when creating a cluster. Impact: TimesTen cannot run the ttCWAdmin -create utility command. User Action: Retry using the ttCWAdmin -create utility command and specify a valid Oracle database password. Then, retry the operation. For more information on the ttCWAdmin utility, see ttCWAdmin in Oracle TimesTen In-Memory Database Reference.
48017	No tns_admin option specified in ttendaemon.options file.	Type of Message: Error Cause: The ttendaemon.options file does not contain a valid tns_admin daemon option. Impact: TimesTen cannot run the ttCWAdmin -create utility command to configure a cluster. User Action: Use the ttInstanceModify -tns_admin utility option to specify a valid tns_admin path. For more information on the ttInstanceModify utility, see ttInstanceModify in Oracle TimesTen In-Memory Database Reference.
48018	Failed to register direct-linked application resources for DSN database_name to Oracle Clusterware.	Type of Message: Error Cause: The ttCWAdmin -create utility command cannot register direct-linked applications to be managed by the Oracle Clusterware. Impact: The ttCWAdmin -create utility command cannot register applications to be managed by the Oracle Clusterware. User Action: Verify that the application attributes are correct in the cluster.oracle.ini file for the specified DSN. Also, ensure that the application script is located in the script install directory of every host. Review the ttcwerrors.log and ttcwmsg.log error message log files for how to proceed. For more information about the cluster.oracle.ini file, see Configuring Oracle Clusterware Management with the cluster.oracle.ini File in Oracle TimesTen In-Memory Database Replication Guide. For more information on the message log files, see Message Log Files in the Oracle TimesTen In-Memory Database Replication Guide.
48019	Failed to restore DSN database_name on the localhost.	Type of Message: Error Cause: You attempted to restore the specified DSN. Impact: TimesTen cannot execute the ttCWAdmin -restore utility command. User Action: Review the ttcwerrors.log and ttcwmsg.log error message log files for how to proceed. For more information on the message log files, see Message Log Files in Oracle TimesTen In-Memory Database Replication Guide.
48020	TimesTen cluster containing DSN database_name not found.	There is no registered cluster containing the specified DSN. If the cluster was created previously, creation may have failed. Drop the existing cluster by calling: ttCWAdmin -drop -dsn dsn_name Create a new closer by calling: ttCWAdmin - create -dsn dsn_name
48021	Resource resource_name not registered.	The specified resource is not registered with Oracle Clusterware. If the cluster was created previously, creation may have failed. Drop the existing cluster by calling: ttCWAdmin -drop -dsn dsn_name Create a new cluster by calling: ttCWAdmin - create -dsn dsn_name
48022	TimesTen cluster containing DSN database_name not completely registered.	Check for resources that are not registered with Oracle Clusterware by reviewing error messages that appear in the ttcwerrors.log file before this error. Drop the existing cluster by calling: ttCWAdmin -drop -dsn dsn_name Create a new cluster by calling: ttCWAdmin - create -dsn dsn_name
48023	TimesTen cluster containing DSN database_name is already running.	Drop the existing cluster by calling: ttCWAdmin -drop -dsn dsn_name
48024	TimesTen cluster containing DSN database_name failed to start.	Check the ttcwmesg.log and ttcwerrors.log files in the daemon home directory for errors that occurred before this error. Also, check the crsd.log file in the CRS_HOME/log/hostname/crsd directory for errors that occurred before this error.
48025	The resource resource_name is still online.	Stop the cluster containing the specified resource by calling: ttCWAdmin -stop -dsn dsn_name
48026	TimesTen cluster containing DSN database_name failed to stop.	Type of Message: Error Cause: The cluster that contains the specified DSN cannot stop. Impact: The state of the cluster is unknown, it may or may not be running. User Action: Contact TimesTen Customer Support.
48027	TimesTen cluster for DSN database_name partly offline.	Some resources of the specified cluster are offline. You may be able to restart the offline resources by calling: ttCWAdmin -start -dsn dsn_name
48028	Could not deregister the TimesTen cluster containing DSN database_name.	The replication scheme does not exist in the specified cluster databases. Stop the cluster by calling: ttCWAdmin -stop -dsn dsn_name Then drop the cluster by calling: ttCWAdmin -drop -dsn dsn_name
48029	Failed to drop active standby pair replication scheme for DSN database_name on host host_name.	The replication scheme does not exist in the specified database on the specified host.
48030	TimesTen Cluster agent could not find application script file with name script_name for the TimesTen cluster containing DSN database_name.	Verify that the application script exists in the script installation directory on all hosts of the cluster.
48031	Failed to create action script for Oracle Clusterware resource 'resource_name' of the TimesTen cluster containing DSN database_name.	Verify that the permissions are correct and there is enough and available space in the script installation directory.
48032	Failed to delete action script for Oracle Clusterware resource resource_name of the TimesTen cluster containing DSN database_name	Verify that the permissions in the script installation directory are correct.
48033	Syntax error in line line_text in the cluster configuration file file_name for DSN database_name.	See the description of the attribute in the TimesTen Configuration Attributes for Oracle Clusterware in Oracle TimesTen In-Memory Database Replication Guide for the correct configuration file syntax.
48034	Unknown attribute attribute_name in the cluster configuration file file_name for DSN database_name.	See the description of the attribute in the TimesTen Configuration Attributes for Oracle Clusterware in Oracle TimesTen In-Memory Database Replication Guide for the correct configuration file syntax.
48035	Conflicting attribute attribute_name in the cluster configuration file file_name for the DSN database_name.	Multiple entries found for the specified attribute in the cluster configuration file. Remove the conflicting attribute(s) and retry the operation.
48036	Invalid value value for attribute attribute_name in the cluster configuration file file_name for the DSN database_name.	See the description of the attribute in the TimesTen Configuration Attributes for Oracle Clusterware in Oracle TimesTen In-Memory Database Replication Guide for the correct configuration file syntax.
48037	The maximum number of subscribers for the TimesTen cluster containing the DSN database_name exceeded the maximum.	See System Limits in Oracle TimesTen In-Memory Database Reference for the maximum number of subscribers in an active standby pair.
48038	Application type of Subscriber specified for application application_name,but no subscribers are configured for TimesTen cluster containing the DSN database_name.	An application type of Subscriber may only be configured if the TimesTen cluster contains subscriber databases.
48039	Invalid subscriber index specified for application application_name in the TimesTen cluster containing the DSN database_name.	The specified subscriber index may not be 0 or less, or greater than the number of subscriber databases.
48040	Orphaned or conflicting application attribute attribute_name specified in the cluster configuration file file_name for DSN database_name.	Verify that the TimesTen cluster configuration file for specified DSN does not contain duplicate application attributes and that the first application attribute for each application is AppName.
48041	Connection to Oracle with OracleNetServiceName service_name failed.	In the sys.odbc.ini entry for the DSN, verify the value for OracleNetServiceName attribute. Also verify that the -tns_admin option is specified correctly in the ttendaemon.options file. Finally, check that the Oracle database is still live.
48042	Failed to determine installation information.	Internal error. Contact TimesTen Customer Support.
48043	The send string string is too long.	The length of an attribute value or a replication scheme is limited to 409600. Verify the length of the attribute values in the cluster configuration file, and the replication scheme if it is specified using the RepDDL attribute.
48044	Wrong ACK string received.	Internal error. Contact TimesTen Customer Support.
48045	No DSN specified in ttCWAdmin command command_string.	Most ttCWAdmin utility commands require that you specify the DSN. Retry the command with the option -dsn dsn_name.
48046	Could not connect to remote database database_name on host host_name.	The host is down, or the TimesTen main daemon or replication agent are down on the specified host, or the database on the specified host is not an active or standby master.
48047	Replication checksum valueof the local database DSN database_name does not match the original checksum value of the replication scheme.	This is a transient error. The local database is automatically duplicated from the remote database in the event of a checksum mismatch.
48048	Another resource is already running binary_executable_name action program for the DSN database_name	Transient error. A new source is starting, but the specified local database is managed by an existing Oracle Clusterware resource. The cluster automatically relocates the new resource to a different host.
48049	Failed to action the replication agent for the DSN database_name.	Transient error. The cluster automatically corrects the problem.
48050	Failed to action the cache agent for the DSN database_name.	This may occur if no cache groups are defined in the DSN, but the CacheConnect attribute is specified with a value of "Y" in the TimesTen cluster configuration file.
48051	TimesTen cluster Action program binary_executable_name timed out for the DSN database_name.	The cluster action program was unable to start the database with a replication state of either active or standby, or was unable to create a subscriber. This may happen if there is a network error in the cluster, or the original active database is destroyed.
48052	Failed to determine the master host name of the local host containing the DSN database_name.	Type of Message: Error Cause: The master host containing the specified DSN could not be determined. Impact: The cluster cannot start. User Action: Ensure that your TimesTen configuration attributes for Oracle Clusterware are correct. The local host should be one of the master hosts or contain one of the master VIP addresses in an active standby pair scheme. For more information see, TimesTen Configuration Attributes for Oracle Clusterware in Oracle TimesTen In-Memory Database Replication Guide. If you are unable to troubleshoot the error or still receive this error, contact TimesTen Customer Support.
48053	Could not find remote active database for the DSN database_name.	The cluster action program was unable to contact the remote active database. This may be a transient network problem.
48054	TimesTen cluster program could not destroy the database with the DSN database_name.	Internal error. Contact TimesTen Customer Support.
48055	Could not find the standby host in the replication scheme for the DSN database_name.	A query to the replication system table TTREP.TTSTORES has failed. Check for SQL errors in the ttmesg.log file.
48056	Could not find backup directory for the DSN database_name.	Verify that the backup directory is accessible from all hosts in the TimesTen cluster.
48057	Another TimesTen Cluster agent is running.	Stop the TimesTen Cluster agent manually by calling ttCWAdmin -shutdown.
48058	TimesTen Cluster agent received an unknown command: command_string.	Internal error. Contact TimesTen Customer Support.
48059	TimesTen Cluster agent did not successfully receive all parameters of the cluster.	The ttCWAdmin utility command closed the connection to the TimesTen Cluster agent due to previous errors or due to a TCP timeout. The TCP timeout for communication between ttCWAdmin and the TimesTen Cluster agent is 30 seconds. Retry the operation if no previous errors or a timeout are mentioned in the ttcwerrors.log file.
48060	TimesTen Cluster agent could not successfully verify Oracle password for the OracleNetServiceName service_name.	Verify that the Oracle database password is correct.
48061	TimesTen Cluster agent received NULL user ID for the DSN database_name.	Internal error. Contact TimesTen Customer Support.
48062	TimesTen Cluster agent received NULL password for the DSN database_name.	Internal error. Contact TimesTen Customer Support.
48063	TimesTen Cluster agent could not create files on directory_name.	On Linux or UNIX systems, all cluster processes of a particular TimesTen instance have their socket files in the temporary directory crsTT_instance admin_instance name. Oracle Clusterware executes action programs that communicate with the TimesTen cluster processes through these file sockets. Ensure that the TimesTen instance administrator and the Clusterware administrator users have read, write and execute permissions on the temp (/tmp) directory. In the ttcwerrors.log file, check if any OS errors occurred before this error.
48064	Failed to determine the status of the TimesTen main daemon with the daemon home directory directory_name,daemon port number port_number.	The daemon is not running, or it is running in a different home directory and with a different port number. Verify that the daemon is running in the appropriate location. If the daemon is running, contact TimesTen Customer Support with the detailed output from ttversion -m on the terminal where the daemon was started.
48065	Failed to obtain replication route from TTCW. Error_details	Type of Message: Error Cause: The replication route from TimesTen Clusterware cannot be obtained. Impact: The attempted operation or TimesTen Clusterware ran into an irrecoverable error. User Action: If you get this error when Oracle Clusterware is managing replication, contact TimesTen Customer Support. If Oracle Clusterware is not managing replication, you can ignore this error.
48066	The host_type host name host_name is invalid.	Verify that the host name is correct and the host exists in the network domain name system.
48067	Failed to read the cluster configuration file file_name.	Check for OS errors preceding this error in the ttcwerrors.log file.
48068	Failed to obtain an IP address for the host host_name.	Verify that the host name is correct and the host exists in the network domain name system.
48069	Process_name failed to connect to the DSN database_name due to the error error_number.	Check for specific connection errors in the ttmesg.log file.
48070	Virtual IP addresses for the DSN database_name were not found in cluster configuration file file_name.	A cluster configuration that uses virtual IP addresses must contain the attribute MasterVIP, specifying the virtual IPs to be used for master databases. If the configuration includes subscribers, it must also include the attribute SubscriberVIP.
48071	The resource resource_name is offline.	An Oracle Clusterware resource is offline. If the TimesTen Cluster agent is offline, bring it up by calling: ttCWAdmin -init If the TimesTen Cluster agent is online, call: ttCWAdmin -start -dsn dsn_name to start all other resources.
48072	Incorrect response is received from TimesTen Cluster Agent for DSN database_name.	Verify that the TimesTen Cluster agent is running and is listening to an available TCP port.
48073	The line 'line_text' in the cluster configuration file is too long. It must be less than number.	If a configuration line is too long, it may be split into multiple lines. Each line may be ended with a "\\" character to indicate that it should be concatenated with the following line. The final concatenated string may be no longer than 2 * posix_LINE_MAX_value.
48074	The concatenated line 'line_text' in the cluster configuration file is too long. It must be less thantwo times number.	An attribute value is too long and must be shortened.
48075	The TimesTen cluster configuration for the DSN database_name was not found in the cluster configuration file file_name.	Verify that the configuration is specified correctly for the specified DSN in the cluster configuration file.
48076	Only one or no host name is mentioned for the attribute MasterHosts for the DSN database_name in the cluster configuration file file_name.	At least two host names must be specified for MasterHosts.
48077	Invalid AppType specified for the application application_name.	The AppType attribute for an application cannot be specified as Active or Standby when the ClusterType is Subscriber.
48078	Attribute attribute_name missing for the DSN database_name in the cluster configuration file file_name.	A required virtual IP attribute is missing from the cluster configuration file.
48079	No value specified for SubscriberHosts for the DSN database_name in the cluster configuration file file_name.	If the ClusterType of the cluster configuration is Subscriber, at least one host name must be specified for SubscriberHosts.
48080	Less than two Virtual IP addresses specified for the attribute MasterVIP for the DSN database_name in the cluster configuration file file_name.	If the ClusterType of the cluster configuration is Active and VIPInterface and VIPNetMask are specified, you must specify at least two virtual IP addresses for the attribute MasterVIP.
48081	No value specified for SubscriberVIP for the DSN database_name in the cluster configuration file file_name.	If subscribers exist in the cluster configuration and VIPInterface and VIPNetMask are also specified, you must specify at least one virtual IP address for the attribute SubscriberVIP.
48082	Backups are disallowed for the DSN database_name in the cluster configuration file file_name.	Backups may only be specified for a DSN when the ClusterType is Active.
48083	A required attribute attribute_name missing for the application application_name for the DSN database_name in the cluster configuration file file_name.	See the description of the attribute in the TimesTen Configuration Attributes for Oracle Clusterware in Oracle TimesTen In-Memory Database Replication Guide for the correct configuration file syntax.
48084	The TimesTen cluster monitor process process_name failed.	The specified process has failed. Check the preceding errors in the ttcwerrors.log file for details.
48085	Failed to create directory directory_name for socket files.	A directory must be created for socket files in /tmp on Linux or UNIX, and C:\\Temp on Windows. Check for preceding OS errors in the ttcwerrors.log file.
48086	Failed to obtain port number for the TimesTen Cluster Agent.	Internal error. Contact TimesTen Customer Support.
48087	Failed to obtain process ID file file_name for reading.	Every cluster monitor process creates a file in the TimesTen info directory that contains its process ID. If this file is missing, the corresponding cluster monitor process is probably not running. If you continuously get this error, contact TimesTen Customer Support.
48088	Failed to delete directory directory_name.	Check OS errors preceding this error in the ttcwerrors.log file.
48089	TimesTen Cluster agent could not successfully receive all application information for the DSN database_name.	Check for TCP communication errors or OS errors preceding this error in the ttcwerrors.log file.
48090	TimesTen Cluster agent could not successfully receive attribute_name for the cluster containing the DSN database_name.	Type of Message: Error Cause: The TimesTen Cluster agent could not receive the specified information when exchanging information with another node in the cluster. Impact: Oracle Clusterware may fail. User Action: Check for TCP communication errors or operating system errors preceding this error in the ttcwerrors.log file. Diagnose and fix the errors. Then run the ttCWAdmin utility command that failed.
48091	TimesTen Cluster agent could not find OracleNetServiceName from the DSN database_name.	Verify that OracleNetServiceName is specified in the DSN configuration in the ODBCINI file.
48092	TimesTen Cluster agent could not successfully send verification_code for the cluster containing the DSN database_name.	Check for TCP communication errors or OS errors preceding this error in the ttcwerrors.log file.
48093	TimesTen Cluster agent could not alter autorefresh state to PAUSED for the cache group owner_name.cache_group_name on the DSN database_name.	Internal error. Contact TimesTen Customer Support.
48094	The cluster monitor process process_name for the DSN database_name failed to obtain connection string.	Type of Message: Error Cause: The indicated cluster monitor process could not obtain a connection string. A common cause for this is that the database does not exist. Impact: The cluster cannot run. User Action: Ensure that the database exists. If you get this error when the database already exists, contact TimesTen Customer Support. For more information, see Specifying Data Source Names to Identify TimesTen Databases in Oracle TimesTen In-Memory Database Operations Guide.
48095	The cluster monitor process process_name detected an invalid database for the DSN database_name.	This error may be received while a failed database is in the process of recovery.
48096	The DSN database_name on Remote master host host_name is unavailable.	A cluster monitor process failed to get a response from the remote replication agent.
48097	Database database_name has changed its role to database_role.	The specified database changed roles without the intervention of a cluster monitor process.
48098	Cluster backup failed for the database database_name on host host_name.	Check preceding errors in the ttcwerrors.log file.
48099	TimesTen daemon is not running on port port_number.	The TimesTen main daemon may have failed. Check for errors in the ttmesg.log file.
48100	TimesTen daemon port port_number in use by TimesTen daemon for other unknown instance with process ID pid.	The configured TimesTen daemon port is not available to the current instance.
48101	TimesTen daemon port port_number in use by an unknown process.	The TimesTen daemon port is not available to the instance.
48102	The hostname host_name in the TTREP.TTSTORES table of database database_name does not match with that of the assigned hostname host_name.	The host name found in the TTREP.TTSTORES system table of the database does not match the host name assigned to the cluster program monitoring it. If the database is a standby master or a subscriber, it is being replaced with a duplicate from the active master. If the database is an active master, it is being recovered from a backup if backups are enabled, otherwise it failed.
48103	The local CTN (timestamp,sequence_number) on the database database_name is larger than that of the database on remote host host_name (timestamp,sequence_number).	Trapped transactions exist on a failed active master database (the transactions were not replicated to the standby master before the database failed). The database is being duplicated to create standby master database that also contains all transactions.
48104	An internal error has occurred for the TimesTen cluster containing the DSN database_name. Error_details.	Check for preceding errors in the ttcwerrors.log file.
48105	The database space usage has exceeded PERMSIZE on DSN database_name.	The database has run out of space and is considered failed.
48106	The database database_name on remote host host_name has declared the local database as FAILED.	If communication is interrupted between the replication agents long enough to meet the configured FAILTHRESHOLD value for the local database, it is automatically recovered by the cluster monitor program.
48107	The replication agent for the database database_name is not running.	The replication agent for the specified database is not running. Oracle Clusterware is restarting it.
48108	The cache agent for the database database_name is not running.	The cache agent for the specified database is not running. The Oracle Clusterware is restarting it.
48109	The remote VIP ip_address for the database database_name is running on the local host.	This may happen if two master VIP addresses start running on the same physical host, such as when only one master host is available. hen an additional host becomes available.
48110	The remote database database_name on host host_name is not in the ACTIVE state.	The remote master database is not in the ACTIVE replication state.
48111	The local database database_name is not in the ACTIVE or STANDBY state.	Type of Message: Error Cause: The local master database is not in the ACTIVE or STANDBY replication state. The local master database is expected to be in the ACTIVE or STANDBY replication state during an intermittent transitional situation for the database, especially during a roll out or when a role change occurs. Impact: None. User Action: Rerun the operation that caused the error. If you still receive this error, contact TimesTen Customer Support.
48112	The last heartbeat from the remote replication agent for database database_name was more than 60 sec.	A heartbeat was not received from the remote replication agent. Verify the network connection between the remote and local hosts.
48115	Not allowed since this database (database_name on host_name) is managed by Clusterware.	A particular operation is disallowed since the database on a host is managed by Clusterware. The list of forbidden SQL operations include: Starting or stopping replication agents. Starting or stopping cache agents. Altering or dropping an active standby pair.
48116	Unsupported Clusterware version version_number.	The Clusterware version for this user does not work with TimesTen.
48117	Unable to obtain Clusterware version.	Contact TimesTen Customer Support.
48118	The local CTN (timestamp,sequence_number) on the database database_name is smaller than that of the database on remote host host_name (timestamp,sequence_number) with virtual IP configured.	While a cluster monitor is bringing up a standby or a read-only subscriber database, and the database is already present locally, the replication CTN of the local database is checked with that of the remote master database. If the CTN of the local database is smaller than that of the remote master database, the local database may have missed transactions that the remote master database had sent. In that case, the local database is destroyed and duplicated from the remote master. This can occur with virtual IP configuration since a standby or a read-only subscriber database can be relocated from one physical host to another.
49044	Failed to acquire latch	Type of Message: Error Cause: TimesTen failed to acquire a database latch. Impact: The database cannot continue normal operations. User Action: Unload and re-load the database.
49045	Latch get for latch_name was interrupted(interrupt_vector)	Type of Message: Error Cause: A latch get operation was interrupted. Impact: The operation failed. User Action: Retry the operation.

Errors 50000-59999

Error number	Error or warning message	Details
50000	Insufficient memory during bulk load operation	Type of Message: Error Cause: The bulk load operation did not start because there is not enough process memory available. Impact: TimesTen failed to initialize the bulk load operation. User Action: Increase the amount of virtual memory available and restart the bulk load operation. For more information on how to increase virtual memory, see Check available swap space (virtual memory) in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
50001	Unsupported table type for bulk load operation	Type of Message: Error Cause: The table type is not supported for use with bulk load operations. Impact: TimesTen cannot perform the bulk load operation. User Action: Restart the bulk load operation with a table with a supported table type.
50002	Unsupported column type for bulk load operation	Type of Message: Error Cause: One or more columns types are not supported for use with bulk load operations. Impact: TimesTen cannot perform the bulk load operation. User Action: Restart the bulk load operation with a table with supported column types.
50003	Failed to allocate blocks for error_buffer	Type of Message: Error Cause: The bulk load operation did not start because there is not enough process memory available. Impact: TimesTen failed to initialize the bulk load operation. User Action: Increase the amount of virtual memory available and restart the bulk load operation. For more information on how to increase virtual memory, see Check available swap space (virtual memory) in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
50005	Too many columns specified for bulk load: number	Type of Message: Error Cause: You specified a greater number of columns than the number of columns available for the bulk load operation. Impact: TimesTen cannot perform the bulk load operation. User Action: Specify the same or a fewer number of columns than the number of columns available in the table and retry the bulk load operation.
50006	Error setting values at row number, col number	Type of Message: Error Cause: An error occurred while setting or converting the data at the specified row and column. Impact: TimesTen aborted the bulk load operation for the current batch of rows. User Action: Correct the data in the specified row and column, and retry the operation.
50007	Error adding page to table	Type of Message: Error Cause: TimesTen could not add a new page of rows to the directory for the table. Impact: TimesTen aborted the bulk load operation for the current batch of rows. User Action: Retry the bulk load operation for the current batch of rows.
50008	Failed to create parallel load context for bulk insert	Type of Message: Error Cause: TimesTen failed to create a parallel load context for the bulk load operation. Impact: TimesTen aborted the bulk load operation. User Action: Retry the bulk load operation.
50009	Failed to commit some or all rows	Type of Message: Error Cause: TimesTen failed to commit the current bulk load transaction. Impact: TimesTen aborted the bulk load operation for the current batch of rows. User Action: Retry the bulk load operation for the current batch of rows.
50010	Failed to issue a log record for some or all rows	Type of Message: Error Cause: TimesTen failed to issue a reclaim log message for the current batch of rows. Impact: TimesTen aborted the bulk load operation for the current batch of rows. User Action: Retry the bulk load operation for the current batch of rows.
50011	The rowsToInsert parameter was zero or invalid	Type of Message: Error Cause: TimesTen failed to issue a reclaim log message for the current batch of rows. Impact: TimesTen aborted the bulk load operation for the current batch of rows. User Action: Retry the bulk load operation for the current batch of rows.
50012	Failed to begin a transaction for bulk load operation	Type of Message: Error Cause: TimesTen failed to begin a system transaction for the bulk load operation. Impact: TimesTen aborted the bulk load operation for the current batch of rows. User Action: Retry the bulk load operation for the current batch of rows.
50013	Failed to initialize fast bulk load mode on table	Type of Message: Error Cause: TimesTen could not initialize the bulk load insert mode against the table. Impact: TimesTen cannot perform the bulk load put operation. User Action: Retry the bulk load operation.
50014	Commit size (number) must be greater than or equal to batch size (number)	Type of Message: Error Cause: You specified a commit size, number of rows, smaller than the specified batch size. Impact: TimesTen cannot perform the bulk load operation. User Action: Specify a batch size lower or equal than the commit size and retry the operation.
50015	Current batch is full, must commit before adding more	Type of Message: Error Cause: You attempted a bulk load put operation when the bulk load batch is already full. Impact: TimesTen cannot perform the bulk load put operation. User Action: Call a bulk load commit and retry the operation.
50016	Bulk load on tables with indexes currently not supported	Type of Message: Error Cause: You attempted a direct load operation on a table with indexes. Impact: TimesTen cannot perform the direct load operation. User Action: Drop the indexes from the table and retry the operation.
50017	Bulk load context is null-- must be allocated	Type of Message: Error Cause: You must allocate a direct load context before initializing a bulk load operation. Impact: TimesTen failed to initialize the direct load operation. User Action: Allocate a direct load context and retry the operation.
50018	Could not allocate dictionary tbl list for bulk load	Type of Message: Error Cause: TimesTen failed to allocate a compressed dictionary during the initialization of a direct load operation. Impact: TimesTen failed to initialize the direct load operation. User Action: Increase the amount of system virtual memory available and retry the operation. For more information on how to increase virtual memory, see Check available swap space (virtual memory) in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
50019	Could not populate dictionary tbl list for bulk load: number	Type of Message: Error Cause: TimesTen failed to populate a compressed dictionary during the initialization of a direct load operation. Impact: TimesTen failed to initialize the direct load operation. User Action: Retry the direct load operation.
50020	Could not populate value table cache for bulk load: number	Type of Message: Error Cause: TimesTen failed to populate the value table cache during the initialization of a direct load operation. Impact: TimesTen failed to initialize the direct load operation. User Action: Retry the direct load operation.
50050	External table loading failed: error_message	Type of Message: Error Cause: An error occurred during an external table loading operation. Impact: TimesTen failed to complete the external table loading operation. User Action: Review the additional message to determine the cause of the failure.
50051	External table: Failed to allocate memory	Type of Message: Error Cause: A block allocation failure caused the external table loading operation to fail. Impact: TimesTen failed to complete the external table loading operation. User Action: Increase the amount of system virtual memory available and retry the operation. For more information on how to increase virtual memory, see Check available swap space (virtual memory) in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
50052	External table: Failed to allocate blocks for message	Type of Message: Error Cause: An allocation failure caused the external table loading operation to fail. Impact: TimesTen failed to complete the external table loading operation. User Action: Increase the amount of system virtual memory available and retry the operation. For more information on how to increase virtual memory, see Check available swap space (virtual memory) in Oracle TimesTen In-Memory Database Monitoring and Troubleshooting Guide.
51000	Failed to read log marker packet	Type of Message: Error Cause: The transaction log files may be corrupted. The transaction log may have not been written properly. Impact: TimesTen failed to read the transaction log. User Action: Contact TimesTen Customer Support.
51001	Failed to locate next log record in rdlog	Type of Message: Error Cause: The transaction log files may be corrupted. The transaction log may have not been written properly. Impact: TimesTen failed to read the transaction log. User Action: Contact TimesTen Customer Support.
51002	Failed to locate next log record in strand strand_number	Type of Message: Error Cause: The transaction log files may be corrupted. The transaction log may have not been written properly. Impact: TimesTen failed to read the transaction log. User Action: Contact TimesTen Customer Support.
51003	Failed to locate next log record in the block	Type of Message: Error Cause: The transaction log files may be corrupted. The transaction log may have not been written properly. Impact: TimesTen failed to read the transaction log. User Action: Contact TimesTen Customer Support.
51004	Failed to map idmap(logical) to lsn(physical)	Type of Message: Error Cause: The transaction log files may be corrupted. The transaction log may have not been written properly. Impact: TimesTen failed to read the transaction log. User Action: Contact TimesTen Customer Support.
51005	Failed to preallocate log file log_file_name.extension with mode = mode	Type of Message: Error Cause: TimesTen cannot allocate enough space on the file system for the log file. Impact: The database cannot continue normal operations. User Action: Ensure that there is enough space on the file system to at least store a log file of the size specified in the LogFileSize attribute. For more information on the LogFileSize attribute, see LogFileSize in Oracle TimesTen In-Memory Database Reference.
51006	Failed to flush to lwn = LWN_boundary	Type of Message: Error Cause: TimesTen cannot flush the log up to the specified log write number (LWN) boundary. Impact: The database cannot continue normal operations. User Action: Contact TimesTen Customer Support.
51007	Failed to switch to lwn = LWN_boundary in strand strand_number	Type of Message: Error Cause: TimesTen cannot advance the specified log write number (LWN) boundary in the specific strand. Impact: The database cannot continue normal operations. User Action: Contact TimesTen Customer Support.
51008	Failed to insert a log marker	Type of Message: Error Cause: TimesTen cannot insert a log marker to the log buffer. Impact: The database cannot continue normal operations. User Action: Contact TimesTen Customer Support.
51011	rxWaitCTN failed for receiver_operation	Type of Message: Error Cause: A failure occurred while waiting for a CTN. Impact: TimesTen will automatically retry the operation. User Action: None.
51012	Replication of bitmap indexes is disabled in the current release (table owner_name.table_name) Contact TimesTen support.	Type of Message: Error Cause: The specified table has a bitmap index. Replication of bitmap indexes is temporarily disabled in the current version of TimesTen. Impact: TimesTen cannot replicate the specified table. User Action: Change the index type in the specified table. Contact TimesTen Customer Support for more information.
51013	Number of index key columns (owner_name) exceeds the maximum (table_name) supported by older releases.	Type of Message: Error Cause: You attempted to replicate a table with more index key columns than the number supported by the receiving table. The receiving table is of an older TimesTen release. Impact: TimesTen cannot replicate the specified table. User Action: Either upgrade the receiving table or modify the table definition to a supported number of index key columns.
51014	Invalid user session parameter value	Type of Message: Error Cause: The value supplied for the user session parameter is unknown or unsupported by TimesTen. Impact: TimesTen cannot perform the operation. User Action: Use a supported user session parameter value.
51015	Skip send of string PROFILE due to subscriber version.	Type of Message: Error Cause: Replication of profile object skipped because the subscriber version does not support it. Impact: TimesTen cannot replicate profile object. User Action: Upgrade to a TimesTen version where replication of profile objects is supported.
51016	Failed to write log record into an unpublished lwn	Type of Message: Error Cause: TimesTen cannot insert a log record into a log write number (LWN) boundary in the specific strand. Impact: The database cannot continue normal operations. User Action: Contact TimesTen Customer Support.