Once the initial data pumps had completed the loading of the new files and alternate key files, a special extract/replicat that had been configured on the source system, was started to apply all changes captured during the initial load, this took several minutes to apply the data to the new files.
Next up how validation of synchronization was accomplished.
There is definitely an advantage to using tools designed for validation of file synchronization. In this case Oracle/GoldenGate Veridata is being used to validate ongoing replication and file synchronizations.
For those installations without Veridata tools, you will probably need to craft your own toolset or think about obtaining Veridata, it makes the entire process so much smoother. (I don't work for GoldenGate or Oracle and this is not an endorsement of any product.)
Veridata compare pairs were created for source to new source as well as source to new target files. This process took about an hour of work building the compare sets and execution of the comparisons varied from just a few minutes to about 34 minutes to compare roughly 41 million records.
All of the validations, following the initial data pump and subsequent change capture application, were successful indicating the new files with new alternate key files were in sync.
At this point it was a matter of scheduling a switch window and build cutover scripts to perform file renames and process shutdown/startup to cutover to the new files.
Next, I'll discuss the methods used to switch, specific to this installation and the impact expected and realized...
- Posted using BlogPress from my iPad
No comments:
Post a Comment