Now, you're ready to add an Extract for your deployment.

1. From the Overview page of the Administration Service, click the + sign next to Extracts.

2. Choose the type of Extract to create and click Next.

   Note:

   To learn about creating initial load Extract, see About Instantiating with Initial Load Extract. You can also create a Change Data Capture (CDC) Extract for MySQL and SQL Server databases. See Add a Change Data Capture (CDC) Extract.

3. Provide the required information designated with an asterisk (*). Here's a description of the options in the different sections for the Add Extract screen:

   Option	Description	Database
   Basic Information Section
   Process Name	Name of the Extract process. The name of the Extract process can be up to 8 characters.	All databases
   Description	Description of the Extract process being created.	All databases
   Intent	Describes the purpose of creating the Extract. The default option is Unidirectional. Other options are High Availability, Disaster Recovery, N-Way, which are informational only.	All databases
   Begin	Used to set the beginning location in the redo or transaction log from which the Extract will start to capture data. Available options are Now, Custom Time, CSN or Position in Log, and EOF depending on the supported database.	All databases
   Trail Name	A two character trail name.	All databases
   Trail Subdirectory, Size, Sequence, and Offset	You can further configure the trail details.	All databases
   Remote	Enable this option if the Extract trail is remote. For Oracle databases, enable this option if the Extract trail is to be written directly to a remote Oracle GoldenGate Classic installation. For MySQL, setting this option enables the TRANLOGOPTIONS ALTLOGDEST REMOTE parameter to support a remote Extract, and is not related to trails.	Oracle, MySQL
   Registration Information Section
   CSN	Commit Sequence Number (CSN) value	Oracle
   Share	Choose the method to share the LogMiner data dictionary. Options are: Automatic: This option allows the system to choose the method for sharing the dictionary . None: Choosing this option, will not allow the dictionary to be shared. Extract: Choose this option to allow sharing the LogMiner dictionary for specific Extract.	Oracle
   Optimized	Enable this option to optimize the Extract registration.	Oracle
   Downstream Capture	Enable this option to set up a downstream Extract for log mining.	Oracle
   Register Only	Use this option to just register the Extract and not add the Extract. The registration creates the replication slot when you register the Extract or use the Register Only option.	PostgreSQL
   Source Database Credential
   Create new credential	If you haven't set up your database login credentials, you can create and save the database login credentials from here.	All
   Credential Domain	Create a domain for the database.	All
   Credential Alias	Specify a credential for the database login.	All
   User ID	Specify a user name for logging into the database.	All
   Password, Verify Password	Enter the password used to login to the database and reenter the password to verify.	All
   Credential Domain	Saves the credential user under the specified domain name. Enables the same alias to be used by multiple Oracle GoldenGate installations that use the same credential store. The default domain is Oracle GoldenGate.	All databases
   Credential Alias	Specifies an alias for the user name. Use this option if you do not want the user name to be in a parameter file or command. If ALIAS is not used, the alias defaults to the user name, which then must be used in parameter files and commands where a login is required. You can create multiple entries for a user, each with a different alias, by using the ADD USER option with ALIAS .	All databases
   Downstream Mining
   Mining Credential Domain	Domain name of the downstream mining database.	Oracle
   Mining Credential Alias	Alias for the mining downstream database.	Oracle
   No UserID	Enable this option if there is no source database connection. Selecting this option enables the ADG fetch options.	Oracle
   ADG Fetch Credential Domain	Domain name for the ADG fetch database.	Oracle
   ADG Fetch Credential Alias	Domain alias for the ADG fetch database. Note: Downstream Capture with ADG does not support per-PDB Extract.	Oracle

4. (Optional) Enter the encryption profile description. If you have not created an encryption profile, then the Local Wallet profile would be selected, by default.

   1. Select the profile name from the list box. You can select the Local Wallet or a custom profile.

   2. Select the encryption profile type from the list box.

   3. Specify the masterkey for the encryption profile. This option doesn't exist with SQL Server.

