Oracle® TimesTen In-Memory Database

Error Messages and SNMP Traps

11g Release 2 (11.2.2)

E21646-15

December 2014

Oracle TimesTen In-Memory Database Error Messages and SNMP Traps, 11g Release 2 (11.2.2)

E21646-15

Copyright © 1996, 2014, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Preface

Oracle TimesTen In-Memory Database (TimesTen) is a relational database that is memory-optimized for fast response and throughput. The database resides entirely in memory at runtime and is persisted to disk storage for the ability to recover and restart. Replication features allow high availability. TimesTen supports standard application interfaces JDBC, ODBC, and ODP.NET, in addition to Oracle interfaces PL/SQL, OCI, and Pro*C/C++. TimesTen is available separately or as a cache for Oracle Database.

Audience

This guide provides a reference of all TimesTen error messages and information on SNMP traps.

This document is intended for readers with a basic understanding of database systems.

Related documents

TimesTen documentation is available on the product distribution media and on the Oracle Technology Network:

http://www.oracle.com/technetwork/database/database-technologies/timesten/documentation/index.html

Oracle Database documentation is also available on the Oracle Technology network. This may be especially useful for Oracle Database features that TimesTen supports but does not attempt to fully document.

http://www.oracle.com/pls/db112/homepage/

Conventions

TimesTen supports multiple platforms. Unless otherwise indicated, the information in this guide applies to all supported platforms. The term Windows refers to all supported Windows platforms and the term UNIX applies to all supported UNIX platforms, including Linux. See "Platforms" in Oracle TimesTen In-Memory Database Release Notes for specific platform versions supported by TimesTen.

Note:

In TimesTen documentation, the terms "data store" and "database" are equivalent. Both terms refer to the TimesTen database.

This document uses the following text conventions:

Convention
Meaning

boldface
Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic
Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace
Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

italic monospace
Italic monospace type indicates a variable in a code example that you must replace. For example:

Driver=install_dir/lib/libtten.sl

Replace install_dir with the path of your TimesTen installation directory.

[ ]
Square brackets indicate that an item in a command line is optional.

{ }
Curly braces indicated that you must choose one of the items separated by a vertical bar ( | ) in a command line.

|

A vertical bar (or pipe) separates arguments that you may use more than one argument on a single command line.

. . .
An ellipsis (. . .) after an argument indicates that you may use more than one argument on a single command line.

%

The percent sign indicates the UNIX shell prompt.

#

The number (or pound) sign indicates the UNIX root prompt.

TimesTen documentation uses these variables to identify path, file and user names:

Convention | Meaning
install_dir | The path that represents the directory where the current release of TimesTen is installed.
TTinstance | The instance name for your specific installation of TimesTen. Each installation of TimesTen must be identified at install time with a unique alphanumeric instance name. This name appears in the install path.
bits or bb | Two digits, either 32 or 64, that represent either the 32-bit or 64-bit operating system.
release or rr | The first three parts in a release number, with or without dots. The first three parts of a release number represent a major TimesTen release. For example, 1122 or 11.2.2 represents TimesTen 11g Release 2 (11.2.2).
jdk_version | Two digits that represent the version number of the major JDK release. Specifically, 14 represent JDK 1.4; 5 represents JDK 5.
timesten | A sample name for the TimesTen instance administrator. You can use any legal user name as the TimesTen administrator. On Windows, the TimesTen instance administrator must be a member of the Administrators group. Each TimesTen instance can have a unique instance administrator name.
DSN | The data source name.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

1 Warnings and Errors

This chapter first explains how to retrieve errors and warnings, and then provides a comprehensive list of all errors and warnings, ordered by error number.

By default, TimesTen messages and diagnostic information are stored in:

A user error log that contains error message information. Generally, these messages contain information on actions you may need to take. The default file is daemon_home/tterrors.log. For more information on modifying the location of the user error log, see "Modifying informational messages" in the Oracle TimesTen In-Memory Database Operations Guide.

A support log containing everything in the user error log plus information that may be useful for TimesTen Customer Support. The default file is daemon_home/ttmesg.log. For more information on modifying the location of the support log, see "Modifying informational messages" in the Oracle TimesTen In-Memory Database Operations Guide.

An invalidation file containing diagnostic information when TimesTen invalidates a database. This file provides useful troubleshooting information for TimesTen Customer Support. The invalidation file is created and named based on the value specified by the DataStore connection attribute. This connection attribute is not a file name. For example on Linux platforms, if the DataStore connection attribute is /home/ttuser/AdminData, the actual invalidation file name has a suffix, .inval, /home/ttuser/AdminData.inval. For more information on the DataStore connection attribute, see "DataStore" in the Oracle TimesTen In-Memory Database Reference.

Note:

Not all error numbers are currently in use.

Retrieving errors and warnings

In JDBC, the native error code and message can be retrieved as shown in this example:

Example 1-1 Native error code and message retrieval in JDBC

private static void printSQLExceptions(SQLException e)
{
     while (e != null) {

        System.out.println("SQLState: " +
        e.getSQLState());
        System.out.println("Message : " +
        e.getMessage());
        System.out.println("Vendor  : " +
        e.getErrorCode());
        e.printStackTrace();
        e = e.getNextException();
        System.out.println("");
     }
      e.printStackTrace();
}
        .   .   .

try {
      // JDBC method calls here
}
catch (SQLException ex) {

     ex.printSQLExceptions();
}

In ODBC, the native error code and message can be retrieved with the SQLError function, as shown in the following example:

Example 1-2 Native error code and message retrieval in ODBC

#define MSG_LNG 512

SQLCHAR szSqlState[MSG_LNG];                     /* SQL state string */
SQLINTEGER pfNativeError;                        /* Native error code */
SQLCHAR szErrorMsg[MSG_LNG];
                                     /* Error msg text buffer pointer */
SQLSMALLINT pcbErrorMsg;
                                    /* Error msg text Available bytes */
SQLRETURN ret = SQL_SUCCESS;

while ( ret == SQL_SUCCESS || ret == SQL_SUCCESS_WITH_INFO ) {
  ret = SQLError(henv, hdbc, hstmt, szSqlState, &pfNativeError,
                 szErrorMsg, MSG_LNG, &pcbErrorMsg);
  switch (ret) {
  case SQL_SUCCESS:
    fprintf(stderr, "*** %s\n*** ODBC Err = %s, ",
                   "TimesTen Err = %ld\n",
            szErrorMsg, szSqlState, pfNativeError);
    break;
  case SQL_SUCCESS_WITH_INFO:
    fprintf(stderr, "*** Call to SQLError failed with return ",
                    "code of SQL_SUCCESS_WITH_INFO.\n ",
                    "*** Need to increase size of ",
                    "message buffer.\n");
    break;
  case SQL_INVALID_HANDLE:
    fprintf(stderr, "*** Call to SQLError failed with ",
                   "return code of SQL_INVALID_HANDLE.\n");
    break;
  case SQL_ERROR:
    fprintf(stderr, "*** Call to SQLError failed with ",
                    "return code of SQL_ERROR.\n");
   break;
  case SQL_NO_DATA_FOUND:
    break;
  }
}

It is possible for a single ODBC or JDBC operation to generate multiple errors. These errors can be retrieved using multiple calls to the ODBC function SQLError or the JDBC method SQLException.

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 database error codes instead of TimesTen error codes. The error messages that accompany the error codes may come from the TimesTen error catalog or the Oracle database error catalog.

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 UNIX
install_dir\include on Windows

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

The errors are listed according to the following ranges:

Errors 0 - 999

Errors 1000 - 1999

Errors 2000 - 2999

Errors 3000 - 3999

Errors 4000 - 4999

Errors 5000 - 5999

Errors 6000 - 6999

Errors 7000 - 7999

Errors 8000 - 8999

Errors 9000 - 9999

Errors 10000 - 10999

Errors 11000 - 11999

Errors 12000 - 13999

Errors 14000 - 14999

Errors 15000 - 15999

Errors 16000 - 16999

Errors 17000 - 19999

Errors 20000 - 39999

Errors 40000 - 49999

Errors 50000 - 59999

Errors 0 - 999

Error number
Error or warning message
Details

400

Data store header fails
basic sanity test

Type of Message: Internal Error

Cause: The checkpoint file contains inconsistent or corrupted information.

Impact: You cannot load or recover from the checkpoint file.

User Action: If you receive this error for both checkpoint files, restore your database from a backup. For more information, see "Migration, Backup, and Restoration" in the Oracle TimesTen In-Memory Database Installation Guide. For additional help, contact TimesTen Customer Support.

402

Cannot close data store
file. OS-detected error:
os_error_number

Type of Message: Internal Error

Cause: While attempting to close the database file, the operating system encountered an error.

Impact: You may be unable to connect to the database or load it into memory.

User Action: Diagnose and troubleshoot the operating system error. Then, load the database into memory using ttAdmin -ramload. For more information, see "ttAdmin" in the Oracle TimesTen In-Memory Database Reference. For additional help, contact TimesTen Customer Support.

403

Attempt to read from
checkpoint truncated

Type of Message: Internal Error

Cause: During a checkpoint read, TimesTen detected that the checkpoint file contains less information than expected.

Impact: You cannot load or recover from the checkpoint file.

User Action: If you receive this error for both checkpoint files, restore your database from a backup. For more information, see "Migration, Backup, and Restoration" in the Oracle TimesTen In-Memory Database Installation Guide. For additional help, contact TimesTen Customer Support.

404

Corrupted block header

Type of Message: Internal Error

Cause: The checkpoint file contains inconsistent or corrupted information.

Impact: You cannot load or recover from the checkpoint file.

User Action: If you receive this error for both checkpoint files, restore your database from a backup. For more information, see "Migration, Backup, and Restoration" in the Oracle TimesTen In-Memory Database Installation Guide. For additional help, contact TimesTen Customer Support.

406

Incomplete write to file
file_name. OS-detected
error: os_error_number

Type of Message: Error

Cause: TimesTen failed to write to a file.

Impact: The operation you attempted failed.

User Action: Diagnose and troubleshoot the operating system error. Then, verify the functionality of the file system or device that holds the reported file. After verifying the functionality, retry the operation. If the problem persists, contact TimesTen Customer Support.

407

Failed to seek in
checkpoint file.
OS-detected error:
os_error_number

Type of Message: Internal Error

Cause: An attempt to seek within a checkpoint file has failed. An operating system call failed with the specified operating system error.

Impact: If this error occurs while loading or recovering from a checkpoint file, the attempt fails with that particular checkpoint file.

User Action: If this error occurred while performing a checkpoint, retry the checkpoint. If the second attempt fails or the error occurred for any other reason, contact TimesTen Customer Support.

408

Failed to sync checkpoint
file file_name to
disk. OS-detected error:
os_error_number

Type of Message: Internal Error

Cause: An attempt to synchronize a checkpoint file to disk has failed. An operating system call failed with the specified operating system error.

Impact: If checkpoints keep failing, database recovery takes longer and transaction log files do not get purged.

User Action: If this error occurred while performing a checkpoint, retry the checkpoint. If the second attempt fails or the error occurred for any other reason, contact TimesTen Customer Support.

409

Invalid checkpoint LSN

Type of Message: Internal Error

Cause: The checkpoint file contains invalid internal information.

Impact: The database cannot be recovered from the checkpoint file.

User Action: Contact TimesTen Customer Support.

411

OS-detected error error
while destroying directory
directory

Type of Message: Error

Cause: TimesTen cannot destroy the specified directory because of an operating system error.

Impact: TimesTen cannot destroy the specified directory.

User Action: Diagnose and troubleshoot the operating system error.

412

Bad file-open mode

Internal error. Contact TimesTen Customer Support.

413

Bad file-exists mode

Internal error. Contact TimesTen Customer Support.

414

Bad file-missing mode

Internal error. Contact TimesTen Customer Support.

415

Incompatible file-open modes

Internal error. Contact TimesTen Customer Support.

416

Block merge operation
terminated due to high
contention

Type of Message: Error

Cause: The ttCompact built-in procedure failed to merge one or more blocks. Another operation is currently using one or more blocks.

Impact: The ttCompact built-in procedure did not finish executing.

User Action: Retry the operation using the ttCompact built-in procedure. For more information, see "ttCompact" in the Oracle TimesTen In-Memory Database Reference.

420

Operation is not permitted
over client-server
connections

Type of Message: Error

Cause: TimesTen cannot perform the operation in client/server connections, and it is only supported in direct connections.

Impact: TimesTen cannot perform the operation.

User Action: Attempt the operation over a direct connection. For information on defining DSNs for direct connections, see "Defining DSNs for direct or client/server connections" in the Oracle TimesTen In-Memory Database Operations Guide.

421

Invalid file handle (may
have been closed by
application)

Type of Message: Error

Cause: The file handle that reads the transaction log unexpectedly closed. This error generally indicates an application programming error.

Impact: Your application cannot read the transaction log.

User Action: Check your application to see if it is improperly closing the file handle associated with the transaction log.

422

File handle repositioned (may
have been read or written by
application)

Type of Message: Error

Cause: The file handle that reads the transaction log unexpectedly repositioned. This error generally indicates an application programming error.

Impact: Your application cannot read the transaction log.

User Action: Check your application to see if it is reading from or writing to the wrong file handle.

423

Log directory in NFS is
not supported on this
platform

Type of Message: Error

Cause: You attempted to store transaction log files in a Windows network share.

Impact: TimesTen does not support storing transaction log files in a Windows network share.

User Action: Ensure that the transaction log directory is not in a Windows network share.

600

Checkpoint not done due to
transaction commit/rollback
failure

Type of Message: Error

Cause: Commit or rollback of the transaction failed.

Impact: Checkpointing was not attempted.

User Action: Consider calling the ttCkpt built-in procedure to create a checkpoint. For more information, see "ttCkpt" in the Oracle TimesTen In-Memory Database Reference.

601

Checkpoint failure

Type of Message: Error

Cause: Checkpointing failed.

Impact: TimesTen cannot create the checkpoint.

User Action: Check that there is sufficient disk space and that database files are writable, then retry.

602

Transaction already has a
pending fuzzy checkpoint
request

Type of Message: Error

Cause: A transaction attempted to perform a checkpoint, but the transaction has a pending checkpoint request.

Impact: TimesTen cannot perform the checkpoint.

User Action: Commit or rollback the current checkpoint transaction. Then, retry the checkpoint operation in a new transaction, using the ttCkpt built-in procedure. For more information, see "ttCkpt" in the Oracle TimesTen In-Memory Database Reference.

603

Transaction already has a
pending checkpoint request

Type of Message: Error

Cause: A transaction attempted to perform a fuzzy checkpoint. However, the transaction has a pending checkpoint request.

Impact: TimesTen cannot perform the fuzzy checkpoint.

User Action: Commit or rollback the current checkpoint transaction. Then, retry the fuzzy checkpoint operation in a new transaction, using the ttCkpt built-in procedure. For more information, see "ttCkpt" in the Oracle TimesTen In-Memory Database Reference.

604

Log missing record for
checkpoint file (lsn
log_file_number.log_file_offset).
info

Type of Message: Error

Cause: The transaction log on disk may be truncated or corrupted. The transaction log may be missing log records related to the specified checkpoint file.

Impact: TimesTen ignores the transaction log on disk, moves any existing log files to the specified directory, and recovers the database from the checkpoint files.

User Action: None.

605

Checkpoint Log record
(number.number)
not present

Type of Message: Error

Cause: The specified log record is either missing or corrupted. If the transaction log on disk has been truncated or otherwise corrupted, it may be missing log records corresponding to the checkpoints on disk.

Impact: The database cannot be loaded into memory.

User Action: Contact TimesTen Customer Support.

606

Checkpoint cannot proceed
because another checkpoint
or backup is in progress

Type of Message: Error

Cause: TimesTen cannot execute a checkpoint operation cannot because another checkpoint or backup is in progress.

Impact: The current checkpoint operation cannot begin.

User Action: Wait until the backup or checkpoint has completed and retry the checkpoint operation.

607

Backup cannot proceed
because another checkpoint
or backup is in progress

Type of Message: Error

Cause: TimesTen cannot execute a backup operation because another checkpoint or backup is in progress.

Impact: The current backup operation cannot begin.

User Action: Wait until the backup or checkpoint has completed and retry the backup operation. If you attempted a ttRepAdmin -duplicate operation, retry the operation.

608

Another connection
(# connection_id) has already
configured table table_name
for parallel insert

Type of Message: Error

Cause: This error message can only occur on an Exalytics Business Intelligence server. The ttParallelInsertBegin built-in procedure failed because another connection already configured the specified table for parallel insert mode.

Impact: The specified table cannot be configured for parallel insert mode.

User Action: Wait and retry the operation. Consider terminating the existing ttParallelInsertBegin built-in procedure by using the ttParallelInsertEnd built-in procedure.

609

Data store failed validity
check

Type of Message: Internal Error

Cause: TimesTen found an invalid database block while performing a checkpoint.

Impact: The current checkpoint operation cannot complete. If several checkpoints fail in a row, the log files will start accumulating.

User Action: Retry the checkpoint operation. If the problem persists, use the ttAdmin utility to unload and then reload the database into memory. For more information on the ttAdmin utility, see "ttAdmin" in the Oracle TimesTen In-Memory Database Reference. If this does not solve the error, contact TimesTen Customer Support.

610

End-checkpoint log record
not found

Type of Message: Internal Error

Cause: TimesTen cannot find a checkpoint related log record while loading the database into memory.

Impact: The database cannot be loaded into memory.

User Action: Contact TimesTen Customer Support.

611

Backup process died

Type of Message: Error

Cause: The ttBackupStatus built-in procedure returns this error message when an in-progress backup was killed or died unexpectedly.

Impact: TimesTen cannot to create a backup copy of the database.

User Action: Attempt to create another backup of the database with the ttBackup utility. For more information on the ttBackup utility, see "ttBackup" in the Oracle TimesTen In-Memory Database Reference. If this is a recurrent error, contact TimesTen Customer Support.

620

Another table (table_name) is
already configured for
parallel insert

Type of Message: Error

Cause: This error message can only occur on an Exalytics Business Intelligence server. The ttParallelInsertBegin built-in procedure failed because another table is already configured for parallel insert mode. Only one table is allowed to be in parallel insert mode at any given time.

Impact: The table you specified cannot be configured for parallel insert mode.

User Action: Wait and retry the operation. Consider terminating the existing ttParallelInsertBegin built-in procedure by using the ttParallelInsertEnd built-in procedure.

621

Table table_name is already
configured for parallel
insert. To change
parallelism, call
ttParallelInsertEnd and then
ttParallelInsertBegin again.

Type of Message: Error

Cause: This error message can only occur on an Exalytics Business Intelligence server. The ttParallelInsertBegin built-in procedure failed because the specified table is already configured for parallel insert mode. Only one table is allowed to be in parallel insert mode at any given time.

Impact: None.

User Action: None.

622

User user_name does not
have group permission to
connect to data store

Type of Message: Error

Cause: TimesTen cannot access the database files because the specified user does not have sufficient operating system file access permissions.

Impact: TimesTen cannot connect to the database.

User Action: Grant operating system file access permissions to the specified user. For more information, see "TimesTen instance administrators and users groups" in the Oracle TimesTen In-Memory Database Installation Guide.

623

User user_name does not
have group permission to
create data store

Type of Message: Error

Cause: TimesTen cannot access the database files because the specified user does not have sufficient operating system file access permissions.

Impact: TimesTen cannot load or destroy the database.

User Action: Grant operating system file access permissions to the specified user. For more information, see "TimesTen instance administrators and users groups" in the Oracle TimesTen In-Memory Database Installation Guide.

629

No permission to access
data store files

Type of Message: Error

Cause: The TimesTen users does not have the file system permissions to access the data store files or directory.

Impact: TimesTen cannot connect to or create a database from the specified directory.

User Action: Ensure that the TimesTen user belongs to a user group that has the proper file system permissions for the data store files and directory. For more information, see "Directory and file permissions" in the Oracle TimesTen In-Memory Database Installation Guide.

649

Log file file_name has
been purged

Type of Message: Warning

Cause: TimesTen purged the specified log file. By default, TimesTen automatically removes archived transaction log files at checkpoint time.

Impact: TimesTen removed the specified transaction log file from disk.

User Action: To retain archived transaction log files, set the LogPurge attribute to 0 in the odbc.ini file for UNIX or in the ODBC Data Source Administrator for Windows. For more information on transaction log files, see "Managing transaction log buffers and files" in the Oracle TimesTen In-Memory Database Operations Guide. For more info on the LogPurge attribute, see "LogPurge" in the Oracle TimesTen In-Memory Database Reference.

650

Invalid backup type

Type of Message: Error

Cause: The specified backup type is invalid.

Impact: TimesTen cannot perform the backup.

User Action: Specify a valid backup type. For more information about valid backup types, see "ttBackup" in the Oracle TimesTen In-Memory Database Reference.

651

Backup path is not enabled
for incremental backup

Type of Message: Error

Cause: The backup file must be enabled for incremental backups when it is created.

Impact: TimesTen cannot perform the incremental backup.

User Action: Use the ttBackup -type option to enable incremental backups. For more information, see "ttBackup" in the Oracle TimesTen In-Memory Database Reference.

652

Backup directory does not
exist

Type of Message: Error

Cause: The backup path you specified with the -dir option of the ttBackup utility does not exist.

Impact: The backup cannot be performed.

User Action: Create or specify a valid backup directory. For more information about the ttBackup utility, see "ttBackup" in the Oracle TimesTen In-Memory Database Reference.

653

Operation is not permitted in
parallel insert mode

Type of Message: Error

Cause: This error message can only occur on an Exalytics Business Intelligence server. The operation failed because it is not permitted in parallel insert mode. When a table is configured for parallel insert mode, only INSERT operations are permitted. Also, the table ID of the target table must match the ID stored for the connection.

Impact: The operation cannot be completed.

User Action: Make sure you are performing INSERT operations on the table. Also, check that the table ID of the target table matches the ID stored for the connection.

654

Too many incremental-enabled
backup directories

Type of Message: Error

Cause: You attempted to create an incremental backup instance. TimesTen is already at the maximum supported number of incremental-enabled backup instances for this database. For more information on the supported number of incremental-enabled backup instances, see "Types of backup provided" in the Oracle TimesTen In-Memory Database Installation Guide.

Impact: The incremental backup instance cannot be created.

User Action: If you want to create a new incremental-enabled backup instance for this database, consider disabling incremental backups for another backup instance of this database. For more information on how to disable incremental backups, see "ttBackup" in the Oracle TimesTen In-Memory Database Reference.

655

Global thread-pool limit
(thread-pool_limit) reached -
operation aborted

Type of Message: Error

Cause: This error message can only occur on an Exalytics Business Intelligence server. The ttParallelInsertBegin built-in procedure failed because the limit of the global thread pool has been reached.

Impact: The requested degree of parallelism cannot be obtained.

User Action: Consider stopping parallel insert operations initiated by other connections. Then, retry the operation.

657

Backup path exceeds maximum
length of number
characters

Type of Message: Error

Cause: The backup path you specified with the -dir option of the ttBackup utility exceeds the maximum supported path length. The error message indicates the maximum supported path length.

Impact: The backup cannot be performed.

User Action: Create or specify a path no longer than the maximum supported path length. For more information about the ttBackup utility, see "ttBackup" in the Oracle TimesTen In-Memory Database Reference.

658

Backup point is behind
backup's log hold

Internal error. Contact TimesTen Customer Support.

659

Backup is out of date

Type of Message: Error

Cause: The backup files specified by the backup directory, or base name, or both are not from the database that TimesTen is trying to back up. The backup files may be from a previous database that had the same database path name but which has since been destroyed.

Impact: TimesTen failed to create a backup of the database.

User Action: Use the -force option of the ttBackup utility to overwrite the out-of-date backup file. For more information on how to use ttBackup -force, see "ttBackup" in the Oracle TimesTen In-Memory Database Reference.

660

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

Internal error. Contact TimesTen Customer Support.

661

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

Internal error. Contact TimesTen Customer Support.

662

Data store file file_name
reflects unfinished restore
operation.

Type of Message: Error

Cause: TimesTen cannot to recover from the specified database file because it is the result of an incomplete restore operation. Common causes for this are:

- A user-initiated interruption of an in-progress restore operation.

- An out of space condition in the file system that contains the database's checkpoint files.

- A system failure.

Impact: The TimesTen database cannot recover from the specified database file.

User Action: Ensure that there is available disk space on the disk that contains your checkpoint files. If the disk is low on space, make more disk space available. Once you have made more disk space available, retry the restore operation.

664

Log record size of number
bytes exceeds maximum size
of number bytes

Internal error. Contact TimesTen Customer Support.

665

The size of LogBufMB should
be at least
LogBufParallelism * 8

Type of Message: Error

Cause: You specified a value for the LogBufMB attribute that is too small.

Impact: TimesTen cannot set the specified LogBufMb size.

User Action: Increase the size of the LogBufMB attribute to a value that is at least eight times the value of LogBufParallelism. You can modify this attribute in the odbc.ini file for UNIX or in the ODBC Data Source Administrator for Windows. For more information on the LogBufMB attribute, see "LogBufMB" in the Oracle TimesTen In-Memory Database Reference.

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 nonzero value or ReplicationParallelism to 0 or 1.

For more information about ReplicationApplyOrdering, see "ReplicationApplyOrdering" in the Oracle TimesTen In-Memory Database Reference. For more information about ReplicationParallelism, see "ReplicationParallelism" in the Oracle TimesTen In-Memory Database Reference.

668

LogBufParallelism value of
LogBufParallelism_value
cannot be smaller than
ReplicationParallelism
value of
ReplicationParallelism_value

Type of Message: Error

Cause: The value of the ReplicationParallelism data store attribute is greater than the value of the LogBufParallelism first connection attribute.

Impact: TimesTen cannot create or connect to the database.

User Action: Change the value of the LogBufParallelism attribute, or the value of the ReplicationParallelism attribute, or both values so that the value of the ReplicationParallelism attribute is not greater than the value of the LogBufParallelism attribute. For more information on the LogBufParallelism first connection attribute, see "LogBufParallelism" in the Oracle TimesTen In-Memory Database Reference. For more information on the ReplicationParallelism data store attribute, see "ReplicationParallelism" in the Oracle TimesTen In-Memory Database Reference.

669

Cannot change replication
track within an active
transaction.

Type of Message: Error

Cause: Your application is not allowed to change the parallel replication track in which it writes logs after it has started a transaction.

Impact: TimesTen cannot change the replication track.

User Action: None.

For more information on parallel replication tracks, see "ReplicationTrack" in the Oracle TimesTen In-Memory Database Reference.

670

Batch cursors cannot be
used because  replication
tracks are not enabled.
(ReplicationParallelism =
ReplicationParallelism_value
ReplicationApplyOrdering =
ReplApplyOrdering_setting).

Internal error. Contact TimesTen Customer Support.

680

Global thread-pool limit
(thread_pool_limit) reached -
parallelism was set
to parallelism_value

Type of Message: Warning

Cause: This warning message can only occur on an Exalytics Business Intelligence server. The degree of parallelism you specified for the ttParallelInsertBegin built-procedure cannot be met because the global thread pool limit has been reached.

Impact: TimesTen sets the degree of parallelism to the maximum possible value based on the current global thread pool limit.

User Action: Consider increasing the global thread pool limit with the ttParallelOpsPoolSizeSet built-in procedure.

681

Parallel Insert is not
supported on this platform

Type of Message: Error

Cause: This error message can only occur on an Exalytics Business Intelligence server. You attempted to use the ttParallelInsertBegin built-in procedure on an unsupported platform.

Impact: The ttParallelInsertBegin built-in procedure cannot be used on the current platform.

User Action: None.

682

Global thread-pool limit was
set to
global_thread_pool_limit
(max. allowable in this
system)

Type of Message: Warning

Cause: This warning message can only occur on an Exalytics Business Intelligence server. You specified a global thread pool limit that is greater than the maximum supported value.

Impact: TimesTen sets the global thread pool to the maximum supported value.

User Action: None.

683

Parallelism was set to
parallelism_value (max.
allowable value)

Type of Message: Warning

Cause: This warning message can only occur on an Exalytics Business Intelligence server. The degree of parallelism you specified for the ttParallelInsertBegin built-in procedure cannot be set because it exceeds the maximum allowable value.

Impact: TimesTen sets the degree of parallelism to the maximum allowable value.

User Action: None.

684

No table is configured for
parallel insert

Type of Message: Warning

Cause: This warning message can only occur on an Exalytics Business Intelligence server. You attempted to call the ttParallelInsertEnd built-in procedure. However, the current connection has not started a parallel insert operation.

Impact: None.

User Action: None.

700

Waiting for other 'in flux'
threads failed

Internal error. Contact TimesTen Customer Support.

701

Marking data store 'in
flux' failed

Internal error. Contact TimesTen Customer Support.

702

Connect failed because max
number of connections
exceeded

Type of Message: Error

Cause: TimesTen reached the maximum number of connections allowed for the database or instance.

Impact: You cannot connect to the database.

User Action: Consider disconnecting applications that are not using the database. For more information, see "System limits" in the Oracle TimesTen In-Memory Database Reference.

703

Subdaemon connect to 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 Customer Support.

704

Connecting to a data store
undergoing recovery after
invalidation

Type of Message: Error

Cause: Another application connected to the database has failed; the RAM-resident version of the database is corrupted.

Impact: You cannot connect to the database while it is being invalidated.

User Action: Try to reconnect after the database invalidation completes.

706

Spawning a thread in the
daemon failed

Internal error. Contact TimesTen Customer Support.

707

Attempt to connect to a
data store that has been
manually unloaded from RAM

Type of Message: Error

Cause: The application failed to connect to a database because the RAM residence policy of the database is set to manual. Also, the database has been manually unloaded from RAM.

Impact: Applications cannot connect to the database.

User Action: Load the database into memory using ttAdmin -ramload. For more information, see "ttAdmin" in the Oracle TimesTen In-Memory Database Reference.

709

Adding new data store to
catalog failed, OS error
'os_error_number'

Type of Message: Error

Cause: The TimesTen daemon cannot add the new database to the catalog. When a database is created, the daemon stores certain information about the database on disk.

Impact: The daemon cannot add the new database to the catalog.

User Action: Diagnose and troubleshoot the reported operating system error. Additional information about the issue may be found in the UNIX syslog or Windows Event Log. For UNIX, ensure that the daemon is running as the instance administrator.

711

Data store creation in
progress, try later

Type of Message: Error

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

Impact: You cannot access the database.

User Action: Wait until the database is created. Then, try to reconnect to the database.

712

Unable to lock data store
memory segment, error
os_error_number

1 (EPERM) - indicates that the daemon was started by a user other than the root user on Linux or a user without administrative privileges on Windows. Restart the daemon, as described in "Working with the TimesTen Data Manager Daemon" in the Oracle TimesTen In-Memory Database Operations Guide.

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

714

Log directory attribute
does not match current
value

Type of Message: Error

Cause: The specified log directory for the connection does not match the log directory that was specified when the database was created.

Impact: TimesTen cannot connect to the database and placed a warning for the directory name in conflict in the UNIX syslog or the Windows Event Log.

User Action: Specify a correct LogDir connection attribute and try reconnecting. For more information on the LogDir attribute, see "LogDir" in the Oracle TimesTen In-Memory Database Reference.

715

Unable to access log
directory 'log_directory'.
OS-detected error:
os_error_details

Type of Message: Internal Error

Cause: The path specified in the LogDir attribute is not accessible due to reasons described in os_error_details.

Impact: TimesTen cannot perform the requested connect or disconnect operation.

User Action: Change the LogDir attribute in the DSN to a valid directory or create the directory as needed. For more information about the LogDir attribute, see "LogDir" in the Oracle TimesTen In-Memory Database Reference.

716

Undo of dead connection
failed

Type of Message: Internal Error

Cause: TimesTen returns this error in the daemon log. TimesTen cannot recover after a user application was terminated abruptly.

Impact: The database is unloaded from memory.

User Action: You should not exit from a TimesTen application before all connections are disconnected. Use signal handlers to catch signals that set a variable indicating that all connections must disconnect. Contact TimesTen Customer Support.

717

Update of data store catalog
entry failed

Type of Message: Error

Cause: The TimesTen main daemon failed to update the DBI file in the daemon home directory to indicate a change in the meta-information about a database. Common causes for this are:

- Your file system is full.

- Ownership of the DBI file has changed.

Impact: The database cannot be accessed.

User Action: Check that your file system is not full. Also, check that file permission and ownership of the DBI file is correct. If the problem persists, contact TimesTen Customer Support.

720

Permission denied while
opening directory
directory_name

Permissions are not set correctly on the specified directory. Ensure that the directory has read and execute permissions for the TimesTen application.

721

No such directory:
directory_name

The specified directory does not exist. Create that directory, or specify another one.

722

Log flusher reports error
error_number (error)

The log manager was not able to flush the log due to operating system error.

723

Log cursor is not open

Internal error. Contact TimesTen Customer Support.

724

Log cursor has no current
position

Internal error. Contact TimesTen Customer Support.

725

Log cursor is
unpositioned

Internal error. Contact TimesTen Customer Support.

726

Log cursor is at end of
log

Internal error. Contact TimesTen Customer Support.

743

Action is not permitted

Type of Message: Error

Cause: You attempted to perform an action that is not supported by TimesTen.

Impact: TimesTen cannot perform the attempted action.

User Action: None.

744

Additional log data may exist
after last valid log record
(lsn log_file_number.log_file_offset)

Type of Message: Error

Cause: TimesTen recovered from an operating system failure or an external event that corrupted one or more log files.

Impact: Recovery has encountered log data after the last complete and intact log record, which suggests that one or more log records may have been lost.

User Action: Recover the database from a backup or failover to a standby node. For additional help, contact TimesTen Customer Support.

745

Log file file contains
partial log block (log file
length = log_file_length)

Type of Message: Error

Cause: TimesTen recovered from an operating system failure or an external event that corrupted one or more log files.

Impact: Recovery has encountered a log file that ends with a partial log block, which suggests that one or more log records may have been lost.

User Action: Recover the database from a backup or failover to a standby node. For additional help, contact TimesTen Customer Support.

746

Extra log files found after
end of log (log_file_offset
files, starting with
log_file_number)

Type of Message: Error

Cause: TimesTen recovered from an operating system failure or an external event that corrupted one or more log files.

Impact: Recovery has encountered log files after the file containing the last complete and intact log record, which suggests that one or more log records may have been lost.

User Action: Recover the database from a backup or failover to a standby node. For additional help, contact TimesTen Customer Support.

747

Log read encountered
incomplete log record at
location
log_record.log_number

Type of Message: Error

Cause: TimesTen recovered from an operating system failure or an external event that corrupted one or more log files.

Impact: Recovery has encountered an incomplete log record after the logical end of the log, which suggests that one or more log records may have been lost.

User Action: Recover the database from a backup or failover to a standby node. For additional help, contact TimesTen Customer Support.

748

Log ended unexpectedly at LSN
log_file_number.log_file_offset;
recovery terminated

Type of Message: Error

Cause: TimesTen recovery encountered a defective log record at the specified LSN, and the LogAutoTruncate attribute is set to 0.

Impact: TimesTen terminated recovery. Checkpoint and transaction log files remain unmodified.

User Action: If possible, diagnose and troubleshoot the problem. Otherwise, contact TimesTen Customer Support. Do not modify or remove any TimesTen checkpoint or transaction log file without first creating a backup copy of the file. For more information on the LogAutoTruncate attribute, see "LogAutoTruncate" in the Oracle TimesTen In-Memory Database Reference.

749

Invalid log block found at
location log_file_number.log_file_offset
-- details: error_description

Internal error. Contact TimesTen Customer Support.

750

Log read encountered log
record with incorrect LSN at
location
log_file_number.log_file_offset
-- remainder of log ignored

Type of Message: Error

Cause: TimesTen encountered an unexpected value while reading the log. The transaction log corruption is likely the result of a crash affecting the disk controller.

Impact: During recovery, the transaction log is effectively truncated at the point of the unexpected value, and the operation continues. Depending on the position of the error, some logged information may be lost. It is extremely unlikely that durable commits are lost, but it is possible on some operating systems.

User Action: If this error is encountered at any time other than recovery, is not the result of a crash that you believe may have affected the disk controller, or if you are concerned that durably committed information may have been lost, contact TimesTen Customer Support.

751

Log read encountered log
record with bad length at
location
log_file_number.log_file_offset
-- remainder of log ignored

Type of Message: Error

Cause: TimesTen encountered an unexpected value while reading the log. The transaction log corruption is likely the result of a crash affecting the disk controller.

Impact: During recovery, the transaction log is effectively truncated at the point of the unexpected value, and the operation continues. Depending on the position of the error, some logged information may be lost. It is extremely unlikely that durable commits are lost, but it is possible on some operating systems.

User Action: If this error is encountered at any time other than recovery, is not the result of a crash that you believe may have affected the disk controller, or if you are concerned that durably committed information may have been lost, contact TimesTen Customer Support.

752

Log read encountered log
record with bad type at
location
log_file_number.log_file_offset
- remainder of log ignored

Type of Message: Error

Cause: TimesTen encountered an unexpected value while reading the transaction log. The transaction log corruption is likely the result of a crash affecting the disk controller.

Impact: During recovery, the transaction log is effectively truncated at the point of the unexpected value, and the operation continues. Depending on the position of the error, some logged information may be lost. It is extremely unlikely that durable commits are lost, but it is possible on some operating systems.

User Action: If this error is encountered at any time other than recovery, is not the result of a crash that you believe may have affected the disk controller, or if you are concerned that durably committed information may have been lost, contact TimesTen Customer Support.

754

Cannot open log copy file
file_name.  OS-detected
error: error_details

Internal error. Contact TimesTen Customer Support.

755

Cannot chmod log copy file
file_name.  OS-detected
error: error_details

Internal error. Contact TimesTen Customer Support.

756

Cannot write to log copy
file file_name: error_details

Internal error. Contact TimesTen Customer Support.

759

Log file file_name has
invalid file header --
details: error_description

Internal error. Contact TimesTen Customer Support.

760

Attempt to read past the
end of the log; LSN =
log_file_number.log_file_offset

Internal error. Contact TimesTen Customer Support.

761

Cannot determine size of
log file file_name.
OS-detected error:
error_details

Internal error. Contact TimesTen Customer Support.

762

Invalid log truncation LSN
log_file_number.log_file_offset

Internal error. Contact TimesTen Customer Support.

763

Cannot truncate log file
file_name. OS-detected error
error_details

Internal error. Contact TimesTen Customer Support.

764

Cannot move away log file
file_name. OS-detected error:
error_details

Internal error. Contact TimesTen Customer Support.

765

Cannot create log file copy
directory. OS-detected error
error_details

Internal error. Contact TimesTen Customer Support.

766

Cannot create log reserve
file file_name. OS-detected
error error_details

The log manager was not able to create reserved log space due to operating system error.

767

Cannot chmod log reserve
file. OS-detected error
error_details

Internal error. Contact TimesTen Customer Support.

768

Cannot determine size of
log reserve file file_name.
OS-detected error:
error_details

Internal error. Contact TimesTen Customer Support.

769

Log reserve file has
invalid size value

Internal error. Contact TimesTen Customer Support.

770

Cannot open log reserve
file file_name.  OS-detected
error: os_error_details

Internal error. Contact TimesTen Customer Support.

771

Cannot write log reserve
file file_name. OS-detected
error: os_error_details

Internal error. Contact TimesTen Customer Support.

772

Cannot seek in log reserve
file file_name.  OS-detected
error: os_error_details

Internal error. Contact TimesTen Customer Support.

773

Cannot sync log reserve
file file_name. OS-detected
error: os_error_details

Internal error. Contact TimesTen Customer Support.

774

Cannot close log reserve
file.  OS-detected error:
os_error_details

Internal error. Contact TimesTen Customer Support.

775

Cannot delete log reserve
file file.  OS-detected
error: os_error_details

Internal error. Contact TimesTen Customer Support.

776

Cannot rename log reserve
file; old name =
old_file_name; new name =
new_file_name.
OS-detected error:
error_details

Internal error. Contact TimesTen Customer Support.

777

Log reserve exhausted

Internal error. Contact TimesTen Customer Support.

778

Log write failed because
filesystem is full;
transaction must rollback

Type of Message: Error

Cause: The file system that holds the transaction log directory is full.

Impact: If your application has AUTOCOMMIT set to 0, your application must rollback the transaction. If your application has AUTOCOMMIT set to 1, the command fails and the application has no further responsibilities.

User Action: You must terminate your transaction. For more information, see "Transaction autocommit behavior" in the Oracle TimesTen In-Memory Database Operations Guide.

779

Request denied; transaction
must rollback because log
filesystem is full

Type of Message: Error

Cause: TimesTen is not accepting new requests for the transaction because error 778 was previously issued.

Impact: TimesTen denied the request and performed a rollback of the transaction.

User Action: None. For more information, see error 778.

780

Log file file_name not
found

Internal error. Contact TimesTen Customer Support.

781

Cannot sync log file.
OS-detected error:
error_details

Internal error. Contact TimesTen Customer Support.

782

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

Internal error. Contact TimesTen Customer Support.

783

Cannot sync log file even
after retrying for number
msec. OS-detected error:
error_details

Internal error. Contact TimesTen Customer Support.

784

Log record type is
disallowed at this time

Internal error. Contact TimesTen Customer Support.

785

No log record exists at LSN
log_file_number.log_file_offset

Internal error. Contact TimesTen Customer Support.

786

Cannot truncate log reserve
file file_name.  OS-detected
error: error_details

The log manager was not able to maintain reserved log space due to operating system error.

787

Log file size exceeds
maximum size of size MB

Type of Message: Error

Cause: The transaction log file size exceeds the maximum defined size for TimesTen.

Impact: TimesTen could not set the specified value for the LogFileSize attribute.

User Action: Set the transaction log file size to a smaller value than the maximum allowed limit. For more information, see "LogFileSize" in the Oracle TimesTen In-Memory Database Reference.

788

Log file size less than
minimum size of size MB.

Type of Message: Error

Cause: The transaction log file size is less than the minimum size allowed by TimesTen.

Impact: TimesTen could not set the specified value for the LogFileSize attribute.

User Action: Set the transaction log file size to a bigger value than the minimum allowed limit. For more information, see "LogFileSize" in the Oracle TimesTen In-Memory Database Reference.

789

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

Type of Message: Error

Cause: You specified a value for the LogFileSize first connection attribute that is less than the minimum allowed value.

Impact: TimesTen cannot create or connect to the database.

User Action: Set the LogFileSize attribute to at least the specified value, eight times the value of the LogBufParallelism attribute, in the odbc.ini file for UNIX or in the ODBC Data Source Administrator for Windows. For more information on the LogFileSize attribute, see "LogFileSize" in the Oracle TimesTen In-Memory Database Reference.

790

Incomplete write to log
file file_name. OS-detected
error: os_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 the description of error 902 for more information.

791

Cannot communicate with
subdaemon

Type of Message: Error

Cause: The TimesTen subdaemon is not running.

Impact: TimesTen could not connect to or disconnect from a subdaemon.

User Action: Restart the TimesTen daemon once all applications have disconnected from the database. For more information on how to start the daemon, see "Working with the TimesTen Data Manager Daemon" in the Oracle TimesTen In-Memory Database Operations Guide.

792

Attempt to read from log
file file_name truncated;
bytes_read num_bytes bytes
read

Unable to read all bytes from the log. Internal error. Contact TimesTen Customer Support.

793

No idle subdaemons

Type of Message: Error

Cause: TimesTen does not have any idle subdaemons available.

Impact: You cannot connect to the database.

User Action: Increase the maximum number of subdaemons that the TimesTen daemon may spawn in the ttendaemon.options file. For more information, see "Changing the allowable number of subdaemons" in the Oracle TimesTen In-Memory Database Operations Guide.

794

Thread join failed

Internal error. Contact TimesTen Customer Support.

795

Protocol failure

Internal error. Contact TimesTen Customer Support.

796

Failed to initialize
procedure procedure_name
with arguments/results
argument/result_list

Internal error. Contact TimesTen Customer Support.

797

Two threads using a single
context

Type of Message: Error

Cause: This error is issued by the debug version of the library.

Impact: None.

User Action: Contact TimesTen Customer Support.

798

Daemon reports error
error_number

Daemon encountered a problem while TimesTen was creating a database, connecting to a database, disconnecting from a database or destroying a database.

799

Unable to connect to
daemon; check daemon status

Type of Message: Error

Cause: You attempted to create, connect, or destroy a database while the TimesTen daemon is not running.

Impact: The operation was not successful.

User Action: Start the daemon with the ttDaemonAdmin -start utility. For more information on the ttDaemonAdmin utility, see "ttDaemonAdmin" in the Oracle TimesTen In-Memory Database Reference.

800

Too many errors - error
buffer overflow

The number of errors pushed onto the error buffer exceeds the maximum of 50.

801

Malloc (C library) failed

Unable to allocate memory for TimesTen internal data structures.

802

Database type_of_space space
exhausted

Type of Message: Error

Cause: TimesTen cannot allocate memory from the heap. An additional error message indicates which memory region is full.

Impact: The database cannot continue normal operations.

User Action: Increase the size of the appropriate memory region by modifying the set value for the PermSize or the TempSize attribute. You must unload the database from memory for changes in the PermSize or the TempSize attribute to take effect. For more information on how to unload the database from memory, see "Unloading the database from memory" in the Oracle TimesTen In-Memory Database Operations Guide. For more information on the PermSize or the TempSize attribute, see "PermSize" or "TempSize", respectively, in the Oracle TimesTen In-Memory Database Reference.

803

Name length exceeds
char_limit characters

Type of Message: Error

Cause: You specified an identifier or user name that exceeds the maximum number of characters allowed for basic names.

Impact: TimesTen cannot create the specified identifier or user name.

User Action: Select an identifier or user name within the allowed length for basic names. For more information on the number of characters allowed for basic names, see "System Limits" in the Oracle TimesTen In-Memory Database Reference. For more information on the creation of identifiers or user names, see "Creating or identifying users to the database" in the Oracle TimesTen In-Memory Database Operations Guide.

804

Internal error: unknown
error code error_string

Internal error. Contact TimesTen Customer Support.

805

operation_name has not been
implemented

Operation is recognized by the parser but its functionality is not currently available.

806

Garbage left on heap

Internal error. Contact TimesTen Customer Support.

807

Null pointer argument

Internal error. Contact TimesTen Customer Support.

808

Operation not atomic
(failed and not undone)

Type of Message: Error

Cause: Operation was not rolled back because logging was not enabled.

Impact: Database may be inconsistent and may not be recoverable.

User Action: You can try dumping and reloading the database using the ttBulkCp utility. You can also attempt the operation again with logging turned on (Logging=1). For more information about the ttBulkCp utility, see "ttBulkCp" in the Oracle TimesTen In-Memory Database Reference.

809

Heap page directory
overflow - cannot allocate
space

This error indicates that the database's allocation structures are full. Try freeing any items possible or compacting the database, using ttCompact, and retrying the operation. Disconnecting all connections and reconnecting may also free up some space. For more information about the ttCompact built-in procedure, see "ttCompact" in the Oracle TimesTen In-Memory Database Reference.

810

Pointer does not reference
the data store

Internal error. Contact TimesTen Customer Support.

812

Platform not supported
platform

Type of Message: Error

Cause: Some characteristics of your system (that is, alignments, type sizes) do not match the expected values, this indicates an installation error. Common causes for this are: - The TimesTen installation was copied directly from another system. - The TimesTen installation is on a network or shared drive, and that installation was installed by a system with different characteristics than your actual system.

Impact: TimesTen cannot run on your system until the installation issue is resolved.

User Action: Reinstall TimesTen. For more information, see Oracle TimesTen In-Memory Database Installation Guide.

814

Size specified by
'attribute' connection
attribute is less than the
minimum size of
megabyte_count megabytes

Type of Message: Error

Cause: The specified PermSize or TempSize value is less than the allowed minimum.

Impact: TimesTen cannot create the database or failed to establish a connection to the database.

User Action: Increase the value for the PermSize or TempSize attribute, or both, to at least the minimum size indicated. For more information on defining DSNs, see "Defining DSNs for direct or client/server connections" in the Oracle TimesTen In-Memory Database Operations Guide. For more information on the PermSize attribute, see "PermSize" in the Oracle TimesTen In-Memory Database Reference. For more information on the TempSize attribute, see "TempSize" in the Oracle TimesTen In-Memory Database Reference.

817

Internal error - TimesTen
initialization failed

Internal error. Contact TimesTen Customer Support.

818

Sum of permanent and
temporary region sizes (size
MB) exceeds maximum size
(max_size MB) allowed on this
platform

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.
OS error: 'os_error_number'.
Consider connecting with
Overwrite=1 to create new
data store

Type of Message: Error

Cause: TimesTen attempted to connect to a database that has been deleted and where both checkpoint files are missing.

Impact: TimesTen cannot connect to the specified database.

User Action: Connect to the database with the Overwrite attribute set to 1 in the connection string to create a new database. For more information on the Overwrite attribute, see "Overwrite" in the Oracle TimesTen In-Memory Database Reference.

823

Compact operation not fully
completed

This warning is issued when a compaction operation cannot complete. Additional errors that are pushed should indicate the reason for the failure. For example, the failure could be caused by an out-of-disk error.

824

Error information lost.
Operation was at line
number

The operation failed, but error information was lost. Contact TimesTen Customer Support regarding this lost error information.

826

Temporary data store exists
but is unattached

Type of Message: Error

Cause: TimesTen cannot connect to a temporary database (Temporary attribute set) that is not attached to an application process.

Impact: TimesTen cannot create or connect to the specified database.

User Action: Destroy the temporary database with the ttDestroy utility, or set the AutoCreate and Overwrite attributes to 1 to overwrite the database. For more information on temporary databases, see "Temporary" in the Oracle TimesTen In-Memory Database Reference. For more information on the AutoCreate or Overwrite attribute, see "AutoCreate" or "Overwrite", respectively, in the Oracle TimesTen In-Memory Database Reference. For more information on the use of the ttDestroy utility, see "ttDestroy" in the Oracle TimesTen In-Memory Database Reference.

829

Bad options: Cannot copy
logging options if first
connection

Type of Message: Error

Cause: The MatchLogOpts attribute is set to 1.

Impact: TimesTen cannot create or connect to the database.

User Action: For UNIX, set the MatchLogOpts attribute to 0 in the odbc.ini file. For Windows, uncheck the Match Log Opts check box in the Windows ODBC Data Source Administrator. For more information on the MatchLogOpts attribute, see "MatchLogOpts" in the Oracle TimesTen In-Memory Database Reference.

830

Cannot create data store
file. OS-detected error:
error_text

Type of Message: Error

Cause: TimesTen is unable to overwrite an existing database or create the database checkpoint files because of an operating system error.

Impact: You cannot create the database.

User Action: Diagnose and troubleshoot the operating system error.

831

Cannot change mode on 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.

832

Cannot open data store file
for reading. OS-detected
error: error_details

Unable to open the database file for reading during a database connection operation because of an operating system error such as file system permission problems.

833

Data store data_store_name
not found

Type of Message: Error

Cause: You attempted to destroy the specified database from the odbc.ini file. However, the specified database has already been destroyed or was never created.

Impact: TimesTen cannot destroy the specified database.

User Action: Verify the database name and retry the operation.

834

Data store file invalid or
corrupted

Type of Message: Error

Cause: During recovery or a database connection operation the database file was found to be corrupted.

Impact: You cannot use the TimesTen database.

User Action: Recover the database from a backup or failover to a standby node. For more information, see "General failover and recovery procedures" in the Oracle TimesTen In-Memory Database Replication Guide. For additional help, contact TimesTen Customer Support.

835

Data store file file_name
reflects unfinished
checkpoint

Type of Message: Error

Cause: Either the application failed when writing the checkpoint or that there was not sufficient disk space to store the checkpoint.

Impact: TimesTen cannot recover from the specified database file because the file is incomplete. Generally a connection is still possible when you receive this error because TimesTen saves two different checkpoints.

User Action: Ensure that there is sufficient disk space to store the checkpoint and retry creating the checkpoint. For more information, see "Check transaction log file use of disk space" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

836

Cannot create data store
shared memory segment, error
os_error_number

Type of Message: Error

Cause: Unable to create a shared memory segment during a database creation or database connection operation.

On UNIX or Linux systems, the shmget call can receive UNIX error EINVAL due to an inability to allocate a shared memory segment of the requested size. Common causes for this are:

- The daemon is configured to use huge pages but huge pages are not configured or unavailable (under configured or being used by another process) on the system.

- The operating system denies the request because the kernel parameters shmmax or shmall are set too low.

- The configured swap space is insufficient for the requested shared memory segment. It is possible that some UNIX or Linux systems have additional possible causes for the error. The shmget man page lists the possibilities.

Impact: You may be unable to connect to the database or load it into memory.

User Action: Diagnose and troubleshoot the operating system error. For more information see "Manage semaphores and shared memory segments" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

837

Cannot attach data store
shared memory segment, error
os_error_number

Type of Message: Error

Cause: Unable to attach the database to the shared memory segment.

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.

Impact: You may be unable to connect to the database or load it into memory.

User Action: Diagnose and troubleshoot the operating system error. For more information see "Manage semaphores and shared memory segments" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

838

Cannot get data store
shared memory segment, error
os_error_number

Type of Message: Error

Cause: Unable to access a shared memory segment during a database creation or database connection operation.

On UNIX or Linux systems, the shmget call can receive UNIX error EINVAL due to an inability to allocate a shared memory segment of the requested size. Common causes for this are:

- The daemon is configured to use huge pages but huge pages are not configured or unavailable (under configured or being used by another process) on the system.

- The operating system denies the request because the kernel parameters shmmax or shmall are set too low.

- The configured swap space is insufficient for the requested shared memory segment. It is possible that some UNIX or Linux systems have additional possible causes for the error. The shmget man page lists the possibilities.

Impact: You may be unable to connect to the database or load it into memory.

User Action: Diagnose and troubleshoot the operating system error. For more information see "Manage semaphores and shared memory segments" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

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.

Type of Message: Error

Cause: TimesTen is unable to overwrite an existing database because a database with the same DSN is in use, or loaded into RAM, or both.

Impact: You cannot create the database.

User Action: Before you can overwrite an existing database, you must first unload the database from memory, close all active connections, set the RAM policy of the database to manual or inUse, or a combination of all of the above.

- To unload the database from memory, use the ttStatus utility to find processes connected to the database and stop them. Then use the -ramUnload option of the ttAdmin utility to unload the database from memory. For more information on the ttAdmin or ttStatus utility, see "ttAdmin" or "ttStatus", respectively, in the Oracle TimesTen In-Memory Database Reference.

- To set the RAM policy to manual or inUse, see "Specifying a RAM policy" in the Oracle TimesTen In-Memory Database Operations Guide.

- If you do not want to overwrite an existing database, set the Overwrite attribute to 0. For more information on the Overwrite attribute, see "Overwrite" in the Oracle TimesTen In-Memory Database Reference.

840

Cannot allocate space
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 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
os_error_number

Type of Message: Internal Error

Cause: Unable to detach a shared memory segment during a disconnect from database operation.On UNIX or Linux systems, the shmdt call can receive UNIX error EINVAL. Common causes for this are:

- There is no shared memory segment attached at shmaddr.

- shmaddr is not aligned on a page boundary. It is possible that some UNIX or Linux systems have additional possible causes for the error. The shmdt man page lists the possibilities.

Impact: The process that encounters this error is still attached to the shared memory segment. This may be problematic if this process is still running when an attempt is made to release the shared memory segment back to the operating system.

User Action: Contact TimesTen Customer Support.

842

Invalid data store
identifier

Internal error. Contact TimesTen Customer Support.

843

query/feature is not
supported

The requested type of query is not supported.

844

Cannot write data store
file file_name. OS-detected
error: error_details

Unable to write to the database file during creation of a database or initiation of a checkpoint, most likely due to a lack of disk space.

845

Cannot read data store
file. OS-detected error:
error_details

Unable to read the database file during a database connection operation.

846

Data store connection
invalid or not current

To execute the current operation, an existing valid database connection was expected but not detected.

847

Cannot open data store file
for writing. OS-detected
error: error_details

Unable to open a database file for writing during an initiation of a checkpoint because of an operating system error such as file system permission problems.

848

Recovery failed on number
sets of data store files;
the TimesTen error log has
more information

Type of Message: Error

Cause: Recovery failed on one or more checkpoint files. The user error log contains warning messages that indicate where the problem occurred.

Impact: Review the warning messages in the user error log for possible impacts on the system.

User Action: Recover the database from a backup or failover to a standby node. For more information, see "General failover and recovery procedures" in the Oracle TimesTen In-Memory Database Replication Guide. For additional help, contact TimesTen Customer Support.

849

Recovery failed on number
sets of data store files;
try connecting with a larger
data store size

Type of Message: Error

Cause: Recovery failed on one or more checkpoint files. During recovery, the database ran out of available disk space.

Impact: The database cannot continue normal operations.

User Action: Increase the value of the PermSize attribute so that your database has at least five percent available space on the permanent memory region. For more information on how to check the amount of memory in use by the database, see "Check the amount of memory allocated to the database" in the Oracle TimesTen In-Memory Database Troubleshooting Guide. For more information on how to increase the value of PermSize, see "Specifying the size of a database" in the Oracle TimesTen In-Memory Database Operations Guide. If you increase the PermSize attribute and still receive this error, contact TimesTen Customer Support.

850

Application has existing
connection to 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: 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.

852

Unable to lock data store
memory segment, error
error_number ...continuing
with connection...

The system was unable to lock memory, but the error was ignored as per the MemoryLock attribute value.

1 - indicates that the daemon was started by a user other than the instance administrator. Restart the daemon as the instance administrator.

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

854

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

857

Invalid flags for heap
creation

Internal error. Contact TimesTen Customer Support.

860

Invalid savepoint

Internal error. Contact TimesTen Customer Support.

862

Number of active
transactions exceeds the
maximum

Internal error. Contact TimesTen Customer Support.

863

Operation requires an
active transaction

Type of Message: Error

Cause: When encountered during LOB operations, this error means the LOB reference has been invalidated due to transaction commit or rollback.

Impact: The operation you attempted failed.

User Action: In non-LOB contexts, this is an internal error. Contact TimesTen Customer Support in this case.

864

Operation prohibited with
an active transaction.

Internal error. Contact TimesTen Customer Support.

865

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

Unable to destroy the log file during a database creation, database connection or destroy database operation because of an operating system error.

867

Cannot flush file buffers
to disk. OS-detected error
error_details

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

868

Cannot open directory
directory_name for
reading. OS-detected error:
error_details

While attempting to open the specified directory, the operating system encountered an error. Check the OS error message.

870

Cannot close data store
shared memory segment, error
error_number

Warning: Unable to close shared memory segment handle after detaching the segment.

871

Column column_name cannot
be set to null

Cannot insert a NULL value into a non-nullable column or field. Check the input values and retry.

872

Length of inline columns
(value) exceeds limit
maximum_value

Length of the inline columns exceeds the maximum limit. Decrease the number or length of the columns in the table (only length of non-variable types matters). For more information on system limits, see "System limits and defaults" in the Oracle TimesTen In-Memory Database Reference.

875

Invalid or missing column
number in column descriptor

Internal error. Contact TimesTen Customer Support.

876

Overlapping columns in
column descriptor

Internal error. Contact TimesTen Customer Support.

877

Misaligned columns in
column descriptor

Internal error. Contact TimesTen Customer Support.

878

Invalid column number

Type of Message: Internal Error

Cause: Column number is not valid. Note that column numbers start at 1 (not 0).

Impact: The operation you attempted failed.

User Action: Contact TimesTen Customer Support.

879

Table owner.table has
existing primary index

Internal error. Contact TimesTen Customer Support.

880

Cannot create index; table
has maximum of max_indexes
indexes

Type of Message: Error

Cause: You attempted a CREATE INDEX statement on a table that has reached the maximum number of indexes per table.

Impact: TimesTen cannot perform the operation.

User Action: Consider using the DROP INDEX statement to remove an existing index that you no longer use from the table and retry the operation. For more information on CREATE INDEX, see "CREATE INDEX" in the Oracle TimesTen In-Memory Database SQL Reference. For more information on DROP INDEX, see "DROP INDEX" in the Oracle TimesTen In-Memory Database SQL Reference.

881

Hash key and primary key
columns must be identical

For a hash table, the columns of the hash key must be the same as the columns of the primary key.

882

Primary index must be unique

Internal error. Contact TimesTen Customer Support.

883

Index has open cursors

Cannot insert into, delete from or destroy an index that has open cursors on it.

884

Invalid hash index

Internal error. Contact TimesTen Customer Support.

885

Invalid T-tree index
index_name

Internal error. Contact TimesTen Customer Support.

886

Index operation unsupported

Internal error. Contact TimesTen Customer Support.

887

Table has no primary index

Internal error. Contact TimesTen Customer Support.

888

Tail log truncated at
position n.n. (where n is a
long integer)

Type of Message: Error

Cause: Recovery was unable to read the log past the specified LSN.

Impact: The log was truncated at that point to allow recovery to continue.

User Action: You may want to review the original pre-truncated log file. This log file can be found in a directory called savedLogFiles, which is a subdirectory of the log directory of the database.

889

Number of log files
exceeded the maximum

Cannot create a transaction log file because the number of transaction log files that currently exists is at the maximum of 9,999. Roll back and perform a checkpoint. See "Checkpoint operations" in the Oracle TimesTen In-Memory Database Operations Guide.

890

Log file name too long

Internal error. Contact TimesTen Customer Support.

891

Log file file_name already
exists

Internal error. Contact TimesTen Customer Support.

892

Cannot create log file file.
OS-detected error:
os_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: os_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:
os_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:
os_error_number

Internal error. Contact TimesTen Customer Support.

896

Cannot read log file
file_name. OS-detected
error: os_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:
os_error_details

Internal error. Contact TimesTen Customer Support.

898

Log record exceeds maximum
size of log file

Internal error. Contact TimesTen Customer Support.

899

Log buffer size exceeds
maximum size of
maximum_size MB

Type of Message: Error

Cause: You have specified a log buffer size value that exceeds the log buffer size limit. For more information on the log buffer size limit, see "LogBufMB" in the Oracle TimesTen In-Memory Database Reference.

Impact: You cannot create or connect to the database.

User Action: Call the ttConfiguration built-in procedure to check the current value of LogBufMB. If the current value of LogBufMB exceeds the log buffer size limit, modify the value of LogBufMB to a supported value. For more information on ttConfiguration, see "ttConfiguration" in the Oracle TimesTen In-Memory Database Reference. For more information on modifying the value of LogBufMB, see "LogBufMB" in the Oracle TimesTen In-Memory Database Reference.

900

Cannot generate temporary
file name

Internal error. Contact TimesTen Customer Support.

901

Cannot create file
file_name for reclaim
records: OS-detected error:
os_error_details

Unable to create a temporary file to be used to spool the headers of reclaimed log records.

902

Cannot write file file_name
for reclaim records:
OS-detected error:
os_error_details

Unable to write to the temporary file used to spool the headers of reclaimed transaction log records. Ensure that there is enough space on the disk where your temporary directory resides or change the location of your temporary directory by setting the TMP environment variable on Windows or the TMPDIR environment variable on UNIX. To avoid writing this file all together, each transaction should limit the number of deleted rows, deleted varying-length data and updated varying-length data. In particular, the total of (number of deletes) + (number of deletes to varying-length data) + (number of updates to varying-length data) should be limited to 90, to avoid writing to this file.

903

Cannot seek in file file_name
for reclaim records:
OS-detected error:
os_error_details

Internal error. Contact TimesTen Customer Support.

904

Cannot read file file_name
for reclaim records:
OS-detected error:
os_error_details

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

905

Invalid index identifier

Internal error. Contact TimesTen Customer Support.

906

Cannot change mode on
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 Customer Support.

908

Key not found in object_name

Internal error. Contact TimesTen Customer Support.

909

Cannot update primary key
or hash key

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

910

Row has already been
deleted

A transaction is trying to delete or update a row that it has already deleted.

911

Null or blank table name

During table creation, no name was provided for the table.

912

Row with ID not found in
table

Internal error. Contact TimesTen Customer Support.

913

MaxCnt exceeds limit

Internal error. Contact TimesTen Customer Support.

914

table is not a valid
table name

The length of the table name exceeds its maximum of 30 characters.

916

Key column must be
not-null

Cannot insert a NULL value into a key column.

917

Invalid column number for key

The column number of the table that is specified as a key column is invalid.

918

Key column count is zero or
greater than the number of
table columns

The number of key columns is either zero or exceeds the number of columns in the table.

919

Invalid comparison condition

Internal error. Contact TimesTen Customer Support.

920

Invalid default value for
column column_name

The specified default value is not a constant or one of the allowed values, NULL was specified for a non-nullable column or the default data type is not compatible with that of the column. 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 Customer Support.

923

Invalid row implementation

Internal error. Contact TimesTen Customer Support.

924

Row implementation
unsupported for operation

Internal error. Contact TimesTen Customer Support.

925

Cannot create data store
semaphores error_info

Type of Message: Error

Cause: Unable to create a semaphore during a database creation or database connection operation. This error usually indicates that your system is not tuned for TimesTen.

Impact: Cannot create database semaphores.

User Action: Tune your system for TimesTen. For more information, see "Installation prerequisites" in the Oracle TimesTen In-Memory Database Installation Guide.

926

Cannot create data store
latch (error_number, info
extra_info

Type of Message: Error

Cause: On Windows, there is a shortage of system resources such as "named events."

Impact: Cannot create database latch.

User Action: End any stray processes that are running. If that does not help, restart the system. If the problem persists, contact TimesTen Customer Support.

927

Cannot open data store
semaphore (number) number

Type of Message: Error

Cause: On Windows, there is a shortage of system resources such as "named events."

Impact: Cannot open the database semaphore.

User Action: End any stray processes that are running. If that does not help, restart the system. If the problem persists, contact TimesTen Customer Support.

928

Error in semaphore
operation
(error error_number)

Type of Message: Error

Cause: An operating system semaphore operation failed.

Impact: The severity of the impact is unknown and requires additional diagnosis.

User Action: Contact TimesTen Customer Support.

931

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 or column name involved.

933

Invalid SQL string

SQL string is NULL.

934

Invalid binary string

A SQL statement has a binary string constant that is larger than 20,000 characters. To get around this limitation, specify the binary value as a parameter. Then, it can be bound to a program variable of arbitrary length.

935

SQL statement must return a
result

Internal error. Contact TimesTen Customer Support.

936

SQL statement may return
multiple results

Internal error. Contact TimesTen Customer Support.

937

Invalid compiled command
 number

Internal error. Contact TimesTen Customer Support.

938

SQL statement has
arguments

Internal error. Contact TimesTen Customer Support.

939

SQL statement has no
arguments

Internal error. Contact TimesTen Customer Support.

940

SQL command has too many
results

A maximum of 32,767 projected expressions are allowed for a single SELECT statement. This includes all columns referenced indirectly by any * expressions.

941

Execution of operation not
possible -- dependent object
(e.g. command or index) is
in use.

The application is currently scanning the table or a corresponding index, so it cannot perform operations such as creating an index, dropping the table or dropping an index. The application must wait until scanning is complete.

942

Imprecise numeric coercion

Warning: unable to convert a numeric value from one type to another without losing precision.

943

MaxTups argument must be
positive

Internal error. Contact TimesTen Customer Support.

946

SQL command is no longer
valid

Type of Message: Error

Cause: The command has been invalidated. This may happen as the result of some DDL operations, such as ALTER TABLE, CREATE INDEX, DROP INDEX, or a modification of optimizer statistics. TimesTen cannot re-prepare the command.

Impact: In some cases, TimesTen attempts to re-prepare the command. In other cases, such as if a table has been dropped and re-created, TimesTen does not attempt to re-prepare the command.

User Action: Restart your application. If you still receive this error, attempt to re-prepare the command.

947

Cannot generate log file
name

A failure occurred generating a name for the log file. Additional errors are returned indicating the reason for this failure.

948

Read log buffer size
specified is too small or
too large

Internal error. Contact TimesTen Customer Support.

950

Invalid format width

Internal error. Contact TimesTen Customer Support.

951

Invalid float precision

The precision of a float type cannot be negative.

952

Null string too long -
value will be truncated

Internal error. Contact TimesTen Customer Support.

954

SQL command has mismatched
version number

Internal error. Contact TimesTen Customer Support.

955

Current Connections
attribute setting (setting)
exceeded by this connection.

Type of Message: Error

Cause: You attempted to connect to a database that has reached the maximum number of user-specified concurrent connections.

Impact: You cannot connect to the database.

User Action: Modify the value of the Connections attribute to increase the maximum number of user-specified concurrent connections. You can modify this attribute in the odbc.ini file for UNIX or in the ODBC Data Source Administrator for Windows. The database must be unloaded from memory for the change to take effect. For more information on the Connections attribute, see "Connections" in the Oracle TimesTen In-Memory Database Reference.

956

Merge statement cannot
update a primary key

You are attempting to update a primary key through a MERGE statement. This is not supported.

960

String exceeds column width
for column column_name -
value will be truncated

Warning: attempting to insert a string into a character or binary column that is larger than the column's maximum length. The string is truncated.

962

Bad value for parameter

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

963

Internal error writing
checkpoint log record

Type of Message: Internal Error

Cause: An error was encountered while writing the checkpoint log record. A common cause for this is low available disk space on the disk that contains your transaction log files.

Impact: The checkpoint cannot complete. If checkpoints keep failing, database recovery takes longer and transaction log files do not get purged.

User Action: Ensure that there is available disk space on the disk that contains your transaction log files. If the disk is low on space, make more disk space available. For more information, see "Check transaction log file use of disk space" in the Oracle TimesTen In-Memory Database Troubleshooting Guide. Once you have made more disk space available, retry the checkpoint. If you still receive this error, contact TimesTen Customer Support.

965

Specified join order is not
applicable - valid join
orders will be considered

Warning: the specified join order is not applicable and is ignored. All valid join orders are considered.

966

Join string too long - join
order not changed

Warning: the length of the specified join order exceeds the maximum of 1,024, and is ignored. All valid join orders are considered.

967

Bad join string - join
order not changed

The join order set by ttOptSetOrder built-in either has incorrect format and therefore is ignored. The correct format is a list of table names separated by spaces.

968

Invalid index usage
specification

The index usage string provided to the ttOptUseIndex built-in procedure has a syntax error.

969

Index string too long -
default index usage will be
used

The index usage string provided to the ttOptUseIndex built-in procedure is too long.

970

Invalid cursor handle

Internal error. Contact TimesTen Customer Support.

971

Supplied buffer too small

Internal error. Contact TimesTen Customer Support.

972

Invalid data store handle

Internal error. Contact TimesTen Customer Support.

973

Invalid savepoint handle

Internal error. Contact TimesTen Customer Support.

974

Invalid format handle

Internal error. Contact TimesTen Customer Support.

975

Invalid table handle

Internal error. Contact TimesTen Customer Support.

976

Invalid index handle

Internal error. Contact TimesTen Customer Support.

977

Invalid row handle

Internal error. Contact TimesTen Customer Support.

978

Invalid command handle

Internal error. Contact TimesTen Customer Support.

979

Invalid command argument
handle

Internal error. Contact TimesTen Customer Support.

980

Input buffer not properly
aligned

Internal error. Contact TimesTen Customer Support.

981

Invalid cursor type (R/W)

Internal error. Contact TimesTen Customer Support.

982

String exceeds column width
for column column_name

Type of Message: Error

Cause: You attempted to insert a string that exceeds the column width of the specified column.

Impact: TimesTen cannot perform the operation.

User Action: Consider dropping and re-creating the table with the appropriate column width for the specified column or shortening the length of the string to insert.

983

Invalid index or table name
table - default index
usage will be used

The specified table or index was not found. The default index is used.

984

Cannot find index that
matches index_name. This
index usage specification
will be ignored

The specified index was not found. No index specification is used.

985

Application cannot change
statistics on statistics
system tables

Statistics system tables are maintained by the system and cannot be changed by the application.

990

Invalid maxCnt value for table

Internal error. Contact TimesTen Customer Support.

991

Quota exceeds maximum row
count for table

Internal error. Contact TimesTen Customer Support.

992

Number of table pages in
use exceeds quota

Internal error. Contact TimesTen Customer Support.

993

Number of index pages in
use exceeds quota

Internal error. Contact TimesTen Customer Support.

994

Data store connection
terminated. Please reconnect

Type of Message: Error

Cause: An unexpected error or abrupt disconnect (that is, control-C) caused the connection to be terminated.

Impact: The database connection is terminated.

User Action: The application can reconnect once all connections have disconnected. If this error was accompanied by other errors indicating an assertion or unexpected error from the engine, contact TimesTen Customer Support.

995

Cannot destroy data store
shared-memory segment, error
os_error_number

This indicates a failed attempt to remove a shared memory segment. The OS-specific error code given in the message indicates the reason for this failure.

997

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 message
Details

1000

Cannot set primary key
columns to different values

Type of Message: Error

Cause: You attempted to change the value of a primary key column. TimesTen does not support changing the values of primary key columns.

Impact: TimesTen cannot change the value of the primary key column.

User Action: Specify a valid SQL UPDATE statement and retry the operation. For more information about the UPDATE SQL statement, see "UPDATE" in the Oracle TimesTen In-Memory Database SQL Reference.

1001

Syntax error in SQL statement
statement

Type of Message: Error

Cause: The parser detected a syntax error in the specified SQL statement.

Impact: TimesTen cannot perform the SQL operation.

User Action: Correct the SQL syntax and retry the operation. For more information about SQL syntax, see "SQL syntax" in the Oracle TimesTen In-Memory Database SQL Reference. If your SQL syntax is correct, check if you are using a TimesTen SQL reserved word. If you are using a TimesTen SQL reserved word, add quotes around the reserved word or use an alternate identifier. For more information, see "Reserved Words" in the Oracle TimesTen In-Memory Database SQL Reference.

1002

Identifier identifier_name in
SQL statement exceeds maximum
length (length)

Type of Message: Error

Cause: The length of the specified identifier of the SQL statement exceeds the maximum allowed length.

Impact: TimesTen cannot perform the SQL operation.

User Action: Set the identifier to a value that is greater than zero and does not exceed the maximum allowed length. Then, retry the operation.

1004

Identifier in SQL statement
is zero-length

Type of Message: Error

Cause: You specified a SQL statement that is missing an identifier name such as a table name, correlation schema name, host name, etc.

Impact: TimesTen cannot perform the SQL operation.

User Action: Ensure that your SQL statement contains valid identifiers. Then, retry the operation.

1005

Identifier in SQL statement
is all spaces

Type of Message: Error

Cause: You specified a table name or identifier that is all spaces.

Impact: TimesTen cannot perform the SQL operation.

User Action: Specify a valid table name or identifier. Then, retry the operation.

1006

Identifier statement
contains illegal characters

Type of Message: Error

Cause: The specified identifier contains illegal characters. Identifiers can contain only characters from the ASCII character set. TimesTen does not support other characters, such as native language characters, in identifiers.

Impact: TimesTen cannot perform the operation.

User Action: Correct the identifier using only characters from the ASCII character set. Then, retry the operation.

1007

Illegal parameter marker name

Type of Message: Error

Cause: You attempted to use a parameter marker name that is reserved for system use.

Impact: TimesTen cannot perform the operation.

User Action: Use a valid parameter marker name. If you are using a TimesTen SQL reserved word, add quotes around the reserved word or use an alternate identifier. For more information, see "Reserved Words" in the Oracle TimesTen In-Memory Database SQL Reference.

1008

PL/SQL object names cannot
contain lower-case letters
or trailing spaces in the
TimesTen environment

Type of Message: Error

Cause: The PL/SQL program unit name contains lower-case letters or trailing spaces.

Impact: TimesTen cannot create the PL/SQL program unit.

User Action: Specify a valid name for the PL/SQL program unit. Then, retry the operation. For more information, see "Creating and using procedures and functions" in the Oracle TimesTen In-Memory Database PL/SQL Developer's Guide.

1009

Pre-allocated log block found
at location
log_file_number.offset_in_file
-- details: details

Type of Message: Error

Cause: TimesTen found a preallocated log block at the specified location. A common cause for this is that TimesTen is reading past the logical end of a log file.

Impact: The log reading application failed. It is possible that your database is invalidated, but it is unlikely.

User Action: Contact TimesTen Customer Support.

1017

Column number in ORDER BY
clause must be greater than
zero

Type of Message: Error

Cause: You attempted to reference a column number in an ORDER BY clause with a value of zero.

Impact: TimesTen cannot perform the operation.

User Action: Set the column number in the ORDER BY clause to a value greater than zero and retry the operation.

1022

Constant number is outside
representable range

Type of Message: Error

Cause: The specified constant value is out of range for the data type and cannot fit in the buffer.

Impact: TimesTen cannot perform the operation.

User Action: Set a constant value within the supported range and retry the operation. For information on the range of each data type, see "Type specifications" in the Oracle TimesTen In-Memory Database SQL Reference.

1024

Referenced table table_name
not in FROM list

Type of Message: Error

Cause: The referenced table is not specified in the FROM list of the query.

Impact: TimesTen cannot perform the operation.

User Action: Ensure that you specify valid table names and that you specify referenced tables in the FROM list. Then, retry the operation.

1025

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

Type of Message: Error

Cause: You specified a number of column names in the INSERT statement that does not match the number of values of the VALUES clause.

Impact: TimesTen cannot perform the operation.

User Action: Specify a number of column names in the INSERT statement that matches the number of values in the VALUES clause and retry the operation.

1026

Column names must contain at
least one character

Type of Message: Error

Cause: You specified an invalid column name. The name of a column name cannot be blank. The name of a table column is missing.

Impact: TimesTen cannot perform the operation.

User Action: Use at least one character to set the column name and retry the operation. For more information, see "Column Definition" in the Oracle TimesTen In-Memory Database SQL Reference.

1027

Floating-point precision out
of legal range

Type of Message: Error

Cause: You specified a floating-point value that is out of the supported range.

Impact: TimesTen cannot perform the operation.

User Action: Set the floating-point precision to a number that is within the supported range and retry the operation. For more information on FLOAT precision, see "FLOAT and FLOAT(n)" in the Oracle TimesTen In-Memory Database SQL Reference.

1032

Aggregate function cannot be
nested

Type of Message: Error

Cause: You attempted to nest an aggregate function. An aggregate function cannot be called within another aggregate function.

Impact: TimesTen cannot perform the operation.

User Action: Correct the nested aggregate and retry the operation. For more information about aggregate functions, see "Aggregate functions" in the Oracle TimesTen In-Memory Database SQL Reference.

1033

Aggregate function cannot be
specified in group by clause

Type of Message: Error

Cause: You specified an aggregate function in a GROUP BY clause. An aggregate function cannot be called within a GROUP BY clause.

Impact: TimesTen cannot perform the operation.

User Action: Specify a correct GROUP BY clause and retry the operation. For more information about the GROUP BY clause, see "GROUP BY clause" in the Oracle TimesTen In-Memory Database SQL Reference.

1061

PRIMARY KEY syntax can only
be used once in statement

Type of Message: Error

Cause: You specified more than one PRIMARY KEY clause. A table can have at most one PRIMARY KEY column list or constraint.

Impact: TimesTen cannot perform the operation.

User Action: Ensure that your SQL statement only contains one PRIMARY KEY clause. If you are attempting to create a primary key on multiple columns, ensure that all of the columns are specified within the same PRIMARY KEY clause.

For more information, see "Primary keys, foreign keys and unique indexes" in the Oracle TimesTen In-Memory Database Operations Guide.

1102

Stale table handle

Type of Message: Internal Error

Cause: The internal version number of a table does not match the version in an associated table handle.

Impact: TimesTen needs to reacquire the table handle and cannot access the table for the current operation.

User Action: Contact TimesTen Customer Support.

1103

Error in converting sysdate
to Timestamp

Type of Message: Error

Cause: You specified an Oracle database SYSDATE or TimesTen SYSDATE with an invalid TIMESTAMP or DATE value.

Impact: TimesTen cannot convert the value to a TIMESTAMP value.

User Action: Ensure that the Oracle database SYSDATE or TimesTen SYSDATE contains valid TIMESTAMP or DATE values. For more information on datetime data types, see "Datetime data types" in the Oracle TimesTen In-Memory Database SQL Reference.

1104

Unable to obtain current date
and time for SYSDATE

Unable to get the time from the system specific call.

1105

Invalid column reference.

Type of Message: Error

Cause: You specified an invalid column or column list.

Impact: TimesTen cannot perform the operation.

User Action: Specify a valid column or column list.

1106

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

Type of Message: Error

Cause: You specified a CREATE SEQUENCE statement that has a START WITH clause that is not within the defined MINVALUE and MAXVALUE range.

Impact: TimesTen cannot perform the operation.

User Action: Ensure that the START WITH clause is within the specified MINVALUE and MAXVALUE range. Alternatively, modify the MINVALUE and MAXVALUE values so that the START WITH value is within the range.

For more information on the CREATE SEQUENCE statement, see "CREATE SEQUENCE" in the Oracle TimesTen In-Memory Database SQL Reference.

1107

Error converting sysdate to
Date

Type of Message: Error

Cause: You specified an Oracle database SYSDATE or TimesTen SYSDATE with an invalid TIMESTAMP or DATE value.

Impact: TimesTen cannot convert the value to a DATE value.

User Action: Ensure that the Oracle database SYSDATE or TimesTen SYSDATE contains valid TIMESTAMP or DATE values. For more information on datetime data types, see "Datetime data types" in the Oracle TimesTen In-Memory Database SQL Reference.

1108

Error in converting Oracle
rowid to TimesTen rowid.

Type of Message: Error

Cause: TimesTen encountered an invalid or improperly formatted Oracle database ROWID value in a SQL statement.

Impact: TimesTen cannot convert the Oracle database ROWID to a TimesTen ROWID value.

User Action: Specify a valid Oracle database ROWID value.

1109

Error converting char to
ROWID

Type of Message: Error

Cause: TimesTen encountered an invalid or improperly formatted CHAR value in a SQL statement.

Impact: TimesTen cannot convert the CHAR value to a ROWID value.

User Action: Specify a valid CHAR value. For more information on the CHAR data type, see "CHAR" in the Oracle TimesTen In-Memory Database SQL Reference.

1110

FOR UPDATE with aggregate
function is deprecated

Type of Message: Warning

Cause: You specified a FOR UPDATE clause while selecting an aggregate function. The FOR UPDATE clause maintains a lock on an element (usually a row) until the end of the current transaction. Aggregate functions perform a specific operation over all rows in a group, causing the FOR UPDATE clause to not know which row to lock. Therefore, this operation is not recommended.

Impact: None.

User Action: Consider rewriting your SQL query.

For more information on the FOR UPDATE clause and aggregate functions, see "SELECT" and "Aggregate functions" respectively in the Oracle TimesTen In-Memory Database SQL Reference.

1111

Error in converting rowid to
char string

Type of Message: Error

Cause: Your application provided a buffer that is too small to store a ROWID string.

Impact: TimesTen cannot convert the ROWID value to a CHAR string.

User Action: Provide a buffer that can hold an 18 byte string.

1112

Error in converting char
string to rowid

Type of Message: Error

Cause: You specified an invalid CHAR string or your application provided a buffer that is too small to store a ROWID string.

Impact: TimesTen cannot convert the CHAR string to a ROWID value.

User Action: Specify a valid CHAR string and provide a buffer that can hold an 18 byte string.

1119

Arguments/bind variables not
allowed for data definition
operations

Type of Message: Error

Cause: You specified a binding variable or argument in a DDL statement.

Impact: TimesTen cannot perform the operation. Binding variables or arguments are not allowed for any DDL statements, such as CREATE VIEW, CREATE TABLE.

User Action: Consider using a CREATE TABLE statement with an INSERT INTO ... SelectQuery statement instead of a CREATE TABLE ... AS SelectQuery ... :BindingVariable statement.

For more information on the CREATE TABLE statement, see "CREATE TABLE" in the Oracle TimesTen In-Memory Database SQL Reference. For more information on the INSERT...SELECT statement, see "INSERT...SELECT" in the Oracle TimesTen In-Memory Database SQL Reference. For more information on CREATE VIEW, see "CREATE VIEW" in the Oracle TimesTen In-Memory Database SQL Reference.

1120

SQL command does not exist

Type of Message: Error

Cause: You specified a SQL unique identifier (sqlCmdID) that cannot be found in the SQL command query cache.

Impact: TimesTen cannot perform the operation.

User Action: Ensure that you specify a correct sqlCmdID value when you call a TimesTen built-in procedure that expects a sqlCmdID argument. Call the ttSQLCmdCacheInfo built-in procedure to view the TimesTen SQL command cache and the sqlCmdID of recent SQL statements.

For more information on the ttSQLCmdCacheInfo built-in procedure, see "ttSQLCmdCacheInfo" in the Oracle TimesTen In-Memory Database Reference. For more information on TimesTen built-in procedures, see "Built-In Procedures" in the Oracle TimesTen In-Memory Database Reference.

1121

Parser Stack Overflow in SQL
statement sql_statement

Type of Message: Error

Cause: The TimesTen parser exhausted its stack while parsing the SQL statement. This is usually due to too many nested or repeating elements in the SQL statement.

Impact: TimesTen cannot perform the SQL operation.

User Action: Contact TimesTen Customer Support.

1200

Invalid transaction ID was
input

Type of Message: Error

Cause: You specified an incorrect transaction ID (xactID) for the ttXactIdRollback utility API.

Impact: TimesTen cannot roll back the transaction.

User Action: Ensure that when you call the ttXactIdRollback utility API you specify a correct xactID argument. For more information on the ttXactIdRollback utility API, see "ttXactIdRollback" in the Oracle TimesTen In-Memory Database C Developer's Guide.

1203

This transaction needs
rollback since rollback was
forced

This transaction has been rolled back by another connection. You must complete it and clear its state by issuing a rollback from your connection.

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.

1801

Cannot create index on
expression with datatype LOB

Type of Message: Error

Cause: You attempted to create an index on a LOB column.

Impact: TimesTen cannot perform the operation.

User Action: Change the column data type or do not create the index on the LOB column.

1802

Column of datatype LOB cannot
be unique or a primary key

Type of Message: Error

Cause: You attempted to create a PRIMARY KEY or UNIQUE constraint on a column of data type LOB.

Impact: TimesTen cannot perform the operation.

User Action: Change the column data type or remove the constraint. Then retry the operation.

1803

Specified trim length is
greater than current LOB
values's length

The input length for which to trim the LOB value to is greater than the current length of the LOB value.

You may not need to trim the LOB value because it is already smaller than the specified trim length. If trimming the LOB value is required, use a smaller trim length.

1804

Invalid character set form

An invalid character set form was passed into an OCI LOB function. For example, SQLCS_CHAR could have been specified for a CLOB or SQLCS_IMPLICIT could have been specified for a NCLOB.

Specify a valid character set form.

1806

Invalid LOB locator specified

The LOB locator in the LOB API call is either not properly allocated or is not initialized.

Initialize the LOB locator.

1807

LOB already opened in the
same transaction

You attempted to open a LOB that is already opened in the transaction.

Close the LOB before attempting to re-open it.

1808

Cannot update a LOB opened in
read-only mode

You attempted to write to or update a LOB opened in read-only mode.

Close the LOB and re-open it in read-write mode before attempting to write to or update the LOB.

1809

LOB type mismatch

When copying or appending LOB locators, both source and destination LOB locators should be of the same type.

Pass the same type of LOB locators for copying or appending.

1812

Operation would exceed
maximum size allowed
number_bytes bytes for a
datatype value

You attempted an operation that would result in writing too much data to the LOB value. Maximum size for the CLOB and the NCLOB data types is 4 MB and maximum size for the BLOB data type is 16 MB.

Either start writing at a smaller LOB offset or write less data to the LOB value.

1813

Less data provided for
writing than indicated

When issuing the OCILobWrite call, ensure that the length of the data buffer is large enough to accommodate the data to be written.

1814

Source offset is beyond the
end of the source LOB

The source offset for the LOB copy or convert operation is beyond the end of the source LOB.

Check the length of the LOB and then adjust the source offset.

1818

Warning: Open LOBs exist at
transaction commit time

Type of Message: Warning

Cause: You attempted to commit a transaction with open LOBs.

Impact: TimesTen closes the LOBs and commits the transaction.

User Action: Make sure your application closes open LOBs before a commit. For more information on closing LOBs, see "CLOSE procedures" in the Oracle TimesTen In-Memory Database PL/SQL Packages Reference.

1819

Inconsistent datatypes:
expected datatype got
datatype

You attempted an operation (such as an INSERT) that was expecting a data type (such as a CLOB) and you provided an invalid data type (such as a BLOB).

Check the supported data types and conversions for the operation.

1820

Cannot create materialized
view that includes LOB
columns

You attempted to create a materialized view on a table with a column of type CLOB, NCLOB, or BLOB.

Recreate the materialized view without including the LOB column.

1821

Offset or offset+amount does
not land on character
boundary

You provided an offset that would cause the operation to override the character boundary.

This error occurs with NCLOB data types stored in a single byte or multibyte database or CLOB data types stored in a multibyte database.

1822

Cannot perform operation
operation on an unopened file
or LOB

Type of Message: Error

Cause: The file or LOB is not open for the required operation to be performed.

Impact: The indicated operation cannot be performed.

User Action: Precede the current operation with a successful open operation on the file or LOB.

1824

Row containing the LOB value
is not locked

The row containing the LOB value must be locked before updating the LOB value.

Lock the row containing the LOB value before updating the LOB value.

1825

CLOB or NCLOB in multibyte
character set not supported

A CLOB or NCLOB in a fixed-width or varying-width multibyte character set was passed to a SQL character function which does not support multibyte LOB data.

1826

Illegal parameter value in
OCI LOB function

You specified an invalid parameter value in the OCI LOB function.

Check each parameter in the OCI LOB function call to ensure that they are correct.

1829

CLOBs are not supported when
database character set is
TIMESTEN8

Your database character set is TIMESTEN8. CLOB and NCLOB functionality is not supported in this character set.

1830

BLOB/CLOBs are not supported
in the SELECT lists of set
operators such as UNION,
INTERSECT, and MINUS

You attempted to specify a LOB data type in the SELECT list of a set operator such as UNION, INTERSECT, or MINUS.

Do not use the LOB data type with these set operators.

1851

Operation on a passthrough
LOB is not supported

Operations such as ConvertToClob and ConvertToBlob are not supported.

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.

2043

Binary data exceeds column
width for column column_name
- value will be truncated

Warning: attempting to insert a string into a binary column that is larger than the column's maximum length. The string is truncated.

2044

Binary data exceeds column
width width

This error happens when an application inserts a binary value into a column that has a declared length that is shorter than the inserted value.

2206

Table table_name not found

Type of Message: Error

Cause: The specified table does not exist.

Impact: TimesTen cannot perform any operation with the specified table name.

User Action: Verify the table name and retry the operation.

2207

Table table_name already
exists

Attempting to create a table that already exists.

2208

Column column_name does not
exist in table

The referenced column does not exist in the table.

2209

Column column_name specified
more than once

The referenced column is specified more than once in the statement.

2210

Column reference of
column_name is ambiguous

A column reference without a table name qualification can be associated with more than one table.

2211

Referenced column
column_name not found

The referenced column does not exist in the table.

2212

Named index not found in
table

Attempting to drop an index that does not exist.

2213

Named index already exists on
specified table

Attempting to create an index that already exists.

2214

Column cannot be named ROWID

ROWID is a reserved word and cannot be used in this context.

2215

Attempt to drop a primary key
index

Primary keys can only be created in a CREATE TABLE statement. An attempt was made to drop a primary key. The primary key cannot be dropped.

2216

Index key length is long,
lookup based on the indexed
key may be slow

An attempt was made to create an index on column(s) having length of more than 4MB. This message warns that the lookup may be slowed down. Indexes can be up to the maximum key length.

2221

Duplicate column name found
in insert list

A column was specified more than once in the INSERT column list.

2222

Index name is not unique

While attempting to drop an index, the index is indirectly referenced more than once.

2223

Named index does not exist

Attempting to reference an index that does not exist.

2230

View view_name not valid
input to ttSize

A view name was specified to ttSize. You cannot pass a non materialized view to ttSize. Only tables, cache groups and materialized views are valid input.

2231

New index index_name would
be identical to existing
index index_name

Redundant indexes are not allowed on TimesTen tables. The new index was not created.

2232

New index index_name is
identical to existing index
index_name; consider dropping
index index_name

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 referenced 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 referenced 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 database_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 TimesTen operations and diagnostics. System tables are identified by the owner SYS or TTREP.

2239

New unique index index_name
has the same key columns as
existing non-unique index
index_name; consider dropping
index index_name.

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

2240

New non-unique index
index_name has the same key
columns as existing unique
index index_name; consider
dropping index index_name

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

2241

Such unique or primary key
already exists in the table

A table in a TimesTen database can have no more than one unique or primary key.

2242

Invalid value for MAXVALUES
in 'COMPRESS BY DICTIONARY'
clause

You entered an incorrect value for MAXVALUES. Valid values are between 1 and 2³² -1.

Respecify the COMPRESS BY DICTIONARY clause using a different value for MAXVALUES.

2244

Cannot drop compressed column
column_name1 without also
dropping column column_name2
which is in the same
compression group.

You must drop all columns in a multiple column compression group.

Use the ALTER TABLE statement to drop all columns in the compression group.

2245

Maximum values for
compression group containing
column column_name already
present

Type of Message: Error

Cause: The space allocated for the dictionary table for your compressed column has been exhausted.

Impact: Inserts or updates in the base table for values that do not have a corresponding value in the dictionary table will fail.

User Action: Investigate the maximum number of distinct values you require in your compressed column group and consider changing the MAXVALUES clause.

For more information on the maximum supported number of values for a compression group, see "In-memory columnar compression of tables" in the Oracle TimesTen In-Memory Database SQL Reference.

2246

Cannot change compression
clause for already defined
column column_name

You attempted to add compression to a column after the column was defined.

Consider respecifying the ALTER TABLE statement without using the already defined column in the compression clause. Or consider dropping the column.

2247

Total table size calculation
overflowed unsigned 32-bit
integer; table too large to
exist in a 32-bit TimesTen
installation

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.

2248

Total table size calculation
overflowed unsigned 64-bit
integer; table too large to
exist in 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.

2251

Compressed column group
exceeds maximum allowable
number of rows with equal
value

Type of Message: Error

Cause: The limit on occurrences of a value for a compressed column (group) has been exceeded. For more information on the limit of a value for a compressed column, see "In-memory columnar compression of tables" in the Oracle TimesTen In-Memory Database SQL Reference.

Impact: Inserts into the base table that have this column value will fail.

User Action: If the number of occurrences of a column group value is expected to exceed the limit, then you cannot use compression for that column group.

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.

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.

2401

Number of columns in
compression group
(num_columns) exceeds the
maximum (max_num_columns)

Type of Message: Error

Cause: You specified too many columns for a compression group in the COMPRESS clause of a CREATE TABLE or ALTER TABLE statement.

Impact: The CREATE TABLE or ALTER TABLE statement failed. TimesTen did not create or alter a table.

User Action: Reduce the number of columns in each compression column group to be less than the maximum allowed per compression group. For more information on columnar compression groups, see "In-memory columnar compression of tables" in the Oracle TimesTen In-Memory Database SQL Reference.

For more information on CREATE TABLE, see "CREATE TABLE" in the Oracle TimesTen In-Memory Database SQL Reference. For more information on ALTER TABLE, see "ALTER TABLE" in the Oracle TimesTen In-Memory Database SQL Reference.

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.

2417

Cannot add not null column
column_name unless it has a
default value specified

Type of Message: Error

Cause: If you use the ALTER TABLE statement to add a NOT NULL column, you must specify a default value.

Impact: You cannot use the ALTER TABLE statement to add a NOT NULL column without specifying a default value.

User Action: When you use the ALTER TABLE ADD statement to add a NOT NULL column, ensure that you specify a default value for the NOT NULL column.

For more information on ALTER TABLE, see "ALTER TABLE" in the Oracle TimesTen In-Memory Database SQL Reference.

2418

Cannot add not null column
column_name to replicated
table table_owner.table_name

Type of Message: Error

Cause: You attempted to use the ALTER TABLE statement to add a NOT NULL column to a table that is part of a replication scheme.

Impact: You cannot use the ALTER TABLE statement to add a NOT NULL column to a table that is replicated.

User Action:

1. Drop the table from the replication scheme. For more information, see "Dropping a table or sequence from a classic replication scheme" in the Oracle TimesTen In-Memory Database Replication Guide.

2. Add the NOT NULL column to the table with ALTER TABLE. For more information see "ALTER TABLE" in the Oracle TimesTen In-Memory Database SQL Reference.

3. Add the table back into the replication scheme. For more information, see "Adding a table or sequence to an existing classic replication scheme" in the Oracle TimesTen In-Memory Database Replication Guide.

2419

All columns in a primary key
constraint must be in the
initial partition; column
column_name was added by
ALTER TABLE

Type of Message: Error

Cause: When you use the ALTER TABLE statement to add a column, the newly added column is located in a secondary partition. You cannot use the ALTER TABLE statement to add a primary key constraint on a column that is in the secondary partition.

Impact: TimesTen did not create a primary key on the specified column because it is in a secondary partition.

User Action: Use ttmigrate -r -relaxedUpgrade to condense the secondary partition into a single partition. Once you condense the partitions, you can then ALTER the table and add a primary key constraint on the column.

For more information on partitions and using ALTER TABLE, see "ALTER TABLE" in the Oracle TimesTen In-Memory Database SQL Reference.

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. For more information on the maximum scale and precision of decimal values, see "NUMBER" in the Oracle TimesTen In-Memory Database SQL Reference.

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.

2599

Overflow: Value too big for
TimestampDiff's return type

The return type for the function TIMESTAMPDIFF is TT_BIGINT. This error occurs if the difference in the values between two timestamps results in a value that is too big or too small to fit into TT_BIGINT for the specified interval. An example is when the difference in the two timestamps is large and the specified interval is small (seconds or nanoseconds).

Respecify the interval making sure to specify a value that is appropriate for the TT_BIGINT return type.

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.

2610

Operand data type data_type
invalid for operator operator
in expr (expression)

Attempt to use an invalid operand data type with an operator. For example, using an integer operand with a LIKE relational operator is invalid.

2611

Errorconverting date to
character string

A DATE value of a TO_DATE function has an incorrect format. For more information, see "DATE" in the for the correct format of Oracle TimesTen In-Memory Database SQL Reference.

2612

Error converting time to
character string

A TIME value of a TO_DATE function has an incorrect format. For more information, see "TIME" in the for the correct format of Oracle TimesTen In-Memory Database SQL Reference.

2613

Error converting timestamp to
character string

A TIMESTAMP value of a TO_DATE function has an incorrect format. For more information, see "TIMESTAMP" in the for the correct format of Oracle TimesTen In-Memory Database SQL Reference.

2614

Value outside of range
supported by integral type

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.

2616

Error converting Oracle date
to TT_TIMESTAMP

Type of Message: Error

Cause: The data type conversion failed.

Impact: You cannot convert the ORA_DATE data type to a TT_TIMESTAMP data type.

User Action: Ensure that the ORA_DATE data type you are attempting to convert is within the ranges supported by the TT_TIMESTAMP data type. For more information on ranges supported by the TT_TIMESTAMP data type, see "Type specifications" in the Oracle TimesTen In-Memory Database SQL Reference.

2617

Error converting Oracle date
to Oracle timestamp

Type of Message: Error

Cause: The data type conversion failed.

Impact: You cannot convert the ORA_DATE data type to a ORA_TIMESTAMP data type.

User Action: Ensure that the ORA_DATE data type you are attempting to convert is within the ranges supported by the ORA_TIMESTAMP data type. For more information on ranges supported by the ORA_TIMESTAMP data type, see "Type specifications" in the Oracle TimesTen In-Memory Database SQL Reference.

2618

Error converting Oracle
timestamp to TT_TIMESTAMP

Type of Message: Error

Cause: The data type conversion failed.

Impact: You cannot convert the ORA_TIMESTAMP data type to a TT_TIMESTAMP data type.

User Action: Ensure that the ORA_TIMESTAMP data type you are attempting to convert is within the ranges supported by the TT_TIMESTAMP data type. For more information on ranges supported by the TT_TIMESTAMP data type, see "Type specifications" in the Oracle TimesTen In-Memory Database SQL Reference.

2619

Error converting Oracle
timestamp to Oracle date

Type of Message: Error

Cause: The data type conversion failed.

Impact: You cannot convert the ORA_TIMESTAMP data type to a ORA_DATE data type.

User Action: Ensure that the ORA_TIMESTAMP data type you are attempting to convert is within the ranges supported by the ORA_DATE data type. For more information on ranges supported by the ORA_DATE data type, see "Type specifications" in the Oracle TimesTen In-Memory Database SQL Reference.

2620

Error converting TT_TIMESTAMP
to Oracle date

Type of Message: Error

Cause: The data type conversion failed.

Impact: You cannot convert the TT_TIMESTAMP data type to a ORA_DATE data type.

User Action: Ensure that the TT_TIMESTAMP data type you are attempting to convert is within the ranges supported by the ORA_DATE data type. For more information on ranges supported by the ORA_DATE data type, see "Type specifications" in the Oracle TimesTen In-Memory Database SQL Reference.

2621

Error converting TT_TIMESTAMP
to Oracle timestamp

Type of Message: Error

Cause: The data type conversion failed.

Impact: You cannot convert the TT_TIMESTAMP data type to a ORA_TIMESTAMP data type.

User Action: Ensure that the ORA_TIMESTAMP data type you are attempting to convert is within the ranges supported by the ORA_TIMESTAMP data type. For more information on ranges supported by the ORA_TIMESTAMP data type, see "Type specifications" in the Oracle TimesTen In-Memory Database SQL Reference.

2622

Format string in string must
be a string literal

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
sql_statement is 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) of table table

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 greater
than zero and less than
max_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 on the
primary key

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

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
supported with temporary tables

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:

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

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'));

Ensure that you specify a valid NLS_SORT language.

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'));

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

Ensure that you specify a valid NLS_SORT language.

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.

2812

Error converting from
character string string to
Oracle date

Could not convert the specified CHAR string to an Oracle database DATE.

2813

Error converting from
character string string to
Oracle timestamp

Could not convert the specified CHAR string to an Oracle database TIMESTAMP. Check the string type and ensure that the result type does not result in an overflow or underflow.

2814

Trim character value should
be a single character

You specified more than one trim characters. Try the operation again with only one character specified for the TRIM function.

2815

Invalid number of arguments
for function function_name

Too many arguments were specified for the function indicated. Try the operation again with fewer function arguments.

2816

Given or computed year year
is out of range

The year specified is out of range.

2817

Invalid data type type for
argument argument_name for
function function_name

An invalid data type was specified for the indicated argument and function. For more information about the valid syntax for this function, see "Functions" in the Oracle TimesTen In-Memory Database SQL Reference.

2818

Unknown function
function_name. If this is a
PLSQL function, note such
functions are not yet
supported in SQL statements.

The specified function is not supported in TimesTen. For more information about supported functions, see "SQL functions" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

2819

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.

2821

DateFormatModel is not a
valid date format
model for date function

You specified an invalid date format model for you date function. Check the date format model and reexecute your query.

2822

Index type was changed

The primary key index type was changed while replication was using the index. TimesTen will attempt to retry using the new index.

2823

Expression ('expression') in
value list is not supported

Type of Message: Error

Cause: You specified a column reference in an IN value list.

Impact: TimesTen cannot execute the SQL statement.

User Action: Rewrite the IN value clause with an OR condition. Alternatively, remove the column reference from the SQL statement and retry the operation.For more information, see "ANY / IN predicate (value list)" in 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 datetime 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 datetime value failed either because the source value was not a valid datetime 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.

2876

Value number out of range;
specify 0 or 1.

The built-in procedure parameter accepts values 0 or 1. Specify a value of 0 (indicating FALSE or NO) or 1 (indicating TRUE or YES).

2877

Output parameter conversion
resulted in an incomplete
character

An output parameter buffer was too small, causing the output value to end with a partial multibyte character. Bind an output buffer that is large enough for the entire result value.

2878

Output parameter conversion
error (code=code)

An internal error occurred while performing character set conversion for an output parameter.

2879

Non-positive timestamps not
allowed for function

You specified a timestamp value with a year less than or equal to 0. TimesTen does not support negative years because timestamp arithmetic involving negative years could result in timestamps falling in year 0. TimesTen does not support year 0.

Respecify the function using positive timestamp values.

2903

Illegal character character

A SQL statement contains a character not acceptable in SQL outside of a string constant. For more information, see "SQL Statements" in the Oracle TimesTen In-Memory Database SQL Reference.

2904

Invalid element element in
number format

An invalid element was found in the format of a TO_CHAR function. For more information about the TO_CHAR function, see "TO_CHAR" in the Oracle TimesTen In-Memory Database SQL Reference.

2905

Invalid element element in
date format

An invalid element was found in the format of a TO_CHAR or TO_DATE function. For more information about the TO_CHAR function, see "TO_CHAR" in the Oracle TimesTen In-Memory Database SQL Reference. For more information about the TO_DATE function, see "TO_DATE" in the Oracle TimesTen In-Memory Database SQL Reference.

2906

Bad number format

The format of TO_CHAR function is invalid. For more information about the TO_CHAR function, see "TO_CHAR" in the Oracle TimesTen In-Memory Database SQL Reference.

2907

Bad date format

The format of TO_CHAR or TO_DATE function is invalid. For more information about the TO_CHAR function, see "TO_CHAR" in the Oracle TimesTen In-Memory Database SQL Reference. For more information about the TO_DATE function, see "TO_DATE" in the Oracle TimesTen In-Memory Database SQL Reference.

2908

Error converting decimal to
character string

Error in converting a DECIMAL to CHAR for TO_CHAR function. For more information, see "TO_CHAR" in the Oracle TimesTen In-Memory Database SQL Reference.

2909

Error converting numeric to
character string

Error in converting an INTEGER or FLOAT to CHAR for TO_CHAR function. For more information, see "TO_CHAR" in the Oracle TimesTen In-Memory Database SQL Reference.

2910

Float overflow for TO_CHAR
function

The absolute FLOAT value of a TO_CHAR function is greater than 1e+126. For more information, see "Format model for TO_CHAR of TimesTen datetime data types" in the Oracle TimesTen In-Memory Database SQL Reference.

2911

Float underflow for TO_CHAR
function

The absolute FLOAT value of a TO_CHAR function is less than 1e-126. For more information, see "Format model for TO_CHAR of TimesTen datetime data types" in the Oracle TimesTen In-Memory Database SQL Reference.

2912

Invalid Unicode escape
string

TimesTen detected an improperly formed Unicode escape sequence. For more information, see "Character and unicode strings" in the Oracle TimesTen In-Memory Database Reference.

2913

Invalid argument
argument_string for
NUMTODSINTERVAL function

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 ensure 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 ensure 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 ensure 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 ensure 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 ensure that the result type does not result in an overflow or underflow.

2930

Error converting Number to
Float

Check the string type and ensure 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

Type of Message: Error

Cause: An error occurred while attempting to round or truncate a date. A common cause for this is that there is not enough free space in the target column.

Impact: The date cannot be rounded or truncated.

User Action: None.

For more information on the ROUND (date) and TRUNC (date) functions, see "ROUND (date)" and "TRUNC (date)" in the Oracle TimesTen In-Memory Database SQL Reference.

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

Type of Message: Warning

Cause: The result was truncated during conversion.

Impact: The result of your operation may be less precise than the original number value.

User Action: If you are attempting INSERT or UPDATE operations, consider increasing the size of the target column. For more information on column sizes, see "Column overview" in the Oracle TimesTen In-Memory Database Operations Guide.

2946

Truncation occurred
converting Number to Char

Type of Message: Warning

Cause: The result is truncated when converting from NUMBER to CHAR, and some fractional data (i.e., numeric data to the right of the decimal point) could not be converted because the supplied CHAR column length is not big enough.

Impact: The result of your operation may be less precise than the original number value.

User Action: Allocate a larger CHAR buffer to accommodate the result of the conversion. Allocating a large enough CHAR buffer size will prevent truncation of the result.

For more information on the CHAR data type, see "CHAR" in the Oracle TimesTen In-Memory Database SQL Reference.

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

Type of Message: Error

Cause: An error occurred while attempting to convert a numeric data type.

Impact: The conversion operation cannot be completed.

User Action: Ensure that your numeric input data is correct. For more information on numeric data types, see "Numeric data types" in the Oracle TimesTen In-Memory Database SQL Reference.

2950

Merge may not update a row
more than once, but the row
at rowid 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 ensure that 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 ensure that 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.

2961

Inconsistent datatypes:
cannot convert datatype_A to
datatype_B in expression
(expression)

Cannot convert data type A to data type B.

2962

Inconsistent datatypes:
expected datatype_A got
datatype_B in
expression (expression)

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

Type of Message: Error

Cause: You attempted an operation where the relational operator IN is specified with more than one value in the left operand but at least one group of values in the right operand has a different number of values than the number of values in the left operand. For example:

SELECT * FROM t WHERE (a,b) IN ((1,1),(2));

In this example, the second group of values in the IN list contains one less entry than the number specified in the left operand.

Impact: TimesTen cannot perform the operation.

User Action: Add the missing value or values to the SQL statement and retry the operation. For more information on SQL statements, see "SQL Statements" in the Oracle TimesTen In-Memory Database SQL Reference.

2973

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

Type of Message: Error

Cause: You attempted an operation where the relational operator ANY or IN is specified with a subquery that returns a different number of values than the specified in the left operand. For example:

SELECT * FROM t1 WHERE (a,b) IN (SELECT c FROM t2);

In this example, the group of values returned in the IN list contains one less entry than that the number specified in the left operand.

Impact: TimesTen cannot perform the operation.

User Action: Add the missing value or values to the SQL statement and retry the operation. For more information on SQL statements, see "SQL Statements" in the Oracle TimesTen In-Memory Database SQL Reference.

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.

2990

Cannot change aging
attributes or add/drop aging
policy of autorefresh cache
group while cache agent is
active

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.

2995

Child child_table of table
parent_table has differnt
aging policy: aging_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, ensure 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

self-referencing foreign keys
are not allowed

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

3001

Foreign key violation error

The INSERT, DELETE or UPDATE statement caused a foreign key constraint violation. See "SQL Statements" in the Oracle TimesTen In-Memory Database SQL Reference.

3003

Table/Index is in use by a
foreign key

The table or index cannot be dropped or modified because it is referenced by a foreign key constraint.

3004

Foreign key column type
mismatch

The foreign key columns do not match the primary key columns in number, type, length, precision or scale.

3005

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

The foreign key constraint requires a primary or unique index on the referenced columns of the referenced table.

3006

System/Cached tables cannot
be referenced by a foreign
key

Cannot create a foreign key on any system or cache tables or referencing any system tables.

3007

Both foreign key function
arguments are nulls

Internal error. Contact TimesTen Customer Support.

3008

Scalar subquery returned
more than one row

A scalar subquery may return at most one row. For more information, see "Scalar subqueries" in the Oracle TimesTen In-Memory Database SQL Reference.

3009

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.

3023

Aging column must be in the
initial partition; column
column_name was added by
ALTER TABLE

Type of Message: Error

Cause: When you use the ALTER TABLE statement to add a column, the newly added column is located in a secondary partition. You cannot add a time-based aging policy on a column that is in the secondary partition.

Impact: You cannot specify a time-based aging policy on the specified column because it is in a secondary partition.

User Action: Use ttmigrate -r -relaxedUpgrade to condense the secondary partition into a single partition. Once you condense the partitions, you can then set a time- based aging policy on the column.

For more information on partitions, see "ALTER TABLE" in the Oracle TimesTen In-Memory Database SQL Reference.

3025

Missing ORDER BY expression
in the window specification

You attempted to specify a window specification without including the ORDER BY clause for an analytic function. Respecify your function including the ORDER BY clause.

3026

ORDER BY is not allowed with
analytic aggregation with
distinct

You attempted to specify both the DISTINCT qualifier and the ORDER BY clause for your analytic aggregate function. Respecify your function omitting either the DISTINCT qualifier or the ORDER BY clause.

3027

Windowing clause is not
allowed with
RANK/DENSE_RANK/ROW_NUMBER
analytic functions

You attempted to use the windowing clause for the RANK or DENSE_RANK or ROW_NUMBER analytic functions. Respecify the function omitting the windowing clause.

3028

Invalid analytic window
argument

You did not correctly specify the start point or end point of your windowing clause in the analytic function. The start point and end point must evaluate to a positive numeric value and the start point value must be less than the end point value. Check your start point and end point specifications and redefine your analytic function using the correct windowing clause specification.

3029

Invalid use of analytic
function function_name

You did not specify the analytic function in the SELECT list of a query. Respecify the analytic function making sure to include the function in the SELECT list of your query.

3030

Missing window specification
for this function

You attempted to specify an analytic function without the windowing clause. Respecify the function with the windowing clause.

3031

Nested Analytical functions
are not allowed

Type of Message: Error

Cause: Your SQL statement contains nested analytic functions.

Impact: TimesTen cannot perform the SQL operation.

User Action: Specify a SQL statement without nested analytic functions. For more information on analytic functions, see "Analytic functions" in the Oracle TimesTen In-Memory Database SQL Reference.

3039

The first argument of NULLIF
cannot be NULL literal

You specified NULL as the first argument to the NULLIF function. Invoke your function again without specifying NULL as the first argument.

3040

GROUPING function only
supported with GROUP BY

You specified a grouping function such as GROUP_ID, GROUPING, or GROUPING_ID that was not within the GROUP BY clause. Modify your query by specifying the grouping function as part of the GROUP BY clause.

3041

Number of groupings exceed
the maximum (2147483648)

Your specified number of groupings in the GROUP BY clause exceeds the maximum limit of 2147483648. Reduce the number of groupings.

3050

Subquery is not allowed in
the RETURNING clause

You specified a subquery in a RETURNING clause. 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.

3080

Cannot create a public
synonym with the same name as
TimesTen built-in procedure
procedure_name

You attempted to create a public synonym with the same name as a TimesTen built-in procedure.

Recreate your synonym with a name that is not the same name as a TimesTen built-in procedure.

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

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.

3113

Cannot drop tables with
defined materialized views:
the view view_name refers
to table_name

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.

3118

View view_name already exists

A CREATE MATERIALIZED VIEW statement specified an existing view.

3119

More than number views
reference table table_name

A CREATE MATERIALIZED VIEW statement specified a detail table that already has 100 views referencing it.

3120

View view_name does not exist

A DROP VIEW statement specified a non-existent view.

3121

A cache group table
table_name cannot be
referenced in a materialized view

A CREATE MATERIALIZED VIEW statement specified a cache group table as a detail table. This is not supported.

3123

Foreign keys on view tables
are not allowed

Foreign keys are not allowed to be defined on materialized views, only tables.

3124

Cannot create a view that
references a system table

A CREATE MATERIALIZED VIEW statement specified a system table as a detail table. This is not supported.

3125

View definition was too
long. Could not store the
definition in the system tables

An error occurred while creating a materialized view because some field was too long.

3128

Invalid size of column name list

A column name list was specified for a derived table or non-materialized view but its size does not match the number of projected columns.

3129

Invalid column name for view

Names in the column name list of a derived table or view cannot have table name specification.

3130

Derived table name
table_name is not unique
among all
based/viewed/derived table
names

A derived table name must be unique among the names of all derived tables, base tables and views referenced in the same query.

3131

View view_name is not a
materialized view; use
DROP VIEW instead

DROP MATERIALIZED VIEW statement was used to drop a non-materialized view. See "DROP MATERIALIZED VIEW" in the Oracle TimesTen In-Memory Database SQL Reference.

3132

A materialized view cannot
reference a regular view

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

3133

Cannot truncate tables with
defined materialized views:
the view view refers to
table

You attempted to truncate a table and the table has a materialized view defined on it.

Either drop the materialized view or do not use the TRUNCATE statement. You can consider using the DELETE statement.

3134

Cannot truncate materialized
view: view_name

You attempted to truncate a materialized view. This is not a supported operation.

Do not use the TRUNCATE statement to delete rows. Consider using the DELETE statement to delete the rows from the table.

3135

Cannot truncate table:
parent_table; child table:
child_table is not empty.
Please execute truncate on
child table first

You attempted to truncate a parent table and the child table was not empty. Consider truncating the child table first and then truncate the parent table.

3136

Cannot truncate temp table:
temp_table; Please use delete

You attempted to truncate a global temporary table. This is not a supported operation. If you want to remove rows from the table, use the DELETE statement.

3137

Cannot insert into a
truncated table in an
uncommitted transaction

An in-progress transaction is attempting to insert rows into a table that has already been truncated. Consider committing the transaction with the truncate statement and then execute the insert operation.

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.

3143

Cannot drop Materialized
View Log table table_name
with Drop Table. Use Drop
Materialized View Log On
view_log

To drop a materialized view log table, you must use the DROP MATERIALIZED VIEW LOG SQL statement.

3144

Cannot drop table
table_name with defined
Materialized View Log. First
drop materialized view log.

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.

3149

Insert/delete/update/
truncate operations not
allowed in a Materialized
View Log Table

You cannot perform SQL operations on a materialized view log table that change the data in the table.

3150

Refresh name is not
accepted. System is busy. Try
again

Only one refresh request can be processed at any given time. Retry the operation again.

3151

Asyncmv Thread encountered
error while refreshing the
view view_name. Check the
Daemon Log

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.

3157

Cannot drop Materialized
View Log on a detail table
with defined Asynchronous
Materialized View. View
materialized_view refers to
the detail table.

Materialized view log was not dropped.

First drop the dependent asynchronous materialized view. Then, drop the materialized view log.

3158

Cannot create a materialized
view log on a system table

Error thrown when user executes CREATE MATERIALIZED VIEW LOG ON system_table. Cannot create a materialized view log on a system table. The materialized view log is not created.

3159

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

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.

3201

Sequence cache has not been
allocated

This is an internal error. Contact TimesTen Customer Support.

3202

Illegal max value. Possible
reasons: maximum/ minimum
limit, or max < min

Type of Message: Error

Cause: You specified a CREATE SEQUENCE statement with a value of the MAXVALUE parameter that is lower than or equal to the value specified for the MINVALUE parameter.

Impact: TimesTen cannot create the sequence object.

User Action: Specify a value for the MAXVALUE parameter that is greater than the value specified for the MINVALUE parameter and retry the CREATE SEQUENCE statement. For more information on the CREATE SEQUENCE statement, see "CREATE SEQUENCE" in the Oracle TimesTen In-Memory Database SQL Reference.

3204

Sequence sequence_name is
not found

Type of Message: Error

Cause: The specified sequence object does not exist.

Impact: TimesTen cannot perform any operation with the specified sequence object name.

User Action: Verify the sequence object name and retry the operation.

3205

A table or sequence with
this name already exists

Type of Message: Error

Cause: You specified a sequence object name or table object name that already exists.

Impact: TimesTen cannot create a sequence object or table object with the specified identifier.

User Action: Select a different name for the sequence object or table object and retry the operation.

3206

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

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 before 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 cannot get the next value of the sequence from the cache because of an update problem or lock timeout; there is a problem in posting the NEXTVAL in the environment due to a memory allocation problem, 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 Customer Support.

3215

An error occurred while
cleaning up sequence cache
during rollback

When a rollback is performed, TimesTen clears up the cached sequences appropriately. An error is reported when the cleanup is not successful.

3221

Invalid statistics
information: error_number

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.

3222

Estimate statistics on
owner.table failed due to
concurrent operations;
try again.

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 many rows are deleted in a concurrent transaction.

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

3230

Another session changed the
enhanced write concurrency
mode while this session was
waiting for the mode
transition to complete

Type of Message: Error

Cause: The enhanced write concurrency mode was changed by another session before the mode transition completed.

Impact: The enhanced write concurrency mode transition started but did not complete.

User Action: Ensure that other sessions have completed the transition of the enhanced write concurrency mode. Then, retry changing the mode of the ttDbWriteConcurrencyModeSet built-in procedure.

3231

You must first call function
before you can switch from
mode current_mode to mode
specified_mode

Type of Message: Error

Cause: You attempted to change the enhanced write concurrency mode from current_mode to specified_mode.

Impact: The enhanced write concurrency mode cannot be changed.

User Action: Call the function that the error message specifies. Then, retry changing the mode of the ttDbWriteConcurrencyModeSet built-in procedure.

3232

Invalid value_type value:
value

Type of Message: Error

Cause: You specified an invalid parameter value.

Impact: The parameter changes you specified cannot be completed.

User Action: Specify valid parameter values and retry calling the built-in procedure.

3233

Failed to wait for a SQL
command to complete that was
not compiled in write
concurrency mode mode

Type of Message: Error

Cause: The ttDbWriteConcurrencyModeSet built-in procedure could not acquire a lock. A common cause for this is that there is a long running SQL statement.

Impact: The enhanced write concurrency mode transition started and will continue until all SQL statements in transition are executed. The ttDbWriteConcurencyModeSet built-in procedure cannot wait because it could not acquire a lock.

User Action: Use the ttXactAdmin utility to check if there is SQL statement blocking the lock acquisition for the ttDbWriteConcurencyModeSet built-in procedure. If there is a SQL statement blocking the lock acquisition, wait for the SQL statement to finish executing. Alternatively, consider terminating the SQL statement. For more information about using the ttXactAdmin utility, see "Using the ttXactAdmin utility" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

3234

Waiting for mode transition
on active SQL commands
prepared or executed in this
connection would never finish

Type of Message: Error

Cause: You attempted to change the enhanced write concurrency mode in a transaction with active SQL statements.

Impact: The enhanced write concurrency mode cannot be changed.

User Action: Commit the current transaction. Then, retry changing the mode of the ttDbWriteConcurrencyModeSet built-in procedure.

3235

Waiting for mode transition
on SQL commands with open
cursors in this connection
would never finish

Type of Message: Error

Cause: You attempted to change the enhanced write concurrency mode in a transaction with open cursors.

Impact: The enhanced write concurrency mode cannot be changed.

User Action: Close the open cursors and commit the current transaction. Then, retry changing the mode of the ttDbWriteConcurrencyModeSet built-in procedure.

3236

Waiting for SQL commands to
transition cannot be done
with database level locking

Type of Message: Error

Cause: You attempted to change the enhanced write concurrency mode in a database with database level locking.

Impact: The enhanced write concurrency mode cannot be changed.

User Action: Consider disabling database level locking with the ttLockLevel built-in procedure. Then, retry changing the mode of the ttDbWriteConcurrencyModeSet built-in procedure. For more information on database level locks, see "Locking granularities" in the Oracle TimesTen In-Memory Database Operations Guide.

Alternatively, consider setting the wait parameter of the ttDbWriteConcurrencyModeSet built-in procedure to 0. Then, retry changing the mode of the ttDbWriteConcurrencyModeSet built-in procedure.

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 Database 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 database 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 database 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 database 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 database 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 database 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 the Oracle database 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' 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.

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

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 active. 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 the Oracle database 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.

3365

Failed to get root table
primary key for transparent
load. Reason details

A transparent load that specifies the primary or foreign key of a child table failed to select the primary key of the root table. The reason is provided in the error message.

3366

ttGridNameSet cannot be
called from the standby of an
active standby pair. Call it
from the active instead

You cannot call the ttGridNameSet utility from the standby of an active standby pair grid member. Call it from the active.

3369

Cannot detach from cache grid
when there are
outstanding_trans_load_count
outstanding transparent load
and/or unloading

A member cannot detach from a cache grid when there are a number of outstanding transparent loads or unloads.

3370

Member is in grid detach or
failed during last detach. If
the last detach failed,
please complete the detach
and re-attach the member
first.

Last detach failed and the member is still in detaching state. Reexecute the detach to complete it.

3371

Grid control table
table_name on Oracle was
corrupted

Some Oracle database tables containing control information for the cache grid were corrupted.

3372

Timed out waiting seconds
seconds for change to be
propagated to Oracle

A timeout occurred while waiting for a change on an instance to be propagated to the Oracle database before loading the instance to another member.

3373

Cache instance does not meet
aging requirement

An instance in an old owner does not meet the aging requirement of the new owner.

3374

Member may contain stale
global cache group table
data. Attach to the grid
to clean up the data.

Attach to the grid to clean up the data.

3375

Oracle table/procedures
needed for global cache group
are missing. Perform
manual install to create
them.

A global cache group was created without creating all Oracle database control tables due to a lack of the required privileges. Perform a manual install to create these tables.

3377

Failed to acquire grid info.
Grid information on Oracle
may be stale. Reason cause

This error occurred while calling a built-in procedure to get information about cache grids. The detailed error is included in the message.

3378

Cannot drop ownership table
of global cache group. Drop
the cache group instead.

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 owner.cache_group
failed ownership checking:
error.

Internal error while calling 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 member(node_id)
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 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.

Type of Message: Error

Cause: The cache grid cannot communicate with the specified members.

Impact: Operations that require communication with these members will fail.

User Action: Check if the specified members are still operational. If they are not operational, use the ttGridDetach built-in to detach them from the grid. For more information on the ttGridDetach built-in procedure, see "ttGridDetach" in the Oracle TimesTen In-Memory Database Reference.

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.

3402

Cannot drop an active
standby pair when the cache
grid is attached. Detach the
cache grid first.

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 asynchronous writethrough cache group are propagated to the Oracle database before trying to drop the cache group. Ensure that 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 the Oracle database. Ensure that the replication agent is up. Wait until the replication agent finishes propagating all changes before retrying the checkpoint. For more information, see "Fuzzy or non-blocking checkpoints" in the Oracle TimesTen In-Memory Database Operations Guide.

3406

Unique constraint
(constraint) violated at
Rowid rowid due to
unpropagated delete

Internal error. Contact TimesTen Customer Support.

3407

Cannot allocate space to
store ownership information
for global cache groups
because temporary data region
free space is below the
minimum threshold of number
bytes

Free up space within the temporary memory region before continuing.

3408

Global statement needs the
database to attach to the
grid first

A member must attach to the grid first before executing any global statements.

3409

Combination of global
processing option and
option_name option is not
supported

Global statement optimizer hint cannot combine with passthrough hint.

3410

Grid sender queue is too full

Internal error. Grid sending queue is too full.

3411

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

Global select failed because temporary memory region 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 Customer 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 Customer Support.

3416

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

Grid failover 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 Customer 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 failover 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 the Oracle database before a node can detach.

3421

Grid Configuration was
changed

A grid member was added or removed after a global query was compiled.

Recompile the query.

3422

The instance has been updated
and unloaded and the update
has not been propagated to
Oracle. Please make sure
replication agent is up

A cache group instance has been updated and unloaded and the update has not been propagated to the Oracle database. As a result, the instance cannot be reloaded.

Check to see if the replication agent is up. If not, start the replication agent.

3423

The instance has been
unloaded by the same
transaction and cannot be
reloaded. Please commit the
transaction first and retry
the operation

A cache group instance has been unloaded by a transaction and the transaction has not been committed. The instance cannot be reloaded until the transaction is committed and the update is propagated to the Oracle database.

Commit the transaction and ensure that the replication agent is up.

3427

Global cache group is not
supported on Windows

Type of Message: Error

Cause: The global cache group feature is not supported on Windows.

Impact: You cannot specify a global cache group on Windows.

User Action: You cannot specify a global cache group on Windows.

3428

Dynamic load is not allowed
with multiple cache groups
when dynamicloadEnable
connection attribute is set
to 1. Set it to 2 instead and
retry the query

When the DynamicLoadEnable connection attribute is set to 1, a dynamic load is not allowed if your query references multiple cache groups.

Set DynamicLoadEnable to 2 and retry your query.

3429

Dynamic load is not allowed
with cache group table in
subquery when
dynamicloadEnable connection
attribute is set to 1. Set it
to 2 instead and retry the
query

When the DynamicLoadEnable connection attribute is set to 1, a dynamic load is not allowed if your query references any cache group in the subquery.

Set DynamicLoadEnable to 2 and retry the query.

Note: With DynamicLoadEnable set to 2, a dynamic load is not performed if your cache group is referenced in the subquery. However, a dynamic load is performed if your cache group is referenced in the main query.

3430

Grid name can not be changed
when there are global cache
groups or local cache groups
in cache grid enabled mode

You attempted to change the grid name by calling the built-in procedure ttGridNameSet when one of the following conditions was true:

1. Your database had global cache groups.

2. Grid is enabled and your database had local AWT cache groups.

Errors 4000 - 4999

Error number
Error or warning message
Details

4053

Internal error. error_number

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

4056

Assertion failure (assertion)
in file file_name at line
line_number

Type of Message: Error

Cause: An internal assertion occurred at the specified location.

Impact: Your current operation failed.

User Action: Contact TimesTen Customer Support.

4501

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

Error min_range and max_range

Bad argument generic error message.

4601

Error value message

Bad argument generic error message.

Errors 5000 - 5999

Error number
Error or warning message
Details

5002

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

Type of Message: Informational

Cause: The cache agent is not running.

Impact: TimesTen cannot autorefresh cache groups.

User Action: Call the ttCacheStart built-in procedure to start the cache agent. For more information about the ttCacheStart built-in procedure, see "ttCacheStart" in the Oracle TimesTen In-Memory Database Reference.

5007

Cache agent error

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

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 database (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 user name 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 or the Oracle database. Ensure that the user name, password and Oracle database ID are correct.

5015

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

Type of Message: Error

Cause: The schema of the cached table changed on the Oracle database after the cache group was created.

Impact: The specified cached tables cannot function correctly.

User Action: Recreate the cache group. For more information, see "Create the cache groups" in the Oracle TimesTen Application-Tier Database Cache User's Guide. Then, retry the operation.

5016

Cache agent has too many
existing connections

Type of Message: Warning

Cause: The Oracle database has run out of resources to accommodate any additional connections made by the TimesTen cache agent.

Impact: The TimesTen Cache features cannot function correctly.

User Action: Diagnose and troubleshoot any connection leaks to the Oracle database. Also, consider configuring the Oracle database to allow additional connections. Then, retry the operation.

5019

Bad table name specification

Type of Message: Error

Cause: The configuration file contains a cache table specification with an invalid table name. Review the user error log for additional error messages.

Impact: The cache agent may have failed certain operations, such as loading a cached table.

User Action: Review the user error log for possible fixes.

5020

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

Type of Message: Warning

Cause: A warning message was generated while TimesTen was populating a cached table. Review the user error log for more information.

Impact: TimesTen may not have completed the population of the cached table.

User Action: Review the user error log for possible fixes.

5021

Could not get meta data
from Oracle:
detailed_error_message

Type of Message: Error

Cause: The TimesTen cache administrator cannot retrieve the requested metadata from the Oracle database.

Impact: The cache agent may have failed certain operations, such as a refresh operation. Review the user error log for more information.

User Action: Review the user error log for possible fixes.

5022

Could not open output file
for writing Oracle meta data

The Cache Administrator was not able to write the Oracle database 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 the Oracle database. 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 of cache_name 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 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 Customer 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.

5037

An error occurred while
loading cache_group_name:
detailed_warning_message

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_name
detailed_error_message

Type of Message: Error

Cause: An error occurred while refreshing the specified cache group. A detailed error message follows this message.

Impact: Review the error message for possible impacts.

User Action: Review the error message for possible fixes.

5040

Warning(s) while unloading
the cache.
detailed_warning_message

Type of Message: Warning

Cause: Some SQL warnings were generated while unloading the cache group. A detailed warning message follows this message.

Impact: Review the warning message for possible impacts.

User Action: Review the warning message for possible fixes.

5041

An error occurred while
unloading
cache_group_name:
detailed_error_message

Type of Message: Error

Cause: An error occurred while unloading the specified cache group. A detailed error message follows this message.

Impact: The cache group unload operation was unsuccessful. Review the error message for possible impacts.

User Action: Review the error message for possible fixes.

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 is too
long. Current system limit on
field_name field 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 database connection terminated during a transaction rollback. The pending Oracle database transaction was (or will be) rolled back by the Oracle database server. The error_number is either an ORA-xxxxx message, an Oracle database error code that was returned by the Oracle database during rollback, or "no error code," which means the connection was broken before the Oracle database rollback request.

5058

The cache operation received
a warning: warning_type=type,
warning_code=code,
warning_message: message

The cache agent generates this warning message. The specific warning is indicated at the end of message.

5061

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

An error was encountered when propagating to the Oracle database. The rollback on the Oracle database also failed. TimesTen and Oracle database data are in a transactional inconsistent state. One way to make the cache groups consistent with the Oracle database 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.

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

Fix is to use compatible Oracle database client/server versions according to documentation.

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

A TimesTen Cache built-in procedure was called with an argument that was not needed. The argument was ignored and the built-in was called without the argument.

5069

Argument argument_name
error_message

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

5070

Error compiling PL/SQL
block. Check that
user_name has
privilege_type on table_name

There was an error compiling an Oracle Database PL/SQL block because the application user does not have the correct privileges on Oracle Database. Check the privileges indicated in the message.

5071

Name string reused within
statement. Use different
names.

The cache group name is being used by another TimesTen object. Use a different name.

5073

Cache operation failed.
Rollback required.

Type of Message: Error

Cause: Review the error message on the error stack for possible causes.

Impact: The transaction must be rolled back.

User Action: Rollback the transaction. For more information on how to rollback a transaction, see "Working with transactions" in the Oracle TimesTen In-Memory Database Operations Guide. Then diagnose and troubleshoot the error on the error stack and retry the cache operation.

5074

Could not log in to Oracle
database. Login Attempt:
num_attempts, Allowed
attempts: max_attempts.

Type of Message: Error

Cause: The cache or replication agent failed to connect to the Oracle database.

Impact: TimesTen cannot connect to the Oracle database. When the number of log in attempts reaches the number of allowed attempts, the agent will stop trying to connect to the Oracle database.

User Action: Review the daemon log for more details about the problem. For more information on how to review the daemon log, see "Using the logs generated by the TimesTen daemon" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

5101

An error occurred while
generating the name of the
type database shared library
for database type:
database_type

Oracle is the only supported back-end database for cache group operations and passthrough.

5102

Cannot load backend library
library_name for Cache
Connect. OS error message
error_details.

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

The library was not installed or is named differently than the 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.

Some platforms use something other than LD_LIBRARY_PATH. See the "Shared library path environment variable" in the Oracle TimesTen In-Memory Database Installation Guide for details.

5103

The cache group operation
could not unload the backend
database shared library.
library_name

The OS had some problem unloading the back-end database library.

5104

Could not initialize the
function pointers backend
database api. Function
function_name was not in
the library.

This usually indicates that an older version of the back-end library was loaded. Check the library search path to verify that it is pointing to the correct library directory.

5105

OCI initialization failed:
description.

The OCI could not be initialized. This is a necessary component for TimesTen Cache. This usually occurs when there is not enough memory on the client system.

5106

Could not allocate
handle_name handle

This is usually occurs when there is very little memory left on the client system.

5107

Oracle(OCI)
Oracle_error_id in
OCI_call:
Oracle_error_number

The operation that was being performed has failed because of an error that occurred while executing an OCI function. Details on the error are specified within the error message.

5109

Cache Connect general
error: Oracle_operation

TimesTen Cache failed in the identified Oracle database operation. This error is usually accompanied by a more specific error message. If not, contact TimesTen Customer Support.

5110

Table does not exist in
Oracle: table_name

The cache group table does not exist on the Oracle database.

5111

Could not find matching
unique index for cache table
table_name

The primary key defined on TimesTen must match the primary key or unique NOT NULL key on the Oracle database.

5112

Cache owner table_name
contains VARCHAR column(s).
Oracle VARCHAR comparison
rule is different.

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

5113

Cache owner table_name
contains REAL/DOUBLE/ FLOAT
column(s). Cached value may
have a different precision.

This is a warning. Oracle Database 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 Database. 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 TimesTen Application-Tier 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 TimesTen Application-Tier 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 the Oracle database.

5118

Column column_name has
different precision/ scale
in Oracle

This is a warning. Oracle Database 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 Database 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 the Oracle database.

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 the Oracle database to match the cache table's primary key.

5121

Non-standard type mapping
for column column_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 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 the Oracle database.

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

5125

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

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

5126

A system managed cache
group cannot contain non-
standard column type mapping

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

5127

Backend connection invalid.
error_details

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

5128

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

A TimesTen Cache handle has been invalidated. In most cases, this occurs when the connection to the Oracle database has been lost. Check if the Oracle database instance is up and retry the operation.

5129

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

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

5130

Error executing the
following statement on
oracle_db: query

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

5131

Cannot connect to backend
database:
OracleNetServiceName =
Oracle_service_name, uid =
user_id, pwd is
hidden,TNS_ADMIN =
tns_admin , ORACLE_HOME=
Oracle_home

Common causes of connection failures are incorrect OracleNetServiceName, user id or password, TNS_ADMIN or location of the Oracle database installation. It is also possible the Oracle database user password (the ORACLEPWD) attribute is not specified.

You may also find the Oracle database error number in other messages on the error stack. Check the Oracle database error message documentation for the corresponding Oracle database 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.

The Oracle database SQL statement used by TimesTen Cache is no longer valid.

5133

Could not re-install SIGINT
signal handler

TimesTen Cache failed to re-install the SIGINT signal handler. The handler was changed by the Oracle database. Contact TimesTen Customer Support.

5134

Could not determine Oracle
server version

TimesTen Cache failed to determine the version of the Oracle database server. Contact TimesTen Customer Support.

5142

Autorefresh is not allowed
on cache groups with Oracle
synonyms

You cannot set AUTOREFRESH for a cache group that uses Oracle database synonyms.

5144

The cache group contains a
Oracle materialized view,
cache operations are
restricted.

You cannot create a restricted cache group on an Oracle database materialized view.

5146

owner.name is a public
synonym which is not
supported

Public synonyms are not supported in cache groups. One reason for this is because the owner and object name on the Oracle database must be the same on TimesTen. Since you cannot create an object owned by PUBLIC, this functionality is not supported in cache groups.

5150

The statement handle is in
an invalid state for the
operation: operation_name

Internal error. Contact TimesTen Customer Support.

5151

Passthrough is not supported
for error_condition

Type of Message: Error

Cause: Attempted to passthrough an unsupported SQL statement or large output parameter values from TimesTen to the Oracle database.

Impact: Statement execution stopped.

User Action: Use a SQL statement that is supported for passthrough. Also, ensure that the SQL statement does not contain large output parameter values. For more information about the PassThrough attribute, see "PassThrough" in the Oracle TimesTen In-Memory Database Reference.

5152

Could not determine what
type of Oracle statement
that is being prepared.
Maybe a possible syntax
error.

OCI was not able to identify the type of statement being passed through. Check the syntax.

5153

operation is not allowed
for this type of Oracle
statement

A fetch was called on a non-SELECT PASSTHROUGH statement.

5155

Wrong number of parameters

The number of input parameters does not match the number of parameters set by the user.

5156

Too many parameters.
Maximum number of parameters
allowed is maximum_number

For passthrough operations, the number of input parameters exceeds the maximum allowed.

5158

Oracle compilation error:
error

The TimesTen Cache operation encountered an Oracle database compilation error. Contact TimesTen Customer Support.

5159

Index owner.name was
converted to a non-unique
index because table
owner.name is a member of
an autorefreshed cache group.

This is a warning. Any unique index created on a table in an autorefresh cache group is automatically converted to a non-unique index.

5160

Failed to prepare Oracle
objects for datastore
duplication: details

Can occur during database duplication. Some Oracle database objects are missing or are in use by another application. Additional details may be displayed.

5161

Conflicting concurrent
updates to bipropagated rows

See "PROPAGATE cache table attribute" in Oracle TimesTen Application-Tier Database Cache User's Guide.

5162

Could not register Oracle
failover callback function

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

5163

Oracle failover failed with
event event_ID. Retried
for number minutes

TimesTen was not able to reestablish a connection to the Oracle database. 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 database table. You must either remove the CASCADE DELETE foreign key on the cache table or add one on the Oracle database 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 database type mode is required for the database that contains the cache group.

5170

Duplicate completed
successfully but the cache
metadata will be updated
after the cache and
replication agents have been
started on the destination
store becuase of the reasons
stated below.

Metadata stored on the Oracle database for cache groups is updated by the cache and replication agents after they are started and they are able to connect to the Oracle database. 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 the Oracle database.

5181

Oracle column maximum byte
length is restricted to 4000
bytes for column column_name

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

5182

TimesTen Cache is supported
only with Oracle Database
Server release 10.2 and
later.

Version of the Oracle database server is not supported. The Oracle database 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 database synonym that is owned by another user in the Oracle database. 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 database privileges to the cache admin user.

5186

The OCI client library in use
does not contain required
routines to support caching
LOBs from Oracle.

The application is linked with an OCI library that was not shipped with TimesTen.

5187

Caching LOBs from Oracle
requires using an OCI client
library provided by the
TimesTen installation, or
other versions of OCI client
supported by TimesTen.

The application is linked with an OCI library that was not shipped with TimesTen.

5190

Table table not found.
error_condition

Type of Message: Warning

Cause: The specified TimesTen table does not exist.

Impact: The TimesTen Cache configuration parameters for the ttCacheConfig built-in procedure are set, but will not be applied until the specified TimesTen table is created.

User Action: Ensure that the specified table exists on TimesTen.

5201

Operations for Cache Agent
are not allowed for
temporary data stores

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

5203

Could not find library
library_name

On UNIX only, the Oracle database client library libcIntsh.sl or libcIntsh.so cannot be found under $ORACLE_HOME/lib or $ORACLE_HOME/lib32. Check your $ORACLE_HOME environment variable.

5204

Environment variable PATH
not set

To cache Oracle database 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 database 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 the Oracle database, there are already existing cache groups in the database. Since the corresponding Oracle database tables may have been altered before the tracking started, there may be an inconsistency between the cache schema and the Oracle database schema. Verify that the TimesTen and Oracle database 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.

5210

Oracle unique constraint
violation error/warning in
OCI_function:
Oracle_error_number

Unique constraint violation occurred on the Oracle database in the named OCI function.

5211

Oracle out of resource
error/warning in
OCI_function:
Oracle_error_number

Out of resource error occurred on the Oracle database in the named OCI function.

5212

No longer connected to
Oracle error/warning in
OCI_function:
Oracle_error_number

Connection lost to the Oracle database.

5213

Bad Oracle login
error/ warning in
OCI_function:
Oracle_error_number

Oracle database login error.

5214

Not connected to Oracle
error/warning in
OCI_function:
Oracle_error_number

No connection to the Oracle database.

5215

Oracle resource timeout
error/warning in
OCI_function:
Oracle_error_number

Oracle database resource timeout occurred on the Oracle database in the named OCI function.

5216

Oracle resource busy
error/warning in
OCI_function:
Oracle_error_number

Oracle database resource busy.

5217

Oracle deadlock
error/ warning in
OCI_function:
Oracle_error_number

Oracle database deadlock occurred on Oracle database during the named OCI function.

5218

Bad parameter to Oracle
error/warning in
OCI_function:
Oracle_error_number

Bad parameter specified for the named OCI function.

5219

Temporary Oracle connection
failure error/warning in
OCI_function:
Oracle_error_number

Temporary TimesTen Cache failure occurred on the Oracle database during the named OCI function.

5220

Permanent Oracle connection
failure error/warning in
OCI_function:
Oracle_error_number

Permanent TimesTen Cache failure occurred on the Oracle database during the named OCI function.

5221

Oracle syntax
error/warning in
OCI_function:
Oracle_error_number

Oracle database syntax error occurred on the Oracle database in the named OCI function.

5222

Oracle constraint violation
error/warning in
OCI_function:
Oracle_error_number

Constraint violation occurred on the Oracle database in the named OCI function.

5223

Oracle orphan violation
error/warning in
OCI_function:
Oracle_error_number

Orphan violation occurred on the Oracle database in the named OCI function.

5224

Oracle foreign key
violation error/warning in
OCI_function:
Oracle_error_number

Foreign key violation occurred on the Oracle database in the named OCI function.

5225

Oracle recovery in progress
error/warning in
OCI_function:
Oracle_error_number

Recovery in progress error occurred on the Oracle database in the named OCI function.

5226

Oracle data truncation
error/warning in
OCI_function:
Oracle_error_number

Data truncation error occurred on the Oracle database in the named 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 the Oracle database. 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 database 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 the Oracle database. 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.

3. Restart the agents.

5252

Could not retrieve the
cache admin user and
password

Failed to retrieve the cache administration user ID and password for asynchronous writethrough cache groups.

5254

Operation failed. Could not
find AWT cache group
information.

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 Database errors reported by TimesTen" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

5257

Cache admin user and/or
password could not be found.
Changes via AWT cannot be
applied without them.

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

5259

Failed to store AWT runtime
information for data store
data_store_name on Oracle

TimesTen could not store the state information for AWT. Check the state of the Oracle database server if the error persists.

5260

Failed to store AWT runtime
information for data store
data_store_name on Oracle.
Wrong number of rows
updated. Should be 1 but
value were updated.

The state information for AWT is corrupt. If the problem persists, contact TimesTen Customer Support.

5261

Failed to read AWT runtime
information for data store
data_store_name on Oracle

TimesTen could not read the state information for AWT. Check the state of the Oracle database server if the error persists.

5262

Could not store the
autorefresh bookmarks
because the autorefresh
state should be state but
instead was state

The system is trying to store bookmarks for AUTOREFRESH when the AUTOREFRESH state is not appropriate. If the problem persists, contact TimesTen Customer Support.

5263

owner.table is not an
autorefresh cache group

The cache or replication agent tried to store AUTOREFRESH bookmarks on a non-AUTOREFRESH cache group. If the problem persists, contact TimesTen Customer Support.

5264

Master data store state not
active or standby. State is
state.

You must specify the ACTIVE or STANDBY state for the database.

5265

Internal error: error_details

Internal error. Contact TimesTen Customer Support.

5266

Cache ddl lock request
denied because of
time-out\Owner info: message

This is a cache DDL lock timeout information. The lock owner information is specified in message.

5267

The operation failed
because the data store is
marked dead and name
option is set to value

The autorefresh cache groups must be recovered before the operation can be performed. For more information about autorefresh cache group recovery, see "Configuring recovery method for certain cache groups" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

5268

Changing the recovery
method to none has caused
recovering cache groups to
be marked dead for all data
stores

All cache groups that were being recovered are marked dead since the recovery method has been changed to none.

5269

owner.name is not an
incrementally autorefreshed
cache group

The status can only be shown on incrementally autorefreshed cache group. The indicated table is not an incrementally autorefreshed cache group.

5275

Asynchronous writethrough
metadata not found error
in object: object

Contact TimesTen Customer Support.

5276

Asynchronous writethrough
role or state change
occurred error in
object: object

Contact TimesTen Customer Support.

5277

Timeout while updating
active standby metadata on
Oracle error in object:
object

Contact TimesTen Customer Support.

5278

Statement over 4000 bytes:
statement

Statement is over accepted limit of 4000 bytes.

5279

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 reexecute 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 database has been lost. Check the status of the Oracle database.

5289

Operation failed because
user lacks Oracle RDBMS
privilege privilege.
Action_statement.

Grant the user the appropriate privilege within the Oracle database.

5293

Cache Propagation will be
serialized for AWT cache
table owner.table because the
following Oracle unique
indexes and constraints on
this table contain cached
columns that do not have
corresponding unique indexes
and constraints on TimesTen:
lst_oracle_indexes_constraints

Type of Message: Warning

Cause: The specified unique constraints and indexes on the cached Oracle database table do not have corresponding unique indexes and constraints on TimesTen.

Impact: Transactions that contain DML to the specified table will not be propagated in parallel to the Oracle database. This will impact the throughput to the Oracle database.

User Action: Ensure that the unique constraints and indexes on the cached Oracle database have corresponding unique indexes and constraints on the TimesTen table.

5294

For Oracle tables that are
cached in an AWT cache group,
propagation will be
serialized because there are
Oracle tables with unique
indexes and constraints that
do not have corresponding
unique indexes and
constraints on TimesTen.

Type of Message: Warning

Cause: Some unique constraints and indexes on the cached Oracle database table do not have corresponding unique indexes and constraints on TimesTen.

Impact: Transactions that contain DML will not be propagated in parallel to the Oracle database. This will impact the throughput to the Oracle database.

User Action: Ensure that the unique constraints and indexes on the cached Oracle database have corresponding unique indexes and constraints on the TimesTen table.

5295

Propagation will be
serialized on AWT cache table
owner.table because the
following Oracle foreign key
constraints on this table
contain cached columns that
do not have corresponding
foreign key constraints on
TimesTen:
lst_oracle_fk_constraints

Type of Message: Warning

Cause: The specified foreign key constraints on the cached Oracle database table do not have corresponding foreign key constraints on TimesTen.

Impact: Transactions that contain DML to the specified table will use serialized propagation to the Oracle database. This will impact the throughput to the Oracle database.

User Action: To ensure the best throughput to the Oracle database, recreate the TimesTen cache group using the foreign key constraint. If you cannot recreate the TimesTen cache group, transactions will use serialized propagation to the Oracle database. For more information on dropping a TimesTen cache group, see "Dropping a cache group" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on creating a cache group, see "Creating a cache group" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

5296

Propagation will be
serialized on AWT cache table
owner.table because the
following Oracle unique
indexes, unique or foreign
key constraints on this table
contain cached columns that
do not have corresponding
constraints on TimesTen:
lst_oracle_constraints

Type of Message: Warning

Cause: The specified unique indexes, unique constraints and foreign key constraints on the cached Oracle database table do not have corresponding constraints on TimesTen.

Impact: Transactions that contain DML to the specified table will use serialized propagation to the Oracle database. This will impact the throughput to the Oracle database.

User Action:

1. Ensure that the unique constraints and indexes on the cached Oracle database have corresponding unique indexes and constraints on the TimesTen table.

2. To ensure the best throughput to the Oracle database, recreate the TimesTen cache group using the foreign key constraint. If you cannot recreate the TimesTen cache group, transactions will use serialized propagation to the Oracle database. For more information on dropping a TimesTen cache group, see "Dropping a cache group" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on creating a cache group, see "Creating a cache group" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

5297

The following Oracle foreign
key constraints on AWT cache
table owner.table contain
cached columns that do not
have corresponding foreign
key constraints on TimesTen:
lst_oracle_constraints

Type of Message: Informational

Cause: The specified table on the cached Oracle database has a foreign key constraint that does not have corresponding foreign key constraint on TimesTen.

Impact: None.

User Action: None.

5298

Propagation will be
serialized because there are
Oracle tables with unique
indexes, unique or foreign
key constraints that are
cached in an AWT cache group
with parallel propagation
enabled that do not have the
corresponding constraint on
TimesTen.

Type of Message: Warning

Cause: Some unique indexes, unique constraints and foreign key constraints on the cached Oracle database table do not have corresponding constraints on TimesTen.

Impact: Transactions that contain DML to the specified table will use serialized propagation to the Oracle database. This will impact the throughput to the Oracle database.

User Action:

1. Ensure that the unique constraints and indexes on the cached Oracle database have corresponding unique indexes and constraints on the TimesTen table.

2. To ensure the best throughput to the Oracle database, recreate the TimesTen cache group using the foreign key constraint. If you cannot recreate the TimesTen cache group, transactions will use serialized propagation to the Oracle database. For more information on dropping a TimesTen cache group, see "Dropping a cache group" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on creating a cache group, see "Creating a cache group" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

5299

There are Oracle tables with
unique indexes, unique or
foreign key constraints that
are cached in an AWT cache
group with parallel
propagation enabled that do
not have the corresponding
constraint on TimesTen.

Type of Message: Informational

Cause: Some Oracle database tables have unique indexes, unique constraints, or unique foreign key constraints that do not have corresponding on TimesTen.

Impact: None.

User Action: None.

5300

Parameter bindings are not
allowed in the select
statement

Type of Message: Error

Cause: The Oracle database select query you specified for the built-in procedure or command contains parameter bindings. Parameter bindings are not supported by the ttTableSchemaFromOraQueryGet built-in procedure, the ttLoadFromOracle built-in procedure, and the createAndLoadfromOraQuery command.

Impact: The call to the built-in procedure or command failed.

User Action: Remove the parameter bindings from the Oracle database select query and call the built-in procedure or command.

For more information on the ttTableSchemaFromOraQueryGet built-in procedure, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttLoadFromOracle built-in procedure, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information on the createAndLoadfromOraQuery command, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.

5301

The Load From Oracle feature
cannot be used to load cache
group tables

Type of Message: Error

Cause: The TimesTen table you specified for the built-in procedure or command is part of a cache group. The ttTableSchemaFromOraQueryGet built-in procedure, the ttLoadFromOracle built-in procedure, and the createAndLoadfromOraQuery command do not support Loading into TimesTen cache group tables.

Impact: The call to the built-in procedure or command failed.

User Action: Specify a table that is not part of a cache group and call the built-in procedure or command.

For more information on the ttTableSchemaFromOraQueryGet built-in procedure, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttLoadFromOracle built-in procedure, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information on the createAndLoadfromOraQuery command, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.

5302

The Load From Oracle feature
cannot be used with
passthrough level 3

Type of Message: Error

Cause: The PassThrough attribute of the TimesTen Cache is set to 3.

Impact: The call to the built-in procedure or command failed.

User Action: Specify a PassThrough level that is not 3 for the TimesTen Cache and call the built-in procedure or command. For more information on PassThrough levels, see "PassThrough" in the Oracle TimesTen In-Memory Database Reference.

For more information on the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information on the createAndLoadfromOraQuery command, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.

5303

Create table statement
generated is too long

Type of Message: Error

Cause: The built-in procedure or command generated a CREATE TABLE statement that exceeds the maximum length for a SQL statement. The CREATE TABLE statement was generated by the ttTableSchemaFromOraQueryGet built-in, or the ttLoadFromOracle built-in, or the createAndLoadfromOraQuery command.

Impact: The generated CREATE TABLE statement cannot be executed.

User Action: Modify the Oracle database SQL statement to shorten the length of the generated CREATE TABLE statement and call the built-in procedure or command. For more information on system limits, see "System limits and defaults" in the Oracle TimesTen In-Memory Database Reference.

For more information on the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information on the createAndLoadfromOraQuery command, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.

5304

The Load From Oracle feature
cannot be used to load LOB
columns

Type of Message: Error

Cause: The TimesTen table you specified for the built-in procedure or command contains LOB data types. TimesTen tables that contain LOB data types are not supported by the ttTableSchemaFromOraQueryGet built-in, the ttLoadFromOracle built-in, and the createAndLoadfromOraQuery command.

Impact: The call to the built-in procedure or command failed.

User Action: Remove or change the LOB data types to a supported type and call the built-in procedure or command.

For more information on the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information on the createAndLoadfromOraQuery command, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.

5305

Oracle query does not match
TimesTen table schema.
Mismatched number of columns
between the TimesTen table
(num_tt_column columns) and
Oracle query (num_ora_column
columns)

Type of Message: Error

Cause: The number of columns in the TimesTen table does not match the number in the Oracle database query result set. The mismatch was detected when you executed the ttTableSchemaFromOraQueryGet built-in, or the ttLoadFromOracle built-in, or the createAndLoadfromOraQuery command.

Impact: The call to the built-in procedure or command failed.

User Action: Examine the TimesTen table and the Oracle database query to resolve the mismatch. Then call the built-in procedure or command.

For more information on the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information on the createAndLoadfromOraQuery command, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.

5306

The Oracle statement must be
a valid select query.

Type of Message: Error

Cause: The Oracle database statement you provided is not a valid select query. The Oracle database statement must be a valid select query to use the ttTableSchemaFromOraQueryGet built-in, or the ttLoadFromOracle built-in, or the createAndLoadfromOraQuery command.

Impact: The call to the built-in procedure or command failed.

User Action: Ensure that the Oracle database statement is a valid select query and call the built-in procedure or command.

For more information on the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information on the createAndLoadfromOraQuery command, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.

5307

The Load From Oracle feature
cannot be used to load
materialized view tables or
detail tables of views

Type of Message: Error

Cause: You attempted to load data into a TimesTen materialized view or a detailed view using the built-in or command. Loading data into TimesTen materialized views and detailed views is not supported by the ttTableSchemaFromOraQueryGet built-in, the ttLoadFromOracle built-in, and the createAndLoadfromOraQuery command.

Impact: The call to the built-in procedure or command failed.

User Action: Loading data into TimesTen materialized views and detailed views is not supported by the ttTableSchemaFromOraQueryGet built-in, or the ttLoadFromOracle built-in, or the createAndLoadfromOraQuery command.

For more information on the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information on the createAndLoadfromOraQuery command, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.

5308

The Load From Oracle feature
cannot be used to load
temporary tables

Type of Message: Error

Cause: You attempted to load data into a TimesTen temporary table using the built-in or command. Loading data into TimesTen temporary tables is not supported by the ttTableSchemaFromOraQueryGet built-in, the ttLoadFromOracle built-in, and the createAndLoadfromOraQuery command.

Impact: The call to the built-in procedure or command failed.

User Action: Loading data into TimesTen temporary tables is not supported by the ttTableSchemaFromOraQueryGet built-in, or the ttLoadFromOracle built-in, or the createAndLoadfromOraQuery command.

For more information on the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information on the createAndLoadfromOraQuery command, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.

5309

The Load From Oracle feature
cannot be used to load
dictionary tables

Type of Message: Error

Cause: You attempted to load data into a TimesTen dictionary table. Loading data into TimesTen dictionary tables is not supported by the ttTableSchemaFromOraQueryGet built-in, the ttLoadFromOracle built-in, and the createAndLoadfromOraQuery command.

Impact: The call to the built-in procedure or command failed.

User Action: Loading data into TimesTen dictionary tables is not supported by the ttTableSchemaFromOraQueryGet built-in, or the ttLoadFromOracle built-in, or the createAndLoadfromOraQuery command. For more information on dictionary tables, see "In-memory columnar compression of tables" in the Oracle TimesTen In-Memory Database SQL Reference.

For more information on the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information on the createAndLoadfromOraQuery command, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.

5311

AWT cache group with parallel
propagation enabled
constraint check: object
owner.name :
constraint_check_status

Type of Message: Informational

Cause: This informational message is in the daemon log while the constraint check is being performed.

Impact: None.

User Action: None.

5313

Load From Oracle Error: Data truncated for table
table_name, column
column_name, value value...

Type of Message: Error

Cause: TimesTen encountered a truncation error while trying to insert data from the Oracle database into the specified TimesTen column. The specified value might be a partial value.

Impact: The load operation is terminated. The load operation periodically commits and successful operations are not rolled back. Some data might have been imported into TimesTen before the operation terminated.

User Action: Modify the Oracle database query, or the TimesTen table, or both to ensure that the Oracle database data can be loaded into the specified TimesTen table.

To retry a failed parallel load operation, delete previously inserted rows from the TimesTen table to avoid duplicate rows.

5314

Load From Oracle Warning:
Cannot check for truncation
of char/nchar columns for
this load.

Type of Message: Warning

Cause: The Oracle database statement you specified could not be checked for truncation of CHAR and NCHAR values. Common causes for this are:

- The Oracle database statement you specified might contain an ORDER BY clause.

- The Oracle database statement you specified might exceed maximum query length once TimesTen rewrites the statement to be used by the ttLoadFromOracle built-in or the createAndLoadfromOraQuery command.

Impact: CHAR and NCHAR column values may be truncated by the ttLoadFromOracle built-in or the createAndLoadfromOraQuery command.

User Action: Review the daemon log for more details about the warning. If you require TimesTen to check for CHAR or NCHAR truncation, ensure that the column lengths in the Oracle database and TimesTen are the same. For more information on how to review the daemon log, see "Using the logs generated by the TimesTen daemon" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

5321

Could not get the maximum
reclaim cache size
configuration parameter

Type of Message: Error

Cause: The cache agent could not retrieve the maximum reclaim cache size configuration parameter. Review the daemon log for any additional error messages to determine a cause for the error message. For more information on how to review the daemon log, see "Using the logs generated by the TimesTen daemon" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

Impact: The cache agent will retry this operation later. Review the daemon log for any additional impacts.

User Action: Review the daemon log for any possible fixes.

5322

Could not set the maximum
reclaim cache size for the
session

Type of Message: Error

Cause: The cache agent could not set the maximum reclaim cache size for the session.

Impact: The cache agent will retry this operation later.

User Action: None.

5323

Maximum reclaim cache size
set to
max_reclaim_cache_size
for receiver_thread_track_id

Type of Message: Informational

Cause: The maximum reclaim cache size is now set to the specified value.

Impact: None.

User Action: None.

5324

There was an error while
getting the statistics for
interval interval_value ms:
detailed_error_message

Type of Message: Error

Cause: An error occurred while retrieving the autorefresh statistics for the specified interval. A detailed error message follows this message.

Impact: The autorefresh statistics are not returned.

User Action: Review the error message for possible fixes.

5325

Deferring autorefresh because
of unmarked records in log
table table_name.
(marked, unmarked, eoLog) =
(marked_rows, unmarked_rows,
max_sequence_num_in_log_tbl)

Type of Message: Informational

Cause: Too many unmarked autorefresh change log records exist in the specified log table.

Impact: The autorefresh operation for the TimesTen cache group is temporarily deferred.

User Action: None.

5326

max_reclaim_cache_size
setting must be less than
the total temporary space
size (ttl_temp_space MB)

Type of Message: Error

Cause: You specified a maximum reclaim buffer size for the cache agent that is greater than the total temporary space size.

Impact: The specified reclaim buffer size for the cache agent is not set.

User Action: Use the CacheAgentCommitBufSize parameter of the ttDBConfig built-in procedure to specify a reclaim buffer size that is less than the total temporary space size. For more information about the ttDBConfig built-in procedure, see "ttDBConfig" in the Oracle TimesTen In-Memory Database Reference.

5800

Could not allocate a
statement handle

The TimesTen cache agent was not able to allocate either an Oracle database 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.

5901

The Oracle refresh log
table, log_table_name, for
base table, owner.table,
cannot be found.

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

Internal error: The length of
the name of the Oracle object
has exceeded the expected
length.

Type of Message: Internal error

Cause: The length of the name of the Oracle database object has exceeded the expected length.

Impact: The severity of the impact is unknown and requires additional diagnosis.

User Action: Contact TimesTen Customer Support.

5903

Autorefresh log table was
truncated during incremental
refresh. Full refresh will
take place.

Type of Message: Error

Cause: Rows in the autorefresh log table were deleted during an incremental refresh.

Impact: TimesTen is performing a full refresh to recover the autorefresh log table.

User Action: Do not delete rows from the TimesTen internal tables TT_XX_YYYY, where XX is the two digit version number and YYYY is the assigned TimesTen name.

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 the Oracle database 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 database 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 database SID for the DSN.

5913

Table parameter should be
NULL

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

5914

not found in Oracle.

The TimesTen cache agent could not find the Oracle database table to be cached. Check if the table exists on the Oracle database. 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 database table that was cached has been dropped in the Oracle database 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 the Oracle database users" in the Oracle TimesTen Application-Tier Database Cache User's Guide for details.

5918

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

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

5919

The type name 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 database 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 the Oracle database.

5921

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

Verify that the Oracle database 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 the Oracle database. Verify the Oracle database instance is running and the network connection is also available. Check the user error log for any errors.

5925

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

The cache administrator does not have Oracle database 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.

5926

An error occurred while
processing a child table

Type of Message: Error

Cause: TimesTen autorefreshed a child table before the parent table from a multi-table cache group causing a foreign key violation.

Impact: The autorefresh cycle fails. TimesTen will retry the autorefresh operation.

User Action: None.

5935

Could not validate Oracle
login: uid = Oracle_UID, pwd
= HIDDEN,
OracleNetServiceName  =
Oracle_Service_Name, TNS_
ADMIN = "tns_admin" ,
ORACLE_HOME= "Oracle_home"

TimesTen Cache failed to verify the Oracle database login for named user ID.The common causes of this error are:

The specified UID/PWD is incorrect.

The OracleNetServiceName setting is incorrect.

The Oracle database listener is down.

The Oracle database is down.

Troubleshoot the causes and then retry the operation.

5936

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

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 before 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 the Oracle database 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.

5943

The source datastore cache
admin uid cacheUid is
different from the
destination datastore cache
admin uid cacheUid.

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 Customer 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 database privileges to create and store metadata information on the Oracle database server. Either grant the appropriate privileges to the cache admin user on the Oracle database server or install the metadata objects manually.

5953

The string string 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 database server, then the cache group is no longer valid. You will need to recreate the cache group.

5954

Error while informing the
replication_or_cache_agent
agent of a configuration
change: configuration_change

Type of Message: Warning

Cause: You attempted to call the ttCacheConfig built-in procedure, but the specified agent is down. For more information on the ttCacheConfig built-in procedure, see "ttCacheConfig" in the Oracle TimesTen In-Memory Database Reference.

Impact: The specified configuration change cannot be passed to the specified agent.

User Action: Start the specified agent.

- Cache agent:

Call the ttCacheStart built-in procedure to start the cache agent. For more information on the ttCacheStart built-in procedure, see "ttCacheStart" in the Oracle TimesTen In-Memory Database Reference.

- Replication agent:

Call the ttRepStart built-in procedure to start the replication agent. For more information on the ttRepStart built-in procedure, see "ttRepStart" in the Oracle TimesTen In-Memory Database Reference.

5955

Autorefresh log table space
monitoring and management
will not be done since the
cache admin user's tablespace
management setting on ORACLE
is not AUTO

Type of Message: Warning

Cause: The tablespace management setting for the Oracle database is set to AUTO.

Impact: The monitoring and management feature for the autorefresh log tablespace on the Oracle database is not enabled.

User Action: If you want to enable the monitoring and management feature for the autorefresh log tablespace on the Oracle database, see "Specifying Segment Space Management in Locally Managed Tablespaces" in the Oracle Database Administrator's Guide.

5956

Autorefresh log table space
monitoring and management
will not be done since there
are no autorefresh trigger
log tables in cache admin
user's schema

Type of Message: Informational

Cause: No autorefresh change log tables exist in the schema of the cache administration user. A common cause for this is that the cache agent was started before the read-only cache groups were created.

Impact: The monitoring and management feature for the autorefresh log tablespace on the Oracle database is not enabled.

User Action: None.

5957

Failed to retrieve the upper
bound of the SELECT
statement.

Type of Message: Error

Cause: The cache agent cannot retrieve the upper bound that is used by the query that retrieves the rows to be refreshed.

Impact: The cache agent retries the autorefresh operations.

User Action: None.

5958

autorefresh_step duration
time: duration_time ms

Type of Message: Informational

Cause: The cache agent completed a step from the autorefresh work flow. The duration of the step was recorded in the autorefresh change log table.

Impact: None.

User Action: None.

5959

Change log table:
change_log_table,
COUNT(logseq): num_rows,
MIN(logseq): min_bookmark,
MAX(logseq): max_bookmark,
curSOLog:
cache_agent_current_bookmark,
retrieved curSOLog:
table_current_bookmark

Type of Message: Error

Cause: The cache agent encountered an error while retrieving information from the autorefresh change log table. The statistics from the table are specified in the message.

Impact: The cache agent rolls back and retries the autorefresh operation.

User Action: If the error persists, contact TimesTen Customer Support.

5960

Change log table:
change_log_table, curSOLog:
current_bookmark was not
found

Type of Message: Error

Cause: The cache agent could not find the current autorefresh bookmark from the specified change log table.

Impact: The cache agent rolls back and retries the autorefresh operation.

User Action: If the error persists, contact TimesTen Customer Support.

5961

Successfully executed the
following Oracle SQL
statement: sql_statement

Type of Message: Informational

Cause: TimesTen successfully executed the specified SQL statement in the Oracle database.

Impact: None.

User Action: None.

5990

A fatal error occurred in
the cache agent.

Cache agent reports an irrecoverable error during autorefresh. Contact TimesTen Customer Support and send TimesTen the latest daemon/sys log.

5991

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 database objects that were used in a previous autorefresh process. Before dropping the orphaned object, the agent locks the FT_USER_COUNT table so that no other agent can create new or drop old Oracle database objects. This warning is triggered when the agent was 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

The USER_COUNT table on the Oracle database is not compatible with this version of TimesTen Cache. Uninstall and reinstall the Oracle database objects for autorefresh manually. For more information, see "Manually creating Oracle Database objects for autorefresh cache groups" in the Oracle TimesTen Application-Tier Database Cache User's Guide for details.

5995

Cache agent is shutting down.

Informational message.

Errors 6000 - 6999

Error number
Error or warning message
Details

6000

Bad locking level
for data store
connection

Only row-level and database-level locking is allowed. Reset LockLevel attribute.

6001

Lock request denied
because of conflict
on conditional
request Details:
error_description

Lock request denied because of conflict on conditional request. This error only appears in the TimesTen user error log. For information on lock resources and modes indicated in this message, see "ttXactAdmin" in Oracle TimesTen In-Memory Database Reference.

6002

Lock request denied
because of deadlock
Details:
error_description

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

6003

Lock request denied
because of time-out
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.

6004

Bad transaction
isolation level

An ODBC application can never get this message.

6005

Lock request denied
because of not enough
temp space available:
error_description

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

6006

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

The lock-wait interval is out of range. Call 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 Customer 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 Customer 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 with 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 statement 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.

6113

SQL statement has been
canceled

The currently executing SQL statement was canceled by user request.

6200

New value for permanent data
region 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 memory region size.

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

6203

Overflow in
converting 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 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.

6220

Permanent data region free
space insufficient to
allocate byte_count bytes of
memory

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

6221

Temporary data region free
space insufficient to
allocate byte_count bytes of
memory

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

6222

Permanent data region in use
size has exceeded
PermWarnThreshold

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

6223

Temporary data region in use
size has exceeded
TempWarnThreshold

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

6226

Ignoring value
requested for first
connection attribute
'attribute_name' --
value currently in
use: used_value,
requested value:
requested_value

Type of Message: Warning

Cause: You attempted to connect to a database with a different value for the specified first connection attribute than the value given in the first connection to the database.

Impact: TimesTen ignores the value not in use for the specified first connection attribute and connects to the database.

User Action: Close all active connections to the database, unload the database from memory, and retry the operation.

To unload the database from memory, you may need to set the RAM policy of the database to manual or inUse. For more information on setting the RAM policy to manual or inUse, see "Specifying a RAM policy" in the Oracle TimesTen In-Memory Database Operations Guide.

6228

Invalid value
(specified_value)
for attribute_name
connection attribute
-- value must be
correct_value

Type of Message: Error

Cause: You attempted to connect to a database with a different value for the specified connection attribute than the value given in the database creation process.

Impact: TimesTen cannot connect to the database.

User Action: To modify the specified connection attribute, destroy and recreate the database with the desired value for the specified connection attribute. For more information on connection attributes, see "Connection Attributes" in the Oracle TimesTen In-Memory Database Reference.

6229

Fatal error: cannot
rollback transaction
because out-of-space
condition prevents
re-inserting old
values into index(es).
Reconnect with a
larger PermSize

Type of Message: Internal Error

Cause: A transaction cannot rollback because your database has run out of available disk space. A common cause for this is that your PermSize attribute is set too low.

Impact: The database is invalidated. If the ramPolicy parameter of the ttRamPolicySet built-in procedure is set to always, automatic recovery might fail. For more information on the ttRamPolicySet built-in procedure, see "ttRamPolicySet" in the Oracle TimesTen In-Memory Database Reference.

User Action: Check and modify the values of PermSize and TempSize so that your database has at least five percent available space on each region. For more information on how to check the amount of memory in use by the database, see "Check the amount of memory allocated to the database" in the Oracle TimesTen In-Memory Database Troubleshooting Guide. For more information on how to increase the values of PermSize and TempSize, see "Specifying the size of a database" in the Oracle TimesTen In-Memory Database Operations Guide. If you still receive this error, contact TimesTen Customer Support.

6230

Cannot perform DML
such as update and DDL
such as create index
or alter table in same
transaction when using
DDLCommitBehavior=1

This error is returned when using DDLCommitBehavior=1. If DDLCommitBehavior=1, TimesTen allows multiple DML and DDL statements in the same transaction. However, some mixes of DML and DDL in the same transaction while using DDLCommitBehavior=1 are no longer allowed. For example, you will see this error when updating rows in a table and then creating an index on that same table (or updating rows in a table and then resizing that table's hash index with ALTER TABLE ... PAGES = n).

To prevent this error, do not mix DML and DDL in the same transaction.

Ensure that the DDL operation is in its own transaction.

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. For the complete list of flags, see "ttOptSetFlag" in the Oracle TimesTen In-Memory Database Reference.

7018

Creation of user
objects in system-user
schemas is not allowed

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.

7022

Recovery must increase size
of permanent data region;
specify a permanent region
size of at least
megabyte_count megabytes

The redo log indicates that a grow operation took place after the most recent checkpoint.

7023

Unable to rebuild
nonpersistent
structures during redo
(error at step
number)

Internal error. Contact TimesTen Customer Support.

7024

Bad sample string
('string'). Format is
'<int> ROWS' or
'<float> PERCENT'

The sample string specified does not have the correct format.

7025

Illegal use of
reserved keyword
keyword

Type of Message: Error

Cause: You specified an identifier or user name that is a keyword reserved by TimesTen.

Impact: TimesTen cannot perform the operation.

User Action: Select a different identifier or user name and retry the operation. If you want to perform an operation with an already existing identifier or user name registered with the specified keyword, add quotation marks to the specified identifier or user name and retry the operation. For more information on reserved words, see "Reserved Words" in the Oracle TimesTen In-Memory Database SQL Reference.

7026

Illegal attempt to
alter system table
'table_name'

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.

7030

Expression provided
as argument for
parameter_name
paremeter message

An expression cannot be provided as an argument for a parameter_name.

7050

Undefined trace
component
'component_name'

Specified a trace component that is not defined.

7051

Error in setting-up
TimesTen traces:
'trace_names'

Invalid trace command or function, or unable to create trace output file.

7052

Cannot disable thread
support after it has
already been enabled

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

Type of Message: Error

Cause: The specified table does not have a unique index that can be used for replication.

Impact: TimesTen cannot replicate the specified table.

User Action: Ensure that every table has a unique index or a primary key. For more information, see "Table requirements and restrictions for classic replication schemes" in the Oracle TimesTen In-Memory Database Replication Guide.

8001

Attempt to read invalid
LSN log record

Type of Message: Error

Cause: You attempted to read an invalid LSN log record.

Impact: TimesTen cannot read the LSN log record.

User Action: Specify a valid log file number and retry the operation.

8002

Cannot drop replicated
table, index, or sequence

Type of Message: Error

Cause: You attempted to use a SQL UPDATE statement to drop a replicated table, index, or sequence.

Impact: TimesTen cannot perform the update operation.

User Action: To drop a table, index, or sequence that is part of a replication scheme, alter the replication scheme using the ALTER REPLICATION SQL statement. For more information, see "ALTER REPLICATION" in the Oracle TimesTen In-Memory Database SQL Reference.

8003

Update older than
TimeStamp of existing row

Type of Message: Error

Cause: You attempted to perform an update that is older than the current timestamp for the row in the database.

Impact: TimesTen cannot perform the update operation. If configured, TimesTen will generate a report of the conflict. For more information, see "Reporting conflicts to a text file" in the Oracle TimesTen In-Memory Database Replication Guide.

User Action: Ensure that your update operation is out of date. If that is the case, consider discarding the UPDATE operation.

8004

Column owner.table.column
cannot be used for
replication timestamp
checking if in an index or
added by ALTER TABLE or if it
is columnar; and must be
binary(8) with NULL values
allowed

Type of Message: Error

Cause: You attempted to use the specified column for replication timestamp conflict resolution.

Impact: TimesTen cannot use the specified column to perform replication timestamp conflict resolution.

User Action: Ensure that the specified timestamp column is not part of an index, is of type BINARY(8) NULL, and was not added as part of an ALTER TABLE statement. For more information, see "Including a timestamp column in replicated tables" in the Oracle TimesTen In-Memory Database Replication Guide.

8005

Invalid update rule for
timestamp-based conflict
checking

Type of Message: Error

Cause: You did not specify a valid SYSTEM or USER parameter for the UPDATE BY clause.

Impact: TimesTen cannot complete the SQL ALTER REPLICATION or the SQL CREATE REPLICATION operation.

User Action: Ensure that your UPDATE BY clause is correctly defined for the ALTER REPLICATION or CREATE REPLICATION statement. Then, retry the operation. For more information, see “ALTER REPLICATION” and “CREATE REPLICATION” in the Oracle TimesTen In-Memory Database SQL Reference.

8006

Application must set
timestamp column with
'UPDATE BY USER'

Type of Message: Error

Cause: You are attempting to update a table that has enabled replication timestamp conflict resolution and contains an UPDATE BY USER clause. However, no timestamp value is defined.

Impact: TimesTen cannot perform the update operation.

User Action: Ensure that your replication timestamp conflict resolution column contains a valid timestamp value. Then, retry the operation. For more information, see “Configuring the CHECK CONFLICTS clause” in the Oracle TimesTen In-Memory Database Replication Guide.

8007

Cannot change aging
attributes or add/drop
aging policy of replicated
tables while replication
Agent is running

Type of Message: Error

Cause: You attempted to change the aging attributes, or add or drop an aging policy of replicated tables while the replication agent is running.

Impact: TimesTen cannot perform the operation.

User Action: Stop the replication agent and retry the operation. For more information about how to stop the replication agent, see “Starting and stopping the replication agents” in theOracle TimesTen In-Memory Database Replication Guide.

8009

Transaction Log API Buffer
size too small or too large

Type of Message: Error

Cause: You specified a transaction log buffer size that is out of the supported range for XLA. This message is followed by another message that describes the details of the failure.

Impact: TimesTen cannot perform the XLA operations.

User Action: Check the accompanying error message and consider increasing the transaction log buffer size. For more information, see "Increase transaction log buffer size when using XLA" in the Oracle TimesTen In-Memory Database Operations Guide.

8010

Unable to attach to XLA
segment

Type of Message: Error

Cause: TimesTen cannot attach to the XLA segment due to an environment issue. This message is followed by another message that describes the details of the failure.

Impact: TimesTen cannot perform the operation.

User Action: Check the accompanying error messages in the log to determine a possible solution to the environment issue.

8011

Unable to re-configure
active XLA segment

Type of Message: Error

Cause: You attempted to change the transaction log buffer size in an active transaction.

Impact: TimesTen cannot reconfigure the XLA segment.

User Action: Contact TimesTen Customer Support.

8012

Table with given ID not
found

Type of Message: Error

Cause: Table with the user-specified ID does not exist in the database.

Impact: TimesTen cannot correctly complete a full (non-incremental) autorefresh on the cache group.

User Action: Check the accompanying error messages in the log and contact TimesTen Customer Support.

8013

Attempt to specify illegal
version

Type of Message: Error

Cause: You specified an invalid TimesTen release version.

Impact: Applications that call the ttXlaSetVersion function cannot execute correctly. For more information on the ttXlaSetVersion function, see "ttXlaSetVersion" in the Oracle TimesTen In-Memory Database C Developer's Guide.

User Action: Ensure that your TimesTen XLA version is the same version (or an earlier version) as the actualVersion output from the ttXlaGetVersion function. For more information on the ttXlaGetVersion function, see "ttXlaGetVersion" in the Oracle TimesTen In-Memory Database C Developer's Guide.

8016

No replication buffer
configured

Type of Message: Error

Cause: TimesTen does not have a replication buffer configured.

Impact: The transaction log buffer cannot store updates.

User Action: Contact TimesTen Customer Support.

8017

Foreign table has number
columns while local table
has number columns

Type of Message: Error

Cause: The tables that TimesTen is comparing have a different number of columns.

Impact: Table information received from the foreign table is not compatible with the local table definition.

User Action: None.

8018

Foreign table indexed on
different columns

Type of Message: Error

Cause: The tables that TimesTen is comparing have different primary key definitions.

Impact: TimesTen cannot execute the ttXlaApply function call and cannot update the target database.

User Action: Ensure that the table definitions are the same for your source and target databases.

For more information on the ttXlaApply function, see "ttXlaApply" in the Oracle TimesTen In-Memory Database C Developer's Guide.

8019

Foreign and local table
differ on column type type

Type of Message: Error

Cause: The tables that TimesTen is comparing have different column data types.

Impact: TimesTen cannot execute the ttXlaApply function call and cannot update the target database.

User Action: Ensure that the table definitions are the same for your source and target databases.

For more information on the ttXlaApply function, see "ttXlaApply" in the Oracle TimesTen In-Memory Database C Developer's Guide.

8020

Inconsistent row in update
description

Type of Message: Error

Cause: The ttXlaGenerateSQL function is attempting to retrieve a tuple that is not valid.

Impact: TimesTen cannot execute the ttXlaGenerateSQL function call.

User Action: Ensure that the ttXlaGenerateSQL function is retrieving the tuple correctly.

For more information on the ttXlaGenerateSQL function, see "ttXlaGenerateSQL" in the Oracle TimesTen In-Memory Database C Developer's Guide.

8021

System table ID invalid

Type of Message: Error

Cause: TimesTen cannot retrieve the table definition details for the specified table ID.

Impact: The function call fails.

User Action: Specify a valid table ID.

8023

Table row does not have
expected value

Type of Message: Error

Cause: The contents of the row do not match the expected values in the transaction log update.

Impact: TimesTen cannot execute the ttXlaApply function call.

User Action: Ensure that you specify a valid row structure for the ttXlaApply function.

For more information on the ttXlaApply function, see "ttXlaApply" in the Oracle TimesTen In-Memory Database C Developer's Guide.

8024

Illegal XLA record type

Type of Message: Error

Cause: The XLA record is invalid or unsupported.

Impact: TimesTen cannot execute the ttXlaApply function call.

User Action: Specify a valid XLA record for the ttXlaApply function.

For more information on the ttXlaApply function, see "ttXlaApply" in the Oracle TimesTen In-Memory Database C Developer's Guide.

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

Type of Message: Error

Cause: A replication peer has set the replication state of this database to FAILED. This happens when the amount of logs that the peer is holding for the database exceeds a user configurable threshold. For more information, see "Setting the log failure threshold" and "Subscriber failures" in the Oracle TimesTen In-Memory Database Replication Guide.

Impact: The TimesTen database is out of sync with the master database.

User Action: Recover the FAILED database and resume replication. For more information, see "Recovering a failed database" in the Oracle TimesTen In-Memory Database Replication Guide.

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

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

8041

Invalid replCTNArr slot

Internal error. Contact TimesTen Customer Support.

8042

ReplCTNArr slot is not
allocated

Internal error. Contact TimesTen Customer 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 "Views and materialized views in a replicated database" in the Oracle TimesTen In-Memory Database 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 the ttRepAdmin utility. 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.

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.

8052

Cannot commit transaction
that involves commit to
Oracle and TWOSAFE
replication handling

Cannot commit RETURN TWOSAFE transactions on tables in a TimesTen cache group.

8055

Variable sized data of size
size bytes exceeds maximum
allowed by replication

Type of Message: Error

Cause: The TimesTen replication agent encountered an out-of-line log record that has a data length that exceeds the maximum supported length for a replicated column. For more information on the maximum supported length for a replicated column, see "System limits and defaults" in the Oracle TimesTen In-Memory Database Reference.

Impact: TimesTen fails to replicate a transaction. The subscriber database is not synchronized with the master database.

User Action: Run the ttXactLog -v 3 utility on the master database and contact TimesTen Customer Support. For more information on the ttXactLog utility, see "ttXactLog" in the Oracle TimesTen In-Memory Database Reference.

8056

Temporary tables cannot be
defined in a replication
scheme

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 database is not in the ACTIVE state for a database that is part of an active standby replication scheme.

8063

Local store not completely
quiesced

This error is returned when an active database 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 database 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

Cannot 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 database 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 database when in the ACTIVE state.

8073

Failed to update XLA
bookmark :bookmark.

The replication agent on the standby database 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 database or locks held on XLA tables on the standby database.

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 database or locks held on XLA tables on the standby database.

8076

Bookmark reset due to
state change at store.

The state of the database 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 database 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 database or locks held on XLA tables on the standby database.

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.

8080

Variable data error
information type
information_type information

Type of Message: Error

Cause: This error message provides additional information for error message 8055.

Impact: None.

User Action: Contact TimesTen Customer Support.

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, call 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 call the built-in procedure ttRepTransmitSet with argument 1.

8097

Error getting parent table
during autorefresh bookmark
lookup

This is a runtime 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 database 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 Replication Guide.

8102

STORE store_name specified
more than once

A database can be specified at most once in a STORE clause of a CREATE REPLICATION or ALTER REPLICATION statement. See "Setting STORE attributes in a classic replication scheme" in the Oracle TimesTen In-Memory Database 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 a classic replication scheme" in the Oracle TimesTen In-Memory Database Replication Guide.

8104

ALTER or DROP ELEMENT for
element following DROP

An ALTER ELEMENT clause cannot follow a DROP ELEMENT clause for the same element in an ALTER REPLICATION statement. For more information, see "ALTER REPLICATION" in the Oracle TimesTen In-Memory Database SQL Reference.

8105

STORE store_name does not
have a MASTER, PROPAGATOR,
or SUBSCRIBER role for any
ELEMENT

It is permissible to define a STORE to a replication scheme without assigning it a replication role. However, doing this evokes this warning.

8106

STORE store_name specified
as both owner and
SUBSCRIBER for replication
ELEMENT element

A database cannot subscribe to the same element for which it is either the MASTER or PROPAGATOR. For more information, see "Database names" in the Oracle TimesTen In-Memory Database Replication Guide.

8107

Cannot specify both
ELEMENT DATASTORE and
ELEMENT TABLE or SEQUENCE
since the former already
covers all objects in the
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 Replication Guide.

8108

For TRANSMIT NONDURABLE, must
use the ELEMENT <elementname>
DATASTORE clause

Nondurable transmits require an ELEMENT DATASTORE clauses. See "Setting transmit durability on DATASTORE element" in the Oracle TimesTen In-Memory Database Replication Guide.

8109

Element element_name
will not have any
subscribers

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

Failure resetting replication
catchup status.

It occurs when you are trying to perform a duplicate operation from a node in an active standby database to another and the source node is not in the correct state. The duplicate operation fails. Try duplicating from the correct database, or setting the state of the source database.

8118

Column column_name of
table owner.table_name
is longer than the maximum
column size of num bytes
when used with replication.

The specified column violates the max size limit for replicated columns. The message indicates the maximum limit.

8119

Set name operation skipped
as the new name for the
element (element_name)
matches the current name.

The new name matches the existing name for the element. If you are attempting to change the element name, supply a unique name to the set operation.

8120

The TRANSMIT NONDURABLE
clause can only be used
with a DATASTORE element

This database attribute can only be specified for database replication elements.

8121

localhost, 127.0.0.1, ::1
or 0:0:0:0:0:0:0:1 cannot
be used as a host
identifier.

The IP address 'localhost' or any of its aliases cannot be used as a host identifier.

8122

The replication scheme
cannot begin with '_'

An attempt was made to create a replication scheme which begins with '_'.

8123

An ACTIVE STANDBY PAIR
scheme does not exist

Type of Message: Error

Cause: You attempted to use an ALTER ACTIVE STANDBY PAIR or DROP ACTIVE STANDBY PAIR statement on a database without an active standby pair replication scheme.

Impact: TimesTen cannot perform the operation.

User Action: None. For more information on active standby pair replication schemes, see "Defining an Active Standby Pair Replication Scheme" in the Oracle TimesTen In-Memory Database Replication Guide.

8124

Store DSN has been
specified as an ACTIVE
STANDBY PAIR node and a
SUBSCRIBER

Type of Message: Error

Cause: You attempted to use a CREATE ACTIVE STANDBY PAIR statement while attempting to designate the specified database as both a master database and a subscriber database.

Impact: TimesTen cannot create the active standby pair replication scheme.

User Action: Define the specified database as a master database or a subscriber database, and retry the operation. For more information on CREATE ACTIVE STANDBY PAIR, see "CREATE ACTIVE STANDBY PAIR" in the Oracle TimesTen In-Memory Database SQL Reference.

8125

The store cannot be
dropped from the ACTIVE
STANDBY PAIR scheme because
it is a master node

An attempt was made to drop a master database that is part of an active standby pair.

8126

An ACTIVE STANDBY PAIR
scheme already exists and
must be the only
replication scheme for the
store.

A database cannot be in two active standby pairs. An attempt was made to create an active standby pair using a database that is already in an active standby pair.

8127

Cannot create ACTIVE
STANDBY PAIR scheme because
another replication scheme
already exists.

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

object_type owner.name is
already part of the
replication scheme, or is
in the process of being
process

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

clause 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 clause table
owner.name because it is
part of a cache group. Use
clause 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_type owner.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 database that was not in a standby state. The operation is only permitted on databases 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 database 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 not permitted.
Reason: error. 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

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.

Type of Message: Error

Cause: You attempted to use an ALTER REPLICATION statement that is not allowed while the replication agent for the database is running.

Impact: TimesTen cannot perform the specified ALTER REPLICATION statement.

User Action: Use the ttRepStop built-in procedure or the ttAdmin -repStop utility to stop the replication agent for the master and subscriber databases. Then, retry the ALTER REPLICAITON statement on both master and subscriber databases. You can restart the replication agent with the ttRepStart built-in procedure or the ttAdmin -repStart utility. For more information on replication scheme changes, see "Altering a Classic Replication Scheme" in the Oracle TimesTen In-Memory Database Replication Guide. For more information on the ttRepStop built-in procedure, see "ttRepStop" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttAdmin utility, see "ttAdmin" in the Oracle TimesTen In-Memory Database Reference.

8151

owner.name'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 database 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.

8153

STORE store_name is already
role of the specified
ELEMENT(s)

It is permissible to use ALTER REPLICATION ALTER ELEMENT SET OWNER to reassign an element to its current owner (MASTER or PROPAGATOR). However, doing this evokes this warning.

8154

REPLICATION scheme
owner.name already exists

The CREATE REPLICATION statement requires that each new replication scheme specified to a database have a different owner.name from any replication scheme already defined there.

8155

ELEMENT element_name
already has
SUBSCRIBERsubscriber_name

A database can subscribe to a replication element only once. See "Defining replication elements" in the Oracle TimesTen In-Memory Database Replication Guide.

8156

Internal error:  Column
column_name for ELEMENT
element_name already
defined for SUBSCRIBER
subscriber_name

Type of Message: Internal Error

Cause: The replication agent attempted to re-add column information for a replicated table. Common causes for this are:

- Table definitions are out of synchronization.

- An ALTER TABLE statement was applied concurrently to both sides of the replication scheme.

Impact: None.

User Action: Check the specified table definitions on both sides of the replication scheme for the listed causes. For additional help, contact TimesTen Customer Support.

8157

No elements element_name
found for REPLICATION
owner.name

Type of Message: Error or Warning

Cause: A replication element cannot be found for the requested operation. This is a warning when the request is for an indefinite number of elements (* IN store_name). It is an error when the statement specifies one particular element.

Impact: None.

User Action: Ensure that your REPLICATION statement contains a valid element name and a definite number of elements.

8158

Failed to retrieve LSN
data for initializing PEER

A MASTER or PROPAGATOR database could not get its local LSN to initialize a (subscribing) peer database.

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

Type of Message: Internal Error

Cause: The replication agent has detected an inconsistency in its schema.

Impact: The replication schema may not work correctly.

User Action: Contact TimesTen Customer Support.

8166

Log not writable or
transaction not initiated
by system

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

8168

Cannot set system table
attributes (e.g. REPACCESS)
for table from
replication role

Internal error. Contact TimesTen Customer Support.

8169

Store transmitting_store
already transmits to store
receiving_store; 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 Replication Guide.

8170

Receipt or commit
acknowledgement not returned
in the specified timeout
interval for
XID:conn_id.counter

A subscriber with RETURN RECEIPT or RETURN TWOSAFE service did not receive a commit acknowledgment within the current connection time limit. This can occur when the subscriber Replication Agent is not running or the standby replication state is set to STOPPED. For an active standby pair, this can occur when the standby replication agent is not running and the standby has not been declared as "failed" on the active.

You can adjust the connection time limit with a call to ttRepSyncGet, as described in "Managing return service timeout errors and replication state changes" in the Oracle TimesTen In-Memory Database Replication Guide.

8171

Illegal to replicate a
system table (owner.table)

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 is
already specified with an
equivalent host name as
store_name

Two different forms of host name were used to refer to one particular database 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 DATASTORE element" in the Oracle TimesTen In-Memory Database 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.

8180

Full versus partial
replication conflict with
an existing replication
scheme on data store
data_store_name

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 the DATASTORE element" in the Oracle TimesTen In-Memory Database 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 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 network interfaces when not using the ROUTE clause" in the Oracle TimesTen In-Memory Database 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 database or the database 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 network interfaces when not using the ROUTE clause" in the Oracle TimesTen In-Memory Database Replication Guide.

8192

Dropping/adding a foreign
key that references a
replicated table is not
allowed while the
replication agent for 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 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 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 Replication Guide for details.

8195

The TWOSAFE subscriber
attribute requires an
exclusive bi-directional
configuration.

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 Replication Guide for details.

8196

Remote application of the
transaction ran into error:
error_description. Please
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 re-creating 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 re-creating 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. For more information, see "System limits and defaults" in the Oracle TimesTen In-Memory Database Reference. Consider rebuilding the table, either using INSERT...SELECT or by using the ttBulkCp utility. For more information about the INSERT...SELECT SQL statement, see "INSERT...SELECT" in the Oracle TimesTen In-Memory Database SQL Reference. For more information about the ttBulkCp utility, see "ttBulkCp" in the Oracle TimesTen In-Memory Database Reference.

8206

Invalid parameter value
value passed in.

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.

8208

Replication FailThreshold
exceeded:
failthreshold_config

Type of Message: Error

Cause: You are attempting to create an active standby pair replication scheme on a database that already contains AWT cache groups. There is an existing propagation backlog between TimesTen and the Oracle database for the AWT cache group(s) which is greater than the FAILTHRESHOLD parameter value you specified for the CREATE ACTIVE STANDBY PAIR command.

Impact: TimesTen cannot create the active standby pair replication scheme.

User Action: Wait for the existing propagation backlog to propagate from TimesTen to the Oracle database, then retry the CREATE ACTIVE STANDBY PAIR command. Alternatively, you can specify a higher FAILTHRESHOLD parameter value for the CREATE ACTIVE STANDBY PAIR command. For more information about the CREATE ACTIVE STANDBY PAIR command, see "CREATE ACTIVE STANDBY PAIR" in the Oracle TimesTen In-Memory Database SQL Reference.

8209

Cannot drop a primary key

Type of Message: Error

Cause: You attempted to drop a primary key.

Impact: TimesTen cannot drop the primary key.

User Action: None.

8210

Table reference of
table_name is ambiguous

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 TimesTen Application-Tier 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 TimesTen Application-Tier Database Cache User's Guide.

8213

Cache group tables must
have a primary key

All tables within a cache group must have a primary key. See "Cache groups and cache tables" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

8214

Cache source cache_name
is not supported

Cache group tables currently work only with Oracle database data sources.

8217

Invalid duration value

A cache group duration must be a positive integer.

8220

Table table_name is both
read only and propagated

Cache group tables may not be simultaneously marked as both READONLY and PROPAGATE. See "PROPAGATE cache table attribute" in the Oracle TimesTen Application-Tier 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 TimesTen Application-Tier 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 TimesTen Application-Tier Database Cache User's Guide.

8223

A referenced primary key
is not found in the
associated parent table

The referenced primary key was not found in the cache group. See "Cache groups and cache tables" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

8224

Cache group cache_name
already exists

Attempting to create a cache group which already exists.

8225

Table table_name is read
only

Tables within a cache group which are marked as READONLY may not be updated.

8226

Column column_name is read
only

Internal error. Contact TimesTen Customer Support.

8227

Cache group cache_name
not found

The referenced cache group does not exist.

8228

Cannot drop cache group
table table_name; pleaes
use DROP CACHE GROUP instead

Tables within a cache group may not be explicitly dropped using the DROP TABLE statement.

8229

Memory threshold value
must be between 0 and 100

The cache group aging memory threshold must be a percentage value between zero and 100.

8230

Aging interval value must
be greater than zero

The cache group aging interval must be a value greater than zero.

8231

Cache groups are not
supported on this platform

Cache groups are not supported in this version of the product. For a list of supported platforms, see "Platforms and configurations" in the Oracle TimesTen In-Memory Database Release Notes.

8232

Oracle PassThrough not
supported on this platform.
PassThrough value must be
set to 0

The PassThrough attribute is not supported on this platform. For a list of supported platforms, see "Platforms and configurations" in the Oracle TimesTen In-Memory Database Release Notes.

8233

PassThrough value must be
between 0 and 5

Incorrect value for the PassThrough attribute. Reset to a value between 0 and 5, as described in "Setting a passthrough level" in the Oracle TimesTen Application-Tier 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.

8238

Cannot truncate cache
group table table_name;
Use DROP/REFRESH/
UNLOAD CACHE GROUP instead.

A TRUNCATE statement is not allowed on a cache group table.

8239

PROPAGATE syntax can only
be used once in statement

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 column_name column
not supported

You cannot create an index on column 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 CACHE GROUP 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. TimesTen 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, TimesTen Cache falsely reports this error. The most likely cause is that there are some residual Oracle database objects that were created by the TimesTen Cache but were not dropped when the cache group was dropped or the cache agent was shutdown. For more information on the Oracle database objects created by TimesTen Cache, see "Managing a caching environment with Oracle Database objects" in the Oracle TimesTen Application-Tier 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 subquery. For more information, see "Using a WHERE clause" in the Oracle TimesTen Application-Tier 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 TimesTen Application-Tier 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.

For more information, see "Cache groups and replication" in the Oracle TimesTen In-Memory Database Replication Guide.

8260

Join predicate does not
match

The root/child tables in one cache group are not joined in the same manner as the root/child tables in that cache group's replicated counterpart.You must specify identical JOIN predicates in the cache group definitions for replicating cache groups. You must: stop replication, delete the replication definitions, drop the cache groups, recreate the cache group definitions, recreate replication definitions and restart replication.

See "Cache groups and replication" in the Oracle TimesTen In-Memory Database Replication Guide.

8261

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 TimesTen Application-Tier 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 read-only 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. For more information, see "Cache groups and replication" in the Oracle TimesTen In-Memory Database Replication Guide.

8263

If a replicating cache
group has AUTOREFRESH
specified than the remote
cache group must also
specify AUTOREFRESH

Replicated cache groups must both have AUTOREFRESH set, though the subscriber must have the AUTOREFRESH STATE OFF.

See "Cache groups and replication" in the Oracle TimesTen In-Memory Database Replication Guide.

8264

Transaction
commit/rollback succeeded
on Oracle but failed on
TimesTen

Updates were successfully propagated to the Oracle database but failed on TimesTen. If a commit or rollback succeeds on the Oracle database but fails on TimesTen, the data in the TimesTen cache group may no longer be synchronized with the data in the Oracle database. After clearing up the cause of the TimesTen failure, it may be necessary to re-apply the failing transaction in TimesTen.

For more information about propagation, see "PROPAGATE cache table attribute" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

8265

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.

For more information about propagation, see "PROPAGATE cache table attribute" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information about AUTOREFRESH cache groups, see "AUTOREFRESH cache group attribute" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

8268

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 TimesTen Application-Tier 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.

See "Cache group types" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

8271

Manual
LOAD/UNLOAD/REFRESH/FLUSH
operations are not allowed
on cache group cache_name
because it is system managed

The LOAD CACHE GROUP, UNLOAD CACHE GROUP, MERGE, and FLUSH CACHE GROUP statements cannot be used on system-managed cache groups. This is a runtime error.

See "Cache group types" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

8273

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.

See "Cache groups and replication" in the Oracle TimesTen In-Memory Database Replication Guide.

8275

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 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 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 TimesTen Application-Tier Database Cache User's Guide and "Cache groups and replication" in the Oracle TimesTen In-Memory Database Replication Guide.

8287

Manual LOAD/REFRESH
operations with WHERE or
WITHID clauses are not
allowed on cache group
cache_group_name because it
is specified as AUTOREFRESH

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/UNLOAD
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, TimesTen 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:

SELECT VALUE FROM v$nls_parameters
WHERE PARAMETER = 'NLS_NCHAR_
CHARACTERSET';

8296

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.

8305

Manual LOAD/REFRESH on
cache group failed because
dynamic counter update
failed.

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.

You attempted to use the REFRESH CACHE GROUP statement with the PARALLEL clause for a dynamic read-only cache group. This is not allowed.

8311

To set the number of
parallel AWT applier
threads,
ReplicationParallelism must
be set to > 0

You cannot configure CacheAWTParallelism to be greater than 1 if ReplicationParallelism is 0.

8312

CacheAWTParallelism value of
cache_value must be greater
than or equal to
ReplicationParallelism value
of replication_value

CacheAWTParallelism must always be greater than or equal to ReplicationParallelism.

8313

Cannot use parallel
replication or parallel AWT
with SMPOptLevel=0

Parallel Replication or Parallel AWT cannot be configured for a database with SMPOptLevel set to 0.

8314

ReplicationParallelism
cannot be greater than 1
with
ReplicationApplyOrdering set
to 0

You cannot set ReplicationParallelism to a greater than 1 value when ReplicationApplyOrdering is set to 0.

8315

Timeout in commit wait for
parallel AWT thread

The parallel AWT applier thread timed out waiting for a dependent AWT applier to commit.

8316

Creation of AWT cache groups
is disabled with
ReplicationApplyOrdering set
to 1

You attempted to create an AWT cache group when ReplicationApplyOrdering is set to 1. This is not supported.

8318

Dynamic read-only cache
groups do not use the
Autorefresh Select Every N
Rows feature

Type of Message: Warning

Cause: You attempted to create a dynamic read-only cache group but the specified interval uses the Autorefresh Select Every N Rows feature.

Impact: The cache group is created but it does not use the Autorefresh Select Every N Rows feature.

User Action: None.

8319

The Autorefresh Select Every
N Rows feature does not
allow more than one table
per cache group

Type of Message: Error

Cause: You attempted to create a cache group that references more than one table and has an interval that uses the Autorefresh Select Every N Rows feature.

Impact: The cache group cannot be created.

User Action: Ensure that there is only a single table in the cache group or disable the Autorefresh Select Every N Rows feature for the specified interval.

8320

The Autorefresh Select Every
N Rows feature does not
allow more than one static
read-only cache group per
interval

Type of Message: Error

Cause: You attempted to create a second cache group in an interval that uses the Autorefresh Select Every N Rows feature.

Impact: The cache group cannot be created.

User Action: Ensure that there is no other cache group in the same interval or disable the Autorefresh Select Every N Rows feature for the specified interval.

8321

The Autorefresh Select Every
N Rows feature does not
allow user managed cache
groups

Type of Message: Error

Cause: You attempted to create a user managed cache group in an interval that uses the Autorefresh Select Every N Rows feature.

Impact: The user managed cache group cannot be created.

User Action: Consider using a different type of cache group or disable the Autorefresh Select Every N Rows feature for the specified interval.

8322

To set the batch size for
parallel propagation for AWT
cache groups
(CacheParAwtBatchSize), you
must set either
ReplicationParallelism or
CacheAwtParallelism greater
than zero

Type of Message: Error

Cause: You attempted to configure the CacheParAWTBatchSize parameter, but parallel propagation is not enable for the AWT cache groups.

Impact: The CacheParAWTBatchSize parameter is not modified.

User Action: Enable parallel propagation for AWT cache groups before attempting to configure the CacheParAWTBatchSize parameter. To enable parallel propagation set the ReplicationParallelism or CacheAWTParallelism connection attribute to a value greater than zero. These connection attributes cannot be modified once the database is created.

To set these connection attributes, follow these steps:

1. Create a migrate object of your TimesTen database with the ttMigrate -c utility. For more information, see "ttMigrate" in the Oracle TimesTen In-Memory Database Reference.

2. Destroy your database with the ttDestroy utility. For more information, see "ttDestroy" in the Oracle TimesTen In-Memory Database Reference.

3. Recreate the TimesTen database and set the ReplicationParallelism or CacheAWTParallelism connection attribute to a value greater than zero. For more information, see "Managing TimesTen Databases" in the Oracle TimesTen In-Memory Database Operations Guide.

4. Restore the migrate object into the new TimesTen database with the ttMigrate -r utility. For more information, see "ttMigrate" in the Oracle TimesTen In-Memory Database Reference.

5. Rely setting the CacheParAWTBatchSize parameter with the ttDBConfig built-in procedure. For more information, see "ttDBConfig" in the Oracle TimesTen In-Memory Database Reference.

8323

Autorefresh for interval
interval will use Select
Every num_of_rows Rows

Type of Message: Informational

Cause: TimesTen is starting autorefresh for the specified interval. The specified interval uses the autorefresh select every n rows feature.

Impact: The autorefresh thread for the specified interval will select the specified number of rows from the Oracle database change log table.

User Action: None.

8324

Creation of AWT cache groups
is disabled with
ReplicationApplyOrdering set
to 2

Type of Message: Error

Cause: You attempted to create an asynchronous writethrough (AWT) cache group in a replication scheme using automatic replication with disabled commit ordering (ReplicationApplyOrdering=2).

Impact: TimesTen cannot perform the operation.

User Action: Set the ReplicationApplyOrdering attribute to 0 or 1 and retry the operation. For more information on AWT cache groups, see "Asynchronous writethrough (AWT) cache group" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on parallel replication and the ReplicationApplyOrdering attribute, see "Configuring parallel replication" in the Oracle TimesTen In-Memory Database Replication Guide and "ReplicationApplyOrdering" in the Oracle TimesTen In-Memory Database Reference.

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

Type of Message: Error

Cause: You attempted to use a PL/SQL feature, but PL/SQL is disabled in the TimesTen instance.

Impact: TimesTen cannot perform the operation.

User Action: Try one of the following actions:

- Enable PL/SQL using the ttmodinstall utility. Then, retry the operation. For more information, see "ttmodinstall" in the Oracle TimesTen In-Memory Database Reference.

- Reinstall TimesTen and enable PL/SQL at install time. Then, retry the operation. For more information, see "TimesTen Installation" in the Oracle TimesTen In-Memory Database Installation Guide.

8501

PL/SQL feature not
installed in this TimesTen
database

Type of Message: Error

Cause: You specified PL/SQL=1 as a connection attribute, but PL/SQL is not enabled for the TimesTen database.

Impact: TimesTen cannot perform the operation.

User Action: Try one of the following actions:

- Specify PL/SQL=0 as a connection attribute. Then, retry the operation. For more information, see "PL/SQL connection attributes" in the Oracle TimesTen In-Memory Database PL/SQL Developer's Guide.

- Reinstall TimesTen and enable PL/SQL at install time. Then, retry the operation. For more information, see "TimesTen Installation" in the Oracle TimesTen In-Memory Database Installation Guide.

8502

Error error_number
initializing PLSQL_MEMORY
string

Type of Message: Internal Error

Cause: A problem occurred while loading the database into memory. This problem should not have occurred.

Impact: The database is not loaded into memory. The application is not connected to the database.

User Action: Contact TimesTen Customer Support.

8503

Error_text

Type of Message: Error

Cause: The PL/SQL compiler detected an error from the Oracle database while compiling the program block you submitted.

Impact: The PL/SQL compiler cannot compile the program block you submitted.

User Action: Review the referenced ORA error number from the Oracle database error documentation and correct your application code. In general, diagnosis is the same for PL/SQL in TimesTen and for PL/SQL in the Oracle database, though there are known differences between PL/SQL in these two environments. Then, retry the operation. For more information, see the Oracle Database Error Messages.

8504

PL/SQL object_type
object created
with compilation warnings

Type of Message: Warning

Cause: During compilation, one or more PL/SQL units generated compiler warnings.

Impact: The compiled PL/SQL unit or units may not work correctly.

User Action: Examine the warnings and correct your application. You can use the show errors command of ttIsql utility to view the generated warnings. For more information, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.

8505

PL/SQL object_type
object created with
compilation errors

Type of Message: Error

Cause: You specified a PL/SQL program unit that contains errors.

Impact: TimesTen cannot execute the PL/SQL program unit.

User Action: Review and correct the application errors. Then, retry the operation.

8506

error_text

Type of Message: Internal Error

Cause: The main causes for this error are:

- An attempted operation, such as COMMIT, ROLLBACK, or other DDL statement, cannot proceed because of a conflict with an existing PL/SQL object.

- An unexpected error occurred while attempting to manage memory or locks in the PL/SQL memory area.

Impact: TimesTen cannot perform the operation.

User Action: Contact TimesTen Customer Support.

8507

error_text

Type of Message: Error

Cause: The execution of a PL/SQL program unit encountered an error from the Oracle database.

Impact: TimesTen cannot finish executing the PL/SQL program unit.

User Action: Review the referenced ORA error number from the Oracle database error documentation and correct your application code. In general, diagnosis is the same for PL/SQL in TimesTen and for PL/SQL in the Oracle database, though there are known differences between PL/SQL in these two environments. Then, retry the operation. For more information, see the Oracle Database Error Messages.

8508

Question mark parameter
markers are not allowed in
PL/SQL blocks

Type of Message: Error

Cause: You provided a question mark as a parameter marker in a PL/SQL program unit.

Impact: TimesTen cannot execute the PL/SQL program unit. Parameter marker names beginning with _QMARK_ are reserved for system use.

User Action: Specify a valid parameter marker, using the :var notation for bind variables. Then, retry the operation. For more information, see "Using bind variables from an application" in the Oracle TimesTen In-Memory Database PL/SQL Developer's Guide.

8509

PL/SQL execution
terminated; PLSQL_TIMEOUT
exceeded

Type of Message: Error

Cause: A PL/SQL program unit exceeded the maximum time specified in the PLSQL_TIMEOUT attribute.

Impact: TimesTen terminated the execution of the PL/SQL program unit.

User Action: Examine if the program unit contains loops or never-ending execution. If the PL/SQL program unit is running but needs more time to complete, increase the PLSQL_TIMEOUT attribute value. Then, retry the operation. For more information, see "PL/SQL connection attributes" in the Oracle TimesTen In-Memory Database PL/SQL Developer's Guide.

8510

Error loading PL/SQL
system package file
file_name:
error_message

Type of Message: Internal Error

Cause: You attempted to create a new TimesTen database. When a TimesTen database is created, a number of predefined PL/SQL packages are defined in the new database. An error occurred during this process.

Impact: TimesTen cannot create the database.

User Action: Contact TimesTen Customer Support.

8511

PL/SQL can only be enabled
during database creation or
at first connect

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.

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

8521

Cannot attached PL/SQL
shared memory; virtual
memory at PLSQL_MEMORY_
ADDRESS already in use by
TimesTen.

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.For more information about the PLSQL_MEMORY_ADDRESS, see "PLSQL_MEMORY_ADDRESS" in the Oracle TimesTen In-Memory Database Reference.

8522

PLSQL_MEMORY_SIZE too small.

For more information about the appropriate memory size for your operating system, see "PLSQL_MEMORY_SIZE" in the Oracle TimesTen In-Memory Database Reference.

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

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 (error)

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

Type of Message: Internal Error

Cause: An internal error occurred in the TimesTen subdaemon during a connection attempt.

Impact: The database is unloaded from memory.

User Action: Try reconnecting to the database. If you still receive this error, contact TimesTen Customer Support.

Errors 10000 - 10999

Error number
Error or warning message
Details

10002

No record of a 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, 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 Customer 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

Type of Message: Error

Cause: You attempted to load a database into memory when the RAM policy for the database is not set to manual.

Impact: TimesTen cannot perform the operation.

User Action: Use the ttAdmin -ramPolicy utility to change the RAM policy of the database to manual and retry the operation. For more information on the ttAdmin utility, see "ttAdmin" in the Oracle TimesTen In-Memory Database Reference.

10010

RAM unload ignored due to
ramPolicy setting

Type of Message: Error

Cause: You attempted to unload a database from memory when the RAM policy for the database is not set to manual.

Impact: TimesTen cannot perform the operation.

User Action: Use the ttAdmin -ramPolicy utility to change the RAM policy of the database to manual and retry the operation. For more information on the ttAdmin utility, see "ttAdmin" in the Oracle TimesTen In-Memory Database Reference.

10011

Data store is currently not
being managed

Type of Message: Error

Cause: There are two possible causes for this error message.

a) A process has attempted to unload a database from RAM, but there is no TimesTen subdaemon currently managing the database.

b) You are attempting to perform an operation on a database that is not loaded. The operation you are trying to perform requires authentication and you are not connecting as the instance administrator.

Impact: Depending on the cause, the impact is either of the following.

a) You cannot run ttAdmin -ramUnload on a database that is not loaded.

b) Your user information cannot be verified because no subdaemon is connected to the database

User Action: Depending of the cause, you should do either of the following.

a) Do not run ttAdmin -ramUnload on a database that is not loaded. For more information, see "ttAdmin" in the Oracle TimesTen In-Memory Database Reference.

b) Connect as the instance administrator or load the database and then connect as another user.

10012

Replication Agent was not
started due to repPolicy
setting

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 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. Ensure that 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. Ensure that the database still exists and the replication agent is still running.

10016

Replication Agent was not
stopped due to repPolicy
setting

An attempt has been made to stop a replication agent for a database, but the replication policy is set to "always." See "Starting and stopping the replication agents" in the Oracle TimesTen In-Memory Database 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. Ensure that the 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. Ensure that 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. Ensure that 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 ensure that the database still exists and the cache agent is still running.

10021

Cache agent was not stopped
due to cache agent policy
setting

Type of Message: Error or Warning

Cause: An attempt has been made to stop a cache agent for a database, but the cache agent policy for the database is "always," which means the TimesTen daemon automatically starts or restarts the cache agent.

Impact: None.

User Action: Use ttAdmin -cachePolicy to change the cache agent policy to "manual" to manually control whether the cache agent is active. For more information, see "Set a cache agent start policy" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

10022

Failed to set ORACLE_HOME

The TimesTen daemon was unable to set the ORACLE_HOME environment variable. Ensure that 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. Ensure that 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. Ensure that you are not out of memory or process table space.

10026

Some cache groups that hold
triggers and other objects
in Oracle may exist in the
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.

Errors 11000 - 11999

Error number
Error or warning message
Details

11000

XA internal error

An unexpected XA-specific internal error has occurred. Contact TimesTen Customer Support.

11002

XA asynchronous operation error

An asynchronous XA operation was attempted. TimesTen does not support asynchronous XA calls.

11003

XA Resource Manager error

A TimesTen error has occurred resulting in the failure of an XA operation. Typically, this error is accompanied by another TimesTen error that indicates the nature of the problem.

11004

XA invalid XID

The XID specified for an XA operation cannot be found in the list of currently active XA transactions.

11005

XA invalid argument

An invalid argument was passed to an XA function. Refer to the XA specification for a description of the valid arguments supported for each XA function.

11006

XA protocol error

An XA function was called out of sequence. Refer to the XA specification for a description of the valid function transition states.

11007

XA Resource Manager failure

A TimesTen error has occurred resulting in the invalidation of the database. All applications must reconnect.

11008

XA duplicate XID

The XID specified for a new XA transaction is already associated with another XA transaction.

11009

XA Resource Manager doing
work outside a global
transaction

A local transaction must be committed before starting work on an XA transaction.

11013

Transaction committed since
no log records were generated

A "prepare to commit" request for an XA transaction resulted in the transaction being committed. The transaction made no persistent changes to the database.

11014

Request ignored due to
blocking condition

An XA request was denied to a temporary resource conflict. The operation can be retried.

11016

Transaction has been
heuristically rolled back

An XA transaction was rolled back outside the control of a transaction manager.

11017

Transaction has been
heuristically committed

An XA transaction was committed outside the control of a transaction manager.

11020

Transation has been marked
rollback-only

Due to an internal condition, TimesTen has marked the XA transaction rollback-only. The application must request a rollback of the transaction.

11030

Autocommit must be turned
off when working on global
(XA) transactions

Autocommit is not supported with XA transactions. See "Distributed Transaction Processing: XA" in the Oracle TimesTen In-Memory Database C Developer's Guide.

11031

Illegal combination of local
transaction and global (XA)
transaction

Use of SQLTransact to commit an XA transaction is not allowed. XA transactions may only be committed through the use of xa_commit. See "Distributed Transaction Processing: XA" in the Oracle TimesTen In-Memory Database C Developer's Guide.

11035

In-doubt transactions
awaiting resolution in
recovery must be resolved
first

Due to recovery of in-doubt transactions, normal operation of the database has been suspended. Normal operation resumes once the in-doubt transactions have been resolved by the transaction manager.

11036

XA transactions may not be
started while replication is
configured

TimesTen Replication is not supported with XA transactions.

11037

XA transactions may not be
started while the cache agent
is running

TimesTen Cache is not supported with XA transactions.

11038

XA transaction cannot be
reconstructed because begin
record (txn_file_number.
txn_file_offset) not found

A transaction log record needed to recover an XA transaction could not be found in the existing transaction log files. Contact TimesTen Customer Support.

11039

XA reconstruct of xcb xcb/xcb
failed

Recovery of an XA transaction failed due to an Internal error. Contact TimesTen Customer Support.

11040

DDL statementes are not
allowed in XA transactions
when DDLCommitBehavior is set
to 0

XA transactions require explicit commits after DDL statements. Set the DDLCommitBehavior attribute to 1, if your application uses XA.

Errors 12000 - 13999

Error number
Error or warning message
Details

12001

Specified DSN is NULL or of
0-length

The DSN argument is either NULL or an empty string. You must specify a valid DSN name.

12002

User and system odbc.ini
file not found

UNIX only. TimesTen could not locate the user or system odbc.ini file. The search order for locating an odbc.ini file is:

The file pointed to by the ODBCINI environment variable, if set

$HOME/.odbc.ini

The odbc.ini file located in the user's home directory

The file pointed to by the SYSODBCINI environment variable, if set

/var/TimesTen/instance/ sys.odbc.ini

See "ODBCINI environment variable" in the Oracle TimesTen In-Memory Database Installation Guide for more information.

12003

Cannot open user/system
odbc.ini file

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

12015

Internal error in TimesTen
utility library. Could not
set current context

Internal error. Contact TimesTen Customer Support.

12016

The number of seconds must
be > 0

The number of seconds for the RAM Grace Period must be greater than 0 seconds.

12017

Failed to allocate
environment handle

A call to the ODBC SQLAllocEnv function failed.

12018

Failed to allocate
connection handle

A call to the ODBC SQLAllocConnect function failed.

12019

Failed to locate 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

Type of Message: Error

Cause: You attempted to load a database into memory that is already loaded into memory.

Impact: TimesTen cannot perform the operation.

User Action: None. For more information on the -ramLoad option of the ttAdmin utility, see "ttAdmin" in the Oracle TimesTen In-Memory Database Reference.

12025

Data store already manually
unloaded from RAM

Type of Message: Error

Cause: You attempted to unload a database from memory that has already been manually unloaded from memory.

Impact: TimesTen cannot perform the operation.

User Action: None. For more information on the -ramUnload option of the ttAdmin utility, see "ttAdmin" in the Oracle TimesTen In-Memory Database Reference.

12026

The agent is already running
for the data store

Type of Message: Error

Cause: You attempted to start the cache agent or replication agent for the database when the agent is already running.

Impact: TimesTen cannot perform the operation.

User Action: None. For more information on the -cacheStart or -repStart option of the ttAdmin utility, see "ttAdmin" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttCacheStart built-in procedure, see "ttCacheStart" in the Oracle TimesTen In-Memory Database Reference. For information on the ttRepStart built-in procedure, see "ttRepStart" in the Oracle TimesTen In-Memory Database Reference.

12027

The agent is already stopped
for the data store

Type of Message: Error

Cause: You attempted to stop the cache agent or replication agent for the database when the agent is not running.

Impact: TimesTen cannot perform the operation.

User Action: None. For more information on the -cacheStop or -repStop option of the ttAdmin utility, see "ttAdmin" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttCacheStop built-in procedure, see "ttCacheStop" in the Oracle TimesTen In-Memory Database Reference. For more information on the ttRepStop built-in procedure, see "ttRepStop" in the Oracle TimesTen In-Memory Database Reference.

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

Type of Message: Error

Cause: You attempted to unload a database from memory that is in use or has an active connection.

Impact: TimesTen cannot perform the operation.

User Action: To unload the database from memory, you must close all active connections to the database and set the RAM policy of the database to manual or inUse. For more information, see "Unloading the database from memory" in the Oracle TimesTen In-Memory Database Operations Guide.

12032

Invalid RamPolicy specified

The valid RAM Policy values are:

TT_RAMPOL_MANUAL

TT_RAMPOL_ALWAYS

TT_RAMPOL_INUSE

12034

RamPolicy cannot be set for
temporary data stores

Type of Message: Error

Cause: You attempted to set a RAM policy for a temporary database.

Impact: TimesTen cannot perform the operation. RAM policy can only be set for permanent databases.

User Action: Ensure that the Temporary attribute is set to 0 and retry the operation. For more information on temporary databases, see "Database persistence" in the Oracle TimesTen In-Memory Database Operations Guide. For more information on the Temporary attribute, see "Temporary" in the Oracle TimesTen In-Memory Database Reference.

12035

Could not initialize winsock

Windows only. A call to WSAStartup failed.

12036

No winsock.dll (that
supports version 1.1.) found

Windows only. A call to WSAStartup could not locate a winsock.dll that supports version 1.1.

12037

Could not terminate winsock

Windows only. A call to WSACleanup failed.

12038

Could not connect to
TimesTen daemon on remote
host host_name

Ensure that the TimesTen daemon is running on the remote host.

12039

Could not get port number of
TimesTen replication agent on
remote host. 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

Ensure 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 Customer Support.

12041

Host not found

TimesTen failed to determine the IP addresses associated with the specified host name in the system's /etc/hosts file. Verify that you have correctly identified the host name, as described in "Configuring network interfaces when not using the ROUTE clause" in the Oracle TimesTen In-Memory Database Replication Guide.

12042

Cannot start transaction to
perform this operation

Internal error. Contact TimesTen Customer Support.

12043

Unable to create temporary
file name

Internal error. Contact TimesTen Customer Support.

12044

Transmission failure sending

TimesTen failed to transmit data to the remote TimesTen replication agent.

12045

Cannot create temporary file

Internal error. Contact TimesTen Customer Support.

12046

Transmission failure receiving

TimesTen failed to receive data from the remote TimesTen replication agent.

12047

Data transmitted corrupt

The type of response received from the remote TimesTen replication agent does not match the expected response type.

12048

Error performing backup at
source

This error can occur during a ttRepDuplicateEx operation when the backup operation on the source database fails. See the verbose user error log on the source database for additional diagnostic information.

12049

Cannot write to temporary file

Internal error. Contact TimesTen Customer Support.

12050

Transaction commit for the
swap operation failed

Internal error. Contact TimesTen Customer Support.

12052

Replication scheme name too
long

Maximum length is 30 characters.

12053

Replication scheme owner too
long

Maximum length is 30 characters.

12054

Internal Error: Cannot
determine userid

Internal error. Contact TimesTen Customer Support.

12055

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

12063

Cannot read from temporary
file

Internal error. Contact TimesTen Customer Support.

12064

Failed to execute SQL
command during update

Internal error. Contact TimesTen Customer Support.

12065

Multiple records of
replication schema version

Internal error. Contact TimesTen Customer Support.

12066

Failed to compile command

Internal error. Contact TimesTen Customer Support.

12067

Failed to open cursor

Internal error. Contact TimesTen Customer Support.

12068

Failed to get next row

Internal error. Contact TimesTen Customer Support.

12069

Failed to get format handle
of the SQL command

Internal error. Contact TimesTen Customer Support.

12070

Failed to get column information

Internal error. Contact TimesTen Customer Support.

12071

Failed to get column value

Internal error. Contact TimesTen Customer Support.

12072

Multiple definitions of
replication store id for the
specified data store

Internal error. Contact TimesTen Customer Support.

12073

Cannot determine my own
store name

Internal error. Contact TimesTen Customer Support.

12074

Cannot determine my own
hostname

Internal error. Contact TimesTen Customer Support.

12075

Replication tables are from
an earlier version. Consider
using 'ttRepAdmin -self
-upgrade' to upgrade

The specified operation is not allowed on replication schemes for older versions of TimesTen.

12076

Replication schema is later
than TimesTen utility library

The specified operation is not allowed on replication schemes for new versions of TimesTen.

12077

Hostname is not set on this
machine

Internal error. Contact TimesTen Customer Support.

12078

Failed to reset
is_local_store

Internal error. Contact TimesTen Customer Support.

12079

Failed to set is_local_store

Internal error. Contact TimesTen Customer Support.

12080

No receiver found to swap
with

Internal error. Contact TimesTen Customer Support.

12081

Unsupported column type in
upgrade

Internal error. Contact TimesTen Customer Support.

12082

Failed to reset receiver CTN

TimesTen failed to reset receiver Commit Ticket Number.

12083

Found no source store ID in
TTREP.REPLICATIONS

Internal error. Contact TimesTen Customer Support.

12084

Call to gethostname() failed

Internal error. Contact TimesTen Customer Support.

12085

No table found for table id

Internal error. Contact TimesTen Customer Support.

12086

Cannot get information on
table

Internal error. Contact TimesTen Customer Support.

12087

Cannot get format of table

Internal error. Contact TimesTen Customer Support.

12088

Multiple definitions of
source store id

Internal error. Contact TimesTen Customer Support.

12089

Cannot get column
information of table

Internal error. Contact TimesTen Customer Support.

12090

Cannot get type mapping for
column

Internal error. Contact TimesTen Customer Support.

12091

Cannot determine if version
2 replication tables exist

Internal error. Contact TimesTen Customer Support.

12092

Replication schema is not
empty; cannot upgrade

Replication schema must be empty for the upgrade operation.

12093

No count information
returned from upgrade's scan
of TTREP.TABLES

Internal error. Contact TimesTen Customer Support.

12094

Cannot get count information
from TTREP.TABLES

Internal error. Contact TimesTen Customer Support.

12095

Cannot update object id

Internal error. Contact TimesTen Customer Support.

12096

Cannot set object id

Internal error. Contact TimesTen Customer Support.

12097

Cannot get column values
from TTREP.PEER

Internal error. Contact TimesTen Customer Support.

12098

Failed to determine correct
write LSN for
TTREP.REPPEERS.SENDLSN

Internal error. Contact TimesTen Customer Support.

12099

Multiple schemes found. Must
specify -scheme to identify
which replication scheme to
use

Multiple replication schemes found.

12100

Cannot create replication
table definition

Internal error. Contact TimesTen Customer Support.

12101

Cannot start transaction to
check replication schema
version

Internal error. Contact TimesTen Customer Support.

12102

Failed to commit transaction
for checking replication
schema version

Internal error. Contact TimesTen Customer Support.

12103

Cannot get column value from
TTREP.REPELEMENTS table

Internal error. Contact TimesTen Customer Support.

12104

Cannot find write LSN

Internal error. Contact TimesTen Customer Support.

12105

Failed to update LSN

Internal error. Contact TimesTen Customer Support.

12106

Cannot set new replication
hold LSN

Internal error. Contact TimesTen Customer Support.

12107

Deleting table definition
info failed

Internal error. Contact TimesTen Customer Support.

12108

Invalid policy
'invalid_policy' specified.
Must be valid_policy_list

You did not specify a valid policy value for a built-in procedure used to configure daemon policies. For example, ttCachePolicySet, ttRamPolicySet and ttRepPolicySet. For information about correct policy values, see the description of the particular procedure in the "Built-In Procedures" chapter in the Oracle TimesTen In-Memory Database Reference.

12109

Syntax error in connection
string

There is a syntax error in the specified connection string. Correct the connection string and try connecting again.

12110

Neither DSN= nor DRIVER=
attributes are present in the
connection string

The connection string must contain either a DSN or DRIVER attribute.

12111

Signal signal_name received

The application received a signal and terminated.

12114

Version mismatch between 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 Customer Support.

12117

Disconnect from newly
created database failed

Internal error. Contact TimesTen Customer Support.

12119

Cannot open destination file

Failed to open database file while restoring from stream input.

12120

Insufficient bytes read from
input stream

Internal error. Contact TimesTen Customer Support.

12125

Bad 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 Customer Support.

12136

Error while deleting log files

Internal error. Contact TimesTen Customer Support.

12148

Specified connection string
is NULL or of 0-length

The connection string argument passed is either NULL or an empty string. You must specify a valid connection string argument.

12150

Cannot start transaction to
update receiver CTN in
TTREP.REPPEERS

Internal error. Contact TimesTen Customer Support.

12151

Failed to commit TimesTen
transaction for updating
receiver CTN

Internal error. Contact TimesTen Customer Support.

12152

Cannot set timestamp column
for table

Internal error. Contact TimesTen Customer Support.

12153

Cannot get DS_OBJ_ID value
from TTREP.REPELEMENTS

Internal error. Contact TimesTen Customer Support.

12154

Cannot get TBLID value from
SYS.TABLES

Internal error. Contact TimesTen Customer Support.

12155

Cannot get row id for row in
TTREP.REPELEMENTS

Internal error. Contact TimesTen Customer Support.

12156

Too many tables found on
second pass

Internal error. Contact TimesTen Customer Support.

12157

Failed to update the table
IDs from the mapping we've
created

Internal error. Contact TimesTen Customer Support.

12158

Cannot set replication
fields in SYS.TABLES

Internal error. Contact TimesTen Customer Support.

12159

NULL passed for a pointer
argument

The pointer argument must be a non-NULL value.

12160

Timeout - the agent is still
starting

Under some conditions, you may receive this error when trying to stop the cache agent for a database while the agent is starting up. Retry the operation.

12161

Cannot backup temporary 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 Customer Support.

12185

No definitions of replication
store id for the specified
database. Ensure that the
host name of this machine, or
the name specified if
-localhost was used, matches
the host name specified in
the replication scheme

Internal error. Contact TimesTen Customer Support.

12186

fstat() system call failed
for user/system odbc.ini fle

Internal error. Contact TimesTen Customer Support.

12187

read() system call failed
for user/system odbc.ini file

Internal error. Contact TimesTen Customer Support.

12188

close() system call failed
for user/system odbc.ini file

Internal error. Contact TimesTen Customer Support.

12189

Scan stopped for user/system
odbc.ini file

Internal error. Contact TimesTen Customer Support.

12190

Attribute name is too long

Maximum length of attribute names is 30 characters.

12191

Invalid length for connection
string

The value specified for the length of the connection string to the SQLDriverConnect ODBC call is less than 0 and not equal to SQL_NTS.

12192

Invalid backup type

An invalid value was passed as the type parameter of the ttBackup utility library function. See "ttBackup" in 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 Customer Support.

12195

Basename contains invalid
characters

An invalid value was passed as the baseName parameter of the ttBackup utility library function. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12196

Backup status file file not found

No backup status file was found for the given backup directory 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 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 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 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 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 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 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 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 or base name is incomplete. See "ttBackup" in the Oracle TimesTen In-Memory Database C Developer's Guide.

12206

Backup control information
corrupted or incomplete (may
indicate TimesTen version
mismatch)

The backup status information for the backup indicated by the backup directory or base name is corrupted or incomplete. See "ttBackup" in 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 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 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 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 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 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 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 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 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

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

12221

Platform mismatch between
backed-up files and
ttRestore. Backed-up files
are backup_platform;
ttRestore is restore_platform

Files can only be restored on the same platform type where they were backed up.

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

Type of Message: Error

Cause: You attempted to truncate a table that does not exist, is part of a replication scheme, or is a cache group object.

Impact: TimesTen unsuccessfully completed the duplicate operation.

User Action: Destroy the destination database and retry the operation. Ensure that the table you want to truncate exists and is not part of a replication scheme or a cache group object. For more information on the ttRepAdmin utility or how to duplicate a database, see "ttRepAdmin" in the Oracle TimesTen In-Memory Database Reference.

12232

Failed to drop objects

Type of Message: Error

Cause: TimesTen cannot drop an object that does not exist, is part of a replication scheme, or is a cache group object.

Impact: TimesTen unsuccessfully completed the duplicate operation.

User Action: Destroy the destination database and retry the operation. Ensure that the object you want to drop exists and is not part of a replication scheme or a cache group object. For more information on the ttRepAdmin utility or how to duplicate a database, see "ttRepAdmin" in the Oracle TimesTen In-Memory Database Reference.

12233

Failed to truncate table

Specifies the table that had the problem referred to in error 12231.

12234

Failed to drop table

Specifies a table that was referred to in error 12232.

12235

There are identifiers
supplied for the drop option
which are also quoted for the
truncate option

Type of Message: Error

Cause: You specified the same object to be dropped and truncated while running the ttRepAdmin -duplicate utility.

Impact: TimesTen cannot perform the operation.

User Action: Ensure that any object specified in the ttRepAdmin -duplicate utility is not specified for the -drop option and -truncate option at the same time and retry the operation. For more information on the ttRepAdmin utility, see "ttRepAdmin" in the Oracle TimesTen In-Memory Database Reference.

12236

There are duplicate
identifiers specified in the
drop option

Type of Message: Error

Cause: You specified the same object to be dropped at least twice while running the ttRepAdmin -duplicate utility.

Impact: TimesTen cannot perform the operation.

User Action: Only specify the objects that you want to drop once for the -drop option of the ttRepAdmin -duplicate utility. Then retry the operation. For more information on the ttRepAdmin utility, see "ttRepAdmin" in the Oracle TimesTen In-Memory Database Reference.

12237

There are duplicate
identifiers specified in the
truncate option.

Type of Message: Error

Cause: You specified the same object to be truncated at least twice while running the ttRepAdmin -duplicate utility.

Impact: TimesTen cannot perform the operation.

User Action: Only specify the objects that you want to drop once for the -truncate option of the ttRepAdmin -duplicate utility. Then retry the operation. For more information on the ttRepAdmin utility, see "ttRepAdmin" in the Oracle TimesTen In-Memory Database Reference.

12238

For -truncate or -drop you
can specify "ALL" or a list
of tables, not both.

Type of Message: Error

Cause: You specified ALL and one or more objects for the -drop or -truncate option of the ttRepAdmin -duplicate utility.

Impact: TimesTen cannot perform the operation.

User Action: Ensure that you specify ALL or a list of objects, not both, for the -drop or -truncate option of the ttRepAdmin -duplicate utility and retry the operation. For more information on the ttRepAdmin utility, see "ttRepAdmin" in the Oracle TimesTen In-Memory Database Reference.

12245

No definitions of
replication store id for the
data store DSN on
host_name

Arguments passed during database duplication are not consistent with database 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 disaster recovery Oracle database cannot be the same database as the active standby Oracle subscribing database. The check has identified a tt_03_reppeers entry which is from one of the Active Standby master databases to the disaster recovery Oracle database. Reconfigure the data recovery to resolve this conflict.

12254

Remote peer does not support
parallel replication.

There is a mismatch in the parallel replication configuration between two databases involved in a replication scheme, where one database is enabled for parallel replication and the other is not.

12255

ACTIVE STANDBY PAIR
replication schemes cannot be
created when
ReplicationApplyOrdering=1

Type of Message: Error

Cause: You attempted to create an active standby pair replication scheme while the ReplicationApplyOrdering attribute is set to 1.

Impact: TimesTen cannot create the active standby pair replication scheme.

User Action: Set the ReplicationApplyOrdering attribute to 0. Then, retry the operation. For more information on the ReplicationApplyOrdering attribute, see "ReplicationApplyOrdering" in the Oracle TimesTen In-Memory Database Reference.

12257

Error creating bookmarks for
the parallel tracks.

Internal error. Tried to create entries in TTREP.REPPEERS for parallel replication tracks. When parallel replication is enabled, there are more than one TTREP.REPPEERS entry for master->subscriber. The number of entries is dependent upon the ReplicationParallelism parameter.

12258

Return Receipt or Return
TwoSafe cannot be used when
parallel mode replication is
configured.

Return Receipt and Return Twosafe cannot be used for a return service when the database has been created with parallel replication attributes, where the ReplicationApplyOrdering attribute is greater than 0.

12259

A store cannot be defined as
a PROPAGATOR when parallel
mode replication is configured.

Propagator databases are not supported when the database has been created with parallel replication attributes, where the ReplicationApplyOrdering attribute is greater than 0.

12260

Create cache group is not
permitted when parallel mode
replication is configured.

Cache groups are not supported when the database has been created with parallel replication attributes, where the ReplicationApplyOrdering attribute is greater than 0.

12261

ALTER TABLE is not permitted
on a replicated table when
parallel mode replication is
configured.

ALTER TABLE is not allowed when the database has been created with parallel replication attributes, where the ReplicationApplyOrdering attribute is greater than 0. This error is raised at application time.

12262

Error setting track for
connection.

Internal Error. The replication agent cannot use a specific track for its database connection.

12263

Aging is not permitted on a
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, aging is disabled when ReplicationApplyOrdering is set to 1. When a database with ReplicationApplyOrdering set to 1 is upgraded from 11.2.1.6.0, aging will be disabled.

12264

ALTER TABLE cannot be
replicated to a 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 Customer Support.

12275

Failed to convert replicated
XLA bookmarks to
non-replicated for read only
subscriber

This error is returned after ttRepAdmin -duplicate processing. When a read-only subscriber is created with the -duplicate qualifier, TimesTen modifies replicated bookmarks to non-replicated.

This error is returned if there is a problem modifying the bookmarks.

12276

RamPolicyAutoReload value
must be 0 or 1.

Type of Message: Error

Cause: You specified an incorrect value for the parameter of the ttRamPolicyAutoReloadSet built-in procedure.

Impact: TimesTen cannot call the ttRamPolicyAutoReloadSet built-in procedure.

User Action: Call the ttRamPolicyAutoReloadSet built-in procedure and pass either 0 or 1 as a parameter. For more information on the ttRamPolicyAutoReloadSet built-in, see "ttRamPolicyAutoReloadSet" in the Oracle TimesTen In-Memory Database Reference.

12325

Specifed local IP address
could not be looked up

Type of Message: Error

Cause: The IP address you specified with the ttRepAdmin -duplicate -localIPAddress option cannot be resolved by the target host.

Impact: ttRepAdmin -duplicate failed because a connection from the local network interface device to the target host cannot be established.

User Action: Ensure that the alias or IP address you specified for the local network interface device is correct. Also, ensure that the local network interface device you specified has access to the target host.

12326

Specifed remote IP address
could not be looked up

Type of Message: Error

Cause: The IP address you specified with the ttRepAdmin -duplicate -remoteIPAddress option cannot be resolved by the target host.

Impact: ttRepAdmin -duplicate failed because a connection from the remote network interface device to the target host cannot be established.

User Action: Ensure that the alias or IP address you specified for the remote network interface device is correct. Also, ensure that the remote network interface device you specified has access to the target host.

12327

Could not connect to the
remote replication agent by
binding to the specified
local address

Type of Message: Error

Cause: The ttRepAdmin utility cannot bind to the local address you specified in order to connect to the remote replication agent.

Impact: ttRepAdmin -duplicate failed because the utility cannot bind to the local address you specified.

User Action: Ensure that the alias or network address you specified is correct. Also, ensure that the remote replication agent you specified has access to the local network interface device.

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

For the UNISTR SQL function,
'\\' must be followed by four
hexadecimal characters or
another '\\'

The UNISTR function argument allows the back-slash character only as an escape for a hexadecimal Unicode character or itself. For example:

UNISTR('\0041')

UNISTR('abc\\nop')

12717

Character data loss in
character set conversion

Type of Message: Warning

Cause: During character set conversion of data, a character was encountered for which no valid conversion exists.

Impact: TimesTen substituted a replacement character in its place.

User Action: You should change your connection character set to one that is compatible with the database character set in use. For more information, see "ConnectionCharacterSet" in the Oracle TimesTen In-Memory Database Reference.

12718

Error setting default
date/timestamp format
'format_string'

Contact TimesTen Customer Support.

12719

Error in conversion of NCHAR
to ASCII

If you attempt to convert the NCHAR type to either the DATE type or numeric type, TimesTen first converts the NCHAR type to ASCII. There was an error when TimesTen attempted to convert NCHAR TO ASCII. Check the data for your NCHAR type.

Errors 14000 - 14999

Error number
Error or warning message
Details

14000

TimesTen daemon internal
error: error_number

Internal error. Contact TimesTen Customer Support.

14001

TimesTen daemon out of
memory error_details

Type of Message: Error

Cause: The TimesTen daemon has run out of swap space.

Impact: Unknown.

User Action: None.

14002

TimesTen daemon port in use
port_number

The TimesTen daemon cannot listen on its specified port because the port is already in use.

14003

TimesTen daemon thread
creation failed: 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.

14007

TimesTen daemon destroy
failed: reason_for_failure

TimesTen daemon could not destroy the database for specified reason.

14008

TimesTen daemon association
table full
(number_of_connections entries)

Too many simultaneous connections have been made.

14009

TimesTen daemon startup
failed: reason_for_failure

Startup of TimesTen daemon failed for the specified reason.

14010

TimesTen daemon spawn
failed: process_name

TimesTen daemon could not spawn a subprocess.

14011

TimesTen daemon operation
failed due to invalidation:
reason_for_failure

Specified operation failed due to a database invalidation.

14012

TimesTen daemon subdaemon
failed: reason_for_failure

A TimesTen subdaemon failed to perform the requested operation.

14013

TimesTen daemon out of
subdaemons: reason_for_failure

The TimesTen daemon could not spawn a subdaemon to perform some operation, such as managing a database or rolling back transactions for a terminated process.

14014

TimesTen daemon policy
request failed: reason_for_failure

A ttAdmin request failed for the specified reason.

14015

User user_name, not instance
admin, trying to start
TimesTen daemon as setuid
root

A user other than the instance administrator attempted to start the main TimesTen daemon.

Errors 15000 - 15999

Error number
Error or warning message
Details

15000

Password is incorrect

Incorrect password given.

15001

User lacks privilege
privilege_needed

The users lacks the privilege for the given operation.

15002

No such user

Attempt to modify or remove a user which does not exist.

15003

Number of users specified
at daemon startup exceeded

Attempt to add another user when the limit has been reached. The daemon should be restarted with a new -maxusers option specified in the ttendaemon.options file.

15004

User user already exists

Type of Message: Error

Cause: You attempted to create a user that already exists.

Impact: TimesTen cannot perform the operation.

User Action: Select a different user name and retry the operation.

15006

Cannot delete the instance
administrator user

Attempt to remove the instance administrator user.

15007

Access control not enabled

Attempt to perform authorization functions when access control has not been enabled.

15008

User name exceeds limit of
30 characters

Specified user name is too long. Must be 30 characters or less.

15009

Password required for
username

A PWD or PWDCrypt attribute must be specified for the given user name.

15010

Cannot convert user from
'identified externally' to
internal or vice versa.

Cannot give a password to a user defined as IDENTIFIED EXTERNALLY, or remove a password for a user defined as an internal TimesTen user.

15011

Password exceeds limit of
number characters

Type of Message: Error

Cause: You specified a password that exceeds the maximum allowed number of characters.

Impact: TimesTen cannot perform the operation.

User Action: Select a password that is within the maximum allowed number of characters and retry the operation.

15012

Encrypted password must
have exactly number characters

PWDCrypt attribute is not the correct length.

15013

Cannot alter privileges for
the instance administrator 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

Type of Message: Error

Cause: You cannot alter the password for a user that was created during TimesTen database creation, including the instance administrator.

Impact: TimesTen cannot perform the operation.

User Action: None.

15016

Unsupported use of an
internal system-user 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.

Type of Message: Error

Cause: You specified a password with one or more of the listed restrictions.

Impact: TimesTen cannot perform the operation.

User Action: Specify a password that does not contain any of the listed restrictions and retry the operation.

15019

Only the instance admin may
alter the attribute
attribute.

The current user is attempting to connect to the database using the specified first connection attribute with a value different from the existing database value. Only the instance administrator user may change that attribute.

The user can either connect as instance administrator to change the attribute value, or connect without changing the value.

15020

UID not specified

The UID was not specified when executing a ttRepAdmin -duplicate operation. The user must provide the UID and rerun the ttRepAdmin -duplicate operation.

15021

PWD or PWDCrypt not specified

The PWD or PWDCrypt were not specified when executing a ttRepAdmin -duplicate operation. The user must provide a password or a value for the PWDCrypt attribute and rerun the ttRepAdmin -duplicate operation.

15022

OraclePwd connection
attribute needs to be
specified and has to be
non-empty for using TimesTen
Cache features

Type of Message: Error

Cause: The OraclePWD connection attribute is not specified.

Impact: Your application cannot use TimesTen Cache features if you do not specify a value for the OraclePWD connection attribute. For more information on TimesTen Cache features, see "Cache Group Operations" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

User Action: Specify the OraclePWD connection attribute for the TimesTen connection. Also, ensure that your OraclePWD is non-empty. For more information on specifying the OraclePWD connection attribute, see "OraclePWD" in the Oracle TimesTen In-Memory Database Reference.

15100

User user_name lacks
privilege privilege_name

Type of Message: Error

Cause: The specified user does not have the required privileges to perform the operation.

Impact: TimesTen cannot perform the operation.

User Action: The instance administrator or a user with the ADMIN privilege must GRANT the required privilege to the specified user. For more information on user privileges, see "Privileges" in the Oracle TimesTen In-Memory Database SQL Reference.

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

Type of Message: Error

Cause: You cannot DROP system-defined users and roles.

Impact: TimesTen cannot DROP the specified user or role.

User Action: None.

15104

Only the instance
administrator can destroy a
database

Type of Message: Error

Cause: You attempted to destroy a database.

Impact: You cannot destroy a database while you are connected as the specified user. Only the instance administrator can destroy the database.

User Action: Connect as the instance administrator and destroy the database. For more information on the instance administrator, see "TimesTen instance administrators and users groups" in the Oracle TimesTen In-Memory Database Installation Guide.

15105

User username requesting
database creation is not the
instance administrator.
Please verify user id and
password. Only the instance
administrator can create a
database.

Type of Message: Error

Cause: You attempted to create a database.

Impact: You cannot create a database while you are connected as the specified user. Only the instance administrator can create a database.

User Action: Connect as the instance administrator and create the database. For more information on the instance administrator, see "TimesTen instance administrators and users groups" in the Oracle TimesTen In-Memory Database Installation Guide.

15106

Database users cannot
invoke internal built-in
procedures

You attempted to call a TimesTen built-in procedure that is reserved for internal use only.

15107

User lacks CREATE SESSION
privilege; logon denied

Type of Message: Error

Cause: You attempted to connect to a database with a user that does not have the CREATE SESSION privilege.

Impact: The specified user cannot connect to the database.

User Action: The instance administrator or an user with the ADMIN privilege must GRANT the CREATE SESSION privilege to the specified user. For more information on user privileges, see "Privileges" in the Oracle TimesTen In-Memory Database SQL Reference.

15109

The system privilege SYSDBA
is not supported. The system
privilege ADMIN can be used
for most administrative
tasks.

Type of Message: Error

Cause: SYSDBA is not a valid privilege.

Impact: TimesTen cannot GRANT the SYSDBA privilege to the specified user.

User Action: Consider granting the ADMIN privilege to the specified user. For more information on the ADMIN privilege, see "Granting administrator privileges" in the Oracle TimesTen In-Memory Database Operations Guide.

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.

Type of Message: Error

Cause: The privilege you attempted to GRANT does not exist.

Impact: TimesTen cannot GRANT the specified privilege.

User Action: Check the name or spelling of the privilege and retry the operation. For more information on user privileges, see "Privileges" in the Oracle TimesTen In-Memory Database SQL Reference

15140

GRANT failed: User user_name
already has system privilege
privilege_name

Type of Message: Error

Cause: The specified user already has the system privilege you attempted to GRANT.

Impact: TimesTen cannot perform the operation.

User Action: Ensure that your SQL statement is correct. If necessary, retry the operation. For more information on system privileges, see "System privileges" in the Oracle TimesTen In-Memory Database SQL Reference. For more information on granting system privileges, see "Granting or revoking system privileges" in the Oracle TimesTen In-Memory Database Operations Guide.

15141

GRANT failed: User user_name
already has object privilege
privilege on object

Type of Message: Error

Cause: The specified user already has the object privilege you attempted to GRANT.

Impact: TimesTen cannot perform the operation.

User Action: Ensure that your SQL statement is correct. If necessary, retry the operation. For more information on object privileges, see "Object privileges" in the Oracle TimesTen In-Memory Database SQL Reference. For more information on granting object privileges, see "Granting or revoking object privileges" in the Oracle TimesTen In-Memory Database Operations Guide.

15142

REVOKE failed: User
user_name does not have
system privilege
privilege_name

Type of Message: Error

Cause: The specified user does not have the system privilege you attempted to REVOKE.

Impact: TimesTen cannot perform the operation.

User Action: Ensure that your SQL statement is correct. If necessary, retry the operation. For more information on system privileges, see "System privileges" in the Oracle TimesTen In-Memory Database SQL Reference. For more information on revoking system privileges, see "Granting or revoking system privileges" in the Oracle TimesTen In-Memory Database Operations Guide.

15143

REVOKE failed: User user_name
does not have object
privilege privilege on object

Type of Message: Error

Cause: The specified user does not have the object privilege you attempted to REVOKE.

Impact: TimesTen cannot perform the operation.

User Action: Ensure that your SQL statement is correct. If necessary, retry the operation. For more information on object privileges, see "Object privileges" in the Oracle TimesTen In-Memory Database SQL Reference. For more information on revoking object privileges, see "Granting or revoking object privileges" in the Oracle TimesTen In-Memory Database Operations Guide.

15144

REVOKE failed: Cannot revoke
system-granted object
privilege privilege on object
from role

Type of Message: Error

Cause: You attempted to REVOKE an object privilege from PUBLIC that was system-granted during database creation.

Impact: TimesTen cannot perform the operation.

User Action: You can only REVOKE privileges granted to the PUBLIC role after database creation. For more information on the PUBLIC role, see "PUBLIC role" in the Oracle TimesTen In-Memory Database Operations Guide.

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

Type of Message: Error

Cause: The specified user does not exist.

Impact: TimesTen cannot perform the operation.

User Action: Check the name or spelling of the user and retry the operation.

15152

operation failed: Object
object_name does not exist

Type of Message: Error

Cause: The specified object does not exist.

Impact: TimesTen cannot perform the operation.

User Action: Check the name or spelling of the object and retry the operation.

15154

operation failed: Invalid
privilege privilege_name
for object object_name
type type_name

The operation failed because there is a mismatch between the specific privilege and the object.

15155

operation failed: You do
not have the rights to grant
or revoke privilege
privilege_name

Type of Message: Error

Cause: You do not have the adequate privileges necessary to GRANT or REVOKE the specified privilege.

Impact: TimesTen cannot perform the operation.

User Action: The instance administrator or an user with the ADMIN privilege must GRANT or REVOKE the specified privilege. For more information on user privileges, see "Privileges" in the Oracle TimesTen In-Memory Database SQL Reference.

15156

operation failed: You do
not have the rights to grant
or revoke privilege
privilege_name on object_name

Type of Message: Error

Cause: You do not have the rights necessary to GRANT or REVOKE the specified privilege to the specified object.

Impact: TimesTen cannot perform the operation.

User Action: The instance administrator, an user with the ADMIN privilege, or the owner of the specified object must GRANT or REVOKE the specified privilege. For more information on object privileges, see "Providing authorization to objects through privileges" in the Oracle TimesTen In-Memory Database Operations Guide.

15157

operation failed: User
user_name is the owner of
object_name

Type of Message: Error

Cause: You attempted to GRANT or REVOKE privileges for the owner of the specified object.

Impact: TimesTen cannot perform the operation.

User Action: Ensure that your SQL statement is correct. If necessary, retry the operation. For more information on object privileges, see "Granting or revoking object privileges" in the Oracle TimesTen In-Memory Database Operations Guide.

15158

operation failed: Cannot
grant or revoke privilege
from instance admin user_name

You do not have adequate privileges to grant or revoke privileges to/from the instance administrator.

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 want to GRANT or REVOKE.

15162

operation failed: operation
on object_name is redundant
with ALL on object_name

Type of Message: Error

Cause: You attempted to GRANT ALL or REVOKE ALL privileges for the specified object, while attempting to add additional privileges that make the SQL statement redundant.

Impact: TimesTen cannot perform the operation.

User Action: Specify either ALL or the specific privileges you want to GRANT or REVOKE, and retry the operation. For more information, see "Granting or revoking object privileges" in the Oracle TimesTen In-Memory Database Operations Guide.

15163

operation failed:
user_name is listed more
than once in user list.

You must list the user name only once in a SQL statement.

15164

operation failed: Cannot
grant or revoke privileges
from internal system-user
user_name

Type of Message: Error

Cause: You attempted to GRANT or REVOKE a privilege to or from an internal TimesTen user.

Impact: TimesTen cannot perform the operation.

User Action: None.

15165

Invalid system privilege
sys_privilege.

The user specified an invalid privilege in a GRANT or REVOKE statement when a system privilege was expected. For more information about valid system privileges, see "Providing authorization to objects through privileges" in the Oracle TimesTen In-Memory Database Operations Guide.

15166

Invalid object privilege
object_privilege.

The user specified an invalid privilege in a GRANT or REVOKE statement when an object privilege was expected. For more information about valid system privileges, see "Providing authorization to objects through privileges" in the Oracle TimesTen In-Memory Database Operations Guide.

15167

Cannot drop a user that is
currently connected.

Type of Message: Error

Cause: You attempted to DROP a user that has an active connection to the database.

Impact: TimesTen cannot perform the operation.

User Action: Disconnect the specified user from the database and retry the operation. Use the utility ttXactAdmin -connections to identify the process associated to the specified user. For more information on the ttXactAdmin utility, see "ttXactAdmin" in the Oracle TimesTen In-Memory Database Reference.

15168

Cannot drop a user that
owns database objects
(string string).

Type of Message: Error

Cause: You attempted to DROP a user that owns one or more objects in the database.

Impact: TimesTen cannot perform the operation.

User Action: DROP all objects owned by the user and retry the operation. For more information on dropping a SQL object, see the respective section in the Oracle TimesTen In-Memory Database SQL Reference.

Errors 16000 - 16999

Error Number
Error or warning message
Details

16001

TimesTen Replication Agent
(version major_release.
minor_release.patch_release)
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 database without first performing the duplicate operation. Set the ForceConnect attribute as described in "Recovering nondurable databases" in the Oracle TimesTen In-Memory Database 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.

16018

Failed to connect to TimesTen
daemon for socket_name
socket; port: port_number;
id:
rep_agent_subdaemon_id_number

The replication agent was unable to initiate a connection to the TimesTen daemon.

16019

Error reading from deadman
socket. System Error:
error_message

A network or out-of-memory problem prevented a thread in the replication agent from opening a socket to the TimesTen daemon to perform a read.

16020

Fatal Error. Data received
on deadman socket

A thread in the replication agent opened a socket to the TimesTen daemon to perform a read. The read returned information, which means that the TimesTen daemon failed.

16021

TimesTen daemon appears to
be vanished. Terminating
Replication Agent

TimesTen daemon appears to have terminated. Terminating replication agent.

16022

Received a command_name
command

Informational message. No action required.

16023

Failed to create
thread_name thread

Creation of a thread failed. This can occur because of an operating system failure or a memory resource shortage.

16024

Not enough memory to start
thread_name thread

A memory allocation failed for a TimesTen data structure that is used to manage threads.

16025

Thread thread_name
(context
pointer_to_context_structure)
starting

Informational message. No action required.

16026

Thread 'thread_name' (context
pointer_to_context_struct;
return code
'return_code_name') exiting

Informational message. No action required.

16027

All replication service
threads have finished

Informational message. No action required.

16028

Number_of_threads replication
service threads did not
finish

The replication agent is exiting, but some threads are not properly terminated.

16029

Waiting for thread_name'
thread to finish

Informational message. No action required.

16030

*** CANNOT PERFORM ANY
REPLICATION WORK ***  The
replication schema has no
information about the local
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:
os_error_number

Type of Message: Error

Cause: The specified operating system call failed with the operating system error that is displayed.

Impact: Review the man pages of the failed operating system call for possible impacts.

User Action: The man pages of the failed system call lists the possible causes for the failure. Diagnose and troubleshoot the operating system error. Then run the ttCWAdmin utility command that failed. If you are unable to troubleshoot the operating system error or still receive this error, contact TimesTen Customer Support.

16033

Waiting for resolution of
in-doubt 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.

This error usually occurs due to a locking issue that is caused by either a long commit on the receiving side or an application blocking the replication agent.

When this error is encountered, TimesTen will retry in 10 seconds.

Check to ensure that you do not directly access the TTREP tables especially if you are using serializable isolation. Also, ensure that your transactions are not too large.

16042

Failed to awaken log
readers (TRANSMITTER threads)

A keep-alive message to a replication master failed.

16043

Failed to retrieve
replication LSN from 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.

16045

Failed to retrieve peer store
ID for the provided database
name 'dsname' ON host
'host_name'. error_code.
error_message

The replication agent failed to get a store ID for a specific database name and host name.

16046

Failed to force log

A full flush of the replication log to the subscriber failed.

16048

Mismatch in TimesTen
version for source and
destination machine

The same version of TimesTen must be operating on the source and destination systems.

16049

Failed to update CTN for
peer 'dsname'

An attempt to update a Commit Transaction Number in the database failed.

16050

Failed to update
replication hold LSN

An attempt to update the HOLD Log Sequence Number failed.

16051

Failed to update
replication state

An attempt to update a log sequence number failed during a backup.

16052

Failed to set DB-level
locking

Attempt to set the data-store-level lock failed.

16053

Failed to open temporary
file needed for this
operation. OS-detected
error: OS_error_name

A temporary file could not be opened during a backup. The operating system error is displayed.

16054

Failed to perform file seek
in the temporary file needed
for this operation.
OS-detected error:
OS_error_name

A seek on a temporary file failed during a backup. The operating system error is displayed.

16055

Failed to read from the
temporary file needed for
this operation. OS-detected
error: OS_error_name

A read on a temporary file failed during a backup. The operating system error is displayed.

16056

Failed to backup data
store. error_message

Database backup operation failed. The error message provides details.

16057

Failed to perform Network
Checkpoint

Database checkpoint over a network connection failed.

16058

Failed to execute table
renewal.
error_code.error_message

An attempt to create a list of tables on the subscriber failed.

16059

Failed to send
request/response to peer.
error_message

Sending a message to the peer failed. The error message is displayed.

16060

Failed to read data from the
network. error_message isAwt
(awt_cond) parallelism
(parallel_async_tracks)
trackId (track_id) socket
(socket)

A read on a socket failed. This is often the result of network problems.

16062

Failed to compile command:
command_name

Compilation of a SQL statement that is used by the replication agent failed.

16063

Failed to execute command:
command_name

Execution of a SQL command used by the replication agent failed.

16064

Failed to execute prepared
command in function_name()

Execution of a SQL command in the specified function failed.

16065

Failed to open cursor for
command: command_name

Opening a cursor during execution of a SQL statement used by the replication agent failed. The SQL statement is specified.

16066

Failed to open cursor in
function_name()

Opening a cursor during execution of a SQL statement used by the replication agent failed. The replication agent function in which this occurred is specified.

16067

Failed to retrieve next row
for command: command_name

Opening a cursor during execution of a SQL statement used by the replication agent failed. The SQL statement is specified.

16068

Failed to retrieve next row
in function_name()

Opening a cursor during execution of a SQL statement used by the replication agent failed. The replication agent function in which this occurred is specified.

16069

Failed to find a row for
command: command_name

The replication agent on the subscriber could not find replication information about a peer.

16070

Internal Error. Failed to
get format from command
arguments for command_name

Command argument substitution failed for a SQL statement used by the replication agent.

16071

Internal Error. Failed to
get format from command
results for command_name

Command result substitution failed for a SQL statement used by the replication agent.

16072

Failed to delete command

Attempt to delete a compiled SQL command failed.

16073

Internal Error. Failed to
allocate a new slot for CTN.
Retrying

The commit ticket number identifies a transaction. This error means that a slot could not be allocated to store the commit ticket number.

16074

No table found with id
table_id

A specified table cannot be found. This can occur when the SQL schema is updated.

16075

Failed to lookup table
table_name

Given an owner and table name, the table could not be found in the database.

16076

Failed to retrieve version
information of table
table_name

The version of a table could not be determined.

16077

Failed to retrieve format
of table table_name

The format of a table could not be determined.

16078

Table definition for ID
table_id is invalid
(Original failure
message_id message_details)

A specified table cannot be found. This can occur when the SQL schema is updated.

16079

Failed to retrieve
information for column
column_number of table
table_name

The replication agent could not obtain description information for some column.

16080

Table: table_name. Failed
to lookup row row from
master master for operation

A specific row was not found in a SQL table. This can occur during conflict resolution.

16081

Table: table_name. Failed
to update row

A row of a table could not be updated.

16082

Table: table_name. Failed
to update row row from
master master for operation

A row of a table could not be updated.

16083

Table: table_name. Failed
to delete row for
'operation_name'

A row of a table could not be deleted.

16084

Table: table_name. Failed
to insert row for
'operation_name'

A row of a table could not be inserted. This can occur during conflict resolution.

16085

Table: table_name. Failed
to empty table

An attempt to make a table empty failed.

16086

Wrong number
(number_of_peers) of peers
updated

An attempt to update the peer in the database returned an unexpected number of results.

16087

Failed to read duplicate
options

An attempt to determine the options given for a duplicate operation failed.

16088

Unique constraint violation

A uniqueness constraint failed on update or insert.

16089

Foreign Key constraint
violation

A foreign key constraint failed on an update or insert.

16090

Failed to check constraints
for table table_name

A constraint check failed on an update or insert.

16091

Failed to retrieve
constraints information for
table table_name

A table constraint failed on a update or insert.

16092

Unexpected log record type
record_type

An unrecognized record type was found in the log.

16093

Invalid column type:
column_type

An unrecognized column type was encountered in a log entry.

16094

Failed to execute SQL:
SQL_statement

A SQL statement failed to execute for a command generated by the replication agent. The SQL string is displayed.

16095

No matching index columns
for table table_name

The unique key on a column that was chosen by TimesTen on the table in the master does not exist on the subscriber.

16096

Failed to retrieve
information on index
table_name.index_name
for table table_name

The replication agent was unable to determine information about an index.

16097

Failed to retrieve inline
partition widths for table
table_name

Internal error. Contact TimesTen Customer Support.

16098

Invalid replicationschema.
More than one entry for
element element_name in
replication scheme
replication_owner.
scheme_name. Continuing...

More than one replication element has been found for a specific element such a table.

16099

Invalid replication schema.
More than one master
transmits table
owner.table_name to me in
replication scheme
owner.scheme_name.
Continuing...

Multiple tables with a particular owner and name were found in a replication schema.

16100

More than one host has peer
'dsname'

Multiple hosts have been identified as masters by a replication agent acting in a subscriber role.

16101

Count of zero return
subscribers disagrees with
peer return service of
machine_name for table id
table_id

There is a difference in the return service specified by the two sides of a replication scheme.

16102

Count of zero return by
request subscribers
disagrees with having a
return by request peer for
table id table_id

The Return Receipt by Request attribute is inconsistent between two peers.

16103

Failed look up cache group
owner.cache_group_name

Named cache group was not found.

16104

Incompatible cache group
definition. Length of join
predicate/where clause does
not match for cache group
owner.cache_group_name

Cache group definitions are inconsistent.

16105

Incompatible definition for
cache group owner.
cache_group_name

The cached group on the two peers is incompatible.

16106

Table table_name of cache
group cache_name is not subscribed

There is an inconsistency in defining which tables are in a cache group.

16107

Failed to check cache cache
group subscription for
cache_name

Failed to check whether all tables of a cache view are subscribed to by a specific peer.

16108

Failed to retrieve local
store information

The replication agent was unable to locate the TTREP.REPLICATIONS table.

16109

Failed to update send LSN
(operation: operation_name)

The SEND Log Sequence Number could not be updated in the database.

16110

Failed to update
return-receipt send LSN

Update of return-receipt Log Sequence Number in the database failed.

16111

Failed to initialize send
LSN (operation:
operation_name)

The data structure used to read the SEND Log Sequence Number could not be initialized.

16112

Failed to initialize
replication meta-data

Initialization of the control block used to query the database for replication schema information failed. Additional messages about the cause of the problem are displayed, also.

16113

Failed to get IP address
for host host_name. Retry in
60 seconds

The attempt to map a host name used in a replication schema to an IP address failed.

16114

Attempting to connect to
dsname on host_name
(host_ip_address); port:
port_number

Informational message. No action required.

16115

Connected to dsname
(host_name); socket:
socket_number; port:
port_number

Informational message. No action required.

16116

Added definition for column
column_name (in table
table_owner.table_name)
into TTREP.REPTABLES

Informational message. No action required.

16117

Dropped definition for
column column_name (in table
table_owner.table_name)
from TTREP.REPTABLES

Informational message. No action required.

16118

Failed to get replication
hold value

An attempt to read the log sequence number for the hold log failed.

16119

Failed to enable log buffer
pad

Failed to set an internal TimesTen engine flag. This failure occurs if something is inconsistent in the database. Additional messages about the cause of the problem are displayed.

16120

Failed to update
transaction statistics for
peer dsname

The replication master attempted by update statistics about a peer, but the attempt failed.

16121

Failed to flush transaction
queue. Restarting log read
loop

Flush of the transaction log failed. Restarting read from the initial read LSN.

16122

Failed to send heartbeat to
peer. Restarting log read
loop

The replication agent was unable to send its heartbeat message to its peer.

16123

Transaction
(connection_id.counter) already
on send queue

This is an internal consistency check. The master adds a transaction to a queue to be sent to the subscriber, but the transaction is already on the queue.

16124

Failed to retrieve
subscription information for
table id table_id

A query of the replication schema information about subscribers failed.

16125

Inline data length for
partitioned tuple
(number_of_bytes bytes)
exceeds maximum of
maximum_number_of_bytes

Inline data for row is too long.

16126

Failed to initialize buffer
for transaction log read

Transaction log failed to open.

16127

Failed to read transaction
logs

A read of an entry from the transaction log failed.

16128

Log seek operation failed
at LSN
log_file_number/log_file_offset
(caller line: line_number)

A seek (setting position) on the transaction log failed.

16129

Starting log read at LSN
log_file_number/log_file_offset
(caller line: line_number)

Informational message. No action required.

16130

Update record does not
contain old values

An internal consistency check for the TimesTen engine shows that an update does not include old values.

16131

Internal Error. Bad copy to
action ends at log_field
not log_field with nbuf
buffer primkeylen
primary_key_length

A log record has field lengths that are inconsistent.

16132

Internal Error. Buffer
buffer addr address_value,
size size

This message provides details for message 16131: Internal Error. Bad copy to action ends at log_field not log_field with nbuf buffer primkeylen primary_key_length.

16133

Peer signals change in its
configuration

The peer configuration has changed.

16134

Received a packet of type:
packet_type

The type of network packet from a peer is not a recognized type.

16135

Failed to retrieve column
information for table
table_owner.table_name

An attempt to query the database for information about a table in the replication scheme failed.

16136

Sending definition for
table
table_owner.table_name
(number_of_columns columns)

Informational message. No action required.

16137

Transmitter signon to peer
failed with signon error:
error_number. Shutting down
transmitter

The master attempted to sign on with the subscriber, but the attempt failed.

16138

Propagation cannot co-exist
with Master Catchup

Catchup mode on a propagating replication agent has occurred due to corruption in the database.

16139

Failed to add table to
transmit queue

The master replication agent was unable add a table to its queue to be sent to the subscriber. Details in other error messages.

16140

Failed to initialize post
handle from sbLRRepSync log
record

Synchronous "Post Procedure Fail". For synchronous replication, concerns a data structure used to "wake up" a thread.

16141

Failed to initialize
semaphore from sbLRRepSync
log record

There was a problem initializing a data structure used to manage the peers of the replication agent. Details in other error messages.

16142

Failed to retrieve peer
information. No peers found

The replication peer was not found in replication schema. This message is usually due to a change in the schema.

16143

Failed to retrieve any
timeout information

Internal information about the replication scheme was not found.

16144

Failed to get a slot in the
return-receipt buffer

Failed to allocate the buffer used by RETURN RECEIPT. Details in other error messages.

16145

Failed to update state in
return-receipt buffer

The return receipt updated failed in the database.

16146

Failed to exchange initial
diskless CTN with peer

Diskless "Commit Transaction Number" exchange to a peer failed. Details in other error messages.

16147

Failed to change transmit
byte to 0 for diskless transmit

An update of a table related to diskless replication failed. Details in other error messages.

16148

Reinitialize due to changes
in replication schema

Informational message. No action required.

16149

Current state is FAILED for
peer dsname

While reading the transaction log, the transmitter notices that its state is "peer failed."

16150

Failed to send FAIL packet
to peer

The replication agent failed to notify a peer that the replication has failed. Details in other error messages.

16151

Log record type
record_type, data size
number_of_bytes, LSN
log_file_number.log_file_offset

Internal error. Contact TimesTen Customer Support.

16152

Failed to determine whether
replication state is FAILED

An attempt by the subscriber replication agent to determine if it has been marked Failed has failed.

16153

Failed to initialize
return-receipt buffer

The subscriber replication agent was unable to initialize its RETURN RECEIPT state.

16154

Failed to check for
replication schema changes

An attempt to mark a replication schema as changed has failed.

16155

Temporary failure to access
replication configuration

The agent cannot access configuration information about replication. The agent can recover and continue.

16156

Failed to access
replication configuration.
Restarting replication agent

An attempt by the replication agent to access the replication schema failed.

16157

REPLISTENER thread waiting
for number_of_threads
RECEIVER thread(s) to exit

Informational message. No action required.

16158

Failed to retrieve peer list

Query of the replication schema to determine subscribers failed.

16159

Starting new transmitter
for 'dsname' on 'host_name'

Informational message. No action required.

16160

Failed to flush log
records. Replication Agent
exiting; but will be
restarted by TimesTen daemon

Failed to flush log records. Replication agent exiting; but the TimesTen daemon restarts the replication agent.

16161

Listening on configured
port: port_number
(assigned port: port_number)

Informational message. No action required.

16162

Call to setsockopt
(tcp_socket_option)
failed. System Error:
error_number

A "Set Socket Options Failed" networking OS call failed. The details are included in this message.

16163

RECEIVER thread terminating
due to certain error already
recorded in the system log

The subscriber replication agent is exiting due to an error.

16164

Received a FAIL packet.
Setting replication state to
FAILED and shutting down
myself

The subscriber replication agent received a request to mark the replication state as "failed."

16165

Failed to perform backup operation

A subscriber backup operation failed. Details in other error messages.

16166

Failed to perform memory
copy operation

Memory copy operation failed.

16167

Failed to check catchup
status

Automatic catch-up operation for a failed master database has failed.

16168

Master Catchup started for
'data_store_name' from CTN
timestamp sequence_number to
timestamp sequence_number

Informational message. No action required.

16169

TimesTen Replication Agent
termination begun because of
permanent failure during
Master Catchup

Internal error. Contact TimesTen Customer Support.

16170

Master Catchup completed
for 'data_store_name'

Informational message. No action required.

16171

Confirm Name packet with
unreasonable name length
number_of_bytes

Internal error. Contact TimesTen Customer Support.

16172

Confirm Name packet for
dsname received, but I am
dsname

Internal error. Contact TimesTen Customer Support.

16173

Accepting messages from a
peer which is unknown
locally

A request was received from an unknown peer. This is usually due to a change in the replication schema that has not yet been applied.

16174

Found more than one peer;
cannot determine default

A subscriber discovered more than one peer with the same replication name and owner.

16175

Defaulted connection to
peer store id
peer_store_id; protocol:
protocol_number

Informational message. No action required.

16176

Signon message after
transmitting peer assigned

A subscriber replication agent is reporting that the master requesting to sign on is already signed on.

16177

Lookup of transmitting peer
dsname failed

A subscriber got a sign on request from a master, but there is no appropriate information about that master in the replication schema.

16178

Found transmitting peer
dsname in TTREP.TTSTORES
with no entry in
TTREP.REPPEERS; continuing

A subscriber got a connection request from a master, but the subscriber does not recognize it as a peer according to information in the replication schema.

16179

Transmitting peer dsname
not defined to me

Warning: A subscriber got a connection request from a master, but the subscriber does not recognize it as a peer according to information in the replication schema.

16180

Transmitting peer dsname ON
host_name has the same store
id (data_store_id) as me

The peer ID found by a replication agent was its own ID. Possible cause is corrupt TTREP.REPNETWORK table.

16181

Replication reserve slot
failed

Query to reserve a "commit transaction number" slot failed (and logged its own error message).

16182

Replication ctnlist (CTN:
commit_ticket_number)
value read failed

The replication agent was unable to read the Commit Transaction Number from the database.

16183

Failed to set replication
status for this connection

Query to set replication status failed (and logged its own error message).

16184

Failed to determine whether
to propagate

Query to determine if there is any propagation for the current database has failed. Details in other error messages.

16185

RECEIVER thread noticed
replication configuration
change

Informational message. No action required.

16186

RECEIVER thread disconnects
due to superseded connection
from peer (internal version
was version_number, now
version_number)

The peer uses a different version of the replication schema than this replication agent. Note that this is not the same as the TimesTen version.

16187

Transaction: "SbCTNPrintFmt";
Error: transient flag,
permanent flag state flag
error message : number

The commit of a block of transactions had errors. Details in other error messages for the individual failures. Some failures may be temporary.

16188

rxCommitTx() failed to commit

The commit of a block of transactions failed.

16189

Failed to begin
transaction. Subscriber
state is state_number

Type of Message: Internal Error

Cause: The replication agent is beginning a transaction, but it is not in the idle state.

Impact: The replication receiver is delaying the process and will retry the transaction.

User Action: Restart the replication agent. If you still receive this error after restarting the replication agent, contact TimesTen Customer Support.

16190

Failed to push propagation
loop

A propagation path could not be stored, usually because it is a loop.

16191

Replacing old table
definition
(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.

16193

Adding definition for
table: table_name

Informational message. No action required.

16194

Subscriber return service
attribute conflict for
element element_name
(table table_name) in
replication scheme
replication_owner.
scheme_name. Transmitting
peer dsname ON code_name
says 'message'; local
schema says 'message'.
Transmitter's value will be
used

The return attribute on this replication element is different for each peer.

16195

Failed to find owner for
element element_name
(table table_name) in
replication scheme
replication_owner.
scheme_name (received from
peer dsname ON host_name).
Continuing ...

Failed to find owner for this table element in the replication scheme on the named replication peer.

16196

Master/subscriber conflict
with peer peer_name on
table_name for element
element_name (object
table_name) in replication
scheme owner.scheme.

The owner of this table element conflicts on the two replication peers.

16197

Failed to add element
element_name (table
table_name) for
transmitting peer dsname
ON host_name

Attempt to add a replication element has failed, probably due to a duplicate. This is a rare condition where something happens between when a check is made and the attempt to add the element.

16198

Table definition mismatch
on number of columns for
table table_name.  Local
definition:
number_of_columns;
transmitting peer:
number_of_columns

"Table Definition Mismatch" between the two peers. Some differences are tolerated, but others are not.

16199

Table definition mismatch
on attribute_name for
column column_number in
table table_name.  Local
definition:
attribute_name;
transmitting peer:
attribute_name

"Table Definition Column Mismatch" between the two peers.

16200

Table definition mismatch
on timestamp column in table
table_name. Local
definition: timestamp;
transmitting peer:
timestamp.  Continuing
with transmitter's value

The TIMESTAMP column on one peer is not the same as the TIMESTAMP column on another peer. This can occur during conflict resolution based on timestamps.

16201

Table definition mismatch
on timestamp exception
action in table
table_name.  Local
definition: action;
transmitting peer: action.
Continuing with transmitter's
value

When there is a difference in timestamps between two peers, the action that each peer should take is different. The action of the transmitting peer is chosen.

16202

No cache view entry for
table table_name

A subscriber replication agent could not find a cache group associated with a particular table sent by the master.

16203

Passed extended comparison
for table table_name

Informational message. No action required.

16204

Table table_name marked
invalid. Will not apply
transactions received for it
until a valid definition is
received

A replicated table was marked invalid.

16205

Skipping definition
received for cache group
cache_group_name. Part of
previously processed transaction

Informational message. No action required.

16206

Definition for different
cache group received.
Current:
cache_group_definition;
New:
cache_group_definition.
Table table_name marked
invalid

The cache group definitions are different between the two peers.

16207

Internal error. Table ID
mismatch

Internal error. Contact TimesTen Customer Support.

16208

Failed to open file
file_name for Timestamp
report

Could not open the replication agent report file.

16210

Varying length part of key
tuple > number_of_bytes bytes

The size of a primary key caused an overflow of a data packet.

16211

No matching V* value found
for Table: table_name;
column: column_name; offset:
column_offset; ID:
hexadecimal "Insert LSN
from peer (dsname) was
log_file_number.log_file_offset error

Type of Message: Internal Error

Cause: There is an inconsistency between the master and subscriber in the area of VARCHAR or VARBINARY columns in a replicated table.

Impact: There is a divergence of data between the master and the subscriber because a transaction did not replicate correctly.

User Action: Contact TimesTen Customer Support.

16212

Failed to set column
column_number of table
table_name

Subscriber replication could not set a column value.

16213

Table: table_name. Failed
to insert row.
error_message

Subscriber replication agent could not insert a row into a table due to a timestamp conflict.

16214

Table: table_name. Failed
to delete row. error_message

Subscriber replication agent could not delete a row due to a timestamp conflict.

16215

Table: table_name. Failed
to update row. error_message

Subscriber replication agent could not update a row due to a timestamp conflict.

16216

Failed to retrieve column
number for column_name of
table table_name

In an update, given a column name, the column number could not be computed.

16217

Connection connection_id
awakened

Replication transactions have been halted, but the peers are connected again.

16219

Failed to retrieve any
compression information

The replication agent cannot find information to complete compression.

16220

Replication is not
supported with an agent
using the protocol
protocol_type

Incompatible versions of the replication protocol between the two peers.

16221

Table table_name not found

Table specified by master not found on receiver.

16222

The call gettimeofday failed

The system call to get time of day failed.

16223

Transmitter thread failure
due to high latency
milliseconds with peer
store DSN

The network latency between the databases is higher than permitted for an active standby pair.

16224

Transmitter thread failure
due to high clock skew
milliseconds with peer store
DSN

The clock slew between the databases is higher than permitted for an active standby pair.

16225

Transmitter thread failure
due to lack of scheme
consistency with peer store

The databases that are a part of the active standby pair have replication schemes that are not the same. If the replication scheme is altered, a duplicate operation must be executed to ensure that the schemes on the two databases match.

16226

Receiver thread failure due
to scheme read failure

The local database was unable to read the replication scheme.

16227

Standby store has
replicated transactions not
present on the active. Local
CTN=commit_ticket_number,
Backup CTN=
commit_ticket_number, Received CTN=
commit_ticket_number.

The standby database has transactions present that are not present on the active database. This indicates that the present active database was incorrectly set up to be an active database. To remedy this situation, duplicate the standby database from the active database.

16228

Transmitter thread failure
due to lack of state
consistency between active
and standby stores

The databases that are part of the active standby scheme have replication schemes that are not the same. If the replication scheme is altered, then a duplicate operation must be executed to ensure that the schemes on the two databases match.

16229

Transmitter thread failure
due to lack of state
consistency at subscriber
store DSN

The databases that are part of the active standby scheme have replication schemes that are not the same. If the replication scheme is altered, then a duplicate operation must be executed to ensure that the schemes on the two databases match.

16230

Store not in standby state

An error returned by the replication agent that indicates a transitory condition. No user action is necessary.

16231

The duplicate operation on
this store was not
successfully completed

The local database was created by a duplicate operation that did not complete successfully. Destroy the database and perform the duplicate operation again.

16232

Connection rejected from
the standby until connection
received from the active

Usually indicates a transitory error. A subscriber database allows a standby database to connect only after it has a connection from the active database.

16233

The subscriber store has
updates not present on the
active store

The subscriber database has transactions present that are not present on the active database. This indicates that present active database was incorrectly set up. To remedy this situation, duplicate the subscriber database.

16234

The subscriber store has
been classified as failed by
the active

The databases that are a part of the active standby scheme have replication schemes that are not consistent. This is usually a transitory error. If the error persists, then a duplicate operation must be executed to ensure that the replication schemes on the two databases match.

16235

Failed to update CTNs for
standby 'DSN'

Error updating replication bookmark information (Commit Ticket Number) in the replication agent.

16236

Failed to update CTN for
the subscriber store

Error updating replication bookmark information (Commit Ticket Number) in the replication agent.

16237

Awt thread initialized for
OracleNetServiceName=
net_svc_name,
CacheUid=cache_uid,
BatchCommitSize=size,
AwtErrorFile=awt_err_file,
AwtBufSize=size KB

This message appears in the user error log. It is informational. No action is necessary.

16240

An error occurred
replicating changes to
Oracle but an AWT error file
will not be generated since
TimesTen is running in
diskless mode

An asynchronous writethrough error file is not created when TimesTen is operating in diskless mode.

16242

Failed to retrieve
subscription information for
sequence id sequence_id

A failure occurred while retrieving subscription information for a sequence.

16243

No sequence found with id
sequence_id

A sequence with the specified ID was not found.

16244

Skipping definition
received for already-defined
sequence sequence_id. Part
of previously processed
transaction

A subscriber received information about a sequence but already has the information.

16245

Adding definition for
sequence: sequence_id

Generated when information about a replicated sequence on the subscribing side is added to the list of sequence information.

16246

Sequence definition
mismatch for sequence
sequence_id.  Local
definition: Minval :
value, Maxval: value,
Increment: value;
transmitting peer: Minval:
value, Maxval: value,
Increment: value

The sequence definition on the master database does not match the sequence information generated for the subscriber databases.

16247

Sequence sequence_id
marked invalid. Will not
apply transactions received
for it until a valid
definition is received

An invalid sequence definition has been received by the subscriber databases. No updates are applied for this sequence until a valid description is sent.

16248

Sequence sequence_id not
found

A subscriber database received a definition for a sequence that does not exist on the subscribing side.

16249

Failed to add sequence to
transmit queue

This error occurs a sequence update message from the master database was not added to the queue.

16250

Failed to update sequence
sequence_id

Failed to apply a sequence update to the subscriber database.

16251

Sending definition for
sequence owner.sequence_id

Informational message from master database.

16252

Table definition mismatch
on cascade delete
configuration for table
table_name.  Local
definition: subscriber;
transmitting peer: master

The foreign key cascade delete constraints for the table do not match between the master and subscriber databases.

16253

Failed to retrieve cascade
delete configuration for
table table_name

Type of Message: Internal Error

Cause: The ON DELETE CASCADE definition on the master and subscriber may not be the same.

Impact: Replication for this table cannot work until the ON DELETE CASCADE definition is the same on the master and subscriber.

User Action: Ensure that the ON DELETE CASCADE definition is the same on the master and subscriber. For more information on using ON DELETE CASCADE in a replication scheme, see "Replicating tables with foreign key relationships in a classic replication scheme" in the Oracle TimesTen In-Memory Database Replication Guide. For additional help, contact TimesTen Customer Support.

16254

Master has not been
assigned an Active or
Standby Role

This message could occur when a replication agent for a master database in an ACTIVE STANDBY scheme has been started but has not been classified as either master or standby. The thread attempts to restart until a state has been determined.

16255

Invalid replication schema.
More than two _ORACLE stores
found in scheme

Type of Message: Internal Error

Cause: A sanity check has failed in an ACTIVE STANDBY scheme that includes autorefresh cache groups.

Impact: Replication cannot work.

User Action: Contact TimesTen Customer Support.

16256

Invalid replication schema.
No _ORACLE stores found

Type of Message: Internal Error

Cause: A sanity check has failed in an ACTIVE STANDBY scheme that includes autorefresh cache groups.

Impact: Replication cannot work.

User Action: Contact TimesTen Customer Support.

16257

The ID for this store does
not match either of the
master Ids

Type of Message: Internal Error

Cause: A sanity check has failed after a ttRepAdmin -duplicate operation on an ACTIVE STANDBY scheme that includes autorefresh cache groups.

Impact: You cannot duplicate the database.

User Action: Contact TimesTen Customer Support.

16258

Failed to retrieve
heartbeat factor information

Internal error. Contact TimesTen Customer Support.

16259

Wrong number of rows
(number_of_rows) affected
on Oracle when updating
Active Standby Information

Type of Message: Internal Error

Cause: A sanity check failed in an ACTIVE STANDBY scheme when information was updated on an Oracle database subscriber.

Impact: Replication cannot work correctly.

User Action: Contact TimesTen Customer Support.

16260

Failed to update
autorefresh bookmark

The replication operation was unable to update the autorefreshed cache group bookmark on the subscriber database at runtime. This may occur because the cache group does not exist on the subscriber.

16261

Failed to add cache
bookmark to transmit queue

This error occurred while adding the replicated autorefreshed cache group bookmark to the sending queue. The cache group may no longer exist on the master database.

16262

Failed to retrieve
subscription information for
cache bookmark id ID

This error occurred while accessing the subscription information for an autorefreshed cache group bookmark. The cache group may no longer exist on the master database.

16263

Secure protocol violation

There was a connection attempt from another replication agent that violated the security challenges presented on the protocol.

16264

Awt Ctn initialized to
timestamp=value
SeqNum=value

Informational message. No action required.

16265

This store is currently the
STANDBY. Change to owner.name
not permitted

When an active standby master is in STANDBY mode you cannot update the database directly. Operations such as adding or dropping a column, INSERT, UPDATE, TRUNCATE, or DELETE are prohibited.

16266

The remoteDaemonPort cannot
be used for this -duplicate
operation because the
sending data store has
stores that use automatic
port allocation.

A remote daemon port cannot be selected during a duplication operation when the replication scheme is using automatic port allocation. To use automatic port allocation, do not specify the -remoteDaemonPort option in the duplicate operation or supply a value of 0 for the operation.

16267

The host name list is not
available from
ttrep.ttnework.

An error occurred in performing a query on TTREP.REPNETWORK table. This is usually a transient error, if the database is already running and a replication scheme is already defined on the master database. The transmitter in the replication agent attempts to run this query again in one second.

16268

Failed to retrieve aging
configuration for table
owner.table.

This is part of replication. The first time the transmitter sends a transaction for a particular table, TimesTen sends the table definition. This message indicates something went wrong while trying to retrieve the aging information. There is an additional error message detailing the specific failure. Review that message to determine the problem and fix.

16269

In an Active Standby
scenario, AWT Monitoring
should be enabled on the
Standby node

In an active standby pair with an AWT cache group, monitoring gives relevant results only on the standby node, which does the propagation of the workload to the Oracle database. Enabling AWT monitoring on the active node does not record any monitoring information. If the standby node fails and if the active node takes over, calling the ttCacheAWTMonitorConfig built-in procedure automatically enables monitoring the AWT statistics.

16270

AWT Monitoring should not
be enabled on the Subscriber
node in an Active Standby
scenario

In an active standby pair with subscribers and an AWT cache group, monitoring on a subscriber does not reveal any useful information. Call the ttCacheAWTMonitorConfig built-in procedure to disable monitoring the AWT statistics.

16271

Monitoring could not be
configured because
replication agent does not
have an active AWT thread

This error is thrown if the replication agent is either invalid or in an initialization phase. If the AWT receiver is killed due to an unexpected situation, the replication agent is in an invalid state. It is also possible that the AWT receiver has not been started by the replication agent, in which case it is in an initialization phase. Resolution for this error is to call the ttCacheAWTMonitorConfig built-in procedure again, with the state parameter set to "ON."

16272

Operation not permitted on
a store in the ACTIVE
state.

This is an internal mismatch. In an active standby pair, a routine that should only be running on a standby is running on the active. This is most likely caused during the detection of a "split-brain" (both masters marked active) problem and should be self-correcting.

16273

Error updating standby store.

A failure occurred while trying to get the latest status for an active standby pair standby.

16274

Failed to modify active
standby data. caller:
caller_name

After a duplicate operation, some data on TimesTen system tables must be modified for the destination database on both TimesTen and the Oracle database. This operation has failed, but the replication agent retries the operation.

16275

RECEIVER network helper
thread terminating due to
certain error already
recorded in the system log

Type of Message: Error

Cause: Review the user error log for error messages relating to the RECEIVER network helper thread for possible causes.

Impact: TimesTen terminates the RECEIVER network helper thread.

User Action: None.

16276

RECEIVER restarting daemon
because helper thread failed
to spawn

Type of Message: Error

Cause: Review the user error log for error messages relating to the RECEIVER network helper thread for possible causes.

Impact: The replication agent recycles the helper thread.

User Action: None.

16277

The Instance Admin user id
is not the same in both
instances.

The instance administrator name must be the same on both the source and target databases when running ttRepAdmin -duplicate or ttRepDuplicateEx.

16278

Failed to get Cache AWT
method

Unable to get the attribute value for use in the replication agent. An invalidation was most likely detected.

16279

Cannot start AWT propagation
because replication agent
cannot connect to Oracle
RDBMS database:
OracleNetServiceName =
\"name\", uid = \"uid\",
pwd is hidden, TNS_ADMIN =
\"TNS_ADMIN_name\",
Error Msg= \"message\"

Replication agent is not able to connect to the Oracle database.

Check to see that TNS_ADMIN is configured properly and ensure that the Oracle database is reachable.

16280

Parallel AWT requested
restart of the worker threads

Parallel AWT thread encountered an error and restarting of the threads was necessary.

16281

Replication receiver track
track_id waiting for receiver
track track_id to initialize

This is an informational start up message.

16282

Replication receiver track
track_id waiting for receiver
track track_id to finish

This is an informational shut down message.

16287

Replication receiver with
local store id tt_store_id,
remote store id tt_store_id,
track id track_id still finds
a previous track 0 receiver
running.

A master thread running on the receiver was detected and should not have been.

16288

Replication receivers are
stopping.

This is an informational shut down message.

16289

Replication receivers face
dependency error.

There was an internal error during a replication dependency wait for parallel processing.

16290

Replication transmitters are
stopping.

This is an informational shut down message on the transmitter. The group of threads for a particular subscriber are stopping.

16291

Replication receivers are
starting serial commit mode

Type of Message: Error

Cause: TimesTen detected a problem with parallel replication. TimesTen is reprocessing the transactions in serial mode.

Impact: Replication throughput is momentarily decreased.

User Action: Contact TimesTen Customer Support.

16292

Replication receivers are
stopping serial commit mode

This is an informational message indicating that the replication receivers are stopping serial commit mode.

16293

Failed Replication thread
thread is exiting description

This error occurs when the transmitter is stopping. You should see a description of what the transmitter was doing before it exited.

16294

Transmitter waiting on AWT
appliers.

Type of Message: Warning

Cause: Propagation from TimesTen to the Oracle database is slow, causing transmitter threads to stall.

Impact: This can result in LOG_FS_READS that may cause performance degradation of replication throughput. This may also increase workload on the I/O subsystem. For more information on LOG_FS_READS, see "SYS.MONITOR" in the Oracle TimesTen In-Memory Database System Tables and Views Reference.

User Action: Contact TimesTen Customer Support.

16295

Failure updating Active
Standby
replication_role_or_state
information on the Oracle
database

Type of Message: Error

Cause: The replication agent cannot update the indicated information on the Oracle database.

Impact: Review the error message for possible impacts.

User Action: Review the error message for possible fixes.

16296

Receiver for
subscriber_store on
subscriber_host port port
completed handshake with
Transmitter for master_store
on master_host

Type of Message: Informational

Cause: A receiver for the specified subscriber store completed a handshake with a transmitter of the specified master store.

Impact: None.

User Action: None.

16297

Failed to set transparent
load

Type of Message: Error

Cause: The transmitter cannot set transparent load.

Impact: The transmitter will retry to set transparent load. Also, the threads will attempt to recycle and self-correct the error. Review the error message for any additional impacts.

User Action: Review the error message for possible fixes.

16298

Waiting for the AWT receiver
to complete propagation.
Current sleep iteration
timeout_count

Type of Message: Informational

Cause: The replication agent is waiting for the AWT receiver to complete the propagation of a long running AWT transaction.

Impact: The replication agent cannot timeout while the AWT transaction is being propagated to the Oracle database.

User Action: None.

16299

Finished with received
request request

Type of Message: Informational

Cause: The replication agent completed the specified request.

Impact: None.

User Action: None.

16300

Failed materialized view
info: info additional_info

Type of Message: Error

Cause: The replication agent failed to update a base table for a materialized view.

Impact: The replication agent cannot update the base table for the materialized view. If this is a transient error, the replication agent tries the transaction again. If this is a permanent error, the transaction is lost.

User Action: Review the daemon log for any additional error messages to determine a cause for this error. For more information on how to review the daemon log, see "Using the logs generated by the TimesTen daemon" in the Oracle TimesTen In-Memory Database Troubleshooting Guide. For more information on materialized views, see "Understanding materialized views" in the Oracle TimesTen In-Memory Database Operations Guide.

16303

Backing out of wait and
retrying transaction

Type of Message: Internal Error

Cause: The replication agent detected a parallel replication deadlock and is retrying the operation. This message is preceded by another message that describes the details of the error.

Impact: None.

User Action: Review the daemon log for any additional error messages to determine a cause for this error. For more information on how to review the daemon log, see "Using the logs generated by the TimesTen daemon" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

16304

Flagging transaction
timestamp.sequence_number on
track track_id to rollback
and retry

Type of Message: Informational

Cause: This is an accompanying error message to error 16303. The specified transaction is flagged for retry.

Impact: None.

User Action: None.

16305

Constraint Check Fail table
table_name Optype
SQL_operation tuple key
tuple_key

Type of Message: Error

Cause: The replication agent encountered an error while checking constraints on an operation.

Impact: If this is a transient error, the replication agent tries the operation again. If this is a permanent error, there may be differences in the data contained by the databases that are part of the replication scheme.

User Action: Review the daemon log for any additional error messages to determine a cause for this error. Also, verify that the data contained in the specified table in the databases that are part of the replication scheme is consistent. For more information on how to review the daemon log, see "Using the logs generated by the TimesTen daemon" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

16306

DepCTN[track_id]=
timestamp.sequence_number

Type of Message: Informational

Cause: The replication agent is printing the dependency information on a transaction because of a failed operation. This message is followed by another messages that describe the details of the failure.

Impact: None.

User Action: Review the daemon log for any additional error messages to determine a cause for this error. For more information on how to review the daemon log, see "Using the logs generated by the TimesTen daemon" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

16307

rxWaitCTN waiting for
timestamp.sequence_number on
track track_id currently at
timestamp.sequence_number
stalled for time seconds

Type of Message: Internal Error

Cause: TimesTen is experiencing a performance issue. This message is followed by another message that describe the details of the issue.

Impact: TimesTen is stalling the transaction.

User Action: Use the ttXactAdmin utility to verify the status of the specified transaction. Also, review the message log for any additional error messages to determine a cause for this error. For more information on the ttXactAdmin utility, see "ttXactAdmin" in the Oracle TimesTen In-Memory Database Reference and "Using the ttXactAdmin utility" in the Oracle TimesTen In-Memory Database Troubleshooting Guide. For more information on how to review the daemon log, see "Using the logs generated by the TimesTen daemon" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

16308

Error while initializing
context ctn array

Type of Message: Error

Cause: TimesTen cannot allocate memory from the heap for the CTN array in the context.

Impact: The database cannot continue normal operations.

User Action: Increase the value for the PermSize or TempSize attribute, or both. For more information on how to increase the values of PermSize and TempSize, see "Specifying the size of a database" in the Oracle TimesTen In-Memory Database Operations Guide.

16309

Error requesting sync point
for drift correction

Type of Message: Internal Error

Cause: This message is preceded by another message that describes the details of the error.

Impact: TimesTen cannot perform the operation.

User Action: Retry the operation. If the error persists, review the daemon log for any additional error messages to determine a cause for this error. For more information on how to review the daemon log, see "Using the logs generated by the TimesTen daemon" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

16999

Replication_message

This is an informational replication message that is found in the replication log. The message text provides details on the message.

Errors 17000 - 19999

Error number
Error or warning message
Details

17000

object owner.name was quoted
in an clause clause but
does not exist.

The table or cache group specified in an INCLUDE or EXCLUDE clause does not exist.

17001

The clause object clause
has the same name (object)
mentioned more than once.

The INCLUDE or EXCLUDE clause mentions the same table name or cache group name more than once.

17002

You cannot exclude
everything from being replicated.

All objects in the database were excluded in the CREATE REPLICATION statement. There must be at least one object in the database.

17003

Maximum number of peers
max_peers exceeded for
store

The limit on the maximum number of peer databases was exceeded. The message indicates the maximum limit.

17004

Table owner.table_name
of cache group
owner.cache_group_name
cannot be part of a
replication subscription if
the cache group is using
autorefresh.

A table that is part of an autorefresh cache group, whose autorefresh state is on, cannot be a subscriber in a replication scheme. Turn the AUTOREFRESH STATE to OFF.

17005

Cannot configure conflict
checking on a object_type
element

Conflict checking cannot be configured on a SEQUENCE element, for example.

17006

Cannot configure return
service on a
object_type element

Return service cannot be configured on a SEQUENCE element, for example.

17007

Sequence owner.sequence_id
cannot be replicated because
it was created with CYCLE
specified

TimesTen does not support the replication of sequences that were defined with CYCLE specified. If a replication element is created (either by CREATE REPLICAION or ALTER REPLICATION...ADD ELEMENT) and an INCLUDE or EXCLUDE clause is used or a ELEMENT SEQUENCE clause is used, and if the element involves a cycling sequence, then this error is generated.

17008

Sequence owner.sequence_id
will not be included in the
replication scheme as part of
this operation because it was
created with CYCLE specified

If a database level element is created (either by CREATE REPLICATION or ALTER REPLICATION...ADD ELEMENT) and a cycling sequence is involved, then the cycling sequence is not replicated.

17009

Stores store_name and
store_name on host host_name
would be using the same
replication port
(port_number). These stores
are not necessarily in the
same replication scheme.

The port number for the replicated databases conflict. Master and subscriber port numbers in a replication scheme must be the same.

17010

Store store_name has been
configured with a timeout of
msecs.  This is lower than
the recommended minimum of
num and could lead to
unnecessary replication
timeouts.

The replication connection timeout is below the recommended value. This may lead to many unnecessary connects and disconnects, thereby flooding the syslog and slowing down replication. The message indicates the minimum limit.

17011

The RELEASE attribute has
been specified for store
store_name. This feature has
been deprecated and the value
supplied has been ignored.

This feature has been deprecated.

17012

All AWT cache groups must be
part of the Active Standby
scheme. The AWT cache group
for table owner.table
has been quoted in an EXCLUDE
CACHE GROUP clause.

AWT cache groups cannot be excluded from an ACTIVE STANDBY scheme. Redefine your ACTIVE STANDBY scheme in such a way that these cache groups are included in the scheme.

17013

The default hostname cannot
be set to host_name because a
local host of host_name is
currently in use.

Using the built-in procedure ttHostNameSet you have specified a host name for a replication subscribe to a value that differs from the default host name already in use by a replication scheme. The host name is not changed. To view the current host name specified in the scheme, use the procedure ttHostNameGet.

17014

The replication heartbeat
factor must be between 0.25
and 4.0.

Internal error. A heartbeat factor outside of the specified range was supplied as a database attribute.

17015

The aging policy for table
table_name differs from its
peer: details.

The replication aging policy for a table used in a replication scheme differs between master and subscriber. The details can be one of:

Time-based aging versus LRU aging

No aging versus LRU aging

LRU aging versus time-based aging

Time-based aging versus no aging

Aging enabled versus aging disabled

Aging disabled versus aging enabled

Different lifetime

Different lifetime unit

Different cycle

Different cycle unit

17016

Error getting dbcharset ID

Type of Message: Internal Error

Cause: A sanity check between the master and subscriber of a replication scheme failed to identify the character set used in the database.

Impact: The replication agent cannot start correctly.

User Action: Check the additional error messages to identify a possible cause as to why the character set used in the database could not be identified. For additional help, contact TimesTen Customer Support.

17017

The database character set
differs from its peer

Type of Message: Internal Error

Cause: The database character set used by a master in a replication scheme is different than that used by the subscriber.

Impact: The replication agent cannot start correctly.

User Action: Check the character sets defined by the databases in your replication scheme. If the character sets differ, make the appropriate changes so that all databases are using the same character set. For more information, see "Database character set conversion" in the Oracle TimesTen In-Memory Database Installation Guide. If the character sets are the same, contact TimesTen Customer Support.

17018

Cannot replicate to peer
because it is a pre-7.0 data
store and this store does not
have the DatabaseCharacterSet
attribute set to 'TIMESTEN8'

For TimesTen to be able to replicate NCHAR type columns between this release and pre-7.0 releases of TimesTen the database in this release must have the DatabaseCharacterSet attribute set to TIMESTEN8.

17019

Store store_name on host_name
would be using the same
port as the daemon.

A replication configuration operation failed because the same port number as the main daemon was used for the database. Use a port number for the replication database that does not clash with the main daemon port.

17020

Failed to check CG state for
duplicate

TimesTen failed to check the state of cache groups in the source database. See the message log for the cause of the failure.

17021

Failed to reset Autorefresh
bookmark

As part of the -duplicate initialization, the autorefresh bookmarks for cache groups in the database could not be reset. See the message log for the cause of the failure.

17022

The same attribute
(attribute_name) has been
set multiple times for the
same subscriber
(subscriber_name) for
element element_name

An ALTER REPLICATION statement has altered the return service attribute more than once for the same database.

17023

Store store_name is used in
a route clause but does not
exist

A ROUTE clause quoted a non-existent database. Retry the operation with a different ROUTE name.

17024

ROUTE master master_name
subscriber subscriber_name
hostname host_name not found

A non-existent ROUTE name was specified in a statement that is attempting to ADD or DROP a route to a scheme. Retry the operation with a different ROUTE name.

17025

ROUTE master master_name
subscriber subscriber_info
subscriber_info cannot be
created because a
Master->Subscriber
relationship does not exist
between these stores

An attempt was made to set up a replication ROUTE for a non-existent master/subscriber relationship. Retry the operation with a different ROUTE name.

17026

ROUTE master master_name
subscriber subscriber_info
subscriber_info cannot be
created because an
entry for this route already
exists with priority
priority_level, or is in
the process of being created

The ROUTE name already exists. Retry the operation with a different ROUTE name or wait for the process that uses the specified ROUTE name to complete.

17027

ROUTE master master_name
subscriber subscriber_info
subscriber_info cannot be
created because an entry for
this route already exists
using interface interface, or
is in the process of being
created

The ROUTE name already exists. Retry the operation with a different ROUTE name or wait for the process that uses the specified ROUTE name to complete.

17028

The PRIORITY attribute must
be between 1 and 99

The specified PRIORITY value is out of range.

17029

This store (store_name on
host_name) is not involved as
a local store in replication
scheme host_name.scheme

A scheme is attempting to be created on a database that is not involved in the scheme. Retry the operation with the correct database name, or involve the database in the specified scheme.

17031

CONFLICT REPORTING RESUME
must be less than CONFLICT
REPORTING SUSPEND for STORE
store_name

The RESUME value must be less than the SUSPEND value for conflict reporting. Retry the operation with a smaller value.

17032

CONFLICT REPORTING RESUME
cannot be set without a
CONFLICT REPORTING SUSPEND
value for STORE store_name

You cannot resume conflict reporting without specifying a SUSPEND value. Retry the operation after specifying a SUSPEND value.

17033

CONFLICT REPORTING RESUME or
SUSPEND cannot be set for
stores in an Active Standby
scheme

Conflict resolution cannot be configured in an active standby scheme, therefore trying to supply conflict suspend/resume parameters is invalid.

17034

ASYNCHRONOUS WRITETHROUGH
Cache groups cannot co-exist
with a replication scheme
that uses RETURN TWOSAFE

You cannot have ASYNCHRONOUS WRITETHROUGH cache groups in a replication scheme that uses RETURN TWOSAFE.

17035

CONFLICT SUSPEND/RESUME
cannot be used with DATASTORE
level replication or ACTIVE
STANDBY schemes

Conflict resolution cannot be configured in a scheme that uses database level replication. Therefore attempting to supply conflict suspend/resume parameters is not allowed.

17036

SYNCHRONOUS WRITETHROUGH
cache groups cannot be
replicated in an ACTIVE
STANDBY scheme. Either DROP
or EXCLUDE the cache group
for table owner.table_name

SYNCHRONOUS WRITETHROUGH cache groups cannot be replicated in an ACTIVE STANDBY scheme.

17037

The receiver state in an
ACTIVE STANDBY scheme cannot
be set to STOP

When the database is involved in an active standby scheme, you cannot call ttrepsubscriberstateset(,,,,2) or specify the utility operation ttRepAdmin -receiver -name rep2 -host somemachine -dsn rep1 -state stop.

17038

The store is not a valid peer

The peer specified is not valid in the replication scheme.

17039

Failed to bind name (name);
socket: socket

Type of Message: Informational

Cause: The replication agent cannot bind to the specified host and IP address.

Impact: The replication agent will try connecting using other network interfaces. If the replication agent cannot connect using the other network interfaces, replication for the peer will not work.

User Action: Check the error messages to identify a possible cause as to why the bind failed.

17040

Trying to create socket for
name on DSN

Trying to create socket on an IP address for the indicated database.

17041

Failed to create Oracle DR scheme

This is a generic error, there is an additional detailed error message concerning the actual failure. Review that message to determine the problem and the fix.

17042

A Cache DR scheme can only
be created on an ACTIVE
STANDBY SUBSCRIBER

The ttRepAdmin -duplicate -initCacheDR option can only be used when duplicating to an active standby subscriber. You have attempted to create a disaster recovery scheme on a database that is not involved in active standby replication. This is not supported.

17043

Failed to initialize Oracle
DR tables

The initialization of the Oracle database Disaster Recovery tables failed. In the user error log, review any error messages that were returned during the operation in which the error occurred for more details. Destroy the destination database and attempt to re-initialize the disaster recovery process.

17044

Exited early because could
not get cache group
information

The disaster recovery process exited early because it could not get required information. In the user error log, review any error messages that were returned during the operation in which the error occurred for more details. Destroy the destination database and attempt to re-initialize the disaster recovery process.

17045

Could not truncate cached
tables on Oracle DR site

During disaster recovery, the replication agent could not truncate any cached tables. In the user error log, review any error messages that were returned during the operation in which the error occurred for more details. Destroy the destination database and attempt to re-initialize the disaster recovery process.

17046

Could not flush data to
Oracle DR site

During disaster recovery, the replication agent could not flush data to the Oracle database. In the user error log, review any error messages that were returned during the operation in which the error occurred for more details. Review any error messages that were returned during the operation in which the error occurred for more details. Destroy the destination database and attempt to re-initialize the disaster recovery process.

17047

Could not commit data to the
Oracle DR site

During disaster recovery, the replication agent could not commit data to the Oracle database. In the user error log, review any error messages that were returned during the operation in which the error occurred for more details. Destroy the destination database and attempt to re-initialize the disaster recovery process.

17048

Could not create thread to
initialize the Oracle DR site

During disaster recovery, the replication agent could not create the thread to initialize the Oracle database. In the user error log, review any error messages that were returned during the operation in which the error occurred for more details. Destroy the destination database and attempt to re-initialize the disaster recovery process.

17049

Error invalidating store due
to scheme inconsistency

To correct this problem, verify that the schemes involved in this operation are identical.

17050

Conflict Replication
Reporting starting

Type of Message: Informational

Cause: Replication conflict reporting suspend/resume is configured on your system and the conflict rate has fallen below the resume value.

Impact: Replication conflict reports are now being sent.

User Action: None.

For more information on how to configure suspend and resume values for replication conflict reporting, see "Suspending and resuming the reporting of conflicts" in the Oracle TimesTen In-Memory Database Replication Guide.

17051

Conflict Replication
Reporting stopping

Type of Message: Informational

Cause: Replication conflict reporting suspend/resume is configured on your system and the conflict rate exceeds the suspend value.

Impact: Replication conflict reports are now suspended.

User Action: None.

For more information on how to configure suspend and resume values for replication conflict reporting, see "Suspending and resuming the reporting of conflicts" in the Oracle TimesTen In-Memory Database Replication Guide.

17052

System table owner.table
cannot be excluded from
replication

System tables cannot be modified by users and must be included in the replication process.

17053

Table table_name is
replicating in relaxed mode.

Type of Message: Informational

Cause: The master table being replicated is structurally different than the subscriber.

Impact: Extra performance overhead is required to achieve replication for this table.

User Action: You can improve replication performance if the table structure on both sides of the replication scheme is the same. Adjust the table structure on one side of the replication scheme so that it matches the table structure of its peer. For more information, see "Altering a replicated table in a classic replication scheme" in the Oracle TimesTen In-Memory Database Replication Guide.

17055

Asynchronous Materialized
View Log Table schema.table
cannot be included in a
Replication Scheme.

An explicit ALTER replication include table was used on an Asynchronous materialized view log table.

17056

Dynamic Cache Group Table
schema.table can only be
replicated in an ACTIVE
STANDBY PAIR replication
scheme

A dynamic cache group can only be replicated if the replication scheme is an active standby pair. Dynamic cache groups cannot be replicated with regular replication.

17057

PROPAGATE cache groups
cannot be replicated in an
ACTIVE STANDBY scheme.
Either DROP or EXCLUDE the
cache group for table
schema.table

User managed cache groups with propagated tables are not allowed in active standby replication schemes. You must either drop the cache group or exclude it from the replication scheme.

17058

Table owner.table cannot be
part of a replication scheme
when parallel mode replication
is configured because it is
defined with aging

You cannot include a table in a replication scheme when it has aging configured and ReplicationApplyOrdering=1.

17059

Replicated INCLUDE TABLE
failed for (owner.table)
because the table is not
empty

You attempted a replicated ALTER STANDBY PAIR...INCLUDE TABLE and the table is not empty.

17060

DDLReplicationAction
can only be set to INCLUDE
or EXCLUDE on the ACTIVE
store in an ACTIVE STANDBY
PAIR replication scheme

You attempted ALTER SESSION...SET DDL_REPLICATION_ACTION on a database that is not active in the active standby pair replication scheme.

17061

When DDLReplicationAction =
'INCLUDE' tables must be
created with a primary key
or a unique constraint on
non-nullable column(s)

You specified a DDL_REPLICATION_ACTION that requires the table(s) to be created with an index.

17062

DDLReplicationAction and
DDLReplicationLevel can only
be set on a store with an
ACTIVE STANDBY PAIR scheme

You attempted to use the ALTER SESSION statement to set DDLReplicationAction and DDLReplicationLevel on a database that is not part of an active standby pair scheme.

17063

CREATE INDEX can only refer
to empty tables when
DDLReplicationLevel > 1

When DDLReplicationLevel is greater than 1, CREATE INDEX is replicated. However, your tables must be empty.

17064

CREATE AS SELECT cannot be
used when DDLReplicationLevel
> 1

When DDLReplicationLevel is greater than 1, CREATE TABLE is configured for replication. However, CREATE TABLE AS SELECT is not supported.

17065

Action not permitted because
DDLReplicationLevel > 1
and the store is not active

DDL action is not permitted because DDLReplicationLevel is greater than 1 and the database is not active.

17066

Create Table not permitted
without ADMIN privilege when
DDLReplicationLevel > 1 and
DDLReplicationAction is INCLUDE

When DDLReplicationLevel is greater than 1 and when DDLReplicationAction is set to INCLUDE, then ADMIN privilege is required when replicating CREATE TABLE statements.

17067

Table table was
truncated before inclusion
into the ACTIVE STANDBY PAIR
replication scheme

When ALTER ACTIVE STANDBY PAIR...INCLUDE is executed, the table contents are truncated on the standby and subscriber(s) databases.

17068

Invalid value (value) for
ttDurableWhenAgentStoppedSet.
Valid values are 0 and 1.

You specified an invalid value for ttDurableWhenAgentStoppedSet.

17069

stmt is not permitted on the
standby in an ACTIVE STANDBY
PAIR scheme

The statements CREATE/DROP SYNONYM, GRANT/REVOKE, or CREATE/ALTER/DROP USER are not permitted on the standby in an ACTIVE STANDBY PAIR scheme.

17071

XLA encountered an error
during start-up: error_number

Type of Message: Error

Cause: The replication agent cannot correctly start the XLA thread because an error was encountered.

Impact: The replication agent will periodically try to start the XLA thread until the specified error is fixed.

User Action: Diagnose and troubleshoot the specified TimesTen error.

17072

Failed to read Sync CTN Reset
value

Type of Message: Error

Cause: The state of the transmitter has changed. The active node is invalid, causing the standby node to become the new active node, but the replication agent of the original active node is still running. The original active node switches to a standby state and no new transactions are being issued on the new active node.

Impact: If the blocking situation persists, the new standby node can get stuck in a disconnection and reconnection cycle. The threads will attempt to recycle and self-correct the error.

User Action: Review the error message for possible fixes.

17073

Restarting subscriber
transmitters due to Sync CTN
Reset

Type of Message: Informational

Cause: The state of the transmitter has changed, but the commit ticket number sync reset value has been properly recycled.

Impact: The replication agent is restarting the subscriber transmitter threads.

User Action: None.

17075

Read-write lock object not
initialized

Type of Message: Warning

Cause: A timeout occurred while trying to acquire a read-write lock.

Impact: The user error log may contain an additional error message.

User Action: Review the user error log for error messages indicating a possible replication agent failure in acquiring a resource. Attempt the fixes for the replication agent failure error messages.

17076

Timeout while retrieving peer
information

Type of Message: Warning

Cause: A lock could not be acquired before the timeout expired.

Impact: Peer information cannot be obtained. The user error log may contain an additional error message.

User Action: Review the user error log for error messages indicating a possible replication agent failure in acquiring a resource. Attempt the fixes for the replication agent failure error messages.

17077

DeadLock while retrieving
peer information

Type of Message: Warning

Cause: A deadlock occurred while trying to acquire a lock.

Impact: Peer information cannot be obtained. The user error log may contain an additional error message.

User Action: Review the user error log for error messages indicating a possible replication agent failure in acquiring a resource. Attempt the fixes for the replication agent failure error messages.

17078

Mutex abandoned while
retrieving peer information

Type of Message: Warning

Cause: Mutual exclusion was abandoned while attempting to acquire a lock.

Impact: Peer information cannot be obtained. The user error log may contain an additional error message.

User Action: Review the user error log for error messages indicating a possible replication agent failure in acquiring a resource. Attempt the fixes for the replication agent failure error messages.

17079

Invalid SQL command
at :function_name

Type of Message: Error

Cause: The replication agent attempted to execute an invalid SQL command.

Impact: The replication agent cannot update the metadata. The replication agent will retry the operation.

User Action: None.

17080

Read Only Cache Group
cache_group must first be
excluded from the A/S pair
replication scheme before
executing this operation.

Type of Message: Error

Cause: You attempted to drop a read-only cache group that is part of a replication scheme.

Impact: TimesTen cannot drop the read-only cache group.

User Action: Exclude the read-only cache group from the replication scheme by using the EXCLUDE parameter of the ALTER ACTIVE STANDBY PAIR SQL statement. Then, retry dropping the read-only cache group. For more information on the ALTER ACTIVE STANDBY PAIR SQL statement, see "ALTER ACTIVE STANDBY PAIR" in the Oracle TimesTen In-Memory Database SQL Reference.

17081

Failover message sent to
client connection_info

Type of Message: Informational

Cause: An application requested failover support from the replication agent for an active standby pair replication scheme. Once the replication agent determines that the application is connected to a database other than the active master database, the replication agent sends a client failover message to the application.

Impact: None.

User Action: None.

For more information on active standby pair replication schemes, see "Active standby pair with read-only subscribers" in the Oracle TimesTen In-Memory Database Replication Guide.

17083

XLA is not permitted with
ReplicationApplyOrdering = 2

Type of Message: Error

Cause: You attempted to create a XLA bookmark in a replication scheme using automatic replication with disabled commit ordering (ReplicationApplyOrdering=2).

Impact: TimesTen cannot perform the operation.

User Action: Set the ReplicationApplyOrdering attribute to 0 or 1 and retry the operation. For more information on XLA bookmarks, see "About XLA bookmarks" in the Oracle TimesTen In-Memory Database C Developer's Guide. For more information on parallel replication and the ReplicationApplyOrdering attribute, see "Configuring parallel replication" in the Oracle TimesTen In-Memory Database Replication Guide and "ReplicationApplyOrdering" in the Oracle TimesTen In-Memory Database Reference.

17084

Only ACTIVE STANDBY pair
replication schemes are
permitted with
ReplicationApplyOrdering = 2

Type of Message: Error

Cause: You attempted to create a replication scheme that is not supported while using automatic replication with disabled commit ordering (ReplicationApplyOrdering=2).

Impact: TimesTen cannot perform the operation.

User Action: Set the ReplicationApplyOrdering attribute to 0 or 1 and retry the operation. For more information on parallel replication and the ReplicationApplyOrdering attribute, see "Configuring parallel replication" in the Oracle TimesTen In-Memory Database Replication Guide and "ReplicationApplyOrdering" in the Oracle TimesTen In-Memory Database Reference.

17085

No return services are
permitted with
ReplicationApplyOrdering = 2

Type of Message: Error

Cause: You attempted to create a replication scheme with return services enabled while using automatic replication with disabled commit ordering (ReplicationApplyOrdering=2).

Impact: TimesTen cannot perform the operation.

User Action: Set the ReplicationApplyOrdering attribute to 0 or 1 and retry the operation. For more information on parallel replication and the ReplicationApplyOrdering attribute, see "Configuring parallel replication" in the Oracle TimesTen In-Memory Database Replication Guide and "ReplicationApplyOrdering" in the Oracle TimesTen In-Memory Database Reference.

17086

ASYNCHRONOUS WRITETHROUGH
Cache groups are only
permitted with ACTIVE STANDBY
PAIR replication schemes.

Type of Message: Error

Cause: You attempted to create an asynchronous writethrough (AWT) cache group in a replication scheme that does not support AWT cache groups.

Impact: TimesTen cannot perform the operation.

User Action: Set an active standby pair replication scheme and retry the operation. For more information on AWT cache groups, see "Asynchronous writethrough (AWT) cache group" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on active standby pair replication schemes, see "Active standby pair with read-only subscribers" in the Oracle TimesTen In-Memory Database Replication Guide.

17087

CTN Wait Error wait_type

Type of Message: Informational

Cause: The replication agent aborted a parallel replication wait. This message is followed by another message that describes the details of the error.

Impact: Depending on the cause, the impact may vary.

User Action: Review the daemon log for any additional error messages to determine a cause for this error. For more information on how to review the daemon log, see "Using the logs generated by the TimesTen daemon" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

19000

Open of document
document_name failed

The TimesTen Web server received an error while sending data to the browser. Attempt to open the document again and verify that you have entered the correct name of the document.

19001

Send of number_of bytes to
browser failed, error
error_number

The TimesTen Web server received an error while sending data to the browser. The error referenced in this message provides more details on the problem.

19002

Spawn of CGI script, failed,
error error_number

The TimesTen Web server received an error while spawning a CGI script. The error referenced in this message provides more details on the problem.

19003

Write of POST data failed

The TimesTen Web server received an error while sending POST parameters to a CGI process.

19004

CGI script script_name not
executable

A CGI script requested of the TimesTen Web server is not executable. Check your installation to verify that the script is in the correct location and has the appropriate privileges.

19005

Web server bind to port
failed, error error_number

The TimesTen Web server was unable to bind to its port. The port may be in use by another process. Verify that you specified the correct port number.

19006

Cannot filed perl in path

The TimesTen Web server was unable to find the version of PERL with the product. Check your installation.

19007

Web server system_call
failed, error error_number

The TimesTen Web server was unable to get the host name of the client.

19008

Invalid HTTP date from
client (string)

A date sent to the TimesTen Server is in an invalid format.

19009

Stat of file_name failed,
error error_number

The TimesTen Web server was unable to determine file information for an HTTP document.

19010

Web server denying
connection from host_name
(IP_address)

The TimesTen Web server is denying access from the indicated host. The Web server configuration file can be used to control access.

19011

Authorization failure from
file_name

The TimesTen Web server is denying access to a password-protected page because the user name supplied is unknown or the password does not match. Verify that you have supplied the correct user name and password.

19012

Cannot open password file
file_name

The TimesTen Web server is unable to open its password file. Check your installation.

19013

Bad entry in password file
file_name

There is a bad entry in the TimesTen Web server's password file. Correct the entry and try again.

19014

TimesTen web server internal
error

The TimesTen Web server has encountered an internal error. See the TimesTen user error log for more information.

Errors 20000 - 39999

Error number
Error or warning message
Details

20000

Use of a deprecated feature:
feature_details

This warning indicates use of a feature that is being supported only for backward compatibility. The feature may be removed in a future release. The feature_details text indicates the feature being used and suggests the appropriate course of action.

20100

This connection required
recovery due to an improper
shutdown

When a connection is made after an improper shutdown, a recovery process replays the logs to restore the database to its most current state. This recovery process can be time-consuming. To avoid it, cleanly disconnect from the database when possible. For example, do not exit from a TimesTen application without first waiting for all connections to disconnect. Use signal handlers to catch signals that set a variable indicating that all connections must disconnect.

20101

Data loss because redo
logging was disabled. Connect
with ttAdmin -ramLoad -force.

Type of Message: Error

Cause: The connection attempt failed because an irrecoverable error occurred while redo logging was disabled.

Impact: Any changes made to the database while redo logging was disabled have been lost.

User Action: To permit new connections, explicitly load the database into memory. Load the database into memory using ttAdmin -ramLoad -force. For more information, see "ttAdmin" in the Oracle TimesTen In-Memory Database Reference.

30103

SQLParamOptions is not
supported with result-set
returning statements

An attempt was made to execute a SELECT statement using an array of parameters as indicated by SQLParamOptions. Batch execution using arrays of parameters is supported only with INSERT, UPDATE and CREATE VIEW statements.

30104

SQLBindParameter must be
called because the
ConnectionCharacterSet
attribute was changed

Type of Message: Error

Cause: The ConnectionCharacterSet value was changed after the parameters were bound to the statement.

Impact: If execution continues, incorrect data could be passed in the parameter values due to character set mismatch.

User Action: To allow correct character set conversion, rebind the statement parameters using the SQLBindParameter function. For more information, see "SQLBindParameter function" in the Oracle TimesTen In-Memory Database C Developer's Guide.

30105

Transaction must roll back

Type of Message: Error

Cause: A TimesTen client server failover to the new active (original standby node) occurred.

Impact: The current transaction must be rolled back or committed before further operations can be done.

User Action: Call ROLLBACK on the current connection handle with the SQLTransact call. For more information, see "Making and committing changes to the database" in the Oracle TimesTen In-Memory Database C Developer's Guide.

30106

Transaction status unkown

Type of Message: Error

Cause: The current transaction cannot be committed for unknown reasons.

Impact: The current transaction is assumed to have rolled back and that the operations from the transaction are lost.

User Action: Open a new transaction to complete new operations.

Errors 40000 - 49999

Error number
Error or warning message
Details

40005

sbHttpListParse returned NULL

Internal error. Daemon cannot honor a request from the cache agent. The reply message cannot be parsed. Contact TimesTen Customer Support.

40006

Could not connect to
TimesTen. Cache timer thread
exit.

The cache agent cannot connect to TimesTen. The timer thread used by cache aging is exiting. Review the connection settings and restart the cache agent to begin aging.

40007

Could not connect to
TimesTen. Cache aging thread
exit.

The cache agent cannot connect to TimesTen. The timer thread used by cache aging is exiting. Review the connection settings and restart the cache agent to begin aging.

40008

Could not do aging,  Cache
aging thread will try to
reconnect in 1 minute.

The cache aging operation was unable to complete, the cache agent disconnects and then reconnects and retries in one minute. If the problem does not resolve itself after several retries, review the user error log to find the cause of the aging failure.

40009

Error reading from deadman
socket

The cache agent failed to read from the daemon socket. Cache agent is shutting down. If the cache agent does not restart automatically, restart it manually. If that does not work, then restart the main TimesTen daemon and then restart the cache agent manually if the cache agent policy requires it to be restarted manually.

40010

Data read, fatal internal
error

Internal error. The cache agent failed to read from the daemon socket. Cache agent is shutting down. If the cache agent does not restart automatically, restart it manually. If that does not work, then restart the main TimesTen daemon and then restart the cache agent manually if the cache agent policy requires it to be restarted manually.

40011

Subdaemon exiting, main
daemon gone

The cache agent detected that the TimesTen daemon is down. The cache agent is shutting down. To continue, restart the main TimesTen daemon. Then, restart the cache agent, if it does not restart automatically.

40012

Error code setting
synchronous sockets

The cache agent cannot set a synchronous socket during startup. The operating system error code is displayed in the message. Remove the cause of OS error and restart the cache agent.

40013

Connect fail from
connectToDaemon port portID
as id selfID

Internal Error. The cache agent failed to connect to the TimesTen daemon at port portID as ID selfID. The TimesTen daemon may have died unexpectedly. Check the status of the main TimesTen daemon.

40014

Could not create core
service thread, exiting

The cache agent cannot create one of its core service threads at startup. It is shutting down.

40015

Could not initialize
connection to daemon

The cache agent cannot initialize the connection to daemon at startup. The cache agent is shutting down. The TimesTen daemon may have died unexpectedly. Check the status of the main TimesTen daemon.

40016

Daemon did not accept port
setting. Message: message,
Error Code: code

Internal error. Daemon did not accept cache agent port setting. The details are included in this message.

40017

Daemon did not accept port
setting. Return code: code1
Request Return code: code2

Internal error. Daemon did not accept cache agent port setting. The details are included in this message.

40018

TimesTen error code:code
msg message

The cache agent has generated a Native TimesTen error. For more information see the description for that error in this chapter.

40019

Unable to allocate an ODBC
environment handle

The cache agent failed to allocate an ODBC environment handle. Refer to ODBC documentation to find the cause of failure.

40020

Could not allocate ftclock,
exiting

Internal error message. ftClock thread cannot be initialized. Contact TimesTen Customer Support.

40021

Could not create cache
shutdown event, exiting

The cache agent cannot create an object that is used internally at startup. There may be insufficient memory or other a shortage of another system resource to initialize a condition variable. Stop the cache agent, free up the resources and restart the cache agent.

40022

Could not create thread_name
thread, agent will be
restarted

The cache agent could not create the indicated thread. This may be caused by a lack of system resources to create another thread or the system limit on the total number of threads in a process may have been exceeded. Stop the agent, free up resources or adjust the system limit and restart the cache agent.

40026

Could not initialize
internal structure for
scheduler, agent will be
restarted

The cache agent could not initialize an internal structure for the scheduler. The cache agent is restarting automatically. This message usually follows another message that describes the details about the failure.

40030

Cache agent has exceeded the
maximum TimesTen connection
limit of limit

The cache agent has too many connections to TimesTen. This is often caused by a lot of autorefresh attempts. Alter the autorefresh intervals on your cache groups to be less frequent and so that they are similar on most of your cache groups.

40031

Connect failed (message)

The cache agent failed to connect either to the TimesTen main daemon or to the Oracle database. The message included in this error may give more details. In addition, this message usually follows another message that describes the details about the failure.

40034

Last number_of
autorefreshes failed for
cache groups within interval
msecs ms. Autorefresh will
be retried silently

The latest indicated number of have failed. The autorefresh operation is retried without writing new messages to the user error log. This message usually follows another message that describes the details about the failure.

40035

Autorefresh number number
failed for cache groups with
interval msecs ms after
number retries.

An autorefresh for the indicated interval has failed. This message usually follows another message that describes the details about the failure. The autorefresh operation is being retried automatically.

40036

Create/alter cache group
failed because autorefresh
for cache group
cache_group_name is in the
middle of shutting down

CREATE CACHE GROUP and ALTER CACHE GROUP statements cannot be processed while the cache agent is shutting down the autorefresh thread for the cache group. Wait for the thread to finish shutting down and retry your DDL operation.

40037

Could not allocate a new
cache group structure.
Scheduler thread exiting

The cache agent failed to allocate a new cache group structure. This may happen in response to CREATE CACHE GROUP or ALTER CACHE GROUP operation when there is a lack of memory or other system resource. One of the service threads (scheduler) is shutting down and autorefresh for all cache groups is stopped. Make the resource available and restart the cache agent.

40038

Could not allocate a new
refresher structure.
Scheduler thread exiting

The cache agent failed to allocate a new refresh structure. Cache agent fails to allocate a new refresh structure. This may happen in response to CREATE CACHE GROUP or ALTER CACHE GROUP operation when there is a lack of memory or other system resource. One of the service threads (scheduler) is shutting down and autorefresh for all cache groups is stopped. Make the resource available and restart the cache agent.

40042

Join of
refresher-thread_name failed

A thread join with a refresher thread failed during cache agent shutdown.

40043

ODBC error from API call:
api_name

The specified ODBC call failed. Refer to the ODBC documentation for details.

40044

No data source or driver
specified; dialog prohibited.
Check the DSN definition in
the ODBC system
administrator. The DSN must
be a system DSN.

This error only occurs on Windows systems. The cache agent could not connect to the TimesTen database because the data source or driver was not specified. Check the system DSN settings for this database.

40045

No data source or driver
specified; dialog prohibited.
Check the DSN definition in
the sys.odbc.ini file. The
DSN must be a system DSN.

This error only occurs on UNIX systems. The cache agent could not connect to the TimesTen database because the data source or driver was not specified. Check the system DSN settings for this database.

40046

Error: mesage, ODBC SQL
state = SQL_state,
Additional Warning = code

The specified ODBC call failed with the indicated details.

40047

Call to SQLError failed with
SQL_SUCCESS_WITH_INFO. Need
to increase size of message
buffer.

Internal Error, the cache agent's internal error buffer is too small for SQLError ODBC API call. Contact TimesTen Customer Support.

40048

Call to SQLError failed with
SQL_INVALID_HANDLE.

Internal Error, the ODBC statement, connection, or environment handle passed to SQLError was invalid. Contact TimesTen Customer Support.

40049

Call to SQLError failed with
SQL_ERROR.

Internal error, the call to SQLError fails to get more diagnostic information after a failed ODBC operation. Contact TimesTen Customer Support.

40050

Detected invalid data store.

TimesTen database has been invalidated, Cache agent shuts down, then restarts. Try the operation again.

40051

Cannot attach to Oracle
Server (Oracle error
ORA-number).
OracleNetServiceName =
onet_svc_name, ORACLE_HOME
= Oracle_Home

The cache agent cannot connect to the Oracle database. The Oracle database error code is included in the message. Refer to "Unable to resolve Oracle Service Name" and "Unable to validate the Oracle database username and password" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40052

Cannot start an Oracle
session (Oracle error
ORA-code). uid = user_name.
pwd is hidden, TNS_ADMIN =
tns_path , ORACLE_HOME=
Oracle_install_dir

Cannot start an Oracle database session. The Oracle database error code and the intended user name are included in the message. The password is hidden for security reasons. Refer to "Unable to resolve Oracle Service Name" and Unable to validate the Oracle database username and password" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40053

OCIEnvCreate failed. Return
code code_number

Calling OCIEnvCreate fails. The return code is included in the message. Verify the Oracle database client installation. Refer to "Unable to resolve Oracle Service Name" and Unable to validate the Oracle database username and password" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40054

Could not login to Oracle.
TNS timeout occurred.

Received a TNS timeout error while trying to login to the Oracle database. Check the Oracle database client/server setting and the network health. If the problem does not get fixed after an automatic restart, check the connection and restart cache agent. Refer to "Unable to resolve Oracle Service Name" and Unable to validate the Oracle database username and password" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40055

Delete query too long during
unload.

The system generated a query overflow in the system buffer, while executing an unload statement. This is usually caused by very a long WHERE clause in the UNLOAD CACHE GROUP statement, a large number of tables in the cache group, or very long WHERE clause in the cache group definition.

40056

Not connected to Oracle
during load

Internal error. A connection to the Oracle database was not established before the loading operation. Contact TimesTen Customer Support.

40057

Table name too long:
table_name.

Internal error. The table name is too long. A table name cannot exceed 30 characters.

40058

Select query too long during
load.

While executing a load statement, the system generated SELECT query overflowed a system buffer. This is usually caused by a very long WHERE clause in the LOAD statement, a large number of tables in the cache group, or very long WHERE clause in the cache group definition.

40059

Select list too long during
load.

While executing a load statement, the system generated SELECT query overflowed a system buffer. This is usually caused by a very long WHERE clause in the LOAD statement, a large number of tables in the cache group, or very long WHERE clause in the cache group definition.

40060

Error preparing Oracle
statement: statement

There was an error while preparing the specified SQL statement on the Oracle database.

40061

Error executing Oracle
statement: statement

There was an error while executing the specified SQL statement on the Oracle database.

40062

Column count does not match
for cached table

The Oracle database table columns do not match the cached table columns. Check to determine if the Oracle database table schema has been changed since the cache group was created.

40064

Rowid descriptor alloc
failure

The call to OCIDescriptorAlloc failed.

40066

Internal buffer overflow
during autorefresh
initialization

Autorefresh initialization failed because an internal buffer has overflowed. The required buffer size is proportional to the number of tables in the cache group, the number of columns, the number of columns in the primary key or foreign key, and the length of the WHERE clause of the cache group.

40067

Failed during restarting
autorefresh

Failed to restart autorefresh for some cache groups during cache agent startup. This message usually follows another message that describes the details about the failure.

40068

Failed to prepare the
TimesTen SQL statement: statement

The cache agent encountered an error while preparing a TimesTen SQL statement. This message usually follows another message that describes the details about the failure.

40069

Failed to retrieve from
Oracle change log. query =
query, curSOLog=log

The cache agent failed to retrieve rows from the Oracle database change log for autorefresh. The failing query and the current log content are specified in this message. Ensure that the Oracle database table objects for autorefresh have not been removed and the autorefresh user has not been changed since the creation of the cache group.

40070

Timeout while dropping an
Oracle table. The query is
query

A timeout occurred while dropping an Oracle database table. The optional failed query is specified in the message. This may occur in response to either a ALTER CACHE GROUP or a DROP CACHE GROUP operation when the table is busy. The drop is retried when the cache agent gets restarted. If necessary, restart the cache agent to drop the table immediately.

40071

Table is not found in
Oracle: owner.table

The specified table cannot be found in the Oracle database.

40072

Failed in
checkAutorefreshConnections,
bad argument

Internal error. The autorefresh connection is bad. Contact TimesTen Customer Support.

40073

Could not drop the Oracle
objects. Either an
Autorefresh uid was not
provided or the uid was
invalid.

Failed to drop Oracle database objects for autorefresh because either the cache administration user ID was not given or the UID was incorrect. Ensure that the cache administration user ID provided at cache agent startup time is correct.

40076

Failed calling OCI function:
function_name

The cache agent failed while calling the specified OCI API function. This message is usually followed by another message that describes the details about the failure.

40077

Oracle native error code =
error_code, msg = message

The cache agent encountered a native Oracle database error while calling an OCI function. The details are included in this message.

40078

Assertion failed: message

Internal error. A cache agent internal consistency check failed. Contact TimesTen Customer Support.

40079

Failed to malloc size
memory_size. Please free
system resources.

Failed to malloc memory of the indicated size.

40081

Failed to get Oracle
username and password:
error_number

Failed to get the Oracle database user name and password, the details are included in this message.This may happen during the cache agent startup. This message usually follows another message which describes the details about the failure. The cache agent gets automatically restarted when this error occurs.

40083

Cache agent startup command
line value missing for flag
flag

Internal error. The main TimesTen daemon started the cache agent with missing values for the indicated flag. Contact TimesTen Customer Support.

40084

Cache agent startup command
line flag flag has
incorrect value value

Internal error. The main TimesTen daemon started the cache agent with incorrect values for the specified flag. Contact TimesTen Customer Support.

40086

Could not allocate Oracle
statement handle

Error allocating Oracle database statement handle. Contact TimesTen Customer Support.

40087

Could not allocate TimesTen
statement handle

Error allocating a TimesTen statement handle. Contact TimesTen Customer Support.

40088

Log reader
TTC_FT_OBJECT_PREFIXgetMinSCN
returned OCI_NO_DATA

Internal error. getMinSCN should have returned at least one row, but was unable to do so. Contact TimesTen Customer Support.

40089

Log reader getLmLock
returned OCI_NO_DATA

Internal error. getLmLock should have returned at least one row, but was unable to do so. Contact TimesTen Customer Support.

40090

Log reader getLmUserCount
returned OCI_NO_DATA

Internal error. getLmUserCount should have returned at least one row, but was unable to do so.Contact TimesTen Customer Support.

40091

Log reader getLmUserCount
returned OCI_NO_DATA

Internal error. getLogLimit should have returned at least one row, but was unable to do so. Contact TimesTen Customer Support.

40092

Oracle type type not
supported

Internal error. Oracle database type for the primary key is not supported. Contact TimesTen Customer Support.

40093

Could not parse redo SQL
cscn:cscn_name, SQL: statement

Internal error. Parsing of redo SQL statement failed. Contact TimesTen Customer Support.

40094

Unable to get primary key
metadata for base table
table_name, log table
table_name

Internal error. Unable to get metadata for primary keys for the indicated base and log tables. Contact TimesTen Customer Support.

40096

Log reader initialization
failed

Log reader allocation failed. Contact TimesTen Customer Support.

40108

Could not derive the data
store file name. Data store
path = path_name

Internal Error. TimesTen could not derive the database name from the provided database input parameter to cache agent. Contact TimesTen Customer Support.

40114

Connection to Oracle has not
succeeded for last num
minutes. Number of failed
attempts: num. Initiating
cache agent restart.

At cache agent startup time, the cache agent cannot connect to the Oracle database. A CREATE CACHE GROUP or an ALTER CACHE GROUP statement can encounter this error because the operation was attempted too soon after the cache agent was started or because the cache agent was unable to establish a connect to the Oracle database. Messages in the user error log may provide details on the connection failures. If the problem does not resolve itself after several attempts, manually restart the cache agent. For more details see "Unable to resolve Oracle Service Name" and "Unable to validate the Oracle database username and password" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40115

No cache groups will be
autorefreshed until a connect
to Oracle can be established.
Will try to connect to Oracle
silently every seconds
seconds. Additional error
information: message.

At cache agent startup time, the cache agent cannot connect to the Oracle database. The cache agent keeps trying to connect to the Oracle database.

40116

Fatal error occurred while
trying to connect to Oracle.
Check the Oracle Id, UID, PWD
and the status of Oracle
instance. No autorefreshing
will occur until the problem
is resolved and cache agent
has been restarted.

At cache agent startup time, the cache agent cannot connect to the Oracle database. The cache agent automatically shuts down and restarts. If the problem does not get fixed after this automatic restart, you should stop the cache agent, check the OracleID, UID, PWD, and the status of the Oracle database instance and restart cache agent.

40117

AUTOREFRESH LOGSEQ ERROR:
LogSeq(number) =
error_number considered not
valid. It will not be stored
in the datastore.

Internal Error. TimesTen saw an invalid bookmark when trying to store the log sequence into TimesTen. The autorefresh cannot move forward. It resumes from the last valid LogSeq number.

40119

An error occurred while
preparing or executing the
following Oracle SQL
statement: statement

This message usually follows another message that describes the details about the failure.

40120

Autorefresh has not
succeeded for cachegroups
with interval interval ms
for last minutes minutes.
Number of failed attempts:
num. Initiating cache agent
restart.

Autorefresh for the specified interval has failed in the indicated minutes, after the indicated number of attempts. The cache agent is restarting.

40121

Auto-Refresh failed (Could
not turn on table locking)

Table-level locking could not be turned on for this autorefresh transaction. This autorefresh is being terminated and retried.

40122

Could not parse fullname,
name, in owner and name.

TimesTen was unable to parse the cache group name during the autorefresh object validation for the specified cache group. Contact TimesTen Customer Support.

40123

Autorefresh trigger
trigger_name is not enabled
for table table_name. The
cache group
cache_group_name in data
store data_store_name will
not be refreshed.

Autorefresh Oracle database object validation for cache groups finds that the Oracle database trigger trigger_name on the indicated table is not enabled. Autorefresh cannot work for the table. Either ALTER the AUTOREFRESH state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40124

Could not find autorefresh
trigger trigger_name. The
cache group
owner.cache_group_name in
data store data_store_name
will not be refreshed.

Autorefresh Oracle database object validation for cache groups finds that the Oracle database trigger trigger_name on the indicated table of the cache group was not found on the Oracle database. Autorefresh cannot work for the cache group. Either alter the AUTOREFRESH state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40125

Could not find the Oracle
autorefresh object_type
object_name for table
table_name. The cache group
cache_group_name cannot be
refreshed in any datastores.

A table in the cache group cache_group_name did not find the autorefresh object on the Oracle database. Autorefresh cannot work for the cache group. Either alter the Autorefresh state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40126

Autorefresh obj_type obj_name
for table table_name is not
valid on Oracle. The cache
group cache_group_name will
not be refreshed.

Autorefresh Oracle database object validation for a cache group table found an invalid status for an autorefresh object on the Oracle database. Autorefresh cannot work for the cache group. Either alter the Autorefresh state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40127

Internal error: could not
compute the difference of two
dates.

Autorefresh object validation could not complete because of this error.

40128

Oracle object id is
different - Oracle table
table_name has been
recreated since the cache
group cache_group_name in
data store data_store_name
was created. The cache group
will not be refreshed

Autorefresh object validation for the cache group found an incompatibility between the cache group objectID and the objectID on the Oracle database. This could have been caused when a table was created on the Oracle database after the cache group was created. Autorefresh cannot work for the cache group. Either alter the Autorefresh state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40129

Oracle create date changed -
Oracle table table_name has
been recreated since the
cache group
cache_group_name in data
store data_store_name was
created. The cache group will
not be refreshed

Autorefresh object validation for the cache group found an incompatibility between the create date for the specified table in a TimesTen database and that on the Oracle database. This could have been caused when a table was created on the Oracle database after the cache group was created. Autorefresh cannot work for the cache group. Either alter the Autorefresh state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40130

AutoRefresh log table is
older than base table -
Oracle table table_name has
been recreated since the
cache group
cache_group_name in data
store data_store_name was
created. The cache group will
not be refreshed

The error occurs when autorefreshing Oracle database object validation for the cache group. A change log table for table table_name is older than the table itself. This could have been caused when a table was created on the Oracle database after the cache group was created. Autorefresh cannot work for the cache group. Either alter the autorefresh state of cache group to OFF and then back to ON, or drop and recreate the cache group. For details on fixing this problem, refer to the ""Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40131

Could not parse table names
for cache group
owner.cache_group_name.

Internal Error. The cache agent was unable to parse the tables names during the autorefresh object validation for the specified cache group. Autorefresh object validation could not complete because of this error.

40132

Could not find user count
row for table table_name in
cache_group_name. Any
autorefreshed cache group
containing table table_name
will not be refreshed.

An autorefresh validation check could not find the Oracle database user count row for the indicated table in user_count_table_name. Any autorefresh cache group containing the specified table is not refreshed. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40133

The user count in the user
count table table_name for
table table_name in cache
group
owner.cache_group_name is
NULL. The cache group may not
be refreshed.

An autorefresh validation check found user count to be NULL in the in the user_count_table_name for the specified cache group table. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40134

The user count for table
table_name in cache group
owner.cache_group_name is
less than 0.

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40135

The user count for table
table_name in cache group
owner .cache_group_name
is equal to 0.

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40136

The log sequence number in
the user count table
table_name for table
table_name in cache group
owner.cache_group_name is
NULL. The cache group may not
be refreshed.

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40137

The log sequence number in
the user count table
table_name for table
table_name in cache group
cache_group_name is not
equal to the largest logseq
in the autorefresh log table
table_name. The cache group
may not be refreshed for all
datastores.

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40138

The previous log sequence
number is greater than the
recorded refresh bookmark for
table table_name in cache
group cache_group_name in
data store
owner.data_store_name

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40139

The user count table
table_name on Oracle
instance instance_name was
not found. The autorefresh
will not work for all
datastore for this instance.

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40140

The sequence number for
table table_name had
changed but the table was not
refreshed. cache_group_name
cache group in data store
data_store_name is out of
sync.

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40141

The sequence number for
table owner.table_name
had changed but the table was
not refreshed. The cache
group in data store
data_store_name is out of
sync.

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40143

Could not find table
table_name for cache group
cache_group_name in Oracle.
User user_name may not have
privileges. The cache group
will not be refreshed.

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40144

Table owner.table_name
in cache group
owner.cache_group_name is
not valid on Oracle. The
cache group will not be
refreshed.

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40145

An internal autorefresh
structure has not been
initialized.  Cache group
cache_group_name in data
store data_store_name will
not be refreshed.

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40146

An internal autorefresh
structure has not been
initialized.

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40147

The id for cache group
cache_group_name in data
store data_store_name is
invalid.

A problem occurred while trying to validate an autorefresh Oracle database object. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40148

Could not generate hash of
host and data store name

Internal error. A bi-propagated cache group operation failed to generate a hash of host and database name. Contact TimesTen Customer Support.

40149

Was not able to initialize
an internal autorefresh
structure.  The refresher
will try to reinitialize the
structure later.

The cache agent failed to initialize an internal data structure used by autorefresh. This message usually follows another message that describes the details about the failure. TimesTen is retrying the initialization.

40157

OCIHandleFree() failed.

Check the health of the Oracle database connection.

40158

() failed. uid user_ID.

Internal error. The cache agent failed to set the user ID of the session. Contact TimesTen Customer Support.

40159

Could not initialize OCI
function pointers.  Error:
message

This is a cache agent initialization error. The OCI functions cannot be set up to be used with the cache agent. The specific error is included in the message and may provide a suggestion to solve the problem. Check both the Oracle database and TimesTen installations. On UNIX systems, ensure that the ORACLE_HOME environment variable is set correctly.

40160

Clean up of autorefresh
Oracle objects failed.
snprintf returned value
with buffer length length.

This is an internal error that occurred during clean up of autorefresh Oracle database objects. Contact TimesTen Customer Support.

40162

ODBC call failed with
SQL_INVALID_HANDLE

This is an internal error indicating that an ODBC handle used by the cache agent is invalid. Contact TimesTen Customer Support.

40163

OCI call failed with
OCI_INVALID_HANDLE

This is an internal error indicating that an ODBC handle used by the cache agent is invalid. Contact TimesTen Customer Support.

40164

OCIErrorGet failed with
OCI_INVALID_HANDLE

This is an internal error. The OCIErrorGet call failed to get more diagnostic information after an OCI call failed. The OCI handle is invalid. Contact TimesTen Customer Support.

40165

Unique Constraint is
violated while loading table
owner.table_name

Type of Message: Error

Cause: The unique constraint has been violated in TimesTen during a LOAD CACHE GROUP, MERGE or AUTOREFRESH operation on the indicated table.

Impact: The update to the TimesTen database may fail.

User Action: Unload the cache group and then reload it. For more information, see "Unloading a cache group" in the Oracle TimesTen Application-Tier Database Cache User's Guide. If the error still occurs, contact TimesTen Customer Support.

40166

Required table table_name
does not exist on Oracle

Autorefresh Oracle database object validation detected that the indicated table does not exist. The log table garbage collector cannot work. To recreate the tables, recreate the autorefresh cache group. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40167

owner.table_name table on
Oracle does not have required
lock rows

Autorefresh Oracle database object validation detected that the indicated table does not exist. The log table garbage collector cannot work. To recreate the rows, recreate the autorefresh cache group. For details on fixing this problem, refer to the "Validate autorefresh for the Oracle database objects" section in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

40169

Can't initialize bookmark
reporter

The Cache agent failed to initialize a new data structure used by the bookmark reporter. This may happen in response to a CREATE CACHE GROUP or ALTER CACHE GROUP statement due to a lack of memory or other system resource. The operation cannot continue successfully. Free up the necessary resources and reissue the DDL statement.

40173

Can't initialize log table
marker

The Cache agent failed to initialize a new data structure used by the log table marker. This may happen in response to a CREATE CACHE GROUP or ALTER CACHE GROUP statement due a lack of memory or other system resource. The operation cannot continue successfully. Free up the necessary resources and reissue the DDL statement.

40175

Failover stopped. Failover
will not take place.

The cache agent detected an Oracle database OCI_FO_ABORT failover event. The failover was unsuccessful. If the cache agent does not restart automatically, restart it manually.

40176

Bad Failover Event: event.

Internal error. The cache agent does not recognize the Oracle database failover event. Contact TimesTen Customer Support.

40177

Could not re-establish a
connection in num minutes.
Failover will not take place

The connection to one of the Oracle RAC nodes failed and the cache agent could not failover to another Oracle RAC node. It timed out and the failover was unable to continue. If the cache agent does not restart automatically, restart it manually.

40178

Failed to register failover
callback for server handle
handle.

The cache agent failed to register the Oracle RAC failover callback function. No action is needed if the application is not running against an Oracle RAC server. If you are running against an Oracle RAC server, verify that the OCI client is the latest 9i or 10g client and that TAF is enabled.

40179

OCIHandleAlloc() failed.

The cache agent may have run out of memory or another system resource. Contact TimesTen Customer Support if the problem persists.

40180

Unexpected row count.
Expecting count. Got count.

Oracle database objects required for autorefresh operations could not be uninstalled because a DDL lock could not be acquired. Restart the cache agent. If the error persists, contact TimesTen Customer Support.

40181

object could not be found on
Oracle. Check that user has
privileges on Oracle_object

The Oracle database object could not be found.Verify that the specified Oracle database user has the correct privileges on the object.

40182

Timestamp descriptor alloc
failure

The call to OCIDescriptorAlloc failed.

40183

Could not retrieve aging
lifetime for cache group with
cgID ID

Internal error. The cache agent could not retrieve the aging lifetime for cache group from the TimesTen database. This message usually follows another message that describes the details about the failure. Load/refresh cache group fails.

40185

Can't initialize marker
structure for autorefresh
thread

The cache agent failed to initialize a new data structure used by the log table marker for the autorefresh thread.

40186

Can't initialize tablespace
full alert writer structure

The cache agent failed to initialize a new data structure used by tablespace full alert writer.

40187

Can't initialize tablespace
full alerter  structure

The cache agent failed to initialize a new data structure used by tablespace full alerter.

40188

No cache groups will be
autorefreshed since the data
store is marked "not alive"
and the recovery method is
"none."

The database is dead and cannot be refreshed.

40189

Failure_msg_Optional_msg
Cache Agent for datastore
datastore will be restarted.

Type of Message: Error

Cause: Failure_msg is a message that details the type of failure and where the failure occurred. Optional_msg is an optional error message that further describes the problem.

Impact: TimesTen attempts to restart the Cache Agent for the database.

User Action: None.

40190

Failure_msg_Optional_msg
Cache Agent for datastore
datastore cannot be started.

Type of Message: Error

Cause: Failure_msg is a message that details the type of failure and where the failure occurred. Optional_msg is an optional error message that further describes the problem.

Impact: The cache agent for the database cannot be started.

User Action: Fix the problem described by failure_msg and optional_msg before the cache agent for the database can be started.

40191

Can't retrieve log space
statistics from the
user_count table

Type of Message: Error

Cause: The schema of the TT_version_USER_COUNT table is incorrect.

Impact: The cache agent cannot retrieve log space monitoring statistics.

User Action: Contact TimesTen Customer Support.

40192

Could not find entry for
table cached_table
(obj_id_of_cached_table) in
TT_xx_LOG_SPACE_STATS. Log
space monitoring will not be
performed.

Type of Message: Error

Cause: The cache agent cannot find any information about the specified cached table in the TT_xx_LOG_SPACE_STATS table.

Impact: The cache agent cannot perform log Space monitoring for objects related to the specified cached table.

User Action: Contact TimesTen Customer Support.

40193

The log space stats table
TT_xx_LOG_SPACE_STATS on
Oracle database instance
oracle_instance was not
found. Log space monitoring
will not be performed.

Type of Message: Error

Cause: The cache agent cannot find the TT_xx_LOG_SPACE_STATS table in the Oracle database.

Impact: The cache agent cannot perform log Space monitoring.

User Action: Contact TimesTen Customer Support.

44000

Warning: Statement statement

The TimesTen ODBC driver returns the SQL warning included in the message.

44001

Warning: warning_message,
ODBC SQL state = state,
Additional Warning =
warning_message

The TimesTen ODBC driver returns the SQL warning included in the message.

44002

Table loading warning
summary: number_of data
truncations

This message reports the number of data truncations that occurred during a LOAD CACHE GROUP statement.

44003

Table loading warning: Data
truncated for table
table_name, row row_num,
column column_num

Warning: A data truncation occurred at the specified row and column while loading the specified table.

44004

OCIDescriptorFree : RowId
descriptor was not freed.
i=row, error=code

Internal warning, the OCIDescriptorFree call did not succeed for specified row with the OCI error code that is included in this message.

44005

Table loading warning
summary: number_of column
values truncated

The specified number of column values were truncated during a LOAD CACHE GROUP statement.

44007

Table refresh warning: Data
truncated for table
table_name, row row_num,
column column_num

The specified number of data truncations occurred for the specified table, row and column.

44009

Warning: Oracle object
cleanup failed.

The cache agent may not have cleaned up all the Oracle database objects. If necessary, clean up the objects manually.

44010

Warning: cmd: command

The cache agent encountered an OCI warning while processing the specified command.

44011

Oracle warning i =
warning_no: error_message

The cache agent encountered one or more warning(s) while executing an OCI call. The details are included in this message.

44017

Newly updated records are
missing from log table
table_name because of
truncation. Table
owner.table_name will be
fully refreshed

The specified table must be fully refreshed because log table was truncated. For details on fixing this problem, see "Incremental autorefresh becomes full autorefresh" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

44022

The cache agent has not been
able to established a
connection to Oracle. No
cache groups will be
refreshed until a connection
is made. Check the status of
the Oracle instance.

The cache agent encountered this error after either a CREATE CACHE GROUP or ALTER CACHE GROUP statement because the operation came too soon after the cache agent started or the cache agent could not establish a connection to the Oracle database. Other error messages in the user error log may provide details on connection failures. Resolve the connection problem manually if does not resolve after several retries, and restart the cache agent. Refer to the "Unable to resolve Oracle Service Name" and "Unable to validate the Oracle database username and password" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

44023

Cache agent was successfully
able to connect to Oracle
after num_attempts
failed attempts

The cache agent was initially having trouble connecting to the Oracle database but it succeeded after the indicated number of retries.

44024

Could not find the object id
for table
owner.table_name in the
autorefresh structure. The
cache agent may be lagging
behind.

This is a warning message.

44025

Could not find the cache
group owner.
cache_group_name in data
store data_store_name. The
cache agent maybe lagging
behind. The cache group will
not be validated.

This is a warning message.

44026

The autorefresh mode for
cache group owner.
cache_group_name in data
store data_store_name is
different from refresher. The
cache agent is lagging
behind.

This is a warning message.

44027

The autorefresh state for
cache group owner.
cache_group_name in data
store data_store_name is
different from refresher. The
cache agent is lagging
behind.

This is a warning message.

44028

Cache group
cache_group_name in data
store data_store_name has
number tables yet the
refresher has number tables.

Internal error. Contact TimesTen Customer Support.

44029

Cache group
cache_group_name in data
store data_store_name has
table table_name yet the
refresher has table table_name

Internal error. Contact TimesTen Customer Support.

44030

Autorefresh log table
table_name is empty. The
autorefresher will perform a
full refresh on all
datastores in order to
recovery.

For details on fixing this problem, see "Incremental autorefresh becomes full autorefresh" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

44031

The log sequence number has
changed but the table
table_name in cache group
owner.cache_group_name
was not refreshed. Will check
if it is refreshed during the
next validation cycle.

For details on fixing this problem, see "Incremental autorefresh becomes full autorefresh" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

44032

The current log sequence
number is greater than the
recorded bookmark for the
table table_name in cache
group owner.
cache_group_name in data
store data_store_name. The
table should have been
refreshed but was not. Will
check if it is refreshed
during the next validation
cycle.

For details on fixing this problem, see "Incremental autorefresh becomes full autorefresh" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

44033

The cache agent for data
store data_store_name shows
that the cache group
owner.cache_group_name is
an incremental autorefresh
cache group yet the system
table shows that it is not.
The cache agent may be
lagging behind.

This error could occur after the mode was altered from INCREMENTAL to FULL. Contact TimesTen Customer Support if the problem does not fix itself by the next validation cycle.

44034

The cache agent indicates
that cache group
cache_group_name is active,
incrementally refreshed and
has interval msecs ms for
data store data_store_name.
But the TimesTen system
tables indicate that the
cache group should not be
incrementally refreshed in
this interval. The cache
agent may be lagging behind.

This error could occur after an ALTER CACHE GROUP operation.Contact TimesTen Customer Support if the problem does not fix itself by the next validation cycle.

44035

The TimesTen system tables
indicates that cache group
owner.cache_group_name is
active, incrementally
refreshed and has interval
msecs ms for data store
data_store_name. But the
cache agent is not currently
incrementally refreshing it
in this interval. The cache
agent may be lagging behind.

This error could occur after an ALTER CACHE GROUP operation.Contact TimesTen Customer Support if the problem does not fix itself by the next validation cycle.

44036

The log table table_name
has been truncated and will
result in a full refresh of
the table table_name in
data store data_store_name.

For details on fixing this problem, see "Incremental autorefresh becomes full autorefresh" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

44037

The table table_name on
data store data_store_name
is currently out of sync with
Oracle. The bookmark for the
table is bookmark_name. If
this warning appears again
with the same bookmark, then
the cache agent is not making
any progress refreshing this
table. Otherwise if the
warning does not appear again
with the same bookmark, the
cache agent was only
temporarily behind.

For details on fixing this problem, see "Incremental autorefresh becomes full autorefresh" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

44038

The last recorded log
sequence number is larger
than the current log sequence
number for table table_name
for cache group
owner.cache_group_name.
Updates might get lost.

Internal error. Contact TimesTen Customer Support.

44040

The log table marker is not
making progress for tables in
refresh interval msecs ms
in data store
data_store_name. New
records are being
autorefreshed but bookmark is
not moving ahead, causing
duplicate work

Internal error. Contact TimesTen Customer Support.

44041

Autorefresh was not able to
acquire lock on one of the
cache groups, may be because
a DDL transaction is open on
the cache group. Autorefresh
will be retried number
times without waiting for
next autorefresh interval

Ensure that there are no open DDL transactions on the cache group.

44042

Two-safe transaction was
committed locally because the
commit on the remote node did
not complete within timeout
interval of timeout_interval
seconds.

The cache agent forced a commit of a TWOSAFE transaction because it did not receive an acknowledgment. This causes replication subscribers to be behind.

44043

Entry for object id
object_name exists in "TTC_
FT_OBJECT_PREFIX"agent_status
but missing from "TTC_FT_
OBJECT_PREFIX"user_count
table

For details on fixing this problem, see "Validate autorefresh for the Oracle database objects" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

44044

Last autorefresh for
interval msecs ms has not
finished after msecs ms

An autorefresh transaction is taking significantly longer than the specified autorefresh interval. The first parameter of this message indicates the specified autorefresh interval. The second parameter indicates how long the transaction has been in progress. For details on fixing this problem, see "Incremental autorefresh not progressing" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

44045

pthread_cond_timedwait
failed with return value
return_value

Internal error. An operating system call failed.

44046

Failover error. Retrying...

Type of Message: Error

Cause: A TimesTen operation meant to handle Oracle database failover was unsuccessful.

Impact: The cache agent is retrying the operation.

User Action: None.

44047

Operation is aborted because
cache agent is shutting down

Warning. The cache agent is shutting down.

44048

OCIDescriptorFree failed

Internal warning. The OCIDescriptorFree call did not succeed.

44049

Could not get LockTruncator
lock because the SYNC_OBJS
table or LockTruncator row
does not exist. Will try
again after 1 minute

For details on fixing this problem, see "Validate autorefresh for the Oracle database objects" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

44051

Binding the database column
with the output C type +
precision can result in
overflow errors or truncation
warnings.

Internal error.

44053

OCI function pointers
initialization warning:
warning. No action needed.

This warning can occur during cache agent initialization when a function was not found in the client library. No action is needed as the system will not use that function. Check that the OCI client library version is 11.1 or later.

47000

TimesTen cache agent Version
version, time_of_build
date_of_build

This message indicates the version of the cache agent. The version is of the format major.minor.patch.buildtime.builddate.

47001

Watching for main daemon
termination

Informational message. The agent thread that detects TimesTen daemon shutdown event is up running.

47002

Registered with daemon: Port
port_no, id ID

Informational message. The cache agent has registered itself with daemon.

47003

Starting up cache agent for
data store data_store_name

Informational message. The cache agent is reporting the database name that it is managing.

47006

Received request request

Informational message. The cache agent received a request. The request format is internal.

47007

Replied OK

Informational message. The cache agent replied to a request by sending an OK message.

47008

Replied Missing type

Informational message. The cache agent received a request but the message type was not specified.

47009

The request was denied
because it was not sent by an
authorized process

Informational message. The cache agent rejected a request because the request was not sent by an authorized process.

47010

Refreshed cache group:
cache_group_name

Informational message. A manual refresh statement has been done through the Cache agent on the indicated cache group.

47011

Loaded cache group:
cache_group_name

Informational message. A manual load statement has been done through the cache agent on the indicated cache group.

47012

Stopped autorefresh for
cache group: cache_group_name

Informational message. The stop autorefresh request for the specified cache group has been received and queued.

47013

Bad request

Informational message. The requested message cannot be handled by the cache agent.

47015

pthread_key_create executed:
key

Informational message. The cache agent thread is starting.

47016

Logging off of Oracle

Informational message. Logging off from the Oracle database.

47017

Disconnected from Oracle

Informational message. Disconnected from the Oracle database.

47018

name interval_valueL:
Trying to free orphan cache
group cache_group_name

Cache groups that no longer belong to any autorefresh intervals are orphan cache groups. Cache agent is cleaning up the specified orphan cache group from its internal data structure.

47029

refresher started for
interval interval_value
milliseconds

Informational message. The autorefresh handler thread for the specified interval has started.

47030

refresher for interval
msecs milliseconds is about
to exit

Informational message. The autorefresh handler thread for the specified interval is about to exit.

47037

Disabled autorefresh for
cache group: cache_group_name

Informational message. The scheduler has disabled autorefresh for the specified cache group.

47038

Enabled autorefresh for
cache group: cache_group_name

Informational message. The scheduler has enabled autorefresh for the specified cache group.

47043

OracleNetServiceName not
specified. Will not be able
to perform autorefreshes.

Informational message. The OracleNetServiceName attribute is not specified on the DSN. The cache agent cannot perform any autorefresh tasks.

47044

Logging into Oracle

Informational message. Cache agent is logging into the Oracle database.

47045

Connected to Oracle

Informational message. The cache agent has connected to the Oracle database.

47046

Already connected for
caching for
data_store_name

Informational message. The cache agent is using an existing connection to the Oracle database to operate on database.

47047

Free error handle handle_name

Informational message. The cache agent is freeing an OCI error handle used when setting up a connection to the Oracle database.

47048

Processing Oracle SQL:
statement.

Informational message. This message follows an error message. It indicates the error occurred while the cache agent was processing the specified Oracle database SQL statement.

47049

Performing a full refresh
with cache group root table:
owner.table

Informational message. The cache agent is performing a full refresh on the specified table.

47050

Performing a full refresh

Informational message. The cache agent is performing a full refresh.

47051

restarting autorefresh for
cache group: cache_group_name

Informational message. The cache agent is restarting the autorefresh for the specified cache group. This happens during cache agent startup.

47052

re-started autorefresh for
cache_group_name cache groups

Informational message. The cache agent is restarting the autorefresh for the specified cache groups. This happens during cache agent startup.

47053

Error executing the
following Oracle SQL
statement: statement

Informational message. The Oracle database returned an error while executing the specified SQL statement. This may not be an error condition for the cache agent.

47054

TimesTen transaction
committed.

Informational message. A TimesTen transaction has been committed.

47055

Autorefresh rolled back.

Informational message. An autorefresh operation has been rolled back.

47056

Incremental autorefresh
started for table:
owner.table_name
soLog(first_refresh_row),
eoLog(last_refresh_row).

Informational message. The cache agent is performing an incremental autorefresh on the specified table.

47057

Oracle object busy. Will
retry: msecs

Informational message. The Oracle database object is being used by other user. The operation is retried in the indicate number of milliseconds.

47058

Executing Oracle statement:
statement

Informational message. The indicated statement is being executed on the Oracle database.

47059

Successfully executed Oracle
SQL statement: statement

Informational message. The Oracle database SQL statement has been successfully executed.

47060

Performing a full refresh on
subtree with root:
owner.table

Informational message. The cache agent is performing a full refresh on a subtree of cache group with the specified root table.

47061

Error preparing the
following Oracle SQL
statement: statement

The cache agent encountered an error while preparing the specified SQL statement on the Oracle database.

47062

Rowid was 0 for
cascadeUpDelete on table:
table

This is an internal message indicating the intermediate steps of autorefresh.

47063

Executing Delete statement:
statement

The cache agent executed the specified DELETE statement.

47064

Starting cleanup of the
Oracle objects

Informational message. The cache agent has begun cleaning up Oracle database objects that were used by autorefresh.

47065

Successfully executed Oracle
SQL statement: statement

Informational message. The cache agent has successfully executed the indicated Oracle database SQL statement.

47066

Cleanup of the Oracle
objects completed

Informational message. The cache agent has finished cleaning up Oracle database objects that were used by autorefresh.

47067

Lost connection to Oracle --
shutting down the cache
agent, cmd: command

Type of Message: Informational

Cause: The Oracle database connection was lost while executing the indicated command.

Impact: The cache agent is shutting down and restarting.

User Action: If the cache agent does not start automatically, restart it manually. For more information, see "Starting the cache agent" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

47070

No new connection during
shutdown

Informational message. A request of a new TimesTen/Oracle database connection was denied because the cache agent is in the shutdown process. Wait for the cache agent to completely shutdown and then restart the agent and attempt the connection.

47071

Warning Ignored: message,
ODBC SQL state = SQL_state,
Additional Warning = code

Informational message. The cache agent has purposely ignored the TimesTen ODBC warning, the SQL state and the TimesTen warning code indicated in the message.

47072

Error Ignored: message,
ODBC SQL state =
SQL_state, Additional Error
= error_code

Informational message. The cache agent has purposely ignored the TimesTen ODBC error, the SQL state and the TimesTen error code indicated in the message.

47073

Cannot connect to Oracle
while the cache agent is
during shutdown

Informational message. The cache agent cannot connect to the Oracle database while the cache agent is shutting down.

47074

Cache agent is shutting down
all service threads

Informational message. The cache agent is shutting down all service threads.

47075

Cache agent is in final
shutdown stage

Informational message. The cache agent has shutdown all service threads and is in final shutdown mode.

47076

Cache agent has started all
service threads.

Informational message. The cache agent has started all service threads during startup.

47077

Cache agent for data store
data_store_name is shutting
down

Informational message. The cache agent is shutting down.

47078

Autorefresh number number
succeeded for interval
msecs milliseconds

Informational message. Autorefresh for interval msecs succeeded.

47084

ftSchedulerGetRefreshStats:
cannot find cache group with
cgID ID

Internal Error. TimesTen cannot find the indicated cache group.

47085

AUTOREFRESH advances to new
LOG SEQ Log Seq(num) =
table in cache group
cache_group_name

The autorefresh bookmark for indicated table has been advanced to the indicated log sequence. This indicates the autorefresh has brought in some new changes to TimesTen.

47086

Retry timeout is mins
minutes.

The cache agent is waiting for an Oracle database object to come active. The cache agent retries the operation in the indicated number of minutes.

47087

Cache agent refreshed cache
group owner:cache_group_name

Informational message. The cache agent refreshed the root table rows in the specified cache group.

47088

Cache agent refreshed
number root table rows for
this interval

Cache agent refreshed the indicated number of root table rows for this interval.

47090

DDL on base table after
creating trigger - DDL has
been executed on table
owner.table_name after
the cache group
cache_group_name in data
store data_store_name was
created. The cache group may
not be refreshed or may be
out of sync.

The cache agent has noticed that the Oracle database table has been altered after an autorefresh cache group has been defined on it. As a result, the cache group may not refresh correctly.

47092

Cache group
cache_group_name in data
store data_store_name does
not have autorefresh mode set
to incremental. No validation
is required.

Informational message. Autorefresh is not set for the specific cache group.

47093

Validation starting:
Starting validation check for
cache group
cache_group_name in data
store data_store_name.

Informational message. The cache agent is validating the Oracle database objects for tracking changes for the indicated cache group.

47094

status Anomalies were found in
the objects used to
autorefresh the cache group
cache_group_name in data
store data_store_name.

Informational message. The cache agent has found anomalies in autorefresh tracking objects for the indicated cache group.

47095

status Anomalies were found
in the objects used to
autorefresh cache groups in
refresh interval msecs for
data store data_store_name.

Informational message. The cache agent has found anomalies in autorefresh tracking objects for the cache groups with the specified refresh interval.

47096

status No anomalies were
found in the objects used to
autorefresh the cache group
cache_group_name in data
store data_store_name.

Informational message. Autorefresh validation has successfully completed.

47097

Validation aborted: A fatal
error occurred while
validating cache groups in
refresh interval msecs for
data store data_store_name.

Informational message. The cache agent encountered an error while validating the autorefresh objects for the specified interval.

47098

Number of bipropagate rows
deleted: number_of_rows

Informational message. The cache agent is tracking an operation on cache groups using both the autorefresh and propagate feature.

47100

The cache agent will wait at
least min minutes before
validating cache groups.

Informational message. The cache agent is waiting for at least the specified number of minutes before validating the autorefresh objects.

47107

Autorefresh thread is
skipping marking the logs
because it was not able to
get the locks. Autorefresh
will be performed but
performance may degrade.
Failed SQL: statement

The autorefresher was not able to get the necessary locks to mark the log tables. Another autorefresher may be marking the logs. The autorefresher is skipping this step and move on to performing the autorefresh. The negative side effect of this is that the autorefresher may perform some inserts twice.

47108

Autorefresh state for this
cache group
cache_group_name is no
longer ON. Autorefresh will
be retried after refreshing
the new state

Informational message. The current autorefresh state for this cache group is not ON.

47109

Autorefresh mode for this
cache group
cache_group_name is no
longer incremetal.
Autorefresh will be retried
after refreshing the new mode

Informational message. The autorefresh mode has changed for this cache group.

47110

object_id object, bookmark
bookmark_name

Informational message. The autorefresh bookmark for the specified table.

47111

Cache agent successful in
getting oneTruncator lock for
garbage collection

Informational message. The cache agent has locked the oneTruncator autorefresh object successfully.

47112

Garbage collector deleted
num rows from
TTC_FT_OBJECT_PREFIXobject_L
where logseq < log_sequence
(Min logseq was
min_log_sequence)

Informational message. The garbage collector deleted said number of rows.

47113

Log Table Marker marked
number rows of log table
"TTC_FT_OBJECT_PREFIX"object_L
with logseq next_log_sequence
through last_log_sequence

Informational message. The progress of log marking for autorefresh.

47116

Detect Environment Variable:
variable_name, Value: value

Informational message. The cache agent obtained a value from the indicated environment variable.

47117

Autorefresh thread for
interval msecs ms is
connected to instance
instance_name on host
host_name. Server handle handle

Informational message. The cache agent thread for autorefresh of cache groups with the specified autorefresh interval has connected to the Oracle database.

47118

Starting autorefresh number
number for interval msecs ms

Informational message. The cache agent is starting an autorefresh with the specified autorefresh interval.

47119

Autorefresh number number
finished for interval msecsms
status

Informational message. Autorefresh has completed.

47120

Failing over connection.
Failover type is type.

Informational message. The cache agent is starting an Oracle RAC failover of the indicated type, where type is one of: SESSION, SELECT or unknown.

47121

Failover completed.

Informational message. The failover has completed.

47122

Failover callback function
called.

Informational message. The cache agent's registered Oracle RAC failover callback function has been called.

47123

Failover callback function
registered for server handle
handle_name.

Informational message. The cache agent has registered an Oracle RAC callback function for failover

47125

Autorefresh thread for
interval msecsms is connected
to instance id ID. Server
handle handle_name

Informational message. The autorefresh thread for cache groups with the specified autorefresh interval has connected to the Oracle database.

47126

Failover stopped. Cache
agent shutting down.

Informational message. The cache agent cannot do an Oracle RAC failover since the cache agent is already in shutdown mode.

47127

Autorefresh marker thread
exiting.

Informational message. The autorefresh marker thread is exiting.

47128

Autorefresh garbage
collector thread exiting.

Informational message. The autorefresh garbage collector thread is exiting.

47129

Autorefresh mode for this
cache group
cache_group_name is no
longer full. Autorefresh will
be retried after refreshing
the new mode

Informational message. Autorefresh mode has changed for this cache group.

47130

Full autorefresh will be
performed on the table
owner.table_name because
an initial load was not
performed

Informational message. The application did not load the cache group after it was created. As a result, the first autorefresh is a full refresh.

47131

Lock info object:lock

Informational message. This is an internal message tracking locks on cache agent synchronization objects.

47132

Skipped reporting bookmark
for object_id object

Informational message. The cache agent skipped a reporting bookmark for the table with the specified object ID.

47133

Error freeing odbc handle

Informational message. The cache agent encountered an error when it tried to free a TimesTen ODBC handle.

47135

Thread thread_name
encountered an invalid value
for argument argument while
adding a cache group to the
cache agent scheduler. Cache
group cache_group_name will
not be autorefreshed.

One of the arguments passed to a routine to add a cache group to the scheduler did not pass a validity check. The cache group is not added to the scheduler and therefore is not autorefreshed.

47136

The cache agent hasn't fully
initialized yet. The cache
group cache_group_name will
be refreshed after
initialization is complete.

Type of Message: Informational

Cause: A CREATE or ALTER CACHE GROUP statement was issued before the cache agent had a chance to initialize.

Impact: The CREATE or ALTER operation takes effect after the initialization completes.

User Action: None.

47137

Handle invalid due to client
failover.

Re-initiate the handle. An automatic failover has occurred.

47138

DDL Lock: status lock_info

This is an information message. A DDL lock has been created.

47139

DDL Lock: status lock_info

This is a warning message. A DDL lock may interfere with operations.

47140

The cache agent information
message: Cache group pointer
pointer; name name; state
state_number; newxpointer
pointer

There is an internal cache group INFO message in the daemon log.

47141

Refresher thread with id
ID_number and interval
interval_amount ms with
bejoined.

There is an internal cache group INFO message in the daemon log.

47142

type interval:  number
ms, isDead: number, first
cg: name

There is an internal cache group INFO message in the daemon log.

47143

name threadId: number
isDead: number, first cg:
name

There is an internal cache group INFO message in the daemon log.

47150

Heartbeat thread
initialization failed.

Cache agent heartbeat thread allocation failed.

47151

Heartbeat thread started.
Freq: number seconds.

Informational message that the heartbeat thread has started.

47152

Heartbeat thread has exited.

Informational message that the heartbeat thread has exited.

47153

DeadDsMonitor thread
initialization failed.

Cache Agent dead database monitor thread allocation failed.

47154

Dead database monitor thread
started. Freq: number
seconds.

Informational message that the dead database monitor thread has started.

47155

Dead database monitor thread
has exited.

Informational message that the dead database message has exited.

47156

message: information

Informational generic dead database message.

47157

No cache groups will be
autorefreshed since recovery
method is manual.
Deadcount=value,
NumActiveCgs=value

You must manually refresh the indicated cache groups.

47158

Cache groups will undergo
manual recovery.
Deadcount=value,
NumActiveCgs=value

You must manually recover the indicated cache groups.

47159

LogTblMarker thread
initalization failed.

Cache agent dead database monitor thread allocation failed.

47160

LogTblGc thread
initialization failed.

There is an internal cache group INFO message in the daemon log.

47161

Tablespace full alerter
started for with polling
period number seconds.

Informational message. The thread to monitor the Oracle database tablespace has started.

47162

Tablespace full alerter
exited

Near tablespace full alerter exited message.

47163

percent of the tablespace has
been used. This exceeds
your threshold value of value.

Tablespace used above threshold.

47164

percent of the tablespace
has been used.  This exceeds
your threshold value of
number.

Tablespace used above threshold.

47165

The tablespace full alerter
requires privileges
privileges. Alerter is
shutting down.

Alerter lacks appropriate Oracle database privileges.

47166

Log Table Marker marked
number rows of log table.
"TTC_FT_OBJECT_PREFIX"name_L
with logseq
start_log_sequence
through end_log_sequence

This is an informational message indicating the progress of the autorefresh log marker.

47167

Tablespace full alert writer
started for with polling
period number seconds

Near tablespace full alerter writer started message.

47168

Tablespace full alert writer
exited

Near tablespace full alerter writer exited message.

47169

The tablespace full alert
writer requires name
privileges. Will shut down
the alerter.

Alerter writer lacks appropriate Oracle database privileges.

47170

Could not determine the size
of the Oracle tablespace.

Alerter writer could not determine the size o the Oracle database tablespace.

47171

Tablespace full alert writer
updated cache statistics
table. Tablespace used
percentage percent

This is an informational message from the progress thread monitoring the Oracle database tablespace. The message indicates how much tablespace is in use.

47172

Heartbeat updated.

Informational daemon message.

47173

Bad Oracle agent tuning
parameter read by name
thread. P1=value,
P2=value, P3=value

Informational daemon message.

47174

Autorefresh of cache group
group, failed number
time(s) due to lock
conflicts.

For this dynamic cache group, autorefresh was unable to complete due to lock conflicts with another application. Indicates the number of times failed due to lock conflicts.

47175

Autorefresh of cache group
cachegroup has escalated
locks, after number roll
backs.

For this dynamic cache group, a threshold count of autorefresh lock conflict failures was reached. Autorefresh will now escalate its locks and priority to improve its chances of completion.

47176

Autorefresh Garbage Collector
chunk size is chunk_size.

Type of Message: Informational

Cause: The cache agent is starting scheduled garbage collection of autorefresh change log records.

Impact: Log records representing rows that have been applied from the Oracle database to the TimesTen database are being removed from the change log tables. For more information on log tables, see "Managing a caching environment with Oracle Database objects" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

User Action: None.

47177

LogSpaceMon thread started.
threshold : thresold_time
seconds action :
action_setting.

Type of Message: Informational

Cause: The monitoring and management thread for the autorefresh log space started with the specified threshold value and action setting.

Impact: None.

User Action: None.

47178

LogSpaceMon thread has
exited.

Type of Message: Informational

Cause: The monitoring and management thread for the autorefresh log space exited.

Impact: None.

User Action: None.

47179

logSpaceMon thread
initialization failed.

Type of Message: Error

Cause: The monitoring and management thread for the autorefresh log space failed to start. Review the daemon log for any additional error messages to determine a cause for the error message. For more information on how to review the daemon log, see "Using the logs generated by the TimesTen daemon" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

Impact: Review the daemon log for any possible impacts.

User Action: Review the daemon log for any possible fixes.

47180

LogSpaceMon:
LogSpaceMon_status info

Type of Message: Informational

Cause: General informational message for the monitoring and management thread for the autorefresh log space.

Impact: None.

User Action: None.

47189

Cache group cachegroup
will not be autorefresh
because the cache group is
marked not alive and the
recovery method is manual.

Type of Message: Warning

Cause: The specified cache group has been marked dead because the cache agent has been down too long. You have configured the cache group in a way that requires a full manual refresh to recover the cache group.

Impact: The data in the autorefresh cache group is out of date.

User Action: Perform a full manual refresh on the specified cache group. For more information on how to perform a full manual refresh of a cache group, see "Loading and refreshing a cache group" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

47190

Autorefresh commit every n
operations feature is enabled
for autorefresh interval
interval_value ms and
autorefresh number
autorefresh_number.
Autorefresh will commit after
every num_operations
operations.

Type of Message: Informational

Cause: The ttCacheAutorefreshXactLimit built-in is enabled with the specified settings.

Impact: The autorefresh cycles will be performed as several small transactions instead of one large transaction.

User Action: None.

For more information on the ttCacheAutorefreshXactLimit built-in, see "ttCacheAutorefreshXactLimit" in the Oracle TimesTen In-Memory Database Reference.

47192

Autorefresh for interval
interval_value ms and number
autorefresh_number will apply
changes to Timesten using a
single transaction.

Type of Message: Informational

Cause: The ttCacheAutorefreshXactLimit built-in is not enabled.

Impact: The autorefresh cycles will be performed as single transactions.

User Action: None.

For more information on the ttCacheAutorefreshXactLimit built-in, see "ttCacheAutorefreshXactLimit" in the Oracle TimesTen In-Memory Database Reference.

47193

Could not find
static_or_dynamic
refresher with interval
interval_value ms.

Type of Message: Error

Cause: An internal structure that contains the autorefresh information for the specified interval was not found.

Impact: The operation failed.

User Action: If you receive this error message while using the ttCacheAutorefIntervalStatsGet built-in, retry the operation. If you receive this error message for any other reason, the autorefresh operation will be attempted later.

47194

Incremental autorefresh
encountered an error for
table: owner.table.
soLog(start_of_log),
eoLog(end_of_log).

Type of Message: Error

Cause: The incremental autorefresh operation encountered an error for the specified table. A detailed error message follows this message.

Impact: The incremental autorefresh operation cannot be performed and will be attempted again later. Review the error message for any additional impacts.

User Action: Review the error message for possible fixes.

47195

Incremental autorefresh ended
for table: owner.table.
soLog(start_of_log),
eoLog(end_of_log).

Type of Message: Informational

Cause: The incremental autorefresh operation for the specified table completed.

Impact: None.

User Action: None.

47196

Load table started for table:
table_name

Type of Message: Informational

Cause: The specified table is starting to load.

Impact: None.

User Action: None.

47197

Load table encountered an
error for table: table_name

Type of Message: Error

Cause: The load table operation encountered an error for the specified table. A detailed error message follows this message.

Impact: The load table operation cannot be performed. Review the error message for any additional impacts.

User Action: Review the error message for possible fixes.

47198

Load table ended for table:
table_name

Type of Message: Informational

Cause: The specified table finished loading.

Impact: None.

User Action: None.

47199

Subtree load started for root
table: owner.table

Type of Message: Informational

Cause: The subtree of the specified root table is starting to load.

Impact: None.

User Action: None.

47200

Subtree load encountered an
error for root table:
owner.table

Type of Message: Error

Cause: The subtree load operation encountered an error for the root table. A detailed error message follows this message.

Impact: The subtree load operation cannot be performed and will be attempted again later. Review the error message for any additional impacts.

User Action: Review the error message for possible fixes.

47201

Subtree load ended for root
table: owner.table_name

Type of Message: Informational

Cause: The subtree of the specified root table finished loading.

Impact: None.

User Action: None.

47202

Root load started for root
table: table_name

Type of Message: Informational

Cause: The specified root table is starting to load.

Impact: None.

User Action: None.

47203

Root load encountered an
error for root table:
table_name

Type of Message: Error

Cause: The load table operation encountered an error for the specified root table. A detailed error message follows this message.

Impact: The load table operation cannot be performed and will be attempted again later. Review the error message for any additional impacts.

User Action: Review the error message for possible fixes.

47204

Root load ended for root
table: table_name

Type of Message: Informational

Cause: The specified root table finished loading.

Impact: None.

User Action: None.

47205

Prepared oracle stmt:
oracle_stmt

Type of Message: Informational

Cause: The specified Oracle database statement has been prepared.

Impact: None.

User Action: None.

47206

Log Table Marker marked
marked_rows rows of log table
TT_version_object-ID_L with
logseq start_logseq through
end_logseq

Type of Message: Informational

Cause: The log table marker marked the specified amount of rows within the specified range from the specified log table.

Impact: None.

User Action: None.

47207

Log Table Marker marked
marked_rows rows of log table
TT_version_object-ID_L

Type of Message: Informational

Cause: The log table marker marked the specified amount of rows from the specified log table.

Impact: None.

User Action: None.

47210

AR STATS: autorefresh_stats

Type of Message: Informational

Cause: This is a diagnostic message that shows the autorefresh statistics.

Impact: None.

User Action: None.

47211

TAF callback re-establishing
session settings.

Type of Message: Informational

Cause: This is a progress message indicating that Transparent Application Failover (TAF) is executing during a Real Application Clusters (Oracle RAC) failover.

Impact: TAF callback is reestablishing session settings.

User Action: None.

47212

TAF callback re-establishing
nls settings.

Type of Message: Informational

Cause: This is a progress message indicating that Transparent Application Failover (TAF) is executing during a Real Application Clusters (Oracle RAC) failover.

Impact: TAF callback is reestablishing NLS settings.

User Action: None.

47213

Marked cache group with
id=cache_group_id
(ts=timestamp) for delete

Type of Message: Informational

Cause: The cache agent marked the specified cache group to be removed from the internal structure of the refresher.

Impact: The cache agent will not consider the specified cache group in subsequent autorefresh operations.

User Action: None.

47214

Dropped Oracle database
objects

Type of Message: Informational

Cause: The cache agent is dropping the cache group Oracle database metadata objects that are no longer needed.

Impact: The cache group metadata objects are no longer available on the Oracle database.

User Action: None.

47215

Removed cache group:
id=cache_group_id,
name=cache_group_name,
mode=autorefresh_mode,
state=autorefresh_state,
ts=timestamp,
interval=interval from list

Type of Message: Informational

Cause: The cache agent is deleting the specified cache group from the internal structure of the refresher.

Impact: The refresher thread for the specified interval will no longer manage the specified cache group.

User Action: None.

47216

Added cache group:
id=cache_group_id,
name=cache_group_name,
mode=autorefresh_mode,
state=autorefresh_state,
ts=timestamp,
interval=interval to list

Type of Message: Informational

Cause: The cache agent is adding the specified cache group to the internal structure of the refresher.

Impact: The refresher thread for the specified interval will start managing the specified cache group.

User Action: None.

48001

Could not obtain host list
from Oracle Clusterware found
in CRS_HOME

Type of Message: Error

Cause: The ttCWAdmin utility cannot retrieve the list of hosts used for the Oracle Clusterware cluster.

Impact: The ttCWAdmin utility failed.

User Action: Run the ttmodinstall -crs utility option to verify and change any values used to manage TimesTen hosts within an Oracle Clusterware cluster. For more information on using ttmodinstall -crs, see "Install TimesTen on each host" in the Oracle TimesTen In-Memory Database Replication Guide.

48002

CRS home was not found in the
ttcrsagent.options file.

Type of Message: Error

Cause: The Oracle Clusterware location is not specified in the ttcrsagent.options file.

Impact: The ttCWAdmin utility failed.

User Action: Run the ttmodinstall -crs utility option and verify that all the values are correct. For more information on using ttmodinstall -crs, see "Install TimesTen on each host" in the Oracle TimesTen In-Memory Database Replication Guide.

48003

Failed to load Oracle
Clusterware API library.

Type of Message: Error

Cause: A TimesTen Clusterware utility was unable to load the Clusterware API library from Oracle Clusterware.

Impact: The TimesTen Clusterware utility failed.

User Action: An operating system error may precede this message and may be found in the ttcwerrors.log file. Diagnose and troubleshoot the operating system error. Run the ttmodinstall -crs utility option and verify that all the values are correct. Also, ensure that the API libraries are located in the CRS_HOME/lib, directory.

For more information on the ttcwerrors.log file, see "Message log files" in the Oracle TimesTen In-Memory Database Replication Guide. For more information on using ttmodinstall -crs, see "Install TimesTen on each host" in the Oracle TimesTen In-Memory Database Replication Guide.

48004

Clusterware_function
failed with status =
CRS_error_number

Type of Message: Error

Cause: A call to an Oracle Clusterware API failed.

Impact: TimesTen cannot perform the operation.

User Action: Review the specified error message for possible fixes.

48005

One or more clusters are
active on the host
host_name

Type of Message: Error

Cause: You attempted to shut down one or more cluster agents that are currently active on the specified host.

Impact: TimesTen cannot run the ttCWAdmin -shutdown utility command

User Action: Perform the following steps:

- Identify the active cluster agents by executing the ttCWAdmin -status command.

- Drop the existing cluster agents by executing the ttCWAdmin -drop command.

For more information about the ttCWAdmin utility, see "ttCWAdmin" in the Oracle TimesTen In-Memory Database Reference.

48006

The cluster configuration
file attribute
attribute_name for DSN
dsn_name in the cluster
configuration file
file_name does not have an
assigned value.

Type of Message: Error

Cause: You did not assign a value to the specified cluster configuration file attribute in the cluster.ora.ini file.

Impact: TimesTen cannot run the ttCWAdmin -create utility command

User Action: Assign a value to the specified cluster configuration file attribute. Then, retry the operation. For more information, see "The cluster.oracle.ini.file" in the Oracle TimesTen In-Memory Database Replication Guide.

48007

Virtual IP resources do not
exist in the cluster for DSN
dsn_name.

Type of Message: Error

Cause: The TimesTen virtual IP resources do not exist in the Oracle Clusterware for the specified DSN.

Impact: TimesTen cannot run the ttCWAdmin -create utility command.

User Action: Use the ttCWAdmin -createVIPS utility command to create the TimesTen virtual IP resources. For more information about the ttCWAdmin utility, see "ttCWAdmin" in the Oracle TimesTen In-Memory Database Reference.

48008

A cluster for the DSN
dsn_name has already been
registered.

Type of Message: Error

Cause: You attempted to create a cluster that already exists for the specified DSN.

Impact: TimesTen cannot run the ttCWAdmin utility command.

User Action: If you want to create a new cluster with the specified name, perform the following steps:

- Drop the existing cluster using the ttCWAdmin -drop utility command.

- Then, create the new cluster using the ttCWAdmin -create utility command.

For more information about the ttCWAdmin utility, see "ttCWAdmin" in the Oracle TimesTen In-Memory Database Reference.

48009

Private hostname not found
for the host host_name.

Type of Message: Error

Cause: The private hostname for the indicated host name was not returned by Oracle Clusterware.

Impact: Oracle Clusterware cannot start.

User Action: Verify the cluster configuration by calling crsctl check cluster. If the host is not listed, follow the procedure in the Oracle Clusterware documentation. If the host is listed, contact TimesTen Customer Support.

48010

Connection to TimesTen
Cluster agent on host
host_name failed.

Type of Message: Error

Cause: The TCP connection to the TimesTen Cluster agent failed on the specified host.

Impact: Oracle Clusterware cannot start. If Oracle Clusterware is already running, the Oracle Clusterware services will failover to another host.

User Action: Check the ttcwerrors.log file on the indicated host for any errors occurring before this error. Diagnose and troubleshoot the errors. If no network error is detected, contact TimesTen Customer Support.

For more information on the ttcwerrors.log file, see "Message log files" in the Oracle TimesTen In-Memory Database Replication Guide.

48011

Could not successfully send
cluster configuration model
for DSN dsn_name to
TimesTen Cluster agent on
host host_name

Type of Message: Error

Cause: This error may occur as the result of an incorrect input to a ttCWAdmin utility command, an incorrect value in the TimesTen cluster configuration file, or due to network errors.

Impact: The cluster may not be fully started, or may exclude the specified host, or both.

User Action:

- Ensure that your input to the ttCWAdmin utility command is correct. For more information, see "ttCWAdmin" in the Oracle TimesTen In-Memory Database Reference.

- Check the TimesTen cluster configuration file for any errors. For more information, see "TimesTen Configuration Attributes for Oracle Clusterware" in the Oracle TimesTen In-Memory Database Replication Guide.

- Check the ttcwerrors.log file on the indicated host for errors that occurred before this error. Diagnose and troubleshoot the errors. If no network error is detected, contact TimesTen Customer Support.

For more information on the ttcwerrors.log file, see "Message log files" in the Oracle TimesTen In-Memory Database Replication Guide.

48012

Could not successfully
verify user ID and
password(s) for DSN
dsn_name on host host.

Type of Message: Error

Cause: You specified an invalid user ID or password for the TimesTen database.

Impact: TimesTen cannot run the ttCWAdmin -create utility command.

User Action: Ensure that the specified database exists. Also, ensure that you specify a correct user ID and password for the TimesTen database. If TimesTen Cache is enabled, verify the Oracle database password. For more information, see "UID and PWD" in the Oracle TimesTen In-Memory Database Reference.

48013

Failed to create active
standby pair replication
scheme for DSN dsn_name on
host host_name

Type of Message: Error

Cause: The active standby pair cannot be created.

Impact: Oracle Clusterware cannot start.

User Action: Check for errors in the ttcwerrors.log and the ttmesg.log files. Diagnose and fix the errors. Then run the ttCWAdmin utility command that failed. If the same replication scheme can be created manually without using the ttCWAdmin utility, contact TimesTen Customer Support. For more information on the message log files, see "Message log files" in the Oracle TimesTen In-Memory Database Replication Guide.

48014

Failed to register the
cluster for DSN dsn_name
with Oracle Clusterware.

Type of Message: Error

Cause: TimesTen cannot register the cluster for the specified DSN.

Impact: TimesTen cannot run the ttCWAdmin -create utility command.

User Action: Review the ttcwerrors.log and ttcwmsg.log error message log files for possible fixes. For more information on the message log files, see "Message log files" in the Oracle TimesTen In-Memory Database Replication Guide.

48015

Failed to register resource
resource_name with Oracle
Clusterware.

Check the ttcwmesg.log and ttcwerrors.log files for errors that occurred before this error.

Verify that Oracle Clusterware is running by running the command crsctl check crs.

Verify that attribute values specified in the TimesTen cluster configuration file are correct.

48016

TimesTen Cluster agent
received NULL Oracle password
for DSN dsn_name.

Type of Message: Error

Cause: You did not specify an Oracle database password when creating a cluster.

Impact: TimesTen cannot run the ttCWAdmin -create utility command.

User Action: Retry using the ttCWAdmin -create utility command and specify a valid Oracle database password. Then, retry the operation. For more information on the ttCWAdmin utility, see "ttCWAdmin" in the Oracle TimesTen In-Memory Database Reference.

48017

No -tns_admin option
specified in the
ttendaemon.options file.

Type of Message: Error

Cause: The ttendaemon.options file does not contain a valid tns_admin daemon option.

Impact: TimesTen cannot run the ttCWAdmin -create utility command to configure a cluster.

User Action: Use the ttmodinstall -tns_admin utility option to specify a valid tns_admin path. For more information on the ttmodinstall utility, see "ttmodinstall" in the Oracle TimesTen In-Memory Database Reference.

48018

Failed to register
direct-linked application
resources for DSN dsn_name
with Oracle Clusterware.

Type of Message: Error

Cause: The ttCWAdmin -create utility command cannot register direct-linked applications to be managed by the Oracle Clusterware.

Impact: The ttCWAdmin -create utility command cannot register applications to be managed by the Oracle Clusterware.

User Action: Verify that the application attributes are correct in the cluster.oracle.ini file for the specified DSN. Also, ensure that the application script is located in the script install directory of every host. Review the ttcwerrors.log and ttcwmsg.log error message log files for possible fixes.

For more information about the cluster.oracle.ini file, see "The cluster.oracle.ini file" in the Oracle TimesTen In-Memory Database Replication Guide.For more information on the message log files, see "Message log files" in the Oracle TimesTen In-Memory Database Replication Guide.

48019

Failed to restore DSN
dsn_name on the localhost.

Type of Message: Error

Cause: You attempted to restore the specified DSN.

Impact: TimesTen cannot execute the ttCWAdmin -restore utility command.

User Action: Review the ttcwerrors.log and ttcwmsg.log error message log files for possible fixes. For more information on the message log files, see "Message log files" in the Oracle TimesTen In-Memory Database Replication Guide.

48020

TimesTen cluster containing
DSN dsn_name not found.

There is no registered cluster containing the specified DSN.

If the cluster was created previously, creation may have failed. Drop the existing cluster by calling:

ttCWAdmin -drop -dsn dsn_name

Create a new closer by calling:

ttCWAdmin - create -dsn dsn_name

48021

Resource resource_name not
registered.

The specified resource is not registered with Oracle Clusterware.

If the cluster was created previously, creation may have failed. Drop the existing cluster by calling:

ttCWAdmin -drop -dsn dsn_name

Create a new cluster by calling:

ttCWAdmin - create -dsn dsn_name

48022

TimesTen cluster containing
DSN dsn_name is not
completely registered.

Check for resources that are not registered with Oracle Clusterware by reviewing error messages that appear in the ttcwerrors.log file before this error.

Drop the existing cluster by calling:

ttCWAdmin -drop -dsn dsn_name

Create a new cluster by calling:

ttCWAdmin - create -dsn dsn_name

48023

TimesTen cluster containing
DSN dsn_name is already
running.

Drop the existing cluster by calling: ttCWAdmin -drop -dsn dsn_name

48024

TimesTen cluster containing
DSN dsn_name failed to start.

Check the ttcwmesg.log and ttcwerrors.log files in the daemon home directory for errors that occurred before this error.

Also, check the crsd.log file in the CRS_HOME/log/hostname/crsd directory for errors that occurred before this error.

48025

The resource resource_name
is still online.

Stop the cluster containing the specified resource by calling:

ttCWAdmin -stop -dsn dsn_name

48026

The cluster containing DSN
dsn_name failed to stop.

Type of Message: Error

Cause: The cluster that contains the specified DSN cannot stop.

Impact: The state of the cluster is unknown, it may or may not be running.

User Action: Contact TimesTen Customer Support.

48027

The cluster for DSN
dsn_name partly offline.

Some resources of the specified cluster are offline.

You may be able to restart the offline resources by calling:

ttCWAdmin -start -dsn dsn_name

48028

Could not deregister the
TimesTen cluster for
containing DSN dsn_name.

The replication scheme does not exist in the specified cluster databases. Stop the cluster by calling:

ttCWAdmin -stop -dsn dsn_name

Then drop the cluster by calling:

ttCWAdmin -drop -dsn dsn_name

48029

Failed to drop active
standby pair replication
scheme for DSN dsn_name on
host host_name.

The replication scheme does not exist in the specified database on the specified host.

48030

TimesTen Cluster agent could
not find application script
file with name script_name
for the TimesTen cluster
containing DSN dsn_name.

Verify that the application script exists in the script installation directory on all hosts of the cluster.

48031

Failed to create action
script for Oracle Clusterware
resource resource_name of
the TimnesTen clsuter
containing the DSN dsn_name.

Verify that the permissions are correct and there is enough and available space in the script installation directory.

48032

Failed to delete action
script for Clusterware
resource resource_name of
the TimesTen cluster
containing the DSN dsn_name.

Verify that the permissions in the script installation directory are correct.

48033

Syntax error exists in line
"line_text" in cluster
configuration file
file_name for DSN dsn_name.

See the description of the attribute in the "TimesTen Configuration Attributes for Oracle Clusterware" in the Oracle TimesTen In-Memory Database Replication Guide for the correct configuration file syntax.

48034

An unkown attribute
attribute_name mentioned in
the cluster configuration
file file_name for DSN dsn_name.

See the description of the attribute in the "TimesTen Configuration Attributes for Oracle Clusterware" in the Oracle TimesTen In-Memory Database Replication Guide for the correct configuration file syntax.

48035

Conflicting attribute
attribute_name in the
cluster configuration file
file_name for the DSN
dsn_name.

Multiple entries found for the specified attribute in the cluster configuration file. Remove the conflicting attribute(s) and retry the operation.

48036

Illegal value value for
attribute attribute_name in
the cluster configuration
file file_name for the DSN
dsn_name.

See the description of the attribute in the "TimesTen Configuration Attributes for Oracle Clusterware" in the Oracle TimesTen In-Memory Database Replication Guide for the correct configuration file syntax.

48037

Number of subscribers for
the TimesTen cluster
containing DSN dsn_name
exceeded the maximum.

See "System Limits" in the Oracle TimesTen In-Memory Database Reference for the maximum number of subscribers in an active standby pair.

48038

Application type of
Subscriber specified for
application
application_name, but no
subscribers are configured
for the TimesTen cluster
containing the DSN dsn_name.

An application type of Subscriber may only be configured if the TimesTen cluster contains subscriber databases.

48039

Invalid subscriber index
specified for application
application_name in the
TimesTen cluster containing
the DSN dsn_name.

The specified subscriber index may not be 0 or less, or greater than the number of subscriber databases.

48040

Orphaned or conflicting
application attribute
attribute_name specified in
the cluster configuration
file file_name for DSN dsn_name.

Verify that the TimesTen cluster configuration file for specified DSN does not contain duplicate application attributes and that the first application attribute for each application is AppName.

48041

Connection to Oracle with
OracleNetServiceName name
failed.

In the sys.odbc.ini entry for the DSN, verify the value for OracleNetServiceName attribute. Also verify that the -tns_admin option is specified correctly in the ttendaemon.options file.

Finally, check that the Oracle database is still live.

48042

Failed to determine
installation information.

Internal error. Contact TimesTen Customer Support.

48043

The send string string is
too long.

The length of an attribute value or a replication scheme is limited to 409600.

Verify the length of the attribute values in the cluster configuration file, and the replication scheme if it is specified using the RepDDL attribute.

48044

Wrong ACK ack_string
received.

Internal error. Contact TimesTen Customer Support.

48045

No DSN specified in
ttCWAdmin command
command_line.

Most ttCWAdmin utility commands require that you specify the DSN. Retry the command with the option -dsn dsn_name.

48046

Could not connect to remote
store store_name on host
host_name

The host is down, or the TimesTen main daemon or replication agent are down on the specified host, or the database on the specified host is not an active or standby master.

48047

Replication checksum
checksum_value of the local
store dsn dsn_name does not
match the original checksum
checksum_value of the
replication scheme.

This is a transient error. The local database is automatically duplicated from the remote database in the event of a checksum mismatch.

48048

Another resources is already
running the action program
binary_executable_name for
the DSN dsn_name.

Transient error. A new source is starting, but the specified local database is managed by an existing Oracle Clusterware resource. The cluster automatically relocates the new resource to a different host.

48049

Failed to start/stop the
replication agent for the DSN
dsn_name.

Transient error. The cluster automatically corrects the problem.

48050

Failed to start/stop the
cache agent for the DSN
dsn_name.

This may occur if no cache groups are defined in the DSN, but the CacheConnect attribute is specified with a value of "Y" in the TimesTen cluster configuration file.

48051

TimesTen cluster action
program
binary_executable_name
timed out for the DSN
dsn_name.

The cluster action program was unable to start the database with a replication state of either active or standby, or was unable to create a subscriber. This may happen if there is a network error in the cluster, or the original active database is destroyed.

48052

Failed to determine the
master host containing the
DSN dsn_name.

Type of Message: Error

Cause: The master host containing the specified DSN could not be determined.

Impact: The cluster cannot start.

User Action: Ensure that your TimesTen configuration attributes for Oracle Clusterware are correct. The local host should be one of the master hosts or contain one of the master VIP addresses in an active standby pair scheme. For more information see, "TimesTen Configuration Attributes for Oracle Clusterware" in the Oracle TimesTen In-Memory Database Replication Guide. If you are unable to troubleshoot the error or still receive this error, contact TimesTen Customer Support.

48053

Could not find remote active
data store for the
DSN dsn_name.

The cluster action program was unable to contact the remote active database.

This may be a transient network problem.

48054

TimesTen cluster program
could not destroy the data
store with the DSN dsn_name.

Internal error. Contact TimesTen Customer Support.

48055

Could not find standby host
in the replication scheme for
the DSN dsn_name.

A query to the replication system table TTREP.TTSTORES has failed. Check for SQL errors in the ttmesg.log file.

48056

Could not find data store
backup directory for the DSN
dsn_name.

Verify that the backup directory is accessible from all hosts in the TimesTen cluster.

48057

Another TimesTen Cluster
agent is running.

Stop the TimesTen Cluster agent manually by calling ttCWAdmin -shutdown.

48058

TimesTen Cluster agent
received an unkown command:
command_string.

Internal error. Contact TimesTen Customer Support.

48059

TimesTen Cluster agent did
not successfully receive all
parameters of the cluster.

The ttCWAdmin utility command closed the connection to the TimesTen Cluster agent due to previous errors or due to a TCP timeout. The TCP timeout for communication between ttCWAdmin and the TimesTen Cluster agent is 30 seconds.

Retry the operation if no previous errors or a timeout are mentioned in the ttcwerrors.log file.

48060

TimesTen Cluster agent could
not successfully verify
Oracle password for the
OracleNetServiceName =
oracle_net_service_name.

Verify that the Oracle database password is correct.

48061

TimesTen Cluster agent
received NULL user ID for the
DSN dsn_name.

Internal error. Contact TimesTen Customer Support.

48062

TimesTen Cluster agent
received NULL password for
the DSN dsn_name.

Internal error. Contact TimesTen Customer Support.

48063

TimesTen Cluster agent could
not create files on
socket_file_directory.

On Linux and UNIX systems, all cluster processes of a particular TimesTen instance have their socket files in the temporary directory crsTT_instance admin_instance name. Oracle Clusterware executes action programs that communicate with the TimesTen cluster processes through these file sockets.

Ensure that the TimesTen instance administrator and the Clusterware administrator users have read, write and execute permissions on the temp (/tmp) directory.

In the ttcwerrors.log file, check if any OS errors occurred before this error.

48064

Failed to determine the
status of the TimesTen main
daemon with the daemon home
directory
daemon_home_directory and
daemon port number
port_number.

The daemon is not running, or it is running in a different home directory and with a different port number.

Verify that the daemon is running in the appropriate location.

If the daemon is running, contact TimesTen Customer Support with the detailed output from ttversion -m on the terminal where the daemon was started.

48065

Failed to obtain replication
route from TTCW:
error_string.

Type of Message: Error

Cause: The replication route from TimesTen Clusterware cannot be obtained.

Impact: The attempted operation or TimesTen Clusterware ran into an irrecoverable error.

User Action: If you get this error when Oracle Clusterware is managing replication, contact TimesTen Customer Support. If Oracle Clusterware is not managing replication, you can ignore this error.

48066

The master/subscriber host
name host_name is invalid.

Verify that the host name is correct and the host exists in the network domain name system.

48067

Failed to read the cluster
configuration file file_name

Check for OS errors preceding this error in the ttcwerrors.log file.

48068

Failed to obtain an IP
address for the host
host_name

Verify that the host name is correct and the host exists in the network domain name system.

48069

Process_name failed to
connect to the DSN dsn_name
due to the error
ODBC_native_error_number

Check for specific connection errors in the ttmesg.log file.

48070

Virtual IP addresses for the
DSN dsn_name were not found
in the cluster configuration
file file_name.

A cluster configuration that uses virtual IP addresses must contain the attribute MasterVIP, specifying the virtual IPs to be used for master databases. If the configuration includes subscribers, it must also include the attribute SubscriberVIP.

48071

The resource resource_name
is offline.

An Oracle Clusterware resource is offline. If the TimesTen Cluster agent is offline, bring it up by calling:

ttCWAdmin -init

If the TimesTen Cluster agent is online, call:

ttCWAdmin -start -dsn dsn_name

to start all other resources.

48072

Incorrect response received
from TimesTen Cluster agent
for the DSN dsn_name.

Verify that the TimesTen Cluster agent is running and is listening to an available TCP port.

48073

The line line in the
cluster configuration file is
too long. It must be less
than posix_LINE_MAX_value.

If a configuration line is too long, it may be split into multiple lines. Each line may be ended with a "\" character to indicate that it should be concatenated with the following line. The final concatenated string may be no longer than

2 * posix_LINE_MAX_value.

48074

The concatenated line 'line'
in the cluster configuration
file is too long. It must be
less thantwo times max_value.

An attribute value is too long and must be shortened.

48075

The TimesTen cluster
configuration for the DSN
dsn_name was not found in
the cluster configuration
file file_name.

Verify that the configuration is specified correctly for the specified DSN in the cluster configuration file.

48076

Less than two host names
specified for MasterHosts for
the DSN dsn_name in the
cluster configuration file
file_name.

At least two host names must be specified for MasterHosts.

48077

Invalid AppType specified
for the application
application_name

The AppType attribute for an application cannot be specified as Active or Standby when the ClusterType is Subscriber.

48078

Attribute attribute_name
missing for the DSN
dsn_name in the cluster
configruation file file_name.

A required virtual IP attribute is missing from the cluster configuration file.

48079

No value specified for
SubscriberHosts for the DSN
dsn_name in the cluster
configuration file file_name.

If the ClusterType of the cluster configuration is Subscriber, at least one host name must be specified for SubscriberHosts.

48080

Less than two Virtual IP
addresses specified for the
attribute MasterVIP for the
DSN dsn_name in the cluster
configuration file file_name.

If the ClusterType of the cluster configuration is Active and VIPInterface and VIPNetMask are specified, you must specify at least two virtual IP addresses for the attribute MasterVIP.

48081

No value specified for
SubscriberVIP for the DSN
dsn_name in the cluster
configuration file file_name.

If subscribers exist in the cluster configuration and VIPInterface and VIPNetMask are also specified, you must specify at least one virtual IP address for the attribute SubscriberVIP.

48082

Backups illegally specified
for the DSN dsn_name in the
cluster configuration file
file_name.

Backups may only be specified for a DSN when the ClusterType is Active.

48083

A required  attribute
attribute_name missing for
the application
application_name
for the DSN dsn_name in the
cluster configuration file
file_name.

See the description of the attribute in the "TimesTen Configuration Attributes for Oracle Clusterware" in the Oracle TimesTen In-Memory Database Replication Guide for the correct configuration file syntax.

48084

The TimesTen cluster monitor
process process_name failed.

The specified process has failed. Check the preceding errors in the ttcwerrors.log file for details.

48085

Failed to create directory
directory_name for socket
files.

A directory must be created for socket files in /tmp on UNIX and C:\Temp on Windows. Check for preceding OS errors in the ttcwerrors.log file.

48086

Failed to obtain port number
for the TimesTen Cluster agent.

Internal error. Contact TimesTen Customer Support.

48087

Failed to obtain process ID
file file_name for reading.

Every cluster monitor process creates a file in the TimesTen info directory that contains its process ID. If this file is missing, the corresponding cluster monitor process is probably not running. If you continuously get this error, contact TimesTen Customer Support.

48088

Failed to delete directory
socket file directory
directory_name.

Check OS errors preceding this error in the ttcwerrors.log file.

48089

TimesTen Cluster agent could
not succesfully receive all
application information for
the DSN dsn_name.

Check for TCP communication errors or OS errors preceding this error in the ttcwerrors.log file.

48090

TimesTen Cluster agent could
not successfully receive
attribute_name for the
cluster containing the DSN
dsn_name.

Type of Message: Error

Cause: The TimesTen Cluster agent could not receive the specified information when exchanging information with another node in the cluster.

Impact: Oracle Clusterware may fail.

User Action: Check for TCP communication errors or operating system errors preceding this error in the ttcwerrors.log file. Diagnose and fix the errors. Then run the ttCWAdmin utility command that failed.

48091

TimesTen Cluster agent could
not determine
OracleNetServiceName from the
DSN dsn_name.

Verify that OracleNetServiceName is specified in the DSN configuration in the ODBCINI file.

48092

TimesTen Cluster agent could
not successfully send
attribute_verification_code
for the clsuter containing
the DSN dsn_name.

Check for TCP communication errors or OS errors preceding this error in the ttcwerrors.log file.

48093

TimesTen Cluster agent could
not alter autorefresh state
to PAUSED for the cache group
owner.cache_group_name on the
DSN dsn_name.

Internal error. Contact TimesTen Customer Support.

48094

The cluster monitor process
process_name for the DSN
dsn_name failed to obtain
connection string.

Type of Message: Error

Cause: The indicated cluster monitor process could not obtain a connection string. A common cause for this is that the database does not exist.

Impact: The cluster cannot run.

User Action: Ensure that the database exists. For more information on installing a TimesTen database, see Oracle TimesTen In-Memory Database Installation Guide. If you get this error when the database already exists, contact TimesTen Customer Support.

48095

The cluster monitor process
process_name detected an
invalid data store for the
DSN dsn_name.

This error may be received while a failed database is in the process of recovery.

48096

The DSN dsn_name on Remote
master host host_name
is unavailable.

A cluster monitor process failed to get a response from the remote replication agent.

48097

Data store dsn_name has
changed its role to
ACTIVE/STANDBY/IDLE

The specified database changed roles without the intervention of a cluster monitor process.

48098

Cluster backup failed for
the data store dsn_name on
host host_name.

Check preceding errors in the ttcwerrors.log file.

48099

TimesTen daemon is not
running on port port_number.

The TimesTen main daemon may have failed. Check for errors in the ttmesg.log file.

48100

TimesTen daemon port
port_number in use by
TimesTen daemon for other
unknown instance with process
ID process_id_number.

The configured TimesTen daemon port is not available to the current instance.

48101

TimesTen daemon port
port_number is in use by an
unknown process.

The TimesTen daemon port is not available to the instance.

48102

The host name host_name in
the TTREP.TTSTORES table of
data store dsn_name does not
match the assigned host name
host_name.

The host name found in the TTREP.TTSTORES system table of the database does not match the host name assigned to the cluster program monitoring it. If the database is a standby master or a subscriber, it is being replaced with a duplicate from the active master. If the database is an active master, it is being recovered from a backup if backups are enabled, otherwise it failed.

48103

The local CTN (timestamp,
sequence_number) on the
data store dsn_name is larger
than that of the data store
on the remote host
host_name (timestamp,
sequence_number).

Trapped transactions exist on a failed active master database (the transactions were not replicated to the standby master before the database failed). The database is being duplicated to create standby master database that also contains all transactions.

48104

And internal error has
occurred for the TimesTen
cluster containing the DSN
dsn_name. Error_details.

Check for preceding errors in the ttcwerrors.log file.

48105

The data store space usage
has exceeded PermSize on DSN
dsn_name.

The database has run out of space and is considered failed.

48106

The data store dsn_name on
remote host host_name has
declared the local store as
FAILED.

If communication is interrupted between the replication agents long enough to meet the configured FAILTHRESHOLD value for the local database, it is automatically recovered by the cluster monitor program.

48107

The replication agent for
data store dsn_name is not
running.

The replication agent for the specified database is not running. Oracle Clusterware is restarting it.

48108

The cache agent for data
store dsn_name is not running.

The cache agent for the specified database is not running. The Oracle Clusterware is restarting it.

48109

The remote VIP
host_name/ip_address for
the data store dsn_name is
running on the local host.

This may happen if two master VIP addresses start running on the same physical host, such as when only one master host is available. hen an additional host becomes available.

48110

The remote data store
dsn_name on host
host_name is not in the
ACTIVE state.

The remote master database is not in the ACTIVE replication state.

48111

The local data store
dsn_name is not in the
ACTIVE or STANDBY state.

Type of Message: Error

Cause: The local master database is not in the ACTIVE or STANDBY replication state. The local master database is expected to be in the ACTIVE or STANDBY replication state during an intermittent transitional situation for the database, especially during a roll out or when a role change occurs.

Impact: None.

User Action: Rerun the operation that caused the error. If you still receive this error, contact TimesTen Customer Support.

48112

The last heartbeat from the
remote application agent for
data store dsn_name was more
than 60 seconds ago.

A heartbeat was not received from the remote replication agent. Verify the network connection between the remote and local hosts.

48113

Cache grid configuration
error for dsn dsn_name.error

This error may appear when running the ttCWAdmin -create utility. The cache grid configuration in the cluster configuration file is incorrect or incomplete for the cluster configuration of a particular DSN. The first string provides the DSN. The second string provides the error detail.

48114

Failed to string cache
grid string for the DSN
string.

This message appears when a cluster monitor process fails to attach or detach the cache grid agent in a cluster of a particular DSN.

48115

Not allowed since this store
(datastore on hostname)
is managed by Clusterware

A particular operation is disallowed since the database on a host is managed by Clusterware. The list of forbidden SQL operations include:

Starting or stopping replication agents.

Starting or stopping cache agents.

Altering or dropping an active standby pair.

48116

Unsupported Clusterware
version version_num.

The Clusterware version for this user does not work with TimesTen.

48117

Unable to obtain Clusterware
version.

Contact TimesTen Customer Support.

48118

The local CTN
(timestamp,sequencenumber) on
the data store dsn_name is
smaller than that of the data
store on remote host hostname
(timestamp,sequencenumber)
with virtual IP configured.

While a cluster monitor is bringing up a standby or a read-only subscriber database, and the database is already present locally, the replication CTN of the local database is checked with that of the remote master database. If the CTN of the local database is smaller than that of the remote master database, the local database may have missed transactions that the remote master database had sent. In that case, the local database is destroyed and duplicated from the remote master.

This can occur with virtual IP configuration since a standby or a read-only subscriber database can be relocated from one physical host to another.

48119

Database dsn_name not
attached to Grid.

The database is not attached to the Grid. This message can occur at run-time if the database is invalidated, or if Grid communication fails. The process ttCRSmaster reports this message. There is no user action needed. The process ttCRSmaster will automatically attempt to attach to the Grid.

49001

Table table_name has no
primary key

Type of Message: Informational

Cause: The table referenced by the application workload is defined without a primary key.

Impact: A table without a primary key cannot be cached using the TimesTen Cache.

User Action: Add a primary key to the table definition in the TimesTen Cache Advisor database repository. Then run the ttCacheAdvisor utility.

For more information on the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49003

This FK column or the
corresponding parent column
column_name is not used by
all SQL statements using the
child table

Type of Message: Informational

Cause: A foreign key column or the corresponding parent column column_name is not referenced by at least one SQL statement that references the child table containing the foreign key definition.

Impact: If a SQL statement references a child table without using a join to the parent table using the foreign key, TimesTen only caches part of the child table. The table with the foreign key must be placed into its own cache group. Failing to do so, may result in different results when executing the same query on the Oracle database and TimesTen. For more information about multiple table cache groups, see "Multiple-table cache group" in the Oracle TimesTen Application-Tier Database Cache User's Guide.

User Action: Modify the SQL statement to include a join condition between the parent and child tables using the join key. Then run the ttCacheAdvisor utility to capture a new workload. If the table with the foreign key is placed in a writethrough cache group in the TimesTen Cache, examine your application for potential problems due to the omission of the foreign key definition.

For more information about multiple table cache groups, see "Multiple-table cache group" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49005

This FK completes a cycle in
the FK graph within the
recommended cache group

Type of Message: Informational

Cause: This foreign key completes a cycle in the foreign key graph. Multiple foreign key definitions can form a cycle in the foreign key graph when the defined join keys indicate there is more than one way to join the tables.

Impact: The TimesTen Cache only stores the rows from the child table (the table with the foreign key) that join to the parent table using the foreign key. Since each foreign key represents a potentially different subset of child rows, it is not possible to define multiple foreign keys in the TimesTen Cache that define multiple join paths.

User Action: Eliminate the cycle in the foreign key definitions in the TimesTen Cache Advisor database repository. Then run the ttCacheAdvisor utility to capture a new workload. If the table with the foreign key is placed in a writethrough cache group in the TimesTen Cache, examine your application for potential problems due to the omission of the foreign key definition.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49007

This column uses a data type
that is not supported by
TimesTen

Type of Message: Informational

Cause: The data type for the column is not supported by cache.

Impact: The column you specified cannot be cached in the TimesTen Cache.

User Action: Change the data type of the column in the TimesTen Cache Advisor database repository to a supported type. Also, ensure that you change the data type on your target Oracle database. Then run the ttCacheAdvisor utility.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference. For more information on supported data types, see "Data Types" in the Oracle TimesTen In-Memory Database SQL Reference.

49008

Insufficient cache space

Type of Message: Informational

Cause: The cache size you specified with the -cacheSize option of the ttCacheAdvisor utility is too small for the indicated column.

Impact: The SQL workload statements that reference the indicated column are executing on the Oracle database with no TimesTen Cache performance advantage.

User Action: Run the ttCacheAdvisor utility using a larger value for the -cacheSize option.

For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49009

ttCacheAdvisor failed to find
all tables and columns after
num_attempts attempts

Type of Message: Informational

Cause: The TimesTen Cache Advisor found the indicated SQL statement to be complex.

Impact: The TimesTen Cache Advisor recommendation does not include any columns or tables for the indicated SQL statement.

User Action: Simplify the SQL statement. Then run the ttCacheAdvisor utility to capture a new workload.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49010

Error creating table
table_name during SQL
validation: error_condition

Type of Message: Informational

Cause: A SQL validation error occurred while creating the specified table. A detailed error message follows this message.

Impact: The TimesTen Cache Advisor recommendation does not include any columns or tables for the indicated SQL statement.

User Action: Address the error condition by making the appropriate changes to the table and column definitions in the TimesTen Cache Advisor database repository. Also, ensure that you address this error condition on your target Oracle database. Then run the ttCacheAdvisor utility to capture a new workload.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49012

Error creating user user_name
during SQL validation:
error_condition

Type of Message: Informational

Cause: A SQL validation error occurred while creating the specified user. A detailed error message follows this message.

Impact: The Cache Advisor recommendation does not include any columns or tables for the indicated SQL statement.

User Action: Address the error condition by making changes in the TimesTen Cache Advisor database repository. Also, ensure that you apply these changes on your target Oracle database. Then run the ttCacheAdvisor utility to capture a new workload.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49013

Column column_name not found
during SQL validation:
include any missing schemes
with the -oraTarget -oraConn
command-line option

Type of Message: Informational

Cause: The indicated SQL statement references the specified column. A definition for the specified column was not found in the TimesTen Cache Advisor database repository.

Impact: The TimesTen Cache Advisor recommendation does not include any columns or tables for the indicated SQL statement.

User Action: Address the missing column by making scheme changes in the TimesTen Cache Advisor repository. Also, ensure that you apply the scheme changes on your target Oracle database. Then run the ttCacheAdvisor utility to capture a new workload.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49014

Table table_name not found
during SQL validation:
include any missing schemes
with the -oraTarget -oraConn
command-line option

Type of Message: Informational

Cause: The indicated SQL statement references the specified table. A definition for the specified table was not found in the TimesTen Cache Advisor database repository.

Impact: The TimesTen Cache Advisor recommendation does not include columns or tables for the indicated SQL statement.

User Action: Address the missing table by making scheme changes in the TimesTen Cache Advisor repository. Also, ensure that you apply these scheme changes on your target Oracle database. Then run the ttCacheAdvisor utility to capture a new workload.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49015

Insufficient memory to
allocate number_bytes bytes
for purpose_mem_allocation

Type of Message: Error

Cause: The TimesTen Cache Advisor does not have enough memory for the performance evaluation.

Impact: The performance evaluation cannot be completed. The performance data used for making cache evaluations is incomplete.

User Action: Make more memory available before running the performance evaluation. You can shut down memory consuming programs. You can also increase the amount of virtual memory. Then run the ttCacheAdvisor utility. For more information on how to increase virtual memory, see "Check available swap space (virtual memory)" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

49033

Array fetch buffer allocated
with allocated_bytes bytes is
insufficient for a single row
of required_bytes bytes for
statement: sql_statement

Type of Message: Error

Cause: The specified SQL statement requires too much memory to fetch a single row for the performance evaluation. allocated_bytes indicates the largest size that the TimesTen Cache Advisor can fetch. required_bytes indicates the size required by the indicated SQL statement.

Impact: The indicated SQL statement cannot be performance evaluated. Cache Advisor cannot determine whether to cache tables and columns for the indicated SQL statement.

User Action: Alter the indicated SQL statement to reduce the memory required to fetch a single row. Then run the ttCacheAdvisor utility to capture a new workload.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49034

Bind data type bind_type
(num_data_bind_type) may
be supported by TimesTen but
is not yet supported by
ttCacheAdvisor; skipping
evaluation of SQL using this
bind data type

Type of Message: Error

Cause: The indicated SQL statement uses a bind data type that may or may not be supported by TimesTen but is not supported by the TimesTen Cache Advisor.

Impact: The indicated SQL statement cannot be performance evaluated. The TimesTen Cache Advisor cannot determine the performance benefit for the indicated SQL statement.

User Action: Alter the indicated SQL statement to use a bind data type that is supported by the TimesTen Cache Advisor. Then run the ttCacheAdvisor utility to capture a new workload.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49039

Propagated from reference to
view or materialized view
view_owner.view_name

Type of Message: Informational

Cause: The indicated SQL statement references the view or materialized view view_owner.view_name. Other object references and any errors from the named view or materialized view are propagated to the indicated SQL statement.

Impact: None.

User Action: None.

49040

Synonym creation error
error_condition

Type of Message: Error

Cause: The indicated SQL statement references a synonym, but the specified error occurred when attempting to create the synonym on TimesTen.

Impact: The TimesTen Cache Advisor recommendation does not include any columns or tables for the indicated SQL statement.

User Action: Address the error condition by making changes in the TimesTen Cache Advisor database repository. Also, ensure that you apply these changes on your target Oracle database. Then run the ttCacheAdvisor utility to capture a new workload.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49041

Caching for this SQL
statement has no projected
performance advantage

Type of Message: Informational

Cause: There is not a performance advantage when you run the SQL statement on your TimesTen Cache as compared with your Oracle database.

Impact: The TimesTen Cache Advisor does not recommend caching columns or tables for the indicated SQL statement.

User Action: Tune the application schema in the TimesTen Cache Advisor database repository to work better with the TimesTen Cache. Also, ensure that you apply these changes on your target Oracle database. Then run the ttCacheAdvisor utility with the -evalSqlPerf option.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49042

Error occurred during
performance evaluation

Type of Message: Informational

Cause: The indicated SQL statement returned a different status code on the TimesTen Cache than on the target Oracle database.

Impact: The TimesTen Cache Advisor does not recommend caching columns or tables for the indicated SQL statement.

User Action: In the TimesTen Cache Advisor repository, modify either the SQL statement or the tables and columns that the SQL statement references or both. Then run the ttCacheAdvisor utility to capture a new workload.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

49043

Bind values for SQL statement
sql_statement were not
captured or included with the
workload; therefore, the
statement could not be
performance evaluated

Type of Message: Warning

Cause: The SQL statement contains bind values and was not captured with the workload. The -add -sqlStatementsTab option of the ttCacheAdvisor utility does not support inclusion of bind values.

Impact: The indicated SQL statement cannot be performance evaluated.

User Action: ALTER the indicated SQL statement to not use bind values. Then run the ttCacheAdvisor utility to capture a new workload.

For more information about the TimesTen Cache Advisor, see "Cache Advisor overview" in the Oracle TimesTen Application-Tier Database Cache User's Guide. For more information on the ttCacheAdvisor utility, see "ttCacheAdvisor" in the Oracle TimesTen In-Memory Database Reference.

Errors 50000 - 59999

Error number
Error or warning message
Details

51000

Failed to read log marker
packet

Type of Message: Error

Cause: The transaction log on disk may be corrupted. The transaction log may have not been written properly.

Impact: TimesTen failed to read the transaction log.

User Action: Contact TimesTen Customer Support.

51001

Failed to locate next log
record in rdlog

Type of Message: Error

Cause: The transaction log on disk may be corrupted. The transaction log may have not been written properly.

Impact: TimesTen failed to read the transaction log.

User Action: Contact TimesTen Customer Support.

51002

Failed to locate next log
record in the strand strand

Type of Message: Error

Cause: The transaction log on disk may be corrupted. The transaction log may have not been written properly.

Impact: TimesTen failed to read the transaction log.

User Action: Contact TimesTen Customer Support.

51003

Failed to locate next log
record in the block

Type of Message: Error

Cause: The transaction log on disk may be corrupted. The transaction log may have not been written properly.

Impact: TimesTen failed to read the transaction log.

User Action: Contact TimesTen Customer Support.

51004

Failed to map idmap(logical)
to lsn(physical)

Type of Message: Error

Cause: The transaction log on disk may be corrupted. The transaction log may have not been written properly.

Impact: TimesTen failed to read the transaction log.

User Action: Contact TimesTen Customer Support.

51005

Failed to preallocate log
file file_name.extension with
mode = mode

Type of Message: Error

Cause: TimesTen cannot allocate enough disk space for the log file.

Impact: The database cannot continue normal operations.

User Action: Ensure that there is enough space on disk to at least store a log file of the size specified in the LogFileSize attribute. For more information on the LogFileSize attribute, see "LogFileSize" in the Oracle TimesTen In-Memory Database Reference.

51006

Failed to flush to lwn =
LWN_boundary

Type of Message: Error

Cause: Timesten cannot flush the log up to the specified log write number (LWN) boundary.

Impact: The database cannot continue normal operations.

User Action: Contact TimesTen Customer Support.

51007

Failed to switch to lwn =
LWN_boundary in strand strand

Type of Message: Error

Cause: Timesten cannot advance the specified log write number (LWN) boundary in the specific strand.

Impact: The database cannot continue normal operations.

User Action: Contact TimesTen Customer Support.

51008

Failed to insert a log marker

Type of Message: Error

Cause: Timesten cannot insert a log marker to the log buffer.

Impact: The database cannot continue normal operations.

User Action: Contact TimesTen Customer Support.

2 Server Event Log Entries

This chapter describes messages that may be returned by the TimesTen Server.

By default, TimesTen messages are stored in:

A user error log that contains information you may need to see. Generally, these messages contain information on actions you may need to take.

A support log containing everything in the user error log plus information of use by TimesTen Customer Support.

For details on managing messages and the locations of the user and support logs, see "Modifying informational messages" in the Oracle TimesTen In-Memory Database Operations Guide.

List of log entries

Event ID
Message
Description

1

Unable to open TTServer
key from registry

Windows platform only. TimesTen Server could not open HKEY_LOCAL_MACHINE\SOFTWARE\ TimesTen\TimesTen1122\TTServer key from registry. Your TimesTen installation may be corrupted. Contact customer support for assistance.

2

TimesTen Server is
stopping

This message is informational only.

3

Socket send() failed.
Error_message

This message is caused by the failure of the system call send. Consult your system documentation to determine the cause of this error.

4

Server is exiting. Unable
to create server context
object (CSrvCtx)

An internal error occurred.Make a note of any information necessary to reproduce the error and then contact customer support for assistance.

5

Socket recv() failed.
Error_message

This message is caused by the failure of the system call recv. Consult your system documentation to determine the cause of this error.

6

Disconnecting client:
Client_host_name
(domain_name);
IP Address: client_IP;
Client PID: client_PID;
DSN: server_DSN;
UID: client_UID;
Total connect time:
ddd hh:mi:ss;
Total execution time:
ddd hh:mi:ss

This message is informational only. Could be used to match the connects and disconnects by TimesTen Client application to/from a TimesTen Server.

7

Unable to open the
ODBC.INI data sources
root

Windows platform only. TimesTen Server could not open HKEY_LOCAL_MACHINE\SOFTWARE \ODBC\ODBC.INI\ODBC Data Sources key from registry. Contact customer support for assistance.

8

Unable to read (numeric)
port number from registry;
using default port

Windows platform only. TimesTen Server could not read HKEY_LOCAL_MACHINE\SOFTWARE \TimesTen\TimesTen1122\Servers\logical_server\TCP_Port from registry. Ensure that you did not modify registry entries manually.

9

Server is exiting. Could
not cd to path. OS reports
error(error_number):
error_message

This message is caused by the failure of the system call chdir. Ensure that you have installed TimesTen properly and the directory exists. Consult your system documentation to determine the cause of this error.

10

Server is exiting. Could
not connect to TimesTen
daemon. Check to make sure
that the TimesTen
daemon/service is running

TimesTen Server communicates with TimesTen Data Manager daemon. Ensure that TimesTen Data Manager daemon/service is running.

11

Main Server cleaned up
all child processes and
exiting.

ServerProc thread of TimesTen Server accepts all connection requests from TimesTen Client. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error.

12

Server is exiting. Failed
to create shared memory
segment for IPC.
Error_message

This message is caused by the failure to create a shared memory segment for IPC. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error. This message is generated only for a connection that uses a shared memory segment as the IPC mechanism.

13

Server is exiting. Failed
to attach to shared memory
segment for IPC.
Error_message

This message is caused by the failure to attach to a shared memory segment for IPC. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error. This message is generated only for a connection that uses a shared memory segment as the IPC mechanism.

14

Server is exiting. Failed
to create semaphore for
IPC. Error_message

This message is caused by the failure of a semaphore creation. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error. This message is generated only when TimesTen Server is configured to allow shared memory segment as IPC.

15

Client application
terminated. Terminating
corresponding TimesTen
child server process

This message implies that the TimesTen Server has lost a TCP/IP socket connection to the TimesTen Client ODBC driver (and hence the application) before the application closed the ODBC connection properly. This can happen only if the client application (or the thread that had the ODBC connection) exited without closing the ODBC connection. This message is generated only for a connection that uses a shared memory segment as the IPC mechanism.

16

Connect succeeded from
client: client_host_name
(client_domain_name);
IP Address: client_IP;
Client PID: client_PID;
DSN: server_DSN;
UID: client_UID

This message is informational only. Could be used to match the Connects and Disconnects by TimesTen Client application to/from a TimesTen Server.

17

Connect failed for
client: client_host_name
(client_domain_name);
IP Address: client_IP;
Client PID: client_PID;
DSN: server_DSN;
UID: client_UID;
SQL State: SQL_state;
Error: error_message

This error is generated if SQLDriverConnect fails. The runtime error returned by the driver may indicate the cause of the error. The corrective action depends on the runtime error. For details, refer to the Microsoft ODBC Programmer's Reference and SDK Guide that is included with the ODBC SDK.

18

Server is exiting. Failed
to create REQUEST semaphore
for IPC. Error_message

TimesTen uses a pair of semaphores called REQUEST and RESPONSE to implement shared memory segment as IPC. This message is caused by the failure of a REQUEST semaphore creation. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error. This message is generated only when TimesTen Server is configured to allow shared memory segment as IPC.

19

Server is exiting. Failed
to create RESPONSE
semaphore for IPC.
Error_message

TimesTen uses a pair of semaphores called REQUEST and RESPONSE to implement shared memory segment as IPC. This message is caused by the failure of a RESPONSE semaphore creation. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error. This message is generated only when TimesTen Server is configured to allow shared memory segment as IPC.

20

Shared memory segment for
IPC exhausted the
configured maximum.
File: source_file_name;
line: line_number;
size: requested_size

There is not enough space left in the configured shared memory segment for IPC. Please refer to "Managing the size of the shared memory segment" in the Oracle TimesTen In-Memory Database Operations Guide to configure this properly. This message generated only for a connection that uses a shared memory segment as the IPC mechanism.

21

Server is exiting. Failed
to open shared memory
segment for IPC.
Error_message

This message is caused by the failure to create a shared memory segment for IPC. A log entry with EventID=99 just prior to this may contain additional information. Consult your system documentation to determine the cause of this error. This message is generated only for a connection that uses a shared memory segment as the IPC mechanism.

25

Server is exiting. Socket
initialization failed.
Error_message

Windows platforms only. Call to WSAStartup failed. Consult your system documentation to determine the cause of this error.

26

Server is exiting.
gethostname() failed.
Error_message

On UNIX platforms the uname call failed.

27

Server is exiting.
ttSetSockOptBool() failed.
Error_message

Failed to set a socket option of boolean type. Contact customer support for assistance.

32

Server is exiting. socket()
failed. Error_message

This message is caused by the failure of the system call socket. Consult your system documentation to determine the cause of this error.

33

Server is exiting.
gethostbyname() failed.
Error_message

This message is sent if the system call gethostbyname fails. Consult your system documentation to determine the cause of this error.

34

Server is exiting. bind()
failed. Error_message

This message is caused by the failure of the system call bind. Consult your system documentation to determine the cause of this error.

35

Server is exiting. listen()
failed. Error_message

This message is caused by a failure of the system call listen. Consult your system documentation to determine the cause of this error.

36

Successful TimesTen
Server startup.
Version:
server_version_number;
Host: server_host_name
(server_domain_name);
IP Address: server_IP;
port: port_number,
max connections:
max_connections_allowed

This message is informational only.

37

Client protocol version
client_version is not
supported by this server,
which uses version
server_version. Attempting
to renegotiate protocol
level.

There is a version mismatch between the TimesTen Client and TimesTen Server.

40

Server is exiting.
Error_message. A TimesTen
Server is already active on
this port

An attempt was made to start the TimesTen Server on a system where the same release of TimesTen Server is already running with the same port number. Each version of the TimesTen Server of the same release must have a unique port number.

50

Socket accept() failed. Error_message

This message is caused by the failure of the system call accept. Consult your system documentation to determine the cause of this error.

57

Error creating a mutex to
communicate with separate
server process.
Error_message

The communication setup between the main and child servers could not be set up properly. Contact customer support for assistance.

58

Error creating or mapping
mapped file to communicate
with separate server
process. Error_message

The event logged just prior to this one has further details, if any.

59

Error creating separate
server process.
Error_message

Operating system error. Make a note of the system error number and then contact your system administrator.

60

Error creating waitpid
thread. Error_message

Operating system error. Make a note of the system error number and then contact your system administrator.

61

Internal error in
TimesTen Server. File:
source_file_name; line:
line_number

Contact customer support for assistance.

62

Connection refused. Server
is processing a configured
maximum of number
connections

This message means that the maximum number of clients are currently connected. For more information on the maximum supported number of concurrent client connections for a TimesTen database and instance, see "System limits and defaults" in the Oracle TimesTen In-Memory Database Reference.

67

Failed to allocate
memory. File:
source_file_name; line:
line_number; size:
failed_malloc_size

Note that sometimes the size is logged as zero if for some reason TimesTen Server cannot determine it at the time of logging.

68

Failed to read request from
client. Closing connection
without reply.

The server connection to a client application failed. Common causes are:

- The client application exited without invoking the SQLDisconnect function.

- The waiting time specified in the TTC_Timeout attribute for the client application was exceeded.

For more information on the SQLDisconnect function, see "Managing TimesTen database connections" in the Oracle TimesTen In-Memory Database C Developer's Guide. For more information on the TTC_Timeout client connection attribute, see "TTC_Timeout" in the Oracle TimesTen In-Memory Database Reference.

69

Child server died due to
SEGV signal error_message

A SQL request caused a thread stack overflow. Try increasing the value for the ServerStackSize attribute. For more information on the ServerStackSize server connection attribute, see "ServerStackSize" in the Oracle TimesTen In-Memory Database Reference.

70

Invalid value
specified_value for
attribute: should be in
range min_value to
max_value. Using used_value

The specified value for the specified attribute is invalid. The message identifies the valid range for the specified attribute value.

71

Connect received from
client: client_host_name
(client_domain_name);
IP address: client_IP;
Client PID: client_PID;
DSN: server_DSN;
UID: client_UID

This message is informational only.

99

Log_message

Certain informational/error messages are logged with this event id.

3 Diagnostics through SNMP Traps

Simple Network Management Program (SNMP) is a protocol for network management services. Network management software typically uses SNMP to query or control the state of network devices like routers and switches. These devices sometimes also generate asynchronous alerts called Traps to inform the management systems of problems.

The following sections describe SNMP and traps in TimesTen:

TimesTen and SNMP

SNMP data types

Trapping out of space messages

How TimesTen sends SNMP traps

Generating and receiving SNMP traps

Configuring the snmp.ini file

Trap truncation on overflow

The TimesTen MIB

The traps

Trap names and severity levels

Example

TimesTen and SNMP

TimesTen cannot be queried nor controlled through SNMP. TimesTen only sends SNMP traps for certain critical events, to possibly facilitate some user recovery mechanisms. TimesTen can send traps for the following events:

Assertion failure

Death of daemons

Database invalid

Replicated transaction failure

Database out of space

Autorefresh transaction failure

Replication conflict resolution

File write errors

These events also cause log entries to be written by the TimesTen daemon, but exposing them through SNMP traps allows for the possibility of having some network management software take immediate action.

SNMP data types

The SNMP data types are either INTEGER or TEXT.

ASN_INTEGER data are:

ttPid

ttDSNConn

ttDSCurSize

ttDaeInst

ttRepReceiverPort

ttDSReqSize

ttDaePid

ttDSMaxSize

ttCacheAgentPid

The rest of the variables are ASN_OCTET_STRING type.

Trapping out of space messages

By default, TimesTen records that database space is low based on the region space thresholds of PermWarnThreshold and TempWarnThreshold attributes. If the PermWarnThreshold, which defines the permanent database memory region threshold, is set to 90, TimesTen records a message that the permanent database memory is full. Once the database permanent memory becomes 10% less than the set threshold, which in this case would be 80% full, TimesTen records a second message indicating that the database is no longer low on space.

When connecting to a database, you can change the out of space threshold by setting the PermWarnThreshold and TempWarnThreshold attributes. See "PermWarnThreshold" and "TempWarnThreshold" in Oracle TimesTen In-Memory Database Reference.

How TimesTen sends SNMP traps

SNMP traps are UDP/IP packets. Therefore, there is no guarantee of delivery, and it is not an error if there are no subscribers for the trap. TimesTen sends only SNMPv1 traps, which all network management systems should understand.

Generating and receiving SNMP traps

To enable SNMP trap generation, change the line -enabled 0 in the snmp.ini to 1. TimesTen does not generate SNMP traps by default because, in the case of repeated failures, such as an application that continues to attempt to insert new rows into a full database, the application may experience a performance slowdown due to generation of SNMP traps.

You must have network management software to receive SNMP traps.

Configuring the snmp.ini file

The configuration file install_dir/info/snmp.ini on UNIX systems and install_dir\srv\info\snmp.ini on Windows systems enables or disables trap generation, controls the community string for SNMP traps, the target host and the target port on which to listen for traps.

Note:

install_dir represents the path of the TimesTen installation.

The file contents are:

Component
Description

enabled {0|1}
Disable or enable SNMP trap generation.

-community {string}
The SNMP community string. Default is "public."

-trapdest {host:portnumber}
The SNMP agent host name and port number where SNMP trap messages are received. The default host is "localhost." The default port number where the SNMP agent listens is 162.

Up to 8 destinations may be specified.in the snmp.ini file.

-trapport {portnumber}
To receive SNMP traps on the local system when you do not want to use the default port, specify the port number with the -trapport option. The default port number is 162. If neither -trapdest or -trapport are specified, traps are sent to the default, which is localhost on the IPv4 loopback address and port 162.

An optional environment variable, TT_SNMP_INI, can override the location of the snmp.ini file. If this variable is set, it should contain the full path of the SNMP sender configuration file, which can have a name other than snmp.ini.

Example 3-1 Settings for one target destination

To send messages and set one target destination, your snmp.ini file looks like this:

#Enable SNMP trap generation
-enabled 1
#Default community is "public"
-community "public"
#Default trap destination is "localhost" and default destination SNMP trap port is 162
-trapdest "localhost:162"

Example 3-2 Settings for multiple target destinations

To send messages and set multiple target destinations, your snmp.ini file looks like this:

#Enable SNMP trap generation
-enabled 1
#Default community is "public"
-community "public"
#Default trap destination is "localhost" and default destination SNMP trap port is 162
-trapdest "localhost:162"
-trapdest "pluto:10999"
-trapdest "mymachine:189"

Example 3-3 Settings to disable SNMP trap generation

To disable trap generation, your snmp.ini file looks like this:

#Disable SNMP trap generation
-enabled 0
#Default community is "public"
-community "public"
#Default trap destination is "localhost" and default destination SNMP trap port is 162
-trapdest "localhost:162"

If one or more of the options is not specified, or if the snmp.ini file is missing, then the default value for each option is used.

Trap truncation on overflow

The maximum packet size of a single trap is 1024 bytes. If there is more data than can fit into the 1024 byte limit, the trap is truncated to fit. In this case, the trap contains a ttTrapTruncated OID set to 1.

Note:

You can use the UCD-SNMP perl module from the CPAN http://www.cpan.org/ directory to receive and act upon SNMP traps.

The TimesTen MIB

A Management Information Base (MIB) is like a database schema. It describes the structure of the SNMP data. For more information about MIBs in general, refer to the previously mentioned SNMP overview documents.

The MIB extension file, install_dir/mibs/TimesTen-MIB.txt, describes the structure of the TimesTen SNMP information.

The TimesTen OID is rooted at Private Enterprise 5549. The complete path to root is iso.org.dod.internet.private.enterprise.TimesTen.* or numerically, 1.3.6.1.4.1.5549.*.

The traps

Every trap has a GMT timestamp of when the trap occurred, as well as the Process ID, user name (or User ID on UNIX systems) of the process, TimesTen instance name, TimesTen, release number and a trap specific Message. In addition, most traps provide additional information specific to that message. For example the ttRepAgentDiedTrap also provides the Replication Store ID. For a list of the variables for each trap see the TimesTen-MIB.txt file.

Trap names and severity levels

TimesTen SNMP traps can be categorized by severity level. The information in the trap can be of the type:

Informational

Warning

Error

Table 3-1 describes each trap and its severity level.

Table 3-1 Trap Description and Severity Levels

Trap name
Severity level
Description

ttAssertFailTrap

Error

TimesTen Assertion Failure.

ttAsyncMVFailed

Warning

A refresh of Asynchronous materialized view failed. The SNMP trap includes dsname, daemon PID and viewid. If the error is due to a transient error, such as locking, the refresh may succeed in the next refresh.

ttCacheAgentDiedTrap

Error

The TimesTen Application-Tier Database Cache daemon died.

ttCacheAgentFailoverTrap

Warning

The cache agent detected that a connection to the Oracle database had been lost and has begun to recover the connection.

ttCacheAutoRefFailedTrap

Error

TimesTen Application-Tier Database Cache incremental autorefresh failed.

ttCacheAutorefreshDsMarkedDeadTrap

Warning

TimesTen Application-Tier Database Cache incremental autorefresh failed. The cache agent for a remote datastore has stopped or is no longer responding. Autorefresh for the remote datastore has been disabled.

ttCacheAutorefreshLogSpaceDeFragDetectedTrap

Warning

Some of the autorefresh change log tables on the Oracle database are fragmented. For more information on how to defragment log tables, see "Fragmented autorefresh change log table space" in the Oracle TimesTen In-Memory Database Troubleshooting Guide.

ttCacheAwtRtReadFailedTrap

Error

For Asynchronous Writethrough cache groups, runtime information is stored on the Oracle database instance. While reading this information from the Oracle database, replication either could not find the runtime data table (tt_version_reppeers) or could not find the information within the table.

ttCacheAwtRtUpdateFailedTrap

Error

For Asynchronous Writethrough cache groups, runtime information is stored on the Oracle database instance. While updating this information replication either could not find the runtime data table (tt_version_reppeers) or could not find the information within the table.

ttCacheCgNotAutorefreshedTrap

Warning

The cache group will not be autorefreshed. Instead, it must be manually recovered by performing manual load or refresh cache group.

ttCacheLowOracleTblSpace

Warning

The tablespace the cache admin user is using is below the minimum threshold.

ttCacheRecoveryAutorefreshTrap

Warning

The Cache Agent is performing a full autorefresh. This may be needed when a change log table on the Oracle database was truncated because of lack of tablespace for the cache administration user.

ttCacheValidationAbortedTrap

Error

The Cache Agent aborted cache group validation because of an irrecoverable error. Please refer to the user error log for details.

ttCacheValidationErrorTrap

Error

The Cache Agent has detected irrecoverable anomalies with cache group cache-group-name that will prevent it from properly refreshing the cache group, or it has detected irrecoverable anomalies within the refresh interval time-in-ms. Please refer to the user error log for details.

ttCacheValidationWarningTrap

Warning

The Cache Agent has detected anomalies with cache group cache-group-name that may prevent it from properly refreshing the cache group. Please refer to the user error log for details.

ttDSCkptFailedTrap

Error

A checkpoint has failed. Check the user error log and get view the checkpoint history using the built-in procedure ttCkptHistory.

ttDaemonOutOfMemoryTrap

Error

Call to malloc failed in TimesTen daemon.

ttDSDataCorruptionTrap

Error

Database corruption error has occurred.

ttDSGoingInvalidTrap

Error

Setting database to invalid state. Database invalidation usually happens when an application that is connected to the database is killed or exits abruptly without first disconnecting from the database.If TimesTen encounters an irrecoverable internal error during a database operation, it may also invalidate the database.You must commit or rollback and recover the database.

ttDSThreadCreateFailedTrap

Error

A process (typically multi-threaded) having multiple connections to a database exits abnormally. The subdaemon assigned to clean up the connections creates a separate thread for each connection. If creation of one of these threads fails, this trap is thrown. Thread creation may fail due to memory limitations or having too many threads in the system. After the trap is thrown, the thread creation is attempted four more times, with an increasingly longer pause between each attempt. The total time between the first and last attempt is approximately 30 seconds. If the fifth attempt fails, the database is invalidated.

ttFileWriteErrorTrap

Error

Error encountered during file I/O write.

ttMainDaemonDiedTrap

Error

Main or sub daemons died abnormally. This message is sent by a subdaemon when it notices that the main daemon has died. It suggests that the main daemon has been killed or has crashed.You must restart the main daemon.

ttMainDaemonExitingTrap

Informational

Main or sub daemons exiting normally.

ttMainDaemonReadyTrap

Informational

Main daemon has started.

ttMsgLogOpenFailedTrap

Error

The message log could not be opened, possibly because of a lack of privileges on the file. Check the file location and privileges.

ttPartitionSpaceExhaustedTrap

Error

Database memory region (permanent or temporary) space is exhausted. This message is sent when either the permanent or temporary free space in the database is exhausted. Generally this message is preceded by the ttPartitionSpaceStateTrap warning message. See "PermWarnThreshold" and "TempWarnThreshold" in Oracle TimesTen In-Memory Database Reference for information on how to set the threshold.

ttPartitionSpaceStateTrap

Warning

Database memory region (permanent or temporary) space is transitioning from OK to low or vice versa. This message is sent when either the permanent memory region or the temporary memory region free space in the database reaches a threshold or transitions back below the threshold. This message is sent only when the free space has reached the threshold specified by the PermWarnThrehold or TempWarnThreshold attribute at the time of the first connection to the database. See "PermWarnThreshold" and "TempWarnThreshold" in Oracle TimesTen In-Memory Database Reference for information on how to set the threshold.

ttQueryThresholdWarnTrap

Warning

A SQL query exceeded the user-specified threshold. The text of the query can be found n the user log message. The Transaction ID and the Statement ID of the query can be found both in the trap and the user log message. After issuing the trap, the query continues executing.

ttRepAgentClockSkewTrap

Error

Replication with a peer failed due to excessive clock skew. The skew between nodes in an active standby scheme has exceeded the allowed limit of 250ms.

ttRepAgentDiedTrap

Error

A replication agent has died abnormally. This message is sent when the main TimesTen daemon notices that a replication agent has died abnormally. This generally means that the replication agent has been killed or has crashed.

ttRepAgentExitingTrap

Informational

Replication agent exiting normally.

ttRepAgentStartingTrap

Informational

Replication agent starting.

ttRepCatchupStartTrap

Warning

Indicates that TimesTen has begun to restore a master from a subscriber where bi-directional replication has been configured, after a failure.

ttRepAgentStateChange

Informational

Indicates the state of the replication agent. The possible states of the replication agent are ACTIVE, FAILED, IDLE, RECOVERING, STANDBY, and UNKNOWN. TimesTen only sends this trap when the state of the replication agent changes.

ttRepCatchupStopTrap

Warning

Indicates that TimesTen has restored a master database from a subscriber, where bi-directional replication was configured.

ttRepConflictReportStartingTrap

Informational

Indicates that conflict reporting has been restarted because the rate of conflicts has fallen below the low water mark set in the replication scheme. This trap also indicates how many conflicts went unreported during the period in which reporting was suspended.

ttRepConflictReportStoppingTrap

Informational

Indicates that suspension of conflict reporting has occurred because the rate of conflicts has exceeded the high water mark set in the replication scheme.

ttRepReturnTransitionTrap

Warning

Replication return receipt has been enabled or disabled on the subscriber.

ttRepSubscriberFailedTrap

Error

Subscriber marked as failed because too much log accumulated on its behalf by the master.

ttRepSubscriberTCPConnectFailedTrap

Error

A replication TCP connection failed.

ttRepUpdateFailedTrap

Warning

A replication insert, update or delete operation failed.

ttUnexpectedEndOfLogTrap

Error/Warning

Premature end of log file reached during a database recovery. If your application connected with LogAutoTruncate=1 (the default), this trap represents a warning, recovery continues with error messages. If your application connected with LogAutoTruncate=0, recovery fails with error messages.

Example

A typical TimesTen trap may supply the following information:

Enterprise Specific Trap (ttDSGoingInvalidTrap) Uptime: 4:34:16
enterprises.timesten.ttSystem.ttTimeStamp = "2002-07-20 22:24:49 (GMT)"
enterprises.timesten.ttSystem.ttPid = 127
enterprises.timesten.ttSystem.ttUid = "SYSTEM"
enterprises.timesten.ttSystem.ttVersion = "@(#) TimesTen Revision: 11.2.2.0.0
Date: 2008/07/07 18:24:10, instance giraffe"
enterprises.timesten.ttMsg, ttMesg "Data store going Invalid (from master daemon)"
enterprises.timesten.ttDataStore.ttDSName = "tptbmdata1122"
enterprises.timesten.ttDataStore.ttDSShmKey = "DBI39775920.0.SHM.12"
enterprises.timesten.ttDataStore.ttDSNConn = 2

This trap was generated from a TimesTen daemon running on a Windows system. The Uptime field, which is required by SNMP, lists the elapsed time since the start of the process which generated this trap. In this case, the process ttsrv1122.exe has been running for 4 hours, 34 minutes, and 16 seconds.

This specific trap is for the Database going invalid event. So additionally, it reports the database name, shared memory key of the database and the number of current connections to the database.

Index

D  E  F  M  O  S  T  W 

D

data types

SNMP, 3.2

database

out of space, 3.3

diagnostics

SNMP traps, 3

E

environment variables

TMP, 1.5

TMPDIR, 1.5

TT_SNMP_INI, 3.6

errors

list of, 1.4

retrieving, 1.1

symbolic names, 1.1

event log

server entries, 2

F

files

snmp.ini, 3.6

tt_errCode.h, 1.4

M

Management Information Base (MIB), 3.8

O

OCI

error reporting, 1.2

OID, 3.8

out of space

SNMP trap, 3.3

out of space messages

trapping, 3.3

S

server

event log entries, 2

SNMP

MIB, 3.8

OID, 3.8

SNMP traps

data types, 3.2

described, 3

events, 3.1

names of, 3.10

out of space messages, 3.3

receiving, 3.5

severity levels, 3.10

truncation on overflow, 3.7

snmp.ini file, 3.6

SQLError function, 1.1, 1.1

SQLException, 1.1

SQLGetDialogRec function, 1.1

T

TMP environment variable, 1.5

TMPDIR environment variable, 1.5

truncation

SNMP traps, 3.7

tt_errCode.h, 1.4

TT_SNMP_INI, 3.6

ttAssertFailTrap, 3.10

ttAsyncMVFailed, 3.10

ttCacheAgentDiedTrap, 3.10

ttCacheAgentFailoverTrap, 3.10

ttCacheAutoRefFailedTrap, 3.10

ttCacheAutorefreshDsMarkedDeadTrap, 3.10

ttCacheAutorefreshLogSpaceDeFragDetectedTrap, 3.10

ttCacheAwtRtReadFailedTrap, 3.10

ttCacheAwtRtUpdateFailedTrap, 3.10

ttCacheCgNotAutorefreshedTrap, 3.10

ttCacheLowOracleTblSpace, 3.10

ttCacheRecoveryAutorefreshTrap, 3.10

ttCacheValidationAbortedTrap, 3.10

ttCacheValidationErrorTrap, 3.10

ttCacheValidationWarningTrap, 3.10

ttDaemonOutOfMemoryTrap, 3.10

ttDSCkptFailedTrap, 3.10

ttDSDataCorruptionTrap, 3.10

ttDSGoingInvalidTrap, 3.10

ttDSThreadCreateFailedTrap, 3.10

ttFileWriteErrorTrap, 3.10

ttMainDaemonDiedTrap, 3.10

ttMainDaemonExitingTrap, 3.10

ttMainDaemonReadyTrap, 3.10

ttMsgLogOpenFailedTrap, 3.10

ttPartitionSpaceExhaustedTrap, 3.10

ttPartitionSpaceStateTrap, 3.10

ttQueryThresholdWarnTrap, 3.10

ttRepAgentClockSkewTrap, 3.10

ttRepAgentDiedTrap, 3.10

ttRepAgentExitingTrap, 3.10

ttRepAgentStartingTrap, 3.10

ttRepAgentStateChange, 3.10

ttRepCatchupStartTrap, 3.10

ttRepCatchupStopTrap, 3.10

ttRepConflictReportStartingTrap, 3.10

ttRepConflictReportStoppingTrap, 3.10

ttRepReturnReceiptTransitionTrap, 3.10

ttRepSubscriberFailedTrap, 3.10

ttRepSubscriberTCPConnectFailedTrap, 3.10

ttRepUpdateFailedTrap, 3.10

ttUnexpectedEndOfLogTrap, 3.10

W

warnings

list of, 1.4

retrieving, 1.1

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2015, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.