Difference between revisions of "Patching"
From dbawiki
| Line 1: | Line 1: | ||
| − | On bog standard iron, this is a fairly simple procedure. Download the patch, stop the databases and listeners and opatch the ORACLE_HOME.<br /> | + | On bog standard iron, this is a fairly simple procedure. Download the patch, stop the databases and listeners and opatch the ORACLE_HOME. See general procedure [[here Applying patches]]<br /> |
[https://saruamit4.wordpress.com/2016/01/10/confusion-about-oracle-patches/ a word about the different patching terminology;overlay, merge, bundle etc..]<br /> | [https://saruamit4.wordpress.com/2016/01/10/confusion-about-oracle-patches/ a word about the different patching terminology;overlay, merge, bundle etc..]<br /> | ||
===What patches are installed?=== | ===What patches are installed?=== | ||
Revision as of 14:44, 31 October 2018
On bog standard iron, this is a fairly simple procedure. Download the patch, stop the databases and listeners and opatch the ORACLE_HOME. See general procedure here Applying patches
a word about the different patching terminology;overlay, merge, bundle etc..
Contents
What patches are installed?
Display the Patch inventory
$ORACLE_HOME/OPatch/opatch lsinventory
Display just the patches
$ORACLE_HOME/OPatch/opatch lspatches
From SQL*Plus in version 11
dba_registry_history is a view on registry$history
col action_time for a21 col action for a15 col namespace for a15 col version for a15 col comments for a80 wrap select action_time, action, namespace, version, id, comments from dba_registry_history order by 1;
From SQL*Plus in version 12
select extract(sys.dbms_qpatch.get_opatch_list,'//patchDescription|//appliedDate|//patchID') from dual;
Now things are getting more interesting...
