May be it could be interesting to talk about add the parameter HANDLECOLLISIONS in replicat sync to avoid the errors (unique constraint violated or record not found ) ?
Hey Arun...I have one doubt Will there be any duplicate data problem as when we start the change sync extract then initial load extract ..we loaded the initial load data into the target db but when we start the change sync replicat ..will it ignore the existing/overwrite data from the inital load extract?
Hi Arun , I have a small doubt. At time of IBM DB2 to Oracle Database Migration,how it convert Charecter set and comfortable all objects for Oracle ..Please guide me regarding this DB2 to Oracle full db migration.
Hi Sir, Can you please make video on Oracle TDE on Oracle Golden Gate sweep setup if you have any document for the same please let me know thanks in advance :)
Hello sir, Actually I am facing some during issues during the initial load as ia m getting constraints error in report..I have disabled the constraints and started the initial load but is there any workaround for this, as we cannot do this in production environment
how to prevent the duplication for records that already pushed to target and it's recorded in the extract process? like during the process of initial load (suppose that this process takes a lot of time), some records inserted to source tables then those changes can be applied to target by initial load. But they are also extracted and pushed to the target server by the data pump. Then how can we avoid duplication?
View the Replicat parameter file to make certain that the HANDLECOLLISIONS parameter is listed. If not, add the parameter to the file. And when the replicat have lag at chkpt 0 SEND REPLICAT group, NOHANDLECOLLISIONS and modify the replicat parameter file to remove the parameter
Please support. After changing in mgr process(In target) when I am going to refresh mgr process then this error comes Error: Access denied Warning OGG-01724 Command sent to MGR MGR returned with an error response
Congratulations, clear and interesting example.
Thank you
You are welcome!
Congrats for this great video series.
Glad you enjoy it!
This tutorial was very clear to understand. Thank you ..
Glad to hear that!
May be it could be interesting to talk about add the parameter HANDLECOLLISIONS in replicat sync to avoid the errors (unique constraint violated or record not found ) ?
Thank you. I learning now. You are great.
You are welcome!
Thank you❤
Hey Arun...I have one doubt
Will there be any duplicate data problem as when we start the change sync extract then initial load extract ..we loaded the initial load data into the target db but when we start the change sync replicat ..will it ignore the existing/overwrite data from the inital load extract?
Very nice information but include more topics from Golden gate.
we have a full course on our website. This video is one lecture from the entire course: dbagenesis.com/p/oracle-golden-gate-masterclass
Good information
could you plz share the document used in the video
Congrats for this
send me the document, please!
thanks
Hi Arun ,
I have a small doubt. At time of IBM DB2 to Oracle Database Migration,how it convert Charecter set and comfortable all objects for Oracle ..Please guide me regarding this DB2 to Oracle full db migration.
Hi Sir,
Can you please make video on Oracle TDE on Oracle Golden Gate sweep setup if you have any document for the same please let me know thanks in advance :)
Hello sir,
Actually I am facing some during issues during the initial load as ia m getting constraints error in report..I have disabled the constraints and started the initial load but is there any workaround for this, as we cannot do this in production environment
From where can I get this document?
how to prevent the duplication for records that already pushed to target and it's recorded in the extract process?
like during the process of initial load (suppose that this process takes a lot of time), some records inserted to source tables then those changes can be applied to target by initial load. But they are also extracted and pushed to the target server by the data pump. Then how can we avoid duplication?
View the Replicat parameter file to make certain that the HANDLECOLLISIONS parameter is listed. If not, add the parameter to the file. And when the replicat have lag at chkpt 0 SEND REPLICAT group, NOHANDLECOLLISIONS and modify the replicat parameter file to remove the parameter
Expalined perfectly as a good trainer,good work sir _/\_@NG
Please support.
After changing in mgr process(In target) when I am going to refresh mgr process then this error comes
Error: Access denied
Warning OGG-01724 Command sent to MGR MGR returned with an error response
If you have any technical questions then post it on www.forum.dbagenesis.com/