Rac Test Cases

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

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

To test the complete failover of the session

Action

Expectation

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

1. Connect from the client to the database via sqlplus.

2

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

in event of a node (e.g. sudden shutdown)

2. power off the unix box in which the sqlplus connection is at.

3

To test the stability of the db by killing a ora server process

kill off a process related to the oracle daemons from a terminal. This should crash the database processes.

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

5

To test the failover of the network card of the public IP address.

Plug out one of the cable connecting the node to the public network.

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.

Observation

Pass/fail

8

9

10

To test crash of GRID processes

Kill LMON process on RAC Nodes

To test for automatic shifting of SCAN Listeners

Reboot Node 1 using the OS reboot command

To test for Storage Crash

Forcibly make the SAN disks unvisible to both the nodes.

They must be restarted automatically. 1. When Node 1 goes down all SCAN Listeners must shift to the remaining node on the cluster. 2. When Node 1 come up the SCAN Listener must again shift back to the original Node. The cluster must go down and should not start since ORACLE RAC doesnot safeguard for storage failure.