Dataguard (10.2.0.5, physical standby)

Hi Guys,
Let's say there's a network issue between my production and standby database for about 4 days.
In production db, all archive logs that is older than 12 hours will be deleted on daily basis.
For the 4 days when the network is down, I have manually backup the all the necessary arch logs in a tape.
If i'm able to port all the archive log gaps to the standby site, can i do a "recover database" on the standby database and enable back the replication? Will this work?
Or i really need to manual register all the archive logs and enable back the replication?
thanks

dbaing wrote:
thanks all for the help.
--transport service automatically shall send this archive logs to standby and you not need any register archived logs to standby database.
I don't depend on the above as my archive logs have already been deleted from the primary filesystem so transport service can't find it.
So just wish to confirm again, if I have all the archive log backup then move it to the standby database archive log location and use 'recover standby database' after that use auto. It will recover all the archive of backup. And again you can start automatic recovery of it. Will this work?
Do i need to manual register the archive logs [gaps]? Or simply run "'recover standby database" after i transfer the arch log over?
thanksYou would need to restore the missing archivelog in standby and perform recover standby database up to the last archive.
Hope it helps
Cheers

Similar Messages

Dataguard (10.2.0.5) - physical standby (async, real time apply)

Hi Guys,
Just wondering.
For eg, I have a Production Database and a physical standby DB.
Only the physical standby DB has flash back on.
For eg, one day if there's a need for me to restore the production DB from tape (point in time recovery, so need to resetlogs).
Do i need to rebuild the physical standby DB? (from the backup of restored db)
Or can i make use of flash back? If i make use of flash back, i will have to re-create the control file right?
thanks

Hello;
Within Data Guard can use Flashback for the following :
On the Standby to recover data because of a delay in the apply process.
On the Standby ( Physical ) to open the database in snapshot mode.
On the Primary and Standby to flash the database back in time (if Standby then Primary must flashback too)
On the Primary to recover the database after a failover.If I understand you question correctly you are talking "Incomplete recovery" on the Primary with no Flashback there. So the answer is No, Flashback on the Standby cannot help.
You can correct this by setting up flashback on the Primary.
Best Regards
mseberg

Oracle DataGuard - Standy Redo log on physical Standby db

Hello Guys,
A quick question on my 10.2.0.2 db with Windows 2003 x64 OSs.
I have 2 machines - One for primary & the other for physical standby
I have successfully setup DG with Real Time Apply and also tested switchover & failover scenarios and they work well and as expected...
But I have a query which popped up when I was trying to set this up at home.
I create the physical standby db by shutting the primary db and copying all the datafiles, tempfiles,online redo logs and then creating a standby control file which will be used for the physical standby db to start off with.
After mounting the standby db, I tried to create standby redo logs files starting with Group 4 but I got error that standby group 4 already exists.
Upon querying v$logfile view, I noticed that the standby redo logs that I created on primary are also showing up on the standby db which I understand is from the standby control file.
So here is my quesiton: What is correct method of creating these standby redo logs on the standby database?
I know that I could drop those 4 standby redo logs from the standby db and recreate them but all the DG docs online and the documents that I have referred say that I should create the standby redo logs on the standby as I did on the primary but how can this duplication be avoided i.e. from the standby control file?
I know that I could use another method to create a hot backup such as RMAN etc...but I wanted to follow this way of shutting down the primary and copy the relevant database files.
Any help appreciated...and thanks in advance guys!
-Bharath

so with the setup that I used, i.e. create a standby control file which contains info about the standby redo logs at the primary site, should I also copy over the standby redo logs from the primary to standby as I only copied the datafiles, tempfile(s) & online redo logs? But then the filenames of the standby redo logs will be the exact same as that of the primary. Will that cause any issue during a switchover/failover?
I don't remember exactly how I did it when I got the whole thing working but I have a vague remembrance that I drop the std. redo log files entries from the std database and then recreate new ones with different filenames (as compared to primary).
Thanks

9.2.0.6 DataGuard - how to "break" replication, make standby "standalone"

