In this section, we will cover the creation of a new Dbvisit Standby Configuration, also known as creating a Dbvisit Database Configuration (DDC) file.
It is important that before you continue with these sections that you make sure the following pre-requisites have been performed:
On this page: |
For more detail on the pre-requisite steps please see System Requirements |
Dbvisit Standby version 8.0.x allows you to create a DDC (Dbvisit Standby configuration file) for the following scenarios:
If using Oracle RAC configurations:
In this section of the documentation, we will focus on the creation of the DDC file using the Command Line Interface (CLI).
There will be three sections to this:
When using Dbvisit Standby version 8 Grid Infrastructure (ASM) configurations must be Oracle 11.2 and above - with the latest patch set recommended. Using versions less than 11.2 is not supported. |
Below is a diagram providing an overview of the questions that will be asked when creating a new basic NON-RAC DDC file using the "dbvctl -o setup" command option (review clockwise):
It is important that before you continue with these sections that you make sure the pre-requisites have been performed.
To create a DDC file from the command line interface you will be using the “dbvctl -o setup” command.
Below is a summary of the environment that will be used in this example:
Note that this example is for a single instance environment and not for an Oracle RAC configuration |
The following questions will be asked during the configuration steps:
The end result of the above is that you will have a new DDC file and Repository as illustrated in the diagram below:
Below is an example of the described steps above to create the DDC file called dbv_DEV.env and repository dev.db in /usr/dbvisit/standby/conf/
[oracle@dbv101 /usr/dbvisit/standby]$ ./dbvctl -o setup ========================================================= Dbvisit Standby Database Technology (8.0.01.17322) 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]: Yes ========================================================= Dbvisit Standby setup begins. ========================================================= The following Oracle instance(s) have been found on this server: SID ORACLE_HOME === =========== 1) DEV /u01/app/oracle/product/11.2.0.4/dbhome_1 2) Enter own ORACLE_SID and ORACLE_HOME Please enter choice [] : 1 Is this correct? <Yes/No> [Yes]: =>ORACLE_SID will be: DEV =>ORACLE_HOME will be: /u01/app/oracle/product/11.2.0.4/dbhome_1 ------------------------------------------------------------------------------ Enter the primary server name. Note: The hostname is case sensitive on UNIX based systems. =>SOURCE is [dbv101]: dbv101 Your input: dbv101 Is this correct? <Yes/No> [Yes]: Yes Choice is dbv101 ------------------------------------------------------------------------------ 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/DEV]: /u01/app/oracle/dbvisit_arch/DEV Your input: /u01/app/oracle/dbvisit_arch/DEV Is this correct? <Yes/No> [Yes]: Yes Choice is /u01/app/oracle/dbvisit_arch/DEV ------------------------------------------------------------------------------ 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]: N Your input: N Is this correct? <Yes/No> [Yes]: Yes Choice is N ------------------------------------------------------------------------------ Enter the standby database hostname. If the standby database will be Oracle RAC enabled: Enter the the Virtual Hostname (linked to a Virtual IP) for standby database. This virtual hostname is attached to a 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 resouce in clusterware and must be enabled and started on one of the nodes before yo 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 hosts name here if you do not have a Virtual Hostname (attached to VIP) for the cluster configured. For non-RAC configurations specify the standby database server name here. =>DESTINATION is []: dbv102 Your input: dbv102 Is this correct? <Yes/No> [Yes]: Yes Choice is dbv102 ------------------------------------------------------------------------------ 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]: 7890 Your input: 7890 Is this correct? <Yes/No> [Yes]: Yes Choice is 7890 ------------------------------------------------------------------------------ Enter Dbvisit Standby installation directory on the standby server =>DBVISIT_BASE_DR is [/usr/dbvisit]: /usr/dbvisit Your input: /usr/dbvisit Is this correct? <Yes/No> [Yes]: Yes Choice is /usr/dbvisit ------------------------------------------------------------------------------ Enter ORACLE_HOME directory on the standby server =>ORACLE_HOME_DR is [/u01/app/oracle/product/11.2.0.4/dbhome_1]: Your input: /u01/app/oracle/product/11.2.0.4/dbhome_1 Is this correct? <Yes/No> [Yes]: Yes Choice is /u01/app/oracle/product/11.2.0.4/dbhome_1 ------------------------------------------------------------------------------ Enter DB_UNIQUE_NAME on the standby server =>DB_UNIQUE_NAME_DR is [DEV]: DEV Your input: DEV Is this correct? <Yes/No> [Yes]: Yes Choice is DEV ------------------------------------------------------------------------------ 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/dbvisit_arch/DEV]: /u01/app/oracle/dbvisit_arch/DEV Your input: /u01/app/oracle/dbvisit_arch/DEV Is this correct? <Yes/No> [Yes]: Yes Choice is /u01/app/oracle/dbvisit_arch/DEV ------------------------------------------------------------------------------ Enter ORACLE_SID on the standby server =>ORACLE_SID_DR is [DEV]: DEV Your input: DEV Is this correct? <Yes/No> [Yes]: Yes Choice is DEV ------------------------------------------------------------------------------ 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]: 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 [DEV]: DEV Your input: DEV Is this correct? <Yes/No> [Yes]: Yes Choice is DEV ------------------------------------------------------------------------------ Below are the list of configuration variables provided during the setup process: Configuration Variable Value Provided ====================== ============== ORACLE_SID DEV ORACLE_HOME /u01/app/oracle/product/11.2.0.4/dbhome_1 SOURCE dbv101 ARCHSOURCE /u01/app/oracle/dbvisit_arch/DEV RAC_DR N USE_SSH N DESTINATION dbv102 NETPORT 7890 DBVISIT_BASE_DR /usr/dbvisit ORACLE_HOME_DR /u01/app/oracle/product/11.2.0.4/dbhome_1 DB_UNIQUE_NAME_DR DEV ARCHDEST /u01/app/oracle/dbvisit_arch/DEV ORACLE_SID_DR DEV ENV_FILE DEV Are these variables correct? <Yes/No> [Yes]: Yes >>> Dbvisit Database configuration (DDC) file DEV created. >>> Dbvisit Database repository (DDR) DEV created. Repository Version 8.0 Software Version 8.0 Repository Status VALID PID:5639 TRACE:/usr/dbvisit/standby/log/dbvisit_install.log [oracle@dbv101 /usr/dbvisit/standby]$ [oracle@dbv101 /usr/dbvisit/standby]$ ls -l conf total 52 -rw-r--r-- 1 oracle oinstall 22406 Sep 6 10:45 dbv_DEV.env -rw-r--r-- 1 oracle oinstall 25600 Sep 6 10:45 dev.db [oracle@dbv101 /usr/dbvisit/standby]$ |
To create a DDC file from the command line interface you will be using the “dbvctl -o setup” command.
Below is a summary of the environment that will be used in this example:
The following questions will be asked during the configuration steps:
oracle@dbvlin503[/usr/dbvisit/8.0/standby]: ./dbvctl -o setup ========================================================= Dbvisit Standby Database Technology (8.0.01.15575) http://www.dbvisit.com ========================================================= =>dbvctl only needs to be run on the primary server. Is this the primary server? <Yes/No> [Yes]: 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]: Yes ========================================================= Dbvisit Standby setup begins. ========================================================= The following Oracle instance(s) have been found on this server: SID ORACLE_HOME === =========== 1) PROD /u01/app/oracle/product/11.2.0/db_1 2) Enter own ORACLE_SID and ORACLE_HOME Please enter choice [] : 1 Is this correct? <Yes/No> [Yes]: Yes =>ORACLE_SID will be: PROD =>ORACLE_HOME will be: /u01/app/oracle/product/11.2.0/db_1 ------------------------------------------------------------------------------ Enter the primary server name. Note: The hostname is case sensitive on UNIX based systems. =>SOURCE is [dbvlin503]: Your input: dbvlin503 Is this correct? <Yes/No> [Yes]: Yes Choice is dbvlin503 ------------------------------------------------------------------------------ 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_archdest/PROD]: /u01/app/oracle/dbvisit_archdest/PROD Your input: /u01/app/oracle/dbvisit_archdest/PROD Is this correct? <Yes/No> [Yes]: Yes Choice is /u01/app/oracle/dbvisit_archdest/PROD ------------------------------------------------------------------------------ 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]: N Your input: N Is this correct? <Yes/No> [Yes]: Yes Choice is N ------------------------------------------------------------------------------ Enter the standby database hostname. If the standby database will be Oracle RAC enabled: Enter the the Virtual Hostname (linked to a Virtual IP) for standby database. This virtual hostname is attached to a 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 resouce in clusterware and must be enabled and started on one of the nodes before yo 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 hosts name here if you do not have a Virtual Hostname (attached to VIP) for the cluster configured. For non-RAC configurations specify the standby database server name here. =>DESTINATION is []: dbvlin504 Your input: dbvlin504 Is this correct? <Yes/No> [Yes]: Yes Choice is dbvlin504 ------------------------------------------------------------------------------ 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]: 7890 Your input: 7890 Is this correct? <Yes/No> [Yes]: Yes Choice is 7890 ------------------------------------------------------------------------------ Enter Dbvisit Standby installation directory on the standby server =>DBVISIT_BASE_DR is [/usr/dbvisit/8.0]: Your input: /usr/dbvisit Is this correct? <Yes/No> [Yes]: Yes Choice is /usr/dbvisit ------------------------------------------------------------------------------ Enter ORACLE_HOME directory on the standby server =>ORACLE_HOME_DR is [/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 [PROD]: PROD Your input: PROD Is this correct? <Yes/No> [Yes]: Yes Choice is PROD ------------------------------------------------------------------------------ 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/dbvisit_archdest/PROD]: /u01/app/oracle/dbvisit_archdest/PROD Your input: /u01/app/oracle/dbvisit_archdest/PROD Is this correct? <Yes/No> [Yes]: Yes Choice is /u01/app/oracle/dbvisit_archdest/PROD ------------------------------------------------------------------------------ Enter ORACLE_SID on the standby server =>ORACLE_SID_DR is [PROD]: PROD Your input: PROD Is this correct? <Yes/No> [Yes]: Yes Choice is PROD ------------------------------------------------------------------------------ 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 []: +ASM Your input: +ASM Is this correct? <Yes/No> [Yes]: Yes Choice is +ASM ------------------------------------------------------------------------------ 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 [PROD]: PROD Your input: PROD Is this correct? <Yes/No> [Yes]: Yes Choice is PROD ------------------------------------------------------------------------------ Below are the list of configuration variables provided during the setup process: Configuration Variable Value Provided ====================== ============== ORACLE_SID PROD ORACLE_HOME /u01/app/oracle/product/11.2.0/db_1 SOURCE dbvlin503 ARCHSOURCE /u01/app/oracle/dbvisit_archdest/PROD USE_SSH N DESTINATION dbvlin504 NETPORT 7890 DBVISIT_BASE_DR /usr/dbvisit ORACLE_HOME_DR /u01/app/oracle/product/11.2.0/db_1 DB_UNIQUE_NAME_DR PROD ARCHDEST /u01/app/oracle/dbvisit_archdest/PROD ORACLE_SID_DR PROD ORACLE_SID_ASM_DR +ASM ENV_FILE PROD Are these variables correct? <Yes/No> [Yes]: Yes Dbvisit Database configuration (DDC) file /usr/dbvisit/standby/conf/dbv_PROD.env created Dbvisit Database repository (DDR) PROD created Repository Version 8.0 Software Version 8.0 Repository Status VALID PID:6231 TRACE:/usr/dbvisit/standby/tmp/dbvisit_install.log oracle@dbvlin503[/usr/dbvisit/standby]: cd conf oracle@dbvlin503[/usr/dbvisit/standby/conf]: ls -al total 56 drwxrwxr-x 2 oracle oinstall 4096 Apr 6 13:52 . drwxr-xr-x 11 oracle oinstall 4096 Apr 6 13:45 .. -rw-r--r-- 1 oracle oinstall 21478 Apr 6 13:52 dbv_PROD.env -rw-r--r-- 1 oracle oinstall 23552 Apr 6 13:52 prod.db |
If you are looking at using SSH, then make sure you answer these questions correct by specifying Y to using SSH, then supply the destination (standby server) name followed by the SSH Port number that will be used.
The default port that will be listed is 7890, you must adjust this to the SSH port you will be using.
It is important that SSH passwordless authentication be configured between the primary and standby servers prior to creating the Dbvisit Standby DDC configuration You should be able to ssh between the hosts without using a password. If an SSH banner is used, you can use the following two parameters to skip the banner output: SSH_SKIP_OUTPUT and SSH_SKIP_OUTPUT_LINES |
An example below shows how you can enable SSH during the DDC creation process:
... ... ------------------------------------------------------------------------------ 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]: Y Your input: Y Is this correct? <Yes/No> [Yes]: Yes Choice is Y ------------------------------------------------------------------------------ Enter the standby database hostname. If the standby database will be Oracle RAC enabled: Enter the the Virtual Hostname (linked to a Virtual IP) for standby database. This virtual hostname is attached to a 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 resouce in clusterware and must be enabled and started on one of the nodes before yo 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 hosts name here if you do not have a Virtual Hostname (attached to VIP) for the cluster configured. For non-RAC configurations specify the standby database server name here. =>DESTINATION is []: dbvlin504 Your input: dbvlin504 Is this correct? <Yes/No> [Yes]: Choice is dbvlin504 ------------------------------------------------------------------------------ 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]: 22 Your input: 22 Is this correct? <Yes/No> [Yes]: Choice is 22 ... ... |
The following example shows the steps taken to create a DDC file for an Oracle RAC primary with an Oracle RAC standby database.
(Click on the Images to enlarge them for a clear view)
It is important that the following pre-requisites are met:
The example environment consists of the following (Click on the Images to enlarge them for a clear view)
Note: The virtual IP will be started on one specific node on which you want to run Dbvisit Standby. This node will then also be configured to run Dbvnet and Dbvagent.
Note: The virtual IP will be started on one specific node on which you want to run Dbvisit Standby. This node will then also be configured to run Dbvnet and Dbvagent.
Example DDC creation steps using the command line interface (dbvctl):
oracle@kiwi81[/acfs/dbvisit/standby]: ./dbvctl -o setup --noprompt ========================================================= Dbvisit Standby Database Technology (8.0.01.18066) 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 ========================================================= Dbvisit Standby setup begins. ========================================================= The following Oracle instance(s) have been found on this server: SID ORACLE_HOME === =========== 1) DEV1 /u01/app/oracle/product/11.2.0/db_1 2) DEV /u01/app/oracle/product/11.2.0/db_1 3) Enter own ORACLE_SID and ORACLE_HOME Please enter choice [] : 1 =>ORACLE_SID will be: DEV1 =>ORACLE_HOME will be: /u01/app/oracle/product/11.2.0/db_1 ------------------------------------------------------------------------------ Enter the the virtual hostname (linked to a Virtual IP) for primary database. This virtual hostname is attached to a 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 resouce in clusterware and must be enabled and started on one of the nodes before yo continue with the setup. NOTE: 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 hosts name here if you do not have a Virtual Hostname (attached to VIP) for the cluster configured. =>SOURCE is []: kiwi812-vip Choice is kiwi812-vip ------------------------------------------------------------------------------ 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/DEV]: /acfs/dbvisit_arch/DEV Choice is /acfs/dbvisit_arch/DEV ------------------------------------------------------------------------------ Enter primary Oracle database instance for thread 1 =>RAC1_SID is [DEV1]: Choice is DEV1 ------------------------------------------------------------------------------ Enter primary host name for thread 1 =>RAC1_HOST is [kiwi81]: Choice is kiwi81 ------------------------------------------------------------------------------ Enter primary ASM instance for thread 1 =>RAC1_SID_ASM is [+ASM1]: Choice is +ASM1 ------------------------------------------------------------------------------ Enter primary Oracle database instance for thread 2 =>RAC2_SID is [DEV2]: Choice is DEV2 ------------------------------------------------------------------------------ Enter primary host name for thread 2 =>RAC2_HOST is [kiwi82]: Choice is kiwi82 ------------------------------------------------------------------------------ Enter primary ASM instance for thread 2 =>RAC2_SID_ASM is [+ASM2]: Choice is +ASM2 ------------------------------------------------------------------------------ Will the standby database be a RAC database? =>RAC_DR is [N]: Y Choice is Y ------------------------------------------------------------------------------ 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]: Choice is N ------------------------------------------------------------------------------ Enter the standby database hostname. If the standby database will be Oracle RAC enabled: Enter the the Virtual Hostname (linked to a Virtual IP) for standby database. This virtual hostname is attached to a 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 resouce in clusterware and must be enabled and started on one of the nodes before yo 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 hosts name here if you do not have a Virtual Hostname (attached to VIP) for the cluster configured. For non-RAC configurations specify the standby database server name here. =>DESTINATION is []: kiwi912-vip Choice is kiwi912-vip ------------------------------------------------------------------------------ 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]: Choice is 7890 ------------------------------------------------------------------------------ Enter Dbvisit Standby installation directory on the standby server =>DBVISIT_BASE_DR is [/acfs/dbvisit]: Choice is /acfs/dbvisit ------------------------------------------------------------------------------ Enter ORACLE_HOME directory on the standby server =>ORACLE_HOME_DR is [/u01/app/oracle/product/11.2.0/db_1]: Choice is /u01/app/oracle/product/11.2.0/db_1 ------------------------------------------------------------------------------ Enter DB_UNIQUE_NAME on the standby server =>DB_UNIQUE_NAME_DR is [DEV]: Choice is DEV ------------------------------------------------------------------------------ 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 [/acfs/dbvisit_arch/DEV]: Choice is /acfs/dbvisit_arch/DEV ------------------------------------------------------------------------------ Enter standby Oracle database instance for thread 1 =>RAC1_SID_DR is [DEV1]: Choice is DEV1 ------------------------------------------------------------------------------ Enter standby host name for thread 1 =>RAC1_HOST_DR is []: kiwi91 Choice is kiwi91 ------------------------------------------------------------------------------ Enter standby ASM instance for thread 1 =>RAC1_SID_ASM_DR is [+ASM1]: Choice is +ASM1 ------------------------------------------------------------------------------ Enter standby Oracle database instance for thread 2 =>RAC2_SID_DR is [DEV2]: Choice is DEV2 ------------------------------------------------------------------------------ Enter standby host name for thread 2 =>RAC2_HOST_DR is []: kiwi92 Choice is kiwi92 ------------------------------------------------------------------------------ Enter standby ASM instance for thread 2 =>RAC2_SID_ASM_DR is [+ASM2]: Choice is +ASM2 ------------------------------------------------------------------------------ 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 [DEV]: Choice is DEV ------------------------------------------------------------------------------ Below are the list of configuration variables provided during the setup process: Configuration Variable Value Provided ====================== ============== ORACLE_SID DEV1 ORACLE_HOME /u01/app/oracle/product/11.2.0/db_1 SOURCE kiwi812-vip ARCHSOURCE /acfs/dbvisit_arch/DEV RAC1_THREAD 1 RAC1_SID DEV1 RAC1_HOST kiwi81 RAC1_SID_ASM +ASM1 RAC2_THREAD 2 RAC2_SID DEV2 RAC2_HOST kiwi82 RAC2_SID_ASM +ASM2 RAC_DR Y USE_SSH N DESTINATION kiwi912-vip NETPORT 7890 DBVISIT_BASE_DR /acfs/dbvisit ORACLE_HOME_DR /u01/app/oracle/product/11.2.0/db_1 DB_UNIQUE_NAME_DR DEV ARCHDEST /acfs/dbvisit_arch/DEV RAC1_SID_DR DEV1 RAC1_HOST_DR kiwi91 RAC1_SID_ASM_DR +ASM1 RAC2_SID_DR DEV2 RAC2_HOST_DR kiwi92 RAC2_SID_ASM_DR +ASM2 ENV_FILE DEV Are these variables correct? <Yes/No> [Yes]: >>> Dbvisit Database configuration (DDC) file DEV created. >>> Dbvisit Database repository (DDR) DEV created. Repository Version 8.0 Software Version 8.0 Repository Status VALID PID:28479 TRACE:dbvisit_install.log oracle@kiwi81[/acfs/dbvisit/standby]: oracle@kiwi81[/acfs/dbvisit/standby]: ls conf/ dbv_DEV.env dev.db |
In the example below, we show you how to create a DDC file where the primary environment is a two node RAC environment (same RAC as mentioned in above example - kiwi81 and kiwi82).
The Virtual IP that will be used by Dbvisit Standby on the primary RAC environment is already configured (see example 2.4 above).
The standby database environment in this example will be a Single Instance standby database using just normal filesystem based storage.
Ideally, if your Primary database is using ASM, you should use ASM on the standby as well - with the same disk groups configured. But in this example, we will show the creation of the DDC where the standby is a single instance with just filesystem based storage.
The standby database server is called kiwi91 in this example, the DBVISIT_BASE is /usr/dbvisit and the Oracle database software installed is exactly the same as what is used on the primary.
Example:
oracle@kiwi81[/acfs/dbvisit/standby]: ./dbvctl -o setup --noprompt ========================================================= Dbvisit Standby Database Technology (8.0.01.18066) 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 ========================================================= Dbvisit Standby setup begins. ========================================================= The following Oracle instance(s) have been found on this server: SID ORACLE_HOME === =========== 1) DEV1 /u01/app/oracle/product/11.2.0/db_1 2) DEV /u01/app/oracle/product/11.2.0/db_1 3) Enter own ORACLE_SID and ORACLE_HOME Please enter choice [] : 1 =>ORACLE_SID will be: DEV1 =>ORACLE_HOME will be: /u01/app/oracle/product/11.2.0/db_1 ------------------------------------------------------------------------------ Enter the the virtual hostname (linked to a Virtual IP) for primary database. This virtual hostname is attached to a 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 resouce in clusterware and must be enabled and started on one of the nodes before yo continue with the setup. NOTE: 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 hosts name here if you do not have a Virtual Hostname (attached to VIP) for the cluster configured. =>SOURCE is []: kiwi812-vip Choice is kiwi812-vip ------------------------------------------------------------------------------ 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/DEV]: /acfs/dbvisit_arch/DEV Choice is /acfs/dbvisit_arch/DEV ------------------------------------------------------------------------------ Enter primary Oracle database instance for thread 1 =>RAC1_SID is [DEV1]: Choice is DEV1 ------------------------------------------------------------------------------ Enter primary host name for thread 1 =>RAC1_HOST is [kiwi81]: Choice is kiwi81 ------------------------------------------------------------------------------ Enter primary ASM instance for thread 1 =>RAC1_SID_ASM is [+ASM1]: Choice is +ASM1 ------------------------------------------------------------------------------ Enter primary Oracle database instance for thread 2 =>RAC2_SID is [DEV2]: Choice is DEV2 ------------------------------------------------------------------------------ Enter primary host name for thread 2 =>RAC2_HOST is [kiwi82]: Choice is kiwi82 ------------------------------------------------------------------------------ Enter primary ASM instance for thread 2 =>RAC2_SID_ASM is [+ASM2]: Choice is +ASM2 ------------------------------------------------------------------------------ Will the standby database be a RAC database? =>RAC_DR is [N]: Choice is N ------------------------------------------------------------------------------ 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]: Choice is N ------------------------------------------------------------------------------ Enter the standby database hostname. If the standby database will be Oracle RAC enabled: Enter the the Virtual Hostname (linked to a Virtual IP) for standby database. This virtual hostname is attached to a 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 resouce in clusterware and must be enabled and started on one of the nodes before yo 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 hosts name here if you do not have a Virtual Hostname (attached to VIP) for the cluster configured. For non-RAC configurations specify the standby database server name here. =>DESTINATION is []: kiwi91 Choice is kiwi91 ------------------------------------------------------------------------------ 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]: Choice is 7890 ------------------------------------------------------------------------------ Enter Dbvisit Standby installation directory on the standby server =>DBVISIT_BASE_DR is [/acfs/dbvisit]: /usr/dbvisit Choice is /usr/dbvisit ------------------------------------------------------------------------------ Enter ORACLE_HOME directory on the standby server =>ORACLE_HOME_DR is [/u01/app/oracle/product/11.2.0/db_1]: Choice is /u01/app/oracle/product/11.2.0/db_1 ------------------------------------------------------------------------------ Enter DB_UNIQUE_NAME on the standby server =>DB_UNIQUE_NAME_DR is [DEV]: Choice is DEV ------------------------------------------------------------------------------ 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 [/acfs/dbvisit_arch/DEV]: /u01/app/oracle/dbvisit_arch/DEV Choice is /u01/app/oracle/dbvisit_arch/DEV ------------------------------------------------------------------------------ Enter ORACLE_SID on the standby server =>ORACLE_SID_DR is [DEV1]: DEV Choice is DEV ------------------------------------------------------------------------------ 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 []: 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 [DEV]: Choice is DEV ------------------------------------------------------------------------------ Below are the list of configuration variables provided during the setup process: Configuration Variable Value Provided ====================== ============== ORACLE_SID DEV1 ORACLE_HOME /u01/app/oracle/product/11.2.0/db_1 SOURCE kiwi812-vip ARCHSOURCE /acfs/dbvisit_arch/DEV RAC1_THREAD 1 RAC1_SID DEV1 RAC1_HOST kiwi81 RAC1_SID_ASM +ASM1 RAC2_THREAD 2 RAC2_SID DEV2 RAC2_HOST kiwi82 RAC2_SID_ASM +ASM2 RAC_DR N USE_SSH N DESTINATION kiwi91 NETPORT 7890 DBVISIT_BASE_DR /usr/dbvisit ORACLE_HOME_DR /u01/app/oracle/product/11.2.0/db_1 DB_UNIQUE_NAME_DR DEV ARCHDEST /u01/app/oracle/dbvisit_arch/DEV ORACLE_SID_DR DEV ENV_FILE DEV Are these variables correct? <Yes/No> [Yes]: >>> Dbvisit Database configuration (DDC) file DEV created. >>> Dbvisit Database repository (DDR) DEV created. Repository Version 8.0 Software Version 8.0 Repository Status VALID PID:28418 TRACE:dbvisit_install.log oracle@kiwi81[/acfs/dbvisit/standby]: ls -l conf total 52 -rw-r--r-- 1 oracle oinstall 22533 Nov 6 20:54 dbv_DEV.env -rw-r--r-- 1 oracle oinstall 25600 Nov 6 20:54 dev.db |
This section will provide an overview of creating the DDC file using the Central Console (GUI) interface.
Before you can add a new DDC, it is important to make sure you have added the HOSTS (primary and standby servers) to the Central Console. This can be done by navigating to the "Manage Hosts" option and adding the primary and standby servers there. You must have Dbvisit Standby version 8 Core options already installed on these hosts and have the Dbvisit Agents running prior to adding these hosts. You will also need the specific passphrase for the host. For more detail please see the "Manage Hosts" section here ...
Please note that when creating a new DDC file in Dbvisit Standby version 8 the following default options are used:
This section will guide you through the steps to create a Dbvisit Standby Configuration (DDC) file using the version 8 Central Console (Web-Based User Interface)
The steps to create the DDC files are:
From the Main menu screen seen below, select "Manage Configurations"
During the Initial Configuration, there will not be any DDC files known to the Central Console.
If you already have Dbvisit Standby version 8 DDC files on the primary and standby hosts (you might have created them via the command line and want to inform the Central Console of its existence), you can Import them into the Central Console by clicking the Import button [2], selecting the Host you want to import from, and then selecting the DDC. Once imported, you will be able to see these existing DDC files on the main "Manage Configurations" screen.
The example here is for a cleanly installed system where no DDC files exist yet. The next steps will guide you through the process of creating the new DDC file.
From the screen below click on the "NEW" [1] button to start the process.
The Source host can be seen as the Primary Database Server.
If you are looking at creating a Cascading Standby Database - where the secondary standby database is "feeding" of a standby database, you must make sure you select the SOURCE host where this standby database (the source) is running. |
The Next step is to accept or decline the license agreement. The process can only continue if you accept the license agreement.
Dbvisit Standby version 8 will look at the /etc/oratab file for any known databases on the source server. If you are not using this file it is recommended you do add the databases to this file.
For more details on the use of the /etc/oratab file please consult the Oracle Documentation. The normal format of an entry in this file is: <SID>:<ORACLE_HOME>:<AutoStart-Yes-or-No>, example:
DEV:/u01/app/oracle/product/11.2.0.4/dbhome1:N
If you are using a Windows-based system, the details will be extracted from the Windows Registry Entries - which is created by the DBCA on creation.
If the Database you have running on the system is not listed in the dropdown list, you may add it by selecting the "Manual Entry" option.
This section allows you to specify 2 specific options - as highlighted in the image below with the number 4.
The ARCSOURCE Location:
The Network Communication Option:
As pointed out by the red marked number 5 in the above image, you now need to select the destination also known as the "Standby Host"
In this example, the standby server is "dbv2" which is selected. Once selected, the Standby Database Options are enabled - see Step 7 below.
The Standby Database Options are highlighted with the number 6 (and arrows) in the image below. These include:
Once you have entered all the details - click on "SUBMIT" and the DDC file creation will start. This process only takes a few seconds.
Once complete you will see the DDC file listed under the Configurations menu option.
The following are highlighted in the image above for the DDC that was created named DEV:
It might be required to Edit the DDC to enable additional options - such as enabling Email Notifications or making changes to the default Archivelog Management Module (AMM) parameters.
The two Figures below provide you with a summary of the options available: