An online patch is a special kind of patch that can be applied to a live, running RDBMS instance. It contains a single shared library and does not required to shutdown the instance or relink the oracle binary. It utilizes the oradebug interface to install and enable the patches and is required additional memory consumption overhead.
Online Patches installation:
1) opatch query -is_online_patch
--------------------------------------------------------------------------------
Patch is an online patch: true
2) opatch apply online -connectString LAXCNT:sys:Im1laxcnt
Installing and enabling the online patch 'bug9407198.pch', on database 'LAXCNT'
3) opatch util enableOnlinePatch -connectString SANCNT:sys:Im1sancnt: -id 9407198
Invoking utility "enableonlinepatch"
Installing and enabling the online patch 'bug9407198.pch', on database 'SANCNT'.
alert_SANCNT.log
Patch bug9407198.pch Installed - Update #1
Patch bug9407198.pch Enabled - Update #2
Tue Jan 25 15:26:03 2011
Online patch bug9407198.pch has been installed
Online patch bug9407198.pch has been enabled
Online Patching Best Practices (metalink note: 761111.1)
- It is strongly recommended to rollback all online patches and replace them with regular (offline) patches on next instance shutdown
- Online patches should be used when the patch needs to be applied urgently and a downtime cannot be scheduled. IMPORTANT: It is strongly recommended to rollback all online patches and replace them with regular (offline) patches on next instance shutdown
- Apply one instance at a time
- When rolling back online patches, ensure all patched instances are included
- Avoids the dangerous and confusing situation of having different software across instances using the same $ORACLE_HOME
- Assess memory impact on a test system before deploying to production
- Example: pmap command
- Never remove $ORACLE_HOME/hpatch directory
No comments:
Post a Comment