Data Guard setup after resetlogs on Primary

Hello,
On our primary database we had to perform an incomplete recovery and afterwards had to perform the command "ALTER DATABASE OPEN RESETLOGS". The problem I have is that after switching the Logical and Physical Standby databases back on they are still looking for archive log number 16133 when the log sequences have been reset back to 1.
The error message in the alert log is ....
ORA-16069: Archive Log standby database activation identifier mismatch
So the question is do I need to re-create my Logical and Physical standby databases or is there another may around this?
Thanks.

It depends on the database version, and the configuration in the databases, if the database version is 9i, it's mandatory to re-create the standby database. If the version is 10g, and the flashback database is used, it is possible that automatically the database continue the redo application.

Similar Messages

Data guard setup for 2 node RAC primary to 2 node RAC standby

Hi All,
I am going to setup data guard for 2 node RAC primary to 2 node RAC standby on Oracle 10.2.0.4. in AIX5L.
Can you please provide the document on the above setup which is having all the steps (details).
Also, the documents on different scenarios like
1) If one node of standby goes down, how the redo logs will be applied. IS there any problem?
2) If both nodes of standby are failed, how to reciver them?
3) If one node of primary fails, is there any issue?
4) If two nodes of primary fails, is there any issue?
Thanks in advance,
Mahi

Have a look at the following location, you may find some similar documents:
http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm
By
http://www.oraxperts.com

Data Guard setup with Clustered primary ?

Hi,
I am sure I am not in this unique requirement of setting up a Data Guard configuration where my primary database is clustered (for local server failure) and I am setting up the Data Guard (for the site level failure).
I could do the Data Guard setup without any problem where my primary and standby are on single individual servers (not clustered) but when I do the set up with primary database as clustered and do a local failover (not using Data Guard but using the veritas cluster) the DB Broker just stops recognizing the configuration.
I did come across a metalink note (BUG 4404952 ) which says DG Broker does not support Cold Failover Cluster.
Has anyone found any work around to it?
Has anyone tried using the above configuration in 10.2.0.4? Does it work in 10.2.0.4?
The Bug is dated 2007 so I am sure I am not the first one to encounter this issue.
Would really appreciate if someone can tell me what the workaround would be or guide me to any good link which would tell me the same.
Thanks a lot in anticipation.
Manoj Datar

I read somewhere that cold failover support in 11g is also ONLY for the oracle clusterware configuration.
Its really so hard to believe that there is NO ONE who wants to have a clustered primary (for local server failures) and a Data Guard (for the Site level failure or DR) as a combination in their HA environment.
I am still in the testing phase, What else could I be looking for in the solution if I need to achieve both these objectives (ie Local Server failures and Site level failures or DR)? I already have the Local server failure taken care by using the Veritas cluster so what do I need to include in the mix to achieve the site level failure?

Flashback Database on Data Guard setup

Hello!
Win 2003 server - 64 bit
Oracle 10.2.0.4
As i have noticed Flashback Database is popular in Data Guard setups for the reinstate reason; you dont need to rebuild.
However, im looking at Flashback for 'flashback database' reasons. Some developers has asked for a method to rollback if an release has gone bad, so my questions is;
If i flashback database primary database, will standby also change due to redo log shipment?
Thank u!

After flashing primary database check CURRENT_SCN in Standby. If flashback scn is greater then current_scn, then do nothing. Otherwise, on standby:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
FLASHBACK STANDBY DATABASE TO SCN "flashback_scn_number -1";
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

Oracle11gR2 data guard setup

I am looking for a document on "Active data guard configuration and setup".
In past I have used the following doc.....
http://wiki.oracle.com/page/11GR2+Data+Guard+Setup+project
But now the web link isn't available anymore (The link automatically redirects to www.oracle.com). The document was basically a workshop on how to setup Oracle 11gR2 active data guard with fast-failover option. It was an excellent document and very informative. Any idea where I can find it?
If anyone could point me to the document or atleast let me know who the author is....that will be extremly helpful.
Thanks,
Sourav

Thanks for the reply! But no, that's not the one I was looking for.
The old URL "http://wiki.oracle.com/page/11GR2+Data+Guard+Setup+project" had step by step very detail directions on data guard setup starting from physical standby creation from scratch. Nor typical OBE style....... just step by step instructions. It was indeed a very popular document/workshop.
Since this web link was active just 2 months back, I was wondering if there would be an archived location or someone would be able to help me locate the doc. It's hard to believe that these very helpful docs are deleted overnight.
Thanks,
Sourav
Edited by: user11948852 on Aug 23, 2011 5:01 PM

Data guard synchronization after link down b/w primary and physical standby

