Errors 0 - 999
Error number | Error or warning message | Details |
---|---|---|
TT0400 | Data store header fails basic sanity test | Internal error. Contact TimesTen Technical Support. |
TT0402 | Cannot close data store file. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0403 | Attempt to read from checkpoint truncated | Internal error. Contact TimesTen Technical Support. |
TT0404 | Corrupted block header | Internal error. Contact TimesTen Technical Support. |
TT0406 | Incomplete write to file file_name. OS-detected error: error | If this happens during commit, it may be due to limited disk space for reclaim. See description of error 902 for more information. |
TT0407 | Failed to seek in checkpoint file. OS-detected error: error | Internal error: An attempt to seek within a checkpoint file has failed. Contact TimesTen Technical Support. |
TT0408 | Failed to sync checkpoint file file_name to disk.OS-detected error: error_message | Internal error: An attempt to sync a checkpoint file to disk has failed. Contact TimesTen Technical Support. |
TT0409 | Invalid checkpoint LSN | Internal error: Contact TimesTen Technical Support. |
TT0411 | OS-detected error error while destroying directory directory | Warning only. TimesTen failed to destroy a directory due to an operating system error. |
TT0412 | Bad file-open mode | Internal error. Contact TimesTen Technical Support. |
TT0413 | Bad file-exists mode | Internal error. Contact TimesTen Technical Support. |
TT0414 | Bad file-missing mode | Internal error. Contact TimesTen Technical Support. |
TT0415 | Incompatible file-open modes | Internal error. Contact TimesTen Technical Support. |
TT0416 | Block merge operation terminated due to high contention | Internal error. Contact TimesTen Technical Support. |
TT0420 | Operation is not permitted over client-server connections | The attempted operation can only be performed in direct mode. |
TT0421 | Invalid file handle (may have been closed by application) | A file handle used for reading the transaction log has been unexpectedly closed. This error almost always indicates an application programming error. Check your application code to see if it is closing a file handle improperly. |
TT0422 | File handle repositioned (may have been read for written by application) | A file handle used for reading the transaction log has been unexpectedly repositioned. This error almost always indicates an application programming error. Check your application code to see if it is reading from or writing to the wrong file handle. |
TT0423 | Log directory in NFS is not supported on this platform | Installations of TimesTen are supported on the Linux platform. |
TT0600 | Checkpoint not done due to transaction commit/rollback failure | Commit or rollback of the transaction failed. As a result, checkpointing was not attempted. Consider performing a checkpoint in its own transaction. |
TT0601 | Checkpoint failure | Checkpoint failed. Check that there is sufficient disk space and that database files are writable, then retry. |
TT0602 | Transaction already has a pending fuzzy checkpoint request | A checkpoint procedure has been called on a transaction that has another checkpoint request pending. |
TT0603 | Transaction already has a pending checkpoint request | A checkpoint blocking procedure has been called on a transaction that has another checkpoint blocking request pending. |
TT0604 | Log missing record for checkpoint file (lsn LSN_number). | If the transaction log on disk has been truncated or otherwise corrupted, it may be missing log records corresponding to the checkpoints on disk. In this case, the transaction log is ignored, any log files existing are moved to the directory indicated in this message, and the database is recovered from the checkpoints alone. This message is issued as a warning when this situation occurs. |
TT0605 | Checkpoint Log record number.number) not present | If the transaction log on disk has been truncated or otherwise corrupted, it may be missing log records corresponding to the checkpoints on disk. In this case, an attempt is made to move any existing log files to another directory, so they can be ignored and recovery can continue with the checkpoints alone. If it is not possible to move the existing log files, this error is issued. The database administrator may want to manually move or remove the truncated or corrupt log files and try connecting again. |
TT0606 | Checkpoint cannot proceed because another checkpoint or backup is in progress | An attempt was made to checkpoint the database while a backup or another checkpoint was in progress. Wait until the backup or checkpoint has completed and retry the checkpoint. |
TT0607 | Backup cannot proceed because another checkpoint or backup is in progress | An attempt was made to backup the database while a checkpoint or another backup was in progress. Wait until the backup or checkpoint has completed and retry the backup. |
TT0609 | Data store failed validity check | Internal error. Contact TimesTen Technical Support. |
TT0610 | End-checkpoint log record not found | Internal error. Contact TimesTen Technical Support. |
TT0611 | Backup process died | This error is reported by thettBackupStatus built-in procedure when an in-progress backup was killed or died unexpectedly. |
TT0622 | User user_name does not have group permission to connect to data store | The user is not a member of the group that is authorized to connect to the database. Add the user to the appropriate group. |
TT0623 | User user_name does not have group permission to create data store | The user is not authorized to connect and to and create the database. Add the user to the appropriate group. |
TT0629 | No permission to access data store files | The user is not authorized to connect to the database. Reset theGroupRestrict attribute. |
TT0649 | Log file file_name has been purged | By default, TimesTen automatically removes archived transaction log files at checkpoint time. To retain archived transaction log files, setLogPurge=0 . For more details on transaction log files, see "Managing transaction log buffers and files" in the Oracle TimesTen In-Memory Database Operations Guide. |
TT0650 | Invalid backup type | The specified backup type is invalid. SeettBackup for a description of valid backup types. |
TT0651 | Backup path is not enabled for incremental backup | The backup file must be enabled for incremental backups when it is created. SeettBackup . |
TT0652 | Backup directory does not exist | Create or specify a valid backup directory. |
TT0654 | Too many incremental-enabled backup directories | TimesTen supports the creation of up to eight incremental-enabled backup instances for each database. |
TT0656 | Incremental_enabled backup requires disk logging | Incremental backups are supported only for permanent disk-logging databases. |
TT0657 | Backup path exceeds maximum length of number characters | The backup path cannot exceed the path length indicated in the error message. Create or specify a path no longer than the maximum length. |
TT0658 | Backup point is behind backup's log hold | Internal error. Contact TimesTen Technical Support. |
TT0659 | Backup is out of date | The backup files specified by the backup directory and/or basename are not from the database that is being backed up. They may be from a previous database that had the same database path name but which has since been destroyed. These backup files can be overwritten by specifying a backup with the-force option. |
TT0660 | Requested backup point cannot be honored because needed log files have been purged | Internal error. Contact TimesTen Technical Support. |
TT0661 | Requested backup point cannot be honored because it is in the future | Internal error. Contact TimesTen Technical Support. |
TT0662 | Data store file file_name reflects unfinished restore operation. | Unable to recover from the specified database file because it is the result of an incomplete restore operation. The most likely cause of this error is a user-initiated interruption of an in-progress restore operation. Other possible causes for the incomplete restore operation include an out of space condition in the file system that contains the database's checkpoint files or a system crash. To correct the problem, address the issue that caused the interruption of the original restore operation and retry the restore. |
TT0663 | Operation requires logging to disk | The requested operation requires that you enable disk-based logging (Logging = 1 ). |
TT0664 | Log record size of number bytes exceeds maximum size of number bytes | Internal error. Contact TimesTen Technical Support |
TT0665 | The size of LogBufMB should at least be at least LogBufParallelism * 8 | The size that you have specified for theLogBufMB attribute is too small. Increase the size in the DSN.ini file. |
TT0666 | ReplicationApplyOrdering cannot be 0 if ReplicationParallelism is greater than 1. | 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 theReplicationApplyOrdering attribute. The value of In the DSN |
TT0668 | LogBufParallelism value of <number> cannot be smaller than ReplicationParallelism value of <number> | Change the value ofLogBufParallelism and/orReplicationParallelism value in the DSN.ini file so thatReplicationParallelism is not greater thanLogBufParallelism . |
TT0669 | Cannot change replication track within an active transaction. | When using parallel replication, connections can select which parallel replication track to use. However, an application is not allowed to change the replication track in which it writes logs once it has started a transaction. |
TT0670 | Batch cursors cannot be used because replication tracks are not enabled. (ReplicationParallelism = <number> ReplicationApplyOrdering = <number>). | Internal error. Contact TimesTen Technical Support. |
TT0700 | Waiting for other 'in flux' threads failed | Internal error. Contact TimesTen Technical Support. |
TT0701 | Marking data store 'in flux' failed | Internal error. Contact TimesTen Technical Support. |
TT0702 | Connect failed because max number of connections exceeded | The maximum number of connections to the database or instance has been exceeded. TimesTen allows maximum of 2048 concurrent database connections per instance. |
TT0703 | Subdaemon connect to data store failed with error TTerror_number | Check other error messages for more information. If the problem cannot be identified from other errors, contact TimesTen Technical Support. |
TT0704 | Connecting to a data store that is invalid and still has connected clients | Another application connected to the database has failed; the RAM-resident version of the database is corrupted. Once all users now connected to the database disconnect from it, TimesTen rebuilds the database. Try to connect again later. |
TT0706 | Spawning a thread in the daemon failed | Internal error. Contact TimesTen Technical Support. |
TT0707 | Attempt to connect to a data store that has been manually unloaded from RAM | The application has tried to connect to a database whose RAM residence policy is set to manual and which has been manually unloaded from RAM. Applications cannot connect to the database. UsettAdmin with the -ramLoad option to reload the database. |
TT0709 | Adding new data store to catalog failed, OS error 'error_number' | When a database is created, the daemon stores some information about the database on disk. If this operation fails, this error is issued. The database administrator should consider the OS error that is reported and take action accordingly. Additional information may be present in the syslog on UNIX and the Event Log on Windows. This may involve a disk-space problem or a file permission problem, for example. Make sure the daemon is running as the instance administrator on UNIX systems. |
TT0711 | Data store creation in progress, try later | The database is currently being created and, therefore, cannot be accessed. |
TT0712 | Unable to lock data store memory segment, error error_number | 1 (EPERM) - indicates that the daemon was started by a user other than the super-user. Restart the daemon, as described in "Working with the Oracle TimesTen Data Manager Daemon" in the Oracle TimesTen In-Memory Database Operations Guide.
|
TT0713 | Attempt to connect to data store as user "user_name" | You must supply a user name other thanSYS to connect to the database. |
TT0714 | Log directory attribute does not match current value | Any log directory specified for a connection must agree with the value that was specified when the database was created. A warning is be placed in the syslog on UNIX or the Event Log on Windows indicating the directory names that conflict. The database administrator should amend the connection attribute and try reconnecting. |
TT0715 | Unable to access log directory 'log_directory'. OS- detected error: error_details | The path specified in theLogDir attribute is not accessible due to reasons described inerror_details .TimesTen cannot perform the requested connect or disconnect operation. Change theLogDir attribute in the DSN to a valid directory or create the directory as needed. |
TT0716 | Undo of dead connection failed | This error is returned in daemon log and is an internal error. Contact TimesTen Technical Support. |
TT0717 | Update of data store catalog entry failed | TimesTen main daemon tried to update the DBI file in the daemon home directory to indicate a change in the meta information about a database. Check that your file system is not full. If the problem persists, contact TimesTen Technical Support. |
TT0720 | Permission denied while opening directory directory_name | Permissions are not set correctly on the specified directory. Make sure the directory has read and execute permissions for the TimesTen application. |
TT0721 | No such directory: directory_name | The specified directory does not exist. Create that directory, or specify another one. |
TT0722 | Log flusher reports error error_number (error) | The log manager was not able to flush the log due to operating system error. |
TT0723 | Log cursor is not open | Internal error. Contact TimesTen Technical Support. |
TT0724 | Log cursor has no current position | Internal error. Contact TimesTen Technical Support. |
TT0725 | Log cursor is unpositioned | Internal error. Contact TimesTen Technical Support. |
TT0726 | Log cursor is at end of log | Internal error. Contact TimesTen Technical Support. |
TT0744 | Log read encountered additional data afterend of log | 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. This error should only occur after an operating system crash or other external event that corrupted one or more log files. Contact TimesTen Technical Support. |
TT0745 | Log file file_name" LFN_FMT " contains partial log block | Recovery has encountered a log file that ends with a partial log block. This error should only occur after an operating system crash or other external event that corrupted one or more log files. Contact TimesTen Technical Support. |
TT0746 | Extra log files found after end of log | Recovery has encountered log files after the file containing the last complete and intact log record. This error should only occur after an operating system crash or other external event that corrupted one or more log files. Contact TimesTen Technical Support. |
TT0747 | Log read encountered incomplete log record at location log_record.log_number | Recovery has encountered an incomplete log record after the logical end of the log. This error should only occur after an operating system crash or other external event that corrupted one or more log files. Contact TimesTen Technical Support. |
TT0748 | Log ended unexpectedly at LSN number; recovery terminated | Recovery has encountered an error while reading transaction log and theLogAutoTruncate first connect attribute is set to 0. If you can determine and correct the problem, do so and try to connect again. Otherwise, contact TimesTen Technical Support. Do not modify or remove any TimesTen checkpoint or transaction log file without first making a backup copy of the original file. |
TT0749 | Invalid log block found at location number -- details: error_description | Internal error. Contact TimesTen Technical Support. |
TT0750 | Log read encountered log record with incorrect LSN at location number -- remainder of log ignored | TimesTen encountered an unexpected value while reading the log. During recovery, the transaction log is effectively truncated at the point of the unexpected value, and the operation continues. The transaction log corruption is likely the result of a crash affecting the disk controller. 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. 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 Technical Support. |
TT0751 | Log read encountered log record with bad length at location number -- remainder of log ignored | TimesTen encountered an unexpected value while reading the log. During recovery, the transaction log is effectively truncated at the point of the unexpected value, and the operation continues. The transaction log corruption is likely the result of a crash affecting the disk controller. 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. 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 Technical Support. |
TT0752 | Log read encountered log record with bad type at location number - remainder of log ignored | TimesTen encountered an unexpected value while reading the transaction log. During recovery, the transaction log is effectively truncated at the point of the unexpected value, and the operation continues. The transaction log corruption is likely the result of a crash affecting the disk controller. 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. 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 Technical Support. |
TT0754 | Cannot open log copy file file_name. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0755 | Cannot chmod log copy file file_name. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0756 | Cannot write to log copy file file_name: error_details | Internal error. Contact TimesTen Technical Support. |
TT0759 | Log file file_name has invalid file header -- details: error_description | Internal error. Contact TimesTen Technical Support. |
TT0760 | Attempt to read past the end of the log; LSN = LSN_number | Internal error. Contact TimesTen Technical Support. |
TT0761 | Cannot determine size of log file file_name. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0762 | Invalid log truncation LSN LSN_number | Internal error. Contact TimesTen Technical Support. |
TT0763 | Cannot truncate log file file_name. OS-detected error error_details | Internal error. Contact TimesTen Technical Support. |
TT0764 | Cannot move away log file. OS-detected error error_details | Internal error. Contact TimesTen Technical Support. |
TT0765 | Cannot create log file copy directory. OS-detected error error_details | Internal error. Contact TimesTen Technical Support. |
TT0766 | Cannot create log reserve file file_name. OS- detected error error_details | The log manager was not able to create reserved log space due to operating system error. |
TT0767 | Cannot chmod log reserve file. OS-detected error error_details | Internal error. Contact TimesTen Technical Support. |
TT0768 | Cannot determine size of log reserve file file_name. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0769 | Log reserve file has invalid size value | Internal error. Contact TimesTen Technical Support. |
TT0770 | Cannot open log reserve file. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0771 | Cannot write log reserve file file_name. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0772 | Cannot seek in log reserve file. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0773 | Cannot sync log reserve file file_name. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0774 | Cannot close log reserve file. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0775 | Cannot delete log reserve file file. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0776 | Cannot rename log reserve file; old name = old_file_name; new name = new_file_name. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0777 | Log reserve exhausted | Internal error. Contact TimesTen Technical Support. |
TT0778 | Log write failed because filesystem is full; transaction must rollback | The filesystem that holds the transaction log directory is full. You must abort your transaction. If your application hasAUTOCOMMIT set to 0, your application must rollback the transaction. If your application hasAUTOCOMMIT set to 1, the command failed and the application has no further responsibilities. |
TT0779 | Request denied; transaction must rollback because log filesystem is full | This transaction has previously received error 778. No new requests are accepted for this transaction; the transaction must abort. |
TT0780 | Log file file_name not found | Internal error. Contact TimesTen Technical Support. |
TT0781 | Cannot sync log file. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0782 | Cannot rename log file file_name. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0783 | Cannot sync log file even after retrying for number msec. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0784 | Log record type is disallowed at this time | Internal error. Contact TimesTen Technical Support. |
TT0785 | No log record exists at LSN LSN_number | Internal error. Contact TimesTen Technical Support. |
TT0786 | Cannot truncate log reserve file file_name. OS-detected error: error_details | The log manager was not able to maintain reserved log space due to operating system error. |
TT0787 | Log file size exceeds maximum size of size MB | The transaction log file exceeds the maximum defined size for TimesTen. Set the transaction log file size to a size smaller than the maximum allowed limit. For details, see the description for theLogFileSize attribute in the Oracle TimesTen In-Memory Database Reference. |
TT0788 | Log file size less than minimum size of size MB. | The log file is less than the minimum size required by TimesTen. For details, see the description of theLogFileSize attribute in the Oracle TimesTen In-Memory Database Reference. |
TT0789 | LogFileSize size with parallel mode of replication is less than minimum size of 8* LogBufParallelism = %" UINTP_FMT " MB | When parallel replication is used, theLogFileSize should be at least 8 MB per buffer inLogBufParallelism . The size that is specified for theLogFileSize attribute is too small. Increase the size in the DSN.ini file. |
TT0790 | Incomplete write to log file file_name. OS-detected error: error | Unable to write all bytes to the log. If this happens during commit, it may be due to limited disk space for reclaim. See description of error 902 for more information. |
TT0791 | Cannot communicate with subdaemon | Could not connect to or disconnect from a subdaemon because it is not running. Consider restarting the daemon once all applications have disconnected. |
TT0792 | Attempt to read from log file file_name truncated; byte_countbytes read | Unable to read all bytes from the log. Internal error. Contact TimesTen Technical Support. |
TT0793 | No idle subdaemons | Unable to connect to a database because there are no idle subdaemons available. TimesTen supports up to 50 shared databases per daemon. |
TT0794 | Thread join failed | Internal error. Contact TimesTen Technical Support. |
TT0795 | Protocol failure | Internal error. Contact TimesTen Technical Support. |
TT0796 | Failed to initialize procedure procedure_name with arguments/results argument/result_list | Internal error. Contact TimesTen Technical Support. |
TT0797 | Two threads using a single context | This error is issued by the debug version of the library only. If the error persists, contact TimesTen Technical Support. |
TT0798 | 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. |
TT0799 | Unable to connect to daemon; check daemon status | Unable to connect to the daemon during a database creation, database connection or destroy database operation. The daemon is not running. Start it with thettdaemonadmin -start utility. |
TT0800 | Too many errors - error buffer overflow | The number of errors pushed onto the error buffer exceeds the maximum of 50. |
TT0801 | Malloc (C library) failed | Unable to allocate memory for TimesTen internal data structures. |
TT0802 | Database space exhausted | Unable to allocate memory from the heap. An additional error message indicates which data partition is full. Try increasing the size of the appropriate data partition. |
TT0803 | Name length exceeds 30 characters | The number of characters in the length of an identifier or user name has exceeded the maximum of 30. |
TT0804 | Internal error: unknown error code error_string | Internal error. Contact TimesTen Technical Support. |
TT0805 | operation_name has not been implemented | Operation is recognized by the parser but its functionality is not currently available. |
TT0806 | Garbage left on heap | Internal error. Contact TimesTen Technical Support. |
TT0807 | Null pointer argument | Internal error. Contact TimesTen Technical Support. |
TT0808 | Operation not atomic (failed and not undone) | Operation was not rolled back because logging was not enabled. Database may be inconsistent and may not be recoverable. You can try dumping and reloading withttBulkCp . You can also attempt the operation again with logging turned on (Logging=1 ). |
TT0809 | Heap page directory overflow - cannot allocate space | This error indicates that the database's allocation structures are full. Try freeing any items possible and/or compacting the database, usingttCompact , and retrying the operation. Disconnecting all connections and reconnecting may also free up some space. |
TT0810 | Pointer does not reference the data store | Internal error. Contact TimesTen Technical Support. |
TT0812 | Platform not supported platform | Some of the characteristics of your machine (that is, alignments, type sizes) do not match the expected values. Check that you have installed the correct release of TimesTen appropriately. If the error persists, contact TimesTen Technical Support. |
TT0814 | Size specified by 'attribute' connection attribute is less than the minimum size of megabyte_count megabytes | During a database creation operation, the initial size of either thePermSize orTempSize attribute was less than the allowed minimum. Increase the value of the attribute to at least the minimum indicated size. |
TT0817 | Internal error - TimesTen initialization failed | Internal error. Contact TimesTen Technical Support. |
TT0818 | Sum of permanent and temporary partition sizes (size) exceeds maximum size (max_size) allowed on this platform | During a database creation operation, the initial total size exceeded the maximum. |
TT0819 | Data store not compatible with library library | 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. |
TT0820 | Cannot destroy data store logs | Unable to remove the database logs because of an operating system error, such as"File in use." |
TT0821 | No readable checkpoint files | An attempt was made to connect to a database that has been deleted. Consider connecting withOverwrite=1 to create a new database. |
TT0823 | Compact operation not fully completed | This warning is issued when a compaction operation is unable to complete. Additional errors that are pushed should indicate the reason for the failure For example, the failure could be caused by an out-of-disk error. |
TT0824 | Error information lost. Routine was at step number | The operation failed, but error information was lost. Contact TimesTen, Technical Support regarding this lost error information. |
TT0826 | Temporary data store exists but is unattached | Attempting to connect to a temporary database (Temporary attribute set) that is not connected to an application process and should have been automatically destroyed. Try explicitly destroying the database (seettDestroy ) or setting theAutoCreate andOverwrite attributes to overwrite the database. |
TT0827 | Bad connect options: When Logging=0, DurableCommits must be set to 0 and LockLevel must be set to 1 | If logging to disk is off, then database level locking must be on (LockLevel=1 ), theDurableCommits andLogPurge attributes must be off. |
TT0829 | Bad options: Cannot copy logging options if first connection | The copy logging options must be off if creating a database or establishing the first connection to the database. |
TT0830 | Cannot create data store file. OS-detected error: error_text | Unable to remove existing database during a database creation operation with overwrite (Overwrite attribute set) or unable to create the database checkpoint file because of an operating system error such as file system permission problems. |
TT0831 | Cannot change mode on data store file, error error_text | 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. |
TT0832 | Cannot open data store 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. |
TT0833 | Data store data_store_name not found | Warning: attempting to connect to or destroy a database that does not exist. |
TT0834 | Data store 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 technical support. |
TT0835 | Data store file file_name reflects unfinished checkpoint | Unable to recover from the specified database file because the file is incomplete. This generally indicates that either the application failed when writing the checkpoint or that there was not sufficient disk space to store the checkpoint. See the Oracle TimesTen In-Memory Database Operations Guide for information on preventing disk space shortage. Generally a connection is still possible when you receive this error because TimesTen saves two different checkpoints. |
TT0836 | Cannot create data store shared memory segment, error error_number | Unable to create a shared memory segment during a database creation or database connection operation. The database may have been invalidated and some applications may still be connected to it. The shared memory segment cannot be freed until all applications disconnect from the corresponding database. See "Installation prerequisites" in the Oracle TimesTen In-Memory Database Installation Guide. |
TT0837 | Cannot attach data store shared memory segment, error error_number | Unable to attach to a shared memory segment during a database creation or database connection operation.You receive this error if a process cannot attach to the shared memory segment for the database. On UNIX or Linux systems, the shmat call can fail due to one of: - The application does not have access to the shared memory segment. In this case the system error code isEACCESS . - 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 isENOMEM . - The attach exceeds the system limit on the number of shared memory segments for the process. In this case the system error code isEMFILE . It is possible that some UNIX or Linux systems have additional possible causes for the error. Theshmat man page lists the possibilities. On Windows systems, the error could occur because of one of these reasons: - Access denied - The system has no handles available. - The segment cannot be fit into the data section. |
TT0838 | Cannot get data store shared memory segment, error error_number | Unable to access a shared memory segment during a database creation or database connection operation. |
TT0839 | Cannot access data store because it is in use. A data store may be considered to be in use due to its RAM Policy setting, even though there are no active connections to it. | Operation cannot be performed until other connections have finished. IfOverwrite=1 , consider setting it to zero. |
TT0840 | Cannot allocate space byte_count for non-shared data store | 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 HP, 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 For For Bourne shells ( |
TT0841 | Cannot detach data store shared memory segment, error error_number | Warning: unable to detach a shared memory segment during a disconnect from database operation. |
TT0842 | Invalid data store identifier | Internal error. Contact TimesTen Technical Support. |
TT0843 | query/feature is not supported | The requested type of query is not supported. |
TT0844 | Cannot write data store 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 disk space. |
TT0845 | Cannot read data store file. OS-detected error: error_details | Unable to read the database file during a database connection operation. |
TT0846 | Data store connection invalid or not current | To execute the current operation, an existing valid database connection was expected but not detected. |
TT0847 | Cannot open data store 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. |
TT0848 | Recovery failed on number sets of data store files; the TimesTen error log has more information | Recovery was performed on one or more checkpoint files and failed. The user error log contains warning messages that indicate where the problem occurred. Contact TimesTen Technical Support. |
TT0849 | Recovery failed on number sets of data store files; try connecting with a larger data store size | Recovery was performed on one or more checkpoint files and failed. During recovery, the database ran out of space. The most likely reason is that the database was very full when the application exited. If you increase thePermSize attribute and try reconnecting, more space is available for recovery. Contact TimesTen Technical Support |
TT0850 | Application has existing connection to data store | Unable to create, connect to or destroy a database because the application has an existing connection to the database. |
TT0851 | Cannot destroy data store file | 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. |
TT0852 | Unable to lock data store memory segment, error error_number...continuing with connection... | The system was unable to lock memory, but the error was ignored as per theMemoryLock attribute value.1 - indicates that the daemon was started by a user other than the instance administrator. Re-start 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 theMemoryLock attribute. |
TT0853 | Operation is only supported when logging is enabled | Unable to roll back transactions or use row-level locking in a non-logging database. Connect with logging to disk or do not use this operation. |
TT0854 | Data store data_store_name already exists | Unable to create a database because it already exists. Either usettDestroy to destroy the existing database or connect with theOverwrite attribute set. |
TT0855 | Top level heap not defined | Internal error. Contact TimesTen Technical Support. |
TT0857 | Invalid flags for heap creation | Internal error. Contact TimesTen Technical Support. |
TT0860 | Invalid savepoint | Internal error. Contact TimesTen Technical Support. |
TT0862 | Number of active transactions exceeds the maximum | Internal error. Contact TimesTen Technical Support. |
TT0863 | Operation requires an active transaction | Internal error. Contact TimesTen Technical Support. |
TT0864 | Operation prohibited with an active transaction | Internal error. Contact TimesTen Technical Support. |
TT0865 | Cannot destroy log file 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. |
TT0866 | Cannot close file. OS-detected error: error_details | While attempting to flush file buffers to disk, the operating system encountered an error. |
TT0867 | Cannot flush file buffers to disk. OS-detected error error_details | While attempting to flush file buffers to disk, the operating system encountered an error. Check the OS error message. |
TT0868 | 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. |
TT0870 | Cannot close data store shared memory segment, error error_number | Warning: Unable to close shared memory segment handle after detaching the segment. |
TT0871 | Column column_name cannot be set to null | Cannot insert aNULL value into a non-nullable column or field. Check the input values and retry. |
TT0872 | Length of inline columns (value) exceeds limit maximum_value | Length of the inline columns exceeds the maximum of 8,400. Decrease the number and/or length of the columns in the table (only length of non-variable types matters). |
TT0873 | Length of inline row (value) exceeds limit maximum_value | Length of the inline row exceeds the maximum of 8,400. Decrease the number and/or length of the columns in the table (only length of non-variable types matters). |
TT0875 | Invalid or missing column number in column descriptor | Internal error. Contact TimesTen Technical Support. |
TT0876 | Overlapping columns in column descriptor | Internal error. Contact TimesTen Technical Support. |
TT0877 | Misaligned columns in column descriptor | Internal error. Contact TimesTen Technical Support. |
TT0878 | Invalid column number | Column number is not valid. Note that column numbers start at 1 (not 0). Internal error. Contact TimesTen Technical Support. |
TT0879 | Table table_name has existing primary index | Internal error. Contact TimesTen Technical Support. |
TT0880 | Cannot create index; table has maximum of 32 indexes | A maximum of 32 indexes can exist on a given table. This includes both hash (primary key) and range indexes. |
TT0881 | 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. |
TT0882 | Primary index must be unique | Internal error. Contact TimesTen Technical Support. |
TT0883 | Index has open cursors | Cannot insert into, delete from or destroy an index that has open cursors on it. |
TT0884 | Invalid hash index | Internal error. Contact TimesTen Technical Support. |
TT0885 | Invalid T-tree index | Internal error. Contact TimesTen Technical Support. |
TT0886 | Index operation unsupported | Internal error. Contact TimesTen Technical Support. |
TT0887 | Table has no primary index | Internal error. Contact TimesTen Technical Support. |
TT0888 | Tail log truncated at position n.n. (where n is a long integer) | Recovery was unable to read the log past the given LSN. The log was truncated at that point to allow recovery to continue. The original, pre-truncated log file should be found in a directory calledsavedLogFiles , which should be a subdirectory of the database's log directory. |
TT0889 | 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. |
TT0890 | Log file name too long | Internal error. Contact TimesTen Technical Support. |
TT0891 | Log file file_name already exists | Internal error. Contact TimesTen Technical Support. |
TT0892 | Cannot create log file. OS-detected error: error_details | While attempting to create a log file, the operating system encountered an error such as file system permission problems. |
TT0893 | Cannot open log file 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. |
TT0894 | Cannot write log file file_name. 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. |
TT0895 | Cannot close log file. OS-detected error: error_number | Internal error. Contact TimesTen Technical Support. |
TT0896 | Cannot read log file file_name. OS-detected error: error_details | While attempting to read from a log file, the operating system encountered an error such as file system permission problems. |
TT0897 | Cannot seek in log file. OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0898 | Log record exceeds maximum size of log file | Internal error. Contact TimesTen Technical Support. |
TT0899 | Log buffer size is smaller than minimum size of minimum_size KB | Change the transaction log buffer size to a valid size, using theLogBufMB attribute. To see the current value of the transaction log buffer size, use thettConfiguration built-in procedure. If the problem persists, contact TimesTen Technical Support. |
TT0900 | Cannot generate temporary file name | Internal error. Contact TimesTen Technical Support. |
TT0901 | 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. |
TT0902 | 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. Make sure there is enough space on the disk where your temporary directory resides or change the location of your temporary directory by setting theTMP environment variable on Windows or the TMPDIR environment variable on 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. |
TT0903 | Cannot seek in file file_name for reclaim records: OS-detected error: error_details | Internal error. Contact TimesTen Technical Support. |
TT0904 | 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. |
TT0905 | Invalid index identifier | Internal error. Contact TimesTen Technical Support. |
TT0906 | Cannot change mode on logfile file_name, error error_details | While attempting to change file mode access permissions on the log file, the operating system encountered an error. |
TT0907 | Unique constraint constraint violated at Rowid row_number | 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 Technical Support. |
TT0908 | Key not found in table or index | Internal error. Contact TimesTen Technical Support. |
TT0909 | Cannot update primary key or hash key | Cannot update values in the primary key columns or hash key columns of a table. |
TT0910 | Row has already been deleted | A transaction is trying to delete or update a row that it has already deleted. |
TT0911 | Null or blank table name | During table creation, no name was provided for the table. |
TT0912 | Row with ID not found in table | Internal error. Contact TimesTen Technical Support. |
TT0913 | MaxCnt exceeds limit | Internal error. Contact TimesTen Technical Support. |
TT0914 | table_name is not a valid table name | The length of the table name exceeds its maximum of 30 characters. |
TT0916 | Key column must be not-null | Cannot insert aNULL value into a key column. |
TT0917 | Invalid column number for key | The column number of the table that is specified as a key column is invalid. |
TT0918 | 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. |
TT0919 | Invalid comparison condition | Internal error. Contact TimesTen Technical Support. |
TT0920 | 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. For details, see "Column Definition" in Oracle TimesTen In-Memory Database SQL Reference. |
TT0921 | Unsupported column type | Data type is recognized by the parser but is not currently supported. |
TT0922 | Invalid row identifier | Internal error. Contact TimesTen Technical Support. |
TT0923 | Invalid row implementation | Internal error. Contact TimesTen Technical Support. |
TT0924 | Row implementation unsupported for operation | Internal error. Contact TimesTen Technical Support. |
TT0925 | Cannot create data store semaphores | Unable to create a semaphore during a database creation or database connection operation. This error usually indicates that your system was not tuned for TimesTen. See the "Installation prerequisites" section of the Oracle TimesTen In-Memory Database Installation Guide for more details. |
TT0926 | Cannot create data store latch error_number | On Windows, there is a shortage of system resources such as "named events." End any stray processes that are running. If that does not help, reboot the system. If the problem persists, contact TimesTen Technical Support. |
TT0927 | Cannot open data store semaphore (number) number | On Windows, there is a shortage of system resources such as "named events." End any stray processes that are running. If that does not help, reboot the system. If the problem persists contact TimesTen Technical Support. |
TT0928 | Error in semaphore operation error_number | An operating system semaphore operation failed. Contact TimesTen Technical Support with the error number. |
TT0929 | Logging attributes specified for connection are incompatible with existing connections. | TheLogging attributes provided to a database connection operation were incompatible with the Logging attributes currently in effect for existing connections. Change the logging attributes to be the same or use theMatchLogOpts attribute. See the Oracle TimesTen In-Memory Database Operations Guide for valid combinations. |
TT0931 | Data store has maximum number of connections | Unable to create a connection to the database because the current number of connections is at the maximum of 2047. |
TT0932 | Invalid column name: string | The specified column name is invalid. Thestring in the error message gives more information about the specific problem and/or column name involved. |
TT0933 | Invalid SQL string | SQL string isNULL . |
TT0934 | 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. |
TT0935 | SQL statement must return a result | Internal error. Contact TimesTen Technical Support. |
TT0936 | SQL statement may return multiple results | Internal error. Contact TimesTen Technical Support. |
TT0937 | Invalid compiled command number | Internal error. Contact TimesTen Technical Support. |
TT0938 | SQL statement has arguments | Internal error. Contact TimesTen Technical Support. |
TT0939 | SQL statement has no arguments | Internal error. Contact TimesTen Technical Support. |
TT0940 | SQL command has too many results | A maximum of 32,767 projected expressions are allowed for a singleSELECT statement. This includes all columns referenced indirectly by any* expressions. |
TT0941 | 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. |
TT0942 | Imprecise numeric coercion | Warning: unable to convert a numeric value from one type to another without losing precision. |
TT0943 | MaxTups argument must be positive | Internal error. Contact TimesTen Technical Support. |
TT0946 | SQL command is no longer valid | The command has been invalidated. This may happen as the result of some DDL operations, such asALTER TABLE . The command should be prepared again. |
TT0947 | 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. |
TT0948 | Read log buffer size specified is too small or too large | Internal error. Contact TimesTen Technical Support. |
TT0950 | Invalid format width | Internal error. Contact TimesTen Technical Support. |
TT0951 | Invalid float precision | The precision of a float type cannot be negative. |
TT0952 | Null string too long - value will be truncated | Internal error. Contact TimesTen Technical Support. |
TT0954 | SQL command has mismatched version number | Internal error. Contact TimesTen Technical Support. |
TT0955 | Current Connections attribute setting (setting) exceeded by this connection. For optimal performance, configure Connections attribute higher. | The maximum number of connections allowed per database is determined by theConnections attribute. TimesTen supports between 1 and 2047 connections per database. |
TT0956 | Merge statement cannot update a primary key | You are attempting to update a primary key through aMERGE statement. This is not supported. |
TT0960 | 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. |
TT0962 | Bad value for parameter | While calling an API function, an invalid value was provided to a particular parameter. Internal error. Contact TimesTen Technical Support. |
TT0963 | Internal error writing checkpoint log record | During a checkpoint, an error was encountered when writing the checkpoint log record. Internal error. Contact TimesTen Technical Support. |
TT0964 | Internal error truncating log | During a checkpoint, an error was encountered when truncating the log. Internal error. Contact TimesTen Technical Support. |
TT0965 | 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. |
TT0966 | 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. |
TT0967 | Bad join string - join order not changed | The join order set byttOptSetOrder built-in either has incorrect format and therefore is ignored. The correct format is a list of table names separated by spaces. |
TT0968 | Invalid index usage specification | The index usage string provided to thettOptUseIndex built-in procedure has a syntax error. |
TT0969 | Index string too long - default index usage will be used | The index usage string provided to thettOptUseIndex built-in procedure is too long. |
TT0970 | Invalid cursor handle | Internal error. Contact TimesTen Technical Support. |
TT0971 | Supplied buffer too small | Internal error. Contact TimesTen Technical Support. |
TT0972 | Invalid data store handle | Internal error. Contact TimesTen Technical Support. |
TT0973 | Invalid savepoint handle | Internal error. Contact TimesTen Technical Support. |
TT0974 | Invalid format handle | Internal error. Contact TimesTen Technical Support. |
TT0975 | Invalid table handle | Internal error. Contact TimesTen Technical Support. |
TT0976 | Invalid index handle | Internal error. Contact TimesTen Technical Support. |
TT0977 | Invalid row handle | Internal error. Contact TimesTen Technical Support. |
TT0978 | Invalid command handle | Internal error. Contact TimesTen Technical Support. |
TT0979 | Invalid command argument handle | Internal error. Contact TimesTen Technical Support. |
TT0980 | Input buffer not properly aligned | Internal error. Contact TimesTen Technical Support. |
TT0981 | Invalid cursor type (R/W) | Internal error. Contact TimesTen Technical Support. |
TT0982 | String exceeds column width column width | This error happens when an application inserts a string value into a column that has a declared length that is shorter than the inserted value. |
TT0983 | Invalid index or table name table_name - default index usage will be used | The specified table or index was not found. The default index is used. |
TT0984 | 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. |
TT0985 | Application cannot change statistics on statistics system tables | Statistics system tables are maintained by the system and cannot be changed by the application. |
TT0990 | Invalid maxCnt value for table | Internal error. Contact TimesTen Technical Support. |
TT0991 | Quota exceeds maximum row count for table | Internal error. Contact TimesTen Technical Support. |
TT0992 | Number of table pages in use exceeds quota | Internal error. Contact TimesTen Technical Support. |
TT0993 | Number of index pages in use exceeds quota | Internal error. Contact TimesTen Technical Support. |
TT0994 | Data store connection terminated. Please reconnect | An unexpected error or abrupt disconnect (that is,control-C ) caused the connection to be terminated. 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, notify TimesTen Technical Support. |
TT0995 | Cannot destroy data store shared-memory segment, error 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. |
TT0997 | Data store path too long | The path to the database files is too long. The maximum allowed is 256 characters. |
TT0998 | 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 usingfork( ) to use a connection opened by the parent process returns this error. |