CREATING A NEGATIVE RULE SET TO FILTER OUT UNWANTED SPECIFIC UPDATE DML OPERATION IN A UNIDIRCTIONAL STREAMS REPLICATION ENVIRONMENT
(Doc ID 1457500.1)
Last updated on FEBRUARY 08, 2022
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.5 to 188.8.131.52 [Release 10.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
This sample demonstrates how to filter out transactions on a table based on few columns value condition in update DML operation in an existing one-way Streams replication environment. As per current documentation of Oracle it is possible to weed out transactions based on type of DML (Inserts/Updates/Deletes) operation using a negative rule in this situation. However, this paper and the example test case provided has attempted to prevent unwanted propagation of transactions based on a condition column has been updated in its value or the value in a column has not changed during an update DML operation ? This example illustrates how the creation of negative rule can help in reducing transactional load from source to target database in one-way replication.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document