Switching from Classic Extract

Valid for Oracle only.

This procedure switches an existing Extract group from classic mode to Extract in Microservices. For more information about Extract modes for an Oracle database, see Choosing Capture and Apply Modes in .

To support the transition to integrated mode, the transaction log that contains the start of the oldest open transaction must be available on the source or downstream mining system, depending on where Extract will be running.

To determine the oldest open transaction, issue the SEND EXTRACT command with the SHOWTRANS option. You can use the FORCETRANS or SKIPTRANS options of this command to manage specific open transactions, with the understanding that skipping a transaction may cause data loss and forcing a transaction to commit to the trail may add unwanted data if the transaction is rolled back by the user applications. Review these options in SEND EXTRACT Parameters and Functions Reference for Oracle GoldenGatebefore using them.

GGSCI> SEND EXTRACT group, SHOWTRANS�
GGSCI> SEND EXTRACT group, { SKIPTRANS ID [THREAD n] [FORCE] |�
FORCETRANS ID [THREAD n] [FORCE] }�

To Switch Extract Modes

Back up the current Oracle GoldenGate working directories.
While the Oracle GoldenGate processes continue to run in their current configuration, so that they keep up with current change activity, copy the Extract parameter file to a new name.
Grant the appropriate privileges to the Extract user and perform the required configuration steps to support your business applications in integrated capture mode. See Assigning Credentials to Oracle GoldenGate in for information about configuring and running Extract in integrated mode.
Log into the mining database with one of the following commands, depending on where the mining database is located.
```
DBLOGIN USERIDALIAS alias

MININGDBLOGIN USERIDALIAS alias
```
Where: alias specifies the alias of a user in the credential store who has the privileges granted through the Oracle dbms_goldengate_auth.grant_admin_privilege procedure.
Register the Extract group with the mining database. Among other things, this creates the logmining server.
```
REGISTER EXTRACT group DATABASE
```
Issue the following command to determine whether the upgrade command can be issued. Transactions that started before the registration command must be written to the trail before you can proceed with the upgrade. You may have to issue this command more than once until it returns a message stating that Extract can be upgraded.
```
INFO EXTRACT group UPGRADE
```
Stop the Extract group.
```
STOP EXTRACT group
```
Switch the Extract group to integrated mode. See Oracle RAC options for this command in STOP EXTRACTin Parameters and Functions Reference for Oracle GoldenGate, if applicable.
```
ALTER EXTRACT group UPGRADE INTEGRATED TRANLOG
```
Replace the old parameter file with the new one, keeping the same name.
Start the Extract group.
```
START EXTRACT group
```