We're here to help!

oracle@dbvlab01[/usr/dbvisit/standby8]: cd standby/
oracle@dbvlab01[/usr/dbvisit/standby8/standby]: ll
total 8616
drwxr-x--- 2 oracle oinstall 4096 Nov 14 14:09 conf
-rwxr-xr-x 1 oracle oinstall 8789264 Nov 14 14:09 dbvctl
drwxr-x--- 2 oracle oinstall 4096 Nov 14 14:09 doc
drwxr-x--- 2 oracle oinstall 4096 Nov 14 14:09 gs
drwxr-x--- 2 oracle oinstall 4096 Nov 14 14:09 lib
drwxr-x--- 2 oracle oinstall 4096 Nov 14 14:09 log
drwxr-x--- 2 oracle oinstall 4096 Nov 14 14:09 pid
drwxr-x--- 2 oracle oinstall 4096 Nov 14 14:09 tmp
drwxr-x--- 2 oracle oinstall 4096 Nov 14 14:09 trace

2. Run the create DDC command and follow the questions

   - take note of ARCHSOURCE and ARCHDEST

   - take note of different $ORACLE_HOME if applicable

   - ensure to apply correct version 8 license

oracle@dbvlab01[/usr/dbvisit/standby8/standby]: ./dbvctl -o setup
=======================================
Dbvisit Standby Database Technology (8.0.24_0_ge6b43639)
 http://www.dbvisit.com
=======================================

=>dbvctl only needs to be run on the primary server.

Is this the primary server? <Yes/No> [Yes]:
The following Dbvisit Database configuration (DDC) file(s) found on this
server:

DDC
 ===
1) Create New DDC
2) Cancel

Please enter choice []: 1
Is this correct? <Yes/No> [Yes]:

END USER LICENSE AGREEMENT
 PLEASE READ THIS END USER LICENSE AGREEMENT (AGREEMENT) CAREFULLY BEFORE
 DOWNLOADING THE LICENSED PRODUCT. BY CLICKING I AGREE BELOW, YOU ARE
 REPRESENTING THAT YOU HAVE THE RIGHT AND AUTHORITY TO LEGALLY BIND YOURSELF
 OR YOUR COMPANY, AS APPLICABLE AND YOU ARE AGREEING TO BE BOUND BY THE
 TERMS AND CONDITIONS OF THIS AGREEMENT, THE SUPPORT AGREEMENT AND THE
 IMPLEMENTATION ASSISTANCE AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF
 THIS AGREEMENT, THE SUPPORT AGREEMENT OR THE IMPLEMENTATION ASSISTANCE
 AGREEMENT, CLICK I DO NOT AGREE AND YOU WILL NOT BE PERMITTED TO DOWNLOAD
 THE LICENSED PRODUCT.

Continue ? <Yes/No> [No]: Yes

=======================================
Dbvisit Standby setup begins.
=======================================
The following Oracle instance(s) have been found on this server:
SID ORACLE_HOME
 === ===========
1) asmdb/u01/app/oracle/product/11.2.0/dbhome_1
2) testdb7 /u01/app/oracle/product/11.2.0/dbhome_1
3) testdb8 /u01/app/oracle/product/11.2.0/dbhome_1
4) devdb /u01/app/oracle/product/11.2.0/dbhome_1
5) CHARM /u01/app/oracle/product/11.2.0/dbhome_1
6) XE /u01/app/oracle/product/11.2.0/dbhome_1
7) testbd7 /u01/app/oracle/product/11.2.0/dbhome_1
8) asmdb7 /u01/app/oracle/product/11.2.0/dbhome_1
9) asmdb /u01/app/oracle/product/11.2.0/dbhome_1
10) test /u01/app/oracle/product/11.2.0/dbhome_1
11) Enter own ORACLE_SID and ORACLE_HOME
Please enter choice [] : 10

Is this correct? <Yes/No> [Yes]:
=>ORACLE_SID will be: test
=>ORACLE_HOME will be: /u01/app/oracle/product/11.2.0/dbhome_1

=======================================
Enter the primary server name.
Note: The hostname is case sensitive on UNIX based systems.
=>SOURCE is [dbvlab01]:
Your input: dbvlab01

Is this correct? <Yes/No> [Yes]:
Choice is dbvlab01
=======================================

Please enter a filesystem directory that Dbvisit Standby use to store (archive) log files. This directory is not the same as the database recovery area or archive destinations and should not be
located in these areas.
The ARCHSOURCE directory is located on the primary server and will become the ARCHDEST location when the primary database is converted to a standby database during a Graceful Switchover operation.
This directory will ONLY contain (archive) log files related to this database. It should not contain any other (non archive log) files.
Please ensure that this directory exists on