Hi All,
I have an existing 9.2.0.6.0 DataGuard environment, where currently I just have one primary and one physical standby database. I am planning to add in another physical standby database, but then at some point, I want to "break" the dataguard replication to this one, and basically take it out of the DataGuard environment, and have it run as a standalone database. I am not talking about putting it into "open read-only" mode, I want to completely remove it from the DataGuard replication, and have it up and running as a standalone db. Is that even possible? I don't see anything mentioned about this in the official DataGuard documentation.
If anyone has any thoughts on the best way to do this, I'd really appreciate it!!
Thanks,
Brad

Actually, both... here is my potential plan:
1. Put a copy of the production database onto the new hardware, and instantiate it into the DataGuard configuration as a new physical standby database.
2. "Break" the dataguard replication, so that the new database on the new hardware becomes a standalone database, separate from DataGuard. At this point, we can test out some of the application against this database. The testing could last up to a few weeks.
3. Once we are happy with the testing, then we need to re-create this database as a backup from production, and get it back into the DataGuard replication as a standby. When it is time to cutover the production system, then we do a DataGuard Switchover, so that the database on the new hardware becomes the new primary database, replicating out.
Does that sound feasible? I think I can take care of all of those steps, the only one that I don't really know how to do is step 2, where we "break" the dataguard replication, and bring up the database on the new hardware as a fully stand-alone db.
Thanks,
Brad

Physical standby database fail-over

Hi,
I am working on Oracle 10.2.0.3 on Solaris SPARC 64-bit.
I have a Dataguard configuration with a single Physical standby database that uses real time application. We had a major application upgrade yesterday and before the start of upgrade, we cancelled the media recovery and disabled the log_archive_dest_n so that it doesn't ship the archive logs to standby site. We left the dataguard configuration in this mode incase of a rollback.
Primary:
alter system set log_archive_dest_state_2='DEFER';
alter system switch logfile;
Standby:
alter database recover managed standby database cancel;Due to application upgrade induced problems we had to failover to the physical standby, which was not in sync with primary from yesterday. I used the following method to fail-over since i do not want to apply any redo from yesterday.
Standby:
alter database activate physical standby database;
alter database open;
shutdown immediate;
startupSo, after this step, the database was a stand alone database, which doesn't have any standby databases yet (but it still has log_archive_config parameter set and log_archive_dest_n parameters set but i have 'DEFER' the log_archive_dest_n pointing to the old primary). I have even changed the "archive log deletion policy to NONE"
RMAN> configure archivelog deletion policy to none;After the fail-over was completed, the log sequence started from Sequence 1. We cleared the FRA to make space for the new archive logs and started off a FULL database backup (backup incremental level 0 database plus archivelog delete input). The backup succeded but we got these alerts in the backup log that RMAN cannot delete the archivelogs.
RMAN-08137: WARNING: archive log not deleted as it is still neededMy question here is
1) Even though i have disabled the log_archive_dest_n parameters, why is RMAN not able to delete the archivelogs after backup when there is no standby database for this failed-over database?
2) Are all the old backups marked unusable after a fail-over is performed?
FYI... flashback database was not used in this case as it did not server our purpose.
Any information or documentation links would be greatly appreciated.
Thanks,
Harris.

Thanks for the reply.
The FINISH FORCE works in some cases but if there is an archive gap (though it didn't report in our case), it might not work some times (DOCID: 846087.1). So, we followed the Switch-over & Fail-Over best practices where it mentioned about this "ACTIVE PHYSICAL STANDBY" for a fail-over if you intend not to apply any archivelogs. The process we followed is the Right one.
Anyhow, we got the issue resolved. Below is the resolution path.
1) Even though if you DEFER the LOG_ARCHIVE_DEST_STATE_N parameter's on the primary, there are some situations where the Primary database in a dataguard configuration where it will not delete the archive logs due to some SCN issues. This issue may or may not arise in all fail-over scenarios. If it does, then do the following checks
Follow DOCID: 803635.1, which talks about a PLSQL procedure to check for problematic SCN's in a dataguard configuration even though the physical standby databases are no available (i.e., if the dataguard parameters are set, log_archive_config, log_archive_dest_n='SERVICE=..." still set and even though corresponding LOG_ARCHIVE_DEST_STATE_N parameters are DEFERRED).
If this procedure returns any rows, then the primary database is not able to delete the archivelogs because it is still thinking there is a standby database and trying to save the archive logs because of the SCN conflict.
So, the best thing to do is, remove the DG related parameters from the spfile (log_archive_config, log_archive_dest_n parameters).
After i made these changes, i ran a test backup using "backup archivelog all delete input", the archive logs got deleted after backup without any issues.
Thanks,
Harris.
Edited by: user11971589 on Nov 18, 2010 2:55 PM

