DBZ-3393 Fix typo & wording suggestions
This commit is contained in:
parent
0b95ef6d64
commit
b77e43cfa9
@ -1444,11 +1444,11 @@ See {link-prefix}:{link-oracle-connector}#oracle-transaction-metadata[Transactio
|
||||
|The mining strategy controls how Oracle LogMiner builds and uses a given data dictionary for resolving table and column ids to names. +
|
||||
+
|
||||
`redo_log_catalog` - Writes the data dictionary to the online redo logs causing more archive logs to be generated over time.
|
||||
This also enables tracking DDL changes against monitored tables, so if the schema changes frequently this is the ideal choice. +
|
||||
This also enables tracking DDL changes against captured tables, so if the schema changes frequently this is the ideal choice. +
|
||||
+
|
||||
`online_catalog` - Uess the database's current data dictionary to resolve object ids and does not write any extra information to the online redo logs.
|
||||
`online_catalog` - Uses the database's current data dictionary to resolve object ids and does not write any extra information to the online redo logs.
|
||||
This allows LogMiner to mine substantially faster but at the expense that DDL changes cannot be tracked.
|
||||
If the monitored table(s) schema changes infrequently or never, this is the ideal choice.
|
||||
If the captured table(s) schema changes infrequently or never, this is the ideal choice.
|
||||
|
||||
|[[oracle-property-log-mining-batch-size-min]]<<oracle-property-log-mining-batch-size-min, `+log.mining.batch.size.min+`>>
|
||||
|`1000`
|
||||
|
Loading…
Reference in New Issue
Block a user