4.93 ALL_STREAMS_TABLE_RULES

ALL_STREAMS_TABLE_RULES displays information about several types of rules.

ALL_STREAMS_TABLE_RULES displays information about these types of table and subset rules:

  • Table rules created for the capture processes that enqueue the captured changes into queues accessible to the current user

  • Table rules created for the propagations that have a source queue accessible to the current user

  • Table rules created for the apply processes that dequeue events from queues accessible to the current user

  • Subset rules created for the apply processes that have a source queue accessible to the current user

This view does not contain information about rules created using the DBMS_RULE_ADM package.

Related View

DBA_STREAMS_TABLE_RULES displays information about the table rules created for all capture processes, propagations, and apply processes in the database.

Column Datatype NULL Description

STREAMS_NAME

VARCHAR2(128)

Name of the Replication process or propagation

STREAMS_TYPE

VARCHAR2(12)

Type of the Replication process or propagation:

  • CAPTURE

  • PROPAGATION

  • APPLY

  • DEQUEUE

TABLE_OWNER

VARCHAR2(128)

Table owner in the rule condition. The rule evaluates to true for a redo entry or logical change record (LCR) only if the redo entry or LCR contains this table owner.

TABLE_NAME

VARCHAR2(128)

Table name in the rule condition. The rule evaluates to true for a redo entry or logical change record (LCR) only if the redo entry or LCR contains this table name.

RULE_TYPE

VARCHAR2(7)

Type of the rule:

  • DML

  • DDL

DML_CONDITION

VARCHAR2(4000)

Row subsetting condition, if the rule is a subset rule

SUBSETTING_OPERATION

VARCHAR2(6)

DML operation for row subsetting in the rule condition, if the rule is a subset rule:

  • INSERT

  • UPDATE

  • DELETE

The rule evaluates to true for a logical change record (LCR) only if the LCR contains this command type after internal transformation.

INCLUDE_TAGGED_LCR

VARCHAR2(3)

Indicates whether a redo entry or logical change record (LCR) with a non-NULL tag is considered for capture, propagation, or apply (YES) or not (NO)

SOURCE_DATABASE

VARCHAR2(128)

Source database in the rule condition. The rule evaluates to true for a redo entry or logical change record (LCR) only if the redo entry or LCR contains this source database.

RULE_NAME

VARCHAR2(128)

NOT NULL

Name of the rule

RULE_OWNER

VARCHAR2(128)

NOT NULL

Owner of the rule

RULE_CONDITION

VARCHAR2(4000)

First 4000 bytes of the system-generated rule condition evaluated by the rules engine

See Also: