Data Guard Application Failover

Hi,
We've setup a physical standby database on 11.2.0.1.
I'd request for opinions on how well to manage application fail-over when we switchover/fail over the database. The application connects to the database through TNS name resolution.
Some people have suggested we edit the tns entry for the application server and point it to a virtual hostname, which will resolve to one IP address, then change this IP address only on the DNS to point to the new primary during switchover. But this looks to have challenges since the service names for the primary and standy instances are different, so the tns entry has to be modified.
Any suggestions on best application failover?
dula

Dan,
You are most welcome to OTN
I have a question regarding Active Data Guard and any potential outage that might be encounted in a failover or switchover.Switchover/Failover wont happen without your interaction.
If you configure FSFO with protection mode(Ex: Max Availability)
Read-Only application is accessing Active Data Guard database on standby. Would there be any outage if the standby were made the primary ?What outage? If standby made to primary(failover) then you may less very minor data based on how redo transport you are configuring. if you are using ARCH then the lost would only data+changes what ever in Archive log file, If you using LGWR then its very very less. So recommended to use redo transport as LGWR
I have assumed no, but there is a debate in my office that there would be a small outage due to change in roles. We are using broker also.If you change role, then there would be no outage.
For more details refer this oracle documentation http://www.oracle.com/technetwork/articles/smiley-fsfo-084973.html
Edited by: CKPT on Jan 12, 2012 4:50 PM

Similar Messages

Configure about the DATA GUARD APPLICATION on ORACLE 9i platform

I have worked on Oracle 9i (9.2.0.1) platform. I have installed Oracle 9i server edition in my machine, and created one database name ORCL.
I want to configure DATA GUARD APPLICATION in my machine... is it possible?
if it is then how can I do this...

Yes, it is possible.
Please refer to the Dataguard Concepts and Administration Manual for installation guidance.
Please do not bother to come back to ask further doc questions, showing you are not prepared to do your own work.
Sybrand Bakker
Senior Oracle DBA

Data Guard Failover after primary site network failure or disconnect.

