For KVM, Dbvisit Multiplatform only supports homogeneous environments with both Primary and Standby servers being ODA KVM.
Prerequisites
When planning ODA KVM deployment, in addition to usual Dbvisit prerequisites following must be enabled:
it must be possible to connect from primary DB KVM to primary and standby ASM Baremetal
it must be possible to connect from standby DB KVM to primary and standby ASM Baremetal
This is needed for typical actions such as create standby database or synchronization.
it must be possible to connect from primary ASM Baremetal to standby ASM Baremetal. And vice versa for the switchover in opposite direction
This is required because during switchover we copy the redo from primary ASM Baremetal => standby ASM Baremetal.
All connections above will be done with the same hostname for primary ASM Baremetal and standby ASM baremetal. Because there are only 2 EZ Connect parameters in DDC which will be utilized for connection to Baremetal ASM:
SYS_EZCONNECT_ASM SYS_EZCONNECT_ASM_DR
Creating New Configuration
When creating the configuration on ODA KVM, the process is very similar to the standard Linux to Linux configurations (as described in Create Oracle Configuration). The differences are the following:
When ODA KVM is identified, a new box with ASM details is displayed. For KVM the ASM instance runs directly on ODA bare metal, therefore the user needs to provide the hostname/ip address of the ODA server (e.g. see 10.100.100.250 in the screenshot below). Other connection details have to allow Dbvisit components to be able to connect from KVM to ASM instance running on ODA server via SQLNet.
Creating Standby Database
When creating the Standby database, a couple of spfile parameters need to be changed. Please navigate to Create DR Database for Oracle for more details.
Comments