Declarative rule and capture table condition causing issue

Question

Hi
I have one table which is replicating all the commands except delete and truncate. Also I do have declarative rule which rename the schema from source to target.
When I perform insert operation, it replicates. When i perform delete operation it also captures. but it shouldn't do because we have capture rule not to replicate the delete command.
When I perform truncate, which is not capturing since the condition fulfilled.
I used step_number=0 for declarative rule to rename the schema from source to target while capturing the changes.
Is there any way to override the rules or change the order while capturing the changes?
please do share your thoughts and help me to resolve the situation.
Thanks
Bala

Answer 1

let me explain about my situation.
Table rule defined as below
BEGIN
DBMS_STREAMS_ADM.ADD_TABLE_RULES(
table_name => 'HR.ACCOUNT',
streams_type => 'CAPTURE',
streams_name => 'CAPTURE_TO_&destsid',
queue_name => '&source_strmadmin_user..&sourcesid._TO_&destsid',
include_dml => true,
include_ddl => false,
and_condition => ':lcr.get_command_type() != ''DELETE''',
include_tagged_lcr => false,
source_database => '&source_tns',
inclusion_rule => true);
END;
DML rule for rename schema as below
SET SERVEROUTPUT ON
DECLARE
v_dml_rule VARCHAR2(80);
v_ddl_rule VARCHAR2(80);
BEGIN
DBMS_STREAMS_ADM.ADD_TABLE_RULES(
table_name => 'HR.ACCOUNT',
streams_type => 'CAPTURE',
streams_name => 'CAPTURE_TO_&destsid',
queue_name => '&source_strmadmin_user..&sourcesid._TO_&destsid',
include_dml => true,
include_ddl => false,
include_tagged_lcr => false,
source_database => 'HRDEMO.TESTDOMAIN.COM',
dml_rule_name => v_dml_rule,
ddl_rule_name => v_ddl_rule,
inclusion_rule => true);
DBMS_OUTPUT.PUT_LINE('Capture DML Rule for HR.ACCOUNT => ' || v_dml_rule);
DBMS_STREAMS_ADM.RENAME_SCHEMA(
rule_name => v_dml_rule,
from_schema_name => 'HR',
to_schema_name => 'HR_REPORT',
step_number => 0,
operation => 'ADD');
END;
Whenever insert/update happens in HR.ACCOUNT table, it captures and replicate the changes. It shoudln't capture the delete changes and but it does capture. How to modify or override the delete capture situation.
Is there any way to change the transaformation number, i tried with step_number 0 to 5, it still captures delete changes? How do we avoid delete capture in source database?
Please help.
Thanks
Bala