Hi All,
I have configured data guard on oracle 11gr2 db. Normally switchover between my primary and physical standby happens smoothly and the Apply lag would be zero. Recently We had to test a scenario when the network link between Primary and Physical standby is completely down and Physical standby is isolated completely for more than half an hour.
When we brought up the link every thing worked smoothly but apply lag started increasing from 0 to around 3 hrs. And then it started reducing to 0. Currently Apply lag and transport lag shows 0.
But is this normal behaviour of oracle data guard that when the link between primary and physical standby is completely down, It requires 3-4 hrs for resynchronization ??? Even when during isolation, there were very few transactions happend on primary database ??
Are there any documents available for this scenario??
Thanks

Hi, after the link is up, if there were some transactions and produced archive logs it's normal to take some time for resync. To check if 3-4 hours is normal or not, you can repeat the scenario and this time check
- how many archivelogs does primary produce in this period.
- after the link is up, does archivelog transfer immediately starts from primary to standby? Is primary able to send these archivelogs parallel?
- Is there anything wrong with the apply process?
check primary & standby alert log files, and run this query on standby to check the transport and apply processes:
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
regards

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

Grid Control and Data Guard Setup

Hi,
I have 4 PCs on which I wish to test the following:
1. OEM Grid Control 10.2 - Console + Service + Agent
2. Data Guard feature with Broker
3. Standby Setup for a Primary Database.
I will create the Primary DB on one Linux PC.
Standby DB using Grid Control & DataGuard on second Linux PC.
The Third PC is also Linux but the fourth PC is Windows XP.
Please guide me in understanding the following:
1. On which PCs should I install OEM Grid Control 10.2 - Console + Service + Agent?
2. On which PC should I setup DB Broker?
Please assume that I will use Oracle 10.2 Softwares and Linux x86 version.
Regards

well why don't you go ahead and test?!
Test and see whether you want to put oms, console all one machine, or whether you want to separate out the componests (you'll need an agent on each box regardless). I have no idea what the specs of your machines are, so why don't read the documentation on Grid and dataguard, see what the recommended settings are and then plan what you want to do.
Bazza

Oracle 11i(11.5.0.2) Data guard setup

Hi,
Hi, I am currently doing a test for 11i(with10.2.0.3 db) with Data guard. Since I have only one test server. I have created the Primary,Standby and the application Tier on one server. After switching over to the standby and trying to run autconfig on the application tier, it fails with TNS-entry not found. I would like to know that if its mandatory that the Primary and Standby db should have the same listener port or not.
Thanks

Hi,
Hi, I am currently doing a test for 11i(with10.2.0.3 db) with Data guard. Since I have only one test server. I have created the Primary,Standby and the application Tier on one server. After switching over to the standby and trying to run autconfig on the application tier, it fails with TNS-entry not found. I would like to know that if its mandatory that the Primary and Standby db should have the same listener port or not. Yes u need to have same sid and port number as of prod.
Refer MOS tech note:
*Business Continuity for Oracle Applications Release 11i, Database Releases 9i and 10g [ID 216212.1]*
thanks,
X A H E E R

New Data Guard Setup Required

Hi,
in my organization there is a requirement to setup a Physical Standby data guard for one of our 9i databases. Please find below for the hardware details and oracle version & etc..
Primary Setup
Server :
AIX Version 5.3
$ oslevel -r
5300-07
Database Verion
9.2.0.8
Standby Setup
Server :
Solaris 10 sparc (64-bit)
Database Version :
9.2.0.8
I would like know this can be achieved or not. I'm not very clear on the steps to follow.
Cheers
Kanchana.

No, ASM will be available from oracle 10g.
Regard
Asif Kabir
-- Hope you got the answer so close the thread as marking the post correct/helpful.

Data guard setup using 11g R2.

Hi,
It is possible to setup data guard between Amazon ec2 (primary db) and standby will be on local data center- (Non Amazon) using 11g R2.

Hi,
When I tried to create data guard between amazon ec2 instance and local server using 11g R2 64 bit on linux server I am getting the below mention error.I Need some pointers on this issue.
Thanks in advance
Starting backup at 08-JUN-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
input datafile file number=00005 name=/oracle/app/oradata/abs/abs.dbf
ORACLE error from target database:
ORA-03114: not connected to ORACLE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 06/08/2012 19:01:22
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/08/2012 19:01:22
RMAN-10038: database session for channel ORA_DISK_1 terminated unexpectedly

Data guard related OS processes in Primary and Standby servers

Database version : 11.2.0.3
Operating System : RHEL 5.8
Type: Physical Standby
++++++++++++++++++++++++++++In a typical Linux server hosting a Physical standby DB, the data guard related OS processes that appear in ps output
are like below. One mrp for each standby DB.
ps -ef |grep mrp
oracle 9380     1   0   May 21 ?          57:33 ora_mrp0_STRYKER_DG
oracle 18874     1   0   May 23 ?          33:45 ora_mrp0_FLPSA
oracle 18992 18837   0 23:39:39 pts/3       0:00 grep mrpSimilarly ,In a typical Linux server hosting a Primary DB what are the data guard related OS processes that appear in ps output ? Will LNS process appear in ps output ? Any other processes ?

Similarly ,In a typical Linux server hosting a Primary DB what are the data guard related OS processes that appear in ps output ? Will LNS process appear in ps output ? Not exactly but it appears has different name, on your primary try below commands
SQL> select pid from v$managed_standby where process='LNS';
$ps -ef|grep <pid value>
hope this helps, on standby you can use same procedure to find the RFS OS process

Data Guard Setup

I am trying to set up data guard 10g R2 on RHEL 5.
I was able to successfully set up one. What I did is i followed this blogger:
Data Guard Configuration Example - (Oracle 10g, Physical Standby) by Jeff Hunter, Sr. Database Administrator on http://www.idevelopment.info/
What I did is i installed RHEL 5 on 2 servers. Then I installed database software on both servers. Then on both servers, i used dbca to create database on each server. Am I correct? Since my data guard is working now as verified on testing. what i did is:
-install oracle software and create database on node 1
-install oracle software and create database on node 2
-transformed database on node 2 into physical standby database.
Is this also correct?
I am hearing that i can also create data guard (with physical standby database) using the setup:
- install oracle software and create database on node 1
-install oracle software only on node 2
-create physical standby database on node 2 using the database in node 1.
Any recommendations or am i doing correctly?

Ah, I may have explained incorrectly what I actually did .
What I did is,
- I created a database called test1 in node1 (general purposewith datafiles).
- Then on my node2, I created another database named test2 in node2 (custom databaseno datafiles).
- Node1 and Node2 has the same structures (except some paths which has .../test1/... and .../test2/...).
- Then I used RMAN to clone the database in node1 to node2.
These are my commands:
node2] rman target sys/oracle@test1 auxiliary sys/oracle@test2
RMAN> duplicate target database for standby;
So I believe what I did is also correct since I restored my test1 database in node1 into test2 database in node2. So I believe, my test2 database is an RMAN clone of my node1 database.
Edited by: 859640 on May 24, 2011 7:44 PM

