Oracle Streams Samples and Best Practices

Oracle Streams enables the propagation and management of data, transactions and events in a data stream either within a database, or from one database to another. The stream routes published information to subscribed destinations. The result is a new feature that provides greater functionality and flexibility than traditional solutions for capturing and managing events, and sharing the events with other databases and applications. As users' needs change, they can simply implement a new capability of Oracle Streams, without sacrificing existing capabilities. Streams interoperates with Advanced Queuing (AQ), which supports all the standard features of message queuing systems.

Streams Messaging Sample[11-Dec-2003]
This Streams sample showcases the messaging capability of Streams and how to use Java Messaging Service (JMS) to access Streams Queue and get the XML Logical Change Records (LCR). It shows how streams helps to replicate the data between databases and simplifies the work in such scenarios by interoperating with Advanced Queuing. This sample requires Oracle9i Database Release 2 Enterprise Edition (v9.2.0.4) to work.
Download Now (ZIP, 20KB)
Readme
Source

BooksOnLine Sample (Coming Soon)

Add an Active Table to Existing Streams Environment [18-Dec-2003]
This Streams best practice illustrates setting up bi-directional capture, propagation and application of a table DML and DDL change events between two different databases. It then adds another active table to existing Streams environment. A table is an active table if it is being modified by DML (Inserts/Updates/Deletes).
Download Now (ZIP, 19KB)
Readme
Source

Bitmap SubSetting [18-Dec-2003]
This Streams best practice illustrates the utility of a RAW redo tag for apply forwarding at the hub for update anywhere in a hub and spoke configuration. The changes made at any node in the configuration are propagated and replicated at all other nodes using a central hub. All the other nodes form the spokes of the configuration. Bitmap Subsetting is used to avoid propagating changes back to the database where they originated.
Download Now (ZIP, 13KB)
Readme
Source

Add Active Site to Existing Streams Environment [18-Dec-2003]
This Streams best practice illustrates setting up bi-directional capture, propagation and application of DML and DDL change events in a schema between two different databases. It then adds another active database(site) to existing Streams setup.
Download Now (ZIP, 14.5KB)
Readme
Source

Auto Correction (Coming Soon)