In the OCI GoldenGate deployment console navigation menu, click Replicat.
On the Replicat page, click Add Replicat.
In the Add Replicat panel, on the Replicat Information page, complete the
fields as needed, and then click Next:
Select a Replicat
Type:
Classic Replicat
Coordinated Replicat
Enter a Process Name, no more than 5 characters
long.
Enter a Description, to help distinguish this
process from others.
On the Replicat Options page, complete
the fields as needed, and then click Next:
Replicat Trail:
Enter a Name.
Enter a Subdirectory, if you expect the Trail
file to be in a location other than the default.
Select an Encryption profile. If an
encryption profile wasn't created, the Local Wallet is selected by default.
For Begin, select the starting point for data
processing:
Position in Log (default)
Now
Custom Time
Trail Position:
Enter the Sequence Number.
Enter the RBA Offset.
Select your Target from the dropdown.
Note:
Depending on your target
selection, you may have additional options to such as Streaming, Stage and
Merge, and Staging locations.
Target Credentials:
Select a Domain.
Select an Alias within the specified
Domain.
Select a Checkpoint
Table. Leave the default selection or select the Checkpoint table you created for the target deployment.
Select the Max Threads Number (Coordinated
Replicats only).
On the Managed Options page, complete the optional fields as
needed, and then click Next:
Select a Profile Name, if one is available.
Enable Critical to deployment health.
Enable and configure Auto Start settings.
On the Parameter File page, you can add parameters to further
configure your Replicat. For example:
table source.table1;
If using Coordinated Replicat,
add TARGETDB LIBFILE libggjava.so SET
property=/u02/Deployment/etc/conf/ogg/your_replicat_name.properties to the
parameters file.
Note:
GoldenGate uses Greenwich Mean Time (GMT) by default. Use SETENV to
override the default setting for this Replicat process. This change doesn't apply to deployments. For example:
setenv (TZ="US/Eastern")
setenv (TZ="GMT+5")
On the Properties File page, configure the File Handler and OCI Event Handler
properties as needed, and then click Next. Some
properties to consider modifying include:
gg.handler.name.format: Select how to format the
output data. Available options include:
gg.handler.name.fileNameMappingTemplate: Generates
file names dynamically using Template Keywords.
gg.handler.name.inactivityRollInterval: GoldenGate
creates a file and keeps it open for writing. This property closes the
file after the designated period of inactivity (no incoming
transactions) and then loaded into Oracle Object Storage.
gg.eventhandler.name.compartmentID: Enter the
compartment OCID.
gg.eventhandler.name.bucketMappingTemplate: Enter the
Object Storage bucket name.
You can also add pluggable
formatters as needed. For more information, see Pluggable Formatters.
Click Create and Run. If you click
Create, then you can manually start the Replicat later from the Replicats page.
Add a Replicat (21c)
To add a Replicat for an Oracle Object Storage
target:
In the OCI GoldenGate deployment console, on the Administration Service Overview page,
click Add Replicat (plus icon).
On the Add Replicat page, select a Replicat type, and then click
Next.
The types of Replicats are:
Classic Replicat
Coordinated Replicat
On the Replicat Options page, complete the following fields, and then click
Next:
For Process Name, enter a name for the Replicat process.
(Optional) For Description, enter a short description to distinguish
this process from others.
For Trail Name, enter two-character trail name.
For Target, select Oracle Object Storage from
the dropdown.
For Available aliases for OCI, select your alias from the
dropdown.
On the Parameter File page, add and configure Replicat parameters as needed,
and then click Next.
Note:
If using Coordinated Replicat, add the following
parameters on the second line of the Parameter
File:
TARGETDB LIBFILE libggjava.so SET property=/u02/Deployment/etc/conf/ogg/<replicat
name>.properties
Using
coordinated replicat will result in multiple files
created.
If omitted, you will encounter the
following
error:
OGG-01091 Oracle GoldenGate Delivery, RSNOW.prm: Unable to open file
"/u02/Deployment/etc/conf/ogg/<replicat name>001.properties" (error 2, No such file or
directory).
GoldenGate uses Greenwich Mean Time (GMT) by default.
Use SETENV to override the default setting. For
example:
On the Properties File page, configure the File Handler and OCI Event Handler
properties as needed, and then click Next. Some
properties to consider modifying include:
gg.handler.name.format: Select how to format the
output data. Available options include:
gg.handler.name.fileNameMappingTemplate: Generates
file names dynamically using Template Keywords.
gg.handler.name.inactivityRollInterval: GoldenGate
creates a file and keeps it open for writing. This property closes the
file after the designated period of inactivity (no incoming
transactions) and then loaded into Oracle Object Storage.
gg.eventhandler.name.compartmentID: Enter the
compartment OCID.
gg.eventhandler.name.bucketMappingTemplate: Enter the
Object Storage bucket name.
You're returned to the Administration Service Overview page where you can
monitor the status of the Replicat process. Click the process name to view its details
and access reports.
Known Issues with Oracle Object Storage
connections
OCI Object Storage replication
error when using Resource Principal
Replicat fails with the following error when using OCI Object Storage
connections that use Resource Principal
authentication:
ERROR 2025-06-12 14:48:16.000489 [main] - An exception has occurred: java.lang.NullPointerException: Cannot invoke "String.startsWith(String)" because "path" is null java.lang.NullPointerException: Cannot invoke "String.startsWith(String)" because "path" is null
Workaround: To work around this issue, edit the connection, and then
select a different authentication method.
User OCID Mismatch in OCI Object
Storage connection (Federated users only)
If a federated user selects Use current user when creating an OCI Object
Storage connection, their OCID doesn't match the OCID picked up by the system.
Workaround: When you create an OCI Object Storage connection, ensure
that you choose Specify another user, and then enter the
federated user's OCID.
To find the user OCID, click Profile in the Oracle Cloud console global header, and then select the
user name. On the User Details page, under User Information, click
Show for OCID.