alexey.rassokhin/tet123
1
0
Fork 0
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

DBZ-7939 Clarify LogMiner destination name configuration expectations

Browse Source
This commit is contained in:
Chris Cranford 2024-06-13 15:17:53 -04:00 committed by Chris Cranford
parent 9e684af94a
commit c120fe02f9
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
documentation/modules/ROOT/pages/connectors/oracle.adoc
View File

@ -2490,7 +2490,9 @@ If your Oracle environment includes multiple destinations that satisfy that crit
.Procedure .Procedure
* To specify the archive log destination that you want {prodname} to use, set the xref:oracle-property-log-mining-archive-destination-name[`log.mining.archive.destination.name`] property in the connector configuration. + * To specify the archive log destination that you want {prodname} to use, set the xref:oracle-property-log-mining-archive-destination-name[`log.mining.archive.destination.name`] property in the connector configuration. +
+ +
For example, in an organization with archive destinations `LOG_ARCHIVE_DEST_2` and `LOG_ARCHIVE_DEST_3`, if both destinations satisfy the criteria for use with {prodname} (that is, `status` is `VALID` and `type` is `LOCAL`), to configure the connector to use `LOG_ARCHIVE_DEST_3`, set the value of the `log.mining.archive.destination.name` property as follows: For example, in an database with two archive destination paths configured, `/path/one` and `/path/two`, these are associated with a destination name, column `DEST_NAME` in the `V$ARCHIVE_DEST_STATUS` table.
If both destinations satisfy the criteria for Debezium (that is, `status` is `VALID` and `type` is `LOCAL`), to configure the connector to use the archive logs written to the `/path/two` path, set the value of `log.mining.archive.destination.name` to the value in `DEST_NAME` for that path from `V$ARCHIVE_DEST_STATUS`.
For example, if the `DEST_NAME` is `LOG_ARCHIVE_DEST_3` for `/path/two`, you would configure Debezium as follows:
[source,json] [source,json]
---- ----
@ -2499,6 +2501,12 @@ For example, in an organization with archive destinations `LOG_ARCHIVE_DEST_2` a
} }
---- ----
[NOTE]
====
Do not set `log.mining.archive.destination.name` to the path where the archive logs are written by Oracle.
Instead, this property should refer to the value in the `DEST_NAME` column in the `V$ARCHIVE_DEST_STATUS` table for the preferred row that satisfies your archive log retention policy.
====
[WARNING] [WARNING]
==== ====
If your Oracle environment includes multiple destinations that satisfy that criteria, and you fail to specify the preferred destination, the {prodname} Oracle connector selects the destination path at random. If your Oracle environment includes multiple destinations that satisfy that criteria, and you fail to specify the preferred destination, the {prodname} Oracle connector selects the destination path at random.