We're here to help!

Dbvisit Standby and REDO logs of Type STANDBY

Follow


The issue occurs because Dbvisit Standby doesn't handle Logfile groups of TYPE STANDBY. These are for Dataguard configurations.

I have tested the same scenario and can confirm when I have standby logfiles in place on the primary database

SQL> alter database add standby logfile group 4;
SQL>  select member, type, group# from v$logfile;

MEMBER                          TYPE    GROUP#
------------------------------------------------------------------------ ------- ----------
/u01/app/oracle/oradata/XE/redo02.log            ONLINE      2
/u01/app/oracle/oradata/XE/redo03.log            ONLINE      3
/u01/app/oracle/oradata/XE/redo01.log            ONLINE      1
/u01/app/oracle/fast_recovery_area/XE/onlinelog/o1_mf_4_fyqqs61o_.log  STANDBY  4
/u01/app/oracle/oradata/XE/redo04.log            STANDBY  4
On the Primary server, the GS fails with the same issue that you have observed.

<<<< Dbvisit Standby terminated >>>>
PID:7447
TRACEFILE:7447_dbvctl_f_gs_convert_standby_XE_201811142149.trc
SERVER:dbvlab03
ERROR_CODE:2001
ORA-01184: logfile group 4 already exists (DBD ERROR: OCIStmtExecute)
>>>> Dbvisit Standby terminated <<<<
And the only solution is to drop the standby logfile group on the primary.
However, if the logfile group is created as a normal logfile group.

SQL> alter database add logfile group 4;
SQL>  select member, type, group# from v$logfile;

MEMBER                TYPE  GROUP#
---------------------------------------------------------------------------------------------------- ------- ----------
/u01/app/oracle/oradata/XE/redo02.log            ONLINE      2
/u01/app/oracle/oradata/XE/redo03.log            ONLINE      3
/u01/app/oracle/oradata/XE/redo01.log            ONLINE      1
/u01/app/oracle/fast_recovery_area/XE/onlinelog/o1_mf_4_fyqrrtxn_.log  ONLINE      4
/u01/app/oracle/oradata/XE/redo04.log            ONLINE      4

Then the GS completes without issue.

Have more questions? Submit a request

Comments