1 Warnings and Errors

400

Data store header fails
basic sanity test

402

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

403

Attempt to read from
checkpoint truncated

404

Corrupted block header

406

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

407

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

408

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

409

Invalid checkpoint LSN

411

OS-detected error error
while destroying directory
directory

412

Bad file-open mode

413

Bad file-exists mode

414

Bad file-missing mode

415

Incompatible file-open
modes

416

Block merge operation 
terminated due to high 
contention

420

Operation is not permitted
over client-server
connections

421

Invalid file handle (may
have been closed by
application)

422

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

423

Log directory in NFS is 
not supported on this
platform

600

Checkpoint not done due to
transaction commit/rollback
failure

601

Checkpoint failure

602

Transaction already has a 
pending fuzzy checkpoint 
request

603

Transaction already has a 
pending checkpoint request

604

Log missing record for 
checkpoint file (lsn 
LSN_number).

605

Checkpoint Log record 
number.number) 
not present

606

Checkpoint cannot proceed 
because another checkpoint 
or backup is in progress

607

Backup cannot proceed 
because another checkpoint 
or backup is in progress

609

Data store failed validity 
check

610

End-checkpoint log record 
not found

611

Backup process died

622

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

623

User user_name does not 
have group permission to 
create data store

629

No permission to access 
data store files

649

Log file file_name has 
been purged

650

Invalid backup type

651

Backup path is not enabled 
for incremental backup

652

Backup directory does not 
exist

654

Too many incremental-enabled 
backup directories

657

Backup path exceeds maximum 
length of number 
characters

658

Backup point is behind 
backup's log hold

659

Backup is out of date

660

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

661

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

662

Data store file file_name 
reflects unfinished restore 
operation.

664

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

665

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

666

ReplicationApplyOrdering 
cannot be 0 if 
ReplicationParallelism is 
greater than 1. 

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

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

668

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

669

Cannot change replication 
track within an active 
transaction. 

670

Batch cursors cannot be 
used because  replication 
tracks are not enabled. 
(ReplicationParallelism = 
<number> 
ReplicationApplyOrdering = 
<number>). 

700

Waiting for other 'in flux' 
threads failed

701

Marking data store 'in 
flux' failed

702

Connect failed because max 
number of connections 
exceeded

703

Subdaemon connect to data 
store failed with error 
TTerror_number

704

Connecting to a data store 
that is invalid and still 
has connected clients

706

Spawning a thread in the 
daemon failed

707

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

709

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

711

Data store creation in 
progress, try later

712

Unable to lock data store 
memory segment, error 
error_number

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

713

Attempt to connect to data 
store as user "user_name"

714

Log directory attribute 
does not match current 
value

715

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

716

Undo of dead connection
failed

717

Update of data store catalog 
entry failed

720

Permission denied while 
opening directory 
directory_name

721

No such directory: 
directory_name

722

Log flusher reports error 
error_number (error)

723

Log cursor is not open

724

Log cursor has no current 
position

725

Log cursor is 
unpositioned

726

Log cursor is at end of 
log

743

Action is not permitted

744

Additional log data may exist
after last valid log record
(lsn %" LFN_FMT ".%" LFO_FMT"
)

745