Hello Experts:
I'll try to be clear and specific with my issue:
Environment:
Two nodes with NO shared storage (I don't have an Observer running).
Veritas Cluser Server (VCS) with Data Guar Agent. (I don't use the Broker. Data Guard agent "takes care" of the switchover and failover).
Two single instance databases, one per node. NO RAC.
What I'm being able to perform with no issues:
Manual switch(over) of the primary database by running VCS command "hagrp -switch oraDG_group -to standby_node"
Automatic fail(over) when primary node is rebooted with "reboot" or "init"
Automatic fail(over) when primary node is shut down with "shutdown".
What I'm NOT being able to perform:
If I manually unplug the network cables from the primary site (all the network, not only the link between primary and standby node so, it's like a server unplug from the energy source).
Same situation happens if I manually disconnect the server from the power.
This is the alert logs I have:
This is the portion of the alert log at Standby site when Real Time Replication is working fine:
Recovery of Online Redo Log: Thread 1 Group 4 Seq 7 Reading mem 0
Mem# 0: /u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log
At this moment, node1 (Primary) is completely disconnected from the network. SEE at the end when the database (standby which should be converted to PRIMARY) is not getting all the archived logs from the Primary due to the abnormal disconnect from the network:
Identified End-Of-Redo (failover) for thread 1 sequence 7 at SCN 0xffff.ffffffff
Incomplete Recovery applied until change 15922544 time 12/23/2013 17:12:48
Media Recovery Complete (primary_db)
Terminal Recovery: successful completion
Forcing ARSCN to IRSCN for TR 0:15922544
Mon Dec 23 17:13:22 2013
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance primary_db - Archival ErrorAttempt to set limbo arscn 0:15922544 irscn 0:15922544
ORA-16014: log 4 sequence# 7 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
Resetting standby activation ID 2071848820 (0x7b7de774)
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
Mon Dec 23 17:13:33 2013
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
Terminal Recovery: applying standby redo logs.
Terminal Recovery: thread 1 seq# 7 redo required
Terminal Recovery:
Recovery of Online Redo Log: Thread 1 Group 4 Seq 7 Reading mem 0
Mem# 0: /u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log
Identified End-Of-Redo (failover) for thread 1 sequence 7 at SCN 0xffff.ffffffff
Incomplete Recovery applied until change 15922544 time 12/23/2013 17:12:48
Media Recovery Complete (primary_db)
Terminal Recovery: successful completion
Forcing ARSCN to IRSCN for TR 0:15922544
Mon Dec 23 17:13:22 2013
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance primary_db - Archival ErrorAttempt to set limbo arscn 0:15922544 irscn 0:15922544
ORA-16014: log 4 sequence# 7 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
Resetting standby activation ID 2071848820 (0x7b7de774)
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
Mon Dec 23 17:13:33 2013
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
Attempt to do a Terminal Recovery (primary_db)
Media Recovery Start: Managed Standby Recovery (primary_db)
started logmerger process
Mon Dec 23 17:13:33 2013
Managed Standby Recovery not using Real Time Apply
Media Recovery failed with error 16157
Recovery Slave PR00 previously exited with exception 283
ORA-283 signalled during: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH...
Mon Dec 23 17:13:34 2013
Shutting down instance (immediate)
Shutting down instance: further logons disabled
Stopping background process MMNL
Stopping background process MMON
License high water mark = 38
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
ALTER DATABASE DISMOUNT
Shutting down archive processes
Archiving is disabled
Mon Dec 23 17:13:38 2013
Mon Dec 23 17:13:38 2013
Mon Dec 23 17:13:38 2013
ARCH shutting downARCH shutting down
ARCH shutting down
ARC0: Relinquishing active heartbeat ARCH role
ARC2: Archival stopped
ARC0: Archival stopped
ARC1: Archival stopped
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Mon Dec 23 17:13:40 2013
Stopping background process VKTM
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Mon Dec 23 17:13:43 2013
Instance shutdown complete
Mon Dec 23 17:13:44 2013
Adjusting the default value of parameter parallel_max_servers
from 1280 to 470 due to the value of parameter processes (500)
Starting ORACLE instance (normal)
************************ Large Pages Information *******************
Per process system memlock (soft) limit = 64 KB
Total Shared Global Region in Large Pages = 0 KB (0%)
Large Pages used by this instance: 0 (0 KB)
Large Pages unused system wide = 0 (0 KB)
Large Pages configured system wide = 0 (0 KB)
Large Page size = 2048 KB
RECOMMENDATION:
Total System Global Area size is 3762 MB. For optimal performance,
prior to the next instance restart:
1. Increase the number of unused large pages by
at least 1881 (page size 2048 KB, total size 3762 MB) system wide to
get 100% of the System Global Area allocated with large pages
2. Large pages are automatically locked into physical memory.
Increase the per process memlock (soft) limit to at least 3770 MB to lock
100% System Global Area's large pages into physical memory
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Initial number of CPU is 32
Number of processor cores in the system is 16
Number of processor sockets in the system is 2
CELL communication is configured to use 0 interface(s):
CELL IP affinity details:
    NUMA status: NUMA system w/ 2 process groups
    cellaffinity.ora status: cannot find affinity map at '/etc/oracle/cell/network-config/cellaffinity.ora' (see trace file for details)
CELL communication will use 1 IP group(s):
    Grp 0:
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =88
LICENSE_MAX_USERS = 0
SYS auditing is disabled
NUMA system with 2 nodes detected
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
ORACLE_HOME = /u01/oracle/product/11.2.0.4
System name:    Linux
Node name:      node2.localdomain
Release:        2.6.32-131.0.15.el6.x86_64
Version:        #1 SMP Tue May 10 15:42:40 EDT 2011
Machine:        x86_64
Using parameter settings in server-side spfile /u01/oracle/product/11.2.0.4/dbs/spfileprimary_db.ora
System parameters with non-default values:
processes                = 500
sga_target               = 3760M
control_files            = "/u02/oracle/orafiles/primary_db/control01.ctl"
control_files            = "/u01/oracle/fast_recovery_area/primary_db/control02.ctl"
db_file_name_convert     = "standby_db"
db_file_name_convert     = "primary_db"
log_file_name_convert    = "standby_db"
log_file_name_convert    = "primary_db"
control_file_record_keep_time= 40
db_block_size            = 8192
compatible               = "11.2.0.4.0"
log_archive_dest_1       = "location=/u02/oracle/archivelogs/primary_db"
log_archive_dest_2       = "SERVICE=primary_db ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=primary_db"
log_archive_dest_state_2 = "ENABLE"
log_archive_min_succeed_dest= 1
fal_server               = "primary_db"
log_archive_trace        = 0
log_archive_config       = "DG_CONFIG=(primary_db,standby_db)"
log_archive_format       = "%t_%s_%r.dbf"
log_archive_max_processes= 3
db_recovery_file_dest    = "/u02/oracle/fast_recovery_area"
db_recovery_file_dest_size= 30G
standby_file_management = "AUTO"
db_flashback_retention_target= 1440
undo_tablespace          = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain                = ""
dispatchers              = "(PROTOCOL=TCP) (SERVICE=primary_dbXDB)"
job_queue_processes      = 0
audit_file_dest          = "/u01/oracle/admin/primary_db/adump"
audit_trail              = "DB"
db_name                  = "primary_db"
db_unique_name           = "standby_db"
open_cursors             = 300
pga_aggregate_target     = 1250M
dg_broker_start          = FALSE
diagnostic_dest          = "/u01/oracle"
Mon Dec 23 17:13:45 2013
PMON started with pid=2, OS id=29108
Mon Dec 23 17:13:45 2013
PSP0 started with pid=3, OS id=29110
Mon Dec 23 17:13:46 2013
VKTM started with pid=4, OS id=29125 at elevated priority
VKTM running at (1)millisec precision with DBRM quantum (100)ms
Mon Dec 23 17:13:46 2013
GEN0 started with pid=5, OS id=29129
Mon Dec 23 17:13:46 2013
DIAG started with pid=6, OS id=29131
Mon Dec 23 17:13:46 2013
DBRM started with pid=7, OS id=29133
Mon Dec 23 17:13:46 2013
DIA0 started with pid=8, OS id=29135
Mon Dec 23 17:13:46 2013
MMAN started with pid=9, OS id=29137
Mon Dec 23 17:13:46 2013
DBW0 started with pid=10, OS id=29139
Mon Dec 23 17:13:46 2013
DBW1 started with pid=11, OS id=29141
Mon Dec 23 17:13:46 2013
DBW2 started with pid=12, OS id=29143
Mon Dec 23 17:13:46 2013
DBW3 started with pid=13, OS id=29145
Mon Dec 23 17:13:46 2013
LGWR started with pid=14, OS id=29147
Mon Dec 23 17:13:46 2013
CKPT started with pid=15, OS id=29149
Mon Dec 23 17:13:46 2013
SMON started with pid=16, OS id=29151
Mon Dec 23 17:13:46 2013
RECO started with pid=17, OS id=29153
Mon Dec 23 17:13:46 2013
MMON started with pid=18, OS id=29155
Mon Dec 23 17:13:46 2013
MMNL started with pid=19, OS id=29157
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /u01/oracle
Mon Dec 23 17:13:46 2013
ALTER DATABASE   MOUNT
ARCH: STARTING ARCH PROCESSES
Mon Dec 23 17:13:50 2013
ARC0 started with pid=23, OS id=29210
ARC0: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Successful mount of redo thread 1, with mount id 2071851082
Mon Dec 23 17:13:51 2013
ARC1 started with pid=24, OS id=29212
Allocated 15937344 bytes in shared pool for flashback generation buffer
Mon Dec 23 17:13:51 2013
ARC2 started with pid=25, OS id=29214
Starting background process RVWR
ARC1: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Mon Dec 23 17:13:51 2013
RVWR started with pid=26, OS id=29216
Physical Standby Database mounted.
Lost write protection disabled
Completed: ALTER DATABASE   MOUNT
Mon Dec 23 17:13:51 2013
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
         USING CURRENT LOGFILE DISCONNECT FROM SESSION
Attempt to start background Managed Standby Recovery process (primary_db)
Mon Dec 23 17:13:51 2013
MRP0 started with pid=27, OS id=29219
MRP0: Background Managed Standby Recovery process started (primary_db)
ARC2: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ARC2: Becoming the heartbeat ARCH
ARC2: Becoming the active heartbeat ARCH
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance primary_db - Archival Error
ORA-16014: log 4 sequence# 7 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
At this moment, I've lost service and I have to wait until the prmiary server goes up again to receive the missing log.
This is the rest of the log:
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 23-DEC-2013 17:13:52
Tracing not turned on.
Tns error struct:
    ns main err code: 12543
TNS-12543: TNS:destination host unreachable
    ns secondary err code: 12560
    nt main err code: 513
TNS-00513: Destination host unreachable
    nt secondary err code: 113
    nt OS err code: 0
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 23-DEC-2013 17:13:55
Tracing not turned on.
Tns error struct:
    ns main err code: 12543
TNS-12543: TNS:destination host unreachable
    ns secondary err code: 12560
    nt main err code: 513
TNS-00513: Destination host unreachable
    nt secondary err code: 113
    nt OS err code: 0
started logmerger process
Mon Dec 23 17:13:56 2013
Managed Standby Recovery starting Real Time Apply
MRP0: Background Media Recovery terminated with error 16157
Errors in file /u01/oracle/diag/rdbms/standby_db/primary_db/trace/primary_db_pr00_29230.trc:
ORA-16157: media recovery not allowed following successful FINISH recovery
Managed Standby Recovery not using Real Time Apply
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
         USING CURRENT LOGFILE DISCONNECT FROM SESSION
Recovery Slave PR00 previously exited with exception 16157
MRP0: Background Media Recovery process shutdown (primary_db)
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 23-DEC-2013 17:13:58
Tracing not turned on.
Tns error struct:
    ns main err code: 12543
TNS-12543: TNS:destination host unreachable
    ns secondary err code: 12560
    nt main err code: 513
TNS-00513: Destination host unreachable
    nt secondary err code: 113
    nt OS err code: 0
Mon Dec 23 17:14:01 2013
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 23-DEC-2013 17:14:01
Tracing not turned on.
Tns error struct:
    ns main err code: 12543
TNS-12543: TNS:destination host unreachable
    ns secondary err code: 12560
    nt main err code: 513
TNS-00513: Destination host unreachable
    nt secondary err code: 113
    nt OS err code: 0
Error 12543 received logging on to the standby
FAL[client, ARC0]: Error 12543 connecting to primary_db for fetching gap sequence
Archiver process freed from errors. No longer stopped
Mon Dec 23 17:15:07 2013
Using STANDBY_ARCHIVE_DEST parameter default value as /u02/oracle/archivelogs/primary_db
Mon Dec 23 17:19:51 2013
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance primary_db - Archival Error
ORA-16014: log 4 sequence# 7 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
Mon Dec 23 17:26:18 2013
RFS[1]: Assigned to RFS process 31456
RFS[1]: No connections allowed during/after terminal recovery.
Mon Dec 23 17:26:47 2013
flashback database to scn 15921680
ORA-16157 signalled during: flashback database to scn 15921680...
Mon Dec 23 17:27:05 2013
alter database recover managed standby database using current logfile disconnect
Attempt to start background Managed Standby Recovery process (primary_db)
Mon Dec 23 17:27:05 2013
MRP0 started with pid=28, OS id=31481
MRP0: Background Managed Standby Recovery process started (primary_db)
started logmerger process
Mon Dec 23 17:27:10 2013
Managed Standby Recovery starting Real Time Apply
MRP0: Background Media Recovery terminated with error 16157
Errors in file /u01/oracle/diag/rdbms/standby_db/primary_db/trace/primary_db_pr00_31486.trc:
ORA-16157: media recovery not allowed following successful FINISH recovery
Managed Standby Recovery not using Real Time Apply
Completed: alter database recover managed standby database using current logfile disconnect
Recovery Slave PR00 previously exited with exception 16157
MRP0: Background Media Recovery process shutdown (primary_db)
Mon Dec 23 17:27:18 2013
RFS[2]: Assigned to RFS process 31492
RFS[2]: No connections allowed during/after terminal recovery.
Mon Dec 23 17:28:18 2013
RFS[3]: Assigned to RFS process 31614
RFS[3]: No connections allowed during/after terminal recovery.
Do you have any advice?
Thanks!
Alex.

Hello;
What's not clear to me in your question at this point:
What I'm NOT being able to perform:
If I manually unplug the network cables from the primary site (all the network, not only the link between primary and standby node so, it's like a server unplug from the energy source).
Same situation happens if I manually disconnect the server from the power.
This is the alert logs I have:"
Are you trying a failover to the Standby?
Please advise.
Is it possible your "valid_for clause" is set incorrectly?
Would also review this:
ORA-16014 and ORA-00312 Messages in Alert.log of Physical Standby
Best Regards
mseberg

Data Guard Broker and Cold Failover clusters

Hi,
I wanted to use Data Guard Broker to control primary/standby systems on AIX clusters but found that without Oracle clusterware it is not supported on failover of a database to another node (unless you drop and recreate the configuration which in my opinion is not support at all!).
The 11g documentation states that DG Broker offers support for single instance databases configured for HA using Oracle Clusterware and "cold failover clusters".
Does anyone know whether this support for cold failover clusters in 11g means "proper support" i.e the configuration detects that the hostname has changed and automatically renames it so it continues to work?, or is the support in 11g the same as that in 10g?.
Thanks,
Andy

Hi Jan,
We already use virtual hostnames.
When I set up the configuration the hostname for the databases default to the server name. The only way I know of changing this is to disable the configuration, then use the "edit database...set property" command but when I enable the configuration again it reverts back to its previous value.
regards,
Andy

Data Guard Broker: errors ORA-16816 and ORA-16817 with Fast Start Failover

Hi,
my environment is:
OS: Windows XP Professional Edition SP2
DB: Oracle EE 10.2.0.3
Primary db: orcl
Standby db: stby
both databases are running on the same server.
I have configured Data Guard as described in the DG Administration Guide.
In the Data Guard Broker I switch to 'stby' succesfully and 'stby' is the primary db and 'orcl' is the standby db.
I switched back to 'orcl' as primary db and I get some errors:
DGMGRL> show database 'orcl' statusreport;
STATUS REPORT
INSTANCE_NAME SEVERITY ERROR_TEXT
* WARNING ORA-16817: configuration for Fast Start of Failover is not synchronized.
DGMGRL> show database 'stby' statusreport;
STATUS REPORT
INSTANCE_NAME SEVERITY ERROR_TEXT
* ERROR ORA-16816: wrong databaserole
* WARNING ORA-16817: configuration for Fast Start of Failover is not synchronized.
DGMGRL> show configuration;
Configuration
Name: DG1
Enabled: YES
Protection Mode: MaxAvailability
Fast-Start Failover: ENABLED
Databases:
orcl - Physical standby database
- Fast-Start Failover target
stby - Primary database
Current status for DG1:
Warning: ORA-16607: one or more databases failed.
I have searched for solutions on Metalink and google, but with no success.
Has anyone got this kind of problem?
Any suggestions on how to resolve it?
Thanks

Hi DigerDBA
I did your advice , the error disappear, and thanks for your advice , but do I need to keep standby_file_management='AUTO' or 'MANUAL' in primary and standby init files?
Am asking this because when I use the observer the failover failed and I get the following error
SQL Execution error=604, sql=[ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WAIT WITH SESSION SHUTDOWN]. See error stack below.
ORA-00604: error occurred at recursive SQL level 1
ORA-01275: Operation ADD LOGFILE is not allowed if standby file management is automatic.
Complete Failover operation failed in the step when attempting to convert the database to be the new primary.
Database Resource SetState Error (16771)
01/07/2014 09:14:43
Command FAILOVER TO epprod2 completed with error ORA-16771
if possible can you advice me please?

DB link problem between active Data Guard and report application database

My database version in 11.2.0.2.0 and OS is Oracle Solaris 10 9/10.
I am facing a problem in my Active data guard Database for reporting purpose. Active Data guard information is as below.
SQL> select name, database_role, open_mode from v$database;
NAME DATABASE_ROLE OPEN_MODE
ORCL PHYSICAL STANDBY READ ONLY WITH APPLY
Problem detail is below
I have created a db link (Name: DATADB_LINK) between active data guard and report application database for reporting purpose.
SQL> create database link DATADB_LINK connect to HR identified by hr using 'DRFUNPD';
Database link created.
But when I run a query using db link from my report application database I got this below error.
ORA-01555: snapshot too old: rollback segment number 10 with name "_SYSSMU10_4261549777$" too small
ORA-02063: preceding line from DATADB_LINK
Then I check Active Data Guard database alart log file and get below error
ORA-01555 caused by SQL statement below (SQL ID: 11yj3pucjguc8, Query Duration=1 sec, SCN: 0x0000.07c708c3):SELECT "A2"."BUSINESS_TRANSACTION_REFERENCE","A2"."BUSINESS_TRANSACTION_CODE",MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'feature' THEN "A1"."TRANS_DATA_VALUE" END ),MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'otherFeature' THEN "A1"."TRANS_DATA_VALUE" END )
But the interesting point if I run the report query directly in Active Data Guard database, I never got error.
So is it a problem of DB link between active Data Guard and other database?

Fazlul Kabir Mahfuz wrote:
My database version in 11.2.0.2.0 and OS is Oracle Solaris 10 9/10.
I am facing a problem in my Active data guard Database for reporting purpose. Active Data guard information is as below.
SQL> select name, database_role, open_mode from v$database;
NAME DATABASE_ROLE OPEN_MODE
ORCL PHYSICAL STANDBY READ ONLY WITH APPLY
Problem detail is below
I have created a db link (Name: DATADB_LINK) between active data guard and report application database for reporting purpose.
SQL> create database link DATADB_LINK connect to HR identified by hr using 'DRFUNPD';
Database link created.
But when I run a query using db link from my report application database I got this below error.
ORA-01555: snapshot too old: rollback segment number 10 with name "_SYSSMU10_4261549777$" too small
ORA-02063: preceding line from DATADB_LINK
Then I check Active Data Guard database alart log file and get below error
ORA-01555 caused by SQL statement below (SQL ID: 11yj3pucjguc8, Query Duration=1 sec, SCN: 0x0000.07c708c3):SELECT "A2"."BUSINESS_TRANSACTION_REFERENCE","A2"."BUSINESS_TRANSACTION_CODE",MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'feature' THEN "A1"."TRANS_DATA_VALUE" END ),MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'otherFeature' THEN "A1"."TRANS_DATA_VALUE" END )
But the interesting point if I run the report query directly in Active Data Guard database, I never got error.
So is it a problem of DB link between active Data Guard and other database?
Check this note which is applicable for your environment
*ORA-01555 on Active Data Guard Standby Database [ID 1273808.1]*
also
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:8908307196113

