We're here to help!

Back to Basics With Dbvisit Replicate Part V

Follow

Dbvisit-Replicate-Configuration.jpg

We are about done with the Setup Wizard. In this blog, part 5 of our 6 part series (Part I, Part 2, Part 3, Part 4) we will now go over Step 4 of the Setup Wizard. We start off like every section with a recap of what is configured (or not configured) and then asking if you want to modify it or if you are done. Step 4 - Process configuration The fourth step is to configure the replication processes for each replication. Following processes are defined:

1: MINE on SDB11
   Not configured.
2: APPLY on TDB11
Not configured.
Enter number of process to modify it, or "done": [1]

We will start by configuring the MINE process. The first thing it will do is asking you the fully qualified name of the server. It will have a suggestion for you. (We grab that info from the TNSNAMES.ora file. I know many of you were wondering how we knew that).

The next question is what type of server it is. Enter the appropriate server. The next question is an important one, do you want to enable email notifications? If you don’t want to set it up now…you can always turn this feature on later. For the example here I will show you as if we were setting it up now.

The next question is about setting up SNMP traps. And the last asks what directory you want this set up in. And notice the default location is the same as the one you set up in the very first section of this series.  Once you answer you will see that we have filled in a whole bunch of defaults, the port numbers, the location of the PLOGs, the location of the logs, etc. You can change those if you like and it asks you after they have been displayed.

Fully qualified name of the server for the process 
(usually co-located with the database, unless mine is offloaded 
using fetcher):[dbvlintest.dbvisit.co.nz]
Server type (Windows/Linux/Unix): [Linux]
Enable email notifications about problems (yes/no)? [no] yes
Enable SNMP traps/notifications about problems (yes/no)? [no]
Directory with DDC file and default where to create log files etc. 
(recommended: same as global setting, if possible)? [/home/oracle/DEMO]

Following settings were pre-filled with defaults or your reloaded settings:
[MINE_REMOTE_INTERFACE]: Network remote interface: dbvlintest.dbvisit.co.nz:7901
[MINE_DATABASE]: Database TNS: SDB11
[TNS_ADMIN]: tnsnames.ora path:
/u01/app/oracle/product/11.2.0/db_1/network/admin
[MINE_PLOG]: Filemask for generated plogs: /home/oracle/DEMO/mine/%S.%E
(%S is sequence, %T thread, %F original filename (stripped extension), %P
process type, %N process name, %E default extension)
[LOG_FILE]: General log file: /home/oracle/DEMO/log/dbvrep_%N_%D.%E
[LOG_FILE_TRACE]: Error traces: /home/oracle/DEMO/log/trace/dbvrep_%N_%D_%I_%U.%E

Checking that these settings are valid...

Do you want change any of the settings? [no]

Right after that section the wizard will dive into questions about setting up the email configuration, due to the fact that I said yes to that question. First up is specifying the SMTP hostname. Does that server use SSL? What port do you need to set up for that server? Does that server need a user name and password? You will also get to specify the email address of where the email notifications are coming from. You will certainly want to have this information prepared ahead of time. And as I mentioned before you can always type no for this section and then configure these parameters after the fact.

(MAILCFG_SMTP_SERVER) - Specify mail (SMTP) server hostname: [] smtp.gmail.com
(MAILCFG_USE_SSL) - Use SSL to connect to the mail server (yes/no)? [] yes
(MAILCFG_PORT) - Specify port for SMTP server (usually 25; for SSL, usually 465):[465]
(MAILCFG_AUTH_USER) - If SMTP server requires username and password,
specify the username. Specify OFF if no login is required: [off]
chris.lawless@dbvisit.com
(MAILCFG_AUTH_PASSWD) - If SMTP server requires username and password,
specify the password. Specify OFF if no login is required: [off] my_passwd
(MAILCFG_FROM) - Specify the email address to be used as 'From:' address: 
[oracle@dbvlintest] rep_test@dbvisit.com

As always after a section we have a small review and will allow the option to edit the previous section, enter the next one or be done. Following processes are defined:

1: MINE on SDB11
Host: dbvlintest.dbvisit.co.nz, SMTP: YES, SNMP: no
2: APPLY on TDB11
Not configured.
Enter number of process to modify it, or "done": [2]

The questions are exactly the same for the next section as they were in the first. A question that often arises is why are we setting up email notifications twice? That is a good question. There are some companies out there that have different groups that watch and maintain the source and target databases. For this reason we allow different notifications on the source and target.

Fully qualified name of the server for the process (usually co-located with the 
database, unless mine is offloaded using fetcher): [dbvlintarget.dbvisit.co.nz]
Server type (Windows/Linux/Unix): [Linux]
Enable email notifications about problems (yes/no)? [no]
Enable SNMP traps/notifications about problems (yes/no)? [no]
Directory with DDC file and default where to create log files etc. 
(recommended: same as global setting, if possible)? [/home/oracle/DEMO]

Following settings were pre-filled with defaults or your reloaded settings:

[APPLY_REMOTE_INTERFACE]: Network remote interface: dbvlintarget.dbvisit.co.nz:7902
[APPLY_DATABASE]: Database TNS: TDB11
[TNS_ADMIN]: tnsnames.ora path: /u01/app/oracle/product/11.2.0/db_1/network/admin
[APPLY_STAGING_DIR]: Directory for received plogs: /home/oracle/DEMO/apply
[LOG_FILE]: General log file: /home/oracle/DEMO/log/dbvrep_%N_%D.%E
[LOG_FILE_TRACE]: Error traces:
/home/oracle/DEMO/log/trace/dbvrep_%N_%D_%I_%U.%E

Checking that these settings are valid...

Do you want change any of the settings? [no]

When you are done with the target, we see the review. After you are done you will see some files that are created for you in the directories that you specified previously. It also mentions that the wizard is complete and gives you directions on exactly what you should do. It mentions the running of the ‘all script’. We will talk about the ‘all script’ and the next things you need to do to get Dbvisit Replicate up and running in our next and final installment of this series.

Have more questions? Submit a request

Comments