Back to Basics With Dbvisit Replicate VI

Open

We are near the end of our journey.  In parts 1-5 (Part I, Part II, Part III, Part IV, Part V) we ran through the complete setup wizard.  In Part V we completed the setup wizard and are now ready to take the final steps to get replication up and running.  We will start by looking at the files that are now in your replication directory.  This is the directory that you had the setup wizard create earlier.

The important files to look at now are in the config directory:

This directory contains all of the configuration files.  The cfg files contain all of the answers that were the input from the setup wizard.  The sql files will be called from the ‘master script’ also know as the ‘all script’ . In our example you will see files and scripts with the word DEMO as that is what we input in the setup wizard.  This is why it is important to give it a relevant name. You will also find a log directory which of course is where Dbvisit Replicate logs are kept.  It is worthwhile to look at this directory later.  Also support may ask you for files from that directory. The DEMO directory also contains two DDC files.  DDC stands for Dbvisit Database Configuration.  There will be one file for the MINE process and one for the APPLY process.  You can think of the DDC files as your parameter files for MINE and APPLY.  You will also find two ‘DEMO-run’ files.  One script will start the MINE and one will start the APPLY.   There is also a start-console script to start the console.  There is a text file called Nextsteps.txt.  We will cover these files in a moment.  Lastly there is the ‘all’ script that was mentioned previous.  This all script will make a call to the configuration scripts in the config directory.  You could, in theory, run these scripts one at a time but the all script will make your life easier.  Running the all script is the next step in setting up replication.  Remember the setup wizard makes no changes to the database.  So we will know run the all.sh script.  This may take some time depending on which options you used to get the initial starting point and  how busy the application is.

The last line now tells you what to do.  Look in the Nextsteps.txt and it will give use the instructions on how to finish replication. Step 1. This is nice and easy and we will log onto the target server and make sure that the DEMO folder exists. Step 2. Is needed to copy the APPLY.ddc file over to the target server.  MINE will run on the source server so we don’t have to worry about that one.  So FTP the ddc file over to the target server in the DEMO directory that you created in Step 1. Step 3. Will ensure that the the ‘run’ scripts are pointing to the correct executable paths.  You will need to ensure this on both the source and target and make sure that the two run scripts are appropriate for each. Step 4. This  is similar to step 2.  We need to copy the APPLY run script to the target server.  FTP that over to the DEMO directory. Step 5.  If you are using the default ports of 7901 and 7902, make sure that they are open between the source and target servers.  If you use non default ports (configurable in Step 4 of the setup wizard) those ports would show up here. Step 6.  Depending on the initial data load method you chose you may have to do nothing here or you may need to do your export/import etc Step 7.   Here is where you will run the two run scripts.  These run scripts will start the MINE/APPLY process so that they start running. Step 8 . Starts the Dbvisit Replicate console so that you can ‘see’ the replication and make sure that the data is flowing. After following those 8 steps your replication will be up and running.  There really is nothing left to do but sit back and enjoy the data flow.