(Doc ID 1006717.1)
Last updated on AUGUST 16, 2019
Applies to:Solaris Operating System - Version 8 6/00 U1 to 10 1/13 U11 [Release 8.0 to 10.0]
Code changes cause patches to grow in size and complexity over time
For example, a code change may cause a two-way interdependency between objects contained in two patches. In such cases, the patch contents are accumulated together into a single patch, and the other patch is obsoleted.
Large patches take longer to download and install. A customer wishing to get a simple bug fix may need to take a large amount of change and, if the patch requires a reboot, incur downtime to apply the fix if its applied to an active boot partition. Complex patches may specify Special Install Instructions which customers need to follow. This increases the cost of applying patches.
To help address these problems, the concept of Patch Rejuvenation was developed.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!