This blog post has been superseded by updated information at Mike Dietrich's Oracle Database Upgrade Blog:
Grid Infrastructure Management Repository (GIMR) database now mandatory in Oracle GI 220.127.116.11
Do you have any idea when 18.104.22.168 will be available for Win 7 64 bit?
I can't give you a date but it should be there in less than 4 weeks :-)
We have installed 22.214.171.124.0 successfully for 2 node Linux 64 machines but MGMTDB(GIMR) is not created on either nodes.
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.
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 ;-)
I really don't know - but I can recommend everybody to log an SR and ask support to log a bug/enhancement for it.
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.
thanks a lot - I'll fix it in a second!!!
Does the mgmtdb need to be backed up using RMAN?
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.
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?
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
it's not critical for GI - the health monitor simply won't be able to store data.
you don't have to manage those accounts separately - their passwords don't expire by default.
Im looking for information about patching. The README for 126.96.36.199.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
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!)
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?
Thanks a million for the correction!!! I have included it into the post!
Dear all, Mike,
given some of the comments or for a general update to this topic, you might be interest in the following article: https://www.linkedin.com/pulse/how-handle-oracle-gimr-markus-michalewicz?trk=pulse-det-nav_art
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
MOS Note 1589394.1 How to Move GI Management Repository to Different Shared Storage
in the blog post :-)
very Nice tips! Thank you for note 1589394.13
Can the MGMTDB database exist outside of ASM, on a shared nfs filesystem?
Clear answer: No.
Some very helpful MOS Notes got published
regarding the upgrade to Oracle Database
MOS Note: 2173141.1
Complete Checklist for Manual...
I've had an interesting discussion today. Somebody removed OLAP
with chopt - and got issues afterwards.
My guess: chopt will only remove...
This blog post is an addition to:
Full Transportable Export/Import - Migration an
188.8.131.52 database to Oracle Database 12c - into the...