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.

Error reporting in OCI, Pro*C and PL/SQL applications

TimesTen OCI and Pro*C applications, and those that use PL/SQL, report errors using Oracle 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 error catalog.

Base level diagnostics

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.

List of errors and warnings

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

Note:

A C language header file containing symbolic names for the various TimesTen internal error codes is shipped with TimesTen. It is named tt_errCode.h and is installed in:install_dir/include on UNIXinstall_dir\include on Windows

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

Warning only. TimesTen failed to destroy a directory due to an operating system error.

412

Bad file-open mode

Internal error. Contact TimesTen Technical Support.

413

Bad file-exists mode

Internal error. Contact TimesTen Technical Support.

414

Bad file-missing mode

Internal error. Contact TimesTen Technical Support.

415

Incompatible file-open
modes

Internal error. Contact TimesTen Technical Support.

416

Block merge operation
terminated due to high
contention

Internal error. Contact TimesTen Technical Support.

420

Operation is not permitted
over client-server
connections

The attempted operation can only be performed in direct mode.

421

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.

422

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.

423

Log directory in NFS is
not supported on this
platform

Installations of TimesTen are supported on the Linux platform.

600

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.

601

Checkpoint failure

Checkpoint failed. Check that there is sufficient disk space and that database files are writable, then retry.

602

Transaction already has a
pending fuzzy checkpoint
request

A checkpoint procedure has been called on a transaction that has another checkpoint request pending.

603

Transaction already has a
pending checkpoint request

A checkpoint blocking procedure has been called on a transaction that has another checkpoint blocking request pending.

604

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.

605

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.

606

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.

607

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.

609

Data store failed validity
check

Internal error. Contact TimesTen Technical Support.

610

End-checkpoint log record
not found

Internal error. Contact TimesTen Technical Support.

611

Backup process died

This error is reported by the ttBackupStatus built-in procedure when an in-progress backup was killed or died unexpectedly.

622

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.

623

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.

629

No permission to access
data store files

The user is not authorized to connect to the database. Reset the GroupRestrict attribute.

The specified backup type is invalid. See ttBackup for a description of valid backup types.

651

Backup path is not enabled
for incremental backup

The backup file must be enabled for incremental backups when it is created. See ttBackup.

652

Backup directory does not
exist

Create or specify a valid backup directory.

654

Too many incremental-enabled
backup directories

TimesTen supports the creation of up to eight incremental-enabled backup instances for each database.

656

Incremental_enabled backup
requires disk logging

Incremental backups are supported only for permanent disk-logging databases.

657

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.

658

Backup point is behind
backup's log hold

Internal error. Contact TimesTen Technical Support.

659

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.

660

Requested backup point
cannot be honored because
needed log files have been
purged

Internal error. Contact TimesTen Technical Support.

661

Requested backup point
cannot be honored because it
is in the future

Internal error. Contact TimesTen Technical Support.

662

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.

The size of LogBufMB should
at least be at least
LogBufParallelism * 8

The size that you have specified for the LogBufMB attribute is too small. Increase the size in the DSN .ini file.

666

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 the ReplicationApplyOrdering attribute.

The value of ReplicationApplyOrdering cannot be 0 if ReplicationParallelism is set to a value greater than 1.

In the DSN .ini file change either ReplicationApplyOrdering to a supported non-zero value or ReplicationParallelism to 0 or 1.

668

LogBufParallelism value of
<number> cannot be smaller
than ReplicationParallelism
value of <number>

Change the value of LogBufParallelism and/or ReplicationParallelism value in the DSN .ini file so that ReplicationParallelism is not greater than LogBufParallelism.

669

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.

The maximum number of connections to the database or instance has been exceeded. TimesTen allows maximum of 2048 concurrent database connections per instance.

703

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.

704

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.

706

Spawning a thread in the
daemon failed

Internal error. Contact TimesTen Technical Support.

707

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. Use ttAdmin with the -ramLoad option to reload the database.

709

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.

711

Data store creation in
progress, try later

The database is currently being created and, therefore, cannot be accessed.

12 (ENOMEM) - indicates there was not enough lockable memory available on the system. Add more real memory, delete other memory-consuming processes or connect with a different value for the MemoryLock attribute.

713

Attempt to connect to data
store as user "user_name"

You must supply a user name other than SYS to connect to the database.

714

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.

The path specified in the LogDir attribute is not accessible due to reasons described in error_details.TimesTen cannot perform the requested connect or disconnect operation. Change the LogDir attribute in the DSN to a valid directory or create the directory as needed.

720

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.

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)

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 Technical Support.

724

Log cursor has no current
position

Internal error. Contact TimesTen Technical Support.

725

Log cursor is
unpositioned

Internal error. Contact TimesTen Technical Support.

726

Log cursor is at end of
log

Internal error. Contact TimesTen Technical Support.

744

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.

745

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.

746

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.

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.

748

Log ended unexpectedly at
LSN number; recovery
terminated

Recovery has encountered an error while reading transaction log and the LogAutoTruncate 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.

749

Invalid log block found at
location number -- details:
error_description

Internal error. Contact TimesTen Technical Support.

750

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.

751

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.

752

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.

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 has AUTOCOMMIT set to 0, your application must rollback the transaction. If your application has AUTOCOMMIT set to 1, the command failed and the application has no further responsibilities.

779

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.

780

Log file file_name not
found

Internal error. Contact TimesTen Technical Support.

781

Cannot sync log file.
OS-detected error:
error_details

Internal error. Contact TimesTen Technical Support.

782

Cannot rename log file
file_name. OS-detected
error: error_details

Internal error. Contact TimesTen Technical Support.

783

Cannot sync log file even
after retrying for number
msec. 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 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 the LogFileSize attribute in the Oracle TimesTen In-Memory Database Reference.

LogFileSize size with
parallel mode of replication
is less than minimum size of
8* LogBufParallelism = %"
UINTP_FMT " MB

When parallel replication is used, the LogFileSize should be at least 8 MB per buffer in LogBufParallelism. The size that is specified for the LogFileSize attribute is too small. Increase the size in the DSN .ini file.

790

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.

791

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.

This error is issued by the debug version of the library only. If the error persists, contact TimesTen Technical 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

Unable to connect to the daemon during a database creation, database connection or destroy database operation. The daemon is not running. Start it with the ttdaemonadmin -start utility.

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

803

Name length exceeds 30
characters

The number of characters in the length of an identifier or user name has exceeded the maximum of 30.

804

Internal error: unknown
error code error_string

Internal error. Contact TimesTen Technical 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 Technical Support.

807

Null pointer argument

Internal error. Contact TimesTen Technical Support.

808

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 with ttBulkCp. You can also attempt the operation again with logging turned on (Logging=1).

809

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, using ttCompact, and retrying the operation. Disconnecting all connections and reconnecting may also free up some space.

810

Pointer does not reference
the data store

Internal error. Contact TimesTen Technical Support.

812

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.

814

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 the PermSize or TempSize attribute was less than the allowed minimum. Increase the value of the attribute to at least the minimum indicated size.

During a database creation operation, the initial total size exceeded the maximum.

819

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.

820

Cannot destroy data store
logs

Unable to remove the database logs because of an operating system error, such as "File in use."

821

No readable checkpoint
files

An attempt was made to connect to a database that has been deleted. Consider connecting with Overwrite=1 to create a new database.

823

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.

824

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.

826

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 (see ttDestroy) or setting the AutoCreate and Overwrite attributes to overwrite the database.

827

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), the DurableCommits and LogPurge attributes must be off.

829

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.

830

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.

831

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.

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

Data store data_store_name
not found

Warning: attempting to connect to or destroy a database that does not exist.

834

Data store file invalid or
corrupted

During recovery or a database connection operation the database file was found to be corrupted. Technical Support

835

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.

836

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.

837

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 is EACCESS. - The system cannot allocate memory to keep track of the allocation, or there is not enough data space to fit the segment. In this case the system error code is ENOMEM. - The attach exceeds the system limit on the number of shared memory segments for the process. In this case the system error code is EMFILE. It is possible that some UNIX or Linux systems have additional possible causes for the error. The shmat man page lists the possibilities. On Windows systems, the error could occur because of one of these reasons: - Access denied - The system has no handles available. - The segment cannot be fit into the data section.

838

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.

839

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. If Overwrite=1, consider setting it to zero.

840

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 csh and tcsh:

limit datasize n

For bash:

ulimit -d n

For ksh, zsh and posix shells (sh or sh-posix):

ulimit -d n
# this is kbytes

Bourne shells (sh or sh-bourne) have no built-in but may fall back on /usr/bin/ulimit.

841

Cannot detach data store
shared memory segment, error
error_number

Warning: unable to detach a shared memory segment during a disconnect from database operation.

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 the PermSize attribute and try reconnecting, more space is available for recovery. Contact TimesTen Technical Support

850

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.

851

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.

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. 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 the MemoryLock attribute.

853

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.

854

Data store data_store_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 Technical Support.

857

Invalid flags for heap
creation

Internal error. Contact TimesTen Technical Support.

860

Invalid savepoint

Internal error. Contact TimesTen Technical Support.

862

Number of active
transactions exceeds the
maximum

Internal error. Contact TimesTen Technical Support.

863

Operation requires an
active transaction

Internal error. Contact TimesTen Technical Support.

864

Operation prohibited with
an active transaction

Internal error. Contact TimesTen Technical Support.

865

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.

866

Cannot close file.
OS-detected error:
error_details

While attempting to flush file buffers to disk, the operating system encountered an error.

867

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.

A maximum of 32 indexes can exist on a given table. This includes both hash (primary key) and range indexes.

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 Technical 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 Technical Support.

885

Invalid T-tree index

Internal error. Contact TimesTen Technical Support.

886

Index operation unsupported

Internal error. Contact TimesTen Technical Support.

887

Table has no primary index

Internal error. Contact TimesTen Technical Support.

888

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 called savedLogFiles, which should be a subdirectory of the database's log directory.

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 Technical Support.

891

Log file file_name already
exists

Internal error. Contact TimesTen Technical Support.

892

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.

893

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.

894

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.

895

Cannot close log file.
OS-detected error: error_number

Internal error. Contact TimesTen Technical Support.

896

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.

897

Cannot seek in log file.
OS-detected error:
error_details

Internal error. Contact TimesTen Technical Support.

898

Log record exceeds maximum
size of log file

Internal error. Contact TimesTen Technical Support.

899

Log buffer size is smaller
than minimum size of
minimum_size KB

Change the transaction log buffer size to a valid size, using the LogBufMB attribute. To see the current value of the transaction log buffer size, use the ttConfiguration built-in procedure. If the problem persists, contact TimesTen Technical Support.

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 the TMPenvironment 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.

Unable to read the temporary file used to spool the headers of reclaimed log records.

905

Invalid index identifier

Internal error. Contact TimesTen Technical Support.

906

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.

907

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.

908

Key not found in table or
index

Internal error. Contact TimesTen Technical 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 Technical Support.

913

MaxCnt exceeds limit

Internal error. Contact TimesTen Technical Support.

914

table_name 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 Technical 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. For details, see "Column Definition" in Oracle TimesTen In-Memory Database SQL Reference.

921

Unsupported column type

Data type is recognized by the parser but is not currently supported.

922

Invalid row identifier

Internal error. Contact TimesTen Technical Support.

923

Invalid row implementation

Internal error. Contact TimesTen Technical Support.

924

Row implementation
unsupported for operation

Internal error. Contact TimesTen Technical Support.

925

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.

926

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.

927

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.

928

Error in semaphore
operation error_number

An operating system semaphore operation failed. Contact TimesTen Technical Support with the error number.

929

Logging attributes
specified for connection are
incompatible with existing
connections.

The Logging 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 the MatchLogOpts attribute. See the Oracle TimesTen In-Memory Database Operations Guide for valid combinations.

931

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.

932

Invalid column name:
string

The specified column name is invalid. The string in the error message gives more information about the specific problem and/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 Technical Support.

936

SQL statement may return
multiple results

Internal error. Contact TimesTen Technical Support.

937

Invalid compiled command
number

Internal error. Contact TimesTen Technical Support.

938

SQL statement has
arguments

Internal error. Contact TimesTen Technical Support.

939

SQL statement has no
arguments

Internal error. Contact TimesTen Technical 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 Technical Support.

946

SQL command is no longer
valid

The command has been invalidated. This may happen as the result of some DDL operations, such as ALTER TABLE. The command should be prepared again.

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.

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

While calling an API function, an invalid value was provided to a particular parameter. Internal error. Contact TimesTen Technical Support.

963

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.

964

Internal error truncating
log

During a checkpoint, an error was encountered when truncating the log. Internal error. Contact TimesTen Technical 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 Technical Support.

971

Supplied buffer too small

Internal error. Contact TimesTen Technical Support.

972

Invalid data store handle

Internal error. Contact TimesTen Technical Support.

973

Invalid savepoint handle

Internal error. Contact TimesTen Technical Support.

974

Invalid format handle

Internal error. Contact TimesTen Technical Support.

975

Invalid table handle

Internal error. Contact TimesTen Technical Support.

976

Invalid index handle

Internal error. Contact TimesTen Technical Support.

977

Invalid row handle

Internal error. Contact TimesTen Technical Support.

978

Invalid command handle

Internal error. Contact TimesTen Technical Support.

979

Invalid command argument
handle

Internal error. Contact TimesTen Technical Support.

980

Input buffer not properly
aligned

Internal error. Contact TimesTen Technical Support.

981

Invalid cursor type (R/W)

Internal error. Contact TimesTen Technical Support.

982

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.

983

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.

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 Technical Support.

991

Quota exceeds maximum row
count for table

Internal error. Contact TimesTen Technical Support.

992

Number of table pages in
use exceeds quota

Internal error. Contact TimesTen Technical Support.

993

Number of index pages in
use exceeds quota

Internal error. Contact TimesTen Technical Support.

994

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.

995

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.

997

Data store 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.

Errors 1000 - 1999

Error number

Error or warning messages

Details

1000

Cannot set primary key columns
to different values

Updating values in primary key columns

in not supported.

1001

Syntax error in SQL statement statement

The parser has detected a syntax error in the SQL statement.If your SQL syntax appears ok, check if you are using one of the TimesTen SQL reserved words listed in "Reserved Words" in Oracle TimesTen In-Memory Database SQL Reference. Add quotes around the suspected reserved word or use an alternate word as a test. If your SQL worked before upgrading to a new TimesTen release, this error is likely the result of a reserved word.

1002

Identifier in SQL statement
exceeds maximum length

The length of the identifier used in the SQL statement exceeds the maximum of 30.

1004

Identifier in SQL statement is
zero-length

An identifier specified in the SQL statement is of zero length. For example, the following SQL (where the replication name is of zero length) generates this error: CREATE REPLICATION ELEMENT E1 MASTER REP1 SUBSCRIBER REP2

1005

Identifier in SQL statement is
all spaces

The identifier is all blank spaces. Spaces are not supported in identifiers. Provide a supported identifier and execute the SQL statement again.

1006

Identifier statement
contains illegal characters

Identifiers (including delimited identifiers) can contain only characters from the ASCII character set. Other characters, such as native language characters, are not allowed in identifiers.

1007

Illegal parameter marker name

Parameter marker names beginning with _QMARK_ are reserved for system use.

PL/SQL procedures, packages and function names in TimesTen must follow the rules for TimesTen table names, which cannot include lower case letters or trailing spaces in the name.

1017

Column number in ORDER BY
clause must be greater than zero

When referencing a column by position in an ORDER BY clause, the column number must be greater than zero.

1022

Constant number is outside
representable range

The specified constant value was outside the range of its type. Consult "Data Types" in the Oracle TimesTen In-Memory Database SQL Reference for information on the range of each type.

1024

Referenced table table_name
not in FROM list

The referenced table or correlation name used to qualify a column name does not appear in the FROM list of the query.

1025

Number of column names in
INSERT statement is not equal
to number of values

The number of column names specified in the INSERT statement does not match the number of values specified in the VALUES clause.

1026

Column names must contain at
least one character

The name of a column cannot be blank.

1027

Floating-point precision out
of legal range

The precision of a FLOAT type must be between 1 and 53.

1032

Aggregate function cannot be
nested

An aggregate function cannot be called within another aggregate function.

1033

Aggregate function cannot be
specified in group by clause

An aggregate function cannot be called within a GROUP BY clause

1061

PRIMARY KEY syntax can only be
used once in statement

A table can have at most one PRIMARY KEY column list or constraint.

1102

Stale table handle

A table has been altered during an operation.

1103

Error in converting sysdate to
Timestamp

This error only occurs when trying to convert the system return time to TimesTen internal timestamp format.

1104

Unable to obtain current date
and time for SYSDATE

Unable to get the time from the system specific call.

1106

Start num value must be
between minValue value and
maxValue value.

Make sure that your starting number is within the range specified by the minimum and maximum values supplied for this operation.

1107

Error converting sysdate to Date

This error only occurs when trying to convert the system return time to TimesTen internal date format.

1108

Converting Oracle rowiD to
TimesTen rowiD

This error is caused by an invalid or improperly formatted Oracle ROWID in a SQL statement. TimesTen reports this when it tries to convert an improperly formatted Oracle ROWID to a TimesTen ROWID format.

1109

Error converting char to ROWID

This error is caused by an invalid or improperly formatted CHAR in a SQL statement.

1110

FOR UPDATE with aggregate
function is deprecated

You have used SQL syntax that is no longer supported. It is necessary to rewrite your query.

1111

Error in converting rowid to
char string

Your application provided a buffer that is too small to store a ROWID string. Provide a buffer that can hold an 18-character string.

1112

Error in converting char
string to rowid

You provided a string that is not a valid rowid string.

1119

Arguments/bind variables not
allowed for data definition
operations

Binding variables or arguments are not allowed for any DDL statements, such as CREATE VIEW, CREATE TABLE.

1120

SQL command does not exist

You have specified a SQL command that cannot be found in the SQL command query cache.

1200

Invalid transaction ID was
input

No such transaction exits in TimesTen.

1203

This transaction needs
rollback since rollback was
forced

This transaction has been rolled back via another connection. You must complete it by rolling it back

1740

Missing double quote in
indentifier 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.

Errors 2000 - 2999

Error number

Error or warning message

Details

2042

Column defined with interval
data type is not supported

A column in the CREATE TABLE or ALTER TABLE statement was defined with an INTERVAL type. INTERVAL data type is not supported.

The new index references the same column(s) as a previously existing index. You must drop one of the indexes.

2233

Key columns of new index
index_name are a prefix of the
columns of existing index
index_name; consider dropping
index index_name

Redundant indexes are not allowed on TimesTen tables. Some columns of the new index are refrenced in an existing index. You must drop one of the indexes.

2234

Key columns of existing index
index_name are a prefix of the
columns of new index index_name;
consider dropping index
index_name

Redundant indexes are not allowed on TimesTen tables. Some columns of the new index are refrenced in an existing index. You must drop one of the indexes.

2235

Table can have only one
primary key

A table cannot have more than one primary key.

2236

Nullable column can not be
part of a primary key

All columns that are part of a primary key must be defined as NOT NULL.

2237

Adding a primary key
constraint on a replicated
table is not allowed while the
replication agent for data
store data_store_name is
running. Stop the
replication agent to perform
this operation.

To add a primary key to a table that is involved in replication, you must stop the replication agent.

2238

System table cannot be
altered

TimesTen system tables cannot be altered by user. These tables are used to store metadata for necessary for various TmesTen operations and diagnostics. System tables are identified by the owner SYS or TTREP.

Indicates that 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.

Indicates that the size projection for the specified table overflowed an unsigned 64-bit integer.

2249

Duplicate column name found in
update set list

A column was specified more than once in the SET column list of an UPDATE statement.

2250

New column name `column_name'
duplicates existing column name

When altering a table, use a unique column name.

2286

Attempt to define constraint
on column that does not exist

Attempting to create a PRIMARY KEY or UNIQUE constraint on a column that does not exist.

2294

UNIQUE/PRIMARY KEY column must
specify NOT NULL

Columns referenced in a PRIMARY KEY or UNIQUE constraint cannot be nullable.

2295

Duplicate columns in primary
key specification

The column list specified in the PRIMARY KEY or a UNIQUE HASH clause of a CREATE TABLE statement cannot contain duplicates. Remove them and retry the operation.

2376

Duplicate entries in FROM
clause

A table was specified more than once in the FROM clause of a SELECT statement.

2377

Target table of insert cannot
be in the from clause

When using INSERT SELECT, the table into which rows are to be inserted cannot also be referenced by the SELECT portion of the statement. Rewrite the statement and retry the operation.

2400

Number of columns columns_num
exceeds the maximum max_num

Attempting to create a table with more columns than the maximum limit of 1000.

2404

Number of primary key columns
exceeds the maximum

Attempting to create a primary key containing more columns than the allowed maximum of 16.

2405

Number of index key columns
columns_num exceeds the maximum
max_num

Attempting to create an index with more columns than the allowed maximum of 16.

2407

Length of column column_name
(length) exceeds maximum
(max_length)

Attempting to create a CHAR or BINARY column whose length exceeds 8,300 or a VARCHAR or VARBINARY column whose length exceeds its maximum of 4,1943,04.

2414

Length of column column_name
(length) below minimum
(min_length)

Attempting to create a CHAR, BINARY, VARCHAR or VARBINARY column whose length is less than 1.

2416

Number of hash key columns
exceeds the maximum

Attempting to create a table containing more than the maximum primary key columns of 16.

2420

Number of values specified in
INSERT statement exceeds number
of columns in table

The number of values specified in the VALUES clause in the INSERT statement is greater than the number of columns in the table.

2421

Column number exceeds length
of select list

When referencing a column by position in the ORDER BY clause, the column number must be less than or equal to the number of columns in the SELECT column list.

2430

Precision of decimal or
numeric type is out of range

The specified precision of a DECIMAL or NUMERIC data type must be between 1 and 40.

2431

Scale of decimal or numeric
type is out of range

The specified scale of a DECIMAL or NUMERIC data type must be greater than or equal to zero.

2432

Scale of decimal or numeric
type must not be larger than
precision

The specified scale of a DECIMAL or NUMERIC column cannot exceed the column's precision.

2433

Invalid fixed-point number
provided

A fixed-point value can only contain items in the following order: a sign, digits (0-9), a decimal point and digits (0-9). The sign and decimal point are optional.

2434

Decimal overflow

The number of digits to the left of the decimal point exceeded the amount allowed based on the defined precision and scale.

2435

Decimal value exceeds scale -
value will be truncated

Warning: The number of digits of the right of the decimal point exceeded the amount allowed based on the defined scale. The decimal value is being truncated.

2436

Decimal divided by zero

Attempting to divide a decimal value by zero.

2437

Decimal product cannot be
represented; scale
scale_value is greater than
maximum of maximum_value

Multiplication of decimal values must preserve the full scale in a decimal product. If this is not possible, precision might be lost. In that case, this error is issued and the operation is canceled. Refer to the Oracle TimesTen In-Memory Database SQL Reference for information on the maximum scale and precision of decimal values, and the scale and precision of the results of arithmetic operations on these values.

2438

Precision of decimal or
numeric value is out of range

A decimal or numeric value must have between 1 and 40 digits, inclusive.

2439

Scale of decimal or numeric
value is out of range

A decimal or numeric value must have between 0 and 40 digits to the right of the decimal point, inclusive.

2440

Value outside of range
supported by decimal or
floating point type

A decimal or numeric value must have between 0 and 40 digits to the right of the decimal point, inclusive.

2600

Integer overflow

The specified or calculated value is greater than the upper bound that the signed or unsigned integer type allows.

2602

Integer divide by zero

Attempting to divide an integer by zero.

2603

Extended precision overflow

The specified or calculated value is greater than the upper bound that the signed floating-point type allows.

2604

Extended precision divided by
zero

The specified or calculated value is greater than the upper bound that the signed floating-point type allows.

2605

Extended precision underflow

The specified or calculated value is less than the lower bound that the signed floating-point type allows.

2606

Error converting from
character string `string' to
date

A CHAR or VARCHAR constant is not in correct format to be converted to DATE format. See "Data Types" in the Oracle TimesTen In-Memory Database SQL Reference.

2607

Error converting from
character string `string' to
time

A CHAR or VARCHAR constant is not in correct format to be converted to TIME format. See "Data Types" in the Oracle TimesTen In-Memory Database SQL Reference.

2608

Error converting from
character string `string' to
timestamp

A CHAR or VARCHAR constant is not in correct format to be converted to TIMESTAMP format. See "Data Types" in the Oracle TimesTen In-Memory Database SQL Reference.

2609

Incompatible types found in
expression

Attempt to use an incompatible type in an expression. For example, using a boolean operator on a character string operand is an error.

A data type conversion caused an overflow. Refer to "Data Types" in Oracle TimesTen In-Memory Database SQL Reference for information about the maximum values for each integer data type, and consider using one that permits larger values.

You cannot use an expression when specifying a format string. The format string must be a string literal.

2623

Invalid number

The value is invalid for the data type NUMBER. For a description of valid values for this data type, refer to "Data Types" in Oracle TimesTen In-Memory Database SQL Reference.

2705

Column column_name in select
expression not in group by list

All simple columns (not aggregate or expressions) referenced in the SELECT column list or the HAVING clause must appear in the GROUP BY column list.

2706

query not in select distinct
list

The query contained both an ORDER BY and a DISTINCT clause, however the column that is to be ordered did not appear in the projection list.

2712

Attempt to update primary key
column(s)

Cannot update values in the primary key columns of a table.

2764

DISTINCT within aggregate
function cannot reference
expression

Within an aggregate function, the DISTINCT operator can only reference a simple column and not an expression.

2765

Invalid use of aggregate
function

The aggregate function is being used improperly. For example, an aggregate function cannot be used in the SET clause of an UPDATE statement.

2774

Invalid character following
escape character

Escape character must be followed either by a wildcard character or by the escape character itself.

2775

Invalid ESCAPE clause in LIKE
expression

An invalid escape clause was found within the LIKE expression.

