My Oracle Support Banner

ODA (Oracle Database Appliance): Test Plan Outline (Doc ID 1474273.1)

Last updated on FEBRUARY 26, 2019

Applies to:

Oracle Database Appliance Software - Version 2.1.0.1 and later
Oracle Database Appliance - Version All Versions and later
Information in this document applies to any platform.
***Checked for relevance on 23-Jun-2014***

Purpose

Before a new computer /cluster system is deployed in production it is important to test the system thoroughly to validate that it will perform at a satisfactory level, relative to its service level objectives. Testing is also required when introducing major or minor changes to the system. This document provides an outline consisting of basic guidelines and recommendations for how to test a new ODA (Oracle Database Appliance) system. It can be used as a framework for building a system test plan specific to each company’s ODA implementation and the associated service level objectives.

Scope

This document provides an outline of basic testing guidelines that will be used to validate core component functionality
for ODA system in the form of an organized test plan. Every application exercises the underlying software and hardware infrastructure differently, and must be tested as part of a component testing strategy. Each new system must be tested thoroughly, in an environment that is a realistic representation of the production environment in terms of configuration, capacity, and workload prior to going live or after implementing significant architectural/system modifications. Without a completed system implementation and functional available end-user applications, only core
component functionality and testing is possible to verify cluster, RDBMS and various sub-component behaviors for the networking, I/O subsystem and miscellaneous database administrative functions.
In addition to the specific system testing outlined in this document additional testing needs to be defined and executed for RMAN, backup and recovery, and Data Guard (for disaster recovery). Each component area of testing also requires specific operational procedures to be documented and maintained to address site-specific requirements.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 Test Case 1 - Simulate failures to Internal (OS) disks
 Test description
 Test result
 Test Steps
 1. Check your initial disk configuration
 2. Check the initial disk status with oakcli
 3. Simulate a disk failure
 4. OAK is recongnizing the failure
 5. Restore the disk
 6. Check the disk status using OAK
 Test Case 2 - HDD (Hard Disk Drive) failure
 Test description
 Test result
 Test Steps
 1. Startup system and database
2. Verify initial shared disks status
 3. Remove a shared storage hard disk
 4. Verify alert is received
 5. Verify the removed disk is not available
 6. Reinsert the hard disk (same slot)
 7. Verify all disks are online
 Test Case 3 - SDD (Solid State Disk) failure
 Test description
 Test result
 Test Steps
 1. Startup system and database
2. Verify initial storage shared disks status
 4. Remove a shared storage SSD
 5. Verify alert is received
 6. Verify the removed SSD disk is not available to ASM
 7. Reinsert the SSD back into its slot
 8. Verify all disks are online
 Test Case 4  - Connectivity to Database
 1. Local connection - Verify connectivity to an instance
 Test description
 Test result
 Test Steps
 2. External connection - Connect from an application
 Test description
 Test result
 Test Steps
 3. Connect using services - Connect using services and test load balancing
 Test description
 Test result
 Test Steps
 Test Case 5 - Connection failover and continued service availability
 Test description
 Test result
 Test Steps
 Test Case 6 - Private network failure
 Test description
 Test result
 Test Steps
 1. Initial default status isthat both private NICs are up
 2. Simulate a failure of  eth0
 3. Simulate a failure of both private NICs at the same time
 4. Simulate both failed NICs(eth0/eth1) come back to work
 Test Case 7 - Public Network Failure
 Test Case 8 - Database backup and recovery test
 Test description
 Test result
 1. Backup a database using RMAN.
 2. Recover database (optional) - Optionally simulate database loss and perform database recovery.
 3. Verify database recovery (validate using the database object created or updated previously).
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.