Testing dataguard failover

Dear All,
I am kindanew in oracle dataguard implementation. I want to know how to test failover scenario. I have shutdown the server which contain the primary database but i still dont know how to test the scenario. I keep on executing "select mode from v$database" on the standby database but it still shows mounted state.
Kindly help
Regards
Karam.

First test switchover ... does that work? The commands are well documented all over the net including on my website "MorgansLibrary.org"
If switchover works then the next question is have you configured for failover? If so how? In what version? etc. etc. etc.
We need details to be able to provide advice.

Similar Messages

How to test node failover in Windows 2008 R2 Failover Cluster?

Can anyone give me advice on how to properly test a node failure with a 2 mode Failover Cluster in Windows 2008 R2?

To test the failover of a clustered service or application
In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click
Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster that you want to configure.
Expand Services and Applications, and then click the service or application for which you want to test failover.
Under Actions (on the right), click Move this service or application to another node.
As the service or application moves, the status is displayed in the results pane (center pane).
Optionally, repeat step 4 to move the service or application to an additional node or back to the original node.
Source page:
http://technet.microsoft.com/en-us/library/cc754577.aspx
Regards,
Housam Smadi

How to test UCCX failover (no HA)

Hello,
I would like to test uccx failover with one UCCX and there is no HA configured.
I configured in UCCX/Cisco Unified CM Configuration => there is 2 Callmanagers for AXL Service Providers and 2 Callmanagers for CTI Managers if I stopping both Callmanagers server AXL Service Providers and CTI Managers (First server in list).
Can you tell me how I can test uccx failover (CAD, Calls, etc....)?
There is one uccx which is installed (no HA).
Thank you so much.
BR
Aubert

Hi Gergely,
Thanks a lot for your advices and if I understand this is the same test scenario if we disconnected the first callmanager with activated AXL service Providers or the CTI manager or the test scenario is different for both services.
-To test calls and to verify which are not disconnect
-To verify CAD which should not disconnect
-To verify reports work
Thank you so much;
BR
Aubert

DATAGUARD FAILOVER AND SQITCHOVER TESTING

I AM GOING TO TEST FAILOVER AND SWITCHOVER FOR BOTH PRIMARY AND STANDBY.
I AM STARTING FROM SCRATCH .
DOES SOMEBODY HAVE ANY DOCUMENTATION, NOTE ID'S OR ANY LINKS FOR THE SAME
THANKS LOT IN ADVANCE
JAGMOHAN

First test switchover ... does that work? The commands are well documented all over the net including on my website "MorgansLibrary.org"
If switchover works then the next question is have you configured for failover? If so how? In what version? etc. etc. etc.
We need details to be able to provide advice.

Dataguard failover

I have a dataguard configuration and after a failover to standby database, log_archive_dest_3 gets set to a default value.
SQL> show parameter log_archive_dest
NAME TYPE VALUE
log_archive_dest string
log_archive_dest_1 string location="+FLASH/dudbdr/", val
id_for=(ONLINE_LOGFILE,ALL_ROL
ES)
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string location="dgsby_dudbdr", valid
for=(STANDBYLOGFILE,STANDBY_
ROLE)
log_archive_dest_4 string
log_archive_dest_5 string
NAME TYPE VALUE
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string ENABLE
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string ENABLE
log_archive_dest_state_3 string ENABLE
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
NAME TYPE VALUE
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
SQL> ARCHIVE LOG LIST;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination dgsby_dudbdr
Oldest online log sequence 0
Next log sequence to archive 4661
Current log sequence 4661
Does any body know why it get reset instead of keeping the original vaule '+FLASH/dudbdr/'
thanks,