Data Guard Broker - Complete/Immediate Failover ???

Dear Experts,
I have been reading about Data Guard Broker from Oracle Doc's (10.2). I came across two terms: Immediate Failover and Complete Failover.
I understood from the doc's what each one of them does but unable to understand how to trigger them.
Say, I have a Data Guard configuration setup in MAXIMUM PERFORMANCE mode. My primary database dies for whatever reason. How do I trigger "Complete Failover"?
If I were to use the following command, it will perform "Immediate Failover"
DGMGRL> failover to standbydb;
OS:                    Any OS (as this is related to concept)
Oracle:               Oracle 10g Release 2 (10.2.0.4)
Standby Type:     Physical Standby DatabaseThanks for taking time in reading and answering my question.
Regards

Oracle Lover3 wrote:
If I were to use the following command, it will perform "Immediate Failover"
DGMGRL> failover to standbydb;
According to the documentation at :
http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/sofo.htm#CHDDIEAC
or
http://www.sc.ehu.es/siwebso/KZCC/Oracle_10g_Documentacion/server.101/b10822/siteresource.htm
the command mentioned will execute a 'Complete Failover'
The command to do an Immediate failover would be:
FAILOVER TO STANDBYDB IMMEDIATE ;Correct me if I'm wrong...

Monitoring failover - Data Guard Broker