=>ARCHSOURCE is [/u01/app/oracle/dbvisit_arch/test]:
Your input: /u01/app/oracle/dbvisit_arch/test

Is this correct? <Yes/No> [Yes]:
Choice is /u01/app/oracle/dbvisit_arch/test
=======================================

Do you want to use SSH to connect to the standby server? Note that if you are using SSH, passwordless SSH authentication between the hosts must already be configured. By default Dbvnet will be used.
=>USE_SSH is [N]:
Your input: N

Is this correct? <Yes/No> [Yes]:
Choice is N
=======================================

Enter the standby database hostname.

If the standby database will be Oracle RAC enabled:
Enter the Virtual Hostname (linked to a Virtual IP) for standby database. This virtual hostname 
is attached to the VIP that will be able to move between the RAC nodes. Dbvisit 
Standby will only run on the server where this virtual hostname (VIP) resource is running.
The Virtual Hostname (and VIP) should be configured as a resource in clusterware and must be
enabled and started on one of the notes before you continue with the setup.
If you are not using a Virtual Hostname (Highly Recommended), Dbvisit Standby can
only be configured to run on one dedicated node in the RAC configuration - specify
the hostname here if you do not have a Virtual Hostname (attached to VIP) for the 
for the cluster configured.

For non-RAC configurations specify the standby database server name here.

=>DESTINATION is []: dbvlab03
Your input: dbvlab03

Is this correct? <Yes/No> [Yes]:
Choice is dbvlab03

=======================================
Specify the DBVNET or SSH port number on the standby server. The default value supplied is the dbvnet port 7890. If you specified the use of SSH, please specify the SSH port here.
=>NETPORT is [7890]:
Your input: 7890

Is this correct? <Yes/No> [Yes]:
Choice is 7890

=======================================
Enter Dbvisit Standby installation directory on the standby server
=>DBVISIT_BASE_DR is [/usr/dbvisit/standby8]:
Your input: /usr/dbvisit/standby8

Is this correct? <Yes/No> [Yes]:
Choice is /usr/dbvisit/standby8

=======================================
Enter ORACLE_HOME directory on the standby server
=>ORACLE_HOME_DR is [/u01/app/oracle/product/11.2.0/dbhome_1]: /u01/app/oracle/product/11.2.0/db_1
Your input: /u01/app/oracle/product/11.2.0/db_1

Is this correct? <Yes/No> [Yes]:
Choice is /u01/app/oracle/product/11.2.0/db_1

=======================================
Enter DB_UNIQUE_NAME on the standby server
=>DB_UNIQUE_NAME_DR is [test]:
Your input: test

Is this correct? <Yes/No> [Yes]:
Choice is test

=======================================
Please enter the directory where Dbvisit Standby will transfer the (archive) log files to on standby server. 
This directory is not the same as the database recovery area or archive destinations and
should not be located in these areas.

This directory should ONLY contain (archive) log files related to this database. 
It should not contain any other (non archive log) files.
Please ensure that this directory exists on the standby server

=>ARCHDEST is [/u01/app/oracle/dbvisist_arch/test]:
Your input: /u01/app/oracle/dbvisist_arch/test

Is this correct? <Yes/No> [Yes]:
Choice is /u01/app/oracle/dbvisit_arch/test

=======================================
Enter ORACLE_SID on the standby server
=>ORACLE_SID_DR is [test]:
Your input: test

Is this correct? <Yes/No> [Yes]:
Choice is test

=======================================
Enter ASM instance name on the standby server, if your standby is using ASM. 
If you are not using ASM on the standby leave the value blank.
=>ORACLE_SID_ASM_DR is []:

Is this correct? <Yes/No> [Yes]:
Choice is null

=======================================
Please specify the name of the Dbvisit Database configuration (DDC) file.
The DDC file is a plain text file that contains all the Dbvisit Standby settings.
=>ENV_FILE is [test]:
Your input: test

Is this correct? <Yes/No> [Yes]:
Choice is test

=======================================
Below are the list of configuration variables provided during the setup process:
Configuration Variable Value Provided

=======================================
ORACLE_SID test
ORACLE_HOME /u01/app/oracle/product/11.2.0/dbhome_1

SOURCE dbvlab01
ARCHSOURCE /u01/app/oracle/dbvisit_arch/test
RAC_DR N
USE_SSH N
DESTINATION dbvlab03
NETPORT 7890
DBVISIT_BASE_DR /usr/dbvisit/standby8
ORACLE_HOME_DR /u01/app/oracle/product/11.2.0/db_1
DB_UNIQUE_NAME_DR test
ARCHDEST /u01/app/oracle/dbvisit_arch/test
ORACLE_SID_DR test
ENV_FILE test

Are these variables correct? <Yes/No> [Yes]:

>>> Dbvisit Database configuration (DDC) file test created.