If you have already configured FSFO (refer Andy's post), then follow what Andy has said.
If you are using normal method, then for failover:
1. Your current primary database say P would go down or say crashed.
2. Then, you need to change the role of the standby database say S to primary database (called as failover)
3. So, now you would be having the primary database as S to use after performing step 2 (keep in mind that this was your old standby database (S) which has now become primary database (S))
4. Now, you do not have a standby database. The standby database (S) which you had has become the primary database (S). For this you'll have to create a new standby database say S1.
Hope you understood what I meant. :)
To perform failover manually:
1. When your primary (P) database crashes, on the standby database (S) issue the below command:
sql>alter database recover managed standby database cancel; #You would be cancelling MRP on standby database S
sql>alter database recover managed standby database finish; #You would be telling the standby database that the recovery is finished for ever
sql>alter database commit to switchover to primary; #Your standby S would now serve as primary and you would not be having a standby database anymore.Now to create a standby database, you can create a new one from the new primary database if flashback was enabled or you'll have to create from scratch.
I would request you to refer the below thread and the oracle documentation http://docs.oracle.com/cd/B28359_01/server.111/b28295/sofo.htm
You can refer this
recreate standby after failover test
http://arunmarapally.blogspot.in/2011/03/oracle-database-switch-over-and.html

Dataguard Failover Creation

I am about to create a failover with Data Guard using my current Oracle 11g database on Windows 2003. I have done some intensive reading, but I will appreate if anybody can share with me the steps involved in setting up a Data Guard with the same operating system version, but on different computers (Primary database on one Windows 2003 computer and Seconary database on another Windows 2003).
I am looking for answers to questions like "Do I need to install the secondary instance on the server where the seconary database will be?", "Can I use Enterprise Manager to clone?" "What about using RMAN?"
Thank you,
Edited by: azaza on Dec 6, 2009 9:13 AM

Warner,
I was able to replicate on my home PC the dataguard installation on one node and all is working, but EM can't see standby database (I will work to fix that). I don't have all the error with me because I am not home, but will post it when I leave work this afternoon. Meanwhile, the actual dataguard will be installed on a two nodes environment at my job, so if anybody has hands on experience, please post it for me.
Thank you,
Albert

How to avoid data lost in Dataguard failover ?

Hi gurus,
We are implementing Dataguard with manual failover (Not with Fast Start feature)
How to avoid/minimize lost of data if the primary server goes down before the last log is sent ?
Thank you for your help,
xtanto

Most important the dataguard protection mode, you have 3 choices: Maximum Performance,Maximum Availability,Maximum Protection . If you are interested in no data loss choose Maximum Protection, that's the definition:
Maximum Protection
This protection mode ensures that zero data loss occurs if a primary database fails. To
provide this level of protection, the redo data needed to recover a transaction must be
written to both the online redo log and to at least one synchronized standby database
before the transaction commits. To ensure that data loss cannot occur, the primary
database will shut down, rather than continue processing transactions, if it cannot
write its redo stream to at least one synchronized standby database.
Because this data protection mode prioritizes data protection over primary database
availability, Oracle recommends that a minimum of two standby databases be used to
protect a primary database that runs in maximum protection mode to prevent a single
standby database failure from causing the primary database to shut down.
For details see the documentation for your unknown database version.
Werner

Test DB failover senior with veritas

Hi experts,
My application live database using oracle 9i and clustered 3 servers using VERITAS as active/ passive. I want to test failover senior of my cluster. Can someone tell me the steps to proceed with this test without crashing my database?
regards,
krish

Here you are in a forum dealing with GENERAL Oracle database server questions. Fortunately Symantec has also a community site:
http://www.symantec.com/communities/index.jsp
Werner

Dataguard switchover & failover testing

i want to build new physical & logical dbs just for testing & learning, as per menalink notes 736863.1 & 748595.1
wondering that configuration will let me test switchover & failover testing?

Hi there,
Those notes help you to build a proper data guard configuration in both Physical and Logical Standby enviromnment.
I would also recommend to check:
- [The Oracle online documentation|http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/toc.htm]
- [Oracle Maximum Availability Architecture site on OTN|http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm]
These documents can provide a big picture of Data Guard configurations from different approaches as well as I would also recommend to learn and practice more advanced techniques and features such as Flasback database, Fast-start-failover or Cascaded destinations.
Hope this helps,
Good luck and regards,
Jozsef