Hi,
I work on a Oracle 10.2.0.4 database on Solaris 10. It is a 2 node RAC database with a physical standby configured.
I want to monitor (send a mail) to myself when failover occurs (which will be triggered by data guard broker ) , I think so I can monitor the failover using alert log (which normally does log the command when we initiate a failover) but I am not sure whether data guard broker also does the same( writes appropriate commands when a failover is triggered)
Is there any other way we can come to know when a failover occurs (we can query database_role from v$dataguard status) but I am looking for some trigger that will be fired instantaneously when a failover is initiated ?
Also is it possible to monitor the observer, whether it is up or not ?

Hi,
you have several possiblities to do that. Easiest is to use predefined Grid Control Events for it. Or you may put a trigger on the event "after DB_ROLE_CHANGE on database".
Monitoring the observer can be done with dgmgrl like
connect sys/<pw>@<cd>;
show configuration verbose;That show you the presence and location of the observer.
I give you an example for the usage of the trigger that starts a service depending on the role of the database. You may customize it to send you an email.
begin
dbms_service.create_service('safe','safe');
end;
create trigger rollenwechsel after DB_ROLE_CHANGE on database
declare
vrole varchar(30);
begin
select database_role into vrole from v$database;
if vrole = 'PRIMARY' then
DBMS_SERVICE.START_SERVICE('safe');
else
DBMS_SERVICE.STOP_SERVICE('safe');
end if;
end;
/

