Here’s a good reason to always use the latest version.
Oracle GoldenGate – Version 126.96.36.199.2 to 188.8.131.52.9 [Release 12.1]
Information in this document applies to any platform.
We are trying to exclude the REPLICAT user in OGG 12.1.2 capturing from Oracle 184.108.40.206 bi-directional. But using EXTRACT TRANLOGOPTIONS EXCLUDEUSER to exclude a user in one of the PDBs:
TRANLOGOPTIONS EXCLUDEUSER ZEPP01.ZE_GG
EXTRACT is returning the message:
2015-03-25 15:44:27 ERROR OGG-00303 Could not find USER_ID corresponding to USERNAME ‘ZEPP01.ZE_GG’.
When using Integrated EXTRACT, EXCLUDEUSER is currently not supported in OGG V12.1.2. We have a enhancement request tracked via Bug 21891811 – Support EXCLUDEUSER in Integrated Extract (IE) for DDL records which has been implementd in OGG v220.127.116.11.
For excluding users in a 12c multitenant DB, OGG v12.1.2 has a new EXTRACT param TRANLOGOPTIONS EXCLUDETAG <nn>. This is typically used to exclude the REPLICAT user in bi-directional configurations.
Changes made by Integrated REP are tagged by default in redo as 00. So adding the EXTRACT param TRANLOGOPTIONS EXCLUDETAG 00
Would exclude those operations.
The tag can also be explicitly set in REPLICAT using:
DBOPTIONS SETTAG 0935
Then in EXTRACT param:
TRANLOGOPTIONS EXCLUDETAG 0935
With OGG v18.104.22.168+, you can use the earlier option of TRANLOGOPTIONS EXCLUDEUSER ZEPP01.ZE_GG
(2016, October 18). Retrieved October 30, 2016, from https://support.oracle.com/epmos/faces/DocContentDisplay?id=2008420.1