Testing failover, how to reproduce ORA-24505: transaction status unknown

Database Version:11.2.0.2 psu 2
RAC 2-node
SUSE 11
Dataguard fast start failover
During testing of failover to the standby database we had a problem with taf, oracle reported an error 24505, the application trapped the error ignored it and then failed by attempting to re-insert the same data and recieving a primary key violation. My understanding is that this is one of the possible errors when using TAF and the application should trap the error and then determine if the transaction was completed before either replaying the transaction or continuing. We have raised this as a bug withthe application developers, however we need to reliably test for this condition and due to the nature of the problem we can not reliable reproduce the error condition and setting up the system to execute the failover makes repeatedly testing and hoping to encounter the error impractical.
Is there a method to force this error condition for both possible states? i.e. failover and force an ORA-24505 to be returned with the transaction having completed and also return ORA-24505 withthe transaction having rolledback.
Chris

We have arleady raised an SR, I am curious however as to how others test these types of issues as some of the taf errors are very rare.

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.

Ise failover test

As part of an ISE implementation, I want to test ISE failover for Admin, MnT, and PSN personas. Does anyone have an ISE failover test plan or ISE failover test best practices documentation to share?
Thanks much,
David Daverso

Steps for Administration persona failover testing
1. Stop ISE services on Primary Admin
Primary Admin# application stop ise
2. Log in to the Secondary Admin GUI and manually promote to Primary
3. Wait 10-15 minutes before process is complete
4. Verify ISE services are up on promoted Secondary Admin
Secondary Admin# sh application status ise
5. Promoted Primary Admin checks
Deployment pages shows all nodes are green and in synch
6. User testing to verify successful authentications and logging
Note:
After you promote your secondary Administration node to become the primary Administration
node, you must reconfigure your scheduled Cisco ISE backups in the newly promoted primary
Administration node
because scheduled backups are not replicated from the primary to secondary Administration
node.
7. After step 6 testing is complete restore original Primary Admin
8. Start ISE services on original Primary Admin
Primary Admin# application start ise
9. Verify ISE services are up on original Primary Admin
Primary Admin# sh application status ise
10. Promoted Primary Admin checks
Deployment pages shows original Primary Admin green and in synch
11. Stop ISE services on Promoted Primary Admin
Secondary Admin# application stop ise
12. Log in to the original Primary Admin GUI and manually promote to Primary
13. Wait 10-15 minutes before process is complete
14. Verify ISE services are up on original Primary Admin
Primary Admin# sh application status ise
15. Promoted Primary Admin checks
Deployment pages shows all nodes are green and in synch
16. User testing to verify successful authentications and logging
Note:
After you promote your secondary Administration node to become the primary Administration
node, you
must reconfigure your scheduled Cisco ISE backups in the newly promoted primary
Administration node
because scheduled backups are not replicated from the primary to secondary Administration
node.
17. Start ISE services on original Secondary Admin
Secondary Admin# application start ise
18. Verify ISE services are up on original Secondary Admin
Secondary Admin# sh application status ise
19. Primary Admin checks
Deployment pages shows original Secondary Admin green and in synch
20. User testing to verify successful authentications and logging

Xsan 2.x Failover: How to test, How does it occur ?

