Configure Advanced Settings
Explore different advanced settings for GoldenGate Studio.
You can use Advanced Options to fine tune your replications. These settings allow you to optimize performance, customize deployment behavior, and manage environment-specific requirements.
Initial Load Advanced Options
When setting up a replication, you can configure advanced options to optimize the Initial Load process.
The Initial Load advanced options determine how the data is transferred, handled, and synchronized between the source and target systems.
Setting | Description | Value |
---|---|---|
Action Upon Existing Tables | Determines how to handle existing target tables during initial load. | REPLACE, TRUNCATE, APPEND, SKIP |
Degree of Parallelism |
Number of parallel threads for the Data Pump load. Higher values can speed up loads but increase resource usage. If the number of CPUs is 'n' and degree of parallelism value is less than or equal to 'n' then the degree value is going to be 'n'. However, if the number of CPUs are 'n' but the degree of parallelism value is 'x', which is greater than 'n', then the degree value is going to be 'x' |
Any positive integer value >= 1. |
Additional Initial Load (Data Pump) Job Duration |
Specifies for how much time jobs will run after the expected completion time for Initial Load. After the assigned time it will automatically time out. |
1h |
Transfer Medium | Specifies the transfer method for Initial Load. | Database Link, Object Storage, File
Storage |
Object Storage Bucket URI | Location of the staging bucket for Initial Load files. | https://objectstorage.us-phoenix-1.oraclecloud.com/... |
Target Database SSL Wallet Path |
This is Wallet directory location of SSL Wallet for target database. |
/u02/app/oracle/admin/targetdb/wallet See Configure and Download SSL Wallet for Non-Autonomous Database |
Source Database SSL Wallet Path |
This is Wallet directory location of SSL Wallet for source database. |
/u02/app/oracle/admin/sourcedb/ssl_wallet See Configure and Download SSL Wallet for Non-Autonomous Database |
Wait Time for Open Transactions | Duration to wait for open transactions to finish before replication starts. | 1h |
Export Directory (Local Shared Storage) | This is Source shared directory location for writing dump files during data pump export. | /mnt/source_exports |
Import Directory (Local Shared Storage) | This is target shared directory location for writing dump files during data pump export. | /mnt/target_imports |
Actions Upon Expiry | Specifies if there is need to continue or stop if the transactions are open. | CONTINUE , STOP |
Note:
To get the Wallet Bucket URL from Oracle Cloud Infrastructure (OCI), where Autonomous Database is running, create a bucket in OCI and generate a pre-authenticated read/write URL for that bucket.Types of Initial Load Transfer Mediums
- Database Link
The Database Link method transfers data directly from the source database to the target database using an established database link, without any intermediate storage. This method works best when both databases are in the same network or connected through a stable, high speed link. Since it uses SQL INSERT statements to move data, the process is straightforward but can be slower for large datasets due to SQL execution overhead.
Database Link is less suited for large datasets or cross-region migrations, where latency could significantly slow down the process. It is best used for small to medium sized transfers where simplicity outweighs performance concerns.
- Object Storage
The Object Storage method stages initial load data in an Oracle Object Storage before importing it into the target database. GoldenGate first exports data from the source into Data Pump files, stores them in the specified bucket, and then imports them into the target. This approach eliminates the need for a direct network connection between source and target, which is suitable for cross region, cloud to cloud, or hybrid cloud migrations.
A direct database connection may be slow or restricted, so the data is staged in Object Storage and securely fetched by the target system. This method is highly reliable for large datasets and supports resumable transfers in case of interruptions. However, it requires additional configuration for bucket creation and wallet authentication, as well as extra storage space for staging files. It is best used when the migration involves large volumes of data across different regions or environments.
- File Storage
The File Storage method facilitates initial load by exporting source data into disk files on the GoldenGate server. These files are then ingested into the target database. This method is particularly effective when both source and target databases are non Autonomous Database and can access a shared storage layer, such as:
- Network File System (NFS) mounts
- Oracle File Storage Service (FSS)
- Docker volume mapping (for containerized database installations)
By leveraging shared storage, whether on premises or cloud based organizations can achieve high throughput data transfer and maintain control over the staging environment.
This method mirrors the Object Storage approach but is tailored for environments without access to native cloud object storage. By using shared storage, organizations can replicate the reliability and efficiency of object storage in on premises or hybrid setups.
GoldenGate writes extracted data files to the shared location, and the target database reads these files for ingestion. This intermediate staging allows for data validation, auditing, and performance tuning before final load. It’s particularly useful in secure environments with strict compliance requirements and high speed LAN connectivity.
This setup ensures fast, secure data transfer, audit-friendly staging, and full control over sensitive financial data.
To know more about intial load processing, refer to the Precise Instantiation for Oracle Using Initial Load Extract and About Data Replication Components in Oracle GoldenGate topics in Oracle GoldenGate Microservices Documentation.
Support Matrix – Oracle Database Flavors and Initial Load Methods
Learn about the supported Initial Load methods for different Oracle Databases with recommendations.
The matrix below outlines the supported Initial Load methods in GoldenGate Studio for various Oracle Database environments, including Autonomous Database and non Autonomous Database. These methods applies to all Recipes, including One-way, Active-active, and ZeroETL Recipes. Non Autonomous Database will contain both On-premise and DBaaS (Database as a service which is in Oracle Cloud Infrastructure).
Oracle Databases | Data Pump via Database Link | Data Pump using File Storage | Data Pump using Object Storage | Recommendation |
---|---|---|---|---|
Non Autonomous Database to non Autonomous Database | Yes | Yes | Yes | Choose Database Link for small datasets; Object Storage for large migrations. |
Autonomous Database to non Autonomous Database | Yes | No | Yes | Use Object Storage for secure and reliable transfer. |
Non Autonomous Database to Autonomous Database | Yes (Private Network) | No | Yes | Prefer Object Storage; use Database Link only if private network connectivity is available. |
Autonomous Database to Autonomous Database | Yes | No | Yes | Object Storage is recommended for cross-region or large dataset transfers. |
Replicat Advanced Options
Explore the Replicat Advanced Options.
Setting | Description | Values |
---|---|---|
Action upon DDL Error | Specifies the action to take when a Data Definition Language (DDL) operation fails. | DISCARD,IGNORE,KILL |
Action upon DML Error | Specifies the action to take when a Data Manipulation Language (DML) operation fails. | DISCARD,IGNORE,KILL, DEFAULT(RETRY_OPERATION)
ABORT_TRANSACTION |
Maximum Retry Count | The maximum number of tries can be specified by the users. | 0,1,2,3,4,5 |
If Replicat Auto Restart option is enabled, you will see the following options:
Setting | Description | Values |
Retry Delay | The amount of time (in sec) to pause between discovering that the process has terminated abnormally and restarting the process. | 0,1,2,3,4,5 |
Additional Replicat Parameters | This parameter instructs the Replicat process to ignore records that encounter Oracle error and continue processing. These are custom parameters that can be used to handle specific error codes and conditions. | REPERROR (26961, DISCARD) |
Failure | The number of times a task or process has failed in the current monitoring window. | 0,1,2,3,4,5 |
Max Retries | The maximum number of times the Replicat process will
attempt to restart after a failure. This setting works in conjunction
with RETRYDELAY .
|
|
Restart Windows | Defines the time frame within which the Max
Retries count is applied.
|
|
Parameter | Description | Default Value |
---|---|---|
|
Enables auto start for the Replicat process |
|
|
Delay before starting the Replicat process |
|
Extract Advanced Options
Explore the Extract Advanced Options.
Setting | Description | Values |
---|---|---|
Source Database timezone | Specifies the time zone of the source database. This is a critical setting for ensuring accurate timestamp replication. | EST,PST,UTC,IST |
Additional Extract parameters | This parameter instructs the Replicat process to ignore the records that encounter error and continue processing. These are custom parameters that can be used to handle specific error codes and conditions. | REPERROR (PROCEDURE, DISCARD) |
If Extract auto restart option is enabled, you will see the following options:
Setting | Description | Values |
Max Retries | The maximum number of times the Extract process will attempt to restart after a failure, before it gives up. | 0,1,2,3,4,5 |
Retry Delay | The time interval, in seconds, between each restart attempt. | 1s,2s,3s,4s |
Restart Window | The time frame within which the Max
Retries count is applied.
|
1m,2m,3m |
Failures | The total number of times the Extract task has failed within the specified Restart Window. | 0,1,2,3,4,5 |
Parameter | Description | Default Value |
---|---|---|
extractAutostartEnable |
Enables auto start for extract process | false |
extractAutostartDelay |
Delay before starting extract process | 5s |