Try to drop standby redo groups and then recreate them, get below errors:
SQL> alter database drop logfile group 1;
alter database drop logfile group 1
*
ERROR at line 1:
ORA-01275: Operation DROP LOGFILE is not allowed
if standby file management is automatic.
Read more of this content when you subscribe today.
Read more of this content when you subscribe today.
Read more of this content when you subscribe today.
In Data Guard, for some reason, standby database rule are incorrectly shown as primary database, while primary database shows as standby rule.
DGMGRL> show configuration;
Configuration - TESTDB
Protection Mode: MaxPerformance
Databases:
TESTDBSTY - Primary database
Error: ORA-16810: multiple errors or warnings detected
for the database
TESTDB - Physical standby database
Error: ORA-16810: multiple errors or warnings detected
for the database
Fast-Start Failover: DISABLED
Configuration Status:
ERROR
DGMGRL> show database "TESTDBSTY";
Database - TESTDBSTY
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s): TESTDBSTY
Error: ORA-16782: instance not open for read and write access
Database Error(s):
ORA-16816: incorrect database role
Database Status:
ERROR
How to fix it ?
Read more of this content when you subscribe today.
In 11g, duplicate a standby database from active database with “RMAN-05001” error:
RMAN> run {
duplicate target database for standby from active database;
}
RMAN-05001: auxiliary file name /u02/oradata/TESTDBSTY/sysaux01.dbf
conflicts with a file used by the target database
The issue is a bug, it seems the file system for both primary and standby database are the same, though “db_file_name_convert” and “log_file_name_convert” are configured already.
Add “NOFILENAMECHECK” option into duplicate RMAN command:
RMAN> run
{
duplicate target database for standby
from active database nofilenamecheck;
}
This issue does not happen on 12c, so it seems a bug for 11g.
Make DBA Life Easy 