This chapter first explains how to retrieve errors and warnings, and then provides a comprehensive list of all errors and warnings, ordered by error number.
By default, TimesTen messages and diagnostic information are stored in:
A user error log that contains error message information. Generally, these messages contain information on actions you may need to take. The default file is timesten_home/diag/tterrors.log. For more information on modifying the location of the user error log, see "Error, warning, and informational messages" in the Oracle TimesTen In-Memory Database Operations Guide.
A support log containing everything in the user error log plus information that may be useful for TimesTen Customer Support. The default file is timesten_home/diag/ttmesg.log. For more information on modifying the location of the support log, see "Error, warning, and informational messages" in the Oracle TimesTen In-Memory Database Operations Guide.
An invalidation file containing diagnostic information when TimesTen invalidates a database. This file provides useful troubleshooting information for TimesTen Customer Support. The invalidation file is created and named based on the value specified by the DataStore connection attribute. This connection attribute is not a file name. For example on Linux platforms, if the DataStore connection attribute is /home/ttuser/AdminData, the actual invalidation file name has a suffix, .inval, /home/ttuser/AdminData.inval. For more information on the DataStore connection attribute, see "DataStore" in the Oracle TimesTen In-Memory Database Reference.
Note:
Not all error numbers are currently in use.In JDBC, the native error code and message can be retrieved as shown in this example:
Example 1-1 Native error code and message retrieval in JDBC
private static void printSQLExceptions(SQLException e)
{
while (e != null) {
System.out.println("SQLState: " +
e.getSQLState());
System.out.println("Message : " +
e.getMessage());
System.out.println("Vendor : " +
e.getErrorCode());
e.printStackTrace();
e = e.getNextException();
System.out.println("");
}
e.printStackTrace();
}
. . .
try {
// JDBC method calls here
}
catch (SQLException ex) {
ex.printSQLExceptions();
}
In ODBC the native error code and message can be retrieved with the SQLError function, as shown in the following example:
Example 1-2 Native error code and message retrieval in ODBC
#define MSG_LNG 512
SQLCHAR szSqlState[MSG_LNG]; /* SQL state string */
SQLINTEGER pfNativeError; /* Native error code */
SQLCHAR szErrorMsg[MSG_LNG];
/* Error msg text buffer pointer */
SQLSMALLINT pcbErrorMsg;
/* Error msg text Available bytes */
SQLRETURN ret = SQL_SUCCESS;
while ( ret == SQL_SUCCESS || ret == SQL_SUCCESS_WITH_INFO ) {
ret = SQLError(henv, hdbc, hstmt, szSqlState, &pfNativeError,
szErrorMsg, MSG_LNG, &pcbErrorMsg);
switch (ret) {
case SQL_SUCCESS:
fprintf(stderr, "*** %s\n*** ODBC Err = %s, ",
"TimesTen Err = %ld\n",
szErrorMsg, szSqlState, pfNativeError);
break;
case SQL_SUCCESS_WITH_INFO:
fprintf(stderr, "*** Call to SQLError failed with return ",
"code of SQL_SUCCESS_WITH_INFO.\n ",
"*** Need to increase size of ",
"message buffer.\n");
break;
case SQL_INVALID_HANDLE:
fprintf(stderr, "*** Call to SQLError failed with ",
"return code of SQL_INVALID_HANDLE.\n");
break;
case SQL_ERROR:
fprintf(stderr, "*** Call to SQLError failed with ",
"return code of SQL_ERROR.\n");
break;
case SQL_NO_DATA_FOUND:
break;
}
}
It is possible for a single ODBC or JDBC operation to generate multiple errors. These errors can be retrieved using multiple calls to the ODBC function SQLError or the JDBC method SQLException.
TimesTen OCI and Pro*C applications, and those that use PL/SQL, report errors using Oracle database error codes instead of TimesTen error codes. The error messages that accompany the error codes may come from the TimesTen error catalog or the Oracle database error catalog.
TimesTen optionally generates warnings in the range of 20000 and 29999 that describe basic diagnostic information for a particular connection. The generation of these messages is determined by the general connection attribute Diagnostics. For details, see "Diagnostics" in Oracle TimesTen In-Memory Database Reference.
There is no means to control the generation of any other warnings or errors listed in this chapter.
If an error is prefixed with "Warning," the command completes but has a side effect the user should know about. For all other errors, the command terminates abnormally.
Note:
A C language header file containing symbolic names for the various TimesTen internal error codes is shipped with TimesTen. It is namedtt_errCode.h and is installed in:timesten_home/install/include on Linux or UNIXtimesten_home\install\include on WindowsODBC 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:
| 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 "Backup, Restore, and Migrate Data in TimesTen Classic" in the 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 |
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 "Backup, Restore, and Migrate Data in TimesTen Classic" in the 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 "Backup, Restore, and Migrate Data in TimesTen Classic" in the 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 Impact: The User Action: Retry the operation using the |
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 connections. 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 the 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 Impact: TimesTen cannot perform the operation. User Action: Ensure that the |
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 |
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 Impact: The specified table cannot be configured for parallel insert mode. User Action: Wait and retry the operation. Consider terminating the existing |
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 |
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 Impact: TimesTen cannot to create a backup copy of the database. User Action: Attempt to create another backup of the database with the |
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 |
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 Impact: The table you specified cannot be configured for parallel insert mode. User Action: Wait and retry the operation. Consider terminating the existing |
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 Impact: None. User Action: None. |
622 |
User user_name does not have
group permission to connect
to database
|
Type of Message: Error
Cause: TimesTen cannot access the database files because the specified user does not have sufficient operating system file access permissions. Impact: TimesTen cannot connect to the database. User Action: Grant operating system file access permissions to the specified user. For more information, see "Understanding the TimesTen users group" in the Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide. |
623 |
User user_name does not have
group permission to create
database
|
Type of Message: Error
Cause: TimesTen cannot access the database files because the specified user does not have sufficient operating system file access permissions. Impact: TimesTen cannot load or destroy the database. User Action: Grant operating system file access permissions to the specified user. For more information, see "Understanding the TimesTen users group" in the Oracle TimesTen In-Memory Database Installation, Migration, and Upgrade Guide. |
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 Impact: You cannot connect to the database. User Action: Modify the value of the |
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 the 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 |
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 the 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 |
652 |
Backup directory does not exist |
Type of Message: Error
Cause: The backup path you specified with the Impact: The backup cannot be performed. User Action: Create or specify a valid backup directory. For more information about the |
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 Impact: The operation cannot be completed. User Action: Make sure you are performing |
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 the 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 the 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 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 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 |
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 |
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:
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 Impact: TimesTen cannot set the specified User Action: Increase the size of the |
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 The value of Impact: Parallel replication is not configured. User Action: In the DSN For more information about |
668 |
LogBufParallelism value of value cannot be smaller than ReplicationParallelism value of value |
Type of Message: Error
Cause: The value of the Impact: TimesTen cannot create or connect to the database. User Action: Change the value of the |
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 the 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 the 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 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 |
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 Impact: The 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 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 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 the 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 |
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 the Oracle TimesTen In-Memory Database Operations Guide.
|
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 |
715 |
Unable to access log directory 'directory_name'. OS-detected error: error_details |
Type of Message: Internal Error
Cause: The path specified in the Impact: TimesTen cannot perform the requested connect or disconnect operation. User Action: Change the |
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:
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 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 |
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 User Action: You must terminate your transaction. For more information, see "Transaction autocommit behavior" in the 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 User Action: Set the transaction log file size to a smaller value than the maximum allowed limit. For more information, see "LogFileSize" in the 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 User Action: Set the transaction log file size to a bigger value than the minimum allowed limit. For more information, see "LogFileSize" in the 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 Impact: TimesTen cannot create or connect to the database. User Action: Set the |
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 the 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 |
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 |
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 |
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 the 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 |
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 Impact: TimesTen cannot create the database or failed to establish a connection to the database. User Action: Increase the value for the |
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 |
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 ( Impact: TimesTen cannot create or connect to the specified database. User Action: Destroy the temporary database with the |
829 |
Bad options: Cannot copy logging options if first connection |
Type of Message: Error
Cause: The Impact: TimesTen cannot create or connect to the database. User Action: Set the |
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 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 the 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 the Oracle TimesTen In-Memory Database 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 - 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 - 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 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 the Oracle TimesTen In-Memory Database 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 - The application does not have access to the shared memory segment. In this case the system error code is - 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 - The attach exceeds the system limit on the number of shared memory segments for the process. In this case the system error code is - 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 the Oracle TimesTen In-Memory Database 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 - 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 - 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 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 the Oracle TimesTen In-Memory Database 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 - To unload the database from memory, use the - To set the RAM policy to - If you do not want to overwrite an existing database, set the |
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
limit datasize n
For
ulimit -d n
For
ulimit -d n
# this is kbytes
Bourne shells ( |
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 - There is no shared memory segment attached at - 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
numberset(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 the Oracle TimesTen In-Memory Database Replication Guide. For additional help, contact TimesTen Customer Support. |
849 |
Recovery failed on
numberset(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 |
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 |
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 the Oracle TimesTen In-Memory Database Reference. |
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 Impact: TimesTen cannot perform the operation. User Action: Consider using the |
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 |
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 the 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 the Oracle TimesTen In-Memory Database Reference. Impact: You cannot create or connect to the database. User Action: Call the |
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 the 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 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 |
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 the Oracle TimesTen In-Memory Database Troubleshooting Guide. Once you have made more file system 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, 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. |
| 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 |
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 the 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 illegal characters
|
Type of Message: Error
Cause: The specified identifier contains illegal 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 |
Illegal 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 the 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 the 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. |
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 Impact: TimesTen cannot perform the operation. User Action: Set the column number in the |
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 the 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 Impact: TimesTen cannot perform the operation. User Action: Ensure that you specify valid table names and that you specify referenced tables in the |
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 Impact: TimesTen cannot perform the operation. User Action: Specify a number of column names in the |
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 legal 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 |
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 the 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 Impact: TimesTen cannot perform the operation. User Action: Specify a correct |
1061 |
PRIMARY KEY syntax can only be used once in statement |
Type of Message: Error
Cause: You specified more than one Impact: TimesTen cannot perform the operation. User Action: Ensure that your SQL statement only contains one For more information, see "Primary keys, foreign keys and unique indexes" in the 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 Impact: TimesTen cannot perform the operation. User Action: Verify the |
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 Impact: TimesTen cannot create the table. User Action: Specify the foreign key constraint to use for the |
1065 |
No matching foreign key constraint for 'distribute by reference'. |
Type of Message: Error
Cause: You attempted to create a table with a Impact: TimesTen cannot create the table. User Action: Verify the foreign key name specified in the |
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 Impact: TimesTen cannot create the table. User Action: Ensure that the parent table in the |
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 Impact: TimesTen cannot create the table. User Action: Ensure that you include in the |
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 Impact: TimesTen cannot create the table. User Action: Ensure that the child foreign key columns specified for the |
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 the 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 Impact: TimesTen cannot perform the operation User Action: Specify the foreign key constraint to use for the |
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 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 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. |
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 Impact: TimesTen cannot convert the value to a User Action: Ensure that the Oracle database |
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 Impact: TimesTen cannot perform the operation. User Action: Ensure that the For more information on the |
1107 |
Error in converting sysdate to Date. |
Type of Message: Error
Cause: You specified an Oracle database Impact: TimesTen cannot convert the value to a User Action: Ensure that the Oracle database |
1108 |
Error in converting Oracle rowid to TimesTen rowid. |
Type of Message: Error
Cause: TimesTen encountered an invalid or improperly formatted Oracle database Impact: TimesTen cannot convert the Oracle database User Action: Specify a valid Oracle database |
1109 |
Error converting char to ROWID |
Type of Message: Error
Cause: TimesTen encountered an invalid or improperly formatted Impact: TimesTen cannot convert the User Action: Specify a valid |
1110 |
FOR UPDATE with aggregate function is deprecated |
Type of Message: Warning
Cause: You specified a Impact: None. User Action: Consider rewriting your SQL query. For more information on the |
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 Impact: TimesTen cannot convert the 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 Impact: TimesTen cannot convert the User Action: Specify a valid |
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 User Action: Consider using a For more information on the |
1120 |
SQL command does not exist. |
Type of Message: Error
Cause: You specified a SQL unique identifier ( Impact: TimesTen cannot perform the operation. User Action: Ensure that you specify a correct For more information on the |
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. |
1200 |
Invalid transaction ID was specified |
Type of Message: Error
Cause: You specified an incorrect transaction ID ( Impact: TimesTen cannot roll back the transaction. User Action: Ensure that when you call the |
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 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 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 the 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 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 |
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 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 |
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 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 the 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 |
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 |
Illegal 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. |
1851 |
Operation on a passthrough LOB is not supported |
Operations such as ConvertToClob and ConvertToBlob are not supported. |
| 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 the 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 the 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 the 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 the 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 the 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2214 |
Column cannot be named ROWID |
Type of Message: Error
Cause: You specified the Impact: TimesTen did not perform the operation. User Action: Do not specify |
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 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 the 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 Impact: TimesTen did not perform the User Action: Retry the |
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 |
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 |
2230 |
View view_name not valid
input to ttSize
|
Type of Message: Error
Cause: You attempted to run or call the Impact: TimesTen failed to run or call the 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 the 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 the 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 the 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 |
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 Impact: TimesTen did not perform the operation. User Action: Specify |
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 the 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 the 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 the 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 |
2242 |
Invalid value for MAXVALUES in 'COMPRESS BY DICTIONARY' clause |
Type of Message: Error
Cause: You entered an incorrect value for the Impact: TimesTen did not perform the operation. User Action: Specify the |
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 the 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 |
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 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 the 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 Impact: TimesTen did not perform the alter statement. User Action: Do not specify a previously defined column in the compression clause of the |
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 Impact: TimesTen did not update the table. User Action: Reissue the |
2250 |
New column name column_name
duplicates existing column
name
|
Type of Message: Error
Cause: You attempted to 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 the 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 the Oracle TimesTen In-Memory Database Operations Guide. |
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 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 |
2376 |
Duplicate entries in FROM clause |
Type of Message: Error
Cause: You specified the same table name more than once in the Impact: TimesTen did not perform the User Action: Perform the |
2400 |
Number of columns (number) exceeds the maximum (number) |
Type of Message: Error
Cause: You attempted to 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 |
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 Impact: The 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 the 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 the 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 the 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 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 the 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 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 the 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 the 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 Impact: You cannot use the User Action: When you use the For more information on |
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 Impact: You cannot use the User Action:
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 Impact: TimesTen did not create a primary key on the specified column because it is in a secondary partition. User Action: Use |
2420 |
Number of values specified in INSERT statement exceeds number of columns in table |
Type of Message: Error
Cause: You attempted an Impact: TimesTen did not perform the User Action: Perform the |
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 Impact: TimesTen did not perform the User Action: Re-issue the |
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 Impact: TimesTen did not perform the operation. User Action: Retry the operation, making sure to specify a valid precision for the |
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 Impact: TimesTen did not perform the operation. User Action: Retry the operation, making sure to specify a valid scale for the |
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 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 |
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 the 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 the 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 |
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 the 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 the 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 |
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 the 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 the 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 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 the 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: You did not use an integer value for the parameter, which is expected by the operation. Impact: TimesTen cannot complete the operation. User Action: Use an 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 Impact: TimesTen did not perform the conversion. User Action: Check the conversion rules for converting a character string to a |
2607 |
Error converting from
character string 'string' to
time
|
Type of Message: Error
Cause: TimesTen encountered a conversion error when converting a Impact: TimesTen did not perform the operation. User Action: Check the conversion rules for converting a |
2608 |
Error converting from
character string 'string' to
timestamp
|
Type of Message: Error
Cause: TimesTen encountered a conversion error when converting a Impact: TimesTen did not perform the operation. User Action: Check the conversion rules for converting a |
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 the 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 the 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 User Action: Ensure that the |
2617 |
Error converting Oracle date to Oracle timestamp |
Type of Message: Error
Cause: The data type conversion failed. Impact: You cannot convert the User Action: Ensure that the |
2618 |
Error converting Oracle timestamp to TT_TIMESTAMP |
Type of Message: Error
Cause: The data type conversion failed. Impact: You cannot convert the User Action: Ensure that the |
2619 |
Error converting Oracle timestamp to Oracle date |
Type of Message: Error
Cause: The data type conversion failed. Impact: You cannot convert the User Action: Ensure that the |
2620 |
Error converting TT_TIMESTAMP to Oracle date |
Type of Message: Error
Cause: The data type conversion failed. Impact: You cannot convert the User Action: Ensure that the |
2621 |
Error converting TT_TIMESTAMP to Oracle timestamp |
Type of Message: Error
Cause: The data type conversion failed. Impact: You cannot convert the User Action: Ensure that the |
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 the Oracle TimesTen In-Memory Database SQL Reference. |
2623 |
Invalid number |
Type of Message: Error
Cause: You specified an invalid value for the Impact: TimesTen did not perform the operation. User Action: Specify a correct value for the |
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 Impact: TimesTen did not perform the User Action: Perform the operation again making sure to include columns in the |
2706 |
Query not in select distinct
list
|
Type of Message: Error
Cause: You issued a query using the Impact: TimesTen did not execute the query. User Action: Review the query making sure the columns specified in the |
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 Impact: TimesTen did not invoke the function. User Action: Invoke the aggregate function and ensure that the |
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 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 the 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 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 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 the 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 |
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 |
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 Impact: TimesTen did not perform the operation. User Action: Check the |
2781 |
Pages value must be greater
than zero and less than
number
|
Type of Message: Error
Cause: You specified an inappropriate value for the Impact: TimesTen did not perform the operation. User Action: Specify a constant value that is greater than 0 for the |
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 Impact: TimesTen did not perform the User Action: Run the |
2784 |
Column column_name has no
default value defined
|
Type of Message: Error
Cause: You attempted to specify the Impact: TimesTen did not perform the User Action: Make sure the default clause has been defined on the column used in the |
2785 |
Column column_name has no
unique constraint
|
Type of Message: Error
Cause: You attempted to issue an 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 |
2786 |
Column column_name already
has unique constraint
|
Type of Message: Error
Cause: You attempted to issue an 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 |
2787 |
DateTime arithmetic error.
error_details
|
Type of Message: Error
Cause: You attempted a date time arithmetic operation that resulted in an invalid 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 the 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 |
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 the 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 the 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 Impact: TimesTen did not perform the operation. User Action: Retry the |
2792 |
All updated columns must belong to updated table |
Type of Message: Error
Cause: You issued an Impact: TimesTen did not perform the User Action: Retry the |
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 |
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 the 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 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 |
2796 |
ON COMMIT option is only supported with temporary tables |
Type of Message: Error
Cause: You specified the 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 the 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 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 the 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 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 |
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 Impact: TimesTen did not create the index. User Action: Recreate the linguistic index using the same |
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 Impact: TimesTen did not create the index. User Action: Recreate the linguistic index making sure to specify a constant |
2806 |
Invalid NLS parameter for
NLSSORT function sort_value
|
Type of Message: Error
Cause: You attempted to create a linguistic index using the Impact: TimesTen did not create the index. User Action: Check the |
2807 |
Oracle timestamp precision overflow |
Type of Message: Error
Cause: An Impact: TimesTen cannot perform the operation. User Action: Ensure that the source and target columns of type |
2809 |
Invalid interval |
Type of Message: Error
Cause: You specified an invalid string format for the Impact: TimesTen did not perform the operation. User Action: Specify the |
2811 |
Not a group by expression |
Type of Message: Error
Cause: You attempted to use an expression that is not in the Impact: TimesTen did not execute the query. User Action: Check your query making sure columns in the expression are included in the |
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 Impact: TimesTen did not perform the operation or did not invoke the User Action: Retry the operation or function making sure to specify a valid character string. For more information, see "TO_DATE" in the 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 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 the 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 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 the 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 the 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 the 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 the 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 the Oracle TimesTen In-Memory Database Reference. |
2820 |
Invalid USERENV parameter |
Type of Message: Error
Cause: You specified an invalid parameter to the Impact: TimesTen did not invoke the function. User Action: Check the supported values for the parameters of the |
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 the 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 Impact: TimesTen cannot execute the SQL statement. User Action: Rewrite the |
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 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 |
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 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 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 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 |
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 Impact: The compilation or execution failed. User Action: Modify the application code, making sure the statement handle bound to the |
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 the 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2903 |
Illegal 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 Impact: TimesTen did not perform the operation. User Action: Check the string used in the number format. If you are attempting to invoke a |
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 Impact: TimesTen did not perform the operation. User Action: Check the string used in the date format. If you are attempting to invoke the |
2906 |
Bad number format |
Type of Message: Error
Cause: You specified an invalid number format. One cause could be an improper use of the Impact: TimesTen did not perform the operation. User Action: Check the number format. If you are attempting to invoke a |
2907 |
Bad date format |
Type of Message: Error
Cause: You specified an invalid date format. One cause could be an improper use of the Impact: TimesTen did not perform the operation. User Action: Check the date format. If you are attempting to invoke a |
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 Impact: TimesTen did not perform the operation. User Action: Check the decimal and character string. If you are attempting to invoke a |
2909 |
Error Converting numeric 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 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 |
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 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 |
2911 |
Float underflow for TO_CHAR function |
Type of Message: Error
Cause: You attempted to invoke the Impact: TimesTen did not perform the operation. User Action: Check the invalid floating-point value and the character string passed as arguments to the |
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 the 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 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 the 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 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 the 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 Impact: TimesTen did not perform the update operation. User Action: Check the subquery used in the |
2916 |
Not enough values in the subquery of the set clause |
Type of Message: Error
Cause: You attempted to issue a join Impact: TimesTen did not perform the update operation. User Action: Check the subquery used in the |
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 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 Impact: TimesTen did not perform the operation. User Action: Redefine the column definition specifying the correct precision for the |
2919 |
Scale of number type is out of range [-84,127] |
Type of Message: Error
Cause: You attempted to define the Impact: TimesTen did not perform the operation. User Action: Redefine the column definition specifying the correct scale for the |
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 Impact: TimesTen did not perform the operation. User Action: Review the result data type and the precision and scale you defined for the |
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 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 the 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 |
2923 |
Number type value overflow |
Type of Message: Error
Cause: You specified a value for the 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 |
2924 |
Number type value underflow |
Type of Message: Warning
Cause: You specified a value for the 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2925 |
Overflow converting number to char |
Type of Message: Error
Cause: TimesTen attempted to convert a Impact: TimesTen did not perform the operation. User Action: Check the parameters of the |
2926 |
Underflow converting number to char |
Type of Message: Warning
Cause: TimesTen attempted to convert a Impact: TimesTen issued a warning, completed the operation, but rounded the result to 0. User Action: Check the parameters of the |
2927 |
Error converting Number to Char |
Type of Message: Error
Cause: TimesTen attempted a conversion of a 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 the 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 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2929 |
Error converting Number to Double |
Type of Message: Error
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2930 |
Error converting Number to Float |
Type of Message: Error
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2931 |
Overflow converting Number to TinyInt |
Type of Message: Error
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2932 |
Underflow converting Number to TinyInt |
Type of Message: Warning
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2933 |
Error converting Number to TinyInt |
Type of Message: Error
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2934 |
Overflow converting Number to SmallInt |
Type of Message: Error
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2935 |
Underflow converting Number to SmallInt |
Type of Message: Warning
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2936 |
Error converting Number to SmallInt |
Type of Message: Error
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2937 |
Overflow converting Number to Int |
Type of Message: Error
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2938 |
Underflow converting Number to Int |
Type of Message: Warning
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2939 |
Error converting Number to Int |
Type of Message: Error
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2940 |
Overflow converting Number to BigInt |
Type of Message: Error
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2941 |
Underflow converting Number to BigInt |
Type of Message: Warning
Cause: TimesTen attempted a conversion of a 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2942 |
Error converting Number to BigInt |
Type of Message: Error
Cause: TimesTen attempted a conversion of a 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 the 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 |
2944 |
Invalid number format model |
Type of Message: Error
Cause: You specified an invalid number format model for the 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 the 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 |
2946 |
Truncation occurred converting Number to Char |
Type of Message: Warning
Cause: The result is truncated when converting from Impact: The result of your operation may be less precise than the original number value. User Action: Allocate a larger For more information on the |
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 the 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 the 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 Impact: TimesTen did not perform the User Action: Check the details of the error message to retrieve the |
2951 |
The table being merged into cannot be used for insert values |
Type of Message: Error
Cause: You attempted a Impact: TimesTen did not perform the operation. User Action: Check the semantics of the |
2952 |
Source table table_name
cannot be updated
|
Type of Message: Error
Cause: You attempted a 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 |
2953 |
Columns referenced in the ON Clause cannot be updated |
Type of Message: Error
Cause: You attempted a Impact: TimesTen did not perform the operation. User Action: Check the semantics of the |
2954 |
Column in update whereclause is not in either source or target table |
Type of Message: Error
Cause: You attempted a Impact: TimesTen did not perform the operation. User Action: Check the column reference in the |
2955 |
Column in insert whereclause cannot refer to target table |
Type of Message: Error
Cause: You attempted a Impact: TimesTen did not perform the operation. User Action: Check the column reference in the |
2956 |
Column in insert whereclause is not in source table |
Type of Message: Error
Cause: You attempted a Impact: TimesTen did not perform the operation. User Action: Check the column reference in the |
2957 |
Bad insert value |
Type of Message: Error
Cause: You attempted to insert an invalid value in the 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 the 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 ( Impact: TimesTen did not perform the operation. User Action: Do not use set operators in the source table of the |
2960 |
Scale of timestamp type is out of range [0,9] |
Type of Message: Error
Cause: You specified an invalid scale for the Impact: TimesTen did not perform the operation. User Action: Check the semantics of the |
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 the 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 the 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 the Oracle TimesTen In-Memory Database SQL Reference. |
2970 |
Decode syntax error: not enough operands |
Type of Message: Error
Cause: You attempted to invoke the Impact: TimesTen did not invoke the function. User Action: Specify at least three arguments for the |
2971 |
Coalesce syntax error: need at least two operands |
Type of Message: Error
Cause: You attempted to invoke the Impact: TimesTen did not invoke the function. User Action: Specify at least two expressions as arguments for the |
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 SELECT * FROM t WHERE (a,b) IN ((1,1),(2)); In this example, the second group of values in the 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 the 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 SELECT * FROM t1 WHERE (a,b) IN (SELECT c FROM t2); In this example, the group of values returned in the 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 the 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 Impact: TimesTen did not perform the query. User Action: Review the |
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 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 the 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 Impact: TimesTen did not perform the create or alter operation. User Action: If the column used for time-based aging is of type |
2978 |
Transparent load value must be between 0 and 2 |
Type of Message: Error
Cause: You specified an invalid value for the Impact: TimesTen did not perform the operation. User Action: Change the value of the |
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 the 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 the 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 Impact: TimesTen could not perform the operation. User Action: Redefine the table and specify the column used for time-based aging as type |
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 the 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 the 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 the 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 the 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 the 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 the 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 the 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 the 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 the 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 the 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 Impact: TimesTen did not perform the operation. User Action: Redefine the table making sure to specify |
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 the 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 the 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 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 the 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 the Oracle TimesTen Application-Tier Database Cache User's 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 |
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 the Oracle TimesTen In-Memory Database SQL Reference. |
| 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 the 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 the 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 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 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 is not allowed. Foreign key on cached tables is 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 Impact: The SQL operation fails. User Action: Ensure that at least one of the arguments is not |
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 ( |
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 Impact: TimesTen cannot perform the SQL operation. User Action: Use |
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. This error is returned when an 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 |
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 |
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 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 |
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 |
3021 |
LRU aging policy for a readonly cache group is allowed only if the cache group is dynamic |
Type of Message: Error
Cause: You specified an LRU aging policy on an 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 the 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 Impact: The SQL statement is not executed. User Action: For more information, see "REFRESH CACHE GROUP" in the 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 Impact: TimesTen cannot perform the SQL operation. User Action: Use For more information on partitions, see "ALTER TABLE" in the 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 Impact: TimesTen cannot perform the SQL operation. User Action: Specify your function and include the |
3026 |
ORDER BY is not allowed with analytic aggregation with distinct |
Type of Message: Error
Cause: You attempted to specify the Impact: TimesTen cannot perform the SQL operation. User Action: Specify your function, omitting either the |
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 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 endpoint 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 endpoint value. Impact: TimesTen cannot perform the SQL operation. User Action: Check your start point and endpoint 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 Impact: TimesTen cannot perform the SQL operation. User Action: Specify the analytic function, including the function in the |
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 the 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 Impact: TimesTen cannot perform the operation. User Action: Invoke your function without specifying |
3040 |
GROUPING function only supported with GROUP BY |
Type of Message: Error
Cause: You attempted to specify a grouping function such as Impact: TimesTen cannot perform the SQL operation. User Action: Modify your query by specifying the grouping function as part of the |
3041 |
Number of groupings exceeds the maximum (2147483648) |
Type of Message: Error
Cause: You specified a number of groupings in the 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 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 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 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 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 Impact: TimesTen cannot perform the SQL operation. User Action: Remove one of the references from your |
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 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 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 the 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 the 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 the 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 the 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 then 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 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 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 the 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 Impact: TimesTen cannot execute the SQL statement. User Action: Do not use the |
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 Impact: TimesTen cannot execute the SQL statement. User Action: Do not use the |
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, 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 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: 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 Impact: TimesTen cannot execute the SQL statement. User Action: Use a positive value for the |
3106 |
FIRST keyword cannot be used in subquery |
Type of Message: Error
Cause: You attempted to use the 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 ( 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 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 |
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 the 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 |
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 the 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 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 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 |
3120 |
View view_name does not exist
|
Type of Message: Error
Cause: You attempted to drop a non-existent view using the Impact: TimesTen cannot execute the SQL statement. User Action: Examine the views and drop a view that exists. For more information on the |
3121 |
A cache group table
table_name cannot be
referenced in a materialized
view
|
Type of Message: Error
Cause: Your Impact: TimesTen cannot execute the SQL statement. User Action: Do not reference cache group tables in your |
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 the Oracle TimesTen In-Memory Database SQL Reference. |
3124 |
Cannot create a view that references a system table |
Type of Message: Error
Cause: Your Impact: TimesTen cannot execute the SQL statement. User Action: Do not reference system tables or views in your |
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 an invalid column name. 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 Impact: TimesTen cannot execute the SQL statement. User Action: Use the |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 Impact: TimesTen cannot execute the SQL statement. User Action: Use the |
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 |
3145 |
view_name is not an
Asynchronous Materialized
View
|
Type of Message: Error
Cause: The view name provided in the 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 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 Impact: TimesTen cannot execute the SQL statement. User Action: Ensure that the |
3148 |
No Primary Key in the detail
table table_name. Specify
ROWID option for the
Materialized View Log
|
Type of Message: Error
Cause: The Impact: TimesTen cannot execute the SQL statement. User Action: Use the |
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 |
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 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 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 |
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 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 Impact: TimesTen cannot execute the SQL statement. User Action: To fix an invalid materialized view, re-grant |
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 Impact: TimesTen cannot execute the SQL statement. User Action: To fix an invalid materialized view, re-grant |
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 |
Illegal max value. Possible reasons: maximum/minimum limit, or max < min |
Type of Message: Error
Cause: You specified a Impact: TimesTen cannot create the sequence object. User Action: Specify a value for the |
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 Impact: TimesTen cannot perform the operation. User Action: Do not use |
3207 |
CURRVAL or NEXTVAL not allowed in subquery of update, delete or select |
Type of Message: Error
Cause: The specified sequence value Impact: TimesTen cannot perform the operation. User Action: Do not use |
3208 |
CURRVAL or NEXTVAL not allowed in where clause |
Type of Message: Error
Cause: The specified sequence value Impact: TimesTen cannot perform the operation. User Action: Do not use |
3209 |
CURRVAL or NEXTVAL is not supported in views |
Type of Message: Error
Cause: The specified sequence value Impact: TimesTen cannot perform the operation. User Action: Do not use |
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 Impact: TimesTen cannot complete the operation. User Action: Use the |
3211 |
CURRVAL may not be referenced before NEXTVAL in this session |
Type of Message: Error
Cause: You attempted to reference Impact: TimesTen cannot complete the operation. User Action: Before you use |
3212 |
Failed to get the NEXTVAL |
Type of Message: Error
Cause: Possible causes for this error message are:
Impact: TimesTen is unable to obtain a 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 Impact: TimesTen cannot complete the operation. User Action: Review the |
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:
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: Another session changed the enhanced write concurrency mode 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 |
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 |
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 Impact: The enhanced write concurrency mode transition started and will continue until all SQL statements in transition are executed. The User Action: Use the |
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 |
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 |
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 Alternatively, consider setting the |
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 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 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 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 Impact: TimesTen cannot perform the operation. User Action: Remove the foreign key clause from your statement or create a foreign key using the |
3305 |
Invalid number of column names specified |
Type of Message: Error
Cause: Possible causes for this error are:
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 |
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 the 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 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 Impact: TimesTen cannot perform the operation. User Action: Specify |
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 the 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 been 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 Impact: The current operation failed. User Action: Set |
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 Impact: The current operation failed. User Action: Set |
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 |
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 the Oracle TimesTen In-Memory Database 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 |
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 database's distribution map. For more information, see "Removing elements from the distribution map" in the 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 the Oracle TimesTen In-Memory Database 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 the 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 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 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 |
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 |
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: The 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 transient error |
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 failed element's replicas. 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 TimesTen Scaleout membership service" in the 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 an 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 Impact: TimesTen failed to export the database. User Action: Review the daemon log for further details on the issue, and retry the |
3720 |
Backup failed: Error
error_code returned from
ttBackup
|
Type of Message: Error
Cause: The Impact: TimesTen failed to back up the database. User Action: Review the daemon log for further details on the issue, and retry the |
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 the 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 Impact: TimesTen failed to 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 the Oracle TimesTen In-Memory Database Troubleshooting Guide. |
3725 |
dbImport failed during
restore rows phase: Error
error_code returned from
ttMigrate
|
Type of Message: Error
Cause: The 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 the Oracle TimesTen In-Memory Database Troubleshooting Guide. |
3726 |
dbImport failed during finale
phase: Error error_code
returned from ttMigrate
|
Type of Message: Error
Cause: The Impact: TimesTen failed to 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 the Oracle TimesTen In-Memory Database 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 restore the database. User Action: Use the |
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 the Oracle TimesTen In-Memory Database 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 the 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 the 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 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 the 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 administration worker could not handle the request. Impact: The current element's recovery will fail, and the element will transition into an 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. |
| Error number | Error or warning message | Details |
|---|---|---|
4053 |
Internal error: error_message
|
Type of Message: Error
Cause: An internal error occurred. Review the Impact: Review the User Action: Review the |
4054 |
Internal warning:
warning_message
|
Type of Message: Warning
Cause: An internal warning occurred. Review the Impact: Review the User Action: Review the |
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. |
4501 |
Database cannot checkpoint to a network file system |
Type of Message: Error
Cause: You attempted to perform a checkpoint operation while your Impact: The checkpoint operation failed. User Action: Change the |
4502 |
Database cannot log to a network file system |
Type of Message: Error
Cause: TimesTen attempted to create database logs while your Impact: TimesTen cannot create database logs. User Action: Change the |
4600 |
Error min_range and max_range |
Type of Message: Error
Cause: You specified argument values that are not within the permitted Impact: TimesTen cannot complete the operation. User Action: Specify argument values that are within the permitted |
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. |
| 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 |
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 |
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 Impact: Without the User Action: Ensure that the |
5011 |
Oracle(OCI8) call failed |
Type of Message: Error
Cause: The TimesTen cache agent got an error on an Oracle database ( 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 the Oracle TimesTen In-Memory Database 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 "Set the cache administration user name and password" in the Oracle TimesTen Application-Tier Database Cache User's Guide and "Unable to validate the Oracle database user name and password" in the Oracle TimesTen In-Memory Database 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 "Set the cache administration user name and password" in the Oracle TimesTen Application-Tier Database Cache User's 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 the Oracle TimesTen Application-Tier Database Cache User's 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 |
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 Impact: The cache table may not have been populated correctly during the 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 |
5046 |
Commit/rollback required after Cache operation |
Type of Message: Error
Cause: An error occurred after executing a 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 Impact: The cache group is not defined. User Action: Either limit the column names or decrease the number of tables so that the |
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 |
5052 |
Cache group name required with install_flag value 1 |
Type of Message: Error
Cause: No Impact: The User Action: Provide the cache group name when specifying a value 1 for the |
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 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 ( |
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 Impact: The argument was ignored and the User Action: If used within a script, eliminate the unnecessary argument. For more information on the |
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 "Working with transactions" in the 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 the Oracle TimesTen In-Memory Database Troubleshooting Guide. |
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:
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 |
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 the 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 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 the Oracle TimesTen Application-Tier Database Cache User's 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 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 Application-Tier Database Cache User's 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 Application-Tier Database Cache User's 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 |
Illegal WHERE clause for
cache table table_name
|
Type of Message: Error
Cause: The Impact: You cannot use the User Action: Verify that the |
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 Impact: None. User Action: Ensure that the data type and its precision conform. See "Numeric data types" in the 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 the Oracle TimesTen In-Memory Database 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 Impact: The cache group is created. However, the cache group operations are restricted to full cache group User Action: See "Cache groups and cache tables" in the Oracle TimesTen Application-Tier Database Cache User's 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 User Action: Ensure that the data type mapping conforms to compatibility requirements as documented in "Mappings between Oracle Database and TimesTen data types" in the Oracle TimesTen Application-Tier Database Cache User's 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 the Oracle TimesTen Application-Tier Database Cache User's 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: 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 the Oracle TimesTen Application-Tier Database Cache User's Guide. Ensure that the data type mapping conforms to compatibility requirements as documented in "Mappings between Oracle Database and TimesTen data types" in the Oracle TimesTen Application-Tier Database Cache User's 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 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 |
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 the Oracle TimesTen Application-Tier Database Cache User's 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 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 ( 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 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 Impact: The operation fails. User Action: Avoid using Oracle Synonyms in the |
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 |
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 Impact: TimesTen cannot complete the operation. User Action: Avoid using public synonyms in the |
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 |
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- 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 Impact: The operation fails. User Action: Either remove the |
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 Impact: TimesTen cannot complete the operation. User Action: Either |
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 Impact: The operation fails. User Action: Either |
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 the Oracle TimesTen Application-Tier Database Cache User's 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 replication agent's startup, 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 owned by another user in the Oracle database. Impact: The operation fails. User Action: Try one of the following actions:
|
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 the cache administration user and the cache manager user" in the Oracle TimesTen Application-Tier Database Cache User's 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 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 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 can be either an error or 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 that 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 Impact: TimesTen cannot complete the operation. User Action: Specify the |
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 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. |
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 statement's syntax, 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 restart it if it is not running. |
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 the 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.
For more information, see "ttCacheUidPwdSet" or "ttAdmin" in the 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 the execution of 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 the Oracle TimesTen In-Memory Database 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 |
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 the 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 Impact: TimesTen cannot complete the operation. User Action: Specify the correct |
5263 |
owner_name.table_name is not an autorefresh cache group. |
Type of Message: Error
Cause: The cache or replication agent tried to store 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 Impact: TimesTen cannot complete the operation. User Action: Specify the |
5265 |
Internal error: error_details
|
Type of Message: Error
Cause: An unknown internal error occurred. See the provided message for details. Impact: The severity of the impact is unknown and requires an 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 the Oracle TimesTen In-Memory Database 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 the Oracle TimesTen Application-Tier Database Cache User's 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 groups. 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 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 in the incorrect autorefresh state for the operation you are attempting to perform. Impact: TimesTen cannot complete the operation. User Action: Use the |
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 already 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 Impact: TimesTen cannot complete the operation. User Action: Call the |
5283 |
Autorefresh did not complete within 24 hours |
Type of Message: Error
Cause: When called with 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 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 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 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 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 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 the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on creating a cache group, see "Creating a cache group" in the Oracle TimesTen Application-Tier Database Cache User's 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:
|
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:
|
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 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 |
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 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 |
5302 |
The Load From Oracle feature cannot be used with passthrough level 3 |
Type of Message: Error
Cause: The Impact: The call to the built-in procedure or command failed. User Action: Specify a For more information on the |
5303 |
Create table statement generated is too long |
Type of Message: Error
Cause: The built-in procedure or command generated a Impact: The generated User Action: Modify the Oracle database SQL statement to shorten the length of the generated For more information on the |
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 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 |
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 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 |
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 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 |
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 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 For more information on the |
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 Impact: The call to the built-in procedure or command failed. User Action: Loading data into TimesTen temporary tables is not supported by the For more information on the |
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 Impact: The call to the built-in procedure or command failed. User Action: Loading data into TimesTen dictionary tables is not supported by the |
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 partial. 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 the truncation of
Impact: User Action: Review the daemon log for more details about the warning. If you require TimesTen to check for |
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 ( |
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 the Oracle TimesTen In-Memory Database Troubleshooting Guide. Impact: The cache agent will retry this operation later. Review the daemon log for any additional impact. User Action: Review the daemon log for any information on 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 |
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 Impact: TimesTen did not complete the loading operation. User Action: Review and modify the options specified and re-call the |
5329 |
If the readers clause is specified, the parallel clause must also be specified. |
Type of Message: Error
Cause: You attempted to execute a Impact: TimesTen did not complete the load or refresh cache group operation. User Action: Specify a |
5330 |
Readers value must be at least one |
Type of Message: Error
Cause: You attempted to execute a Impact: TimesTen did not complete the load or refresh cache group operation. User Action: Specify a value of at least one for the |
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 - - 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 |
5800 |
Could not allocate a statement handle. |
Type of Message: Error
Cause: The TimesTen cache agent could not allocate either an Oracle database or a 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 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 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 an 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 |
5907 |
The cache admin user id was not set before performing the operation. Set the cache admin user id and password either through the built-in procedure ttCacheUidPwdSet or the utility ttAdmin and try again. |
Type of Message: Error
Cause: You attempted to perform an operation without setting the cache administration user ID first. Impact: TimesTen cannot complete the operation. User Action: Set the cache administration user ID and password by using either the |
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 to 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:
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 database users" in the Oracle TimesTen Application-Tier Database Cache User's 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 |
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 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 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 Impact: TimesTen cannot complete the operation. User Action: Verify that the Oracle database instance is running and that 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 Impact: The operation failed. User Action: Either grant the privilege to the cache administrator user ID or use the |
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 for this error are:
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 Impact: TimesTen cannot complete the operation. User Action: Provide the cache administration user ID or password when calling the deprecated built-in procedure |
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 start the cache with the assigned 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 |
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 |
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 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 |
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 |
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 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 Impact: The specified configuration change cannot be passed to the specified agent. User Action: Start the specified agent. - Cache agent: Call the - Replication agent: Call the |
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 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 the 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 workflow. 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 Impact: None. User Action: To disable |
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. |
5990 |
A fatal error occurred in the cache agent. |
Type of Message: Error
Cause: The cache agent reports an irrecoverable error during autorefresh. Impact: TimesTen cannot complete the operation. User Action: Contact TimesTen Customer Support and send the latest |
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 used in a previous autorefresh process. Before dropping the orphaned object, the agent locks the 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 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 autorefresh cache groups" in the Oracle TimesTen Application-Tier Database Cache User's 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 |
UseOraConnPool is enabled. The transaction requires a commit/rollback before dynamic load. |
Type of Message: Error
Cause: There is a 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: You attempted 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 |
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 |
| 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 |
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 requests. 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 the 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 the 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 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 the 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 the 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 |
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 |
6013 |
Bad value for checkOverride parameter, should be 0 or 1 |
Type of Message: Error
Cause: You provided an invalid value for the Impact: TimesTen cannot perform the operation. User Action: Provide an appropriate value for the |
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 to 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 Impact: TimesTen cannot perform the operation. User Action: Ensure that the |
6103 |
Cursor has no current row defined |
Type of Message: Error
Cause: You attempted a delete or update operation on a Impact: TimesTen cannot perform the operation. User Action: Ensure that you define the |
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 - 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 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 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 Impact: TimesTen cannot perform the operation User Action: Remove any |
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 |
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 Impact: TimesTen ignored the new value. User Action: Specify smaller values for the |
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 |
6212 |
MemoryLock connection attribute not supported on this platform |
Type of Message: Error
Cause: The Impact: TimesTen ignores the User Action: If you are using AIX, the |
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 |
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 |
6222 |
Permanent data region in use size has exceeded PermWarnThreshold |
Type of Message: Warning
Cause: Memory allocation in the permanent memory region caused the Impact: None. User Action: Increase the size of the permanent memory region by modifying the set value for the |
6223 |
Temporary data region in use size has exceeded TempWarnThreshold |
Type of Message: Warning
Cause: Memory allocation in the temporary memory region caused the Impact: None. User Action: Increase the size of the temporary memory region by modifying the set value for the |
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 |
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 the 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 Impact: The database is invalidated. If the 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 If the error persists after adjusting the values of the |
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 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 the 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 Impact: TimesTen cannot connect to the database. User Action: Specify a valid value for the |
| 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 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 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 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 |
Illegal attempt to update
system table table_name
|
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 |
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 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 the 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 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 an incorrect format. Impact: The SQL statement is not executed. User Action: Modify your string to use the correct format and retry the operation. |
7025 |
Illegal 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 the Oracle TimesTen In-Memory Database SQL Reference. |
7026 |
Illegal attempt to alter
system table table_name
|
Type of Message: Error
Cause: You attempted to alter a system table. System tables are identified by the owner 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 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 |