Grid Infrastructure Management Repository (GIMR)
database now mandatory in Oracle GI 12.1.0.2

During the installation of Oracle Grid Infrastructure 12.1.0.1 you’ve had the following option to choose YES/NO to install the Grid Infrastructure Management Repository (GIMR) database MGMTDB:

With Oracle Grid Infrastructure 12.1.0.2 this choice has become obsolete and the above screen does not appear anymore. The GIMR database has become mandatory.

What gets stored in the GIMR?

See the changes in Oracle Clusterware 12.1.0.2 here:

  • Automatic Installation of Grid Infrastructure Management Repository

    The Grid Infrastructure Management Repository is automatically installed with Oracle Grid Infrastructure 12crelease 1 (12.1.0.2). The Grid Infrastructure Management Repository enables such features as Cluster Health Monitor, Oracle Database QoS Management, and Rapid Home Provisioning, and provides a historical metric repository that simplifies viewing of past performance and diagnosis of issues. This capability is fully integrated into Oracle Enterprise Manager Cloud Control for seamless management.

Furthermore what the doc doesn’t say explicitly:

    • The -MGMTDB has now become a single-tenant deployment having a CDB with one PDB
      • This will allow the use of a Utility Cluster that can hold the CDB for a collection of GIMR PDBs
    • When you’ve had already an Oracle 12.1.0.1 GIMR this database will be destroyed and recreated
      • Preserving the CHM/OS data can be acchieved with OCULMON to dump it out into node view
    • The data files associated with it will be created within the same disk group as OCR or VOTING
      •  The OUI will get the disk groups for OCR and Voting and chooses the first one – which usually is the first OCR. This may lead to serious space issues. It is tracked internally as Bug:19661882  In a future release there may be an option offered to put in into a separate disk group.
        Workaround would be to move the affected OCR to another disk group (use ocrconfig command for it) – see MOS Note:1589394.1
    • Some important MOS Notes:
      • MOS Note 1568402.1
        FAQ: 12c Grid Infrastructure Management Repository, states there’s no supported procedure to enable Management Database once the GI stack is configured
      • MOS Note: 1921105.1
        Managing the Cluster Health Monitor
        Repository (incl how to resize)  
      • MOS Note 1589394.1
        How to Move GI Management Repository to Different Shared Storage
        (shows how to delete and recreate the MGMTDB)
      • MOS Note 1631336.1
        Cannot delete Management Database (MGMTDB) in 12.1
      • MOS Note 1945558.1
        _mgmtdb Service Registered with All Local Listeners in a Grid Infrastructure Environment
    • Average growth size per day per node is roughly 650-750 MB. E.g. a 4 node cluster would lead at the default retention of 3 days to an approximate size of  5.9-6.8 GB
    • Change the retention 12.1.0.1:
      $CRS_HOME/bin/oclumon manage -repos changeretentiontime 260000

Change the retention 12.1.0.2:

$CRS_HOME/bin/oclumon manage -repos checkretentiontime 260000

Update:

Markus Michalewicz, our Director of Product Management, Oracle Real Application Clusters (RAC), has published a very interesting and helpful insight article about GIMR on July 30, 2015. Read it here:
https://www.linkedin.com/pulse/how-handle-oracle-gimr-markus-michalewicz


–Mike

PS: Kudos to Sebastian Solbach who updated me on the things to add (retention, average growth, OUI choosing the first disk group displayed for the MGMTDB) – cheers!

28 thoughts on “Grid Infrastructure Management Repository (GIMR)
database now mandatory in Oracle GI 12.1.0.2

  1. Hi,

    We have installed 12.1.0.2.0 successfully for 2 node Linux 64 machines but MGMTDB(GIMR) is not created on either nodes.

    Any suggestions.

  2. Hi there,

    please see the MOS Notes I have linked at the end – it shows you how to create it when the creation failed. And you may open an SR with Support to have them check what the reason has been for non-creation.

    Cheers, Mike

  3. Hi Mike,

    would you happen to know if Oracle plans on giving us the choice of where to install mgmtdb in future patchsets?
    I’ve done the .1 to .2 upgrade in our development environment, just to discover that with normal redundancy (3 voting disks), even 8G is not big enough any more 😉

  4. Hi Mike,

    just a info … clicking on the link for MoS note #1568402.1 leads me to Mos note #1589394.1. Means the first and second MoS note links are the same in the link destination.

    cheers
    Chris

  5. Hi Mike,

    just a info … clicking on the link for MoS note #1568402.1 leads me to Mos note #1589394.1. Means the first and second MoS note links are the same in the link destination.

    cheers
    Chris

  6. No, it doesn’t need to be backed up in any way. If it should get lost than it can be recreated – just 3 days of performance data lost. It runs in nologging mode anyways – so no need to think about maintenance or backups.

    Cheers
    Mike

  7. Hi,

    I attended th 12c upgrade seminar hosted by Roy Swonger in Chicago 1/8. Can MGMTDB be shut down without affecting the GRID if client does not see the need for the database? Or is the database critical to the GI?

    Thanks

  8. Hi Mike,

    Im looking for information about patching. The README for 12.1.0.2.2 PSU doesn’t tell me anything about MGMTDB. Will it be patched automatically (opatchauto) as part of "Patching Oracle RAC Database Homes and GI Together"? Or do I have to patch the MGMTDB seperately? And do I have to "Load Modify SQL Files into the MGMTDB"?

    Thanks in advance!
    Axel

  9. Alex,

    the design of the MGMTDB is a "no admin required" design. Actually the binary will be patched automatically once you apply a PSU or BP to the GI Home.

    For your question about the SQL part you will have to open an SR as I’m not able to answer this – I have an idea but please double check with Oracle Support (sorry!)

    Cheers
    Mike

  10. Hi Mike,

    please note that the command should be

    $CRS_HOME/bin/oclumon manage -repos changeretentiontime 26000
    (instead of checkretentiontime)

    Trying to run this we get error:
    Failed change retention. Error returned ORA-28001: the password has expired

    Which user is used for that as neither sys nor system account is expired?

  11. Hi Mike,
    Question, is it mandatory to store gimr on the vote+ocr diskgroup? if i move it on another group where i have ocr mirror it will be a problem in the future?
    thanks

  12. Christian,

    please see:

    MOS Note 1589394.1
    How to Move GI Management Repository to Different Shared Storage

    in the blog post 🙂

    Cheers
    Mike

  13. Pingback: Grid Infrastructure Management Repository (GIMR) – Datapatch? | Upgrade your Database - NOW!

  14. Pingback: GIMR DB in Oracle Database 12.2 | Upgrade your Database - NOW!

Leave a Reply

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