Switchover/Failover to physical standby

Hi All,
I have dataguard configured between Primary and physical standby. I would like to know how can i switch over to physical stanby when the network link is down between primary and physical standby.
I mean what steps I can follow to make physical standby to primary and primary to staandby even when the network connectivity is down between them.
Regards,
Raj

user12263161 wrote:
Hi All,
I have dataguard configured between Primary and physical standby. I would like to know how can i switch over to physical stanby when the network link is down between primary and physical standby. You can only failover in this case, but, if you have flashback on, you can reinstate ex-Primary to standby like described [url http://nikolayivankin.wordpress.com/2012/02/14/dgmgrl-reinstating-ex-primary-to-standby-by-flashback-database-feature/]here

Test physical standby database in dataguard

Hi all,
I had a successfull dataguard implementation for oracle 9r2.
Primary and standby databases are on different nodes, logs from primay are shipping and applying to physical standby database successfully.
As these database are for oracle 11i ebs, so for testing dataguard status i had created a table manually having columns date and remarks. Periodically i insert few records in this table in primary database and then chek this tabel in standby database (by opening in read only mode).
Now i want to test physical standby database with applications tier but don't want to disturb origional primary database.
as these are the normal switchover steps
1) at primary db
ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
2) at standby
ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
3) at primary, now this will be the stand by database
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
4) at standby, now this will be the primary database
SHUTDOWN IMMEDIATE;
STARTUP
My concern is if i skip step 1 and 3 and only execute step 2 and 4, will that be applicable for my requirement, or there is some other way to achieve this goal.
Regards,
Ken

To avoid touching the primary production DB, you may try to use the following command on your standby database side:
alter database activate standby database;
This will turn your standby database to primary database, however the log will be reset and this means you will need to rebuild your DR.
Another way is to use flash back feature on your standby database, activate it and revert back to the flashback point when the DR testing is done.

How to create physical standby database without dataguard

Hi,
Can anyone please help me how to create Physical Standby Database without dataguard. As i am using Oracle 10.2.0.1 Standard Edition for production databases.
Please find the specifications of my server :
Database : Oracle 10.2.0.1(Standard Edition)
Server : Linux 4.0(32 bit machine)
As we know that Dataguard cannot be created in Standard Edition as we dont have that option in this edition. So please help me how to create the physical standby database.
Thanks in advance.
Regards,
Farooq

Hello,
I hope this link helps you out...
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm
http://www.dbasupport.com/oracle/ora10g/manual_standby.shtml
Thanks & Regards
Pratik Lakhpatwala
Jr Oracle DBA
Edited by: Pratik.L on Dec 31, 2009 12:03 PM

Oracle 10g Dataguard Physical Standby Database

When I set my dataguard group to "MAXIMIZE AVAILABILITY" the protection level is always RESYNCHRONIZATION.
It's normal ?
SQL> SELECT PROTECTION_MODE, PROTECTION_LEVEL, DATABASE_ROLE FROM V$DATABASE;
PROTECTION_MODE PROTECTION_LEVEL DATABASE_ROLE
MAXIMUM AVAILABILITY RESYNCHRONIZATION PHYSICAL STANDBY
SQL> show parameter log_archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string SERVICE=PIJ10G2 LGWR SYNC AFFIRM
SQL> show parameter log_archive_dest_state_2;
NAME TYPE VALUE
log_archive_dest_state_2 string ENABLE

