OGG BD Coordinated Replicat Does't Load Json Files To S3(from thread 2 and 3) When Downgraded to 1 thread from 3 threads
(Doc ID 2689872.1)
Last updated on SEPTEMBER 29, 2020
Applies to:Oracle GoldenGate Big Data and Application Adapters - Version 22.214.171.124.3 and later
Information in this document applies to any platform.
OGG BD Coordinated Replicat Does't Load Json Files To S3(from thread 2 and 3) When Downgraded to 1 thread from 3 threads:
ogghubxxx-->(HUBDB1) /ggdata/dbxx/dirout/rdbxx> ls -l
-rw-r----- 1 oracle dba 34452 Jun 15 12:18 2020-06-15_16-13-57.505-RDBXX002.json
-rw-r----- 1 oracle dba 30621 Jun 15 12:18 2020-06-15_16-13-57.505-RDBXX003.json
Golden gate for big data with coordinated replicat process.
The target is AWS S3 , so we use golden gate for big data file handler with s3 event handler.
The file format is JSON.
We use either -
MAP *.*, TARGET *.*, threadrange(1-2);
MAP *.*, TARGET *.*, threadrange(1-4);
When we use 3 threads and then downgrade to 1 threads ( Stopping replicat process , changing .prm file and starting
replicat process ) , the JSON files generated by thread 2,3 and are still left in the ogghub server and not uploaded to AWS S3.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document