Data Guard Physical Standby Failover

I need clarification on Physical Standby Failovers. Say I have a Primary db (A) and a physical standby (B), (A) fails and (B) is now the primary, can (A) be setup to become a standby of (B)? I've read 2 different statements in Oracle 10g Data Guard Concepts and Admin
"During failovers involving a physical standby database: In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration."
vice
"After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
Much thanks.

In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration.
TRUE ! But this doesn't mean that you cannot make your failed primary a new standby database !.
You can achieve this using FLASHBACK DATABASE option:
From the documentation:
After a failover occurs, the original primary database can no longer participate in the Data Guard configuration until it is repaired and established as a standby database in the new configuration. To do this, you can use the Flashback Database feature to recover the failed primary database to a point in time before the failover occurred, and then convert it into a physical or logical standby database in the new configuration.
Read the following documents:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/role_management.htm#sthref995
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1049997
In addition to this I'd like to mention that you can achieve the same with doing an incomplete recovery instead of using FLASHBACK DATABASE.
"After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
TRUE. If you enable Fast-Start Failover:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/sofo.htm#CHDDFFEC
Cheers!

Long distance application failover between data centers.

Hello:
I am working a project where there is a requirement to have a primary server and a secondary for application failover. The requirements dictate that the servers must be geographically separate at separate data centers but yet on the same IP subnet so that heartbeat messages are not natively routed. What protocol can I use to bridge the subnet over an IP routed network? GRE? L2TP?