Data Guard SetUp Q

For our new project we need zero data loss incase of disaster. I am thinking to use Data Guard between 2 remote data centers. I was going thru documentation and I have 1 Q:
In Maximum performance mode is it possible to have LGWR SYNC as a way to ship redo data?
If yes then wouldn't it be same as Maximum Availability?
If I use LGWR ASYNC , how much data loss can I expect?
Any help would be much appreciate
Thanks
Kanwal

You can check Oracle doc to fully understand the difference between LGWR SYNC Archival Processing
and LGWR ASYNC Archival Processing
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_transport.htm#i1265730
The main difference is SYNC will not commit change on primary until transaction is received on standby. ASYNC will not wait for remote confirmation.
If your network connection between standby and primary is not reliable it will have huge impact on performance. So it depends on how remote your standby is.
On the primary database, the LGWR process submits the redo data to one or more network server (LNSn) processes, which then initiate the network I/O in parallel to multiple remote destinations. Transactions are not committed on the primary database until the redo data necessary to recover the transaction is received by all LGWR SYNC destinations.
When the LGWR and ASYNC attributes are specified, the log writer process writes to the local online redo log file, while the network server (LNSn) processes (one for each destination) asynchronously transmit the redo to remote destinations. The LGWR process continues processing the next request without waiting for the LNS network I/O to complete.

RAC + Data Guard setup

In high-level terms, if you are running a 2-node RAC and get asked to create a 2-node disaster recovery site, how would I go about doing that? (The cluster in the disaster recovery site has already been created and the Oracle 11.2.0.1 software installed).
I'm thinking generally that an RMAN clone of production to the secondary site would be an idea: but can that be done with both production nodes up? And is the best approach to clone to a single-instance and then add a second instance manually later on?
Any pointers, or tips for a 2-node data guard from a 2-node RAC setup would be appreciated, basically. I realise it's pretty vague, but I'm just scoping this out at the moment and need some general pointers.

Hi,
Step by Step RAC to RAC Dataguard.
<<http://www.oracledba.org/11gR2/dr/11gR2_dataguard_RAC_to_RAC.html>>
Regards,

Data Guard setup after resetlogs on Primary

Similar Messages

Maybe you are looking for