Patching is one of the most critical responsibilities of an Oracle DBA. Oracle regularly releases patches to fix bugs, close security vulnerabilities, improve database performance, and maintain overall system stability.
Understanding the different types of Oracle patches helps DBAs choose the correct patching strategy for production, testing, and mission-critical environments.
What is OPatch?
OPatch is Oracle’s official patching utility used to apply and manage patches in Oracle software.
It is located under:
$ORACLE_HOME/OPatch/opatch
Main Functions of OPatch
OPatch is used to:
Apply patches
Rollback patches
Verify installed patches
Check patch conflicts
Generate inventory details
Important OPatch Commands
Check OPatch Version
opatch version
Check Installed Patches
opatch lsinventory
Verify Oracle Home
opatch lsinventory -detail
Important Note Before Patching
Before applying any Oracle patch:
Always update OPatch utility to the latest version
Take complete database backup
Validate Oracle Home space
Check patch conflicts
Test patches in lower environments first
Types of Oracle Patching
Oracle provides multiple types of patches depending on the purpose and severity of fixes.
1. Interim Patch (One-Off Patch)
An Interim Patch, also called a One-Off Patch, is created to fix a specific issue or bug.
Oracle Support usually provides this patch when a customer encounters a particular production issue requiring immediate resolution.
Characteristics
Fixes only one specific issue
Released for a targeted bug
Usually provided through Oracle Support
Can be applied quickly without major upgrades
Use Case
Suppose a production database crashes due to a known Oracle bug. Oracle Support may provide a one-off patch specifically for that issue.
Advantages
Quick problem resolution
Minimal changes to environment
Faster deployment
Limitations
Fixes only one issue
May conflict with future patches
Requires careful compatibility checks
2. PSU (Patch Set Update)
Patch Set Update (PSU) was Oracle’s traditional quarterly patching model before RU became standard.
It contains:
Security fixes
Critical bug fixes
Stability improvements
Characteristics
Released quarterly
Cumulative patch
Safer and more stable than one-off patches
Recommended for production systems
Advantages
Lower risk
Well tested by Oracle
Improves overall stability
Typical Example
11.2.0.4 PSU
12.1 PSU
3. CPU (Critical Patch Update)
CPU patches mainly focus on security vulnerabilities.
These patches help protect Oracle databases from:
Cyber attacks
Privilege escalation
Security exploits
Vulnerability exposure
Characteristics
Security-focused patching
Released quarterly
Essential for compliance and audits
Importance
Organizations running internet-facing or critical systems must regularly apply CPU patches to remain secure.
Difference Between PSU and CPU
| PSU | CPU |
|---|---|
| Includes security + bug fixes | Primarily security fixes |
| More comprehensive | Security-focused |
| Preferred for stability | Preferred for urgent security needs |
4. RU (Release Update)
Release Update (RU) is Oracle’s modern patching model introduced for newer Oracle versions like Oracle 19c.
RU is now the recommended patching strategy by Oracle.
RU Includes
Security fixes
Optimizer fixes
Functional fixes
Performance improvements
Regression fixes
Characteristics
Released quarterly
Cumulative patching model
Includes all previous RUs
Standard patching method for Oracle 19c+
Example
Oracle Database 19c RU
19.22 RU
19.23 RU
Why RU is Important
RU keeps the database:
Secure
Stable
Fully supported by Oracle
Updated with latest fixes
5. RUR (Release Update Revision)
Release Update Revision (RUR) is a more conservative version of RU.
RUR contains:
Critical security fixes
Important regression fixes
But avoids introducing too many new changes.
Characteristics
More stable than RU
Smaller change set
Reduced risk
Suitable for highly sensitive production environments
Best Use Cases
RUR is useful for:
Banking environments
Financial systems
Telecom production systems
Highly critical enterprise applications
RU vs RUR
| RU | RUR |
|---|---|
| Includes all new fixes and enhancements | Includes limited critical fixes |
| Faster innovation | Greater stability |
| More changes | Fewer changes |
| Recommended generally | Recommended for conservative environments |
6. Patch Set
A Patch Set is a major patch release containing:
New features
Bug fixes
Functional enhancements
It is closer to a minor version upgrade.
Example
11.2.0.1 → 11.2.0.4
Characteristics
Larger upgrade process
Requires extensive testing
May require downtime
Includes many internal changes
Patch Set vs RU
| Patch Set | RU |
|---|---|
| Major upgrade | Incremental update |
| Includes feature changes | Mostly fixes and stability |
| Larger downtime | Smaller maintenance window |
Oracle Patching Best Practices
Every DBA should follow standard patching best practices.
1. Take Full Backup Before Patching
Always perform:
RMAN backup
Oracle Home backup
SPFILE backup
OCR/Voting Disk backup (for RAC)
2. Verify Patch Compatibility
Check:
opatch prereq CheckConflictAgainstOHWithDetail
3. Validate OPatch Version
Older OPatch versions may fail during patching.
Always use the latest supported OPatch utility.
4. Test in Non-Production First
Never directly patch production without testing in:
DEV
TEST
UAT
5. Monitor Logs Carefully
Important patch logs:
$ORACLE_HOME/cfgtoollogs/opatch
6. Use Datapatch for SQL Changes
For Oracle 12c and above:
datapatch -verbose
This updates SQL components after binary patching.
General Oracle Patching Workflow
Step 1 — Download Patch
Download from:
Oracle Support (My Oracle Support)
Step 2 — Unzip Patch
unzip p34765931_190000_Linux-x86-64.zip
Step 3 — Stop Database Services
srvctl stop database -d PROD
Step 4 — Apply Patch
opatch apply
Step 5 — Run Datapatch
datapatch -verbose
Step 6 — Verify Patch
opatch lsinventory
Common Oracle Patching Challenges
DBAs commonly face:
Patch conflicts
Inventory corruption
Insufficient Oracle Home space
OPatch version mismatch
Datapatch failures
RAC rolling patch issues
Proper planning and testing help avoid these problems.
Key Takeaways
OPatch is Oracle’s official patching utility
Interim patches fix specific issues quickly
PSU and CPU were traditional quarterly patch models
RU is the modern recommended patching standard
RUR provides extra stability with fewer changes
Patch Sets are major upgrade-level patch releases
Proper backup and testing are mandatory before patching
Final Thoughts
Oracle patching is not just a maintenance task — it is a critical part of database administration.
A skilled Oracle DBA must understand:
Which patch type to use
When to apply it
How to minimize downtime
How to maintain database stability
Proper patch management ensures that Oracle databases remain:
Secure
High performing
Stable
Fully supported by Oracle
A well-patched database environment is one of the strongest foundations of a reliable enterprise system.
#OracleDatabase #OracleDBA #Oracle19c #OraclePatching #OPatch #DatabaseAdministration #OracleRU #OracleRUR #OraclePSU #CriticalPatchUpdate #DatabaseSecurity #OracleSupport #PatchManagement #OracleRAC #OracleCloud #DatabaseMaintenance #OracleTechnology #DBACommunity #DatabasePerformance #OracleLearning #OracleAdmin #ITInfrastructure #EnterpriseDatabase #OracleExperts #OracleUpgrade #Datapatch #RMAN #DatabaseOperations #TechCommunity #AIOUG
No comments:
Post a Comment