Oracle Active Data Guard Physical Standby as HVR Replicate Source Database
- This topic has 1 reply, 2 voices, and was last updated 1 year, 9 months ago by .
- You must be logged in to reply to this topic.
What we have:
For tables which do NOT have supplemental logging enabled, we want to capture changes as they happen on the standby database.
If we use HVR Replication with the Standby Database as Source Database, can it take care of the tables which do not have supplemental logging to the Target Database?
By default Oracle does not write the external row identifier (primary key or unique key, if there is on) to the transaction logs in case of updates (inserts and deletes are always fully logged). During replication a row identifier is required to know how to process the data downstream.
Traditionally HVR requires supplemental logging to be enabled in order to fully capture the contents for an update, and we still document this as the best practice. However nowadays you can also set up HVR to capture the database’s ROWID as the surrogate key in an extra column, and use that to process the data downstream. Depending on your scenario this may work for you if there is no option to add supplemental logging to the tables on the source that don’t already have supplemental logging enabled.
© 2020 HVR
It appears you are still using Internet Explorer. Support for IE has been discontinued by Microsoft, and many features of our site may not display or work properly.