To create and run Extract and Replicat processes, you need to set up database credentials to connect Extract/Replicat users to the respective source or target databases.

1. Launch the Administration Service interface and log in.
2. Click Configuration from the Application Navigation pane.
3. Click the plus sign (+) sign next to Credentials.
4. Enter the following details in the displayed fields:

   Database Credential Options	Description
   Credential Domain	Specify a domain name to which the database credential is associated. For example, "OracleGoldenGate" is the default domain name, incase you don't specify a domain name.
   Credential Alias	This is the alias for your database credential.
   User ID	This is the username of the database user. For Oracle database, if you use the EZconnect syntax to connect to the database, then you can specify the value in this field in the following manner: dbusername@hostname:port/service_name dbusername is the database user name. hostname or IP address of the server where the database is running. port is the port number for connecting to the database server. Usually, this value is 1521. service_name is the name of the service provided in the tnsnames.ora file for the database connection.
   Password	Password used by database user to log in to the database.

5. Click Submit.
6. Click the Connect to database icon to test that the connection is working correctly. If the connection is successful, the Connect to database icon turns blue.

When you successfully log into your database, you can add and manage checkpoint tables, transaction information (TRANDATA), and heartbeat tables. All of the tables can be searched using the various search fields. As you type, the table is filtered and you can use the search button with the search text.

To set up the transfer of redo log files from a source database to the downstream mining database, and to prepare the downstream mining database to accept these redo log files, perform the steps given in this topic.

The following summarizes the rules for supporting multiple sources sending redo to a single downstream mining database:

• Only one source database can be configured to send online redo to the standby redo logs at the downstream mining database. The log_archive_dest_n setting for this source database should not have a TEMPLATE clause.
• Source databases that are not sending online redo to the standby redo logs of the downstream mining database must have a TEMPLATE clause specified in the log_archive_dest_n parameter.
• Each of the source databases that sends redo to the downstream mining database must have a unique DBID. You can select the DBID column from the v$database view of these source databases to ensure that the DBIDs are unique.
• The FAL_SERVER value must be set to the downstream mining database. FAL_SERVER specifies the FAL (fetch archive log) server for a standby database. The value is a list of Oracle Net service names, which are assumed to be configured properly on the standby database system to point to the desired FAL servers. The list contains the net service name of any database that can potentially ship redo to the downstream database.
• When using redo transport, there could be a delay in processing redo due to network latency. For Extract, this latency is monitored by measuring the delay between LCRs received from source database and reporting it. If the latency exceeds a threshold, a warning message appears in the report file and a subsequent information message appears when the lag drops to normal values. The default value for the threshold is 10 seconds.

When using a downstream mining configuration, there must be an Extract mining user on the downstream database. The mining Extract process uses the credentials of this user to interact with the downstream logmining server.

The downstream mining user is specified by the TRANLOGOPTIONS parameter with the MININGUSERALIAS option.

See Add Database Credentials to Connect to the Source Database to assign the correct credentials for the version of your database.

This procedure configures the downstream mining database to archive redo data in its online redo logs. These are redo logs that are generated at the downstream mining database.

Archiving must be enabled at the downstream mining database if you want to run Extract in real-time integrated capture mode, but it is also recommended for archive-log-only capture. Extract in integrated capture mode writes state information in the database. Archiving and regular backups will enable you to recover this state information in case there are disk failures or corruption at the downstream mining database.

To Archive Local Redo Log Files:

1. Alter the downstream mining database to be in archive log mode. You can do this by issuing the following

    DDL.STARTUP MOUNT;
   ALTER DATABASE ARCHIVELOG;
   ALTER DATABASE OPEN;

2. At the downstream mining database, set the first archive log destination in the LOG_ARCHIVE_DEST_n initialization parameter as shown in the following example:

   ALTER SYSTEM SET
   LOG_ARCHIVE_DEST_1='LOCATION=/home/arc_dest/local
   VALID_FOR=(ONLINE_LOGFILE,PRIMARY_ROLE)'

   Alternatively, you can use a command like this example:

   ALTER SYSTEM SET
   LOG_ARCHIVE_DEST_1='LOCATION='USE_DB_RECOVERY_FILE_DEST' valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE)'

   Note:

   The online redo logs generated by the downstream mining database can be archived to a recovery area. However, you must not use the recovery area of the downstream mining database to stage foreign archived logs or to archive standby redo logs. For information about configuring a fast recovery area, see the Oracle Database Backup and Recovery User’s Guide.

3. Enable the local archive destination.

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_1=ENABLE

When TDE is enabled on source database and downstream database, then the source wallet or keys should be the same on the downstream mining database and the source database.

Follow these steps to copy the wallet directory from the source database to the downstream mining database:

1. Shutdown the downstream database using the shutdown immediate command.

