Discussions
Categories
- 385.5K All Categories
- 4.9K Data
- 2.5K Big Data Appliance
- 2.4K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
Golden Gate Filter condition issue

Golden Gate filter condition on a new source table is checking the previous txn, where as If I use the existing table, it is properly checking the filter on the current txn, very weird situation/ something got enabled ?
example:
Source table -- TABLE_1 (newly created) fields - Field_1, FIeld_2
txn - 1 : values(A,100)
txn -2 : values (B,200)
MAp - Filter ( streq(field_1,'A'))
Ideally txn 1-> should turn out to be true and should replicat, but that is not happening instead filter condition taking previous txn but inserting current values..
Means --> for the txn 2 it is passing the filter (it shouldn't have) and inserting current txn data.
if someone faced a similar problem with filters , please let us know what we are missing on here.
Answers
-
I have not seen this and agree that it is odd, because using the "after" image should be the default. For example, I have needed to filter on the before values in the past. To do that I've added the GETUPDATEBEFORES parameter to the extract (you may want to check if this parameter or something similar has snuck in somewhere) and then I've needed to explicitly notate that I want the before image... something like this: FILTER(@STREQ(@BEFORE(field_1),'A')). To prove your observation, you could try FILTER(@STREQ(@AFTER(field_1),'A')). If that works, then you know for sure that your filter is operating on the before image by default. Oracle support should be able to tell you why that is.