LODH Biswajitt

From: LODH Biswajitt Sent: Friday, January 20, 2012 11:44 AM Subject: Oracle RAC Test Cases

Test Plan for oracle rac database server Database failover
SL No. Objective
Action Expectation Observation Pass/fail

1

To test the failover session of a connected oracle user in the event of an instance failure To test the failover session of a connected oracle user in the event of an instance failure

1. Connect from a client to node 1 in the RAC Environment using sqlplus.

The sql connection should be able to swing over to other instance and still continue the select query.

2. Connect to the database on node 1 and do a shutdown.

# – sqlplus connection from client to db is still available.

sqlplus / as sysdba

To test the complete failover of the session 2 in event of a node (e.g. sudden shutdown) To test the stability of the db by killing a ora server process To test the failover of the network card of the public IP address.

1. Connect from the client to the database via sqlplus. The sql session should not be affected and failover to the next node without any disruption.

2. power off the unix box in which the sqlplus connection is at. kill off a process related to the oracle daemons from a terminal. This should crash the database processes. Plug out one of the cable connecting the node to the public network.

3

The sql session should not be affected and failover to the next node without any disruption.

5

The ping from the client should be able to go thru’

6

To test the failure of ASM instance ( ASM Instance crash)

On Node 1, kill the processes related to ASM

The cluster must not be affected by ASM crash on node 1.

7

To test accidental change of IP addresses of the cluster.

Modify etc/hosts and change the VIP addresses - Try starting the cluster

The cluster must not be able to boot up with error messages related to network Ips.

The cluster must go down and should not start since ORACLE RAC doesnot safeguard for storage failure. 1. . 2.8 To test crash of GRID processes Kill LMON process on RAC Nodes They must be restarted automatically. 9 To test for automatic shifting of SCAN Listeners Reboot Node 1 using the OS reboot command 10 To test for Storage Crash Forcibly make the SAN disks unvisible to both the nodes. When Node 1 goes down all SCAN Listeners must shift to the remaining node on the cluster. When Node 1 come up the SCAN Listener must again shift back to the original Node.

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master Your Semester with a Special Offer from Scribd & The New York Times

Cancel anytime.