Hi,
I have a few questions about Xsan 2.x failover, hope to seek some advice here.
According to this article - http://support.apple.com/kb/HT3315
The following events may result in failover of all Xsan volumes:
- The active MDC is unreachable by the secondary MDC via the ethernet network used for metadata communications.
- The active MDC is rebooted or shutdown.
The following events will result in failover of a specific Xsan volume:
- The active MDC cannot see one or more LUNs associated with the volume.
- Xsan Admin or cvadmin is used to failover a volume.
We tried to simulate a failover, by disconnect the Primary MDC from the Xsan private network, similar to the 1st condition mentioned above.
However the Xsan FC client did not "failover" correctly.
The next failover test was to shutdown the Primary MDC, and this test was successful.
I'm curious in an event of a faulty network port on the Primary MDC, as simulated by disconnecting the network cable, or a faulty FC cable/FC card (which is used to communicate metadata, journal information to the Promise VTrak storage), does it warrant a failover as well?
It seems like the official way to test a failover is to use "Force Failover" in Xsan Admin.
Is this correct?
Cheers,
Ben Cheng · Application Engineer · The Media Village Pte Ltd

Before I start ripping cables to test failover, I always test volume failover in cvadmin. Open Terminal, type "sudo cvadmin", select your volume and type "fail MyXsanVolume". If that works well then you can go get a beer. If cvadmin properly reports the FQDN of my Xsan IPs then I get another beer, if I can fail the volume back and forth between controllers, then I get a keg, the day is done.

VNIC failover testing

Is there a way to test vNIC or hba failover on an individual blade. I don't want to have to turn a fabric interconnect off to validate that I have setup a vNIC or hba appropriately on a single blade so is there anyway from the Fabric Interconnect cli to disable a vNIC / hba or force it to failover to the other fabric?

Unfortunatley not, would be nice to be able to do a "Shut" on a veth in NXOS mode but you can't (not yet anyway.)
The best way I have found to test blade failover with MINIMAL disruption is to pull the FEX - FI link out, that that blade Pins to. THIS CAN EFFECT other blades depending on your setup.
I.e. if you only have a single FEX link obviously all your blades will be using it.
Best scenario is to use 4 FEX links (If using Gen 1 kit, with discrete pinning) then if you have a full chassis of half width blades you will have 2 servers pinned to each uplink. i.e. 1/5 to link 1, 2/6 to Link 2, 3/7 to link 3 and Blades 4/8 to link 4.
So if you pull FEX link one on FEX A out in the above scenario, all vNICS mapped to Fabric A will failover (if configured to do so) on blades 1 and 5.
Not ideal but better and much quicker than failing a whole FI as you were thinking about.
Obviously the above will not work if you have port-channelled the FEX - FI links.
Regards
Colin

Pre-Production Setup for Failover

Hi
I have installed my SAP Production environment on Window 2008 R2 , SAP ECC 6.0 EHP5, Oracle 11.2.0.3.
I have setup my DR system at different seismatic zone on Window 2008 R2 , SAP ECC 6.0 EHP5, Oracle 11.2.0.3.
The Oracle Dataguard is used for data replication from Production to SAP DR system.
Now I want to test the failover scenario. I would like to go and install the separate SAP environment in primary site as Pre-Production for DR Test on different hardware box. The system identification (SID) for production and pre-production is same as RP9.
Would like to know that Can I use the same root domain controller (RDC) available at primary site for production and pre-production environment. The domain users are same for both SAP systems.
Please clarify that does this situation will create any problem to my production or pre-production environment with same root domain controller?
or
should I go head with different root domain controller for pre-production environment ?
Regards
vimal

Hello
It is not recommended to have SAP systems sharing the same SID in a landscape... at least because it is not possible to have the system in the same TMS transport domain (but this can also have other drawback, especially if both system have client with same logical system name).
Even if it is possible to use the same domain users for two different systems I would not recommend this option, especially if one of the systems is a production one...
Suppose that for any reason the SAP domains accounts gets locked / modified / deleted ...
Either you create pre-prod system with a different SID (best option) and then you can share the same windows domain, or if you are willing to keep the same SID I would suggest that you install your pre-prod system either in an other domain or in a workgroup...
If your purpose is to test your Oracle DR abilities that is not a domain related mechanism, so you can test it in a workgroup...
Regards

Testing dataguard failover

Similar Messages

Maybe you are looking for