|
Oracle performs different types of testing on various patch types prior to their release:
- Functional tests
-
- test specific areas of functionality against expected outcomes.
An "area" may be a feature or subset of a feature (eg: Advanced Queueing or a specific functionality of Advanced Queueing)
- functional tests include regression testing to ensure that results and behaviour of specific operations are as expected.
- Stress tests
- test resilience of the database when pushed to its limit in resource utilization and in specific configurations
- heavy destructive tests under high load
- Performance tests
- test various workloads and features
- measure the performance of specific operations to ensure that most common code paths have not degraded in performance (sometimes known as "atomics" tests)
- test overall performance of specific workloads / features
The following table shows the level of testing performed by Oracle for the various patch types:
|
?
Interim Patch
PSU,SPU,Bundle
??? Patch Set Release
Functional
?Functional regression tests for the specific area of database functionality affected by the patch.
Complete set of functional regression tests
(tests all areas of database functionality).
Complete set of functional regression tests
(tests all areas of database functionality).
?Verification that the fix addresses the known symptoms of the bug issue.
?
?
Stress
None.
Subset of stress tests based on patch content.
Full stress testing.
Performance
None.
Workload based performance regression testing.
Full set of performance tests.
Other
Install testing in unpatched environment.
Install testing in clean environment.
Install & upgrade testing – many scenarios.
Installation using EM CC patching.
“Upgrading” from previous PSU,bundles.
Deployed and used internally in Oracle
before release.
?
Installation using EM CC patching.
Certification testing.
?
Testing Recommendation by Patch Type
Customers are advised to perform testing of patches in a test environment prior to deployment to critical production environments.
The following table gives an overview of the level of testing recommended for each patch type:
?
Interim Patch
PSU,SPU
Bundle Patch
Patch Set Release
Install / Rollback
Yes
?Yes
?Yes
?Yes
Bug Fix Verification
Where possible and relevant???
Admin Activities
Not required
Basic
Basic
Full
Application Function
Not required
Core applications only
Core and non-core applications
Full
Application Performance
Not required
Not required
Not required
Full
Where:
- Install / Rollback = basic testing that patch apply / rollback works. Patch installation and rollback should be tested for every type of patch.
- Bug Fix Verification =?If you are applying a patch for the purpose of installing a bug fix then you should verify that the bug fix addresses the specific bug issue.
- For some fixes this may not be feasible - eg: if the fix addresses a rare race condition.
- Admin Activities = Software / system administration activities:
- "Basic" is defined as common activities. ?
For example,"Basic" admin activities would include validating Database and Grid Infrastructure shutdown and startup,validating monitoring
- Application Function = Functionality of your application. "Core" indicates business critical application functionality.
Which Patching Method to Use?
（编辑：济源站长网）
【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容!
