We have an Oracle environment that has been operating with supplemental logging set to PK. However, we now have a new requirement that requires changing the supplemental logging setting to ALL.
So I have the two following questions: (1) In this case, is it necessary to stop any tasks in Qlik Replicate that are related to the Oracle source which setting will be changed? If stopping the task is required, what kind of impact could be expected?
Also, would the impact differ depending on whether the change is made at the database level or at the table level?
(2) Is my understanding correct that when changing the supplemental logging settings on the Oracle side, no changes are required on the Qlik Replicate side?
(1) In this case, is it necessary to stop any tasks in Qlik Replicate that are related to the Oracle source which setting will be changed? If stopping the task is required, what kind of impact could be expected?
-- supplemental logging required at DB level, so Db process put extra info into redo logs which helps in faster DML operation on target. It always good to enable at TABLE LEVEL. NO task stop required
it requires prior to add table into the QR for replication.
Also, would the impact differ depending on whether the change is made at the database level or at the table level?
Yes if you set it At DB level the all the table operation logged with extra info even, they are not part of replication setup thus redo generation increased up to 5 to 10% approx. if its sets up at table level then the redo generation increased up to 1 to 3% approx. only. " Be informed its approx. it may be less or high and depend upon DML volume on Source DB."
(2) Is my understanding correct that when changing the supplemental logging settings on the Oracle side, no changes are required on the Qlik Replicate side?
yes as i mentioned supplemental logging requires prior to add table into the QR for replication.
(1) In this case, is it necessary to stop any tasks in Qlik Replicate that are related to the Oracle source which setting will be changed? If stopping the task is required, what kind of impact could be expected?
-- supplemental logging required at DB level, so Db process put extra info into redo logs which helps in faster DML operation on target. It always good to enable at TABLE LEVEL. NO task stop required
it requires prior to add table into the QR for replication.
Also, would the impact differ depending on whether the change is made at the database level or at the table level?
Yes if you set it At DB level the all the table operation logged with extra info even, they are not part of replication setup thus redo generation increased up to 5 to 10% approx. if its sets up at table level then the redo generation increased up to 1 to 3% approx. only. " Be informed its approx. it may be less or high and depend upon DML volume on Source DB."
(2) Is my understanding correct that when changing the supplemental logging settings on the Oracle side, no changes are required on the Qlik Replicate side?
yes as i mentioned supplemental logging requires prior to add table into the QR for replication.
