Mani's Blog

December 14, 2012

Error: ORA-16751: failed to switchover to physical standby database. Both Oracle DB says Physical Standby

I ran the switchover to dataguard box.  I ran into issue where both database became physical standby.

Problem:

DGMGRL for Linux: Version 11.1.0.7.0 – 64bit Production

Copyright (c) 2000, 2005, Oracle. All rights reserved.

Welcome to DGMGRL, type “help” for information.
DGMGRL> connect sys/oracle
Connected.
DGMGRL> swtichover to xnodb01c
Unrecognized command “swtichover”, try “help”
DGMGRL> switchover to xnodb01c
Performing switchover NOW, please wait…
Error: ORA-16751: failed to switchover to physical standby database

Failed.
Unable to switchover, primary database is still “xnodb01cdg”

Solution:

Now I have to choose one database and promote as primary.   Following steps worked well for me.

SQL> select database_role from v$database;

DATABASE_ROLE
—————-
PHYSICAL STANDBY

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.

Total System Global Area 2.6724E+10 bytes
Fixed Size            2160272 bytes
Variable Size         8321501552 bytes
Database Buffers     1.8254E+10 bytes
Redo Buffers          146423808 bytes
Database mounted.
SQL> alter database recover managed standby database cancel;
alter database recover managed standby database cancel
*
ERROR at line 1:
ORA-16136: Managed Standby Recovery not active

SQL> alter database recover managed standby database finish;

Database altered.

SQL> ALTER database commit to switchover to primary with session shutdown;

Database altered.

SQL> alter database open;

Database altered.

SQL>  select database_role from v$database;

DATABASE_ROLE
—————-
PRIMARY

SQL> alter system switch logfile;

System altered.

SQL>

Now other DB functioning as Physical Standby with no issues.

October 8, 2012

ORA-16789: standby redo logs not configured

Filed under: Data Guard Broker,Database,Dataguard,Oracle — mani @ 9:42 pm
Tags: ,

In our environment, Dataguard Manager log was showing following errors.

DG 2012-10-08-21:23:11        0 2 0 RSM0: HEALTH CHECK WARNING: ORA-16789: standby redo logs not configured
DG 2012-10-08-21:23:11        0 2 760559130 Operation CTL_GET_STATUS continuing with warning, status = ORA-16789
DG 2012-10-08-21:23:11        0 2 760559130 Operation CTL_GET_STATUS continuing with warning, status = ORA-16809
DG 2012-10-08-21:24:11        0 2 0 RSM Error: LogXptMode value ‘ASYNC’ of requires this database to have status redo logs, but they are not configured.

Show Configuration reports warning “ORA-16608: one or more databases have warnings”

DGMGRL> show configuration

Configuration
Name:                aclu1c
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
xnodb01c   – Primary database
xnodb01cdg – Physical standby database

Fast-Start Failover: DISABLED

Current status for “aclu1c”:
Warning: ORA-16608: one or more databases have warnings

show database verbose xnodb01cdg  returned success.

show database verbose xnodb01c returned errors, so I am sure the primary DB has issue.
Solution: is to add standby log files to primary DB.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 31 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 32 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 33 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 34 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 35 ( ‘+XN_DATA’) SIZE 209715200 reuse;

Database altered.

Problem solved:

After adding all above standby log files,   Dataguard log stopped reporting the error.  Also dgmgrl stopped reporting the warnings.

DGMGRL> show configuration

Configuration
Name:                aclu1c
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
xnodb01c   – Primary database
xnodb01cdg – Physical standby database

Fast-Start Failover: DISABLED

Current status for “aclu1c”:
SUCCESS

DGMGRL>

 

September 20, 2012

ORA-16792: configurable property value is inconsistent with database setting

I have DG broker configured on stand-alone database servers (primary and standby).  After I migrated standby database to new ASM diskgroup I ran into issue “Warning: ORA-16608: one or more databases have warnings” and “ORA-16792: configurable property value is inconsistent with database setting”

Restarting the Data guard broker fixed the issue.

DGMGRL> show configuration

Configuration
Name:                contact
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
xnodbcntdg – Primary database
xnodbcnt   – Physical standby database

Fast-Start Failover: DISABLED

Current status for “contact”:
Warning: ORA-16608: one or more databases have warnings

DGMGRL> show database xnodbcnt

Database
Name:            xnodbcnt
Role:            PHYSICAL STANDBY
Enabled:         YES
Intended State:  APPLY-ON
Instance(s):
XNODBCNT

Current status for “xnodbcnt”:
Warning: ORA-16792: configurable property value is inconsistent with database setting

I just restarted as below.

 

SQL> alter system set dg_broker_start=false scope=both;

System altered.

SQL> alter system set dg_broker_start=true scope=both;

System altered.

SQL>

Then the issue is gone.

 

DGMGRL> show database xnodbcnt

Database
Name:            xnodbcnt
Role:            PHYSICAL STANDBY
Enabled:         YES
Intended State:  APPLY-ON
Instance(s):
XNODBCNT

Current status for “xnodbcnt”:
SUCCESS

DGMGRL>

September 17, 2012

Warning: ORA-16607: one or more databases have failed Error: ORA-16816: incorrect database role

Filed under: Data Guard Broker,Database,Dataguard,Oracle — mani @ 10:01 pm
Tags:

I have Data guard broker configured on my Primary and Standby database servers.  For some reason we had to failover using SQL commnad (didn’t use DG manager).  Later on dgmgrl shows errors as below.

DGMGRL> show configuration

Configuration
Name:                CONTACT
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
XNODBCNT   – Primary database
XNODBCNTDG – Physical standby database

Fast-Start Failover: DISABLED

Current status for “CONTACT”:
Warning: ORA-16607: one or more databases have failed

DGMGRL> show database ‘XNODBCNT’

Database
Name:            XNODBCNT
Role:            PRIMARY
Enabled:         YES
Intended State:  TRANSPORT-ON
Instance(s):
XNODBCNT

Current status for “XNODBCNT”:
Error: ORA-16816: incorrect database role

Solution: I tried many thing like enabling/disabling configuration, database and other nothing helped,  I had reconfigure it again as below to make DG broker to work properly.

DGMGRL> create configuration CONTACT as primary database is XNODBCNTDG connect identifier is xnodbcntdg;
Configuration “contact” created with primary database “xnodbcntdg”
DGMGRL> add database XNODBCNT as connect identifier is xnodbcnt maintained as physical;
Database “xnodbcnt” added
DGMGRL> show configuration;

Configuration
Name:                contact
Enabled:             NO
Protection Mode:     MaxPerformance
Databases:
xnodbcntdg – Primary database
xnodbcnt   – Physical standby database

Fast-Start Failover: DISABLED

Current status for “contact”:
DISABLED

DGMGRL> enable configuration
Enabled.
DGMGRL> show configuration verbose

Configuration
Name:                contact
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
xnodbcntdg – Primary database
xnodbcnt   – Physical standby database

Fast-Start Failover: DISABLED

Current status for “contact”:
Warning: ORA-16610: command “EDIT DATABASE xnodbcnt SET PROPERTY” in progress

DGMGRL> show configuration verbose

Configuration
Name:                contact
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
xnodbcntdg – Primary database
xnodbcnt   – Physical standby database

Fast-Start Failover: DISABLED

Current status for “contact”:
SUCCESS

DGMGRL>

Create a free website or blog at WordPress.com.