GRE will not work as according to the last information I have you cannot bridge over a GRE tunnel. We had one such application with similar requirements and we ended up using L2TPv3 that allows transparent LAN extension. We have not had any issues with it and if you are only going to use it for heartbeats you should not run into any performance issues. L2TPv3 does tend to drive the CPU utilization high in case you have a lot of data traversing the tunnel.

Data Guard & Real Application Clusters

Hello, i have a problem with my data guard configuration. I am configuring data guard in a RAC
but i don'n know how to configured the redo sending to the standby database.
I would like any documentation about it.
thanks.

Here are some links:
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimarySingleInstancePhysicalStandby.pdf
And of course there is the manual:
http://download.oracle.com/docs/cd/E11882_01/server.112/e10700/toc.htm
Check out Chapter 3 and Appendices D and F.
Larry

Application of patches on oracle data guard 10g

Help!
I need apply the patch 9233832 on oracle 10.2.0.4 but I have configuration a pysical data guard. Considerations should I have to do? What steps should I follow?
Thanks.

Hello;
I have the steps in my notes will post back here - These :
Disable log shipping from the Primary
Shutdown Standby
Install patch software on Standby
Startup Standby in recovery mode (do NOT run any SQL at the standby)
Shutdown Primary
Install patch software on Primary
Run SQL for patch on the Primary
Re-enable log shipping
Monitor the redo apply from Primary This is pretty much the same for a CPU type patch or going from say 11.2.0.1 to 11.2.0.2. On Standby you just install the software and let the redo handle the rest.
Best Regards
mseberg
Edited by: mseberg on Mar 6, 2012 12:56 PM

