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

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

With Oracle Grid Infrastructure 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 here:

  • Automatic Installation of Grid Infrastructure Management Repository

    The Grid Infrastructure Management Repository is automatically installed with Oracle Grid Infrastructure 12crelease 1 ( 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 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
    $CRS_HOME/bin/oclumon manage -repos changeretentiontime 260000
  • Change the retention
    $CRS_HOME/bin/oclumon manage -repos checkretentiontime 260000


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:


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!



Do you have any idea when will be available for Win 7 64 bit?

Posted by Rajesh on August 22, 2014 at 04:49 PM CEST #


I can't give you a date but it should be there in less than 4 weeks :-)

Cheers, Mike

Posted by Mike on August 22, 2014 at 05:16 PM CEST #


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

Any suggestions.

Posted by jay on August 23, 2014 at 10:16 AM CEST #

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

Posted by Mike on August 24, 2014 at 11:31 PM CEST #

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 ;-)

Posted by guest on September 11, 2014 at 06:36 PM CEST #

I really don't know - but I can recommend everybody to log an SR and ask support to log a bug/enhancement for it.


Posted by Mike on September 12, 2014 at 10:44 AM CEST #

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.


Posted by guest on October 29, 2014 at 10:34 AM CET #

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.


Posted by ChrisM on October 29, 2014 at 10:36 AM CET #

thanks a lot - I'll fix it in a second!!!


Posted by Mike on October 30, 2014 at 06:58 PM CET #

Does the mgmtdb need to be backed up using RMAN?

Posted by guest on November 07, 2014 at 08:46 PM CET #

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.


Posted by Mike on November 07, 2014 at 08:48 PM CET #


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?


Posted by guest on January 09, 2015 at 04:25 PM CET #

I see SYS SYSTEM are manged by the default profile. Do I need to manage these accounts so that passords do not expire?

Thanks for the help

Posted by sam newberry on January 09, 2015 at 04:29 PM CET #


it's not critical for GI - the health monitor simply won't be able to store data.


Posted by Mike on January 09, 2015 at 05:13 PM CET #


you don't have to manage those accounts separately - their passwords don't expire by default.


Posted by Mike on January 09, 2015 at 05:14 PM CET #

Hi Mike,

Im looking for information about patching. The README for 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!

Posted by Axel D on January 22, 2015 at 09:53 AM CET #


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!)


Posted by Mike on January 24, 2015 at 05:19 PM CET #

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?

Posted by Stefan on March 11, 2015 at 04:18 PM CET #

Thanks a million for the correction!!! I have included it into the post!


Posted by Mike on March 12, 2015 at 10:34 AM CET #

Dear all, Mike,

given some of the comments or for a general update to this topic, you might be interest in the following article:


Posted by Markus on July 31, 2015 at 06:44 AM CEST #

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?

Posted by cris on September 05, 2015 at 02:59 PM CEST #


please see:

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

in the blog post :-)


Posted by Mike on September 07, 2015 at 09:47 AM CEST #

Post a Comment:
  • HTML Syntax: NOT allowed

Mike Dietrich - Oracle Mike Dietrich
Master Product Manager - Database Upgrade & Migrations - Oracle

Based in Germany. Interlink between customers/partners and the Upgrade Development. Running workshops between Arctic and Antartica. Assisting customers in their reference projects onsite and remotely. Connect via:

- -


« July 2016
Slides Download Center
Visitors since 17-OCT-2011
White Paper and Docs
Viewlets and Videos
Workshop Map
x Oracle related Tech Blogs
This week on my Rega & Pono
Upgrade Reference Papers