>>> Dbvisit Database repository (DDR) test created.
Repository Version 8.4
 Software Version 8.4
 Repository Status VALID

Do you want to enter license key for the newly created Dbvisit Database configuration (DDC) file? 
<Yes/No> [Yes]:

Enter license key and press Enter: []: 4xx4x-4zzzz-y99y9-wwwww-4vvv4-uuuuu-99y9y
>>> Dbvisit Standby License
License Key :
4xx4x-4zzzz-y99y9-wwwww-4vvv4-uuuuu-99y9y
customer_number : 1
dbname :
expiry_date : 2018-12-14
product_id : 8
sequence : 1
status : VALID
updated : YES

PID:24301
TRACE:dbvisit_install.log

3. Confirm new DDC file 

oracle@dbvlab01[/usr/dbvisit/standby8/standby]: cd conf
oracle@dbvlab01[/usr/dbvisit/standby8/standby/conf]: ll
total 60
-rw-r--r-- 1 oracle oinstall 23150 Nov 14 14:25 dbv_test.env
-rw-r--r-- 1 oracle oinstall 33792 Nov 14 14:26 test.dbzvf

 6. Send and Apply Log manually 

1. Run dbvisit on Primary to send logs 

oracle@dbvlab01[/usr/dbvisit/standby8/standby]: ./dbvctl -d test
=============================================================
Dbvisit Standby Database Technology (8.0.24_0_ge6b43639) (pid 26548
dbvctl started on dbvlab01: Wed Nov 14 17:46:38 2018
=============================================================

>>> Obtaining information from standby database (RUN_INSPECT=Y)... done
Thread: 1 Archive log gap: 0. Transfer log gap: 3

Note FORCE_LOGGING is disabled in the primary database.

>>> Sending heartbeat message... skipped
>>> First time Dbvisit Standby runs, Dbvisit Standby configuration will be copied to
dbvlab03...
>>> Performing a log switch... done
>>> Transferring Log file(s) from test on dbvlab01 to dbvlab03 for thread 1:

thread 1 sequence 4 (o1_mf_1_4_fyqb640b_.arc)

=============================================================
dbvctl ended on dbvlab01: Wed Nov 14 17:47:05 2018
=============================================================

2. Run dbvisit on Standby to apply logs

oracle@dbvlab03[/usr/dbvisit/standby8/standby]: ./dbvctl -d test
=============================================================
Dbvisit Standby Database Technology (8.0.24_0_ge6b43639) (pid 17556)
dbvctl started on dbvlab03: Wed Nov 14 18:59:04 2018
=============================================================

>>> Sending heartbeat message... skipped

>>> Applying Log file(s) from dbvlab01 to test on dbvlab03:

thread 1 sequence 4 (1_4_992095872.arc)
Last applied log(s):
thread 1 sequence 4

Next SCN required for recovery 1250714 generated at 2018-11-14:17:46:59 +13:00.
Next required log thread 1 sequence 5

=============================================================
dbvctl ended on dbvlab03: Wed Nov 14 18:59:09 2018
=============================================================

3. Run Log Gap report on Primary

oracle@dbvlab01[/usr/dbvisit/standby8/standby]: ./dbvctl -d test -i
=============================================================
Dbvisit Standby Database Technology (8.0.24_0_ge6b43639) (pid 27572)
dbvctl started on dbvlab01: Wed Nov 14 19:09:40 2018
=============================================================

Dbvisit Standby log gap report for test thread 1 at 201811141909:
-------------------------------------------------------------
Destination database on dbvlab03 is at sequence: 4.
Source database on dbvlab01 is at log sequence: 5.
Source database on dbvlab01 is at archived log sequence: 4.
Dbvisit Standby last transfer log sequence: 4.
Dbvisit Standby last transfer at: 2018-11-14 17:47:05.

Archive log gap for thread 1: 0.
Transfer log gap for thread 1: 0.
Standby database time lag (DAYS-HH:MI:SS): +01:20:07.

=============================================================
dbvctl ended on dbvlab01: Wed Nov 14 19:09:49 2018
=============================================================

7. Post-installation steps. 

1. Start the daemon processes to allow Dbvisit Standby to run in the background (or enable normal schedules)

https://dbvisit.atlassian.net/wiki/spaces/DS8QSG/pages/106135893/Dbvisit+Standby+Scheduling#DbvisitStandbyScheduling-4.RunningDbvisitStandbyintheBackground

2. Enable email notification

https://dbvisit.atlassian.net/wiki/spaces/DS8QSG/pages/106135901/E-Mail+Notification+Configuration

3. Configure AMM (Archive Log Management Module) as required

https://dbvisit.atlassian.net/wiki/spaces/DS8QSG/pages/127860797/Dbvisit+Archive+Log+Management+Module+AMM