Use of Flashback Database in Data guard environments

11.2.0.3/RHEL 5.8
I've come across several docs which talk about configuring FLASHBACK DATABASE in dataguard environments. We have several
Physical standby DBs (Single Instance & RAC) running in our shop.I would like to know two or three major(common) use of FLASHBACK DATABASE in data guard environments.
I understood one use mentioned in the below URL ie. recovering from a logical mistake
http://uhesse.com/2010/08/06/using-flashback-in-a-data-guard-environment/
I would like to know what are the other major/common use of Flashback Database feauture in DataGuard environment

A couple of other uses:
1) You can use flashback to test your DR. So you can activate your standby. Test application/network connectivity and functionality on your DR site and when done revert this database back to a physical standby. You do however have to ensure that this is allowed in your environment. In some places I have worked this would be a big no no as there were zero data loss requirements. However some companies will allow this as long as the standby is back in place within a certain time period.
2) In the case that you have to do a failover for whatever reason, but then what was the primary site becomes available, you can flashback what was your primary to make it the standby rather than re-instatiating the database from scratch.
Eg. You have a power outage at your primary site so you perform a failover and your standby becomes the primary. Once what was your primary site is back online, you can convert your previous primary into a standby by doing a full back/restore (or whatever method you choose) to recreate your standby again. However you also have the option of using flashback on this database and then convert it into a standby as this would potentially be quicker than re-instantiating the standby.

ORA-16525: the Data Guard broker is not yet available while conneting ...

Hi,
I am trying to connect oracle database instance in dgmgrl prompt.
Following error message appear ...
DGMGRL>
DGMGRL> connect sys/<password>@<oracle_service_name>
Connected.
Error:
ORA-16525: the Data Guard broker is not yet available
ORA-06512: at "SYS.DBMS_DRS", line 124
ORA-06512: at line 1
DGMGRL> exit
$ e
We are using oracle enterprise manager ...
SSM