2776

Both arguments of binary
operation cannot be parameters

In a binary operation, both operands cannot be argument references like dynamic parameters.

2777

Argument of unary operation
cannot be parameter

In a unary operation or aggregate, the operand cannot be an argument reference like a dynamic parameter.

2778

Cannot infer type of parameter
from its use

The operator requires operands of a specific type. TimesTen cannot determine whether the dynamic parameter used as one of the operands is of the appropriate type. For example, providing dynamic parameters to the LIKE operator does not guarantee that the operands are character types.

2779

Value length is inconsistent
with type length

The routine to set column statistics takes VARBINARY values as input. A VARBINARY value has been specified that does not have the correct length of the column. Check this length and provide an appropriate VARBINARY value.

2781

Pages value must be a positive
value

A negative value has been specified for PAGES. Change the value to a positive value.

2783

Alter table to set new pages
value is valid only if the
table has a hash index

You must set a hash value on the table to include the SET PAGES clause in an ALTER TABLE statement.

2784

Column column_name has no
default value defined

Default value clause was used in an INSERT or an UPDATE statement with a non-nullable column where no default value had been defined.

2785

Column column_name has no
unique constraint

ALTER TABLE to drop UNIQUE constraint was executed on a column with no UNIQUE constraint.

2786

Column column_name already has
unique constraint

ALTER TABLE to add a UNIQUE constraint on a column which already has a UNIQUE constraint.

2787

DateTime arithmetic error

A datetime operation results in an invalid DATE, TIME or TIMESTAMP. For example, the resulting HOUR is not in the range 0..23 (inclusive), the resulting MONTH is not in the range 0..12, or the resulting DAY is invalid like 'Feb 30' or 'Jan 32'.

2788

Value too big for the interval
type

Interval constant is too big or conversion from one interval type to the other results in a value that is too large.

2789

An interval data type must be
specified for a datetime
arithmetic result

Casting to interval type was not specified for a datetime subtraction and this type cannot be inferred from the context.

2790

Cannot infer type of case
expression from its use

All resulted expressions are arguments without a CAST operator and the data type cannot be inferred from the context.

2791

The FROM clause of a join
update statement must include
the updated table

The updated table was not specified in the FROM clause.

2792

All updated columns must
belong to updated table

The SET clause of a join UPDATE was used to update a table different from the updated table.

2793

A selected rowid or column
reference is not found in the
current scope

You cannot select a ROWID from a view.

2794

Argument argument_name is
out of range

The specified n value of an INSTR function is less than or equal to zero. The value must be positive and greater than 0.

2795

column_name not in the select
list of the first select

Only column name of tables or column alias in the left most SELECT can be specified in the ORDER BY clause.

2796

ON COMMIT option is only
support with temporary table

ON COMMIT option was specified with a permanent table.

2797

First two arguments of INSTR
operation cannot be both
parameters with undefined type;
use CAST operator to
define data type for
parameters

Both expressions of an INSTR are arguments with no defined type.

2798

First argument of SUBSTR
operation cannot be parameter
with undefined type; use
CAST operator to define data
type for parameter

First argument of SUBSTR has no defined type.

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

You must use the same NLS_SORT value for all character type columns in a linguistic index. For example, the following statement is not allowed:

Use one of the multi-lingual sorts instead or create separate indexes for each NLS_SORT value if needed.

2804

NLS parameter for linguistic
index must be a constant
string

The NLS_SORT parameter to the NLSSORT function in a linguistic index definition must be a constant, as in:

CREATE INDEX i1 ON t1 (NLSSORT(c1, 'NLS_SORT=french'));

2806

Invalid NLS parameter for
NLSSORT function sort_value

The NLS_SORT value supplied to the NLSSORT function is invalid. It may be a sort that is unsupported or unknown to TimesTen or there may be a problem with the syntax, which must be of the form

NLS_SORT=sort

For example:

CREATE INDEX i1 ON t1(NLSSORT(c1,
'NLS_SORT=bogus'));

Returns

2806: Invalid NLS parameter for NLSSORT function 'NLS_SORT=bogus'

2809

Invalid interval

The string specified in interval literal, thus INTERVAL 'string' is of an illegal format.

2811

Not a group by expression

The user try to use a non-aggregate expression which is not in the group by list of a group by query. Within a group by query, all column references must be either inside an aggregate function or on the group by list. For example, the following query triggers this error:

Invalid value 'value' for
argument number of procedure
procedure_name. The valid
values are values.

You have passed an invalid value for a parameter in the position indicated in when calling a built-in procedure. The position of the invalid parameter, the invalid value and a list of valid values are displayed. Call the built-in procedure passing a valid value for the parameter.

2820

Invalid USERENV parameter

The user supplied an invalid option to the function SYS_CONTEXT. For more information, see "SYS_CONTEXT" in the Oracle TimesTen In-Memory Database SQL Reference.

2860

Invalid zero-length parameter
value

The application provided a parameter of the incorrect length.

2861

Incorrect parameter value
length

The application provided a parameter of the incorrect length.

2862

Parameter length exceeds
maximum

The application provided a parameter of the is greater than the maximum allowed length. Provide a parameter with a shorter length and try your operation again.

2863

Char parameter length exceeds
maximum length

The application provided a CHAR parameter value that exceeds the maximum parameter length. Provide a CHAR parameter with a shorter length and try your operation again.

2864

Output parameter value
truncated

The value of an output parameter is too large for the buffer provided by the application. The value was truncated. This is a warning.

2865

Output parameter buffer is too
small

The value of an output parameter is too large for the buffer provided by the application. The value was truncated. This is a warning.

2866

Parameter value too large for
2-byte included-length

The length of an output parameter is larger than the maximum value that can be expressed with a 2-byte included length.

2867

Length of number value exceeds
maximum

The length of a NUMBER parameter value exceeds the maximum length of a NUMBER value. Provide a NUMBER parameter with a shorter length and try your operation again.

2868

String contains an invalid
hexadecimal character

Conversion of a character string to binary failed because the string contained an invalid hexadecimal character. Valid hexadecimal characters are 0-9, A-F and a-f. Provide a valid string and try your operation again.

2869

String is not a valid numeric
literal

Conversion of a character string to a numeric value failed because the string does not contain a valid numeric literal value. Provide a valid numeric literal value and try your operation again.

2870

String contains an invalid
date-time character

Conversion of a character string to a date-time value failed because the string contains an invalid character. Provide a valid character string and try your operation again.

2871

Truncation occurred during
conversion to date-time value

Conversion to TIMESTAMP resulted in truncation of the fractional seconds because the source value specified more digits of fractional seconds than the destination value can accept.

2872

Error converting to date-time
value

Conversion to a date-time value failed either because the source value was not a valid date-time value or because one or more values were out of range.

2873

Invalid statement handle

An invalid statement handle was bound to a ref cursor parameter.

2874

Statement handle for ref
cursor is in an invalid state

A statement handle bound to a ref cursor was in an invalid state. A statement handle bound to an out ref cursor must not have an open result set.

2875

Ref cursor statement handle
must be from same connection as
base statement handle

A statement handle bound to a ref cursor was allocated from a different connection handle than the base statement handle. The two statement handles must be allocated from the same connection handle.

The second argument of NUMTODSINTERVAL is not one of: 'DAY', 'HOUR', 'SECOND' or 'MINUTE'.

2914

Invalid argument
argument_string
for NUMTOYMINTERVAL function

The second argument of NUMTODSINTERVAL is not one of: 'YEAR' or 'MONTH'.

2915

Too many values in the
subquery of the set clause

In the SET clause of a join update, the subquery specifies more values than the updated column list.

2916

Not enough values in the
subquery of the set clause

In the set clause of a join update, the subquery specifies fewer values than the updated column list.

2917

Invalid extract field for
extract source

An attempt was made to extract an incompatible field from a value, for example extracting a YEAR field from an interval DAY to SECOND.

2918

Precision of number type is
out of range [1,38]

The NUMBER type precision can be between 1 and 38. It is currently out of range. Check the string type and make sure that the result type does not result in an overflow or underflow.

2919

Scale of number type is out of
range [-84,127]

The NUMBER type scale can be between -84 and 127. It is currently out of range. Check the string type and make sure that the result type does not result in an overflow or underflow.

2920

Number type arithmetic overflow

The result of the arithmetic operation was too large for the result type, based on the precision and scale of the NUMBER.

2921

Number type arithmetic underflow

This is a warning. The result of the arithmetic operation was too small for the result type, based on the precision and scale of the NUMBER. The result was rounded to 0.

2922

Invalid number type value

An operand to an arithmetic operation was not a valid number. Specify a valid number type.

2923

Number type value overflow

The value of a NUMBER was too large for the type of the variable.

2924

Number type value underflow

This is a warning. The value of a NUMBER was too small for the type of the variable.The result value was rounded to zero.

2925

Overflow converting number to
char

A NUMBER parameter to the TO_CHAR function was too large to be converted.

2926

Underflow converting number to
char

This is a warning. A NUMBER parameter to the TO_CHAR function was too small to be converted. The result value was rounded to zero.

2927

Error converting Number to
Char

The NUMBER could not be converted to a character type. Check the string type and make sure that the result type does not result in an overflow or underflow.

2928

Error converting Char to
Number

The character string could not be converted to a NUMBER. Check the string type and make sure that the result type does not result in an overflow or underflow.

2929

Error converting Number to
Double

A NUMBER value could not be converted to a DOUBLE. Check the string type and make sure that the result type does not result in an overflow or underflow.

2930

Error converting Number to
Float

Check the string type and make sure that the result type does not result in an overflow or underflow.

2931

Overflow converting Number to
TinyInt

A NUMBER value was too large to be converted to a TINYINT.

2932

Underflow converting Number to
TinyInt

A NUMBER value was too small to be converted to a TINYINT. This is a warning. The result value was rounded to zero.

2933

Error converting Number to
TinyInt

A NUMBER value was too small to be converted to a TINYINT.

2934

Overflow converting Number to
SmallInt

A NUMBER value was too large to be converted to a SMALLINT.

2935

Underflow converting Number to
SmallInt

A NUMBER value was too small to be converted to a SMALLINT. This is a warning. The result value was rounded to zero.

2936

Error converting Number to
SmallInt

A NUMBER value was too small to be converted to a SMALLINT.

2937

Overflow converting Number to
Int

A NUMBER value was too large to be converted to an INT.

2938

Underflow converting Number to
Int

A NUMBER value was too small to be converted to a INT. This is a warning. The result value was rounded to zero.

2939

Error converting Number to Int

A NUMBER value was too small to be converted to a INT.

2940

Overflow converting Number to
BigInt

A NUMBER value was too large to be converted to a BIGINT.

2941

Underflow converting Number to
BigInt

A NUMBER value was too small to be converted to a BIGINT. This is a warning. The result value was rounded to zero.

2942

Error converting Number to
BigInt

A NUMBER value was too small to be converted to a BIGINT.

2943

Error truncating a date

This is a warning. The date could not be truncated.

2944

Invalid number format model

The format string does not represent a valid NUMBER. Specify a valid NUMBER format.

2945

Truncation occurred during
Number conversion

This is a warning. The number could not be truncated.

2946

Truncation occurred converting
Number to Char

This is a warning. Truncation occurred when converting from NUMBER to CHAR, and some fractional data (i.e., numeric data to the right of the decimal point) could not be converted because the supplied CHAR buffer was not big enough.

2947

Buffer too small for number to
char conversion

The NUMBER to CHAR conversion requires more bytes than the size of the buffer provided for the conversion. The application can fix this problem by passing in a larger buffer.

2948

