JavaScript must be enabled to correctly display this content
Add a Replicat for Redis
Learn to add a Replicat process for a Redis
target.
Add a Replicat
(21c)
To add a Replicat for an Redis target in Oracle GoldenGate
21c:
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.
If the source is Trail, then for Trail Name, enter the name
of the Extract trail.
For Target, select Redis.
For Alias, select your Redis connection.
On the Parameter File page, add and configure Replicat parameters as
needed, and then click Next.
Note:
When 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
On the Properties page, you can update Redis integration point by changing the
gg.handler.redis.integrationType property. OCI GoldenGate
supports hashmaps, streams and jsons as Redis integration
points. Refer to Redis Handler Configuration Properties
for more information.
Click Create and Run. If you click
Create, then you can manually start the Replicat later from the
Administration Service Overview page.
You return to the Administration Service Overview page where
you can view the creation of the Replicat process and access Replicat Actions.
In the OCI GoldenGate deployment console, on the Administration Service Home page, click
Add Replicat (plus icon).
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 page, you can update Redis integration point by changing the
gg.handler.redis.integrationType property. OCI GoldenGate
supports hashmaps, streams and jsons as Redis integration
points. Refer to Redis Handler Configuration Properties
for more information.
Click Create and Run. If you click
Create, then you can manually start the Replicat later from the
Administration Service Home page.
Oracle customer access to and use of Oracle support
services will be pursuant to the terms and conditions specified in their Oracle
order for the applicable services.