Using Changed Data: Simple Journalizing

Working with Changed Data Capture 7-11 ■ OdiRefreshJournalCount refreshes the number of rows to consume for a given table list or CDC set for a specified journalizing subscriber. See Appendix A, Oracle Data Integrator Tools Reference for more information on these functions.

7.3.5 Package Templates for Using Journalizing

A number of templates may be used when designing packages to use journalized data. Below are some typical templates. See Chapter 10, Working with Packages for more information on package creation. Template 1: One Simple Package Consistent Set ■ Step 1: Extend Window + Lock Subscribers ■ Step 2 to n-1: Interfaces using the journalized data ■ Step n: Unlock Subscribers + Purge Journal This package is scheduled to process all changes every minutes. This template is relevant if changes are made regularly in the journalized tables. Template 2: One Simple Package Simple Journalizing Step 1 to n: Interfaces using the journalized data This package is scheduled to process all changes every minutes. This template is relevant if changes are made regularly in the journalized tables. Template 3: Using OdiWaitForLogData Consistent Set or Simple ■ Step 1: OdiWaitForLogData. If no new log data is detected after a specified interval, end the package. ■ Step 2: Execute a scenario equivalent to the template 1 or 2, using OdiStartScen This package is scheduled regularly. Changed data will only be processed if new changes have been detected. This avoids useless processing if changes occur sporadically to the journalized tables i.e. to avoid running interfaces that would process no data. Template 4: Separate Processes Consistent Set This template dissociates the consistency window, the purge, and the changes consumption for two different subscribers in different packages. Package 1: Extend Window ■ Step 1: OdiWaitForLogData. If no new log data is detected after a specified interval, end the package. ■ Step 2: Extend Window. This package is scheduled every minute. Extend Window may be resource consuming. It is better to have this operation triggered only when new data appears. Package 2: Purge Journal at the end of week Step 1: Purge Journal This package is scheduled once every Friday. We will keep track of the journals for the entire week. Package 3: Process the Changes for Subscriber A 7-12 Oracle Fusion Middleware Developers Guide for Oracle Data Integrator ■ Step 1: Lock Subscriber A ■ Step 2 to n-1: Interfaces using the journalized data for subscriber A ■ Step n: Unlock Subscriber A This package is scheduled every minute. Such a package is used for instance to generate events in a MOM. Package 4: Process the Changes for Subscriber B ■ Step 1: Lock Subscriber B ■ Step 2 to n-1: Interfaces using the journalized data for subscriber B ■ Step n: Unlock Subscriber B This package is scheduled every day. Such a package is used for instance to load a data warehouse during the night with the changed data.