Skip Headers
Oracle® TimesTen In-Memory Database SQL Reference
Release 11.2.1

Part Number E13070-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

TTREP.REPELEMENTS

The TTREP.REPELEMENTS table describes elements in a replication scheme. In this release, the only elements recorded are tables.

Columns

Column name Type Description
REPLICATION_

NAME

TT_CHAR(31) NOT NULL Name for a replication scheme.
REPLICATION_

OWNER

TT_CHAR(31) NOT NULL The replication scheme's owner.
ELEMENT_NAME TT_CHAR(31) NOT NULL The replication name for this element, logically different from the DS_OBJ_NAME of the underlying data base object. For example, the ELEMENT_NAME for a replicated table may differ from the table name. This name must be unique in a replication scheme.
ELEMENT_TYPE TT_CHAR (1) NOT NULL The type of this replication element:

'T' – Table

'D' – Data store

'S' – Sequence

OWNED_BY_

SYSTEM

BINARY (1) NOT NULL 0x01 - Element is maintained by the system and cannot be directly referenced by SQL statements.

0x00 - Element is defined and maintained by a user.

MASTER_ID TT_BIGINT NOT NULL The TT_STORE_ID for the master or propagator of this element.
OLD_MASTER_ID TT_BIGINT NOT NULL The TT_STORE_ID for the immediately preceding MASTER for this element. -1 if none.
IS_PROPAGATOR BINARY (1) NOT NULL 0 if the MASTER_ID identifies a true MASTER store. 1 if it, in fact, identifies a -PROPAGATOR.
DS_OBJ_NAME TT_CHAR(31) NOT NULL If this replication refers to a single, underlying data base object, then this is its name. Specifically, it is the name of the replicated table if ELEMENT_TYPE = 'T'.

it is NULL if ELEMENT

_TYPE = 'D'. DS_OBJ_OWNER._DS_OBJ_NAME need not be unique in a replication scheme, but each occurrence must be associated with a distinct ELEMENT_NAME.

DS_OBJ_OWNER TT_CHAR(31) NOT NULL The owner of the replication element – if defined. NULL otherwise. This is always the owner of the table. DS_OBJ_OWNER._DS_

OBJ_NAME need not be unique in a replication scheme, but each occurrence must be associated with a distinct ELEMENT_NAME.

DS_OBJ_ID TT_INTEGER If the ELEMENT_TYPE = 'T':

Table ID - Table is in the owning (master or propagator) data store.

1- Table is in the subscriber data store.

If the ELEMENT_TYPE = 'D':

0 - Data store is a master or propagator.

1- Data store is a subscriber.

NULL - If the store has been migrated, restored or upgraded from an earlier version.

DURABLE_

TRANSMIT

BINARY (1) NOT NULL 0 - Transactions are made durable before they are transmitted (default).

1 - Transactions are not made durable before they are transmitted.

CONFLICT_CHECKS BINARY (8) NOT NULL A bit map indicating which conflict detectors are enabled. This field is either: 0x0000000000000000 (no configured conflict detector, the default) or:  0x0000000000000001 (ROW TIMESTAMP conflict detector).
TS_COLUMN_NAME TT_CHAR (31) The name of the timestamp column specified in the CheckConflicts portion of a CREATE MATERIALIZED VIEW statement. This column must be of type BINARY(8) and permit NULL values.
TS_EXCEPTION_

ACTION

TT_CHAR (1) NOT NULL The action to take upon detecting a conflict by a timestamp-based detector. The action is specified by the ON EXCEPTION clause in the CheckConflicts portion of a CREATE MATERIALIZED VIEW statement. They appear in this column as:

'\0' - action not defined

'N' - NO ACTION

'R' - rollback transaction (default)

TS_UPDATE_RULE TT_CHAR (1) NOT NULL The rule for maintaining the timestamp for a timestamp-based conflict detector:

'\0'- rule not defined

'U' - by user

'S' - by system (default)

TS_REPORT_FILE TT_VARCHAR (1000) NOT INLINE The name of the file to which the replication agent reports timestamp conflicts.

This file is specified by the REPORT TO clause in the CheckConflicts portion of a CREATE MATERIALIZED VIEW statement.

     
IS_MASTER_

PROPAGATOR

BINARY (1) NOT NULL Indicates if the store is both a master and a propagator.
EXTERNAL_DB TT_CHAR (1)  
REPORT_FORMAT TT_CHAR(1) The report format for the replication conflict file:

NULL - No report file specified, therefore no format

'S' - Standard format

'X' - XML format