This illustration shows an Oracle Streams two-database replication environment that includes the following Oracle databases:

• db1.example.com

• db2.example.com

Both databases contain the redo log for the local database. This redo log records changes to the hr schema.

The db1.example.com database has the following Oracle Streams components configured:

• A queue with a system-generated name.

• A capture process with a system-generated name that captures DML changes to the tables in the hr schema from the local redo log. The capture process enqueues these changes into the local queue.

• A propagation with a system-generated name that sends changes from the local source queue to the destination queue at db2.example.com.

The db2.example.com database has the following Oracle Streams components configured:

• A queue with a system-generated name.

• An apply process with a system-generated name that dequeues changes that originated at db1.example.com from the local queue and applies them to the tables in the hr schema.

For an optional bi-directional replication environment, the db1.example.com database also has the following Oracle Streams components configured. These components are shown in gray in the graphic and their actions are shown in dashed lines.

• A queue with a system-generated name.

• An apply process with a system-generated name that dequeues changes that originated at db2.example.com from the local queue and applies them to the tables in the hr schema.

For an optional bi-directional replication environment, the db2.example.com database also has the following Oracle Streams components configured. These components are shown in gray in the graphic and their actions are shown in dashed lines.

• A queue with a system-generated name.

• A capture process with a system-generated name that captures DML changes to the tables in the hr schema from the local redo log. The capture process enqueues these changes into the local queue.

• A propagation with a system-generated name that sends changes from the local source queue to the destination queue at db1.example.com.