...
When installing Dbvisit Standby on Oracle RAC environments, please review this section, if you are using Single instance configurations please continue with the next section below.
For Oracle RAC installations please see - Configure Oracle RAC Primary with Oracle RAC Standby
| Note | ||
|---|---|---|
| ||
Note: For Oracle RAC environments you will need to create a DDC file on all nodes. To do this you have to run the setup on all the RAC nodes. During the configuration you will be asked if it is the 1st node you are configuring, state yes, that will then ensure the Repository is created as part of the first node setup. When creating the second node's DDC file, you can specify No to this question as the repository would have been already created from node 1. If the standby is RAC, we can only create a single instance (multithread) db with our process. Once CSD (create standby database) successfully completes, you will have to convert the standby to RAC manually. |
...
- License Agreement
- Do you want the quick setup (recommended)
- Confirm PATH variable
- Confirm /etc/oratab location
- Select Database to be configured in a standby configuration
- Confirm operating system account – oracle
- Confirm Dbvnet port to be used (7890)
- Specify if compression should be used
- Confirm server name
- Confirm repository user (dbvisit7) and password
- Provide ASM SID if used (+ASM if using Single instance and +ASM1 or +ASM2 etc if using RAC - specify the ASM instance that is running on this server)
- Provide standby server name
- Provide name for standby database
- Confirm software Dbvisit Base directory on standby server
Specify the Dbvisit ARCHDEST location
Note Please note that the Dbvisit Standby ARCHDEST location must exist on both primary (if using RAC - on all primary nodes) and standby server. It must be located on normal filesystem, not ASM. This location is not the same as the Oracle Database archive destinations, but is specific to Dbvisit Standby.
The Dbvisit Standby ARCHDEST should not be located in the primary or standby database FRA (Fast/Flash Recovery Area).
It is also important to make sure that you do not have the Dbvisit ARCHDEST set to the same as what you database archive log destination is. The ARCHDEST is specific to Dbvisit Standby and is not the same as the Oracle database archive log destinations, and should not be set to a different location.
The Dbvisit Standby ARCHDEST can not be specified as an ASM location.
- Provide ASM SID for standby server, if used (+ASM for single instance environments, but if the standby is located on a RAC environment make sure to specify the RAC ASM instance on that node, example +ASM1 or +ASM2 etc.)
- Provide email settings for email notifications
- Confirm if the Archivelog Management Module (AMM) should be used on primary and standby
- Review settings and provide a name for your DDC (ORACLE_SID in most cases)
- DDC file is created in ../dbvisit/standby/conf/
- The Dbvisit Repository is created in the primary database
...