Prepare the Second Source Database to Send Redo to the Mining Database

To prepare the second source database to send redo to the mining database:

Make sure that DBMS2 source database is running with the required compatibility.
```
select name, value from v$parameter where name = 'compatible'; NAME VALUE
    --------- --------------------- compatible 11.1.0.0.0
```
The minimum compatibility setting required from capture is 11.1.0.0.0.

Set DG_CONFIG at DBMS2 source database.

ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(dbms2, dbmscap)';

Set up redo transport at DBMS2 source database. The TEMPLATE clause is mandatory if you want to send redo data directly to foreign archived logs at the downstream mining database.
```
ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=DBMSCAP.EXAMPLE.COM ASYNC
OPTIONAL NOREGISTER  TEMPLATE='/usr/orcl/arc_dest/dbms2/dbms2_arch_%t_%s_%r.log
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)DB_UNIQUE_NAME=dbmscap';
```
Enable the downstream destination.
```
ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;
```

Note:

You can create multiple Extracts running in real-time Extract mode in the downstream mining database, as long as they all are capturing data from the same source database, such as capturing changes for database DBMS1 in the preceding example.