Академический Документы
Профессиональный Документы
Культура Документы
From: LODH Biswajitt Sent: Friday, January 20, 2012 11:44 AM Subject: Oracle RAC Test Cases
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
The sql connection should be able to swing over to other instance and still continue the select query.
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.
The sql session should not be affected and failover to the next node without any disruption.
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.
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.
10