...
| Note |
|---|
For filtering to work, the columns used in the conditions must always be included in the redo log. This can be achieved simply by forcing Oracle to include them for every DML operation on the table by creating a supplemental log group. Therefore when data is filtered for replication, enable supplemental logging for participating column. It is also helpful when PL/SQL is used for conflict handling. Click here to learn more about Supplemental logging and how to turn it on. |
| Note |
|---|
When target is not oracle database then avoid using inbuilt functions in filtering as same functions might not be available on target environment. |
| Note |
When using FILTER conditions with LOAD (which is used to instantiate/provision the data set at the target) note that the FILTER conditions will be invoked in this process. If this is not desired then you can add the filtering condition(s) after the baselining LOAD has occurred via the console (see bellow). |
...
In the next example we use
| Note |
|---|
When target is not oracle database then avoid using inbuilt functions in filtering as same functions might not be available on target environment. |
Disable filtering
...