Tracking history of patch Sets and PSU patches

Display patching history
SQL> select ACTION_TIME, ACTION, VERSION, COMMENTS  from registry$history;
ACTION_TIME                    ACTION      VERSION       COMMENTS
------------------------------ ----------- -----------   ----------------------
17-SEP-11 10.21.11.595816 AM   APPLY       11.2.0.3       Patchset 11.2.0.2.0
05-JAN-14 04.10.01.602424 PM   APPLY       11.2.0.3       Patchset 11.2.0.2.0
11-JAN-14 10.13.57.653407 AM   APPLY       11.2.0.3       PSU 11.2.0.3.8
11-JAN-14 06.04.36.695049 PM   ROLLBACK    11.2.0.3       PSU 11.2.0.3.8

2 thoughts on “Tracking history of patch Sets and PSU patches”

  1. I just applied the patch to my 11.2.0.2.3 environment making it 11.2.0.2.4. All ran successfully.
    After rolling the patch back I looked in the registry$history table and was surprised to see the ROLLBACK action and comments still indidcating it was at 11.2.0.2.4. I was expecting to see it at 11.2.0.2.3!!

    Why is it showing the wrong patch level and is there a better way to identify the current patch level for my instance?

    Thanks for the assistance…this one has me stumped.

    1. 1) Did you run catrelod.sql successfully ?
      If yes I expect the that following PLSQL procedure should write are record to
      –> Extract from catrelod.sql
      Rem =====================================================================
      Rem Record Reload Completion
      Rem =====================================================================

      BEGIN
      dbms_registry_sys.record_action(‘RELOAD’,NULL,
      ‘Reloaded after downgrade from ‘ ||
      dbms_registry.prev_version(‘CATPROC’));
      END;
      /
      <--- Note catrelod.sql is a necessary step . See How To Downgrade From Database 11.2 To Previous Release (includes 11.2.0.4-11.2.0.1) (Doc ID 883335.1) 2) If you only want to check your current installed software version (including patches ) please run : $ORACLE_HOME/OPatch/opatch lsinventory

Leave a Reply to admin Cancel reply

Your email address will not be published. Required fields are marked *