Add an Extract for Amazon DocumentDB
Extract is a process that runs against the source data source connection and extracts, or captures, data. Learn to add an Extract for Amazon DocumentDB.
Before you begin
Ensure that you review the details specific to this source connection type.
Add the Extract
-
In the OCI GoldenGate deployment console navigation menu, select Extracts.
-
On the Extracts page, select Add Extract.
-
In the Add Extract panel, on the Extract Information page, complete the following fields as needed, and then select Next:
-
Enter a Process Name, no more than 8 characters long.
-
Enter a Description (optional) to help you distinguish this process from others.
-
Select a Source from the dropdown.
-
-
On the Extract Options page, complete the following fields as needed, and then select Next:
-
For Extract Trail:
-
Enter a Name for the Extract process.
-
Enter a Subdirectory name to set a custom location for the generated Trail file.
-
Enter Trail Sequence to set the starting number for Trail files.
-
Enter a Trail Size to set the max size for the generated trail file.
-
Select an Encryption Profile. The Local Wallet profile is selected by default if an encryption profile wasn't created.
-
Select an Encryption Algorithm:
-
NONE
-
AES256
-
AES192
-
AES128
-
-
-
For Source Credentials, select the:
-
Domain
-
Alias
-
When/where to Begin
-
-
-
On the Managed Options page, complete the following optional fields as needed, and then select Next:
-
Profile Name
-
Critical to deployment health
-
Auto Start
-
Auto Restart
Note: Adding a profile and configuring Auto Start and Auto Restart options enables your deployment to restart automatically after a network disruption. See Configure managed processes to learn more.
-
-
On the Parameter File page, update the source mapping with
TABLE source.*;Note: This is the source database/collection mapping.
TABLE *.*;results in the process extracting from all databases/collections. -
Select Create and Run to create and start the Extract. If you select Create, then you can manually start the Extract later from the Extracts page.
Known issues
Replicats fail when using Trail file from MongoDB Extract with BINARY_JSON_FORMAT
When a Replicat uses a Trail file generated from a MongoDB Extract with BINARY_JSON_FORMAT in the Extract parameter file, the Replicat fails with the following error:
ERROR 2023-08-04 17:13:13.000421 [main] - Unable to decode column 0 : Input length = 1
java.nio.charset.MalformedInputException: Input length = 1 at
java.nio.charset.CoderResult.throwException(CoderResult.java:281) ~[?:1.8.0_311]at java.nio.charset.CharsetDecoder.decode(CharsetDecoder.java:816) ~[?:1.8.0_311] at
oracle.goldengate.datasource.UserExitDataSource.createColumnValue(UserExitDataSource.java:1106)
[ggdbutil-21.9.0.0.3.001.jar:21.9.0.0.3.001] Exception in thread "main"
oracle.goldengate.util.GGException: Unable to decode column 0 : Input length = 1 at
oracle.goldengate.datasource.UserExitDataSource.createColumnValue(UserExitDataSource.java:1203)
Workaround: When BINARY_JSON_FORMAT is removed from the Extract parameters, the Replicat runs successfully and documents are represented in Extended JSON format.