Bad format string `string'

Specify a valid string format.

2949

Error occurred during Number
conversion

This is a warning. The number could not be converted.

2950

Merge may not update a row
more than once, but the row at
rowid ID matched at least two
source rows

More than one row in the source table matches the same row in the target table. But the target table row cannot be updated more than once in one MERGE operation.

2951

The table being merged into
cannot be used for insert
values

You cannot insert values from target table columns.

2952

Source table table_name
cannot be updated

MERGE update columns cannot be used in the ON clause.

2953

Columns referenced in the ON
Clause cannot be updated

MERGE update WHERE clause can refer to both source and target table, but only a target table can be updated.

2954

Columns referenced in update
WHERE clause is not in either
source or target table

The MERGE statement contains a column reference in the UPDATE WHERE clause that cannot be resolved. Check to make sure the column exists in either the source or the target table of the MERGE.

2955

Column in insert whereclause
is cannot refer to target
table

The MERGE statement contains a column reference to the target table in its insert clause. This is not allowed.

2956

Column in insert whereclause
is not in source table

The MERGE statement contains a column reference in the UPDATE WHERE clause that cannot be resolved. Check to make sure the column exists in the source table of the MERGE.

2957

Bad insert value

If the application inserts a value such as COUNT(*) and TimesTen does not know to which table it refers, the MERGE operation fails. Avoid using an aggregate function as an INSERT value.

2958

Source table table_name with
set operators such as UNION,
INTERSECT, and MINUS is not
supported in merge statements

You have specified SET operator in a MERGE statement that are not supported in TimesTen.

2960

Scale of timestamp type is out
of range [0,9]

A TIMESTAMP can only have a scale in the range 0..9. Any other specified scale value is out of range.

Expected data type A , but instead received the unexpected data type B.

2963

Inconsistent datatypes:
(datatype_A,datatype_B) are not
compatible in
expression (expression)

Data type A is not compatible with data type B in this expression.

2970

Decode syntax error: not
enough operands

A DECODE operation must have at least 3 arguments.

2971

Coalesce syntax error: need at
least two operands

A COALESCE operation must have at least 2 arguments.

2972

Invalid relational operator:
all group of values in the
value list must have the same
number of values as the left
operand

This problem occurs when the relational operator ANY or IN is specified with more than one value in the left operand and the right operand is a list of constant sets where some set has a different number of value than the number of values in the left operand. For example:

SELECT * FROM t1 WHERE (x1,y1) IN ((1,1),(2));

In this example, the error is returned because the second set of values in the IN list contains only one entry instead of the correct number of 2.

The remedy is to add the missing value.

2973

Invalid relation operator:
subquery does not project same
number of columns as specified
in the left operand

This problem occurs when the relational operator ANY or IN is specified where the right operand is a subquery and the select list of this subquery specifies fewer or more values than the left operands. For example:

SELECT * FROM t1 WHERE (x1,y1) IN
(SELECT x2 FROM t2);

In this example, the error is returned because the second set of values in the IN list contains only one entry instead of the correct number of 2.

The remedy is to add the missing value.

2974

Using rownum to restrict
number of rows returned cannnot
be combined with first N or
rows M to N

ROWNUM cannot be used in the same query as either FIRST N or ROWS M to N operators.

2975

Number divide by zero

Performing an arithmetic operation with numbers resulted in a divide-by-zero error.

2976

Parallel value must be greater
than one

Specify a parallel value that is greater than one and retry the operation

2977

Only DAY lifetime unit is
allowed with a TT_DATE column

DAY is the only unit supported for the lifetime unit of a TT_DATE column.

2978

Transparent load value must be
between 0 and 2

An invalid value has been supplied for the TransparentLoad attribute. Use 0, 1 or 2.

2979

Invalid relational operator

During parsing, an invalid relational operation was found.

2980

Cannot add aging policy to a
table with an existing aging
policy. Have to drop the old
aging policy first.

Only one aging policy can be defined on a table at any time.

2981

Non existent column column_name
specified for time-based aging

The column specified in the AGING USE clause of a CREATE TABLE statement does not exist.

2982

Column column_name specified
for time-based aging is not a
timestamp column

The column specified in the AGING USE clause of a CREATE TABLE statement must be of the type TIMESTAMP.

2983

Cannot drop aging or change
aging attribute of a table with
no aging policy

An attempt was made to drop or change aging on a table that does not have an aging policy defined.

2984

LRU aging does not have the
specified attribute

LRU aging must specify one of LowUsageThreshold, HighUsageThreshold or Aging cycle attributes.

2985

Cannot add aging policy to a
materialized view table

Aging policy is not supported on a materialized view or its detail tables.

2986

Cannot add aging policy to a
detail table of materialized
view table

Aging policy is not supported on a materialized view or its detail tables.

2987

A temporary table cannot have
an aging policy

Aging policy is not supported on temporary tables.

2988

Cannot add aging policy to a
non-root table of a cache
group

LRU and time based aging cannot be specified on any non-root table in the cache group. Aging can only be specified on the root table.

2989

LRU aging policy is not
allowed with autorefresh cache
group

An LRU aging policy is not allowed with autorefresh cache group. Specify either time-based aging or no aging policy.

To solve this problem, stop the cache agent, alter aging and then restart the cache agent.

2991

Cannot combine aging duration
with other aging policy

The application has specified the duration aging and either time-based or LRU aging. DURATION is deprecated in this release and is only available for backward compatibility. Specify either time-based or LRU aging for this cache group.

2992

Cannot drop aging column

To drop a column used by time-based aging, you must first drop the aging policy.

2993

Aging column cannot be
nullable

A column used by time-based aging are required to be specified as NOT NULL.

2994

Parent parent_table of table
child_name has different
agining policy:
aging_policy

The parent and children tables involved in an aging definition must have the same policy.

The parent and children tables involved in an aging definition must have the same policy.

2996

Cannot start aging on table
without aging policy

To use aging, the table must be created with an aging policy.

2997

Transparent load cannot be
used with passthrough 3

Transparent load is not supported with the passthrough policy specified as 3. You can prepare the statement with a passthrough value other than 3.

2998

Named constraint not found in
table

An attempt was made to drop a foreign key that was not defined.

2999

Illegal format for rowid type

The second parameter of TO_CHAR is specified and the data type of the first parameter is a ROWID data type. Alternatively, make sure that if the first parameter of the TO_CHAR function is a ROWID expression the second parameter is NULL.

Errors 3000 -3999

Error Number

Error or warning message

Details

3000

There is no unique index on
the referenced columns for
foreign key defined on table
table_name

A foreign key cannot reference any of the columns contained in the foreign key itself.

3001

Foreign key violation
index_name parent key not
found in table table_name;
(or) Foreign key violation
[Index_name]: the row at
Rowid rowid in child table
table_name has no key in
the parent table table_name

Dropping an index used to
enforce unique column
constraint is not allowed

A DROP INDEX statement was used to drop an index used to force a unique constraint. Use ALTER TABLE MODIFY to drop the unique constraint instead.

3011

Duplicate columns in foreign
key specification

When defining a foreign key, duplicate column names were used. To avoid receiving this error, do not construct foreign key columns with duplicate names.

3014

Cascade and non-cascade
foreign keys cannot be mixed
on a table

For consistency, all foreign key constraint paths in a table or leading to a table must be specified as cascaded or not cascaded in a CREATE TABLE statement.

3015

Cascade and non-cascade
foreign keys cannot be mixed
on paths leading to a table

For consistency, all foreign key constraint paths in a table or leading to a table must be specified as cascaded or not cascaded in a CREATE TABLE statement.

3016

Cannot add a foreign key
that makes two paths for a
parent-child pair have
different cascade delete action

For consistency, all foreign key constraint paths in a table or leading to a table must be specified as cascaded or not cascaded in a ALTER TABLE statement.

3017

Child table table_name of
a cascade delete foreign key
is not replicated while its
parent table table_name is
replicated

When a primary key table is included in a replication scheme, its corresponding foreign key table must included in the replication scheme, as well. This error is returned when an ON DELETE CASCADE operation is attempted on a foreign key table in a replication scheme, but the primary key table is not included in the replication scheme.

3018

Child table table_name of
a foreign key is not
replicated while its parent
table table_name is replicated

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.

3019

Parent table table_name of
a cascade delete foreign key
is not replicated while its
child table table_name is
replicated

When a primary key table is included in a replication scheme, its corresponding foreign key table must included in the replication scheme, as well. This error is returned when an ON DELETE CASCADE operation is attempted on a primary key table in a replication scheme, but the foreign key table is not included in the replication scheme.

3020

Parent table table_name of
a foreign key is not
replicated while its child
table table_name is replicated

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.

3021

LRU aging policy for a
readonly cache group is
allowed only if the cache
group is dynamic

You have specified an LRU aging policy on a explicitly loaded cache group.

3022

REFRESH CACHE GROUP with a
WHERE clause is only allowed
only if the cache group is
not dynamic

You cannot execute the REFRESH CACHE GROUP command with a WHERE clause for dynamic cache groups.

3050

Subquery is not allowed in
the RETURNING clause

You have specified a subquery in a RETURNING clause. You must modify your query.

3051

Number of returning
expressions (num) should
match the number of arguments
in the INTO clause
(clause_arguments)

The number of expressions and arguments in the INTO clause do not match. You must modify your query.

3052

Rownm is not allowed in the
RETURNING clause

You have specified rownum in a RETURNING clause. This is not supported. You must rewrite your query.

3053

Sequence references are not
allowed in the RETURNING
clause

You have specified a sequence reference in a RETURNING clause. This is not supported. You must rewrite your query.

3054

Outparameter (:parameter)
in the INTO clause is
referenced more than once in
the SQL statement

The specified parameter is referenced more than once in the INTO clause. You must remove one of the references.

3055

Error in handling the output
parameters in the INTO
clause: (error_message)

There is an error when processing the output values in the specified INTO clause. The details are in the error message.

3056

Aggregate functions are not
allowed in the RETURNING
clause

You have specified an aggregate function in a RETURNING clause. This is not supported. You must remove the aggregate function from the clause.

3070

Cannot create a synonym with
same name as object

This error appears when users create a synonym that points to an object of the same name.

3071

Synonym <synonym> does not
exist

This error appears when users drop a non-existing private synonym. The private synonym may have been previously dropped or may have never existed.

3072

Public synonym <synonym>
does not exist

This error appears when users drop a non-existing public synonym. The public synonym may have been previously dropped or may have never existed.

3073

Public synonym cannot have a
schema name

This error appears when users create a public synonym name with a schema name.

3074

Looping chain of synonyms

A synonym can be created to point to another synonym. If two or more synonyms are created to point to each other, this synonym chain can form a loop. Whenever a loop forms, this error is thrown when using any synonyms in the loop.

3076

Using synonyms in this
statement is not implemented

Synonyms are not supported in certain statement types. This error is thrown when using a synonym in a statement where synonyms are not allowed.

3077

Cannot resolve synonym
string to any existing
object

This error appears when users use an synonym that points to an non-existing object.

3078

Circular view definition
encountered

This error appears when users create an view that uses a synonym inside its SELECT statement, which points to the view itself.

3079

Creating synonyms in schema
string is not allowed

This error is thrown when users create synonyms in restricted schemas, such as SYS, GRID, and TTREP.

3095

Name is already used by an
existing object

This error appears when users create a synonym name that is the same as an existing object.

3096

Object object_name not
found

The database object does not exist.

3097

A object with this
name (name) already exists

An object with this name is already in use in the database.

3098

User username does not
exist.

The user tried to create a database object for a schema that does not exist.

3100

Outer join operator (+) not
allowed in operand of OR or IN

The OUTER JOIN operator (+) was either used in a OR'd condition (for example: x1(+)=1 OR x1(+) FROM...) or in an IN condition (for example: x1(+)IN (1,2,3)). Neither of these uses are supported.

3101

Outer join operator (+) not
allowed in select list, order
by, or group by clause

The OUTER JOIN operator (+) was illegally used in a SELECT list (for example: SELECT x1(+)FROM...) or in an ORDER BY clause (for example: ORDER BY x1(+)) or in a group BY clause (for example: GROUP BY x1(+)). None of these uses are supported.

3102

A table may be outer joined
with at most one outer table

A table was outer joined with more than one table. For example: T1.X1(+) = T2.X2+T3.X3 OR T1.Y1(+)=T3.Y3. Table T1 was outer joined with both T1 and T2. This is not supported.

3103

Two tables cannot be outer
joined together

A cycle of OUTER JOIN was found where each table is both an inner and an outer table. For example: T1.X1(+) = T2.X2 AND T3.X3(+)=T1.X1. This is not supported

3104

A predicate may reference
only one outer-joined table

An OUTER JOIN condition illegally refers to more than one inner table. For example: T1.X1(+) + T2.X2(+)=T3.X3. In this case, both tables T1 and T2 are inner tables. This is not supported

3105

In the First or Rows Clause
the number must be greater
than 0

The value passed for the FIRSTN clause was negative or zero. You must use a positive value

3106

FIRST keyword cannot be used
in subquery

The FIRST keyword can only be used in the main query. TimesTen does not support the FIRST keyword in subqueries.

3107

N must be bigger or equal to
M in 'Rows M to N'
specification

In a SELECT statement change the value of N to a value larger than M.

3108

Outer join operator (+)
cannot be used in query that
specifies joined table

Joined table and outer join specification using operator (+) cannot be both specified in the same query.

3110

Expression expression has
no name

Supply an expression name and run the statement again. A name was not specified for a column in the select list of a CREATE VIEW statement.

3111

Column name column
specified more than once

Each column in a table must have a unique name. Rename the column.

3112

Cannot drop view table
table_name; use DROP
VIEW instead

The specified table is a view. Use the DROP VIEW statement to drop this table.

The detail table that you are attempting to drop has an associated view. You cannot drop a detail table without first dropping the view. See "Working with materialized views" in the Oracle TimesTen In-Memory Database Operations Guide.

3114

Cannot alter view tables

To alter a view, you must drop the table, using the DROP VIEW statement and then create a new view, using the CREATE MATERIALIZED VIEW statement. See "Working with materialized views" in the Oracle TimesTen In-Memory Database Operations Guide.

3115

Cannot drop columns
referenced in materialized views

The specified column is referenced in a view. 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

The view's select text is bigger than the maximum size of 400*1024 bytes.

A non-materialized view was referenced in the definition of a materialized view. See "DROP MATERIALIZED VIEW" in Oracle TimesTen In-Memory Database SQL Reference.

3138

Cannot delete from a
truncated table in an
uncommitted transaction

An in-progress transaction is attempting to delete rows from a table that has already been truncated. To avoid this problem, commit the truncate transaction and then execute the delete operation.

3139

Cannot update from a
truncated table in an
uncommitted transaction

An in-progress transaction is attempting to update rows from a table that has already been truncated. To avoid this problem, commit the truncate transaction and then execute the update operation.

3140

Cannot alter to change hash
page a truncated table in an
uncommitted transaction

An in-progress transaction is attempting to alter the hash pages on a table that has already been truncated. To avoid this problem, commit the truncate transaction and then execute the ALTER operation.

3141

Cannot alter to add/drop
column on a truncated table
in an uncommitted transaction

An in-progress transaction is attempting to add or drop a column on a table that has already been truncated. To avoid this problem, commit the truncate transaction and then execute the DROP or ADD the column.

You must drop the materialized view log before dropping the table. Use the DROP MATERIALIZED VIEW LOG SQL statement.

3145

view_name is not an
Asynchronous Materialized View

The name that you provided in the REFRESH MATERIALIZED VIEW statement is not an asynchronous materialized view. Verify the name and try again.

3146

Column owner.name not
found in the Materialized View Log

The CREATE MATERIALIZED VIEW with REFRESH FAST statement specifies a column that is not in the materialized view log. 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, then drop the materialized view log.

3147

Key Column or rowid
owner.column_name not
found in the selectlist or it
is part of an expression.

The CREATE MATERIALIZED VIEW with REFRESH FAST statement must include all the primary key columns or ROWIDs of all the detail tables. If the primary key column is an argument to a function such as UPPER, it does not satisfy this rule.

3148

No Primary Key in the detail
table table_name. Specify
ROWID option for the
Materialized View Log

The CREATE MATERIALIZED VIEW LOG statement has the primary key clause (either explicitly coded or by default). However, the detail table does not have a primary key. In this case use the ROWID clause in the CREATE MATERIALIZED VIEW LOG statement.

An error was encountered by the asynchronous materialized view daemon thread while refreshing the materialized view. The refresh failed.

The correction to this problem depends on the error message on the daemon log. For example, if the error is due to a lock conflict, you can retry the refresh statement. If it due some other internal error, contact TimesTen Customer Support.

3152

Refresh interval of 0 is not
allowed for Asynchronous
Materialized View with
refresh mode Complete

The refresh interval value must be a positive integer.

3153

There is no materialized
view log on table table_name

You issued a DROP MATERIALIZED VIEW LOG statement on the indicated table. However, there is not materialized view log on that table.

3154

A materialized view log
already exists on table table_name

You issued a CREATE MATERIALIZED VIEW LOG statement on the indicated table. However, there is already a materialized view log on that table.

3155

Cannot drop column
column_name that is
included in the corresponding
materialized view log

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.

3156

Cannot create a materialized
view on a materialized view log.

You have made an attempt to create a materialized view on a materialized view log table. This operation is not supported. The materialized view was not created.

Check the FROM list of the CREATE MATERIALIZED VIEW statement to ensure that no materialized log views are listed, then retry the operation.

When a materialized view is invalid, the owner of the view does not have SELECT privileges on every detail table referenced by that view. To fix an invalid materialized view, re-grant SELECT privileges on every detail table to the view owner (or grant higher-level privileges such as SELECT ANY TABLE or ADMIN). Once the privileges are granted, drop the materialized view and then re-create it.

3160

REFRESH not allowed on
invalid materialized view
string

When a materialized view is invalid, the owner of the view does not have SELECT privileges on every detail table referenced by that view. To fix an invalid materialized view, re-grant SELECT privileges on every detail table to the view owner (or grant higher-level privileges such as SELECT ANY TABLE or ADMIN). Once the privileges are granted, drop the materialized view and then re-create it.

3200

Sequence increment by value
cannot be 0

The sequence increment option that is specified must be greater than 0.

The maximum value input is not valid in a CREATE SEQUENCE statement. Make sure that the maximum value does not exceed the maximum limit, or that the specified maximum is not less than the minimum value.

3204

Sequence sequence_name is
not found

The sequence object specified is not found. Use CREATE SEQUENCE to create one.

3205

A table or sequence with
this name already exists

The sequence object has a name conflict with an existing table name or vice versa. The sequence object name has to be unique in the sequence and table name spaces.

3206

CURRVAL or NEXTVAL not
allowed in select with
distinct, aggregate function,
group by or order by

When a SELECT query has a DISTINCT, GROUP BY or ORDER BY clause specified, CURRVAL and NEXTVAL references are not allowed.

3207

CURRVAL or NEXTVAL not
allowed in subquery of
update, delete or select

References to CURRVAL and NEXTVAL are allowed in main query statements but not in the subquery of an UPDATE, CREATE VIEW or SELECT statement.

3208

CURRVAL or NEXTVAL not
allowed in where clause

The WHERE clause in the SELECT, UPDATE or CREATE VIEW SQL statements cannot have sequence reference. However, CURRVAL is allowed only in the SELECT WHERE clause.

3209

CURRVAL or NEXTVAL is not
supported in views

References to CURRVAL and NEXTVAL are not supported in a VIEW statement.

3210

Sequence max/min limit has
been reached.

The value in the sequence has already reached its maximum or minimum limit. This occurs when the CYCLE option is not turned on for the sequence, and the minimum or maximum has been reached.

3211

CURRVAL may not be
referenced before NEXTVAL in
this session

In a single session, the application should reference NEXTVAL prior to referencing CURRVAL, so that the CURRVAL can be posted to this session.

3212

Failed to get the NEXTVAL

Unable to obtain a NEXTVAL. Possible reasons are: Application is unable to get the next value of the sequence from the cache because of an update problem or lock timeout; there is a problem in posting the NEXTVAL in the environment due to a memory allocation problem, or The application is adding the NEXTVAL to the session context.

3213

Load sequence to cache
failed

An internal error occurred while loading the sequence into the cache.

3214

An error occurred while
adding sequence value info to
context

An internal error occurred while trying to add a sequence value into the context, possibly because of a memory allocation failure. Contact TimesTen Technical 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

The statistics information passed to the ttOptSetColIntvlStats built-in procedure was invalid or incorrectly formatted. The error_number describes the specific problem. See "ttOptSetColIntvlStats" in Oracle TimesTen In-Memory Database Reference for a description of the correct format.

The ttOptEstimateStats built-in procedure may throw this error when there are concurrent transactions, which makes it difficult to estimate statistics.

This error happens when there are a large number of rows deleted in a concurrent transaction.

The table listed is the one on which the statistics are being updated.

3300

type_name is not a valid
type name; instead use
type_name

An attempt was made to use a type name that is not valid in the current type mode. Use the suggested name instead.

3301

Type mode must be set to
Oracle to use this feature

Only databases that have the TypeMode attribute set to Oracle type (TypeMode=0; the default) can contain cache groups. The TypeMode of the database cannot be changed after creation. To use cache groups, recreate the database with Oracle type mode.

3304

Foreign key definition is
not allowed for CREATE TABLE
AS SELECT

A foreign key clause cannot be specified in a CREATE TABLE AS SELECT statement.

3305

Invalid number of column
names specified

You have specified too many column names. Attempt the operation again with fewer column names.

3306

No column name specified
when creating table with hash
index

A column name is required when creating a table with a hash index.

3307

Need to specify the datatype
for the column

When creating a column in this statement, you must specify a data type for that column. Retry the operation, specifying a data type for the column.

3308

May not specify column
datatypes in this CREATE
TABLE

The statement does not allow the specification of a data type for the column. Retry the operation, without specifying a data type for the column.

3309

No column name specified
when creating table with
aging

When creating a table, each column in a table must have a name.

3315

Only dynamic AWT cache group
can be defined as a global
cache group

The CREATE CACHE GROUP statement cannot include the GLOBAL keyword for a cache group that is not an asynchronous writethrough (AWT) cache group.

3316

Cache group definition
mismatch among the members of
the grid

Global cache groups on the same set of Oracle tables cannot have different definitions among the members of the grid. Redefine one or more of the global cache groups.

3317

Cache group cache_group
does not exist in grid member
member

A message was sent to a grid member that specifies a non-existent cache group. It is possible that the cache group was dropped from that member.

3318

Cache group group is not a
global AWT cache group in
grid member member

An operation related to a global cache group encountered a local cache group. It is possible that the global cache group was dropped and replaced by a local cache group.

3319

This operation needs the
database to attach to the
grid first

A member must be attached to the grid before performing any DML on a global cache group table. Use the ttGridAttach built-in procedure to attach the member to the grid.

3320

Node ID table table_name
is not found on Oracle

An Oracle table that stores information about the node ID of all grid members has been dropped.

3321

Node ID table table_name
has no row

The row on an Oracle table that stores information about the node ID of all grid members has been deleted.

3322

Node information table
table_name is not found on
Oracle

An Oracle table that stores information about the node ID of all grid members has been dropped.

3323

Cache group definition table
table_name is not found on
Oracle

Table on Oracle to store information about global cache groups of a grid has been dropped.

3324

Cache grid cannot be
destroyed when there are
attached members

Before destroying a cache grid, you must detach all members of the group. Use the ttGridDetach built-in procedure to detach the member to the grid.

3325

Cache grid cannot be
destroyed when there are
global cache groups
or local cache groups in
cache grid enabled mode

Before destroying a cache grid, you must drop all global and local cache groups. TimesTen cannot destroy a grid if there are global cache group or local cache groups when cache grid is enabled.

3326

Cannot create a cache grid
or change cache grid while
attached or attaching to the
grid

Before creating a cache grid, you must detach from the grid. Use the ttGridDetach built-in procedure to detach from the grid.

3327

Only one uncommitted
create/destroy grid statement
is allowed. Please commit the
previous one before starting
a new one.

A statement to destroy or create cache grid must be executed in its own transaction.

3328

Have to commit grid
create/destroy statement
before attaching

You have to commit the current transaction before you can attach the grid.

3329

Have to detach from grid
before destroying a grid

Before destroying a cache grid, you must detach from the grid. Use the ttGridDetach built-in procedure to detach from the grid.

3330

Grid grid_name with
adminID ID does not exist

Cannot find the specified grid under the specified admin ID.

3331

Fail to send a message to
member member_name

There may be a network problem or the member has exited and TimesTen cannot communicate with that member.

3332

Failed to open a connection
member member_name from
member member_name.
Check if this node is still
alive and detach it if it is
dead and/or set its standby
state to fail

There may be a network problem or the member has exited and TimesTen cannot connect with that member.

3333

Time out waiting for a
response from member
member_name

TimesTen could not get a response from a remote member within the specified time. Either the member has exited or there was a network problem.

3334

Specified IP address and
port number combination have
been used

The IP address and port number of each node in a cache grid must be unique.

3335

Cannot use cache grid with
SMPOptLevel=0

Cache grid is not supported with the attribute SMPOptLevel set to 0. One or more cache grid members has the SMPOptLevel attribute set to 0. Change the SMPOptLevel setting for these members.

3336

Cache gride name must be set
for this database before
performing this operation

Before a database can attach to a cache grid, it must name the cache grid to which it would like to attach.

3337

Cannot stop the cache agent
when the cache grid is
attached. Detach the
cache grid first

A cache grid requires that the cache agent be running. Before stopping the cache agent, you must first detach the cache grid. Use the ttGridDetach built-in procedure to detach the member to the grid.

3338

The instance has been
deleted and has not been
propagated to Oracle. Please
make sure replication agent is up.

A cache instance has been deleted and this delete is being propagated to Oracle. No operations are allowed on this instance.

3339

Active or standby node of an
active standby pair must be
in active or standby state
before it can attach to a grid

Put the master of the active standby pair in the ACTIVE or STANDBY state and attempt to attach to the grid again.

3340

Passthrough
delete/update/insert
/truncate of cache grid
tables are not allowed

You cannot passthrough DELETE, UPDATE, INSERT or TRUNCATE statements to Oracle tables that are defined in a global cache group.

3341

Cache grid can only work
with active standby pair or
standalone node

When using replication in a cache grid, active standby pair is the only supported configuration.

3342

Inserted key already exists
on Oracle or remote node

Duplicate keys were inserted.

3343

Key was not found in current
owner member member_name

Key was not found in the member that owns the instance. This is an internal member communication error and it is not reported to the application level.

3344

Error creating grid threads:
thread_names

Some threads needed to support cache grid operation could not be created.

3345

Grid platform platform_name
and node platform platform_name
are different

Cache grid configurations must be set up on similar (homogenous) platforms.

3346

Grid release
release_number
and node release
release_number are different

All members of a grid must run the same major release of TimesTen.

3347

Both active and standby have
to attach to the grid before
loading can be done

Attach both the active and standby before attempting to load data into the global cache group.

3348

Missing communication
address for standby node.
Need to detach and re-attach
the grid with this information

If a database is part of an active standby pair scheme, both the active and standby communication addresses must be identified at attach time.

3349

Member member_name is not
in active state to receive
message destined to active node

The active state of a master of an active standby pair has changed. An old message was routed to a wrong node. The grid software retries one time. If the message still fails, you can retry the operation.

3350

Member member_name is not
in standby state to receive
message destined to standby
node

The standby state of a master of an active standby pair has changed. An old message was routed to a wrong node. The grid software retries one time. If the message still files, you can retry the operation.

3351

P2PTest failure at line
line_number, number of
message sent message_number:
message

Internal error used for testing communication problem.

3352

Key was not found in standby
member member_name

A key was not found in a standby node of a cache grid member. Replication may be behind and the instance has not been replicated. Retry the operation.

3353

Key is being loaded in
remote member member_name

The instance needed by a member is being loaded by another member of the grid. Wait and retry the operation.

3354

Grid thread died before
committing ownership change
to Oracle

A thread died while loading data. The change is being rolled back.

3355

Member member_name
timed out waitng for updates
to be propagated to Oracle

Instance loading failed because it took too long for a change on the instance to be propagated to Oracle.

3356

Error loading cache instance
from member member_name;
some instance is already
owned by some member

Bulk load of a global cache group can succeed only if no other members own any loaded instance.

3357

Failed to detach remote
member member_name. Member
was not attached or standby
is still attached and force
was not specified

Detaching a remote node member failed because this node member is not attached.

3358

Failed to detach remote
member member_name. Member
is still alive

Cannot detach a remote member that is still alive. That member must detach itself.

3359

Grid receiver thread
received obsolete message Id

Internal communication error. An old message was received.

3360

Grid already exists

Each cache grid must have a unique name. The name you chose is already assigned to a cache grid.

3361

Failed to check if inserted
key is unique in Oracle.
Reason inserted_key

The statement checks whether a newly inserted instance that already exists in Oracle fails. The failure reason is provided in the error message. The insert will fail.

3362

Node already attached to a grid

You have attempted to attach a node to a grid, but the node is already attached to a grid.

3363

Node is not attached to a grid

Cannot detach a member from the grid because it is not attached to the grid.

3364

Grid attached operation
failed. details

A member failed to attach to the grid. The message contains the details of this error.

Tables used to store ownership information cannot be dropped using the DROP TABLE statement. Drop the associated global cache group instead.

3380

This operation is invalid
with ownership table table.

The SELECT statement is the only statement that is allowed on tables used to store ownership information of global cache groups.

3381

Timed out waiting number
seconds for response from
remote nodes name to add or
remove node.

A remote member did not respond within the specified time during an attach or detach operation.

3382

Timed out waiting number
seconds for response from
remote nodes.

A remote member did not respond within the specified time during the current operation.

3383

Cache group string.string
failed ownership checking:
string.

Internal error while executing an internal built-in.

3384

Transparent load failed
because both primary and
backup ownership nodes are
down.

Both primary and backup nodes that contain ownership information needed for a transparent load are still down, even after three retries.

3385

Invalid char found in member
name string string.

The argument string of the ttGridDetachList built-in procedure that specifies a list of member names to be remotely detached contains some unrecognized characters.

3387

Conflict owner information
was found during load. Old
configuration owner owner,
new configuration owner owner.

Conflict ownership information was found while a transparent load was executed concurrently with a member attach or detach. This error is not expected to occur.

3390

Create/drop global cache
group is disallowed during a
grid member configuration change.

During a member attach, detach or fail over, global cache group creation and dropping are disallowed.

3391

Operation failed because
cache agent for remote member
member was restarted and
information was lost.

Internal communication error during ownership maintenance. The operation will automatically be retried.

3392

Operation failed because
remote member string(number) was
invalidated.

A remote member was invalidated during an ownership maintenance. Retry will be attempted if the member is recovered right away. Otherwise, the command will fail

3398

Mismatched cache group type
in grid member grid_member

An attach failed because the current node did not define some of the global cache groups or mismatch global cache group definition. Define and fix the cache group definition and retry the attach.

3399

The recorded information
indicates that there are
or were number attached
members of the grid but this
member failed to communicate
with any of them

During an attach, the attaching node cannot contact any other members even though the grid information indicates that there are some attached members. This could happen because some members exit before detaching from the grid. All these members must be detached from the grid to clear up the grid.

3400

The following members
members are not responding.
Check if they are still alive
and detach them if they are dead.

The cache grid was not able to communicate to the members specified. The operation that must communicate with these members will fail. Check if these members are still operational. If they are not operational, use the ttGridDetach command to detach them from the grid.

3401

P2P error: string

This error is issued when a problem occurs with the peer-to-peer communication layer of cache grid. The provided string provides details for the problem.

The active standby pair cannot be dropped from a member that is being attached to the grid. You must detach the member from the grid and retry the command.

3403

This node was attached as
part of an active standby
pair and the other node of
the active standby pair is
still attached. Detach the
other node first and retry.

A node of an active standby pair was converted to a stand-alone node and an attempt was made to attach this node to the grid. The operation failed because the previous standby of this node is still attached to the grid. Detach the standby node first and then retry the command.

3404

Cannot drop AWT cache group
with unpropagated deletes

Wait until all deletes of a dynamic ascynchronous writethrough cache group are propagated to Oracle before trying to drop the cache group. Ensure the replication agent is up. Wait until the replication agent completes propagating before retrying the drop.

3405

Cannot do blocking
checkpoint until all commited
deletes of AWT cache groups
have been propagated to
Oracle

A non-fuzzy checkpoint cannot complete until all committed deletes of all dynamic asynchronous writethrough cache groups have been propagated to Oracle. Ensure that the replication agent is up. Wait until the replication agent finishes propagating all changes before retrying the checkpoint.

Global select failed because temporary data partition free space is below the minimum threshold of the specified number of bytes.

3412

Detach is disallowed on
transaction with uncommitted
grid work

A transaction with uncommitted statements that involves global cache group ownership change is not allowed to execute detach command. You must commit the transaction first.

3413

Internal error: conflict
ownership acquisition of
threads of same member.

Internal error. Contact TimesTen Technical Support.

3414

Member failed to attach as
an active during the last
fail-over. Please re-execute
attach before performing this
operation.

The last failover that turned this node into an active node has failed to complete grid failover. Execute the attach command before performing operations on any global cache group tables.

3415

Internal error: instance was
found but not qualified.

Internal error. Contact TimesTen Technical Support.

3416

Member is doing failover and
not in grid active state yet.

Grid fail-over is still in progress, so operations on global cache group tables are not allowed.

3417

Internal error: Propagation
thread is executing on active
node.

Internal error. Contact TimesTen Technical Support.

3418

Load/unload are disabled
because there may be some
unpropagated update before
the last failover/restart.
Please check if the standby
is up and set its state to
fail if it is not up.

Operations on global cache group tables are not allowed, since there may still be some un-propagated changes since last fail-over or restart. If the standby is not active, set its state to fail so propagation can progress.

3419

Cannot detach standby node.
Either detach active node
first, or stop replication
agent on standby and use
ttRepStateSave to set its
replication state to 'FAILED'
before detaching standby.

Cannot detach the standby node that is not in failed state before detaching the active node. Either detach the active node first or set the standby state to failed from the active node before detaching the standby.

3420

Cannot detach from cache
grid when there are pending
transaction on global cache
groups.

All pending transactions on global cache group table must commit and changes must be propagated to Oracle before a node can detach.

Errors 4000 -4999

Error number

Error or warning message

Details

4053

Internal error. error_number

Internal error. Contact TimesTen Technical Support.

4054

Internal warning: detailed_warning

This message warns that TimesTen adjusted either the heap page sizes or number of heap pages during a heap validity check. These values may have required readjusting because they had been overwritten.

4501

Data store cannot
checkpoint to a network file
system

Database files cannot be located on a network file system. Move the checkpoints to a local file system and retry the operation.

4502

Data store cannot log to a
network file system

Database files cannot be located on a network file system. Move the checkpoints to a local file system and retry the operation.

4600

Argument error and error

Bad Argument Generic error message

4601

Argument errormessage

Bad argument generic error message

Errors 5000 -5999

Error number

Error or warning message

Details

5002

Unable to connect to the
cache agent for
data_store_path_name;
check agent status

Cannot connect to Oracle for the named database. Check the status of the cache agent.

5006

Defining SQL string exceeds
maximum allowed length

The sum of the "Column Mapping," "Primary Key" and "SQL Piece" specifications in the configuration file exceeds the maximum allowed length.

5007

Cache agent error

There was a communication failure between the TimesTen cache agent and the client process.

5008

ODBC call failed

The TimesTen cache agent got an error on an ODBC call. For more details, look at the user error log entries.

5010

No OracleNetServiceName
specified in DSN

An attempt was made to start a TimesTen cache agent for a DSN that does not have the OracleNetServiceName attribute specified.

5011

Oracle (OCI8) call failed

The TimesTen cache agent got an error on an Oracle (OCI8) call. For more details, look at the user error log entries.

5012

Oracle login failed

The TimesTen cache agent could not connect to the Oracle database with the given username and/or password.

5013

Operation requires cache
connection

The TimesTen cache agent could not execute the operation because it was not able to connect to TimesTen and/or Oracle. Ensure that the user name, password and Oracle ID are correct.

5014

Could not execute defining SQL

The SQL specified for defining the cached table could not be executed against the Oracle database. Check the column names and table names.

5015

Mismatch in number of
columns extracted and number
of columns in cached table

Internal error. Contact TimesTen Technical Support.

5016

Cache agent has too many
existing connections

The number of active connections to this TimesTen cache agent exceeds the maximum allowed limit.

5019

Bad table name specification

The "Cached Table" specification in the configuration file has an invalid table name.

5020

Warning(s) during
population of cache. See the
user error log for details.
detailed_error_message

A warning was given during table population. View the user error log for more details.

5021

Could not get meta data
from Oracle: detailed_error_message

The Cache Administrator could not get the requested metadata from Oracle.

5022

Could not open output file
for writing Oracle meta data

The Cache Administrator was not able to write the Oracle metadata to the output file because it was not able to open the output file.

5025

Commit failure in Oracle.
Transaction must be rolled
back in TimesTen.

Commit failed in Oracle. The TimesTen transaction must be explicitly rolled back.

5026

Cannot alter cached tables

Cached tables cannot be altered. To modify a cached table and execute the new CREATE CACHE GROUP statement.

5029

"Warning(s) while
populating the cache.
detailed_warning_message(s)

A warning was generated while populating the cached table. The details are attached to the message.

5030

Communication buffer
overflow. The cache group
definition is too large to
perform this operation

The TimesTen cache agent communication buffer overflowed. The operation failed. The most likely cause of this error is that the cache group contains several tables and/or each table contains several columns and the total length of these tables and columns has exceeded the communication buffer

5034

The operation must be
executed within its own
transaction

Each cache group operation must be 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

Internal error. Contact TimesTen Technical Support.

5036

Warning(s) while populating
the cache.
detailed_warning_messasge(s)

Some SQL warnings were generated while loading or refreshing the cached table. Detail warning messages are appended to the end.

An error occurred while loading or refreshing the cached table. The detailed error follows this error message.

5038

Warning(s) while populating
the cache. detailed_warning_message

Some SQL warnings were generated during the population stage of the MERGE operation.The detailed error follows this error message.

5039

An error occurred while
refreshing the cache_group_namedetailed_error_message

An error occurred while refreshing the cached table. A detailed error follows this error message.

5045

Cache group operations may
not use data store level locking

Cache group operations require row-level locking to allow the TimesTen cache agent to get simultaneous access to the database.

5046

Commit/rollback required
after Cache operation

An error occurred after executing a LOAD, UNLOAD or REFRESH command. This error occurs when the user does not immediately commit or rollback the transaction after executing a LOAD, UNLOAD or REFRESH command. These cache group commands are required to be the only operation in the transaction. To fix this error, commit or rollback right after these cache group operations.

5047

This operation is not
allowed on cached tables

An index from a cached table cannot be dropped.

5048

Feature, feature_name,
not supported

The feature entered is invalid or not supported.

5050

Cache group definition was
too long. Current system
limit on field_name is size
bytes. Specified definition
requires size bytes

Either the cache group WHERE clause is too long or the cache group has too many long column names or too many tables. The maximum allowed length of the cache group WHERE clause is 4096 characters.

5051

Commit message to cache
agent failed. Cache agent
must be restarted

Failed to notify the cache agent of the transaction commit. Check if cache agent has been shut down. If so, restart the cache agent.

5052

Cache group name required
with install_flag value 1

No cache_group_name parameter was provided for the ttCacheSqlGet built-in procedure call. The cache_group_name parameter cannot be NULL or empty when the install_flag parameter is set to 1.

5053

Add/Drop foreign keys are
not allowed on cached
tables

Adding or dropping foreign keys to cached tables is not supported in TimesTen.

5054

Detect loss of Oracle
Connection (error_number)
during rollback. Oracle
rollback will be implicit

The Oracle connection terminated during a transaction rollback. The pending Oracle transaction was (or will be) rolled back by the Oracle server. The error_number is either an ORA-xxxxx message, an Oracle error code that was returned by Oracle during rollback, or "no error code," which means the connection was broken prior to the Oracle rollback request.

5060

Rollback on TimesTen not
available in no logging
mode. Rollback on Oracle
succeeded. Must refresh the
affected cache groups

An error was encountered when propagating to Oracle. The transaction on Oracle has been successfully rolled back. Because there is no rollback available on TimesTen, the user must manually fix the TimesTen transaction. One way to make the cache groups consistent with Oracle is to unload and reload all affected cache groups.

5061

Oracle and TimesTen in
inconsistent state.
Invalidating the data store.
Must refresh the affected
cache groups

An error was encountered when propagating to Oracle. The rollback on Oracle also failed. TimesTen and Oracle data are in a transactionally inconsistent state. One way to make the cache groups consistent with Oracle is to unload and reload all affected cache groups.

5064

The Oracle client version
version_number is not
compatible with Oracle
server version
version_number.
Upgrade Oracle serve to
version_number or higher.

An Oracle Client Oracle client version is 10.2 or higher and it is not compatible with the Oracle Server version. This error can be encountered by the application during any operation that requires a connection to Oracle.

Fix is to use compatible Oracle client/server version according to our docs.

5067

Name name is already used
by an existing object

The name specified is already in use. Specify a unique name for the indicated object.

5068

Argument argument_name ignored

An IMDB Cache built-in procedure was called with an argument that was not needed. The argument was ignored and the built-in was executed without the argument.

5069

Argument argument_nameerror_message

An IMDB Cache built-in procedure was called with an invalid argument. The error message indicates the invalid argument.

The library used by IMDB Cache could not be loaded. This can happen if:

The library was not installed or is named differently than the Oracle OCI

The library was not found

The library search path does not contain the TimesTen library directory. The search path is defined by the PATH environment variable on Windows NT systems or the LD_LIBRARY_PATH environment variable on UNIX systems.

The Oracle library bits do not match the TimesTen bits. For example, on HPUX11, if you receive this error with errorno=8 (exec format error), the common cause is that the 64-bit Oracle shared library got linked in instead of the 32-bit library. Check the values of your SHLIB_PATH, LD_LIBRARY_PATH, and PATH environment variables. Make sure $ORACLE_HOME/lib is not in any of them and also make sure $ORACLE_HOME/lib32 is in SHLIB_PATH.

This is a warning. The comparison rule for Oracle VARCHAR differs from the TimesTen comparison rule. This may cause a primary key constraint violation on TimesTen while loading Oracle rows. The problem may happen when there are trailing spaces in the Oracle data. TimesTen generates this warning whenever there is a VARCHAR column in a cache table.

This is a warning. Oracle and TimesTen have different implementations of floating point data types and the precisions are different. As a result, the cached value may be slightly different than the value in Oracle. TimesTen generates this warning when you try to create a table with a REAL, FLOAT or DOUBLE type.

5114

Unsupported type mapping
for key column column_name

The data type mapping rules were violated on a key field. See "Data type support" in the Oracle In-Memory Database Cache User's Guide for more information.

5115

Unsupported type mapping
for column column_name

The data type mapping rules were violated on a non-key field. See "Data type support" in the Oracle In-Memory Database Cache User's Guide for more information.

5116

Column column_name does not
exist in Oracle

Verify that you have correctly spelled the column name or provide a new name.

5117

Illegal WHERE clause for
cache table table_name

The WHERE clauses specified in the CREATE CACHE GROUP statement do not work on Oracle.

5118

Column column_name has
different precision/ scale
in Oracle

This is a warning. Oracle and TimesTen have different implementations of floating point data types and the precisions are different. TimesTen issues this warning when a TimesTen DECIMAL type is mapped to an Oracle NUMBER type.

5119

Column column_name has
different nullability
setting in Oracle

This is a warning. The nullability setting of a column on TimesTen differs from that of the column on Oracle.

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

The cache group operations are restricted to full cache group LOAD CACHE GROUP, UNLOAD CACHE GROUP and MERGE operations because TimesTen cannot find a primary key or a unique NOT NULL index on Oracle to match the cache table's primary key.

The cache group operations are restricted to full cache group LOAD CACHE GROUP, UNLOAD CACHE GROUP and MERGE operations because non-standard type mapping was used.

5123

Operation not allowed on
restricted cache group
cache_group

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

5124

Autorefresh/propagate are
not allowed on restricted
cache group

AUTOREFRESH and PROPAGATE are not allowed on a restricted cache group. A cache group is restricted if it has a non-standard data type mapping in one of its columns or if there is no matching primary key on Oracle.

5125

Caching of Timestamp
column(s): fractional
seconds may be truncated

The scale of the TimesTen TIMESTAMP type is always 6. Mapping of Oracle TIMESTAMPCOLUMNS with a scale other than 6 to a TimesTen TIMESTAMP column may cause silent truncation of the column value at runtime.

See "Data type support" in the Oracle In-Memory Database Cache User's Guide for a list of supported data type mappings.

5127

Backend connection invalid.
error_details

An error occurred while trying to connect to Oracle or an invalid backend database was specified in the connection.

5128

handle_name handle is
invalid. The Oracle
connection may have been
lost. Retry your operation.

IMDB Cache handle has been invalidated. In most cases, this occurs when the connection to Oracle has been lost. Check if the Oracle 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.

IMDB Cache handle has been invalidated. In most cases, this occurs when the connection to Oracle has been lost. Check if the Oracle instance is up and retry the operation. The prepared statement must be re-prepared.

5130

Error executing the
following statement on
Oracle: query

The execution of query failed on Oracle. Examine the query and verify the Oracle schema has not changed during IMDB Cache operations.

Common causes of connection failures are incorrect Oracle Service Name, user id or password, TNS_ADMIN or location of the Oracle installation. You may also find the Oracle error number in other messages on the error stack. Check Oracle error message documentation for the corresponding Oracle error.

5132

SQL command is no longer
valid. type handle has
been invalidated. The Oracle
connection may have been
lost after the statement was
prepared.

A callback function to handle Oracle RAC failures was not registered. You must manually reconnect to Oracle after a connection failure.

5163

Oracle failover failed with
event event_ID. Retried
for number minutes

TimesTen was not able to re-establish a connection to Oracle. TimesTen retries the connection for the indicated number of minutes.

5164

No matching foreign key
with cascade action for
table table_name on Oracle

To specify a CASCADE DELETE foreign key on a cache table that is specified as PROPAGATE, or belongs to a cache group that is specified as AWT or SWT, there must be a matching CASCADE DELETE foreign key defined on the corresponding Oracle table. You must either remove the CASCADE DELETE foreign key on the cache table or add one on the Oracle table.

5165

Autorefresh state state
for cache_group is
incompatible with
replication scheme.
Autorefresh state should be state.

The AUTOREFRESH state indicated in the messages for the specified cache group is incompatible with the associated replication scheme.You must either ALTER or CREATE the cache group with the compatible state indicated in the message.

5166

Autorefresh state state
for store is incompatible
with replication store state
state. Autorefresh state
should be state.

The AUTOREFRESH state indicated in the messages for the specified cache group is incompatible with the associated replication store state.You must either alter or create the cache group with the compatible state indicated in the message.

5167

Deprecated type mapping for
column column_name

The type mapping is not supported. You must change the type of the indicated column.

5168

Restricted cache groups are
deprecated

Restricted cache groups are supported in this release for backward compatibility.

5169

The data store must be in
Oracle data type mode
(TypeMode=0) in order to use
any of the Cache Connect
features.

Oracle 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
store becuase of the reasons
stated below.

Metadata stored on Oracle for cache groups is updated by the cache and replication agents after they are started and they are able to connect to Oracle. Ensure that the cache and replication agents are started on the destination database.

5171

Lookup for username
user_name failed on Oracle.

The cache operation requires the specified user name, but not such user is found on Oracle.

You have specified a column length on the specified table that is greater than the maximum allowed length of 4000 bytes.

5182

IMDB Cache is supported
only with Oracle server
release 10.2 and later.

Version of the Oracle RDBMS Server is not supported. The Oracle Server must be release 10.2 or later.

5183

Function <function_name>
was not in the library. The
function will not be
called.

Discover that a function is not a part of the library during the first cache connect operation within an application or during the startup of the replication agent. No action necessary, as the function will not be called by cache connect. Check that the OCI client library version is 11.1 or later.

5184

<owner>.<name> cannot be
cached. The Oracle synonym
is owned by another
user and cannot be cached by
the current session user.

Tried to create a cache group on an Oracle synonym that is owned by another user in Oracle. Resolve by performing one of the following:

The owner of the synonym creates the cache group.

Create another synonym to point to the other owner's synonym. The cache group then references the new synonym.

5185

Cache admin user
<cache_admin_user_id> does
not have <privilege>
Oracle privileges on
<schema>.<object>.

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.

The user should grant the appropriate Oracle privileges to the cache admin user.

5201

Operations for Cache Agent
are not allowed for
temporary data stores

Oracle data can be cached only in a permanent TimesTen database.

5202

Environment variable
ORACLE_HOME must be set to
perform this operation

Set the ORACLE_HOME environment variable to point to the location of your Oracle installation.

To cache Oracle data, you must specify the location of the OCI.DDL in the PATH environment variable.

5205

OCI.DLL must be in PATH to
perform this operation

To cache Oracle data, you must specify the location of the OCI.DDL in the PATH environment variable.

5206

Environment variable
ORACLE_HOME must not be more
than 256 characters long

TimesTen limits the value of $ORACLE_HOME to 256 characters.

5207

The cache admin UID cannot
be changed while there are
any cache groups in the
datastore. Drop all cache
groups and try again.

The cache administrator UID/PWD cannot be set if there are any AWT or autorefresh cache groups with state ON or PAUSED. Drop or alter the cache group and reset the UID/PWD.

5208

There are existing cache
groups under the Cache
Admin's schema on Oracle.
schema_name

When TimesTen starts to track DDL changes on Oracle, there are already existing cache groups in the database. Since the corresponding Oracle tables may have been altered before the tracking started, there may be an inconsistency between the cache schema and the Oracle schema. Verify that the TimesTen and Oracle schema still match.

5209

Cannot start cache agent
because TNS_ADMIN not
specified during install.
Use ttModInstall -tns_admin to fix.

The user did not specify a value for TNS_ADMIN during the installation of TimesTen. You cannot start a cache agent without specifying the TNS_ADMIN variable.

Data truncation error occurred on Oracle in the named Oracle OCI function.

5227

Insufficient privileges
name occurred while
performing an Oracle
operation in function:
error_message.

The user has insufficient privileges. Grant the user the appropriate privileges and retry.

5228

A transient mode
occurred while performing an
operation in function:
error_message.

There was a temporary error while executing the indicated function. The transaction must be rolled back. The details are in the error message. The mode is set to error.

5229

An Oracle savepoint error
occurred: error_message

This cache operation requires TimesTen to set a savepoint on Oracle. The setting failed. The details are in the error message.

5230

A transient mode occurred
while performing an Oracle
operation in function:
error_message.

There was a temporary loss of connection to the Oracle server while executing the indicated function. The transaction must be rolled back. The details are in the error message. The mode is set to error.

5243

The operation cannot be
executed if the Replication
Agent is not running.
Check the status of the agent.

Check the status of the replication agent and restart the agent if it is not running.

5244

Asynchronous WriteThrough
will not be enabled until
the Replication Agent for
this datastore has been
started.

Asynchronous writethrough cache groups require the replication agent to be running. The replication agent appears to be stopped. Restart the replication agent if it is not running.

5245

The operation cannot be
executed while the
Replication Agent for this
datastore is running.

Stop the replication agent.

5246

The Replication Agent for
this datastore is currently
running.

Informational message.

5247

The operation cannot be
executed while the cache
agent for this data store is
running.

Stop the cache agent.

5249

Awt Initialization Failure:
detailed_error_number

An error occurred while initializing the asynchronous writethrough thread in the replication agent.

5250

Awt Initialization Failure.
Could not compile meta data
SQL.

TimesTen attempted to get metadata from Oracle. One of TimesTen SQL statements did not compile.

5251

Cache admin uid and pwd
must be set since there are
awt cache groups in this
datastore. Shutdown the
replication agent and the
cache agent, set the cache
admin uid and pwd, and
restart the agents.

Asynchronous writethrough cache group must have the cache administration user ID and password set.

1. Stop the replication agent and the cache agent.

2. Set the cache administration user ID and password by using either the ttCacheUidPwdSet procedure or ttAdmin -cacheUidPwdSet -cacheUid -cachePwd.

This error can occur during execution of ttAdmin -duplicate. Information about an asynchronous writethrough cache group could not be found in the TimesTen schema.

5256

Could not find runtime data
for AWT.

This error can occur during the creation of an asynchronous writethrough cache group. The replication information for the cache group could not be found. Try creating the cache group again. See "Permanent Oracle errors reported by TimesTen" in the Oracle TimesTen In-Memory Database Troubleshooting Procedures Guide.

The cache administration user ID or password is not set or could not be found during startup of an asynchronous writethrough cache group. Use ttCacheUidPwdSet to set the cache administration user ID and password and restart the replication agent.

5258

An update operation tried
to update a row that does
not exist on Oracle.
Expecting number updates
and number rows were
affected.

The transaction was rolled back because there were update operations on rows that are not in the Oracle tables.

statement is not allowed
when transaction isolation
level is set to
serializable.

The CREATE, DROP and ALTER CACHE GROUP statements are not allowed with the serializable isolation level. Reset the transaction isolation level to read-committed isolation and re-execute the statement.

5280

Autorefresh state of
string.string is
string; autorefresh state
must be string.

The specified cache group is in the incorrect autorefresh state for the operation you are attempting. Use the ALTER CACHE GROUP ... SET AUTOREFRESH STATE command to set the autorefresh state as indicated.

5281

Autorefresh of specified
cache group is already in
progress.

A new autorefresh operation cannot be initiated while a current autorefresh operation is in progress. Wait for the current autorefresh operation to complete and try again.

5282

ttCacheAutorefresh cannot
be called from the standby
of an A/S pair. Call it
from the active instead.

The ttCacheAutorefresh built-in procedure cannot be called from the standby node of an active/standby pair. Call it from the active node instead.

5283

Autorefresh did not
complete within 24 hours

When called with SYNCHRONOUS >1, the ttCacheAutorefresh built-in procedure waits for the autorefresh operation to complete. In this case, the autorefresh operation did not complete within 24 hours. Check the daemon log for issues.

5284

Error launching
autorefresh, see daemon log

The ttCacheAutorefresh built-in procedure encountered an unexpected error while initiating the autorefresh operation. Check the daemon log for issues.

5285

Autorefresh failed, see
daemon log

The autorefresh operation initiated by the ttCacheAutorefresh built-in procedure failed. See the daemon log for details.

5286

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

The TimesTen cache agent keeps a history of the 10 most recent autorefresh operations. The autorefresh operation that you initiated with the ttCacheAutorefresh built-in has completed. Before its status could be read from the autorefresh history, it was displaced by another autorefresh operation that occurred at an unusually high rate. This is not necessarily a problem. The autorefresh operation you initiated may have completed successfully. Check the daemon log for the status of your autorefresh operation.

5287

Unexpected status returned
by autorefresh, see daemon log

The ttCacheAutorefresh built-in procedure encountered an unexpected status return value from the autorefresh operation. Check the daemon log for issues.

5288

Autorefresh failed due to
contact lost with Oracle
(dead cache group)

The autorefresh operation failed because contact with the Oracle RDMBS server has been lost. Check the status of the Oracle server.

The TimesTen cache agent was not able to allocate either an Oracle or TimesTen statement handle. See the user error log for more details.

5801

Could not get a column
attribute.

The TimesTen cache agent was not able to get information about the columns in a table. The operation that the agent was performing failed. See the user error log for more details.

5900

Could not get the start and
end of auto-refresh log

This error occurs when the TimesTen cache agent is not able to access the log table or the log table is corrupt. When this happens the agent tries to access the log table a few times. If all attempts fail, the agent stops incrementally auto-refreshing the cache group.

The log table log_table_name for autorefresh of the table owner.table cannot be found. It may be that the cache administrator user does not have sufficient privileges to read the log table.

5902

The length of the name of
the Oracle object has
exceeded the expected
length. Call
technical support

This is a fatal system error. Contact TimesTen Technical Support.

5903

Log was truncated during
incremental refresh.
Report to technical support.

This is a fatal system error. Contact TimesTen Technical Support.

5904

A cache admin uid was not
set before starting the cache agent.

If you are incrementally refreshing a cache group, the cache administrator user ID is required.

1. Stop the agent.

2. Set the cache administration user ID and password by using either the ttCacheUidPwdSet procedure or ttAdmin-cacheUidPwdSet -cacheUid -cachePwd.

3. Restart the agent.

5905

A cache admin pwd was not
set before starting the
cache agent. The Oracle
objects required for
incremental autorefresh must
be created manually.

1. Stop the agent.

2. Set the cache administration user ID and password by using either the ttCacheUidPwdSet procedure or ttAdmin-cacheUidPwdSet -cacheUid -cachePwd.

3. Restart the agent.

5907

The cache admin uid 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.

Set the cache administration user ID and password by using either the ttCacheUidPwdSet procedure or the ttAdmin utility and retry the operation.

5908

The cache admin pwd 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.

Set the cache administration user ID and password by using either the ttCacheUidPwdSet procedure or the ttAdmin utility and retry the operation.

5909

The cache admin user id was
not set before starting the
agent. Set the cache admin
user ID and password either
through the built-in
procedure ttCacheUidPwdSet
or the utility ttAdmin and
try again.

The TimesTen cache agent must be started with the cache administration user ID and password for autorefresh and AWT cache groups.

1. Stop the agent.

2. Set the cache administration user ID and password by using either the ttCacheUidPwdSet procedure or ttAdmin-cacheUidPwdSet -cacheUid -cachePwd.

3. Restart the agent.

5911

Could not login into Oracle
using the cache admin user
id and password.

The TimesTen cache agent was not able to login into Oracle using the cache administration user ID and password that were provided. Check if the cache administration user ID and password are valid on the Oracle SID that you specified for the DSN.

5912

Cache admin uid is not a
user on the Oracle instance.

Invalid cache administration user ID provided for the cache agent. Check if the cache administrator user ID that was provided is a user on the Oracle SID for the DSN.

5913

Table parameter should be NULL

The table_name parameter for the ttCacheSqlGet built-in procedure should be NULL.

5914

table not found in Oracle.

The TimesTen Cache Agent could not find the Oracle table to be cached. Check if the table exists on Oracle. Also verify that the cache administration user ID has the privilege to access the table.

5917

Object id ID not found or
the user user does not
have sufficient privilege to
view the object

Indicates that either the Oracle table that was cached has been dropped in Oracle or, if this error is returned in response to a CREATE CACHE GROUP statement, the specified Cache Agent account does not have the appropriate privileges. See "Grant privileges to Oracle users" in the Oracle In-Memory Database Cache User's Guide for details.

5918

Log table table_name not
found or the user user does
not have sufficient
privilege to view the log
table

The autorefresh log table could not be found on Oracle, or the specified cache agent account does not have the appropriate privileges.

5919

The description is
different from when the
cache was created or no
longer exists. The cache
group definition is no
longer valid

Verify that a cache group exists with the original attributes.

5920

Oracle object id objectID
or log table table_name
for cache group
cache_group_name not found
on Oracle

TimesTen cannot find the Oracle object with ID objectID or the TimesTen installed table table_name for AUTOREFRESH. Check that the table has not been dropped or altered under AUTOREFRESH. Also, check that no changes have been made to the schema on Oracle.

5921

Could not connect to
Oracle. Check the
status of the Oracle instance.

Verify that the Oracle instance exists.

5922

The minimum stop timeout
value is min_value which
will be used instead of
specified_value

The timeout value specified for the ttCacheStop procedure is too small. The default value is used. Autorefresh does not start until able to connect. Check the user error log for any errors.

5923

Cache agent has deferred
the create/alter cache group
request because it is not
connect to Oracle yet.

The CREATE, ALTER or DROP CACHE GROUP statement cannot be completed because the cache agent is still waiting to connect to Oracle. Verify the Oracle instance is running and the network connection is also available. Check the user error log for any errors.

5925

Cache admin user does not
have privilege to create
trigger_name trigger.
Grant CREATE ANY TRIGGER
privilege or use
ttCacheSqlGet built-in to
manually create the trigger

The cache administrator does not have Oracle CREATE TRIGGER privileges, so the operation failed. Either grant the privilege to the cache administrator UID or use the ttCacheSqlGet built-in procedure to manually execute the SQL statement.

IMDB Cache failed to verify the Oracle login for named user ID.The common causes of this errors are:

The specified UID/PWD is incorrect

The OracleNetServiceName setting is incorrect

The Oracle listener is down

The Oracle server is down

5936

Need to specify both cache
admin uid and pwd or neither
of them when starting the
cache agent.

The cache administration user ID or password was omitted when calling the deprecated built-in procedure ttOracleAgentStart.

5937

Need to specify both cache
admin uid and pwd to start
the cache agent since there
are cache groups specified
with autorefresh or there
are asynchronous cache groups.

The cache administration user ID and password must be set prior to the start of the cache agent if there are autorefresh or asynchronous writethrough cache groups. Use the ttCacheUidPwdSet procedure to set the User ID and password and restart the cache agent.

5938

owner.name or
owner.name table does not
exist on Oracle. Oracle
objects related to cache
groups may not get cleaned up.

The specified objects created by TimesTen on Oracle are missing. Drop and recreate the cache groups in TimesTen.

5940

The operation failed
because the cache admin uid
could not be verified.
Reconnect and try again.

The cache group operation requires that the cache agent be first started with the assigned cacheUid and cachePwd. 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 cacheUid to
cacheUid. Switching over
to the new uid.

The cache administration user ID has been changed by the user. Verify that the cache agent is started with a new cacheUid.

5942

The specified cache admin
uid cacheUid and pwd
(hidden) does not match the
stored ones. Use
ttCacheUidPwdSet() to change
the stored ones.

The cache administration user ID and password do not match the stored cache administration user ID and password. Change the stored cache administration user ID and password with the ttCacheUidPwdSet procedure.

The cache administration user ID must be the same on the source database and the destination database.

5947

Cache admin UID and PWD
need to be specified for
datastore duplication
because there are
AUTOREFRESH or ASYNCHRONOUS
WRITETHROUGH cache groups

The cache administration user ID and password are required to duplicate autorefresh or AWT cache groups.

5948

Subscribing stores in
Active Standy schemes must
specify -noKeepCg

When duplicating databases that contain Active Standby schemes, cache group tables cannot be maintained as cache group tables. You must specify the -noKeepCG option with ttRepAdmin -duplicate.

5949

Cache agent uid UID is
different from the data
store cache uid UID

Internal error. Contact TimesTen Technical Support.

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.

You must have the appropriate privileges on the Oracle database to create the requested objects. Either obtain the appropriate privileges or install the objects manually.

5951

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.

You must have the appropriate privileges on the Oracle database to create the requested objects. Either obtain the appropriate privileges or install the objects manually.

5952

Metadata objects on Oracle
are missing. Either grant
appropriate privileges to
cache admin user to create
the objects and reexecute
ttCacheUidPwdSet or install
the objects manually

The cache admin user does not have the appropriate Oracle RDBMS privileges to create and store metadata information on the Oracle RDBMS server. Either grant the appropriate privileges to the cache admin user on the Oracle RDBMS server or install the metadata objects manually.

5953

The stringstring is
different from when the
cache was created or could
not be found. Check if you
have SELECT privileges to
the table on Oracle
Database. If
you have privileges, then
the cache group definition
is no longer valid.

If the user has SELECT privileges to the table on the Oracle RDBMS server, then the cache group is no longer valid. You will need to recreate the cache group.

5992

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.

You must have the appropriate privileges on the Oracle database to create the requested objects. Either obtain the appropriate privileges and re-execute the ttCacheidPwdSet procedure or install the objects manually.

The refresh operation
failed. The agent will try
again to refresh the cache
group

A nonfatal error, such as a lock timeout, occurred during autorefresh. The cache agent retries the autorefresh.

5992

Unable to cleanup orphaned
Oracle objects because it
could not lock the
appropriate tables

When the cache agent starts, the agent removes any orphaned Oracle objects that were used in a previous autorefresh process. Before dropping the orphaned object, the agent locks the FT_USER_COUNT table so that no other agent can create new or drop old Oracle objects. This warning is triggered when the agent was not able to lock the FT_USER_COUNT table.

5994

Existing 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

Lock request denied because of conflict on conditional request. This error only appears in the TimesTen user error log.

6002

Lock request denied
because of deadlock
Details: error_description

Unable to grant lock request because granting it would cause a deadlock situation. The application must rollback and re-start the whole transaction. For information on lock resources and modes indicated in this message, see "ttXactAdmin" in Oracle TimesTen In-Memory Database Reference.

6003

Lock request denied
because of time-out
Details: error_description

Unable to grant lock request because the lock is not immediately available or a timeout occurred waiting for the lock to be released. (If the lockwait interval is set to 0-2 seconds, this error may also result from a deadlock, as the deadlock detector runs only every 2 seconds.)Retry the lock request. If denied, rollback and restart the operation. For information on lock resources and modes indicated in this message, see "ttXactAdmin" in Oracle TimesTen In-Memory Database Reference.

The lock manager has run out of memory in the temporary segment. Compact the database, or increase the size of the temporary segment.

6006

Lock-wait interval
must be between 0 and
1,000,000

The lock-wait interval is out of range. Use the ttLockWait built-in procedure to set the lock-wait interval.

6009

Active connection
has conflicting
isolation level

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. The conflicting transactions must be committed or rolled back. 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:
data_store_name)

The database is not valid. See the description of error 994 for more information.

6011

lock request denied
(locksleep error
error)

Internal error. Contact TimesTen Technical Support.

6013

Bad value for check
Override parameter,
should be 0 or 1

Provide the appropriate attribute value. Legal values are 0 or 1.

6014

Row list maintenance
error. To avoid this
use prefetchcount of 1

A row list that was thought to be wide enough for storing rowids was not wide enough. The system underestimated the required memory size. The fetch failed. No invalidation should have occurred. Use a prefetch count of 1 and try to force the system not use these lists. Alternatively, use cursor stability isolation mode.

6015

Transaction priority
value must be between
0 and 65535

Internal error. Contact TimesTen Technical Support.

6101

Attempting operation
beyond end of cursor

Application is trying to fetch rows beyond the end of cursor. This typically happens when the application does not check for end-of-cursor indication and attempts to seek beyond.

6102

Cursor is not updatable

Application attempts to open cursor for updating on a non-updatable SELECT.

6103

Cursor has no
current row defined

Cannot perform the delete or update operation because the operation is being done on CURRENT of cursor before the first FETCH.

6104

Column is not
updatable via this cursor

The column cannot be updated by the cursor because the column is not a simple column or it does not exist.

6105

Update conflict
caused by open index
cursor(s) on table

There is an open index scan on the table and the application attempts to delete a row from the table or the application attempts to insert a row into the table, thereby attempting the deletion or insertion of a key into one or more indexes.

6106

Operation conflicts
with open table
cursor(s)

The operation is not permitted when a cursor is open on the table. Close any cursor on the table and retry the operation.

6107

Invalid cursor

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.

6108

Cursor state made
"unpositioned" by
updates in the same
transaction

Within the same transaction, an operation has deleted the page of the row that the cursor was positioned on. This error can occur when the following conditions are met:

- Logging is turned off, and- A searched CREATE VIEW (DELETE FROM ... WHERE ...) is issued on a table on which this transaction also has an open cursor, and

- The transaction does the next fetch on the cursor and tries to fetch the rows it deleted via the searched delete.

6109

Cannot open cursor
until updates are
committed

There is an open index scan on the table, and the application attempts to delete CURRENT of cursor, or the application attempts to update CURRENT of cursor. One (or more) of the columns being updated is also the key for the index being used in the index scan.

6110

Cursor update
disallowed due to
conflict with index

Cannot use a cursor to delete from or update an index.

6111

SQL Query has
reached its timeout
limit and has been
terminated

This statement has exceeded the maximum time allowed by the SQL_QUERY_TIMEOUT option. TimesTen has stopped its execution and removed its effects, if any

6112

Ref cursor binds are
not allowed in SQL
statements executed
from PL/SQL

This error is thrown whenever refcursor bindings are found in any SQL statements from PLSQL

6200

New value for
permanent data
partition size
ignored since smaller
than current value of
megabyte_count megabytes

Warning: Connect PermSize is ignored if it is smaller than or only slightly greater than the current permanent data partition size.

To avoid this warning, increase the value of the PermSize attribute or set PermSize=0 to leave the permanent partition size unchanged.

6203

Overflow in
converting data store
or log file size from
megabytes to bytes,
or in converting log
buffer size from
kilobytes to bytes

The attribute Size, MaxSize and LogFileSize are expressed in megabytes. Overflow occurred when converting them to bytes.

6206

Heap is full

This error indicates that the database's allocation structures are full. Try freeing any items possible and/or compacting the database. See "ttCkptBlocking" in Oracle TimesTen In-Memory Database Reference. Disconnecting all connections and reconnecting may also free up some space.

6212

MemoryLock
connection attribute
not supported on this
platform

The MemoryLock connection attribute is supported only on select platforms.

6213

Could not shmget the
user-defined segment

Could not shmget the user-defined segment For HP-UX only, the shmget system call failed for the user-defined shmkey.

6214

Could not start
user-defined segment

For HP-UX only, shmctl system call with IPC_STAT as the cmd parameter failed for the user-defined shmkey.

6215

User-defined segment
too small

For HP-UX only, the size of the user-defined shared memory segment is less than the size needed by the database.

6216

User-defined segment
attach count not zero

For HP-UX only, one or more processes are attached to the user-defined shared memory segment. The attach count must be 0.

This error is pushed following error 802 and indicates the partition in which memory has been exhausted.

6222

Permanent data
partition in use size
has exceeded
PermWarnThreshold

This warning is returned when a memory allocation in the permanent data partition causes the threshold to be exceeded, and memory threshold warnings have been enabled by the ttWarnOnLowMemory built-in procedure.

6223

Temporary data
partition in use size
has exceeded
TempWarnThreshold

This warning is returned when a memory allocation in the temporary data partition causes the threshold to be exceeded, and memory threshold warnings have been enabled by the ttWarnOnLowMemory built-in procedure.

If you enter more than one value for a First Connection attribute in the same connection string, or if you attempt to connect to a database with a different value than that given in the first connection to the database, TimesTen ignores the second value and returns this warning.

The value specified for the named connection attribute is invalid. Use the correct value, as indicated. The TYPEMODE connection attribute cannot be modified once a database has been created. To change the type mode of a database, you are required to destroy and recreate the database with a changed type mode.

Errors 7000 - 7999

Error number

Error or warning message

Details

7000

SQL statement exceed
the limit of limit
table references

The number of tables referenced in the SQL statement has exceeded the allowed maximum.

7001

User authentication
failed

Authentication using the user and password information supplied has failed. Check the user and password information and retry.

7002

No current user to
use as default
user_name

Cannot find current user name from the operating system.

7003

Value is not a valid
float

Floating-point values provided for FLOAT columns can only contain an optional sign (+ or -), followed by the digits 0-9 and an optional decimal point or exponential notation character between the digits.

7004

Value is not a valid
double

Floating-point values provided for DOUBLE PRECISION columns can only contain an optional sign (+ or -), followed by the digits 0-9 and an optional decimal point or exponential notation character between the digits.

7005

Procedure
procedure_name not
found

Attempted to call an ODBC procedure that does not exist.

7006

Bad argument supplied

Argument value is not valid. Check the description of the relevant procedure in the manual and retry.

7007

Required argument
omitted

In the call to the TimesTen built-in procedure, a required parameter was not being passed. See "Built-In Procedures" in Oracle TimesTen In-Memory Database Reference.

7008

Statement forbidden
for read-only
connections

This operation is not permitted on a read-only table.

7009

Too many parameters
for procedure
procedure_name

In the call to the TimesTen built-in procedure, more parameters were passed than was expected.

7011

Procedure
procedure_name failed

The procedure failed. Additional errors are returned indicating the reason for this failure.

7012

Illegal attempt to
update system table
table_name

Cannot destroy, insert into, delete from or update a system catalog table or index.

7013

Error while scanning
SQL statement: statement

On a Windows or Linux system, the scanner detected an error in the SQL statement. The text of the error found is included in the message. An "input buffer overflow" error text indicates that the length of a string literal has exceeded a platform-dependent internal buffer limit. Any other error text indicates an unexpected internal error condition.

7014

Fixed size of command
argument too large

The length of the input argument row descriptor has exceeded the maximum of 8,400. Command should use fewer (or shorter) arguments.

7015

System table cannot
be used in index creation

This error occurs when an attempt has been made to use the CREATE INDEX statement with system tables. The CREATE INDEX statement cannot be used with system tables.

7017

Unknown optimizer
flag flag_name

The name of the flag provided to the optimizer is invalid. See ttOptSetFlag for the complete list of flags.

7018

Creation of user
objects in system-user
schemas is not allowed

Cannot explicitly create a table with the owner SYS, which is used for TimesTen system tables.

7019

Index owner must
match table owner
owner_name

An attempt is made to create an index whose owner is different from that of its underlying table.

7020

Durable commits not
available with logging
to disk disabled

An attempt is made to perform a durable commit to a transaction log that is not writable.

Application used a keyword that is reserved by TimesTen. For a list of reserved words, see "Reserved Words" in the Oracle TimesTen In-Memory Database SQL Reference.

7026

Illegal attempt to
alter system table
'table_name'

Applications cannot modify TimesTen system tables. System tables are identified by the owner SYS or TTREP. 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

If possible, rewrite the expression to avoid warnings, so that the value can be inserted into the index successfully.

7028

Table names must
contain at least one
character

The name of a table must have a least one character. Rename the table and retry the operation.

7029

Index names must
contain at least one
character

The name of an index must have at least one character. Rename the index and retry the operation.

Application tried to disable multithreading support even though it had already turned multithreading support on.

7053

Cannot enable thread
support after it has
already been disabled

Application tried to enable multithreading support even though it had already turned multithreading support off.

Errors 8000 -8999

Error number

Error or warning message

Details

8000

No primary or unique index
on non-nullable column
found for replicated table
owner.table_name

To be replicated, a table must have a unique index over non-nullable columns.See "Table requirements and restrictions" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for details.

8001

Attempt to read invalid
LSN log record

The LSN provided does not exist.See "About XLA bookmarks" in the Oracle TimesTen In-Memory Database C Developer's Guide for information on bookmarks.

8002

Cannot drop replicated
table, index, or sequence

TimesTen Replication prevents tables, indexes, and sequences from being dropped when they are being used for replication.To drop such a table, index, or sequence, stop the replication agent, drop the replication scheme with the DROP REPLICATION statement. Then drop the table, index, or sequence.

8003

Update older than
TimeStamp of existing row

The timestamp of update is older than that of the row in the database. The update was rejected.

8004

Column
owner.table.column
cannot be used for
replication timestamp
checking if in an index or
added by ALTER TABLE; and
must be binary(8) with NULL
values allowed

The Timestamp column type must be BINARY(8) NULL, cannot be in the index and must be in the original unaltered table.

8005

Invalid update rule for
timestamp-based conflict
checking

Invalid flag value used by a replication stored procedure.

8006

Application must set
timestamp column with
'UPDATE BY USER'

The application has not set the timestamp column. The insert or update is rejected. Set timestamp or allow TimesTen to automatically set timestamp.

Unable to attach to the shared memory segment used to store the transaction log updates.

8011

Unable to re-configure
active XLA segment

The transaction log buffer size cannot be changed in an active transaction.

8012

Table with given ID not
found

Table with the user-specified ID does not exist in the database.

8013

Attempt to specify illegal
version

The version specified is not a valid TimesTen release version.

8016

No replication buffer
configured

The transaction log buffer has not been configured to store updates. See "Configuring the staging buffer" in the Oracle TimesTen In-Memory Database C Developer's Guide for information on configuring the staging buffer.

8017

Foreign table has number
columns while local table
has number columns

The tables being compared differ in the number of columns.

8018

Foreign table indexed on
different columns

The tables being compared have indexes on different sets of columns.

8019

Foreign and local table
differ on column type type

The tables being compared do not match on the column types.

8020

Inconsistent row in update
description

Bad row format in transaction log update.

8021

System table ID invalid

User specified system table ID does not exist.

8022

Operation not permitted on
non-shared data store

Operation permitted on shared database only.

8023

Table row does not have
expected value

The contents of the row do not match the expected values in the transaction log update.

8024

Illegal XLA record type

The XLA record is invalid or unsupported.

8025

Replication log threshold
limit reached at master.
The replication state for
this subscriber data store
is now set to FAILED. This
store is not in sync with
the master

The replication state for this database has been set to FAILED state by a replication peer. This happens when the amount of log that the peer is holding for the database exceeds a user configurable threshold. See "Setting the log failure threshold" and "Subscriber failures" in Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for further details.

8027

Network load of data store
not allowed because
connection was reset

Network error occurred while running a ttRepAdmin -duplicate operation. Check your network connections. Make sure that the remote replication agent is still running. If not, restart the replication agent.

8028

Network load of data store
timed out

Network timed out while running a ttRepAdmin -duplicate operation. Check your network connections. Make sure that the remote replication agent is still running. if not, restart the replication agent.

8029

Persistent transaction log
API bookmark already in use

Only one persistent transaction log API connection can use a persistent transaction log API bookmark. Close the connection using the bookmark or set up a new bookmark.

8031

Persistent transaction log
API log sequence number is
invalid

The transaction log API log sequence number is not a valid one. It is either not provided by the API or it is in the range already acknowledged by the connection.

8032

Stale post handle

The replication transmitter accessed a synchronization object, used for return service processing, that no longer applies to this particular service request. This is an internal condition that is externalized only as a part of the user error log warning "Attempt to awaken connection connection_id failed."

8033

Invalid post handle

The replication transmitter accessed a synchronization object, used for return service processing, that was no longer a valid synchronization object. This is an internal condition that is externalized only as a part of the user error log warning "Attempt to awaken connection connection_id failed."

8034

Record cannot be expressed
in SQL

This error is returned when an XLA record presented to ttXlaGenerateSQL does not translate into SQL.

8035

Persistent XLA requires
disk based logging

Logging to disk is required for persistent transaction logging API. See "XLA concepts" in the Oracle TimesTen In-Memory Database C Developer's Guide for more information.

8036

Parameter parameter
value not in valid range

The parameter is not in the valid range. Change the parameter.

8037

Table definition of record
differs from the table
definition in the data store

The table definition of the record at the time of its creation differs from the table definition of the record in the data s tore. Since the definitions do not match, the record cannot be interpreted by the database.

8038

Operation not permitted on
system table

You cannot perform the attempted operation on a SYS table. The operation is only permitted on a user-defined table.

8039

Attempt to drop
replication timestamp
column from table table_name

The timestamp column is used by TimesTen to resolve conflicts. This column cannot be dropped.

8040

No free slots in replCTNArr

Internal error. Contact TimesTen Technical Support.

8041

Invalid replCTNArr slot

Internal error. Contact TimesTen Technical Support.

8042

ReplCTNArr slot is not
allocated

Internal error. Contact TimesTen Technical Support.

8043

Materialized views cannot
be defined in a replication
scheme

An attempt was made to replicate a materialized view. Only detail tables can be replicated. See "Replicating materialized views" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for more information.

8044

To avoid data
inconsistency, copy the
data store from a
replication subscriber
using 'ttRepAdmin -
duplicate'. Use
ForceConnect=1 in the
connection string to
override this restriction

When RETURN RECEIPT replication is used with the TRANSMIT NONDURABLE option, a failed master database is allowed to recover only by restoring its state from a subscriber database using the -duplicate option of ttRepAdmin command. Use the ForceConnect attribute to override this restriction.

8046

The input old value row
does not match the data
store row

The old value row of the XLA update being applied does not match the value of the row in the database.

8047

Connection is currently
dedicated to XLA
exclusively

The connection is in use by XLA. No direct ODBC calls may be made on this connection until the XLA connection is closed.

8049

Commit ticket number will
wrap around

The commit ticket number for replication wraps around with this operation.

8050

The alter table operation
on a replicated table needs
to be in a transaction of its own

The ALTER TABLE statement for a replicated table must be in a transaction of its own and cannot be preceded or followed by any other SQL statement.

8051

The alter table operation
on a replicated table
cannot be in a two safe by
request transaction

Cannot use ALTER TABLE to alter replicated tables in a RETURN TWOSAFE BY REQUEST transaction. Rollback the transaction.

A temporary table was used in a replication scheme. Temporary tables cannot be used in a replication scheme.

8059

All DDLs on a replicated
table need to be in a
transaction of their own

This error is returned when DDL operations on a replicated table are not present exclusively in a transaction of their own.

8060

Cannot specify replication
timestamp column on a
cached table

The user is not allowed to configure timestamp-based conflict resolution for replication on cached tables.

8061

Operation not permitted
when the connection
attribute ForceConnect is
set to 1

The connection attribute ForceConnect must be set to 0 on any connections that attempt these replication operations.

8062

Local store not in ACTIVE state

The state of the local store is not in the ACTIVE state for a store that is part of an active standby replication scheme.

8063

Local store not completely
quiesced

This error is returned when an active store in an active standby replication scheme has pending updates that have not yet been replicated. Turn off local application updates and ensure that replication has sent all pending updates to the standby store to avoid this error.

8064

Table is already subscribed

A subscription attempt for the same table is being attempted twice.

8065

Table is not subscribed

The table is already unsubscribed from the XLA bookmark. There is no need to perform an unsubscribe operation.

8066

Canot alter subscription

The XLA bookmark must be closed before this operation can be performed.

8067

Inconsistency detected in
the COLUMN_HISTORY system
table

The contents of the system table, COLUMN_HISTORY seem to be corrupted.

8068

Cannot drop a table or
view that is subscribed by
an XLA bookmark.

The table must be unsubscribed from every XLA bookmark to avoid this error.

8069

Operation only supported
when the character set of
the data store in which the
record is generated matches
that of the connected store

The operation is only supported when the character set of the source and destination store match.

8070

The specified XLA bookmark
does not exist

The XLA bookmark does not exist. You can create a bookmark using the ttXlaBookmarkCreate built-in procedure.

8071

A replicated bookmark can
only be created on a store
with active standby pair
replication.

Enforcement of this restriction.

8072

Operation only permitted
on an ACTIVE store.

User attempted an XLA operation that is only permitted on a store when in the ACTIVE state.

8073

Failed to update XLA
bookmark :bookmark.

The replication agent on the standby store ran into a problem updating the XLA bookmark. The agent will keep trying until the condition that caused the error is alleviated. Standby updates to XLA bookmarks will fail every time this error is returned. Possible causes may be an unhealthy standby store or locks held on XLA tables on the standby store.

8074

Maximum number of
bookmarks exceeded.

User attempted to create more than the maximum number of replicated bookmarks per database.

8075

Error loading bookmark
list.

The replication agent ran into an error reading the set of replicated bookmarks from the database. Agent will keep trying until the condition that caused the error is alleviated. Possible causes may be an unhealthy standby store or locks held on XLA tables on the standby store.

8076

Bookmark reset due to
state change at store.

The state of the store was recently changed. All the bookmarks that were open at the time of the state change need to be reset since their state may be stale. The bookmarks are reset and users can use them to read XLA updates.

8077

Error moving bookmark on
the standby store.

The replication agent on the standby store ran into a problem updating the XLA bookmark. Agent will keep trying until the condition that caused the error is alleviated. Standby updates to XLA bookmarks will fail every time this error is returned. Possible causes may be an unhealthy standby store or locks held on XLA tables on the standby store.

8078

The deletion of replicated
XLA bookmarks is not
allowed while the
replication agent is
running.

Replicated bookmarks can only be removed when the local replication agent is not running.

8079

Cache group ownership
table cannot be defined in
a replication scheme.

An attempt was made to replicate a table used to store ownership table of a global cache group. Only cache group tables can be replicated.

8093

The local replication
agent needs to be running
for this operation

The local replication agent must be started.

8094

Mutiple concurrent
executions of this built-in
are not permitted

Only one execution of the built-in is allowed at any time. Once the previous call returns, a new call may be made.

8095

Truncate table not
permitted when
ttRepTransmitSet(0) has
been invoked on the connection

The replication agent attempted to truncate a table when replication has been disabled on this connection. To allow table truncation, invoke the built-in procedure ttRepTransmitSet with argument 1.

8096

Alter table not permitted
when ttRepTransmitSet(0)
has been invoked on the
connection

The replication agent attempted to alter a table when replication has been disabled on this connection. To alter a table, you must invoke the built-in procedure ttRepTransmitSet with argument 1.

8097

Error getting parent table
during autorefresh bookmark
lookup

This is a run-time error that indicates that a table that is part of an autorefreshed cache group is missing.

8098

This built-in is not
permitted in an active
standby pair scheme

The built-in procedure is not permitted in an active standby scheme.

8099

2-safe operation not
permitted with
AutoCommit = 1.

RETURN TWOSAFE transactions are not permitted when AutoCommit=1.

8100

Invalid parameter value
passed in

Check the validity of all parameters passed into the built-in procedure

8101

ELEMENT element_name
specified more than once,
being ALTER'ed or DROP'ed
with ADD, already exists,
or its owner (MASTER or
PROPAGATOR) is already the
owner for another ELEMENT
with the same data store object.

Element names must be unique within a replication scheme. Also, one store cannot be a MASTER or PROPAGATOR more than once for any elements with the same underlying database object. See "Defining replication elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8102

STORE store_name specified
more than once

A store can be specified at most once in a STORE clause of a CREATE REPLICATION or ALTER REPLICATION statement. See "Setting STORE attributes" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8103

attribute specified more
than once or already
defined for STORE store_name

A store attribute can be specified at most once in a STORE clause of a CREATE REPLICATION or ALTER REPLICATION statement. See "Setting STORE attributes" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

Cannot specify both
ELEMENT DATASTORE and
ELEMENT TABLE or SEQUENCE
since the former already
covers all objects in the
data store

When you specify ELEMENT DATASTORE, all tables are included in the statement. To only specify a particular table or sequence, remove the ELEMENT DATASTORE clause and use the ELEMENT TABLE or ELEMENT SEQUENCE clause. See "Defining replication elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8108

For TRANSMIT NONDURABLE,
must use the ELEMENT
element_name DATASTORE clause

No subscriber specified for the element in the replication scheme. A replicated element must always have at least one subscriber. Either remove the element from the scheme or specify a subscriber for the element.

8110

Connection not permitted.
This store requires Master
Catchup.

Master catchup is required for the database. New connections are disallowed until master catchup is complete.

8111

Connection not permitted.
Master Catchup in
progress.

Master catchup in progress. New connections not allowed until catchup is complete.

8112

Operation not permitted.
Master Catchup not
complete.

An update, insert, delete or alter to a replicated table is not permitted until master catchup is complete.

8113

Operation not permitted
since replication DDL was
performed in the
transaction.
Commit/rollback the
transaction.

Replication DDL should be in a transaction of its own. If an operation that is disallowed in the same transaction as replication DDL is attempted, this error is returned.

8114

Duplicate not permitted.
Reason reason. Duplicate
is only permitted from the
ACTIVE store to the STANDBY
store, from the STANDBY
store to a SUBSCRIBER, or
from the ACTIVE store to a
SUBSCRIBER if the STANDBY
store has failed.

It occurs when you are trying to perform a duplicate operation from a node in an active standby store to another and the source node is not in the correct state. The duplicate operation fails. Try duplicating from the correct store, or setting the state of the source store.

8118

Column column_name of
table owner.table_name
is longer than the maximum
column size of num bytes
when used with replication.

An attempt was made to create an active standby pair, but a replication scheme already exists.

8128

Store DSN is already in
the ACTIVE STANDBY PAIR scheme.

ALTER ACTIVE STANDBY PAIR attempts to add a database that is already in the active standby pair.

8129

Store DSN: The
"attribute_name"
attribute cannot be set for
DSN in an ACTIVE STANDBY
PAIR scheme.

Only the PORT and TIMEOUT attributes can be set for subscribers.

8130

CREATE ACTIVE STANDBY PAIR
must only be run on one of
the MASTER nodes.

The CREATE ACTIVE STANDBY PAIR statement must be run from one of the nodes on which a master database resides. For example, CREATE ACTIVE STANDBY PAIR rep1, rep2 SUBSCRIBER rep3 must be run from the node on which rep1 or rep2 resides.

8131

Table owner.name is
already part of the
replication scheme, or is
in the process of being
included

An attempt is made to add a table to a replication scheme, but the table is already part of the replication scheme or is already in the process of being added to the replication scheme.

8132

{INCLUDE|EXCLUDE}
element_name cannot be
used on TABLE element
element_name. The
operation is for DATASTORE
level elements only

An attempt was made to include or exclude a table-level element.

8133

You cannot
{include|exclude} table
owner.name because it is
part of a cache group. Use
{INCLUDE|EXCLUDE} CACHE
GROUP instead.

An attempt was made to include or exclude a cache group table.

8134

Store DSN is not a
MASTER for any element.

The ALTER ELEMENT statement did not find a matching element name in the database.

8135

Object_typeowner.name
is not part of DATASTORE
element element_name, or
is in the process of being
excluded

An attempt was made to exclude a table or sequence that is not in the replication scheme or that is already in the process of being excluded.

8136

All tables or cache groups
cannot be excluded from
element element_name.
Use DROP ELEMENT instead.

An attempt was made to exclude all tables or cache groups from an element. There must be at least one object in an element.

8137

Cannot exclude
object_type owner.name
because it is not in the
Active Standby scheme.

An attempt was made to exclude a table or sequence from the databases by using an ALTER ACTIVE STANDBY PAIR...EXCLUDE statement, but the table or sequence is not in the active standby pair.

8138

All tables or cache groups
cannot be excluded from the
ACTIVE STANDBY PAIR scheme

An attempt was made to exclude all tables and cache groups from the databases in an ALTER ACTIVE STANDBY PAIR...EXCLUDE statement.

8139

The specified peer store
is not in the standby state

An operation was attempted for a store that was not in a standby state. The operation is only permitted on stores that are in the standby state.

8140

Scheme does not exist or
inconsistency detected in
the local ACTIVE STANDBY
PAIR scheme

Error returned for an store with an inconsistent or corrupted active standby replication scheme.

8141

Local store not eligible
to be set to the active
state

Local database that is part of an active standby pair is not eligible to be set to the active state.

8142

Error checking on store
header attributes

An error occurred while reading the database header for attributes related to the active standby replication scheme.

8143

The standby can only be
duplicated from the active

A database that is in the standby state for an active standby pair can be duplicated only from the active database.

8144

Duplicate only allowed
from a standby store or
from an active when the
standby has failed

Subscriber databases in a active standby pair can be duplicated only from the standby database or from the active database when the standby database is in a failed state.

8145

The local store needs to
be in the active state for
this operation.

A database that is part of an active standby pair must be in the active state.

8146

There can be only one
INCLUDE or EXCLUDE clause
for object_type.

There can be only one INCLUDE or EXCLUDE clause for an object type (cache group or table). For example, the following is invalid: ALTER ACTIVE STANDBY PAIR INCLUDE TABLE t EXCLUDE table u.

8147

INCLUDE and EXCLUDE can
only be used on DATASTORE
level elements.

An attempt was made to use an INCLUDE or EXCLUDE clause with a table element definition in a CREATE TABLE or CREATE ACTIVE STANDBY PAIR statement.

8148

Host name exceeds limit of
num characters

The size exceeds the maximum permitted limit. The message indicates the maximum limit.

8149

Data store name exceeds
limit of max_num
characters

The size exceeds the maximum permitted limit. The message indicates the maximum limit.

8150

This change is not allowed
while the replication agent
for data store
data_store_name is
running. Stop the
replication agent to
perform this change.

Most replication scheme changes are not allowed while the replication agent is in the start state. For a list of supported scheme changes, see "Altering Replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8151

owner.name's replication
role disallows the
requested operation

Replication denies write access to a database object underlying a replication element for which it is a subscriber or propagator, provided that the local store is not the master for any other element with the same underlying database object.

8152

No ODBC type for column
owner.name.column

The type for a column in a replicated table could not be mapped to a known ODBC data type. See "Data Types" in the Oracle TimesTen In-Memory Database SQL Reference.

A replication element could not be found for the requested operation. This is a warning when the request is for an indefinite number of elements (* INstore_name). It is an error when the statement specifies one particular element.

8158

Failed to retrieve LSN
data for initializing PEER

A MASTER or PROPAGATOR store could not get its local LSN to initialize a (subscribing) peer store.

8159

No SUBSCRIBER PEER
information found for
REPLICATION owner.name
for MASTER or PROPAGATOR
store store_name

It is permissible for there to be no peers to delete for a DROP REPLICATION request. However, doing this evokes this warning.

8160

REPLICATION owner.name
not found

The local store does not know about the replication scheme specified in an ALTER REPLICATION or DROP REPLICATION request. (It is not registered in the TTREP.REPLICATIONS table.)

8161

No STORE store_name found
for REPLICATION
owner.name

Database was not found for the STORE specified in an ALTER REPLICATION ALTER STORE or DROP REPLICATION request.

8162

No subscriptions found for
ELEMENT element_name in
REPLICATION owner.name

No subscriptions could be found for an element in an ALTER REPLICATION DROP ELEMENT, ALTER REPLICATION ALTER ELEMENT DROP SUBSCRIPTION, ALTER REPLICATION ALTER ELEMENT SET OWNER or DROP REPLICATION request.

8163

Failed to retrieve table
or column descriptor for
table owner.name

While trying to create a replication element for CREATE REPLICATION or ALTER REPLICATION ADD ELEMENT, this information about the underlying table could not be retrieved.

8165

Replication schema is
inconsistent

Replication has noticed an inconsistency in its schema. This is an internal error. Contact TimesTen Technical Support

8166

Log not writeable or
transaction not initiated
by system

Replication DDL requests require that transaction logging be enabled for transaction rollback. This error is returned if logging is disabled.

8167

Cannot determine system
table attributes (e.g.
REPACCESS) for table from
replication role

Internal error. Contact TimesTen Technical Support.

8168

Cannot set system table
attributes (e.g. REPACCESS)
for table from
replication role

Internal error. Contact TimesTen Technical Support.

8169

Store transmitting_store
ON ransmitting_host
already transmits to store
receiving_store ON
receiving_host; at most
one path allowed from one
store to another

An attempt was made to configure a replication scheme with an element that has the same master or propagator and subscriber as an element in another replication scheme. Two such elements must reside in the same replication scheme. See "Defining replication elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8170

Receipt or commit
acknowledgement not
returned in the specified
timeout interval

A subscriber with RETURN RECEIPT or RETURN TWOSAFE service did not receive a commit acknowledgement within the current connection time limit. This can occur when the subscriber Replication Agent is not running or f the standby replication state is set to STOPPED. For an active standby pair, this can occur when the standby replication agent is not running and the standby has not been declared as "failed" on the active.

At attempt was made to specify as a replicated object one of the SYS.* or TTREP.* tables that the system creates and maintains. These tables cannot be replicated.

8172

The store store_name ON
host_name_1 is already
specified with an
equivalent host name as
store_name on host_name_2

Two different forms of host name were used to refer to one particular store in a replication scheme. The same form of host name must be consistently used to refer to any one database.

8173

Replication may not be
configured while XA
transactions are active

TimesTen Replication is not supported with XA transactions.

8174

attribute specified more
than once

You have specified more than one value for an attribute. Remove one of the instances of the attribute specification.

8175

Report file name
report_name cannot be resolved

An attempt to configure a conflict resolution report file to a non existent directory failed. Use a valid path to the report file

8176

Conflict checking
configuration conflict
between elements
element_name and
element_name with the
same underlying table

TimesTen cannot configure a partial database replication because a replication scheme already exists that covers the entire database. Use DROP REPLICATION to drop the existing replication scheme and CREATE REPLICATION to create a new replication scheme.

8177

Executing store
(store_name) not permitted
to operation_name

TimesTen cannot drop the replicating element because the specified replication scheme covers the entire database and the TRANSMIT NONDURABLE option is set. If needed, drop the replication scheme and use a CREATE REPLICATION statement to create a new replication scheme.

8178

Cannot set a subscriber to
state code code_number

TimesTen cannot specify the TRANSMIT NONDURABLE option for the replication scheme because the scheme does not cover the entire database. The NONDURABLE option must apply to the entire database. If needed, drop the replication scheme and use a CREATE REPLICATION statement to create a new replication scheme, using the ELEMENT DATASTORE clause with the TRANSMIT NONDURABLE option. See "Setting transmit durability on databease elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8179

Cannot create dupicate
store: store already exists

This error message indicates that the user is attempting to overwrite an existing database during an operation to duplicate databases.

When a DATASTORE element is used on a particular database for replication, no other element type can be used either in the same scheme or in any other scheme. See "Defining data store elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8181

Cannot create table or
alter replication because
data store
data_store_name is
covered by a full datastore
replication scheme

When a DATASTORE element for replication is present in a database no other new element type can be introduced. See "Defining data store elements" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8182

Cannot configure conflict
checking on DATASTORE element

To configure conflict resolution for replication DATASTORE elements cannot not be used. Replication must to be configured for each individual table. See "Resolving replication conflicts" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8183

Cannot alter element
because it is owned and
managed by the system

ALTER REPLICATION cannot be run on elements created as part of the DATASTORE element configuration. ALTER REPLICATION must be run on the DATASTORE element itself.

8184

Attempt to configure
replication_type
replication for a store
with no permanent objects

An attempt was made to configure database-level replication or active standby replication with an empty database.

8185

Attempt to exceed limit
for return receipt
receivers

Number of subscribers to receive RETURN RECEIPT replication updates exceeds the system specified limit.

8186

Replication agent not
responding to Return
Receipt transactions

The replication agent is not processing return receipt replication updates.

8187

A Return receipt
transaction has not been
executed on this connection

A transaction with return receipt replication updates has not been run on the connection.

8188

Transaction handle not valid

The handle for examining the status of a transaction with RETURN RECEIPT replication is not valid.

8189

Transaction token
subscriber information not
available

The replication subscriber cannot be found in the replication scheme.

8190

Host name host could not
be resolved

The host name specified cannot be resolved on this host. Check the host name for correctness or make changes to the network host name lookup.See "Configuring host IP addresses" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8191

This store store_name on
host_name not involved in
a replication scheme

The replication agent does not start if the database does not participate in any replication scheme. Either no replication scheme is defined on this store or the store is not part of any replication scheme.

If a replication scheme is defined, verify that the name of each database involved in replication matches the names specified in the DataStore attribute in their respective DSN definitions. This name may be different from the names specified for the Data Source Name attribute in the DSNs.

This error might also occur if the replication agent cannot determine that the current running host is involved in the specified replication scheme. Confirm that you have correctly identified your database hosts, as described in "Configuring host IP addresses" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8192

Dropping/adding a foreign
key that references a
replicated table is not
allowed while the
replication agent for data
store store_name is
running. Stop the
replication agent to
perform this operation

You cannot add or drop a foreign key in a table that references a replicated table. Stop the replication agents, add or drop the foreign key in the table that references the replicated table, and restart the replication agents. See "Starting and stopping the replication agents" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for details on how to stop and restart the replication agents.

8193

The TWOSAFE subscriber
attribute is only permitted
on a DATASTORE element.

Attempt to configure RETURN TWOSAFE with a table element. Change the ELEMENT type to DATASTORE or remove RETURN TWOSAFE from the replication scheme. For more information, see "Return twosafe replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8194

The TWOSAFE subscriber
attribute is not permitted
on a propagator element.

Attempt to configure RETURN TWOSAFE for a propagator database. The RETURN TWOSAFE service can't be used in a propagation scheme. See "Return twosafe replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for details.

Attempt to configure RETURN TWOSAFE in an invalid replication scheme. RETURN TWOSAFE can only be used in a bi-directional scheme between a master and a single subscriber database. See "Return twosafe replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for details.

8196

Remote application of the
transaction ran into error
: error_description.
Rollback the
transaction.

The RETURN TWOSAFE transaction ran into an error when it was applied on the subscriber. The transaction was not applied to the subscriber and must be rolled back on the master.

8197

Operation not permitted
once commit processing has begun

A commit call has already been issued for this RETURN TWOSAFE transaction. Therefore the operation is not permitted.

8198

A 2-safe transaction has
not been executed on this
connection

Attempt to get the replication status of a RETURN TWOSAFE transaction when none has been executed.

8199

A 2-safe or return receipt
transaction has not been
executed on this connection

The above is usually returned when attempting to get the replication status of a RETURN TWOSAFE or RETURN RECEIPT transaction when none has been executed.

8200

Attempt to drop all
columns in table

An application cannot drop all columns in a table. Consider using DROP TABLE to drop the table instead.

8201

Column is part of the
table's primary key

An application cannot drop a column that is part of a primary key. Consider dropping and recreating the table.

8202

Column is part of a
foreign key

An application cannot drop a column that is part of a foreign key. Consider dropping and recreating the table.

8203

Attempt to drop indexed
column

Application attempted to drop an indexed column in a table. Consider dropping the index and then dropping the column.

8204

Columns have been added to
table too many times

The operation is not permitted because the table would have more than the maximum number of partitions. As described in Oracle TimesTen In-Memory Database SQL Reference, the maximum number of partitions for a table cannot exceed 255. Consider rebuilding the table, either using INSERT SELECT or by using the ttBulkCp utility.

8206

Invalid parameter value
STANDBY passed in. The
command failed.

Indicates that an invalid input parameter has been passed in to an active standby pair.

8207

Illegal to replicate a
system sequence
(owner.sequence)

Objects owned by SYS and TTREP are system objects. Users cannot perform operations on these items, including involving them in a replication scheme. Remove the sequence from your replication scheme.

8210

Table reference of
table_name is ambiguous

More than one table with a matching foreign key constraint was found. Qualify all references to other tables with an owner name.

8211

Table table_name is not
a member of the cache group

No tables external to the cache group may be referenced by a foreign key constraint from within the cache group. See "Cache groups and cache tables" in the Oracle In-Memory Database Cache User's Guide.

8212

Multiple foreign keys
defined for table table_name

Foreign keys for a cache group table have been found to refer to more than one table. All foreign keys for a cache group table may only refer to a single table within the same cache group. See "Cache groups and cache tables" in the Oracle In-Memory Database Cache User's Guide.

Cache group tables may not be simultaneously marked as both READONLY and PROPAGATE. See "PROPAGATE cache table attributes" in the Oracle In-Memory Database Cache User's Guide.

8221

No parent table found

No table in the cache group was found to be a root table. Only one table in a cache group may have any foreign key constraints. All other tables in a cache group must refer to a single table within the same cache group.See "Cache groups and cache tables" in the Oracle In-Memory Database Cache User's Guide.

8222

Multiple parent tables found

Multiple potential root tables were found within the cache group. Only one table in a cache group may have foreign key constraints. All other tables in a cache group must refer to a single table within the same cache group.See "Cache groups and cache tables" in the Oracle In-Memory Database Cache User's Guide.

Incorrect value for the PassThrough attribute. Reset to a value between 0 and 5, as described in "Setting a passthrough level" in the Oracle In-Memory Database Cache User's Guide.

8234

PassThrough command is no
longer valid. One possible
cause is creation of a new
table on the TimesTen data store

After creating a table in TimesTen, including a cache group table, all prepared passthrough statements are invalidated, until reprepared. This error indicates that the application is trying to use an invalidated statement.The application must prepare the passthrough statement after creating a table or cache group.

8235

Number of WITH ID keys
values does not match the
primary key columns for
cache group cache_name

The number of values given in the WITH ID clause does not match the number of primary key columns defined on the root table of the cache group.

8236

Invalid commit value

A commit interval for a LOAD CACHE GROUP or MERGE statement on a cache group must be a positive integer value.

8237

Cache group WHERE clauses
must be less than number
bytes long

Each WHERE clause of a cache group may not exceed the maximum byte length specified in the error message.

This is a syntax error for the CREATE CACHE GROUP statement. You specified a PROPAGATE or NOT PROPAGATE clause on a cache table that already has been specified as either PROPAGATE or NOT PROPAGATE. Check the syntax and remove the redundant or contradictory PROPAGATE or NOT PROPAGATE clause.

8240

READONLY syntax can only
be used once in statement

This is a syntax error for the CREATE CACHE GROUP statement. You specified the READONLY keyword twice for the same cached table. Remove one of the instances of READONLY.

8242

Index on name column not
supported

You cannot create an index on column name because it is a system-created column.

8243

Invalid AUTOREFRESH
interval value

The specified AUTOREFRESH INTERVAL is invalid. It must be a positive integer.

8244

Cannot alter AUTOREFRESH
status of a cache group
which was not initially
created with AUTOREFRESH

For a cache group's AUTOREFRESH setting to be altered, it must be created with the AUTOREFRESH clause. For example, you cannot create a cache group without an AUTOREFRESH clause and later try to modify it to AUTOREFRESH STATE ON.

8247

The ttCGGenSQL built-in
procedure requires that the
cache group was initially
created with AUTOREFRESH

The ttCacheSqlGet built-in procedure cannot be called on a cache group that was created without an AUTOREFRESH clause

8248

Cache group
cache_group_name is not
currently being
autorefreshed

Either AUTOREFRESH state is off or AUTOREFRESH has been stopped because of a fatal error during refresh. Check user error log to find cause for refresh failure.

8249

Cache agent is shutting
down autorefresh for cache
group cache_group_name.
Please try again

When AUTOREFRESH is deactivated either by dropping the cache group or by altering the state to off, the TimesTen cache agent takes some time before the AUTOREFRESH is completely shutdown. An application may not be able to reactivate (create the same cache group or alter the state to ON/PAUSE) that cache group while it is being shut down. The application must wait for AUTOREFRESH to completely shut down before it can be reactivated.

8252

Table table_name is both
read only and not
propagated

The cache group table, table_name, cannot be specified as both READONLY and NOT PROPAGATE. This error can occur if you try to create a READONLY cache group that contains a table that is specified as NOT PROPAGATE.

8253

Table table_name cannot
have same name as an
existing cache group or the
cache group containing this
table

Cache groups and tables cannot have the same name. You see this error when you try to create a cache group or a table that has the same name as another table or cache group. To correct the error, use a different name in the CREATE CACHE GROUP/TABLE statement.

8254

Flush fails; all tables
are either propagated or
read only

This error occurs if you use FLUSH CACHEGROUP on a cache group where all of its tables are configured with PROPAGATE or READONLY and therefore not flushable. You can flush a table that is marked PROPAGATE by using the ttCachePropagateFlagSet built-in procedure.

8255

Attempt to
bi-directionally propagate
multiple copies of cache
group cache_group

You can create any number of cache groups that are bi-directionally propagated as long as the names of the cache groups are different and no bi-directionally propagated table appears in more than one cache group. IMDB Cache has this restriction to avoid update conflict anomalies. To correct the error, choose a different name for one of the cache group.In very rare instances, IMDB Cache falsely reports this error. The most likely cause is that there are some residual Oracle objects that were created by IMDB Cache but were not dropped when the cache group was dropped or the cache agent was shutdown. For more about the Oracle objects created by IMDB Cache, see "Oracle objects used to manage a cached environment" in the Oracle In-Memory Database Cache User's Guide.

8256

Illegal subquery used in
create cache group table
WHERE clause

Sub-queries are not allowed in the WHERE clause of the CREATE CACHE GROUP statement. To correct the error, remove the sub-query. For more information, see "Using a WHERE clause" in the Oracle In-Memory Database Cache User's Guide.

8257

Parameters are not
supported in Oracle WHERE
clauses

Parameter binding ("?") is not allowed in the WHERE clause of LOAD CACHE GROUP and MERGE statements. Use SQL literals instead. For more information, see "Using a WHERE clause" in the Oracle In-Memory Database Cache User's Guide.

8259

WHERE clause does not match

You must specify identical WHERE clauses in cache group definitions for replicating cache groups. You must: stop replication, delete the replication definitions, drop the cache groups, recreate the cache group definitions with the same WHERE clauses, recreate replication definitions and restart replication.

The root/child tables in one cache group aren't joined in the same manner as the root/child tables in that cache group's replicated counterpart.You must specify identical JOIN predicates in the cache group definitions for replicating cache groups. You must: stop replication, delete the replication definitions, drop the cache groups, recreate the cache group definitions, recreate replication definitions and restart replication.

Cache groups operations
may not be performed while
XA transactions are alive

There is an active XA transaction. No cache operations are allowed when there is an XA transaction accessing the database. These two TimesTen features cannot be used at the same time.

The XA and JTA APIs described in the TimesTen developer guides are not supported in cache groups. See "Summary of compatibility issues" in Oracle In-Memory Database Cache User's Guide.

8262

A READONLY or WRITETHROUGH
cache group can only
replicate to a cache group
of the same type

Attempted to replicate a readonly or writethrough cache group to a database with another type of cache group. When replicating between cache groups, only one cache group can be specified as AUTOREFRESH. In addition, the other cache groups must be marked READONLY.

Transaction
commit/rollback succeeded
on Oracle but failed on
TimesTen

Updates were successfully propagated to Oracle but failed on TimesTen. If a commit or rollback succeeds on Oracle but fails on TimesTen, the data in the TimesTen cache group may no longer be synchronized with the data in Oracle. After clearing up the cause of the TimesTen failure, it may be necessary to re-apply the failing transaction in TimesTen.

To use AUTOREFRESH, all of
the tables in the cache
group must be READONLY or
all the tables in the cache
group must be PROPAGATE

You cannot specify AUTOREFRESH with propagation disabled (NOT PROPAGATE). A cache group that is using AUTOREFRESH must be marked either PROPAGATE or READONLY. By default, cache tables are marked NOT PROPAGATE. If the cache group is not READONLY, you must explicitly mark each table either PROPAGATE or READONLY. This is to avoid overwriting changes during the next C operation.

Asynchronous or
Synchronous Writethrough
cache group cannot have a
WHERE clause

The CREATE SYNCHRONOUS WRITETHROUGH CACHE GROUP statement or the CREATE ASYNCHRONOUS WRITETHROUGH CACHE GROUP specifies a WHERE clause on at least one of its tables, which is not allowed. This is a compile time error message.

See "Cache group types" in the Oracle In-Memory Database Cache User's Guide for a description of asynchronous writethrough cache groups and synchronous writethrough cache groups.

8270

Table level READONLY/NOT
PROPAGATE/PROPAGATE flags
are not allowed in a System
Managed cache group

The table-level READONLY and PROPAGATE attributes cannot be used in system-managed cache groups. This is a compile time error.

At least one of the local
or remote cache groups must
set autorefresh STATE to
OFF or PAUSED

When replicating to a cache group, the AUTOREFRESH state of the cache group must be set to OFF.

8274

If a replicating cache
group has both AUTOREFRESH
and PROPAGATE then the
remote cache group must set
autorefresh STATE to OFF

When replicating from a user managed cache group that is specified as both AUTOREFRESH and PROPAGATE, to another cache group that is specified with AUTOREFRESH only, the second cache group must have the AUTOREFRESH STATE set to OFF. To enable replication, you must first set ALTER CACHE GROUP and set AUTOREFRESH STATE OFF on the cache group that currently has AUTOREFRESH on or paused.

Manual
LOAD/UNLOAD/REFRESH/FLUSH
operations are not allowed
on cache group
cache_group_name because
it uses AUTOREFRESH

The manual LOAD CACHE GROUP, UNLOAD CACHE GROUP or FLUSH CACHE GROUP statement failed because the cache group is specified with AUTOREFRESH. This is not allowed.

8277

If a cache group on the
receiver has AUTOREFRESH
specified then the
corresponding cache group
on the transmitter must
also specify AUTOREFRESH

When replicating to a subscriber cache group with AUTOREFRESH STATE OFF, the master cache group must specify the AUTOREFRESH attribute with either the STATE ON or OFF. See "Cache groups and replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8278

Cache groups with
AUTOREFRESH and PROPAGATE
can only be replicated if
both the transmitter and
receiver cache groups have
autorefresh STATE set to OFF

The subscriber cache group must have AUTOREFRESH STATE OFF. See "Cache groups and replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8279

If a transmitting cache
group has AUTOREFRESH and
the receiving cache group
has PROPAGATE then
transmitting cache group
must also have PROPAGATE

Attempt to replicate from a cache group with AUTOREFRESH specified but PROPAGATE not specified to a cache group with PROPAGATE specified. For details on how to replicate cache groups, "Replicating cache tables" in the Oracle In-Memory Database Cache User's Guide and "Cache groups and replication" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

8287

Manual LOAD/REFRESH
operations with WHERE or
WITHID clauses are not
allowed on cache group
cache_group_name because
it is specified as
AUTOREFRESH

Issued during a LOAD or REFRESH cache group operation on an autorefresh cache group. A LOAD or REFRESH operation cannot have a WHERE clause or WITH ID clause for an autorefresh cache group.

8288

Manual LOAD of cache group
cache_group_name is not
allowed because it is
specified as AUTOREFRESH
and it is not empty

This error is issued during a LOAD CACHE GROUP operation on an AUTOREFRESH cache group. A LOAD CACHE GROUP operation cannot be performed on a non-empty AUTOREFRESH cache group. REFRESH cache group can be used instead.

8289

Manual LOAD/REFRESH of
cache group requires
AUTOREFRESH STATE to be
PAUSED, but the STATE of
cache_group_name is
state. The LOAD is not
allowed.

This error is issued during a LOAD or REFRESH CACHE GROUP operation on an AUTOREFRESH cache group. AUTOREFRESH STATE must be PAUSED when issuing LOAD or REFRESH cache group statements.

8290

Manual LOAD/REFRESH must
have COMMIT EVERY N ROWS clause

This error is issued during a LOAD or REFRESH CACHE GROUP operation. To solve this problem, specify a COMMIT EVERY N ROWS clause in the statement.

8291

Manual LOAD/REFRESH WITH
ID statement cannot have
the COMMIT EVERY N ROWS clause

This error is issued during a LOAD or REFRESH CACHE GROUP operation. A COMMIT EVERY N ROWS clause cannot be specified when a WHERE or WITH ID clause is used.

8292

The cache group where
clause contains a subquery.
Changes of the subquery
result may not be tracked
by INCREMENTAL AUTOREFRESH

An autorefresh cache group has a subquery in the WHERE clause. Incremental AUTOREFRESH does not track any changes of the subquery result list. Accordingly, IMDB Cache may not cache the result rows as specified by the cache group WHERE clause.

8293

Autorefresh interval
should be at least num
milliseconds

The AUTOREFRESH interval should be at least num milliseconds. Currently the minimum number of milliseconds allowed for the AUTOREFRESH interval is 10.

8294

Replication not allowed
from a non-cache group
table to a READONLY cache
group table

You cannot replicate from a non-cache table to a table in a READONLY cache group.

8295

To use NCHAR/NVARCHAR
values through Cache
Connect, Oracle Database
national character set must
be AL16UTF16

To use NCHAR/NVARCHAR2 types in a a cache group table column or a passthrough statement, the Oracle database national character set must be AL16UTF16.

You can use SQL*Plus to connect to the Oracle database and issue the following query to check the database national character set:

TimesTen and Oracle
database character sets do
not match. TimesTen:
database_character_set,
Oracle: database_character_set

TimesTen databases that use cache groups or provide passthrough must have the same database character set as the Oracle database. The DatabaseCharacterSet of the database cannot be changed after creation.

8297

The session parameter
parameter cannot be
altered through a
PassThrough statement

TimesTen does not support passthrough execution of the indicated parameter in a SQL ALTER SESSION SET statement.

8298

Table in autorefresh cache
group cannot have more than
num columns

The maximum number of columns in an autorefresh cache group table is 999. Generally TimesTen supports tables that contain up to 1000 columns.

8299

Cache Connect database
character set cannot be
TimesTen8

The TIMESTEN8 database character set cannot be specified for databases that are used with cache groups.

8302

Autorefresh state of cahe
group cache_group_name is
off

The AUTOREFRESH state for the cache group is OFF. To perform AUTOREFRESH operations, set the state to ON.

8303

Sequence number must be
non-negative and end
sequence must be greater
than or equal to start
sequence

A sequence number must be positive and must be greater than or equal to the first number in the sequence.

8304

Manual REFRESH operation
with WHERE clause is not
allowed on cache group
cahegroup_name because it
is specified as dynamic
AUTOREFRESH

Refresh operations are automated on the dynamic autorefresh cache group. You have attempted to perform a manual refresh operation. It is not supported.

Manual load or refresh of a dynamic cache group failed because of the failure in updating the internal dynamic counter. This could be because of another operation holding a lock on the row for this cache group in the SYS.CACHE_GROUP table.

8306

A cache group cannot be
created as dynamic if it is
defined as both autorefresh
and propagate

A dynamic user managed cache group cannot use both the autorefresh cache group attribute and the PROPAGATE cache table attribute.

8307

Autorefresh interval
cannot exceed 99 days

Create the cache group with an AUTOREFRESH interval less than or equal to 99 days.

8308

All replicated autorefresh
cache groups should have
autorefresh state PAUSED
before calling ttRepDeactivate.

This error can occur when a user calls the built-in ttRepDeactivate. The error is triggered when there are some replicated autorefresh cache groups where state is ON and the cache agent is running.

Alter the replicated autorefresh cache groups on the active node (to be deactivated) to the PAUSED state.

8309

Manual REFRESH with
PARALLEL clause is not
allowed for dynamic
readonly cache groups.

Refresh cache group statement was allowed to have parallel clause for refreshing a dynamic read only cache group. It is disabled in this release.

8400

System catalog creation
failed: failure_message

When a TimesTen database is created, a number of predefined tables and views are defined in the new database. An error occurred in the process of defining these objects. Review the included message, make suggested corrections and attempt database creation again.

8500

PL/SQL feature not
installed in this TimesTen
instance

You have attempted to use a PL/SQL feature, but PL/SQL was not enabled for TimesTen at install time. PL/SQL features not supported unless PL/SQL was enabled for the TimesTen instance. To use PL/SQL, it is necessary to re-install TimesTen and enable PL/SQL at install time.

8501

PL/SQL feature not
installed in this TimesTen
database

You have attempted to use a PL/SQL feature, but PL/SQL was not enabled for TimesTen at install time. PL/SQL features not supported unless PL/SQL was enabled for the TimesTen instance. To use PL/SQL, it is necessary to re-install TimesTen and enable PL/SQL at install time.

8502

Error Error_number
initializing PLSQL_MEMORY
string

Internal error. Contact TimesTen Technical Support.

8503

Error_text

An error occurred while the PL/SQL compiler was compiling an anonymous block. The text of the error message references an ORA error number from the Oracle error documentation. In general, diagnosis is the same for PL/SQL in TimesTen and for PL/SQL in Oracle, though there are known differences between PL/SQL in these two environments.

8504

PL/SQL object_typeobject created
with compilation warnings

This is a warning. A PL/SQL block specified in a CREATE or REPLACE procedure, function or package statement cannot be compiled due to a syntax problem or other problem.

8505

PL/SQL object_typeobject created with
compilation errors

This is an error. A PL/SQL block specified in a CREATE or REPLACE procedure, function or package statement cannot be compiled due to a syntax problem or other problems.

8506

error_text

You have received this error for one of the following reasons:

An attempted operation, such as COMMIT, ROLLBACK, or other DDL statement, cannot proceed because of a conflict with an existing PL/SQL object.

An unexpected error occurred while attempting to manage memory or locks in the PLSQL_memory area.

8507

error_text

An error occurred while a PL/SQL subprogram is executing or while invoking the PL/SQL compiler. The text of the error message references an ORA error number from the Oracle error documentation. In general, diagnosis is the same for PL/SQL in TimesTen and for PL/SQL in Oracle, though there are known differences between PL/SQL in these two environments.

8508

Question mark parameter
markers are not allowed in
PL/SQL blocks

You provided a question mark parameter in a PL/SQL block. Parameter marker names beginning with _QMARK_ are reserved for system use. This is not supported.

This error generally signifies either that an attempted operation (such as commit, rollback, or some DDL statement) cannot proceed because of a conflict with an existing PL/SQL object or because some unexpected error occurred while attempting to manage memory or locks in the PLSQL_memory area.

8509

PL/SQL execution
terminated; PLSQL_TIMEOUT
exceeded

A PL/SQL block executed for longer than the value specified for the PLSQL_TIMEOUT attribute.

8510

Error loading PL/SQL
system package file
file_name:
error_message

When a TimesTen database is created, a number of predefined PL/SQL packages are defined in the new database. Any error encountered during this process is returned in this message.

8511

PL/SQL can only be enabled
during database creation or
at first connect

You attempted to enable PL/SQL on an existing database. You can only enable PL/SQL at the time that you create a database.

8512

PL/SQL is not supported
with exclusive mode data
store access

PL/SQL is not supported with databases that are created with exclusive access. Exclusive access is a deprecated feature.

8513

PL/SQL is not supported in
non-thread-safe mode

PL/SQL is not supported with databases that are created without thread safety. Non thread-safe mode is a deprecated feature.

8514

Invalid PL/SQL compiler
parameter parameter_name

Only persistent parameters are allowed. The PL/SQL persistent parameters are PLSQL_OPTIMIZE_LEVEL, PLSQL_CODE_TYPE, PLSQL_DEBUG, PLSQL_WARNINGS, PLSQL_CCFLAGS and NLS_LENGTH_SEMANTICS. You supplied a parameter other than one of these.

8515

Duplicate setting for
PL/SQL compiler parameter
parameter_name

You can specify each parameter only once in each statement. See the Oracle Database documentation for complete compiler parameters clause information.

8516

PL/SQL is not supported
with logging turned off

You must log transactions to use PL/SQL. Set the Logging attribute to 1 for this database.

8517

Cannot attach PL/SQL
shared memory;
PLSQL_MEMORY_ADDRESS
not valid or already in use

The virtual memory address specified by PLSQL_MEMORY_ADDRESS is in use. Specify a virtual address that is free in all processes that can connect to the database.

8518

The preceding error
occurred during the
execuation of an internal
SQL statement

Warning message:

8519

Invalid
PLSQL_MEMORY_ADDRESS specified

An illegal value (for example, 0) was specified for PLSQL_MEMORY_ADDRESS.

8520

PL/SQL library mismatch.
Corrupted TimesTen
installation.

Your TimesTen installation is corrupted. Some files are from a PL/SQL-enabled version of TimesTen. Others are from a non-PL/SQL-enabled version. Re-install TimesTen with PL/SQL enabled.

Your application has connected to two different TimesTen databases that use the same PLSQL_MEMORY_ADDRESS value. Specify a different PLSQL_MEMORY_ADDRESS value for one of the databases.See PLSQL_MEMORY_ADDRESS for details.

8522

PLSQL_MEMORY_SIZE too small.

See PLSQL_MEMORY_SIZE for the appropriate memory size for your operating system.

8523

No data found.

No rows were found when the user executed a SELECT statement inside PL/SQL.

Errors 9000 -9999

Error number

Error warning message

Details

9990

Unkown error from TimesTen
daemon

An internal error occurred in the TimesTen subdaemon during a connection attempt. Contact TimesTen Technical Support

9991

Invalidation of data store
in progress

An application attempted to connect to a database while it was being invalidated. Wait and retry the operation.

9992

Daemon reports error
error_details

The TimesTen daemon encountered a problem when executing an administrative request, such as starting or stopping the cache agent or the replication agent. The details are contained in the error message.

9993

Final checkpoint of data
store from RAM onto disk in
progress

Unloading the database from RAM or in the middle of final checkpoint. The amount of time this takes depends on the number of changed pages in the database.

9994

Loading data store from
disk into RAM in progress

Loading the database from disk into RAM. The amount of time this takes depends on the size of the database and the number of inserts, updates and/or view creations that have occurred since the last checkpoint.

9995

Process recovery in
progress: rolling back
transaction of failed process

Process recovery running on this database. Rolling back transactions. The amount of time this takes depends on the number of inserts, updates and/or view creations caused by the failing transaction.

9996

Process recovery in
progress: examing health of
in-RAM data store

Process recovery running on this database. Checking the state of the database. This can take anywhere from several seconds to 15 minutes, depending on the precise state of the database when the application failed or terminated. In general, you can expect it to take between 5-6 minutes to recover a database.

9998

Cannot perform requested
operation because TimesTen
service is being quiesced

An attempt was made to connect to or destroy a database while the TimesTen daemon was shutting down. Wait for the TimesTen daemon to start again.

9999

Subdaemon exited unexpectedly

An internal error occurred in the TimesTen subdaemon during a connection attempt. Contact TimesTen Technical Support.

Errors 10000 - 10999

Error number

Error or warning message

Details

10001

Only temporary data stores
with diskless or no logging
allowed in diskless mode

The daemon is running in diskless mode, and an attempt was made to connect to a permanent database, or a database with Logging enabled and not diskless. To prevent this error from happening, only connect to a temporary database or a diskless database with Logging disabled.

10002

No record of a data store
located in 'location'

Warning: When creating a database, the daemon found files whose names look like names of checkpoint or transaction log files for the database.Since it is a new database, the TimesTen daemon renames the files so they have a tilde (~) at the end. This can happen if checkpoint files get moved manually instead of using the proper utilities, or if database files from a previous version of TimesTen exist where the TimesTen daemon is attempting to put the new files.

10003

Unexpected data store file
exists for new data store:
description.

When connecting to a database, checkpoint and/or transaction log files exist which are incompatible or should not exist. The description field gives more information.You can destroy the existing database and replace it with a new one by specifying Overwrite=1 in your connect string. For example:

ttisql -connStr "dsn=myDSN; overwrite=1"

10004

Unable to connect to
daemon: error_details

When a process is initiating communication with the TimesTen daemon, a communication protocol error has occurred. This is most likely due to some process other than a TimesTen daemon running on the TimesTen daemon port. Use ttStatus to check whether the TimesTen daemon is running, and on which port.

10006

Busy with another policy request

An attempt to make a request, such as changing the RAM policy, starting the replication agent, or holding a database in RAM, has timed out because some other related policy request is running.

10007

Could not wait for not-in-flux

Internal error. Contact TimesTen Technical Support.

10008

Data store was deleted
while daemon was waiting for
completion of changing the
state of the database

While processing an attempt to make a request such as changing the RAM policy, starting the replication agent, or loading a database into RAM, the database has been deleted.

10009

RAM load ignored due to
ramPolicy setting

A process has attempted to load a database into RAM, but the RAM policy for the database is not "manual." Use ttAdmin-ramPolicy to change the RAM policy to "manual" before attempting a RAM load or unload.

10010

RAM unload ignored due to
ramPolicy setting

A process has attempted to unload a database into RAM, but the RAM policy for the database is not "manual." Use ttAdmin-ramPolicy to change the RAM policy to "manual" before attempting a RAM load or unload.

10011

Data store is currently not
being managed

A process has attempted to unload a database from RAM, but there is no TimesTen subdaemon currently managing the database.

10012

Replication Agent was not
started due to repPolicy
setting

An attempt has been made to start a replication agent for a database, but the replication policy for the database is "always," which means the TimesTen daemon automatically starts or restarts the replication agent. Use ttAdmin -repPolicy to change the replication policy to "manual" to manually control whether the replication agent is active. See "Starting and stopping the replication agents" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for details.

10013

Could not start Replication
Agent for the requested data
store

A replication agent failed during its initialization. More information is available in the user error log.

10014

Could not spawn Replication
Agent for the requested data
store. Refer to user
error log for further
information

The TimesTen daemon could not spawn a replication agent. Make sure you are not out of memory or process table space.

10015

Could not stop Replication
Agent for the requested data
store. Refer to user
error log for further information

An attempt to stop the replication agent failed. Make sure the database still exists and the replication agent is still running.

10016

Replication Agent was not
stopped due to repPolicy
setting

An attempt has been made to stop a replication agent for a database, but the replication policy is set to "always." See "Starting and stopping the replication agents" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for information on setting the replication policy.

10017

OracleNetServiceName not set

An attempt was made to start the cache agent for a database, but the OracleNetServiceName connection string value was not set. Make sure OracleNetServiceName attribute is correctly defined in the DSN

10018

ORACLE_HOME not set

An attempt was made to start the cache agent for a database, but ORACLE_HOME was not set in the user environment. Make sure the ORACLE_HOME environment variable is set properly, as described in "Environment variables" in the Oracle TimesTen In-Memory Database Installation Guide.

10019

ORACLE_HOME path too long

The value of the ORACLE_HOME environment variable is too long. Make sure it is set correctly, and use symbolic links if necessary. See "Environment variables" in the Oracle TimesTen In-Memory Database Installation Guide.

10020

Could not stop cache agent
for the requested data
store. Refer to user
error log for further
information

An attempt to stop the cache agent failed. Use ttStatus to make sure the database still exists and the cache agent is still running.

10021

Cache agent was not stopped
due to cache agent policy setting

An attempt has been made to stop an Cache Agent for a database, but the Cache Agent policy for the database is "always," which means the TimesTen daemon automatically starts or restarts the Cache Agent. Use ttAdmin-oraAgentPolicy to change the Cache Agent policy to "manual" to manually control whether the Cache Agent is active. See "Setting a cache agent start policy" in the Oracle In-Memory Database Cache User's Guide for details.

10022

Failed to set ORACLE_HOME

The TimesTen daemon was unable to set the ORACLE_HOME environment variable. Make sure you are not out of memory. See "Environment variables" in the Oracle TimesTen In-Memory Database Installation Guide for information on setting ORACLE_HOME.

10023

Failed to set LD_LIBRARY_PATH

The TimesTen daemon was unable to set the LD_LIBRARY_PATH environment variable. Make sure you are not out of memory. See "Shared library path environment variable" in the Oracle TimesTen In-Memory Database Installation Guide for information on setting LD_LIBRARY_PATH.

10024

Could not start Cache Agent
for the requested data store

A Cache Agent failed during its initialization. More information is available in the user error log.

10025

Could not spawn Cache Agent
for the requested data store

The TimesTen daemon could not spawn an Cache Agent. Make sure you are not out of memory or process table space.

10026

Some cache groups that hold
triggers and other objects
in Oracle may exist in the
data store, drop all the
cache groups before
destroying the data store

A ttDestroy operation may not destroy the database if it contains cache groups that hold triggers and other objects on the Oracle database. Drop the cache groups and attempt the destroy operation again.

10028

Attempted stop of TimesTen
daemon while being managed
by Clusterware

If a TimesTen installation is managed by Oracle Clusterware and the user attempts to gracefully stop the daemon directly using ttDaemonAdmin -stop, the daemon refuses to stop.

The user can only stop the daemon if the Cluster agent and the daemon monitor are first stopped with ttCWAdmin -shutdown -hosts localhost.

Use of SQLTransact to commit an XA transaction is not allowed. XA transactions may only be committed through the use of xa_commit.See "Distributed Transaction Processing XA" in the Oracle TimesTen In-Memory Database C Developer's Guide.

11033

XA support requires that
logging to disk be enabled

XA support requires that the Logging connection attribute be set to 1.

11035

In-doubt transactions
awaiting resolution in
recovery must be resolved first

Due to recovery of in-doubt transactions, normal operation of the database has been suspended. Normal operation resumes once the in-doubt transactions have been resolved by the transaction manager.

11036

XA transactions may not be
started while replication is
configured

TimesTen Replication is not supported with XA transactions.

11037

XA transactions may not be
started while the cache agent
is running

IMDB Cache is not supported with XA transactions.

11038

XA transaction cannot be
constructed because record
record_number not found

A transaction log record needed to recover an XA transaction could not be found in the existing transaction log files. Contact TimesTen Technical Support.

11039

XA reconstruct of xcb
record failed

Recovery of an XA transaction failed due to an Internal error. Contact TimesTen Technical Support.

11040

DDL statementes are not
allowed in XA transactions
when DDLCommitBehavior is set to 0

UNIX only. TimesTen could not open either the user or system ODBC.INI file.

12004

Syntax error in odbc.ini file

UNIX only. TimesTen encountered a syntax error while parsing the user or system ODBC.INI file.

12005

Environment variable
specified in the attribute is
not set

UNIX only. In either the user or system ODBC.INI file, you have specified an attribute of the DSN with an environment variable that has not been set.

12006

Invalid attribute name

The specified DSN attribute name is NULL, an empty string or not a valid attribute for a TimesTen data manager DSN. This error is also returned if the user or system ODBC.INI file contains an invalid attribute_name=value pair.

12007

The value of the attribute
in the ini file is empty. It
should not be empty

UNIX only. TimesTen DSN attributes are defined in the user or system ODBC.INI file using a attribute_name=value pair. The value specified is either an empty string or white space.

12008

The length of the
value-string in the ini file
is too long for this
attribute

UNIX only. TimesTen DSN attributes are defined in the user or system ODBC.INI file using a attribute_name=value pair. The length of the value specified exceeds the maximum length allowed for the attribute.

12009

Specified DSN is not found
in user and system odbc.ini
files (or registry)

On Windows, the DSN has not been defined as a user or system DSN using the ODBC Data Source Administrator. On UNIX, the DSN is not defined as a user or system DSN in a ODBC.INI file.

12010

Specified buffer is NULL or
of 0-length

The buffer specified for returning a value is either NULL or the length of the buffer is 0.

12011

Specified buffer length is
not big enough to hold the
value for this attribute.
Value truncated.

The specified buffer length is less than the length of the requested DSN attribute value. TimesTen returns a truncated value.

12012

malloc() failed

Unable to allocate memory for TimesTen internal data structures.

12013

Specified data store name is
NULL or of zero length, or a
client DSN was used

The specified database name is either NULL or an empty string. You must specify a valid database name.

12014

Internal error in TimesTen
utility library. Could not
get current context

Internal error. Contact TimesTen Technical Support.

12015

Internal error in TimesTen
utility library. Could not
set current context

Internal error. Contact TimesTen Technical Support.

12016

The number of seconds must
be > 0

The number of seconds for the RAM Grace Period must be greater than 0 seconds.

12017

Failed to allocate
environment handle

A call to the ODBC SQLAllocEnv function failed.

12018

Failed to allocate
connection handle

A call to the ODBC SQLAllocConnect function failed.

12019

Failed to locate data store files

TimesTen cannot determine the path and names of the database files for the specified database.

12020

Failed to connect to data store

A call to the ODBC SQLDriverConnect function failed to connect to the database using the specified connection string.

12021

Failed to disconnect from
data store

A call to the ODBC SQLDisconnect function failed.

12022

Failed to free connection handle

A call to the ODBC SQLFreeConnect function failed.

12023

Failed to free environment handle

A call to the ODBC SQLFreeEnv function failed.

12024

Data store already loaded
into RAM and being managed

A request to load a database into RAM failed because the database has already been loaded into RAM.

12025

Data store already manually
unloaded from RAM

A request to unload a database from RAM failed because the database has already been unloaded from RAM.

12026

The agent is already running
for the data store

The specified agent has already been started by the TimesTen daemon.

12027

The agent is already stopped
for the data store

The specified agent has already been stopped by the TimesTen daemon.

12028

No record of a data store in
the location specified by the
DataStore attribute of the
DSN. Specified DSN may be a
temporary data store

The database does not exist in the location specified by the DataStore attribute of the DSN.

12030

Data store is in use

The TimesTen daemon cannot perform the requested operation because another application is connected to the database.

12032

Invalid RamPolicy specified

The valid RAM Policy values are:

TT_RAMPOL_MANUAL

TT_RAMPOL_ALWAYS

TT_RAMPOL_INUSE

12034

RamPolicy cannot be set for
temporary data stores

RAM Policy can only be set for permanent databases.

12035

Could not initialize winsock

Windows only. A call to WSAStartup failed.

12036

No winsock.dll (that
supports version 1.1.) found

Windows only. A call to WSAStartup could not locate a winsock.dll that supports version 1.1.

12037

Could not terminate winsock

Windows only. A call to WSACleanup failed.

12038

Could not connect to
TimesTen daemon on remote
host host_name

Make sure that the TimesTen daemon is running on the remote host.

12039

Could not get port number of
TimesTen replication agent on
remote host. The replication
agent may have either not
been started or may have just
been started and have not had
time to communicate its port
number to the TimesTen daemon

Make sure that the TimesTen replication agent for the specified database is running on the remote host.

12040

Could not connect to
TimesTen replication agent on
remote host

Internal error. Contact TimesTen Technical Support.

12041

Host not found

TimesTen failed to determine the IP addresses associated with the specified host name in the system's /etc/hosts file.Verify that you have correctly identified the host name, as described in "Configuring host IP addresses" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide.

The type of response received from the remote TimesTen replication agent does not match the expected response type.

12048

Error performing backup at source

This error can occur during a ttRepDuplicateEx operation when the backup operation on the source database fails. See the verbose user error log on the source database for additional diagnostic information.

12049

Cannot write to temporary file

Internal error. Contact TimesTen Technical Support.

12050

Transaction commit for the
swap operation failed

Internal error. Contact TimesTen Technical Support.

12052

Replication scheme name too long

Maximum length is 30 characters.

12053

Replication scheme owner too long

Maximum length is 30 characters.

12054

Internal Error: Cannot
determine userid

Internal error. Contact TimesTen Technical Support.

12055

No changes needed to upgrade
the replication schema

During upgrade, if the replication schema version of the old database is same as the current installation, no upgrade is required.

12056

Size values of local store
must match that of the remote store

The PermSize, TempSize and LogBuffSize attributes of the local database do not match those of the remote database.

12057

Error creating temporary
data store

Failed to create a local database.

12058

Failed to read replication
backup CTN

Failed to read replication backup Commit Ticket Number.

12059

Deadlock/Timeout

Either the operation caused a deadlock or the operation timed out.

12060

Invalid remote host specified

A call to gethostbyname with the specified remote host name failed.

12061

Invalid local host specified

A call to gethostbyname with the specified local host name failed.

12062

Failed to upgrade from
unsupported version

Upgrade from this previous replication schema version is not supported.

Replication tables are from
an earlier version. Consider
using 'ttRepAdmin -self
-upgrade' to upgrade

The specified operation is not allowed on replication schemes for older versions of TimesTen.

12076

Replication schema is later
than TimesTen utility library

The specified operation is not allowed on replication schemes for new versions of TimesTen.

12077

Hostname is not set on this machine

Internal error. Contact TimesTen Technical Support.

12078

Failed to rest is_local_store

Internal error. Contact TimesTen Technical Support.

12079

Failed to set is_local_store

Internal error. Contact TimesTen Technical Support.

12080

No receiver found to swap with

Internal error. Contact TimesTen Technical Support.

12081

Unsupported column type in upgrade

Internal error. Contact TimesTen Technical Support.

12082

Failed to reset receiver CTN

TimesTen failed to reset receiver Commit Ticket Number.

12083

Found no source store ID in
TTREP.REPLICATIONS

Internal error. Contact TimesTen Technical Support.

12084

Call to gethostname() failed

Internal error. Contact TimesTen Technical Support.

12085

No table found for table id

Internal error. Contact TimesTen Technical Support.

12086

Cannot get information on table

Internal error. Contact TimesTen Technical Support.

12087

Cannot get format of table

Internal error. Contact TimesTen Technical Support.

12088

Multiple definitions of
source store id

Internal error. Contact TimesTen Technical Support.

12089

Cannot get column
information of table

Internal error. Contact TimesTen Technical Support.

12090

Cannot get type mapping for column

Internal error. Contact TimesTen Technical Support.

12091

Cannot determine if version
2 replication tables exist

Internal error. Contact TimesTen Technical Support.

12092

Replication schema is not
empty; cannot upgrade

Replication schema must be empty for the upgrade operation.

12093

No count information
returned from upgrade's scan
of TTREP.TABLES

Internal error. Contact TimesTen Technical Support.

12094

Cannot get count information
from TTREP.TABLES

Internal error. Contact TimesTen Technical Support.

12095

Cannot update object id

Internal error. Contact TimesTen Technical Support.

12096

Cannot set object id

Internal error. Contact TimesTen Technical Support.

12097

Cannot get column values
from TTREP.PEER

Internal error. Contact TimesTen Technical Support.

12098

Failed to determine correct
write LSN for
TTREP.REPPEERS.SENDLSN

Internal error. Contact TimesTen Technical Support.

12099

Multiple schemes found. Must
specify -scheme to identify
which replication scheme to use

Multiple replication schemes found.

12100

Cannot create replication
table definition

Internal error. Contact TimesTen Technical Support.

12101

Cannot start transaction to
check replication schema version

Internal error. Contact TimesTen Technical Support.

12102

Failed to commit transaction
for checking replication
schema version

Internal error. Contact TimesTen Technical Support.

12103

Cannot get column value from
TTREP.REPELEMENTS table

Internal error. Contact TimesTen Technical Support.

12104

Cannot find write LSN

Internal error. Contact TimesTen Technical Support.

12105

Failed to update LSN

Internal error. Contact TimesTen Technical Support.

12106

Cannot set new replication
hold LSN

Internal error. Contact TimesTen Technical Support.

12107

Deleting table definition
info failed

Internal error. Contact TimesTen Technical Support.

12108

Invalid policy
'invalid_policy' specified.
Must be valid_policy_list

The policy value supplied to the built-in procedure must be of the values in the valid_policy_list. Refer to the documentation on each specific built-in procedure for a description of its valid policy values. See "Built-In Procedures" in Oracle TimesTen In-Memory Database Reference.

12109

Syntax error in connection string

There is a syntax error in the specified connection string. Correct the connection string and try connecting again.

Version mismatch between the
backup files and restore.
Backed-up files are version
version_number; ttRestore
is version version_number

The restore operation failed because the backup files were created by a different version of TimesTen than the ttRestore utility used.

12116

Cannot create database for restore

Internal error. Contact TimesTen Technical Support.

12117

Disconnect from newly
created database failed

Internal error. Contact TimesTen Technical Support.

12119

Cannot open destination file

Failed to open database file while restoring from stream input.

12120

Insufficient bytes read from
input stream

Internal error. Contact TimesTen Technical Support.

12125

Bad data store file header
read from input stream

Verify that the stream input is valid.

12132

Error forming basename of
data store

Failed to create a file name from the DataStore attribute of the DSN.

12133

Data store file already exists

A database file with the same name as indicated by the DataStore attribute of the DSN already exists.

12134

Log file(s) already exist

Log file(s) with the same name as indicated by the DataStore attribute of the DSN already exists.

12135

Failed to delete data store
files; OS-detected error:
error_number

Internal error. Contact TimesTen Technical Support.

12136

Error while deleting log files

Internal error. Contact TimesTen Technical Support.

12148

Specified connection string
is NULL or of 0-length

The connection string argument passed is either NULL or an empty string. You must specify a valid connection string argument.

12150

Cannot start transaction to
update receiver CTN in
TTREP.REPPEERS

Internal error. Contact TimesTen Technical Support.

12151

Failed to commit TimesTen
transaction for updating
receiver CTN

Internal error. Contact TimesTen Technical Support.

12152

Cannot set timestamp column
for table

Internal error. Contact TimesTen Technical Support.

12153

Cannot get DS_OBJ_ID value
from TTREP.REPELEMENTS

Internal error. Contact TimesTen Technical Support.

12154

Cannot get TBLID value from
SYS.TABLES

Internal error. Contact TimesTen Technical Support.

12155

Cannot get row id for row in
TTREP.REPELEMENTS

Internal error. Contact TimesTen Technical Support.

12156

Too many tables found on
second pass

Internal error. Contact TimesTen Technical Support.

12157

Failed to update the table
IDs from the mapping we've
created

Internal error. Contact TimesTen Technical Support.

12158

Cannot set replication
fields in SYS.TABLES

Internal error. Contact TimesTen Technical Support.

12159

NULL passed for a pointer
argument

The pointer argument must be a non-NULL value.

12160

Timeout - the agent is still
starting

Under some conditions, you may receive this error when trying to stop the cache agent for a database while the agent is starting up. Retry the operation.

12161

Cannot backup temporary data stores

Backup is not allowed for temporary databases.

12164

RamGrace cannot be set for
temporary data stores

ttAdmin-ramGrace can only be set on a permanent database.

12166

Failed to start Backup

The replication agent ran into an error while running the ttBackup utility on the subscriber database or when running ttRepAdmin-duplicate concurrently on more than one database. Run the ttBackup utility on the subscriber with replication disabled, or avoid running two duplicate operations concurrently.

12184

Could not initialize
connection to TimesTen daemon

Internal error. Contact TimesTen Technical Support.

12185

No definitions of
replication store id for the
specified data store

Internal error. Contact TimesTen Technical Support.

12186

fstat() system call failed
for user/system odbc.ini fle

Internal error. Contact TimesTen Technical Support.

12187

read() system call failed
for user/system odbc.ini file

Internal error. Contact TimesTen Technical Support.

12188

close() system call failed
for user/system odbc.ini file

Internal error. Contact TimesTen Technical Support.

12189

Scan stopped for user/system
odbc.ini file

Internal error. Contact TimesTen Technical Support.

12190

Attribute name is too long

Maximum length of attribute names is 30 characters.

12191

Invalid length for connection string

The value specified for the length of the connection string to the SQLDriverConnect ODBC call is less than 0 and not equal to SQL_NTS.

12192

Invalid backup type

An invalid value was passed as the type parameter of the ttBackup utility library function. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12193

No backup directory specified

A null pointer or empty string was passed as the backupDir parameter of the ttBackup utility library function. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12194

Failed to retrieve data
store information

Internal error. Contact TimesTen Technical Support.

12195

Basename contains invalid
characters

An invalid value was passed as the baseName parameter of the ttBackup utility library function. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12196

Backup status file not found

No backup status file was found for the given backup directory and/or base name. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12197

Existing backup files do not
match data store

The backup files indicated by the given backup directory and/or base name are not from the database that is being backed up.Causes for the mismatch include:These backup files can be overwritten by specifying a non-atomic backup. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

The database that is stored in the backup files has a different database path name than the database that is being backed up.

The database being backed up has the same database path name as the database that is stored in the backup files, but the two databases do not have the same creation time. This can happen if the backed up database was destroyed and a new database was created with the same database path name.

12198

One or more files missing
from backup directory

One or more backup files are missing from the backup indicated by the given backup directory and/or base name. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12199

Cannot read directory
contents; OS-detected error:
error_number

The contents of the backup directory could not be read due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12200

Failed to open backup status
file: OS-detected error:
error_number

The backup status file for the backup indicated by the backup directory and/or base name could not be opened due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12201

Failed to read backup status
file: OS-detected error:
error_number

The backup status file for the backup indicated by the backup directory and/or base name could not be read due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12202

Failed to write backup
status file: OS-detected
error: error_number

The backup status file for the backup indicated by the backup directory and/or base name could not be written due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12203

Failed to close backup
status file: OS-detected
error: error_number

The backup status file for the backup indicated by the backup directory and/or base name could not be closed due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12204

Invalid or corrupted backup
status file

The backup status file for the backup indicated by the backup directory and/or base name is invalid or corrupt. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12205

Backup is incomplete

The backup status file for the backup indicated by the backup directory and/or base name is incomplete. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

The backup status information for the backup indicated by the backup directory and/or base name is corrupted or incomplete. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12207

Failed to write backup
status record; OS-detected
error: error_number

Backup status information for the backup indicated by the given backup directory and/or base name could not be written due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12208

Failed to retrieve file
information; OS-detected
error: error_number

An attempt to retrieve information about one or more of the backup files indicated by the backup directory and/or base name failed due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12209

Failed to open file
file_name; OS-detected
error: error_number

One or more of the backup files indicated by the backup directory and/or base name could not be opened due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12210

Failed to read backup file;
OS-detected error:
error_number

One or more of the backup files indicated by the backup directory and/or base name could not be read due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12211

Backup file is shorter than expected

One or more of the backup files indicated by the given backup directory and/or base name have been truncated. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12212

Failed to write backup file;
OS-detected error:
error_number

One or more of the backup files indicated by the backup directory and/or base name could not be written due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12213

Failed to close backup file;
OS-detected error:
error_number

One or more of the backup files indicated by the backup directory and/or base name could not be closed due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12214

Failed to rename backup
file; OS-detected error:
error_number

One or more of the backup files indicated by the backup directory and/or base name could not be renamed due to an operating system error. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12215

Backkup terminated because
data store connection
invalidated

The requested backup operation was terminated because the database connection was terminated. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12216

Invalid restore type

An invalid value was passed as the type parameter of the ttRestore utility library function. See "ttRestore" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12217

Cannot restore into a
temporary data store

A temporary database cannot be the target of a database restore operation. See "ttRestore" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12218

Could not get port number of
TimesTen Server. Make sure
that it is running

Generally, the TimesTen Server is automatically started by the TimesTen daemon. Upon start up, the TimesTen Server lets the daemon know the port number that the Server is listening on. This error indicates that there was a problem starting the TimesTen Server. Hence, the daemon does not know the port number of the TimesTen Server. Refer to the daemon/server log for further details.

12219

Failed to connect to
TimesTen Server. Refer
to user error log for further
details

A socket connection to the TimesTen Server failed. Refer to the daemon/server log for further details.

12220

Failed to send request to
TimesTen Server

A socket send call failed. Normally, this is accompanied with a description of the OS error.

Files can only be restored on the same platform type where they were backed up.

12222

Backed-up files appear to be
from a TimesTen release prior
to TimesTen 5.0

Files that were backed up using a TimesTen release prior to 5.0 cannot be restored using this TimesTen release's utilities.

12231

Failed to truncate tables

A problem occurred during the execution of the ttRepAdmin -duplicate utility with the-truncate option.

12232

Failed to drop objects

A problem occurred during the execution of ttRepAdmin -duplicate utility with the -drop option

12233

Failed to truncate table

Specifies the table that had the problem referred to in error 12231.

12234

Failed to drop table

Specifies a table that was referred to in error 12232.

12235

There are identifiers
supplied for the drop option
which are also quoted for the
truncate option

The ttRepAdmin -duplicate utility tries to drop and truncate the same table or tables with the -drop and -truncate options.

12236

There are duplicate
identifiers specified in the
drop option

The same table is listed twice for the -drop option of ttRepAdmin -duplicate.

12237

There are duplicate
identifiers specified in the
truncate option.

The same table is listed twice for the -truncate option of ttRepAdmin -duplicate.

12238

For -truncate or -drop you
can specify \"ALL\" or a list
of tables, not both.

For the -truncate or -drop options of the ttRepAdmin -duplicate utility, you can specify "ALL" or a list of tables, but you cannot specify both in the same statement.

12245

No definitions of
replication store id for the
data store DSN on
host_name

Arguments passed during database duplication are not consistent with store definitions on the source database.

12246

DSN DSN_name exceeds the
maximum length of length

A database name cannot exceed 32 characters.

12247

A sequence cannot be truncated

Occurs when the name of a sequence is supplied to the -truncate option of ttRepAdmin-duplicate or to ttRepDuplicateEx.

12248

RamGrace cannot be specified
with always or manual RAM policy

When setting the RAM residence policy for a database, a grace period can be used only with the inUse policy.

12249

The remoteDaemonPort can
only be 0 or between 1024 and
65535

Reset the value of the ttRepAdmin -duplicate -remoteDaemonPort option to a value specified in the error message.

12250

The duplicate verbosity
level must be 0, 1, or 2

Acceptable values for the ttRepAdmin -duplicate -verbosity option are 0, 1 or 2.

12251

The duplicate verbosity
level must be 0, 1, or 2

Acceptable values for the ttRepAdmin -duplicate -verbosity option are 0, 1 or 2.

12252

Could not check Oracle DB

An additional error message from the cache layer accompanies this message. Review that message to determine the problem and fix.

12253

The Active Standby Oracle
Database is the same as the
DR Oracle database

When the ttRepAdmin -duplicate -initCacheDR option is used the DR Oracle database cannot be the same database as the active standby Oracle subscribing database. The check has identified a tt_03_reppeers entry which is from one of the Active Standby master stores to the DR Oracle Database. Reconfigure the data recovery to resolve this conflict.

12254

Remote peer does not support
parallel replication.

There is a mismatch in the parallel replication configuration between two stores involved in a replication scheme, where one store is enabled for parallel replication and the other is not.

12255

A/S pairs cannot be created
when parallel mode
replication configured.

Active Standby Pair replication schemes are not configured while the database has been created with parallel replication attributes, with the ReplicationApplyOrdering attribute configured greater than 0.

12257

Error creating bookmarks for
the parallel tracks.

Internal error. Tried to create entries in TTREP.REPPEERS for parallel replication tracks. When parallel replication is enabled, there are more than one TTREP.REPPEERS entry for master->subscriber. The number of entries is dependent upon the ReplicationParallelism parameter.

12258

Return Receipt or Return
TwoSafe cannot be used when
parallel mode replication is
configured.

Return Receipt and Return Twosafe cannot be used for a return service when the database has been created with parallel replication attributes, where the ReplicationApplyOrdering attribute is greater than 0.

12259

A store cannot be defined as
a PROPAGATOR when parallel
mode replication is configured.

Propagator stores are not supported when the database has been created with parallel replication attributes, where the ReplicationApplyOrdering attribute is greater than 0.

12260

Create cache group is not
permitted when parallel mode
replication is configured.

Cache groups are not supported when the database has been created with parallel replication attributes, where the ReplicationApplyOrdering attribute is greater than 0.

12261

ALTER TABLE is not permitted
on a replicated table when
parallel mode replication is
configured.

ALTER TABLE is not allowed when the database has been created with parallel replication attributes, where the ReplicationApplyOrdering attribute is greater than 0. This error is raised at application time.

12262

Error setting track for
connection.

Internal Error. The replication agent cannot use a specific track for its database connection.

12263

Aging is not permitted on a
replicated table when
parallel mode replication is
configured.

In 11.2.1.6.0, aging on tables was allowed when ReplicationApplyOrdering was set to 1. Currently, we disable aging when ReplicationApplyOrdering is set to 1. When a database with ReplicationApplyOrdering set to 1 is upgraded from 11.2.1.6.0, aging will be disabled

12264

ALTER TABLE cannot be
replicated to a store with
parallel mode replication
enabled.

This error occurs if the replication agent detects ALTER TABLE when parallel mode replication is enabled.

12274

Failed to read track entries
for peer.

This is an internal error that is returned if the transmitter could not read metadata from ttrep.reppeers. Contact TimesTen Technical Support.

12700

NLSRTL environment could not
be initialized

The NLS data files could not be located. The installation directory may have been corrupted or become unreadable.

12701

DatabaseCharacterSet
attribute required for data
store creation. Refer to the
TimesTen documention for
information on selecting a
character set.

You must specify a value for the DatabaseCharacterSet attribute when creating a database. The database character set cannot be changed after database creation. For more details on selecting a database character set, see "Choosing a database character set" in the Oracle TimesTen In-Memory Database Operations Guide.

12702

Unable to load NLS data
data from NLS_data_item

A particular NLS data file could not be located. The installation directory may have been corrupted or become unreadable. NLS_data_item could be a character set name or a sort name.

12705

Invalid session parameter

The session parameter is unknown or unsupported by TimesTen. For example:

ALTER SESSION SET NLS_BOGUS='french';

returns

12705: Invalid NLS session parameter

12706

Invalid session parameter value.

The value supplied for the session parameter is unknown or unsupported by TimesTen. or example:

ALTER SESSION SET NLS_SORT='bogus';

returns

12706: Invalid NLS session parameter value

12707

Linguistic index maximum key
value length limit exceeded

The value computed for the linguistic index key exceeds the maximum length allowed for that index. There is a 64k upper limit for linguistic index key values.

12708

Conversion of TIMESTEN8
character set data is not
allowed

An operation either explicitly or implicitly tried to convert TIMESTEN8 data to another character set. Conversion of TIMESTEN8 character data is undefined and therefore not allowed.

12713

Character data loss in
NCHAR/CHAR conversion

NLS_NCHAR_CONV_EXCP was set to TRUE and a conversion was attempted for an NCHAR character having no corresponding mapping in the database character set.

12714

NLSSORT computation failed
due to invalid characters in
string

The string passed to the NLSSORT function contained invalid characters for the given character set. A meaningful NLSSORT result value could not be computed. Character data containing invalid characters is of dubious usefulness and should be eliminated from the database.

12715

NLS_SORT value must be
BINARY when database
character set is TIMESTEN8

When the database character set is TIMESTEN8, the only setting allowed for NLS_SORT is BINARY. Non-binary comparison rules for TIMESTEN8 data are undefined.

12716

'\' must be followed by four
hexadecimal characters or
another '\'

The UNISTR function argument allows the back-slash character only as an escape for a hexadecimal Unicode character or itself. For example:

UNISTR('\0041')

UNISTR('abc\\nop')

12717

Character data loss in
character set conversion

This is a warning. During character set conversion of data, a character was encountered for which no valid conversion exists. TimesTen substituted a replacement character in its place. You should change your connection character set to one that is compatible with the database character set in use.

12718

Error setting default
date/timestamp format
format_string

Contact TimesTen Technical Support.

13000

License file file_name does
not exist.

TimesTen cannot locate the evaluation license file.

13001

License file file_name unreadable.

TimesTen cannot read the evaluation license file.

13002

License key in file_name is
invalid.

Invalid evaluation license.

Errors 14000 - 14999

Error number

Error or warning message

Details

14000

TimesTen daemon internal
error: error_number

Internal error. Contact TimesTen Technical Support.

14001

TimesTen daemon out of
memory allocated_size

The TimesTen daemon has run out of swap space.

14002

TimesTen daemon port in use
port_number

The TimesTen daemon cannot listen on its specified port because the port is already in use.

14003

TimesTen daemon thread
creation failed: thread_name

TimesTen daemon thread creation failed.

14004

TimesTen daemon creation
failed: reason_for_failure

TimesTen daemon could not create database for specified reason.

14005

TimesTen daemon connection
failed: reason_for_failure

TimesTen daemon could not make new database connection for specified reason.

14006

TimesTen daemon disconnect
failed: reason_for_failure

TimesTen daemon could not do database disconnect for specified reason.

Cannot give a password to a user defined as IDENTIFIED EXTERNALLY, or remove a password for a user defined as an internal TimesTen user.

15011

Password exceeds limit of
number characters

PWD attribute is too long.

15012

Encrypted password must
have exactly number characters

PWDCrypt attribute is not the correct length.

15013

Cannot alter privileges for
the instance administrator user

Must be logged into administrator account to alter administrator privileges.

15014

Only the instance
administrator user can
perform this command

Insufficient privileges to execute command restricted to the administrator.

15015

Cannot alter password for
predefined users

Insufficient privileges to alter administrator password.

15016

Unsupported use of an
internal system-user acccount

One of the predefined users ('PUBLIC', 'SYS', 'TTREP') is being used in an unsupported operation.

15017

ADMIN privilege required to
alter attribute_name attribute

When Access Control is in use, changing first-connection attributes from their previous values requires the ADMIN privilege.

15018

Password is illegal.
Either it is empty, has
leading or trailing white
space characters, or
contains carriage-return,
newline or semi-colon characters.

Due to limitations in the ODBC connection string and .ini file syntax, passwords having any of the listed restrictions cannot be correctly recognized and are disallowed at password creation time.

15019

Only the instance admin may
alter the attribute attribute.

The current user is attempting to connect to the database using the specified first connection attribute with a value different from the existing database value. Only the instance administrator user may change that attribute.

The user can either connect as instance administrator to change the attribute value, or connect without changing the value.

15020

UID not specified

The UID was not specified when executing a ttRepAdmin -duplicate operation. The user must provide the UID and rerun the ttRepAdmin -duplicate operation.

15021

PWD or PWDCrypt not specified

The PWD or PWDCrypt were not specified when executing a ttRepAdmin -duplicate operation. The user must provide a password or a value for the PWDCrypt attribute and rerun the ttRepAdmin -duplicate operation,

15100

User user_name lacks
privilege privilege_name

The specified user must have the indicated privilege to perform the attempted operation.

15101

Cannot grant or revoke more
than a single atomic
privilege when logging is
not enabled

Perform separate GRANT or REVOKE operations for each privilege you wish to grant or revoke from the user.

15102

Statement compilation
failed. During privilege
checking for statement,
could not allocate num
bytes on the compilation heap

Internal error. Contact TimesTen Customer Support.

15103

System-defined users and
roles cannot be dropped

You cannot drop users and roles from TimesTen system tables.

15104

Only the instance
administrator can destroy a
database

You must be the instance administrator to create or destroy a database.

15105

User username requesting
database creation is not the
instance administrator.
Only the instance
administrator can create a
database

You must be the instance administrator to create or destroy a database.

15106

Database users cannot
invoke internal built-in
procedures

You attempted to execute a TimesTen built-in procedure that is reserved for internal use only.

15107

User lacks CREATE SESSION
privilege; logon denied

To perform operations on a TimesTen database, you must have the CONNECT or CREATE SESSION privilege in addition to any other privileges required for the specific operation.

15109

The system privilege SYSDBA
is not supported. The system
privilege ADMIN can be used
for most administrative tasks.

SYSDBA is not a valid privilege. Use the ADMIN privilege.

15110

object does not exist

This message displays in cases where the lack of existence should have been caught prior to privilege computation.

15111

Invalid privilege:
privilege. Roles are not
supported.

Check the name or spelling of this privilege. The name supplied is not supported.

This error is generated when the user tries to revoke one of the privileges that were granted to PUBLIC as part of database creation. Any other privileges that a user grants to PUBLIC can be revoked as usual.

15150

operation failed:
(internal error) error_message

The specified operation failed for the reason indicated in the error message.

15151

operation failed: User
user_name does not exist

The specified operation failed because the indicated user does not exist on the database.

15152

operation failed: Object
object_name does not exist

The specified operation failed because the indicated object does not exist on the database.

The operation failed because there is a mismatch between the specific privilege and the object.

15155

operation failed: You do
not have the rights to grant
or revoke privilege privilege_name

You do not have adequate privileges necessary to grant or revoke the specified privilege.

15156

operation failed: You do
not have the rights to grant
or revoke privilege
privilege_name on object_name

You do not have adequate privileges necessary to grant or revoke requested privilege on the specified object.

15157

operation failed: User
user_name is the owner of
object_name

User attempted to grant or revoke privileges for the indicated object to the current owner. An object's owner always has all privileges for that object. Additional privileges cannot be granted, and none of these privileges can be revoked. If necessary attempt the operation again after correcting the user name or object name.

You do not have adequate privileges to grant or revoke privileges to/from the instance administrator.

15159

operation failed:
privilege_name listed more
than once in privilege list.

You must indicate a privilege only once in the SQL statement when attempting to grant or revoke it.

15160

operation failed:
privilege_name on
object_name is listed more
than once in privilege list

You must indicate a privilege only once for a specific object in the SQL statement when attempting to GRANT or REVOKE it.

15161

operation failed:
keyword is redundant with ALL

You issued a GRANT ALL or REVOKE ALL statement, while attempting to grant or revoke other specific privileges. Adding additional privileges to the GRANT ALL (or REVOKE ALL) statement is redundant. Attempt the operation again and specify either ALL or the specific privileges that you wish to GRANT or REVOKE.

15162

operation failed:
keyword is redundant with
ALL on object_name

You issued a GRANT ALL or REVOKE ALL statement on the indicated object, while attempting to grant or revoke other specific privileges. Adding additional privileges to the GRANT ALL (or REVOKE ALL) statement is redundant. Attempt the operation again and specify either ALL or the specific privileges that you wish to GRANT or REVOKE.

The operation failed because you attempted to GRANT or REVOKE a privilege to/from an internal TimesTen user, such as sys. or ttrep.

15165

Invalid system privilege
sys_privilege.

The user specified an invalid privilege in a GRANT or REVOKE statement when a system privilege was expected. See the documentation for the list of valid system privileges and the appropriate syntax for specifying them.

15166

Invalid object privilege
object_privilege.

The user specified an invalid privilege in a GRANT or REVOKE statement when an object privilege was expected. See the documentation for the list of valid object privileges and the appropriate syntax for specifying them.

15167

Cannot drop a user that is
currently connected.

An attempt was made to drop a user that is currently connected to the database. That user must disconnect first, then the DROP USER command can be retried.

15168

Cannot drop a user that
owns database objects
(stringstring).

An attempt was made to drop a user that owns objects in the database. The existing object triggering the error is listed in the error message text, though there may be additional objects not listed. Drop all the objects owned by the user first, and then retry the DROP USER command.

Errors 16000 - 16999

Error Number

Error or warning message

Details

16001

TimesTen Replication Agent
(version version_number) started

Informational message. No action required.

16002

TimesTen Replication Agent
termination begun

Informational message. No action required.

16003

Replication Agent will not
be restarted automatically

Informational message. No action required.

16004

Failed to connect to
datastore
'data_store_name' for
'thread_name' thread

The specified thread was unable to connect to the named database.

16005

Failed to disconnect from
datastore
'data_store_name' for 'thread_name' thread

The specified thread was unable to disconnect from the named database.

16006

Failed to create DB context
for 'thread_name' thread

Creation of the structure that maintains status information for a specific thread failed.

16007

Failed to set DB context
for 'thread_name' thread

The internal request to create the structure that maintains status information for a specific thread failed.

16008

Failed to retrieve
datastore info

Fetching the database information block failed.

16009

Failed to determine
diskless status of the data store

Replication agent failed to determine the diskless status of the database.

16010

Failed to update diskless
status of the data store

Replication agent failed to set the diskless status of the database.

16011

To avoid data
inconsistency, copy the data
store from a replication
subscriber using 'ttRepAdmin
-duplicate'. Use
ForceConnect=1 in the
connection string to
override this restriction

Attempt to reconnect to the master store without first performing the duplicate operation. Set the ForceConnect attribute as described in "Recovering NONDURABLE databases" in the Oracle TimesTen In-Memory Database TimesTen to TimesTen Replication Guide for more information.

16012

Data store is invalid.
Replication Agent exiting
but may be restarted by
TimesTen daemon (depending
on restart policy)

The replication agent considers the database to be invalid.

16014

Current replication schema
version is
schema_version_number; we
require schema_version_number

The version of the SQL schema that contains the replication schema is incompatible with the version of TimesTen that is currently operating.

16015

Failed to determine
replication schema version

The replication agent was unable to determine the version of the SQL schema that contains the replication schema.

16016

Internal Error. Error from
TimesTen daemon: daemon_name

A request to the TimesTen daemon failed with the specified error message.

16017

Failed to initialize
socket_name socket due to
malloc failure

The replication agent was unable to allocate a data structure for communicating with the TimesTen daemon. This is a memory allocation failure.

The replication agent is exiting, but some of the threads are not properly terminated.

16029

Waiting for thread_name'
thread to finish

Informational message. No action required.

16030

*** CANNOT PERFORM ANY
REPLICATION WORK *** The
replication schema has no
information about the local
store. The schema may be
empty or incomplete, or the
local store incorrectly
represented. Monitoring the
schema for changes...

Informational message. No action required.

16031

Failed to allocate
number_of_bytes bytes

Memory allocation failure

16032

Call to function_name()
failed. System Error:
error_number

The specified operating system call failed with the error that is displayed.

16033

Waiting for resolution of
in-doubt transaction

XA transaction has been prepared but not committed.

Informational message. No action required.

16034

Invalid special purpose
debug options entry in
debug.options file

An unrecognized debug option was specified.

16035

Special Purpose. Repagent
enabled for check
debugging_option

Informational message. No action required.

16036

A transmitter thread
already exist for peer
'dsname' on 'host_name'

Internal error. Two master threads are started for the same subscriber.

16037

Internal Error. Nested
transaction started by
function_name()

Unexpected nested internal query

16038

Failed to begin transaction
for caller: function_name()

The replication agent was unable to start a transaction.

16039

Failed to commit
transaction for caller:
function_name()

The replication agent was unable to commit a transaction.

16040

Failed to rollback
transaction for caller:
function_name()

Replication agent requested that a completed transaction be rolled back, but the request failed.

16041

Failed to compute a new
replication hold LSN in
function_name()

The replication agent was unable to set the HOLD log sequence number. The hold log is the oldest record held in the log for possible transmission to a subscriber.

16042

Failed to awaken log
readers (TRANSMITTER threads)

A keep-alive message to a replication master failed.

16043

Failed to retrieve
replication LSN from data store

Reading the log sequence number failed.

16044

Failed to retrieve my store
ID from data store

The replication agent could not determine the ID of the connected database.

The commit of a block of transactions had errors. Details in other error messages for the individual failures. Some of the failures may be temporary.

16188

rxCommitTx() failed to commit

The commit of a block of transactions failed.

16189

Failed to begin
transaction. Subscriber
state is state_number

The replication agent is beginning a transaction, but it is not in the idle state. Internal error. Contact TimesTen Technical Support.

16190

Failed to push propagation loop

A propagation path could not be stored, usually because it is a loop.

16191

Replacing old table
definition
(table_definition) with
the one received from peer (dsname)

A SQL table that has already been seen in the replication stream has been encountered. This can occur if there are SQL schema changes.

16192

Skipping definition
received for already-defined
table table_name. Part of
previously processed transaction

A SQL table that has already been seen in the replication stream has been encountered. This can occur if there are SQL schema changes. The transaction is skipped and the new table definition is discarded.