Oracle TimesTen In-Memory Databaseエラー・メッセージおよびSNMPトラップ

エラー8000 - 8999


No primary or unique
index on non-nullable
column found for
replicated table
<owner>.<table_name> 
Attempt to read invalid
LSN log record 
Cannot drop replicated
table, index, or sequence 
Update older than
TimeStamp of existing row 
Column
<owner>.<table>.<column>
cannot be used for
replication timestamp
checking if in an index
or added by ALTER TABLE;
and must be binary(8)
with NULL values allowed 
Invalid update rule for
timestamp-based conflict
checking 
Application must set
timestamp column with
'UPDATE BY USER' 
Cannot change aging
attributes or add/drop
aging policy of
replicated tables while
replication Agent is
running 
Transaction Log API
Buffer size too small or
too large 
Unable to attach to XLA
segment 
Unable to re-configure
active XLA segment 
Table with given ID not
found 
Attempt to specify
illegal version 
No replication buffer
configured 
Foreign table has
<number> columns while
local table has <number>
columns 
Foreign table indexed on
different columns 
Foreign and local table
differ on column <type>
type 
Inconsistent row in
update description 
System table ID invalid 
Operation not permitted
on non-shared data store 
Table row does not have
expected value 
Illegal XLA record type 
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 
Network load of data
store not allowed because
connection was reset 
Network load of data
store timed out 
Persistent transaction
log API bookmark already
in use 
Persistent transaction
log API log sequence
number is invalid 
Stale post handle 
Invalid post handle 
Record cannot be
expressed in SQL 
Persistent XLA requires
disk based logging 
Parameter <parameter>
value not in valid range 
Table definition of
record differs from the
table definition in the
data store 
Operation not permitted
on system table 
Attempt to drop
replication timestamp
column from table
<table_name> 
No free slots in
replCTNArr 
Invalid replCTNArr slot 
ReplCTNArr slot is not
allocated 
8043 
8044 
The input old value row
does not match the data
store row 
Connection is currently
dedicated to XLA
exclusively 
Commit ticket number will
wrap around 
The alter table operation
on a replicated table
needs to be in a
transaction of its own 
The alter table operation
on a replicated table
cannot be in a two safe
by request transaction 
Cannot commit transaction
that involves commit to
Oracle and TWOSAFE
replication handling 
Temporary tables cannot
be defined in a
replication scheme 
All DDLs on a replicated
table need to be in a
transaction of their own 
Cannot specify
replication timestamp
column on a cached table 
Operation not permitted
when the connection
attribute ForceConnect is
set to 1 
Local store not in ACTIVE
state 
Local store not
completely quiesced 
Table is already
subscribed 
Table is not subscribed 
Cannot alter subscription 
Inconsistency detected in
the COLUMN_HISTORY system
table 
Cannot drop a table or
view that is subscribed
by an XLA bookmark. 
Operation only supported
when the character set of
the data store in which
the record is generated
matches that of the
connected store 
The specified XLA
bookmark does not exist 
8095 
Alter table not permitted
when ttRepTransmitSet(0)
has been invoked on the
connection 
Error getting parent
table during autorefresh
bookmark lookup 
This built-in is not
permitted in an active
standby pair scheme 
2-safe operation not
permitted with AutoCommit
= 1. 
Invalid parameter value
passed in 
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. 
STORE <store_name>
specified more than once 
<attribute> specified
more than once or already
defined for STORE
<store_name> 
ALTER or DROP ELEMENT for
<element> following DROP 
STORE <store_name> does
not have a MASTER,
PROPAGATOR, or SUBSCRIBER
role for any ELEMENT 
STORE <store_name>
specified as both owner
and SUBSCRIBER for
replication ELEMENT
<element> 
Cannot specify both
ELEMENT DATASTORE and
ELEMENT TABLE or SEQUENCE
since the former already
covers all objects in the
data store 
For TRANSMIT NONDURABLE,
must use the ELEMENT
<element_name> DATASTORE
clause 
Element <element_name>
will not have any
subscribers 
Connection not permitted.
This store requires
Master Catchup. 
Connection not permitted.
Master Catchup in
progress. 
Operation not permitted.
Master Catchup not
complete. 
Operation not permitted
since replication DDL was
performed in the
transaction. Please
commit/rollback the
transaction. 
Duplicate not permitted.
Reason <reason>.
Duplicate is only
permitted from the ACTIVE
store to the STANDBY
store, from the STANDBY
store to a SUBSCRIBER, or
from the ACTIVE store to
a SUBSCRIBER if the
STANDBY store has failed. 
Column <column_name> of
table
<owner>.<table_name> is
longer than the maximum
column size of <num>
bytes when used with
replication. 
Set name operation
skipped as the new name
for the element
(<element_name>) matches
the current name. 
The TRANSMIT NONDURABLE
clause can only be used
with a DATASTORE element 
localhost, 127.0.0.1 or
::1 cannot be used as a
host identifier. 
The replication scheme
cannot begin with '_' 
An ACTIVE STANDBY PAIR
scheme does not exist 
Store DSN has been
specified as an ACTIVE
STANDBY PAIR node and a
SUBSCRIBER 
The store cannot be
dropped from the ACTIVE
STANDBY PAIR scheme
because it is a master
node 
An ACTIVE STANDBY PAIR
scheme already exists and
must be the only
replication scheme for
the store. 
Cannot create ACTIVE
STANDBY PAIR scheme
because another
replication scheme
already exists. 
Store DSN is already in
the ACTIVE STANDBY PAIR
scheme. 
Store DSN: The
"attribute_name"
attribute cannot be set
for DSN in an ACTIVE
STANDBY PAIR scheme. 
CREATE ACTIVE STANDBY
PAIR must only be run on
one of the MASTER nodes. 
Table owner.name is
already part of the
replication scheme, or is
in the process of being
included 
{INCLUDE|EXCLUDE}
element_name cannot be
used on TABLE element
element_name. The
operation is for
DATASTORE level elements
only 
You cannot
{include|exclude} table
owner.name because it is
part of a cache group.
Use {INCLUDE|EXCLUDE}
CACHE GROUP instead. 
Store DSN is not a
MASTER for any element. 
Object_type owner.name
is not part of DATASTORE
element element_name, or
is in the process of
being excluded 
All tables or cache
groups cannot be excluded
from element
element_name.  Use DROP
ELEMENT instead. 
Cannot exclude
<Object_type>
<owner.name> because it
is not in the Active
Standby scheme. 
All tables or cache
groups cannot be excluded
from the ACTIVE STANDBY
PAIR scheme 
The specified peer store
is not in the standby
state 
Scheme does not exist or
inconsistency detected in
the local ACTIVE STANDBY
PAIR scheme 
Local store not eligible
to be set to the active
state 
Error checking on store
header attributes 
The standby can only be
duplicated from the
active 
Duplicate only allowed
from a standby store or
from an active when the
standby has failed 
The local store needs to
be in the active state
for this operation. 
There can be only one
INCLUDE or EXCLUDE clause
for <object_type>. 
INCLUDE and EXCLUDE can
only be used on DATASTORE
level elements. 
Host name exceeds limit
of <num> characters 
Data store name exceeds
limit of <max_num>
characters 
This change is not
allowed while the
replication agent for
data store
<data_store_name> is
running. Please stop the
replication agent to
perform this change. 
<owner>.<name>'s
replication role
disallows the requested
operation 
No ODBC type for column
<owner>.<name>.<column> 
Store <store_name>
already owns (is MASTER
or PROPAGATOR of)
specified  ELEMENT(s) 
REPLICATION scheme
<owner>.<name> already
exists 
ELEMENT <element_name>
already has SUBSCRIBER
<subscriber_name> 
Internal error:  Column
<column_name> for ELEMENT
<element_name> already
defined for SUBSCRIBER
<subscriber_name> 
No elements
<element_name> found for
REPLICATION
<owner>.<name> 
Failed to retrieve LSN
data for initializing
PEER 
No SUBSCRIBER PEER
information found for
REPLICATION
<owner>.<name> for MASTER
or PROPAGATOR store
<store_name> 
REPLICATION
<owner>.<name> not found 
No STORE <store_name>
found for REPLICATION
<owner>.<name> 
No subscriptions found
for ELEMENT
<element_name> in
REPLICATION
<owner>.<name> 
Failed to retrieve table
or column descriptor for
table <owner>.<name> 
Replication schema is
inconsistent 
Log not writeable or
transaction not initiated
by system 
Cannot determine system
table attributes (e.g.
REPACCESS) for <table>
from replication role 
Cannot set system table
attributes (e.g.
REPACCESS) for <table>
from replication role 
Store
<transmitting_store> ON
<ransmitting_host>
already transmits  to
store <receiving_store>
ON <receiving_host>; at
most one path allowed
from one store to another 
Receipt or commit
acknowledgement not
returned in the specified
timeout interval 
Illegal to replicate a
system table <system_
table_name> 
The store <store_name> ON
<host_name_1> is already
specified with an
equivalent host name as
<store_name> on
<host_name_2> 
Replication may not be
configured while XA
transactions are active 
<attribute> specified
more than once 
Report file name
<report_name> cannot be
resolved 
Conflict checking
configuration conflict
between elements
<element_name> and
<element_name> with the
same underlying table 
Executing store
(<store_name>) not
permitted to
<operation_name> 
Cannot set a subscriber
to state code
<code_number> 
Cannot create dupicate
store: store already
exists 
Full versus partial
replication conflict with
an existing replication
scheme on data store
<data_store_name> 
Cannot create table or
alter replication because
data store
<data_store_name> is
covered by a full
datastore replication
scheme 
Cannot configure conflict
checking on DATASTORE
element 
Cannot alter element
because it is owned and
managed by the system 
Attempt to configure
replication_type
replication for a store
with no permanent objects 
Attempt to exceed limit
for return receipt
receivers 
Replication agent not
responding to Return
Receipt transactions 
A Return receipt
transaction has not been
executed on this
connection 
Transaction handle not
valid 
Transaction token
subscriber information
not available 
8190 
8191 
8192 
8193 
8194 
8195 
8196 
8197 
8198 
8199 
Attempt to drop all
columns in table 
Column is part of the
table's primary key 
Column is part of a
foreign key 
Attempt to drop indexed
column 
Columns have been added
to table too many times 
Invalid parameter value
STANDBY passed in. 
The command failed. 
Table reference of
<table_name> is ambiguous 
Table <table_name> is not
a member of the cache
group 
Multiple parents defined
for table <table_name> 
A primary constraint is
not defined for table
<table_name> 
Cache source <cache_name>
is not supported 
Invalid duration value 
Table <table_name> is
both read only and
propagated 
No parent table found 
Multiple parent tables
found 
A referenced primary key
is not found in the
associated parent table 
Cache group <cache_name>
already exists 
Table <table_name> is
read only 
Column <column_name> is
read only 
Cache group <cache_name>
not found 
Cannot drop cache group
table <table_name>;
pleaes use DROP CACHE
GROUP instead 
Memory threshold value
must be between 0 and 100 
Aging interval value must
be greater than zero 
Cache groups are not
supported on this
platform 
Oracle PassThrough not
supported on this
platform. PassThrough
value must be set to 0 
PassThrough value must be
between 0 and 3 
PassThrough command is no
longer valid. One
possible cause is
creation of a new table
on the TimesTen data
store 
Number of WITH ID keys
values does not match the
primary key columns for
cache group <cache_name> 
Invalid commit value 
8237 
8239 
8240 
8242 
8243 
8244 
8247 
Cache group
<cache_group_name> is not
currently being
autorefreshed 
Cache agent is shutting
down autorefresh for
cache group
<cache_group_name>.
Please try again 
Table <table_name> is
both read only and not
propagated 
Table <table_name> cannot
have same name as an
existing cache group 
Flush fails; all tables
are either propagated or
read only 
Attempt to bi-
directionally propagate
multiple copies of cache
group <cache_group> 
Illegal subquery used in
create cache group table
WHERE clause 
Parameters are not
supported in Oracle WHERE
clauses 
WHERE clause does not
match 
Join predicate does not
match 
Cache groups operations
may not be performed
while XA transactions are
alive 
A READONLY or
WRITETHROUGH cache group
can only replicate to a
cache group of the same
type 
If a replicating cache
group has AUTOREFRESH
specified than the remote
cache group must also
specify AUTOREFRESH 
Transaction commit/
rollback succeeded on
Oracle but failed on
TimesTen 
8265 
Asynchronous or
Synchronous Writethrough
cache group cannot have a
WHERE clause 
Table level READONLY/NOT
PROPAGATE/PROPAGATE flags
are not allowed in a
System Managed cache
group 
Manual LOAD/UNLOAD/
REFRESH/FLUSH operations
are not allowed on cache
group <cache_name>
because it is system
managed 
The REQUIRED clause is
not supported 
At least one of the local
or remote cache groups
must set autorefresh
STATE to OFF or PAUSED 
If a replicating cache
group has both
AUTOREFRESH and PROPAGATE
then the remote cache
group must set
autorefresh STATE to OFF 
Manual LOAD/UNLOAD/
REFRESH/FLUSH operations
are not allowed on cache
group <cache_group_name>
because it uses
AUTOREFRESH 
If a cache group on the
receiver has AUTOREFRESH
specified then the
corresponding cache group
on the transmitter must
also specify AUTOREFRESH 
Cache groups with
AUTOREFRESH and PROPAGATE
can only be replicated if
both the transmitter and
receiver cache groups
have autorefresh STATE
set to OFF 
If a transmitting cache
group has AUTOREFRESH and
the receiving cache group
has PROPAGATE then
transmitting cache group
must also have PROPAGATE 
The cache group where
clause contains a
subquery.  Changes of the
subquery result may not
be tracked by INCREMENTAL
AUTOREFRESH 
Autorefresh interval
should be at least <num>
milliseconds 
Replication not allowed
from a non-cache group
table to a READONLY cache
group table 
To use NCHAR/NVARCHAR
values through Cache
Connect, Oracle Database
national character set
must be AL16UTF16 
TimesTen and Oracle
database character sets
do not match.  TimesTen:
<database_character_set>,
Oracle:
<database_character_set> 
The session parameter
<parameter> cannot be
altered through a
PassThrough statement 
8298 
8299 