AutoUpgrade New Features: Include Monthly Recommended Patches When Patching

Staying even more up-to-date with Monthly Recommended Patches (MRP) is now easier when patching using AutoUpgrade.

MRP contains fixes from 555.1 conveniently bundled together in a single patch.

> To provide customers more frequent access to recommended and well-tested collections of patches, Oracle is pleased to introduce Monthly Recommended Patches (MRPs)

From My Oracle Support note ID 555.1

How To

  1. Get the latest version of AutoUpgrade:
    wget https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar
    
  2. Add MRP to the patch entry in your AutoUpgrade config file:
    global.keystore=/home/oracle/autoupgrade-patching/keystore
    patch1.source_home=/u01/app/oracle/product/19/dbhome_19_25_0
    patch1.target_home=/u01/app/oracle/product/19/dbhome_19_26_0
    patch1.sid=DB19
    patch1.folder=/home/oracle/autoupgrade-patching/patch
    patch1.patch=RECOMMENDED,MRP
    
  3. Run AutoUpgrade in analyze, download or deploy mode, and AutoUpgrade gets: * RECOMMENDED – latest available Release Update, OPatch, Data Pump Bundle Patch and OJVM Bundle Patch * MRP – latest available MRP matching the Release Update
  4. Optionally, you can add one-off fixes that are not part of the Release Update or MRP:
    patch1.patch=RECOMMENDED,MRP,34672698
    
    • You can add more one-off fixes using a comma-separated list

Tell Me More About Monthly Recommended Patches

Here’s a little snippet from Virtual Classroom #16: Oracle Database Release and Patching Strategy for 19c and 23ai, where Mike explains the concept.

I recommend that you also install MRPs when possible. Using AutoUpgrade, it’s really easy to add them, so why miss out?

Happy patching

Appendix

Further Reading

5 thoughts on “AutoUpgrade New Features: Include Monthly Recommended Patches When Patching

  1. Thank you Daniel. I just have one question, seems it is the same question are monthly patch (MRUs) now available for the Windows platform?

    Like

  2. Hi Daniel,

    after creating new ORACLE HOME 19.27 with the lastest version of autoupgrade.jar and patch specification containing MRP i found that OJVM patch is installed after MRP , which surprises me .

    patch1.patch=RU:19.27,OPATCH,OJVM,MRP

    Is it correct order : RU , then MRP , then OJVM ?

    $ORACLE_HOME/OPatch/opatch lspatches
    37499406;OJVM RELEASE UPDATE: 19.27.0.0.250415 (37499406)
    38145140;MERGE ON DATABASE RU 19.27.0.0.0 OF 36837787 37175666
    38145137;MERGE ON DATABASE RU 19.27.0.0.0 OF 34728524 38074341
    38080838;Fix for Bug 38080838
    38071741;WRONG RESULT ROWNUM IS DUPLICATED IN PARALLEL QUERY FROM UNION [ALL] WITH DISABLED ROWSETS
    38044116;LATCH ACTIVE SERVICE LIST EVENT AFTER APPLY DRU 19.27.0.0.250415
    38026197;MERGE ON DATABASE RU 19.27.0.0.0 OF 36637998 37014248
    37914344;WMSYS.WM$?$$ VIEWS MISSING AFTER APPLYING 19.27DBRU
    37899753;CREATING DB VIA OCI CONSOLE FAILED
    37899125;HIGH WAITS ON ENQ ZH AND COMPRESSION ANALYSIS AFTER UPGRADE TO 19.26
    37894648;THE OFS/FUSE GETS STUCK AFTER ALTER PLUGGABLE DATABASE CLOSE IMMEDIATE AND OPEN
    37890509;INTERMITTENT ORA-600 [KPSS-MIG-COST-DEC] WITH SIGNALING FUNCTION AS KKSCLOSECURSORCBK
    37831436;LOG FILE SYNC OBSERVED ON THE PRIMARY DATABASE.
    37790293;CROSS SHARD QUERIES THROW ORA-02019 AFTER APPLYING 19.25 DBRU
    37771855;DIA0 PROCESS DIES WITH ORA-7445 [KJZNCALCSAFESESSTIME] AFTER 19.26 RU UPGRADE
    37757910;ORA-03113 END-OF-FILE ON COMMUNICATION CHANNEL WHILE ACCESSING VIEWS FOR JSON/ORA-7445 [QCSJCJTABCHN] [SIGSEGV] [ADDR 0X7FFE92E17FC0]
    37693383;AIM ORA-600 [KCFIS_GET_DISK_FOR_TRANSLATION VOLUME LOOKUP] – KCFIS_GET_DISK_FOR_TRANSLATION
    37655622;THE CP -P COMMAND FAILS ON A DBFS MOUNTED DIRECTORY
    37641011;REMOVE LIBCURL FROM GDAL PACKAGE
    37450190;SECUREFILE LOB UPDATE SHOWS HIGH LEVEL OF WRITE COMPLETE WAITS
    37104857;AIM ORA-600 [KXHRPACK CVL2], [1], [0], [4] [PDB G39A3DB6B49FD2B_NSN0758267] – QERHN_KXHRPACK
    37082638;FIXED FOR BUG 35999766 CAUSED PEROFRMANCE ISSUE FOR QUERY WITH SET MARKUP CSV ON
    37063308;CT23.1MFSR_SCN4VI1_C2EIP – TRC – KXFPRIENQ – ORA-600 [15773]
    36785903;UNIFIED AUDIT RECORD WRITE TO AUDIT TRAIL TABLE FAILED DUE TO ORA-22990
    36501568;REMOVE REQUIREMENT TO SET TARGET_PDBS EVEN FOR SMALL SGA SYSTEMS
    34744415;TDM OCI-24550 CMOP DIED AT KPUXCPROCESSPIGGYBACKS()
    32761547;FAST TABLESPACE FREE SPACE COMPUTATION IN SERVERLESS AUTONOMOUS DB.
    37642901;Database Release Update : 19.27.0.0.250415 (37642901)
    29585399;OCW RELEASE UPDATE 19.3.0.0.0 (29585399)

    OPatch succeeded.

    regards

    Januš

    Like

Leave a reply to Januš Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.