Log file %" LFN_FMT "
contains partial log block
(log file length = %" LFO_FMT
")

746

Extra log files found after
end of log (%" LFN_FMT "
files, starting with %" LFN_
FMT ")

747

Log read encountered 
incomplete log record at 
location log_record.log_number

748

Log ended unexpectedly at 
LSN number; recovery 
terminated

749

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

750

Log read encountered log 
record with incorrect LSN at 
location number -- 
remainder of log ignored

751

Log read encountered log 
record with bad length at 
location number -- 
remainder of log ignored

752

Log read encountered log 
record with bad type at 
location number - 
remainder of log ignored

754

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

755

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

756

Cannot write to log copy 
file file_name: error_details

759

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

760

Attempt to read past the 
end of the log; LSN = 
LSN_number

761

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

762

Invalid log truncation LSN 
LSN_number

763

Cannot truncate log file 
file_name. OS-detected error 
error_details

764

Cannot move away log file. 
OS-detected error error_details

765

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

766

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

767

Cannot chmod log reserve 
file. OS-detected error 
error_details

768

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

769

Log reserve file has 
invalid size value

770

Cannot open log reserve 
file.  OS-detected error: 
error_details

771

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

772

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

773

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

774

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

775

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

776

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

777

Log reserve exhausted

778

Log write failed because 
filesystem is full; 
transaction must rollback

779

Request denied; transaction 
must rollback because log 
filesystem is full

780

Log file file_name not 
found

781

Cannot sync log file. 
OS-detected error: 
error_details

782

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

783

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

784

Log record type is 
disallowed at this time

785

No log record exists at LSN 
LSN_number

786

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

787

Log file size exceeds 
maximum size of size MB 

788

Log file size less than 
minimum size of size MB.

789

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

790

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

791

Cannot communicate with 
subdaemon

792

Attempt to read from log 
file file_name truncated; 
byte_count bytes read

793

No idle subdaemons

794

Thread join failed

795

Protocol failure

796

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

797

Two threads using a single 
context

798

Daemon reports error 
error_number

799

Unable to connect to 
daemon; check daemon status

800

Too many errors - error 
buffer overflow

801

Malloc (C library) failed

802

Database space exhausted

803

Name length exceeds 30 
characters

804

Internal error: unknown 
error code error_string

805

operation_name has not 
been implemented

806

Garbage left on heap

807

Null pointer argument

808

Operation not atomic 
(failed and not undone)

809

Heap page directory 
overflow - cannot allocate 
space

810

Pointer does not reference 
the data store

812

Platform not supported 
platform

814

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

817

Internal error - TimesTen 
initialization failed

818

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

819

Data store not compatible 
with library library

820

Cannot destroy data store 
logs

821

No readable checkpoint 
files

823

Compact operation not fully 
completed 

824

Error information lost. 
Operation was at line 
number

826

Temporary data store exists 
but is unattached

829

Bad options: Cannot copy 
logging options if first 
connection

830

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

831

Cannot change mode on data 
store file, error error_text

832

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

833

Data store data_store_name 
not found

834

Data store file invalid or 
corrupted

835

Data store file file_name 
reflects unfinished 
checkpoint

836

Cannot create data store 
shared memory segment, error 
error_number

837

Cannot attach data store 
shared memory segment, error 
error_number

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

838

Cannot get data store 
shared memory segment, error 
error_number

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.

840

Cannot allocate space 
byte_count for non-shared 
data store

/usr/bin/ulimit -d n

This command is built in some shells, in which case the shell may take precedence.

For csh and tcsh:

limit datasize n 

For bash:

ulimit -d n 

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

ulimit -d n 
# this is kbytes

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

841

Cannot detach data store 
shared memory segment, error 
error_number

842

Invalid data store 
identifier

843

query/feature is not 
supported

844

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

845

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

846

Data store connection 
invalid or not current

847

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

848

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

849

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

850

Application has existing 
connection to data store

851

Cannot destroy data store 
file

852

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

854

Data store data_store_name 
already exists

855

Top level heap not defined

857

Invalid flags for heap 
creation

860

Invalid savepoint

862

Number of active 
transactions exceeds the 
maximum

863

Operation requires an 
active transaction

In non-LOB contexts, this is an internal error. Contact TimesTen Technical Support in this case.

864

Operation prohibited with 
an active transaction.

865

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

867

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

868

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

870

Cannot close data store 
shared memory segment, error 
error_number

871

Column column_name cannot 
be set to null

872

Length of inline columns 
(value) exceeds limit 
maximum_value

875

Invalid or missing column 
number in column descriptor

876

Overlapping columns in 
column descriptor

877

Misaligned columns in 
column descriptor

878

Invalid column number

879

Table table_name has 
existing primary index

880

Cannot create index; table 
has maximum of 500 indexes

881

Hash key and primary key 
columns must be identical

882

Primary index must be unique

883

Index has open cursors

884

Invalid hash index

885

Invalid T-tree index

886

Index operation unsupported

887

Table has no primary index

888

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

889

Number of log files 
exceeded the maximum

890

Log file name too long

891

Log file file_name already 
exists

892

Cannot create log file. 
OS-detected error: 
error_details

893

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

894

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

895

Cannot close log file. 
OS-detected error: 
error_number

896

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

897

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

898

Log record exceeds maximum 
size of log file

899

Log buffer size exceeds 
maximum size of 
maximum_size MB

If the problem persists, contact TimesTen Technical Support.

900

Cannot generate temporary 
file name

901

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

902

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

903

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

904

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

905

Invalid index identifier

906

Cannot change mode on 
logfile file_name, error 
error_details

907

Unique constraint 
constraint violated at 
Rowid row_number

908

Key not found in table or 
index

909

Cannot update primary key 
or hash key

910

Row has already been 
deleted

911

Null or blank table name

912

Row with ID not found in 
table

913

MaxCnt exceeds limit

914

table_name is not a valid 
table name

916

Key column must be 
not-null

917

Invalid column number for key

918

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

919

Invalid comparison condition

920

Invalid default value for 
column column_name

921

Unsupported column type

922

Invalid row identifier

923

Invalid row implementation

924

Row implementation 
unsupported for operation

925

Cannot create data store 
semaphores

926

Cannot create data store 
latch error_number

927

Cannot open data store 
semaphore (number) number

928

Error in semaphore 
operation error_number

931

Data store has maximum 
number of connections

932

Invalid column name: 
string

933

Invalid SQL string

934

Invalid binary string

935

SQL statement must return a 
result

936

SQL statement may return 
multiple results

937

Invalid compiled command
 number

938

SQL statement has 
arguments

939

SQL statement has no 
arguments

940

SQL command has too many 
results

941

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

942

Imprecise numeric coercion

943

MaxTups argument must be 
positive

946

SQL command is no longer 
valid

947

Cannot generate log file 
name

948

Read log buffer size 
specified is too small or 
too large

950

Invalid format width

951

Invalid float precision

952

Null string too long - 
value will be truncated

954

SQL command has mismatched 
version number

955

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

Merge statement cannot 
update a primary key

960

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

962

Bad value for parameter

963

Internal error writing 
checkpoint log record

964

Internal error truncating 
log

965

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

966

Join string too long - join 
order not changed

967

Bad join string - join 
order not changed

968

Invalid index usage 
specification

969

Index string too long - 
default index usage will be 
used

970

Invalid cursor handle

971

Supplied buffer too small

972

Invalid data store handle

973

Invalid savepoint handle

974

Invalid format handle

975

Invalid table handle

976

Invalid index handle

977

Invalid row handle

978

Invalid command handle

979

Invalid command argument 
handle

980

Input buffer not properly 
aligned

981

Invalid cursor type (R/W)

982

String exceeds column width 
column width

983

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

984

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

985

Application cannot change 
statistics on statistics 
system tables

990

Invalid maxCnt value for table

991

Quota exceeds maximum row 
count for table

992

Number of table pages in 
use exceeds quota

993

Number of index pages in 
use exceeds quota

994

Data store connection 
terminated. Please reconnect

995

Cannot destroy data store 
shared-memory segment, error 
error_number

997

Data store path too long

998

Connections cannot be used 
across fork().

1000

Cannot set primary key columns 
to different values

in not supported.

1001

Syntax error in SQL statement 
statement

1002

Identifier identifier_name in 
SQL statement exceeds maximum 
length (length)

1004

Identifier in SQL statement is 
zero-length

1005

Identifier in SQL statement is 
all spaces

1006

Identifier statement 
contains illegal characters

1007

Illegal parameter marker name

1008

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

1017

Column number in ORDER BY 
clause must be greater than zero

1022

Constant number is outside 
representable range

1024

Referenced table table_name 
not in FROM list

1025

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

1026

Column names must contain at 
least one character

1027

Floating-point precision out 
of legal range

1032

Aggregate function cannot be 
nested

1033

Aggregate function cannot be 
specified in group by clause

1061

PRIMARY KEY syntax can only be 
used once in statement

1102

Stale table handle

1103

Error in converting sysdate to 
Timestamp

1104

Unable to obtain current date 
and time for SYSDATE

1106

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

1107

Error converting sysdate to Date

1108

Converting Oracle rowiD to 
TimesTen rowiD

1109

Error converting char to ROWID

1110

FOR UPDATE with aggregate 
function is deprecated

1111

Error in converting rowid to 
char string

1112

Error in converting char 
string to rowid

1119

Arguments/bind variables not 
allowed for data definition 
operations

1120

SQL command does not exist

1200

Invalid transaction ID was 
input

1203

This transaction needs 
rollback since rollback was 
forced

1740

Missing double quote in 
indentifier identifier_name

1742

Comment not terminated 
properly message

1756

Quoted string not properly 
terminated message

1801

Cannot create index on
expression with datatype LOB

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

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

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

Action: Specify a valid character set form.

1806

Invalid LOB locator specified

Action: Initialize the LOB locator.

1807

LOB already opened in the same 
transaction

Action: Close the LOB before attempting to re-open it.

1808

Cannot update a LOB opened in 
read-only mode

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

1809

LOB type mismatch

Action: 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

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

1813

Less data provided for writing 
than indicated

1814

Source offset is beyond the end 
of the source LOB

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

1818

Warning: Open LOBs exist at 
transaction commit time

This is a warning message. TimesTen closes the LOBs and commits the transaction.

1819

Inconsistent datatypes: expected 
datatype got datatype

Check the supported data types and conversions for the operation.

1820

Cannot create materialized view 
that includes LOB columns

Recreate the materialized view without including the LOB column.

1821

Offset or offset+amount does not 
land on character boundary

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

1822

Cannot perform operation 
operation on an unopened file or 
LOB

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

1824

Row containing the LOB value is 
not locked

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

1825

CLOB or NCLOB in multibyte 
character set not supported

1826

Illegal parameter value in OCI 
LOB function

Action: Check each parameter in the OCI LOB function call to make sure they are correct.

1829

CLOBs are not supported when 
database character set is 
TIMESTEN8

1830

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

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

1851

Operation on a passthrough LOB 
is not supported

2042

Column defined with interval 
data type is not supported

2043

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

2044

Binary data exceeds column 
width width

2206

Table table_name not found

2207

Table table_name already 
exists

2208

Column column_name does not 
exist in table

2209

Column column_name specified 
more than once

2210

Column reference of column_name 
is ambiguous

2211

Referenced column 
column_name not found

2212

Named index not found in 
table

2213

Named index already exists on 
specified table

2214

Column cannot be named ROWID

2215

Attempt to drop a primary key 
index

2216

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

2221

Duplicate column name found in 
insert list

2222

Index name is not unique

2223

Named index does not exist

2230

View view_name not valid 
input to ttSize

2231

New index index_name would 
be identical to existing index 
index_name

2232

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

2233

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

2234

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

2235

Table can have only one 
primary key

2236

Nullable column can not be 
part of a primary key

2237

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

2238

System table cannot be 
altered

2239

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

2240

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

2241

Such unique or primary key
already exists in the table

2242

Invalid value for MAXVALUES in
'COMPRESS BY DICTIONARY' clause

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.

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

1-byte compression accommodates 255 (2⁸-1) distinct values. 2-byte compression accommodates 65,535 (2¹⁶-1) distinct values. 4-byte compression accommodates 4,294,967,295 (2³²-1) distinct values.

NULL is considered a distinct value and is counted.

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

2246

Cannot change compression clause
for already defined column 
column_name

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

2248

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

2249

Duplicate column name found in 
update set list

2250

New column name `column_name' 
duplicates existing column name

2251

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

Cause: The four billion limit on occurrences of a value for a compressed column (group) has been exceeded.

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

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

2286

Attempt to define constraint 
on column that does not exist

2294

UNIQUE/PRIMARY KEY column must 
specify NOT NULL

2295

Duplicate columns in primary 
key specification

2376

Duplicate entries in FROM 
clause

2400

Number of columns columns_num 
exceeds the maximum max_num

2404

Number of primary key columns 
exceeds the maximum

2405

Number of index key columns 
columns_num exceeds the maximum 
max_num

2407

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

2414

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

2416

Number of hash key columns 
exceeds the maximum

2417

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

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, make sure to specify a default value for the NOT NULL column.

For more information about 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

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

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 about using ALTER TABLE, see "ALTER TABLE" in the Oracle TimesTen In-Memory Database SQL Reference. For more information about partitions, 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

2421

Column number exceeds length 
of select list

2430

Precision of decimal or 
numeric type is out of range

2431

Scale of decimal or numeric 
type is out of range

2432

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

2433

Invalid fixed-point number 
provided

2434

Decimal overflow

2435

Decimal value exceeds scale - 
value will be truncated

2436

Decimal divided by zero

2437

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

2438

Precision of decimal or 
numeric value is out of range

2439

Scale of decimal or numeric 
value is out of range

2440

Value outside of range 
supported by decimal or 
floating point type

2599

Overflow: Value too big for 
TimestampDiff's return type

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

2600

Integer overflow

2602

Integer divide by zero

2603

Extended precision overflow

2604

Extended precision divided by 
zero

2605

Extended precision underflow

2606

Error converting from 
character string `string' to 
date

2607

Error converting from 
character string `string' to 
time

2608

Error converting from 
character string `string' to 
timestamp

2610

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

2611

Errorconverting date to 
character string

2612

Error converting time to 
character string

2613

Error converting timestamp to 
character string

2614

Value outside of range 
supported by integral type

2616

Error converting Oracle date 
to TT_TIMESTAMP

2617

Error converting Oracle date 
to Oracle timestamp

2618

Error converting Oracle 
timestamp to TT_TIMESTAMP

2619

Error converting Oracle 
timestamp to Oracle date

2620

Error converting TT_TIMESTAMP 
to Oracle date

2621

Error converting TT_TIMESTAMP 
to Oracle timestamp

2622

Format string in string must 
be a string literal

2623

Invalid number

2705

Column column_name in select 
expression not in group by list

2706

query not in select distinct 
list

2712

Attempt to update primary key 
column(s)

2764

DISTINCT within aggregate 
function cannot reference 
expression

2765

Invalid use of aggregate 
function

2774

Invalid character following 
escape character

2775

Invalid ESCAPE clause in LIKE 
expression

2776

Both arguments of binary 
operation cannot be parameters

2777

Argument of unary operation 
cannot be parameter

2778

Cannot infer type of parameter 
from its use

2779

Value length is inconsistent 
with type length

2781

Pages value must be a positive 
value

2783

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

2784

Column column_name has no 
default value defined

2785

Column column_name has no 
unique constraint

2786

Column column_name already has 
unique constraint

2787

DateTime arithmetic error

2788

Value too big for the interval 
type

2789

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

2790

Cannot infer type of case 
expression from its use

2791

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

2792

All updated columns must 
belong to updated table

2793

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

2794

Argument argument_name is 
out of range

2795

column_name not in the select 
list of the first select

2796

ON COMMIT option is only 
supported with temporary tables

2797

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

2798

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

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

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

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

2806

Invalid NLS parameter for 
NLSSORT function sort_value

NLS_SORT=sort

For example:

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

Returns

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

2809

Invalid interval

2811

Not a group by expression

CREATE TABLE t1(c1 INT);
SELECT c1+1 FROM t1 GROUP BY c1+2;
/* incorrect */

should be

SELECT c1+1 FROM t1 GROUP BY c1+1; 
/* the expression is on the GROUP 
BY list */

or

SELECT c1+1 FROM t1 GROUP BY c1 /* 
the column is on the GROUP BY list 
*/

2812

Error converting from 
character string string to 
Oracle date

2813

Error converting from 
character string string to 
Oracle timestamp

2814

Trim character value should be 
a single character

2815

Invalid number of arguments 
for function function_name

2816

Given or computed year year 
is out of range

2817

Invalid data type type for 
argument argument_name for 
function function_name

2818

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

2819

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

2820

Invalid USERENV parameter

2821

<DateFormatModel> is not a 
valid date format 
model for date function

2822

Index type was changed

2860

Invalid zero-length parameter 
value

2861

Incorrect parameter value 
length

2862

Parameter length exceeds 
maximum

2863

Char parameter length exceeds 
maximum length

2864

Output parameter value 
truncated

2865

Output parameter buffer is too 
small

2866

Parameter value too large for 
2-byte included-length

2867

Length of number value exceeds 
maximum

2868

String contains an invalid 
hexadecimal character 

2869

String is not a valid numeric 
literal

2870

String contains an invalid 
date-time character

2871

Truncation occurred during 
conversion to date-time value

2872

Error converting to date-time 
value

2873

Invalid statement handle

2874

Statement handle for ref 
cursor is in an invalid state

2875

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

2876

Value number out of range; 
specify 0 or 1. 

2877

Output parameter conversion 
resulted in an incomplete 
character

2878

Output parameter conversion 
error (code=<code>) 

2879

Non-positive timestamps not 
allowed for function

Respecify the function using positive timestamp values.

2903

Illegal character character 

2904

Invalid element element in 
number format

2905

Invalid element element in 
date format

2906

Bad number format

2907

Bad date format

2908

Error converting decimal to 
character string

2909

Error converting numeric to 
character string

2910

Float overflow for TO_CHAR 
function

2911

Float underflow for TO_CHAR 
function

2912

Invalid Unicode escape 
"\ustring\"

2913

Invalid argument 
argument_string 
for NUMTODSINTERVAL function

2914

Invalid argument 
argument_string 
for NUMTOYMINTERVAL function

2915

Too many values in the 
subquery of the set clause

2916

Not enough values in the 
subquery of the set clause

2917

Invalid extract field for 
extract source

2918

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

2919

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

2920

Number type arithmetic overflow

2921

Number type arithmetic underflow

2922

Invalid number type value

2923

Number type value overflow

2924

Number type value underflow

2925

Overflow converting number to 
char

2926

Underflow converting number to 
char

2927

Error converting Number to 
Char

2928

Error converting Char to 
Number

2929

Error converting Number to 
Double

2930

Error converting Number to 
Float

2931

Overflow converting Number to 
TinyInt

2932

Underflow converting Number to 
TinyInt

2933

Error converting Number to 
TinyInt

2934

Overflow converting Number to 
SmallInt

2935

Underflow converting Number to 
SmallInt

2936

Error converting Number to 
SmallInt

2937

Overflow converting Number to 
Int

2938

Underflow converting Number to 
Int

2939

Error converting Number to Int

2940

Overflow converting Number to 
BigInt

2941

Underflow converting Number to 
BigInt

2942

Error converting Number to 
BigInt

2943

Error truncating a date

2944

Invalid number format model

2945

Truncation occurred during 
Number conversion

2946

Truncation occurred converting 
Number to Char

2947

Buffer too small for number to 
char conversion

2948

Bad format string `string'

2949

Error occurred during Number 
conversion

2950

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

2951

The table being merged into 
cannot be used for insert 
values

2952

Source table table_name 
cannot be updated

2953

Columns referenced in the ON 
Clause cannot be updated

2954

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

2955

Column in insert whereclause 
is cannot refer to target 
table

2956

Column in insert whereclause 
is not in source table

2957

Bad insert value

2958

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

2960

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

2961

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

2962

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

2963

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

2970

Decode syntax error: not 
enough operands

2971

Coalesce syntax error: need at 
least two operands

2972

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

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

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

The remedy is to add the missing value.

2973

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

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

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

The remedy is to add the missing value.

2974

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

2975

Number divide by zero

2976

Parallel value must be greater 
than one

2977

Only DAY lifetime unit is 
allowed with a TT_DATE column

2978

Transparent load value must be 
between 0 and 2

2979

Invalid relational operator

2980

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

2981

Non existent column column_name 
specified for time-based aging

2982

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

2983

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

2984

LRU aging does not have the 
specified attribute

2985

Cannot add aging policy to a 
materialized view table

2986

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

2987

A temporary table cannot have 
an aging policy

2988

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

2989

LRU aging policy is not 
allowed with autorefresh cache 
group

2990

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

2991

Cannot combine aging duration 
with other aging policy

2992

Cannot drop aging column

2993

Aging column cannot be 
nullable

2994

Parent parent_table of table 
child_name has different 
agining policy: 
aging_policy

2995

Child child_table of table 
parent_table has differnt 
aging policy: aging_policy

2996

Cannot start aging on table 
without aging policy

2997

Transparent load cannot be 
used with passthrough 3

2998

Named constraint not found in 
table

2999

Illegal format for rowid type

3000

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

3001

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

3003

Table/Index is in use by a 
foreign key

3004

Foreign key column type 
mismatch

3005

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

3006

System/Cached tables cannot 
be referenced by a foreign 
key

3007

Both foreign key function 
arguments are nulls

3008

Scalar subquery returned 
more than one row

3009

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

3011

Duplicate columns in foreign 
key specification

3014

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

3015

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

3016

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

3017

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

3018

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

3019

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

3020

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

3021

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

3022

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

3023

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

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 about partitions, see "ALTER TABLE" in the Oracle TimesTen In-Memory Database SQL Reference

3025

Missing ORDER BY expression in 
the window specification

3026

ORDER BY is not allowed with 
analytic aggregation with 
distinct

3027

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

3028

Invalid analytic window 
argument

3029

Invalid use of analytic 
function function_name

3030

Missing window specification 
for this function

3039

The first argument of NULLIF 
cannot be NULL literal

3040

GROUPING function only 
supported with GROUP BY

3041

Number of groupings exceed the 
maximum (2147483648)

3050

Subquery is not allowed in 
the RETURNING clause

3051

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

3052

Rownm is not allowed in the 
RETURNING clause

3053

Sequence references are not 
allowed in the RETURNING 
clause

3054

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

3055

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

3056

Aggregate functions are not 
allowed in the RETURNING 
clause

3070

Cannot create a synonym with 
same name as object 

3071

Synonym <synonym> does not 
exist 

3072

Public synonym <synonym> 
does not exist 

3073

Public synonym cannot have a 
schema name 

3074

Looping chain of synonyms 

3076

Using synonyms in this 
statement is not implemented 

3077

Cannot resolve synonym 
string to any existing 
object 

3078

Circular view definition 
encountered 

3079

Creating synonyms in schema 
string is not allowed 

3080

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

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

3096

Object object_name not 
found

3097

A object with this 
name (name) already exists

3098

User username does not 
exist.

3100

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

3101

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

3102

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

3103

Two tables cannot be outer 
joined together

3104

A predicate may reference 
only one outer-joined table

3105

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

3106

FIRST keyword cannot be used 
in subquery

3108

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

3110

Expression expression has 
no name

3111

Column name column 
specified more than once

3112

Cannot drop view table 
table_name; use DROP 
VIEW instead

3113

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

3114

Cannot alter view tables

3115

Cannot drop columns 
referenced in materialized views

3117

View SQL must be less than 
number bytes long

3118

View view_name already exists

3119

More than number views 
reference table table_name

3120

View view_name does not exist

3121

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

3123

Foreign keys on view tables 
are not allowed

3124

Cannot create a view that 
references a system table

3125

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

3128

Invalid size of column name list

3129

Invalid column name for view

3130

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

3131

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

3132

A materialized view cannot 
reference a regular view

3133

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

User Action: 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

User Action: 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

3136

Cannot truncate temp table: 
temp_table; Please use delete

3137

Cannot insert into a truncated 
table in an uncommitted 
transaction

3138

Cannot delete from a 
truncated table in an 
uncommitted transaction

3139

Cannot update from a 
truncated table in an 
uncommitted transaction

3140

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

3141

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

3143

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

3144

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

3145

view_name is not an 
Asynchronous Materialized View

3146

Column owner.name not 
found in the Materialized View 
Log

3147

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

3148

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

3149

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

3150

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

3151

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

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

3153

There is no materialized 
view log on table table_name

3154

A materialized view log 
already exists on table 
table_name

3155

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

3156

Cannot create a materialized 
view on a materialized view 
log. 

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.

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

3158

Cannot create a materialized 
view log on a system table 

3159

SELECT not allowed on 
invalid materialized view 
string

3160

REFRESH not allowed on 
invalid materialized view 
string

3200

Sequence increment by value 
cannot be 0

3201

Sequence cache has not been 
allocated

3202

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

3204

Sequence sequence_name is 
not found

3205

A table or sequence with 
this name already exists

3206

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

3207

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

3208

CURRVAL or NEXTVAL not 
allowed in where clause

3209

CURRVAL or NEXTVAL is not 
supported in views

3210

Sequence max/min limit has 
been reached.

3211

CURRVAL may not be 
referenced before NEXTVAL in 
this session

3212

Failed to get the NEXTVAL

3213

Load sequence to cache 
failed

3214

An error occurred while 
adding sequence value info to 
context

3215

An error occurred while 
cleaning up sequence cache 
during rollback

3221

Invalid statistics 
information: error_number

3222

Estimate statistics on 
schema.table_name
failed due to 
concurrent operations; 
try again. 

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

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

3300

type_name is not a valid 
type name; instead use 
type_name

3301

Type mode must be set to 
Oracle to use this feature

3304

Foreign key definition is 
not allowed for CREATE TABLE 
AS SELECT

3305

Invalid number of column 
names specified

3306

No column name specified 
when creating table with hash 
index

3307

Need to specify the datatype 
for the column

3308

May not specify column 
datatypes in this CREATE 
TABLE

3309

No column name specified 
when creating table with 
aging

3315

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

3316

Cache group definition 
mismatch among the members of 
the grid

3317

Cache group cache_group 
does not exist in grid member 
member

3318

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

3319

This operation needs the 
database to attach to the 
grid first

3320

Node ID table table_name 
is not found on Oracle

3321

Node ID table table_name 
has no row

3322

Node information table 
table_name is not found on 
Oracle

3323

Cache group definition table 
table_name is not found on 
Oracle

3324

Cache grid cannot be 
destroyed when there are 
attached members

3325

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

3326

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

3327

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

3328

Have to commit grid 
create/destroy statement 
before attaching

3329

Have to detach from grid 
before destroying a grid

3330

Grid grid_name with 
adminID ID does not exist

3331

Fail to send a message to 
member member_name

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

3333

Time out waiting for a 
response from member 
member_name

3334

Specified IP address and 
port number combination have 
been used

3336

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

3337

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

3338

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

3339

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

3340

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

3341

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

3342

Inserted key already exists 
on Oracle or remote node

3343

Key was not found in current 
owner member member_name

3344

Error creating grid threads: 
thread_names

3345

Grid platform platform_name 
and node platform 
platform_name 
are different

3346

Grid release 
release_number 
and node release 
release_number are different

3347

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

3348

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

3349

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

3350

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

3351

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

3352

Key was not found in standby 
member member_name

3353

Key is being loaded in 
remote member member_name

3354

Grid thread died before 
committing ownership change 
to Oracle

3355

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

3356

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

3357

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

3358

Failed to detach remote 
member member_name. Member 
is still alive

3359

Grid receiver thread 
received obsolete message Id

3360

Grid already exists

3361

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

3362

Node already attached to a grid

3363

Node is not attached to a grid

3364

Grid attached operation 
failed. details

3365

Failed to get root table 
primary key for transparent 
load. Reason details

3366

ttGridNameSet cannot be 
called from the standby of an 
active standby pair. Call it 
from the active instead

3369

Cannot detach from cache 
grid when there are number 
outstanding transparent load 
and/or unloading

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.

3371

Grid control table 
table_name on Oracle was 
corrupted

3372

Timed out waiting seconds 
seconds for change to be 
propagated to Oracle

3373

Cache instance does not meet 
aging requirement

3374

Member may contain stale 
global cache group table 
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.

3377

Failed to acquire grid info. 
Grid information on Oracle 
may be stale. Reason cause

3378

Cannot drop ownership table 
of global cache group. Drop 
the cache group instead. 

3380

This operation is invalid 
with ownership table table. 

3381

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

3382

Timed out waiting number 
seconds for response from 
remote nodes. 

3383

Cache group string.string 
failed ownership checking: 
string. 

3384

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

3385

Invalid char found in member 
name string string. 

3387

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

3390

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

3391

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

3392

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

3398

Mismatched cache group type 
in grid member grid_member

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

3400

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

3401

P2P error: string

3402

Cannot drop an active 
standby pair when the cache 
grid is attached. Detach the 
cache grid first.

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.

3404

Cannot drop AWT cache group 
with unpropagated deletes

3405

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

3406

Unique constraint (constraint) 
violated at Rowid <rowid> 
due to unpropagated delete

3407

Cannot allocate space to 
store ownership information 
for global cache groups 
because temporary data 
partition free space is below 
the minimum threshold of 
number bytes

3408

Global statement needs the 
database to attach to the 
grid first 

3409

Combination of global 
processing option and 
<option_name> option is not 
supported 

3410

Grid sender queue is too full 

3411

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

3412

Detach is disallowed on 
transaction with uncommitted 
grid work 

3413

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

3414

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

3415

Internal error: instance was 
found but not qualified. 

3416

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

3417

Internal error: Propagation 
thread is executing on active 
node. 

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. 

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. 

3420

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

3421

Grid Configuration was changed

User Action: 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

User Action: 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

User Action: Commit the transaction and make sure replication agent is up.

3427

Global cache group is not 
supported on Windows

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

User Action: 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

User Action: 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

1. Your database had global cache groups.

2. Grid is enabled and your database had local AWT cache groups.

4053

Internal error. error_number

4054

Internal warning: 
detailed_warning

4501

Data store cannot 
checkpoint to a network file 
system

4502

Data store cannot log to a 
network file system

4600

Argument error and error

4601

Argument error message

5002

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

5006

Defining SQL string exceeds 
maximum allowed length

5007

Cache agent error

5010

No OracleNetServiceName 
specified in DSN

5011

Oracle (OCI8) call failed

5012

Oracle login failed

5013

Operation requires cache 
connection

5014

Could not execute defining
SQL

5015

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

5016

Cache agent has too many 
existing connections

5019

Bad table name specification

5020

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

5021

Could not get meta data 
from Oracle: 
detailed_error_message

5022

Could not open output file 
for writing Oracle meta data

5025

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

5026

Cannot alter cached tables

5029

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

5030

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

5034

The operation must be 
executed within its own 
transaction

5035

A cache group may not have 
a negative number of tables

5036

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

5037

An error occurred while 
loading cache_group_name: 
detailed_warning_message

5038

Warning(s) while populating 
the cache. 
detailed_warning_message

5039

An error occurred while 
refreshing the 
cache_group_name 
detailed_error_message

5045

Cache group operations may 
not use data store level
locking

5046

Commit/rollback required 
after Cache operation 

5047

This operation is not 
allowed on cached tables

5048

Feature, feature_name, 
not supported

5050

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

5051

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

5052

Cache group name required 
with install_flag value 1

5053

Add/Drop foreign keys are 
not allowed on cached 
tables

5054

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

5058

The cache operation received 
a warning: warning_type=type,
warning_code=code, 
warning_message: message

5061

Oracle and TimesTen in 
inconsistent state. 
Invalidating the data store. 
Must refresh the 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.

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

5067

Name name is already used 
by an existing object

5068

Argument argument_name 
ignored

5069

Argument argument_name 
error_message

5070

Error compiling PL/SQL 
block. Check that 
user_name has 
privilege_type on table_name

5071

Name string reused within 
statement. Use different 
names.

5101

An error occurred while 
generating the name of the 
backend database shared 
library for database type: 
database_type

5102

Cannot load backend library 
library_name for Cache 
Connect. OS error message 
error_details.

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

• The library was not found

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

• The Oracle library bits do not match the TimesTen bits.

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

5104

Could not initialize the 
function pointers backend 
database api. Function 
function_name was not in 
the library.

5105

OCI initialization failed: 
description.

5106

Could not allocate 
handle_name handle

5107

Oracle(OCI) 
Oracle_error_id in 
OCI_call: 
Oracle_error_number

5109

Cache Connect general 
error: Oracle_operation

5110

Table does not exist in 
Oracle: table_name

5111

Could not find matching 
unique index for cache table 
table_name

5112

Cache table table_name 
contains VARCHAR column(s). 
Oracle VARCHAR comparison 
rule is different.

5113

Cache table table_name 
contains REAL/DOUBLE/ FLOAT 
column(s). Cached value may 
have a different precision.

5114

Unsupported type mapping 
for key column column_name

5115

Unsupported type mapping 
for column column_name

5116

Column column_name does not 
exist in Oracle

5117

Illegal WHERE clause for 
cache table table_name

5118

Column column_name has 
different precision/ scale 
in Oracle

5119

Column column_name has 
different nullability 
setting in Oracle

5120

No matching unique index 
with not null columns, 
unique key constraint with 
not null columns, or primary 
key constraint on table 
table_name, cache 
operations are restricted

5121

Non-standard type mapping 
for column column_name, 
cache operations are 
restricted

5123

Operation not allowed on 
restricted cache group 
cache_group

5124

Autorefresh/propagate are 
not allowed on restricted 
cache group

5125

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

5126

A system managed cache 
group cannot contain non- 
standard column type mapping

5127

Backend connection invalid. 
error_details

5128

handle_name handle is 
invalid. The Oracle 
connection may have been 
lost. Retry your 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.

5130

Error executing the 
following statement on 
Oracle: query

5131

Cannot connect to backend 
database: 
OracleNetServiceName = 
Oracle_service_name, uid = 
user_id, pwd is 
hidden,TNS_ADMIN = 
tns_admin , ORACLE_HOME= 
Oracle_home

You may also find the Oracle error number in other messages on the error stack. Check the Oracle error message documentation for the corresponding Oracle error.

5132

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

5133

Could not re-install SIGINT 
signal handler

5134

Could not determine Oracle 
server version

5142

Autorefresh is not allowed 
on cache groups with Oracle 
synonyms

5144

The cache group contains a 
Oracle materialized view, 
cache operations are 
restricted.

5146

owner.name is a public 
synonym which is not 
supported

5150

The statement handle is in 
an invalid state for the 
operation: operation_name

5151

Passthrough is not supported 
for error_condition

Cause: Attempted to passthrough an unsupported SQL statement or large output parameter values from TimesTen to Oracle.

Impact: Statement execution stopped.

User Action: Use a SQL statement that is supported for passthrough. Also, make sure that the SQL statement does not contain large output parameter values. For more information, see the description for the PassThrough attribute 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.

5153

operation is not allowed 
for this type of Oracle 
statement

5155

Wrong number of parameters

5156

Too many parameters. 
Maximum number of parameters 
allowed is maximum_number

5158

Oracle compilation error:
 error

5159

Index owner.name was 
converted to a non-unique 
index because table 
owner.name is a member of 
an autorefreshed cache group.

5160

Failed to prepare Oracle 
objects for datastore 
duplication: details

5161

Conflicting concurrent 
updates to bipropagated rows

5162

Could not register Oracle 
failover callback function

5163

Oracle failover failed with 
event event_ID. Retried 
for number minutes

5164

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

5165

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

5166

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

5167

Deprecated type mapping for 
column column_name

5168

Restricted cache groups are 
deprecated

5169

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

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.

5171

Lookup for username 
user_name failed on Oracle.

5181

Oracle column maximum byte 
length is restricted to 4000 
bytes for column column_name

5182

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

5183

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

5184

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

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

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

5186

The OCI client library in use 
does not contain required 
routines to support caching 
LOBs from Oracle.

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.

5201

Operations for Cache Agent 
are not allowed for 
temporary data stores

5202

Environment variable 
ORACLE_HOME must be set to 
perform this operation

5203

Could not find library 
library_name

5204

Environment variable PATH 
not set

5205

OCI.DLL must be in PATH to 
perform this operation

5206

Environment variable 
ORACLE_HOME must not be more 
than 256 characters long

5207

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

5208

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

5209

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

5210

Oracle unique constraint 
violation error/warning in 
OCI_function: 
Oracle_error_number

5211

Oracle out of resource 
error/warning in 
OCI_function: 
Oracle_error_number

5212

No longer connected to 
Oracle error/warning in 
OCI_function: 
Oracle_error_number

5213

Bad Oracle login 
error/ warning in 
OCI_function: 
Oracle_error_number

5214

Not connected to Oracle 
error/warning in 
OCI_function: 
Oracle_error_number

5215

Oracle resource timeout 
error/warning in 
OCI_function: 
Oracle_error_number

5216

Oracle resource busy 
error/warning in 
OCI_function: 
Oracle_error_number

5217

Oracle deadlock 
error/ warning in 
OCI_function: 
Oracle_error_number

5218

Bad parameter to Oracle 
error/warning in 
OCI_function: 
Oracle_error_number

5219

Temporary Oracle connection 
failure error/warning in 
OCI_function: 
Oracle_error_number

5220

Permanent Oracle connection 
failure error/warning in 
OCI_function: 
Oracle_error_number

5221

Oracle syntax 
error/warning in 
OCI_function: 
Oracle_error_number

5222

Oracle constraint violation 
error/warning in 
OCI_function: 
Oracle_error_number

5223

Oracle orphan violation 
error/warning in 
OCI_function: 
Oracle_error_number

5224

Oracle foreign key 
violation error/warning in 
OCI_function: 
Oracle_error_number

5225

Oracle recovery in progress 
error/warning in 
OCI_function: 
Oracle_error_number

5226

Oracle data truncation 
error/warning in 
OCI_function: 
Oracle_error_number

5227

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

5228

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

5229

An Oracle savepoint error 
occurred: error_message

5230

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

5243

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

5244

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

5245

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

5246

The Replication Agent for 
this datastore is currently 
running.

5247

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

5249

Awt Initialization Failure: 
detailed_error_number

5250

Awt Initialization Failure. 
Could not compile meta data 
SQL.

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.

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

5254

Operation failed. Could not 
find AWT cache group 
information.

5256

Could not find runtime data 
for AWT.

5257

Cache admin user and/or 
password could not be found. 
Changes via AWT cannot be 
applied without them.

5258

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

5259

Failed to store AWT runtime 
information for data store 
data_store_name on Oracle

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

5261

Failed to read AWT runtime 
information for data store 
data_store_name on Oracle

5262

Could not store the 
autorefresh bookmarks 
because the autorefresh 
state should be state but 
instead was state

5263

owner.table is not an 
autorefresh cache group

5264

Master data store state not 
active or standby. State is 
state.

5265

Internal error: error_details

5266

Cache ddl lock request 
denied because of 
time-out\Owner info: message 

5267

The operation failed 
because the data store is 
marked dead and name 
option is set to value

5268

Changing the recovery 
method to none has caused 
recovering cache groups to 
be marked dead for all data 
stores

5269

owner.name is not an 
incrementally autorefreshed 
cache group 

5275

Asynchronous writethrough 
metadata not found error 
in object: object

5276

Asynchronous writethrough 
role or state change 
occurred error in 
object: object

5277

Timeout while updating 
active standby metadata on 
Oracle error in object: 
object 

5278

Statement over 4000 bytes: 
statement

5279

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

5280

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

5281

Autorefresh of specified 
cache group is already in 
progress. 

5282

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

5283

Autorefresh did not 
complete within 24 hours 

5284

Error launching 
autorefresh, see daemon log

5285

Autorefresh failed, see 
daemon log 

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. 

5287

Unexpected status returned 
by autorefresh, see daemon 
log 

5288

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

5289

Operation failed because 
user lacks Oracle RDBMS 
privilege privilege. 
Action_statement. 

5291

The following Oracle indexes 
and constraints on table 
owner.table contain cached 
columns that do not have 
corresponding unique indexes 
on TimesTen: <list of oracle 
unique indexes or 
constraints>

In order to use Parallel AWT, all unique constraints and indexes on a cached Oracle table must also have a corresponding unique index on TimesTen.

During Replication Agent Start:

The replication agent could not be started because Parallel AWT requires that all unique constraints and indexes on a cached Oracle table must also have a corresponding unique index on TimesTen.

To resolve these errors do one of the following:

1. Create the appropriate unique indexes on the AWT table

2. Disable Parallel AWT

3. Do not cache the columns that have missing unique indexes

5292

Any unique indexes and 
constraints on Oracle tables 
that are cached in an AWT 
cache group that has enabled 
parallel propagation contain 
cached columns that do not 
have corresponding unique 
indexes on TimesTen

Do one of the following:

1. Create the appropriate unique indexes on the AWT table

2. Disable Parallel AWT

3. Do not cache the columns that have missing unique indexes

5300

Parameter bindings are not 
allowed in the select 
statement

Cause: The Oracle select query you specified for the built-in procedure or command contains parameter bindings. Parameter bindings are not supported by the ttTableSchemaFromOraQueryGet built-in, the ttLoadFromOracle built-in, and the createAndLoadfromOraQuery command.

Impact: The execution of the built-in procedure or command failed.

User Action: Remove the parameter bindings from the Oracle select query and rerun the built-in procedure or command.

For more information about the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information about the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information about 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

Cause: The TimesTen table you specified for the built-in procedure or command is part of a cache group. Loading into TimesTen cache group tables is not supported by the ttTableSchemaFromOraQueryGet built-in, the ttLoadFromOracle built-in, and the createAndLoadfromOraQuery command.

Impact: The execution of the built-in procedure or command failed.

User Action: Specify a table that is not part of a cache group and rerun the built-in procedure or command.

For more information about the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information about the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information about 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

Cause: The PassThrough attribute of the Oracle In-Memory Database Cache is set to 3.

Impact: The execution of the built-in procedure or command failed.

User Action: Do not specify a PassThrough level of 3 for the Oracle In-Memory Database Cache and rerun 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 about the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information about the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information about the createAndLoadfromOraQuery command, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.

5303

Create table statement 
generated is too long

Cause: The built-in procedure or command generated a CREATE TABLE statement that exceeds 409,600 characters, 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 run.

User Action: Modify the Oracle SQL statement to shorten the length of the generated CREATE TABLE statement and rerun 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 about the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information about the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information about 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

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 execution of the built-in procedure or command failed.

User Action: Remove or change the LOB data types to a supported type and rerun the built-in procedure or command.

For more information about the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information about the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information about 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)

Cause: The number of columns in the TimesTen table does not match the number in the Oracle 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 execution of the built-in procedure or command failed.

User Action: Examine the TimesTen table and the Oracle query to resolve the mismatch. Then rerun the built-in procedure or command.

For more information about the ttTableSchemaFromOraQueryGet built-in, see "ttTableSchemaFromOraQueryGet" in the Oracle TimesTen In-Memory Database Reference. For more information about the ttLoadFromOracle built-in, see "ttLoadFromOracle" in the Oracle TimesTen In-Memory Database Reference. For more information about the createAndLoadfromOraQuery command, see "ttIsql" in the Oracle TimesTen In-Memory Database Reference.