C Example Downstream Mining Configuration
Configuring a downstream mining database, see Configuring a Downstream Mining Database.
Topics:
- Example 1: Capturing from One Source Database in Real-time Mode
This example captures changes from source database DBMS1 by deploying an integrated capture session at a downstream mining database DBMSCAP. - Example 2: Capturing from Multiple Sources in Archive-log-only Mode
The following example captures changes from database DBMS1 and DBMS2 by deploying an integrated capture session at a downstream mining database DBMSCAP. - Example 3: Capturing from Multiple Sources with Mixed Real-time and Archive-log-only Mode
The following example captures changes from database DBMS1, DBMS2 and DBMS3 by deploying an integrated capture session at a downstream mining database DBMSCAP.
Example 1: Capturing from One Source Database in Real-time Mode
This example captures changes from source database DBMS1 by deploying an integrated capture session at a downstream mining database DBMSCAP.
Note:
The example assumes that you created the necessary standby redo log files as shown in Configuring a Downstream Mining Database.
This assumes that the following users exist:
-
User GGADM1 in DBMS1 whose credentials Extract will use to fetch data and metadata from DBMS1. This user has the alias of
ggadm1
in the Oracle GoldenGate credential store and logs in asggadm1@dbms1
. It is assumed that theDBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE()
procedure was called to grant appropriate privileges to this user at the source database. -
User GGADMCAP in DBMSCAP whose credentials Extract will use to retrieve logical change records from the logmining server at the downstream mining database DBMSCAP. This user has the alias of
ggadmcap
in the Oracle GoldenGate credential store and logs in asggadmcap@dbmscap
. It is assumed that theDBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE()
procedure was called to grant appropriate privileges to this user at the mining database.
- Prepare the Mining Database to Archive its Local Redo
- Prepare the Mining Database to Archive Redo Received in Standby Redo Logs from the Source Database
- Prepare the Source Database to Send Redo to the Mining Database
- Set up Integrated Capture (ext1) on DBMSCAP
Parent topic: Example Downstream Mining Configuration
Prepare the Mining Database to Archive its Local Redo
To prepare the mining database to archive its local redo:
Prepare the Mining Database to Archive Redo Received in Standby Redo Logs from the Source Database
To prepare the mining database to archive the redo received in standby redo logs from the source database:
Prepare the Source Database to Send Redo to the Mining Database
To prepare the source database to send redo to the mining database:
Set up Integrated Capture (ext1) on DBMSCAP
To set up integrated capture (ext1) on DBMSCAP:
Note:
You can create multiple Extracts running in real-time integrated capture 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.
Example 2: Capturing from Multiple Sources in Archive-log-only Mode
The following example captures changes from database DBMS1 and DBMS2 by deploying an integrated capture session at a downstream mining database DBMSCAP.
It assumes the following users:
-
User GGADM1 in DBMS1 whose credentials Extract will use to fetch data and metadata from DBMS1. It is assumed that the
DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE()
procedure was called to grant appropriate privileges to this user at DBMS1. -
User GGADM2 in DBMS2 whose credentials Extract will use to fetch data and metadata from DBMS2. It is assumed that the
DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE()
procedure was called to grant appropriate privileges to this user at DBMS2. -
User GGADMCAP in DBMSCAP whose credentials Extract will use to retrieve logical change records from the logmining server at the downstream mining database. It is assumed that the
DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE()
procedure was called to grant appropriate privileges to this user at the downstream mining database DBMSCAP.
This procedure also assumes that the downstream mining database is configured in archive log mode.
- Prepare the Mining Database to Archive its Local Redo
- Prepare the Mining Database to Archive Redo from the Source Database
- Prepare the First Source Database to Send Redo to the Mining Database
- Prepare the Second Source Database to Send Redo to the Mining Database
- Set up Extracts at Downstream Mining Database
Parent topic: Example Downstream Mining Configuration
Prepare the Mining Database to Archive its Local Redo
To prepare the mining database to archive its local redo:
Prepare the Mining Database to Archive Redo from the Source Database
Set DG_CONFIG
at the downstream mining database.
ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(dbms1,dbms2, dbmscap)'
Prepare the First Source Database to Send Redo to the Mining Database
To prepare the first source database to send redo to the mining database:
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:
Example 3: Capturing from Multiple Sources with Mixed Real-time and Archive-log-only Mode
The following example captures changes from database DBMS1, DBMS2 and DBMS3 by deploying an integrated capture session at a downstream mining database DBMSCAP.
Note:
This example assumes that you created the necessary standby redo log files as shown in Configuring a Downstream Mining Database.
It assumes the following users:
-
User GGADM1 in DBMS1 whose credentials Extract will use to fetch data and metadata from DBMS1. It is assumed that the
DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE()
procedure was called to grant appropriate privileges to this user at DBMS1. -
User GGADM2 in DBMS2 whose credentials Extract will use to fetch data and metadata from DBMS2. It is assumed that the
DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE()
procedure was called to grant appropriate privileges to this user at DBMS2. -
User GGADM3 in DBMS3 whose credentials Extract will use to fetch data and metadata from DBMS3. It is assumed that the
DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE()
procedure was called to grant appropriate privileges to this user at DBMS3. -
User GGADMCAP in DBMSCAP whose credentials Extract will use to retrieve logical change records from the logmining server at the downstream mining database. It is assumed that the
DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE()
procedure was called to grant appropriate privileges to this user at the downstream mining database DBMSCAP.
This procedure also assumes that the downstream mining database is configured in archive log mode.
In this example, the redo sent by DBMS3 will be mined in real time mode, whereas the redo data sent from DBMS1 and DBMS2 will be mined in archive-log-only mode.
- Prepare the Mining Database to Archive its Local Redo
- Prepare the Mining Database to Accept Redo from the Source Databases
- Prepare the First Source Database to Send Redo to the Mining Database
- Prepare the Second Source Database to Send Redo to the Mining Database
- Prepare the Third Source Database to Send Redo to the Mining Database
- Set up Extracts at Downstream Mining Database
Parent topic: Example Downstream Mining Configuration
Prepare the Mining Database to Archive its Local Redo
To prepare the mining database to archive its local redo:
Prepare the Mining Database to Accept Redo from the Source Databases
Because redo data is being accepted in the standby redo logs of the downstream mining database, the appropriate number of correctly sized standby redo logs must exist. If you did not configure the standby logs, see Configuring a Downstream Mining Database.
Prepare the First Source Database to Send Redo to the Mining Database
To prepare the first source database to send redo to the mining database:
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:
Prepare the Third Source Database to Send Redo to the Mining Database
To prepare the third source database to send redo to the mining database:
Set up Extracts at Downstream Mining Database
These steps set up Extract at the downstream database to capture from the archived logs sent by DBMS1 and DBMS2.
Set up Extract (ext1) to Capture Changes from Archived Logs Sent by DBMS1
Perform the following steps on the DBMSCAP downstream mining database.
Parent topic: Set up Extracts at Downstream Mining Database
Set up Extract (ext2) to Capture Changes from Archived Logs Sent by DBMS2
Perform the following steps on the DBMSCAP downstream mining database.
Parent topic: Set up Extracts at Downstream Mining Database
Set up Extract (ext3) to Capture Changes in Real-time Mode from Online Logs Sent by DBMS3
Perform the following steps on the DBMSCAP downstream mining database.
Note:
You can create multiple Extracts running in real-time integrated capture mode in the downstream mining database, as long as they all are capturing data from the same source database, such as all capturing for database DBMS3 in the preceding example.
Parent topic: Set up Extracts at Downstream Mining Database