The Purpose of this Article is to explain how to deal with an error ORACLE_SID_DR cannot be set on dbvisit-vip when creating DDC file.
Problem Details
Problem Statement
When creating DDC configuration, error "ORACLE_SID_DR (or ORACLE_SID) cannot be set" appears for no apparent reason
Applicable Error Code
ORACLE_SID_DR cannot be set on dbvisit-standby-vip.
Please set variable ORACLE_SID_DR in
Dbvisit Database configuration (DDC) file dbv_PROD.env on dbvisit-primary-vip. Solution
Despite the message text, this error usually means that there is some kind of inconsistency between parameters which we set in DDC file and the actual environment.
In our case, when creating DDC file we tried to set variables:
RAC1_DR = 1:oracledb_01d:prod1:+ASM1
RAC2_DR = 2:oracledb_02dr:prod2:+ASM2
In this case, we made a typo, because 1st standby RAC hostname is actually "oracledb_01dr". Dbvisit Standby will try to match string oracledb_01d with actual hostname and is not successful - and as a result we get the error.
But same error can also appear, when we try to set IP address as node hostname:
RAC1_DR = 1:10.0.0.2:prod1:+ASM1
RAC2_DR = 2:10.0.0.3:prod2:+ASM2
Using IP addresses in RAC DDC variables is not supported and we will again receive error:
<<<< Dbvisit Standby terminated >>>>
PID:30885
TRACEFILE:30885_dbvctl_f_validate_ddc_prod_201902261428.trc
SERVER:dbvisit-standby-vip
ERROR_CODE:2109
ORACLE_SID_DR cannot be set on dbvisit-standby-vip. Please set variable ORACLE_SID_DR in
Dbvisit Database configuration (DDC) file dbv_prod.env on dbvisit-primary-vip.
Comments