第三部分_GoldenGate常用参数合编.ppt

* * * * IGNOREINSERTS is default * * STATOPTIONS [REPORTFETCH | NOREPORTFETCH] -- useful for debugging fetch issue * * Replicat reads GoldenGate trail files sequentially, and processes inserts, updates and deletes that meet your criteria. GoldenGate trail files are simply queues for the Replicat. Each record header in the trail file provides information about the database change record. Replicat reads extracted data in blocks to maximize throughput. Alternatively, you can filter out the rows you do not wish to deliver, as well as perform data transformation prior to replicating the data. Replicat supports a high volume of data replication activity. As a result, network activity is block-based rather than a record-at-a-time. Database operations used to deliver the data are executed using native call. You can configure multiple REPLICAT processes for increased throughput. When replicating, REPLICAT preserves the boundaries of each transaction so that the target database has the same degree of integrity as the source. Small transactions can be grouped into larger transactions to improve performance. REPLICAT uses a checkpointing scheme so changes are processed exactly once. After a graceful stop or a failure, processing can be restarted without repetition or loss of continuity. * The MAP parameter establishes a relationship between one source and one target file (or table). Insert, update and delete records originating in the source file are replicated in the target file. With MAP, you can replicate particular subsets of data to the target file, for example, WHERE (STATE = “CA”). In addition, FILE enables the user to map certain fields or columns from the source record into the target record format (“column mapping”). You can also include a FILTER command to evaluate data provided built-in functions for more complex filtering criteria A table or file can appear in multiple maps as either source or target. For example, one might replicate a “sales” file to eithe