this is my log on primary db :
Thread 1 advanced to log sequence 422
Current log# 1 seq# 422 mem# 0: /oradata/orapij10g/redologs/PIJ10G/redo01.log
Wed Oct 1Thread 1 cannot allocate new log, sequence 423
Private strand flush not complete
Current log# 1 seq# 422 mem# 0: /oradata/orapij10g/redologs/PIJ10G/redo01.log
Wed Oct 17 16:24:51 2007
Destination LOG_ARCHIVE_DEST_3 is SYNCHRONIZED
LNSc started with pid=34, OS id=21052
Wed Oct 17 16:24:56 2007
Destination LOG_ARCHIVE_DEST_3 is UNSYNCHRONIZED
Wed Oct 17 16:24:56 2007
Errors in file /oracle/ora10g/admin/PIJ10G/bdump/pij10g_lgwr_26248.trc:
ORA-16086: Message 16086 not found; No message file for product=RDBMS, facility=ORA
LGWR: Failed to archive log 2 thread 1 sequence 423 (16086)
Thread 1 advanced to log sequence 423
Current log# 2 seq# 423 mem# 0: /oradata/orapij10g/redologs/PIJ10G/redo02.log
I don't understand this error message. How can solve my probleme ?

Physical standby without dataguard

Naive question.
I am going thru metalink note (374069.1) on how to create a physical standby. In that note, they didn't mention data guard stuff. Am I to assume that physical standby without dataguard can be created?
Thanks.

It might appears to be easy to create psuedo standy but you will have hardtime to simulate the automatic archive log apply and gap resolve.
Plus the level of data availability provided by self-managed standby can't come close to Data Guard can offer.
With Data Guard you can almost get zero data loss between Primary and Standy, depends on your redo logfile size there could be many data in online redo logs.

RAC & DataGuard (Physical Standby)

Hello all,
I'm trying to get a high level overview of how RAC & DataGuard would behave in the following configuration. I've written down my understanding of how things would work. Please correct me if I'm wrong.
1) 2 node RAC (Primary Database) with a single instance physical standby.
a) Same standby related init.ora parameters would have to configured on both primary rac nodes.
b) The redo apply service at the standby would merge the redo from the 2 threads from the primary and apply it to the standby to keep it in sync.
c) During switch over only one primary RAC instance should be up besides the standby instance.
d) During switch back again only one primary RAC instance should be up besides the standby instance.
e) During failover ofcourse both primary instances would be down which warrants the fail over.
2) 2 node RAC (Primary) with a 2 node physical standby
This where it gets complex and I'm not really sure how a,b,c,d,e would be in this scenario. Appreciate if you could shed some light on this and list what
a,b,c,d,e would look like in this scenario.
I'm assuming that only one instance in the standby RAC should be up when the standby is in RAC configuration for the redo apply to work.
Also, if there is a white paper that details step by step procedure for setting up the above 2 scenarios, please let me know. So far I was able to find only the MAA white paper but that was not very helpful. If you can prescribe a good book for RAC & DataGuard that would be great too..
Thanks for your help

>
1) 2 node RAC (Primary Database) with a single instance physical standby.
a) Same standby related init.ora parameters would have to configured on both primary rac nodes.Usually rac nodes share their spfile on a shared diskvolume or through ASM. So they have identical DG parameter anyway
b) The redo apply service at the standby would merge the redo from the 2 threads from the primary and apply it to the standby to keep it in sync.Correct
c) During switch over only one primary RAC instance should be up besides the standby instance.
Sounds logical to me
Edit: In fact during normal operation both RAC nodes are up, so during switchover they are both active too
It is the configuration that matters. As soon as the standby is becoming primary, it might be that it talks only to one RAC node for its log-apply files
d) During switch back again only one primary RAC instance should be up besides the standby instance.That single was the only one running in step c.
e) During failover ofcourse both primary instances would be down which warrants the fail over.Correct. Keep in mind that during a failover the RAC config would be deconfigured from the DG setup and has to be added back again as standby.
You might have to take a look at: http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimarySingleInstancePhysicalStandby.pdf
>
2) 2 node RAC (Primary) with a 2 node physical standby
This where it gets complex and I'm not really sure how a,b,c,d,e would be in this scenario. Appreciate if you could shed some light on this and list what
a,b,c,d,e would look like in this scenario.
I'm assuming that only one instance in the standby RAC should be up when the standby is in RAC configuration for the redo apply to work.
No. RAC primary to RAC Standby would mean both nodes are up on both side. PrimNode1 send its redo logs to StandbyNode1 and the same for PrimNode2 and StandbyNode2
Have a look here: http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf
HTH,
FJFranken
My Blog: http://managingoracle.blogspot.com
Edited by: fjfranken on 16-jul-2010 1:13