5. This is an optional step. Enter the Managed Options while creating all types of Extract processes. See Configure Managed Processes.

   The following table provides these options:

   Option	Description
   Profile Name	Provides the name of the autostart and autorestart profile. You can select the default or custom options. If you have already created a profile, then you can select that profile also. If you select the Custom option, then you can set up a new profile from this section itself.
   Critical to deployment health	(Oracle only) Enable this option if the profile is critical for the deployment health. Note: This option only appears while creating the Extract or Replicat and not when you set up the managed processes in the Profiles page.
   Auto Start	Enables autostart for the process.
   Startup Delay	Time to wait in seconds before starting the process
   Auto Restart	Configures how to restart the process if it terminates
   Max Retries	Specify the maximum number of retries to try to start the process
   Retry Delay	Delay time in trying to start the process
   Retries Window	The duration interval to try to start the process
   Restart on Failure only	If true the task is only restarted if it fails.
   Disable Task After Retries Exhausted	If true then the task is disabled after exhausting all attempts to restart the process.

6. Click Next.

7. You can edit the parameter file in the text area to list the table details that you are interested in capturing. For example, table source.table1;.

8. You can select Register Extract in the background to register the Extract in the background asynchronously. This option is required for Oracle and PostgreSQL databases. See Register an Extract.

9. Click Create and Run to create and start the Extract. If you select Create, the Extract is created but you need to start it using the Extract drop-down on the Overview page.

   You are returned to the Overview page of the Administration Service. Select the Action list if you want to look at the Extract details such as process information, checkpoint, statistics, parameters, and report.

These steps configure a CDC Extract to capture transactional data from a source database.

CDC Extract is available with SQL Server and PostgreSQL databases.

1. Using the Admin Client, or REST API client on the source system, create the Extract parameter file. EDIT PARAMS extname

   In this sample, extname is the name of the primary Extract and matches the name of the Extract that was registered with the database in the previous steps.

   To learn about using Oracle GoldenGate Microservices to perform this task, see Add a Primary Extract.

2. Enter the Extract parameters in the order shown, starting a new line for each parameter statement. Sample basic parameters for Extract for Microservices installations:

   EXTRACT extname
   SOURCEDB dsn_name 
   USERIDALIAS alias
   EXTTRAIL ep
   GETTRUNCATES
   TABLE schema.*;

   Parameter	Description
   EXTRACT extname	extname is the name of the Extract and cannot be more than 8 alpha-numeric characters in length. For more information, see extract in Reference for Oracle GoldenGate.
   SOURCEDB dsn_name	Specifies the name of the database connection DSN.
   USERIDALIAS alias	Specifies the alias of the database login credential of the user that is assigned to Extract. This credential must exist in the Oracle GoldenGate credential store.
   EXTTRAIL trailname	Specifies a two character, local trail to which the primary Extract writes captured data.
   GETTRUNCATES	Optional parameter but needed in order to capture truncation operations.
   TABLE schema.object; or TABLE schema.*;	Specifies the database object for which to capture data. TABLE specifies a table or a wildcarded set of tables. schema is the schema name or a wildcarded set of schemas. object is the table or sequence name, or a wildcarded set of those objects. * is a wildcard for all tables in the schema. Terminate the parameter statement with a semi-colon. To exclude a name from a wildcard specification, use the SCHEMAEXCLUDE, TABLEEXCLUDE, and EXCLUDEWILDCARDOBJECTSONLY parameters as appropriate. Note: If the schema of tables to be captured from is the same as the schema in GGSCHEMA of the GLOBALS file, which is not recommended, then you cannot use schema.* in the TABLE statement.

3. Enter any optional Extract parameters that are recommended for your configuration. You can edit this file at any point before starting processing by using the EDIT PARAMS command.
4. Save and close the file.
5. Add the Extract and its associated trail file.