2. Remove the wallet directory in the downstream database: rm $OGG_DS_HOME/wallet/*

3. Copy the $OGG_DS_HOME/wallet/* from the source database view to the downstream database view.

4. Restart the downstream database.

5. Run checksum on the source database view and downstream database view to ensure that it matches:

   cksum $OGG_DS_HOME/wallet/*

Topics:

To prepare the mining database to archive its local redo:

1. The downstream mining database must be in archive log mode. You can do this by issuing the following DDL:

   STARTUP MOUNT;
   ALTER DATABASE ARCHIVELOG;
   ALTER DATABASE OPEN;

2. At the downstream mining database, set log_archive_dest_1 to archive local redo:

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='LOCATION=/home/arc_dest/local
   VALID_FOR=(ONLINE_LOGFILE, PRIMARY_ROLE)'

3. Enable log_archive_dest_1.

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_1=ENABLE

To prepare the mining database to archive the redo received in standby redo logs from the source database:

1. At the downstream mining database, set log_archive_dest_2 as shown in the following example:

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='LOCATION=/home/arc_dest/srl_dbms1 
   VALID_FOR=(STANDBY_LOGFILE,PRIMARY_ROLE)'

2. Enable log_archive_dest_2 as shown in the following example:

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE

3. Set DG_CONFIG at the downstream mining database:

    ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(dbms1,dbmscap)'

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

1. Make sure that the source database is running with the required compatibility:

   select name, value from v$parameter where name = 'compatible'; 

   The minimum compatibility setting required from integrated capture is 11.1.0.0.0.
2. Set DG_CONFIG at the source database:

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

3. Set up redo transport at the source database..

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=DBMSCAP.EXAMPLE.COM ASYNC
   OPTIONAL NOREGISTER
   VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)DB_UNIQUE_NAME=dbmscap';

4. Enable the downstream destination.

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;

To set up Extract (ext1) on DBMSCAP:

1. Register Extract with the downstream mining database. In the credential store, the alias name of ggadm1 is linked to a user connect string of ggadm1@dbms1. The alias name of ggadmcap is linked to a user connect string of ggadmcap@dbmscap.

   DBLOGIN USERIDALIAS ggadm1

   MININGDBLOGIN USERIDALIAS ggadmcap

   REGISTER EXTRACT ext1 DATABASE

2. Create Extract at the downstream mining database:

   ADD EXTRACT ext1 INTEGRATED TRANLOG BEGIN NOW

3. Edit Extract parameter file ext1.prm. The following lines must be present to take advantage of real-time capture. In the credential store, the alias name of ggadm1 is linked to a user connect string of ggadm1@dbms1. The alias name of ggadmcap is linked to a user connect string of ggadmcap@dbmscap.

   USERIDALIAS ggadm1 TRANLOGOPTIONS MININGUSERALIAS ggadmcap TRANLOGOPTIONS 
   INTEGRATEDPARAMS (downstream_real_time_mine Y)

4. Start Extract.

   START EXTRACT ext1

To prepare the mining database to archive its local redo:

1. The downstream mining database must be in archive log mode. You can do this by issuing the following DDL.

   STARTUP MOUNT; ALTER DATABASE ARCHIVELOG; ALTER DATABASE OPEN;

2. At the downstream mining database, set log_archive_dest_1 to archive local redo.

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='LOCATION=/home/arc_dest/local
   VALID_FOR=(ONLINE_LOGFILE, PRIMARY_ROLE)'

3. Enable log_archive_dest_1.

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_1=ENABLE

4. Start Extract.

   START EXTRACT ext1

Set DG_CONFIG at the downstream mining database.

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

Topics:

To prepare the mining database to archive its local redo:

1. The downstream mining database must be in archive log mode. You can do this by issuing the following DDL:

   STARTUP MOUNT;
   ALTER DATABASE ARCHIVELOG;
   ALTER DATABASE OPEN;

2. At the downstream mining database, set log_archive_dest_1 to archive local redo.:

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='LOCATION=/home/arc_dest/local
   VALID_FOR=(ONLINE_LOGFILE, PRIMARY_ROLE)'

3. Enable log_archive_dest_1.

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_1=ENABLE

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 Create the Standby Redo Log Files.

1. At the downstream mining database, set the second archive log destination in the LOG_ARCHIVE_DEST_n initialization parameter as shown in the following example. This is needed to handle archive standby redo logs.

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='LOCATION=/home/arc_dest/srl_dbms3
   VALID_FOR=(STANDBY_LOGFILE,PRIMARY_ROLE)'

2. Enable the LOG_ARCHIVE_DEST_STATE_2 initialization parameter that corresponds with the LOG_ARCHIVE_DEST_2 parameter as shown in the following example:

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE

3. Set DG_CONFIG at the downstream mining database to accept redo data from all of the source databases.

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

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

1. Make certain that DBMS1 source database is running with the required compatibility.

   select name, value from v$parameter where name = 'compatible'; 

2. Set DG_CONFIG at DBMS1 source database:

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

3. Set up redo transport at DBMS1 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/dbms1/dbms1_arch_%t_%s_%r.log VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)DB_UNIQUE_NAME=dbmscap';

4. Enable the downstream destination:

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;

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

1. Make sure that DBMS2 source database is running with the required compatibility.

   select name, value from v$parameter where name = 'compatible';

2. Set DG_CONFIG at DBMS2 source database:

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

3. 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';

4. Enable the downstream destination:

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;

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

1. Make sure that DBMS2 source database is running with the required compatibility.

   select name, value from v$parameter where name = 'compatible';

2. Set DG_CONFIG at DBMS2 source database:

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

3. 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';

4. Enable the downstream destination:

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;

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

1. Make sure that DBMS3 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.

2. Set DG_CONFIG at DBMS3 source database:

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

3. Set up redo transport at DBMS3 source database. Because DBMS3 is the source that will send its online redo logs to the standby redo logs at the downstream mining database, do not specify a TEMPLATE clause.

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=DBMSCAP.EXAMPLE.COM ASYNC
       OPTIONAL NOREGISTER
       VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)DB_UNIQUE_NAME=dbmscap';

4. Enable the downstream destination:

   ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;

Topics: