eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

DBA Data [Home] [Help] [Dependency Information]

VIEW: SYS.DBA_XSTREAM_RULES

Object Details

Object Name:	DBA_XSTREAM_RULES
Object Type:	VIEW
Owner:	SYS
Subobject Name:
Status:	VALID

Details about the XStream server rules

[View Source]

Columns

Name	Datatype	Length	Mandatory	Comments
STREAMS_NAME	VARCHAR2	(128)		Name of the Streams process
STREAMS_TYPE	VARCHAR2	(12)		Type of the Streams process: CAPTURE or APPLY
STREAMS_RULE_TYPE	VARCHAR2	(9)		For global, schema or table rules, type of rule: TABLE, SCHEMA or GLOBAL
RULE_SET_OWNER	VARCHAR2	(128)		Owner of the rule set
RULE_SET_NAME	VARCHAR2	(128)		Name of the rule set
RULE_SET_TYPE	CHAR	(8)		Type of the rule set: POSITIVE or NEGATIVE
RULE_OWNER	VARCHAR2	(128)	Yes	Owner of the rule
RULE_NAME	VARCHAR2	(128)	Yes	Name of the rule
RULE_TYPE	VARCHAR2	(9)		For global, schema or table rules, type of rule: DML, DDL or PROCEDURE
RULE_CONDITION	CLOB	(4000)		Current rule condition
SCHEMA_NAME	VARCHAR2	(128)		For table and schema rules, the schema name
OBJECT_NAME	VARCHAR2	(128)		For table rules, the table name
INCLUDE_TAGGED_LCR	VARCHAR2	(3)		For global, schema or table rules, whether or not to include tagged LCRs
SUBSETTING_OPERATION	VARCHAR2	(6)		For subset rules, the type of operation: INSERT, UPDATE, or DELETE
DML_CONDITION	VARCHAR2	(4000)		For subset rules, the row subsetting condition
SOURCE_DATABASE	VARCHAR2	(128)		For global, schema or table rules, the name of the database where the LCRs originated
ORIGINAL_RULE_CONDITION	VARCHAR2	(4000)		For rules created by Streams administrative APIs, the original rule condition when the rule was created
SAME_RULE_CONDITION	VARCHAR2	(3)		For rules created by Streams administrative APIs, whether or not the current rule condition is the same as the original rule condition
SOURCE_ROOT_NAME	VARCHAR2	(128)		Root Database where the transactions originated
SOURCE_CONTAINER_NAME	VARCHAR2	(30)		The short container name of the database where the LCRs originated

Query Text

Cut, paste (and edit) the following text to query this object:


SELECT STREAMS_NAME
,      STREAMS_TYPE
,      STREAMS_RULE_TYPE
,      RULE_SET_OWNER
,      RULE_SET_NAME
,      RULE_SET_TYPE
,      RULE_OWNER
,      RULE_NAME
,      RULE_TYPE
,      RULE_CONDITION
,      SCHEMA_NAME
,      OBJECT_NAME
,      INCLUDE_TAGGED_LCR
,      SUBSETTING_OPERATION
,      DML_CONDITION
,      SOURCE_DATABASE
,      ORIGINAL_RULE_CONDITION
,      SAME_RULE_CONDITION
,      SOURCE_ROOT_NAME
,      SOURCE_CONTAINER_NAME
FROM SYS.DBA_XSTREAM_RULES;

Dependencies

[top of page]

SYS.DBA_XSTREAM_RULES references the following:

SYS: DBA_APPLY; DBA_CAPTURE; DBMS_LOB - show dependent code; DBMS_LOGREP_UTIL - show dependent code; GET_MAX_CHECKPOINT; REPL$_DBNAME_MAPPING; _DBA_STREAMS_RULES_H2

SYS.DBA_XSTREAM_RULES is referenced by following:

PUBLIC: DBA_XSTREAM_RULES
SYS: ALL_XSTREAM_RULES; DBA_STREAMS_TRANSFORMATIONS; DBA_XSTREAM_TRANSFORMATIONS; DBMS_APPLY_ADM - show dependent code; DBMS_XSTREAM_ADM_UTL - show dependent code