DG broker is the way to go. There are only minor points you can't control - like when you have standby redo logs and no redo application delay, dg broker will always start real-time apply.
Also, DG broker is the only way if you want fast-start failover (10gR2 feature).
What is the latency of your nework, especially under load? Add this latency to each commit - will the commit time be acceptable? If not, you cannot use sync.
What version do you use? In 10gR1, there are issues with async - there is only about 50MB buffer, and if you get such backlog, even with async commit will wait for standby. (In 10gR2 this is solved, async will read from disk redo logs.)
NET_TIMEOUT - set it low for sync (so commits won't hang long), higher for async. Default is 180 seconds, Oracle recommends minimum value to 10 seconds. I would start with 10 sec for sync, 180 for sync. The main question is, how reliable your network is, and how long brownouts you want to survive without affecting data protection (with the expense of performance).
Regarding the proper setting of all bells and whistles of archive_log_dest_n - I had best experience with leaving it to dg broker. Just set LogXptMode property to sync/async/arch, and let dg broker set everything else (service, valid_for, affirm, retries...).
The authoritative source: http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm#Publications
If you are on 10.2.0.1 - 10.2.0.3, please see metalink bug 5578157, 5587231 - if sqlnet.outbound_connection_timeout is not set, the lgwr can hang even if net_timeout is set. (Yes, real-world experience:-)

Error: ORA-16525: the Data Guard broker is not yet available

Hi ,
After upgrading from 11201 to 11203 ON AIX GI/RDBMS on standby but have not upgraded the primary db yet.I had set dg_broker_start=false and disable configuration before i started the upgrade .
once the GI for oracle restart was upgraded i upgraded the rdbms binaries and brought up the standby on mount ,while trying to enable configuration its throwing the below error.I had already started the broker process.
SQL> show parameter dg_
NAME TYPE VALUE
dg_broker_config_file1 string /u01/app/omvmxp1/product/11.2.
0/dbhome_2/dbs/dr1mvmxs2.dat
dg_broker_config_file2 string /u01/app/omvmxp1/product/11.2.
0/dbhome_2/dbs/dr2mvmxs2.dat
dg_broker_start boolean TRUE
DGMGRL> show configuration;
Configuration - Matrxrep_brkr
Protection Mode: MaxAvailability
Databases:
mvmxp2 - Primary database
mvmxs2 - Physical standby database
Error: ORA-16525: the Data Guard broker is not yet available
Fast-Start Failover: DISABLED
Configuration Status:
ERROR
from drcmvmxs2.log
Starting Data Guard Broker bootstrap <<Broker Configuration File Locations:
dg_broker_config_file1 = "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr1mvmxs2.dat"
dg_broker_config_file2 = "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr2mvmxs2.dat"
12/19/2012 16:05:33
Data Guard Broker shutting down
DMON Process Shutdown <<12/19/2012 16:10:20
Starting Data Guard Broker bootstrap <<Broker Configuration File Locations:
dg_broker_config_file1 = "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr1mvmxs2.dat"
dg_broker_config_file2 = "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr2mvmxs2.dat"
~
Regards
Edited by: Monto on Dec 19, 2012 1:23 PM

Hi,
I removed the configuration and removed the broker files from RAC primary(mvmxp2) and single instance standby(mvmxs2) and re-created back.i tried it many times but getting error "ORA-16532" .I needed to have this standby backup before i start upgrading the primary.
SQL> alter system set dg_broker_start=true scope=both;
System altered.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
palmer60:/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs>dgmgrl
DGMGRL for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - 64bit Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys@mvmxp2
Password:
Connected.
DGMGRL> CREATE CONFIGURATION 'Matrxrep'
AS
PRIMARY DATABASE IS 'mvmxp2'
CONNECT IDENTIFIER IS 'mvmxp2';> > >
Configuration "Matrxrep" created with primary database "mvmxp2"
DGMGRL> ADD DATABASE 'mvmxs2'
AS
CONNECT IDENTIFIER IS 'mvmxs2'
;Database "mvmxs2" added
DGMGRL> SHOW CONFIGURATION;
Configuration - Matrxrep
Protection Mode: MaxPerformance
Databases:
mvmxp2 - Primary database
mvmxs2 - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
DISABLED
DGMGRL> ENABLE CONFIGURATION;
Enabled.
DGMGRL> SHOW DATABASE MVMXS2;
Database - mvmxs2
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: (unknown)
Apply Lag: (unknown)
Real Time Query: OFF
Instance(s):
mvmxs2
Database Status:
DGM-17016: failed to retrieve status for database "mvmxs2"
ORA-16532: Data Guard broker configuration does not exist
ORA-16625: cannot reach database "mvmxs2"
DGMGRL>
tailed the drcmvmxs2.log during stop and start of the broker
palmer60:/u01/app/omvmxp1/diag/rdbms/mvmxs2/mvmxs2/trace>tail -f drcmvmxs2.log
12/19/2012 20:32:20
drcx: cannot open configuration file "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr1mvmxs2.dat"
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
12/19/2012 20:32:55
drcx: cannot open configuration file "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr2mvmxs2.dat"
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
12/19/2012 20:59:10
Data Guard Broker shutting down
DMON Process Shutdown <<12/19/2012 20:59:35
Starting Data Guard Broker bootstrap <<Broker Configuration File Locations:
dg_broker_config_file1 = "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr1mvmxs2.dat"
dg_broker_config_file2 = "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr2mvmxs2.dat"
Not sure how to fix this one.
Regards

Data Guard Application Failover

Similar Messages

Maybe you are looking for