Dataguard physical standby archive log question

Hi all,
I will try to keep this simple..
I have a 4 node RAC primary shipping logs to a 2 node physical standby.
On the primary when I run 'alter system archive log current' on an instance I only see 1 log being applied on the standby, that is by querying v$archived_log.
If I run the following on the standby:
select thread#,sequence#,substr(name,43,70)"NAME",registrar,applied,status,first_time from v$archived_log where first_time
in
(select max(first_time) from v$archived_log group by thread#)
order by thread#
I get:
THREAD# SEQUENCE# NAME REGISTR APPLIED S FIRST_TIME
1 602 thread_1_seq_602.2603.721918617 RFS YES A 17-jun-2010 12:56:58
2 314 thread_2_seq_314.2609.721918627 RFS NO A 17-jun-2010 12:56:59
3 311 thread_3_seq_311.2604.721918621 RFS NO A 17-jun-2010 12:57:00
4 319 thread_4_seq_319.2606.721918625 RFS NO A 17-jun-2010 12:57:00
Why do we only see the max(sequence#) having been applied and not all of them?
This is the same no matter how many times I archive the current log files on any of the instances on the primary and also the standby does not have any gaps.
Hope this is clear..
any ideas?
jd

ok output from gv$archived_log on standby BEFORE 'alter system archive log current' on primary
THREAD# SEQUENCE# NAME REGISTR APPLIED S FIRST_TIME
1 679 thread_1_seq_679.1267.722001505 RFS NO A 18-jun-2010 11:58:22
1 679 thread_1_seq_679.1267.722001505 RFS NO A 18-jun-2010 11:58:22
2 390 thread_2_seq_390.1314.722001507 RFS NO A 18-jun-2010 11:58:23
2 390 thread_2_seq_390.1314.722001507 RFS NO A 18-jun-2010 11:58:23
3 386 thread_3_seq_386.1266.722001505 RFS YES A 18-jun-2010 11:58:22
3 386 thread_3_seq_386.1266.722001505 RFS YES A 18-jun-2010 11:58:22
4 393 thread_4_seq_393.1269.722001507 RFS NO A 18-jun-2010 11:58:23
4 393 thread_4_seq_393.1269.722001507 RFS NO A 18-jun-2010 11:58:23
Output from v$archived_log on standby AFTER 'alter system archive log current' on primary
THREAD# SEQUENCE# NAME REGISTR APPLIED S FIRST_TIME
1 680 thread_1_seq_680.1333.722004227 RFS NO A 18-jun-2010 11:58:29
1 680 thread_1_seq_680.1333.722004227 RFS NO A 18-jun-2010 11:58:29
2 391 thread_2_seq_391.1332.722004227 RFS NO A 18-jun-2010 11:58:30
2 391 thread_2_seq_391.1332.722004227 RFS NO A 18-jun-2010 11:58:30
3 387 thread_3_seq_387.1271.722004225 RFS NO A 18-jun-2010 11:58:28
3 387 thread_3_seq_387.1271.722004225 RFS NO A 18-jun-2010 11:58:28
4 394 thread_4_seq_394.1270.722004225 RFS YES A 18-jun-2010 11:58:29
4 394 thread_4_seq_394.1270.722004225 RFS YES A 18-jun-2010 11:58:29
as a reminder we have a 4 node RAC system shipping logs to a 2 node RAC standby. There are no gaps but only one log is ever registered as being applied.
Why is that? Why arnt all logs registered as being applied?

RAC physical standby in dataguard

Hi All
How many nodes need to be on the mount state in the RAC physical standby ? for example if we have RAC of 4 nodes in the physical standby . do I startup all of them in mount state or only one and what about the other they should be open or we shut them down ?
Thanks

Hi,
-- assuming version 10.2
If your primary database is a rac all the instances will send the redo information but even if the standby database is also a rac only one will receive/apply the redo information.
How many nodes need to be on the mount state in the RAC physical standby ? for example if we have RAC of 4 nodes in the physical standby . do I startup all of them in mount state or only one and what about the other they should be open or we shut them down ?
The instances will be mounted, if the working instance fails another one will be able to do the job.
Best regards
Phil
Edited by: Philippe Florent on Sep 15, 2010 12:05 AM -- completing the answer

Active dataguard physical standby

Hi,
Is it possible to create additional tables and do DML operations on them ( these tables will not be present on primary db) in physical standby database created by active data guard.
Regards,
prasad.

Is it possible to create additional tables and do DML operations on them ( these tables will not be present on primary db) in physical standby database created by active data guard.Prasad,
Here Active datagaurd feature is only for READ ONLY or reporting purpose, where you can perform only Select queries which is from 11gRx at the same time recovery also will be active.
If you want to open database in Read & Write , There there would be no consistent with Primary database, These behaves as different databases.
So Either you have to use flashback option after completing your REad & Write options,
Again you will lost all of the data, whatever you performed DML operations. So this is no use again.
You can use this note for that procedure *How To Open Physical Standby For Read Write Testing and Flashback [ID 805438.1]*
But i can say conclusion to make your standby high available your DML operations are not supported, ofcourse supported but its not High availability.
Hope this clears.
You seems to be new user to OTN , consider closing the thread as answered, Keep the forum clean. https://forums.oracle.com/forums/ann.jspa?annID=718
Edited by: CKPT on Mar 19, 2012 11:38 AM

Dataguard 9iR2 using same SID for primary and physical standby issues

Hello, I have been following the Creating Physical Standby Database document from Oracle setting up a physical clone for a 9iR2 database on Solaris 9 environment between two identical workstations. I want to databases to have the same SID for relatively seemless failover however the redo logs are not pushed to the physical clone. when I switch a logfile on the primary and then query v$archive_dest on dest_id=2 I get a status of ERROR and the ERROR is the ORA-12154 TNS service name error.
Here is a summary of my setup:
Primary - SID = PROD1, located on WS001
Clone - SID = PROD1, located on WS002
SPFILE settings on Primary:
*.db_name='PROD1'
*.dg_broker_start=true
*.fal_client='PROD1_node2'
*.fal_server='PROD1_node1'
*.log_archive_dest_2='service=PROD1_node2 optional lgwr async=20480 noaffirm reopen=15 max_failure=10 delay=30 net_timeout=30'
tnsnames.ora on Primary:
PROD1_node2 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = WS002) (PORT = 1521))
(CONNECT_DATA =
(SID = PROD1)
listener.ora on secondary:
PROD1_node2 =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = WS002) (PORT = 1521))
SID_LIST_PROD1_node2 =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME = /export/oracle/oracle_9.2/PROD1)
(SID_NAME = PROD1)
Any input would be appreciated. I can provide whatever else you might need. I thought this was the most pertinent to this problem.
Thanks.
Jim

I have been looking at the sqlnet.ora files for the two databases
for WS001:
Names.Default_Domain = WS001.example.com
Names.Directory_Path = (TNSNAMES, ONAMES,HOSTNAME)
for WS002:
Names.Default_Domain = WS002.example.com
Names.Directory_Path = (TNSNAMES, ONAMES,HOSTNAME)
I cannot connect with sqlplus from WS001 to WS002 on the other machine.

Dataguard (10.2.0.5, physical standby)

Similar Messages

Maybe you are looking for