Got Active DataGuard on a primary database, quite nicely sending its archive logs to its secondary. I can quite happily use the Broker and switchover between them.
Now if I take RMAN backups of the primary database, if I have to failover to the secondary, I'm gonna loose all those backups.
Well, I can restore the whole database to the backup, cos I can restore the control file, from the backuip and therefore I can restore the whole db.
But if I want to restore to a tablespace, I wont be able to , cos the db_unique_names names are different, and the DB ID's will be different.
Same goes if I use a recovery catalog....
so how do I failover/switchover without loosing my previous rman backups ??
In my production -- we have 3 nodes Primary RAC with 2 Nodes Physical secondary Standby RAC. Due to some reason we will have to failover means 3 nodes Primary Standby RAC to 2 Nodes secondary physical Standby RAC. share Steps for Failover ( not switchover) from 3 Nodes Primary RAC to 2 Nodes Physical Standby RAC. I know this is generic and can be find from google but issue is how can failover from 3 nodes primary standby rac to 2 nodes secondary physical standby rac.
- Oracle 11.2.0.3 - RHEL 4.6 64 bits - Active Data Guard - Broker configured - DBconsole configured on primary server
Now, I have server PRIM with the primary database, and server STB with the standby server. For now, the dbconsole is configured in the PRIM server.When I do a switchover (to the standby on STB), EM is not configured, so I use RepManager.sh to clean the sysman user, and I use emca to recreate the dbconsole. After this, everything works.
Once I switch back, the EM is no longer configured on PRIM, so I repeat the previous steps (repManager and emca). Everything is ok after this. I can access the EM on the primary normaly, and this gets information from the broker to provide basic information on the STB (like db status, apply, and so forth).
i have a db's in maximum protection mode and i am trying to perform a switchover of physical standby database to primary role. but it failed., the steps followed is as follows. everything is fine with old primary site and the it is now in mounted state. When I went through the log file, I got the error message as "ORA-16072: a minimum of one standby database destination is required".the standby_archive_dest is as follows.
old primary database
SQL> alter system switch logfile; SQL> alter system archive log current;
old standby database...Disconnect the managed recovery mode in Standby database.
SQL> recover managed standby database cancel; Media recovery complete. SQL> recover standby database; AUTO SQL> exit [code]....
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=demodb' scope=both;
System altered.
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE SCOPE=BOTH;
System altered.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
Database altered.
SQL> recover managed standby database cancel; Media recovery complete. SQL> alter database open read only; alter database open read only * ERROR at line 1: ORA-16004: backup database requires recovery ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1: '/u002/app/OraDB10g/stdemo/oradata/system01.dbf'
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH; ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH * ERROR at line 1:
I am trying to create standby database on second machine ie. not on my machine. For this i have made added the required parameters in the pfile of the primary database but when I am trying to startup the database using the new pfile I am receiving some errors.
SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> startup nomount pfile='E:oracleproduct10.2.0db_1databaseinitden1.ora' LRM-00101: unknown parameter name 'L0G_ARCHIVE_DEST_2' ORA-01078: failure in processing system parameters SQL>
I did standby before and it works wighout any disturbations and even configuration seems to me not very complicated - but it was before. now i am trying to do standby configuration once again. there is database named DESK.
two physical serwers: sczepl-db07 - primary r00979 - standby
on each for this serwer there is listener listening on port 1521, and on each is tnsnames configured properly:
If flashback is enable in physical standby database 1. If we failover at 11AM can I flash back NEW primary database to 6 AM ? 2. if I convert physically standby database to snapshot standby database at 11AM , Can I flashback snapshot standby database to 6 AM and do some works on it (DML operations) then converting the snapshot standby database into physical standby database ?
I have a dataguard configuration (physical standby).Database A is the primary database and database B is the standby database (I do not use the broker).Both are Oracle RDBMS 12cR1 EE. The Apply process uses the current log (standby redo logs).On database B, when querying v$managed_ standby;, I get:
It works fine. Before to perform a switchover,- from database A (current physical database), I get switchover_status = 'TO STANDBY'- from database B (current standby database). I get switchover_status = 'NOT ALLOWED'. What switchover_status = 'NOT ALLOWED' means exactly and how to get further with the switchover?
we have a created primary and physical standby databases. Before the switchover the application connected to dataguard allows updates on the database. However after the switchover, it allows read-only access and we are unable to update. Any comments prima-facie ?
I am fairly new to Oracle and have recently started learning the basics of Data Guard. I have set-up a Primary 11g database which successfully ships and applies logs to a Single Standby (on the same server) as expected. Manual switchovers work fine; however, I have found a slight problem when performing switchovers using the Data Guard Broker utility.
The switchover is successful- but the broker cannot restart the Primary instance. The strange thing is that when I perform a switchover in the opposite direction (i.e. the new Primary goes back to standby again) it works fine. The error is receive is: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor.
The majority of posts I have seen on this topic seem to point to incorrect listener / tnsnames set up but they have exactly the same values. If both databases are identical, why does it work one way but not the other? I will provide any necessary files to pinpoint where the issue could be.
I am having setup of 2 node 10.2.0.4.0 RAC setup on ASM with Single Instance Physical standby on File System (OS: RHEL 5.4). I configured DG Broker without any major issues. Getting all output of 'show configuration' and all DG related logs are clear. Archives are getting transferred from both Primary nodes.
Now I am getting error Error: ORA-16535: CRS is preventing execution of a broker operation.
DGMGRL> switchover to livedg; Performing switchover NOW, please wait... Error: ORA-16535: CRS is preventing execution of a broker operation
Oracle Says
Quote:Cause A broker operation was underway that required CRS to stop managing the instances of this database, but CRS management could not be stopped on behalf of the broker"s request on at least some of the instances, so the broker operation was canceled.Suspend CRS management of this database using SRVCTL STOP DATABASE -D <name> -O NONE. Then reissue the broker request.But this command is not working as it's given to stop the database.
One more thing, it's nowhere said to stop CRS while performing Switchover / Switchback using DG Broker. When we do Switchover / Switchback we keep open only one of the Primary instance.
is there any documentation / link available to switchover of RAC database using dgmgrl (DG Broker)
I am very new to data guard...I have a primary and a physical standby database...If the primary got crashed, are the users directly switched to physical standyby (is it automated) or the DBA has to manually do the fail over or switch over....is it the same concept as in RAC like TAF....How can the DBA know that the users are disconnected from the database.....explain with some steps...
I am running some small tests here in my test env, using dataguard. I have configured the Primary and Standby with Maximum Availability... they're running just fine. Now i want to execute a failover test (i have already ran a Switchover test with the Broker successfully).
My question is very simple, at my point of view: What are the required steps to execute a successful manual failover? For example, i have my env as follows:
- Primary: prim1 - Standby: stdb1
Suppose that the primary database crashes in an unrecoverable way... is this case a manual failover would be necessary.
To do so, i would have to execute the following command, in my Standby database:
-- stdb1 is the standby database... DGMGRL> failover to stdb1
The above command is correct? Are there any required configurations after the failover? I read the Oracle Docs, and it says
what is the configuration dba has do for enabling the "fast-start failover concept" in the event of loss of primary database without requiring any manual steps to invoke the failover.whether the configuration are to be made in parameter file if yes what are those ?
My Data Guard 's Enviroment: Primary: 11.1.0.7 RAC 2 Nodes Standby: 11.1.0.7 Single Instance
I want to implement Fast-Start Failover at my enviroment. Reading requirements, I found that Oracle Flashback is needed (I don't use Flashback on my databases).
Best Practices recommends 60 min (1 hr) for DB_FLASHBACK_RETENTION_TARGET if I just want to use Flashback to fast-start failover.
My questions:
What 's better, setup up flash recovery area on ASM or O.S. filesystem? What is the recommended size for flash recovery area?
I have a situation where I want to configure primary database (11.2) with 2 remote destinations. dest_2 is the default and points to a standby on host_2. However, I also want the primary db to continue transporting redo to dest_3 on node_3 when node_2 is taken down (planned or unplanned).
1) Configure the ALTERNATE attribute of dest_2 to point to dest_3.
2) Configure tnsnames client-side failover on primary host to point to 2 nodes (node_2 and node_3).
i have Oracle 10g data guard set up on windows environment.....i need to know the what are the right steps to perform failover in case the primary database gets fail.
I have dataguard configuration operating in maximum availability mode with a local standby db (A - lgwr sync not using real time apply) and a remote standby db (B - lgwr async). I then simualted a crash of my primary database with batch jobs running. Since the stby db A is in lgwr sync option ,all the commited data in the current online redo log has been transmitted to stby A and is present in its stby redo log (Group 2).How do I apply this stby redo log to the remote stby db.
Tried the following methods.
1.ftp the stby redo log to the remote db and tried to regiter it, got an error that it is not completely archived.
2.issued the recover standby database command and supplied the stby redo log when it asked for the sequence in the stby redo, got an error saying there is corruption in a block(tried this option multiple times ended up with the same result.)
1.create a primary database 2.duplicate a physical standby database; 3.turn on flashback on both databases. 4.record SCN xxx on physical standby database. 5.convert physical standby to logical standby (using keep identity statement) 6.flashback to logical standby to xxx 7.convert logical standby to physical standby 8.using real time apply I got errors: Fast Parallel Media Recovery enabledManaged Standby Recovery starting Real Time ApplyMRP0:
Background Media Recovery waiting for new incarnation during transient logical upgrade procedure
Errors in file /home ora/ app/ oracle/ diag/ rdbms/ ora11gr1dg/ora11gr1dg/trace/ora11gr1dg_mrp0_10120.trc:ORA-19906: recovery target incarnation changed during recoveryManaged Standby Recovery not using Real Time ApplyErrors in file /home/ ora/app/ oracle/diag/ rdbms/ ora11gr1dg/ ora11gr1dg/ trace/ora11gr 1dg_mrp0_ 10120.trc:ORA-19906: recovery target incarnation changed during recovery
Errors appears every 10 seconds. Seems MPR0 is waiting for new incarnation for a long time. So am I.Standby database incarnation:
List of Database IncarnationsDB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time-------1 1 ORA11GR1 3853851354 CURRENT 1 08/09/2013 01:02:182 2 ORA11GR1 3853851354 ORPHAN 2127877 08/28/2013 19:22:01 BGV
GROUP# THREAD# SEQUENCE# sizeMB ARC STATUS T ---------- ---------- ---------- ---------- --- ---------------- - 1 1 115 512 YES CLEARING O 2 1 116 512 YES CURRENT O 6 1 114 512 YES CLEARING O 4 1 112 512 YES CLEARING O 5 1 113 512 YES CLEARING O 3 1 111 512 YES CLEARING O
6 rows selected. [code]...
Above result is from standby database.I am trying to understand the concept of standby redo log.My stadby database protection_mode is MAXIMUM PERFORMANCE.
tell me about data guard accommodate with 11g database standard additions or not if no,is there any way to make it working under this edition?one more thing may i have the steps of configuration data guard in real time for anew server.
just realised the data guard configuration seems to be workin but the error kepps appearing on the alert log of both primary and physical standby that i configured. below is my primary and standby pfiles.
For the maximum protection and maximum availability as well as to enable Real Time Apply we need to setup the standby redo log group. My question is what would be the standby redo log group configuration in case if we setup single instance standby database for 2-Node RAC primary database. Do we require a separate standby redo thread for each primary online redo thread or RFS use the Multiple Standby redo group from the same thread to receive the redo changes from both the node ?
We have a request to configure data guard for databases on the production server. Here is my situation:
We have a backup strategy in place where the backups are being taken on a regular basis. Archive logs are deleted as soon as they are backed up.
My question now is , is there a way of configuring the Data guard in such a way that there would be no change to existing backup strategy (RMAN) and still duplicate the archive logs to another destination and not delete the archive logs by RMAN backup process on that destination while the first destination is deleted.
We will be deleting the logs in the second archive destination using a script which checks if the logs were applied.
I have created dataguard between two instances hosted in two different servers. I have done switchover from primary to standby & then again standby to primary with DGMGRL utility.
1- When I done switchover to primary & trying to open standby database in readonly mode it was giving below error-
ORA-01154: database busy. Open, close, mount, and dismount not allowed now
Why this error was coming ?
2- As I was not able to open standby database in read only mode, I have executed below command-
alter database recover managed standby database disconnect from session;
which return an error as-
ORA-01153: an incompatible media recovery is active
After this I have executed-
alter database recover managed standby database cancel;
which executed successfully.
& then after standby database open in read only mode.
Why above error was coming ?
3- After this I had tried to check the checkpoint_change# & controlfile_change# from primary database and result shows both number were different.
