FAQ: 12c Grid Infrastructure Management Repository (GIMR) (文档 ID 1568402.1)

In this Document

Purpose

Questions and Answers

What is Management Repository?

What's the purpose of Management Database?

Where does Management Database store it's datafiles?

What's the implications of not configuring Management Database during installation/upgrade OUI?

What are the resources associated with Management Database?

How to start Management Database if it's down?

How to "cd" to Management Database subdirectory to review trace file etc?

Is there any need to manually backup or tune Management Database?

Will GIMR be created in Oracle Restart by default?

How much (shared) disk space should be allocated for the Management Database?

Community Discussions

References

---

APPLIES TO:

Oracle Database - Enterprise Edition - Version 12.1.0.1 and later
Information in this document applies to any platform.

PURPOSE

This is a FAQ of 12c Grid Infrastructure new feature Management Database.

QUESTIONS AND ANSWERS

What is Management Repository?

Management Repository is a single instance database that's managed by Oracle Clusterware in 12c. As it's a single instance database, it will be up and running on one node in the cluster; as it's managed by GI, in case the hosting node is down, the database will be automatically failed over to other node.

 

What's the purpose of Management Database?

Management Database will be the central repository to store Cluster Health Monitor (aka CHM/OS, ora.crf) and other data in 12c. 

 

Where does Management Database store it's datafiles?

In 12.1, by default, Management database uses the same shared storage as OCR/Voting File.

 

What's the implications of not configuring Management Database during installation/upgrade OUI?

In 12.1.0.1, GIMR is optional, if Management Database is not selected to be configured during installation/upgrade OUI, all features (Cluster Health Monitor (CHM/OS) etc) that depend on it will be disabled.

Note: there's no supported procedure to enable Management Database once the GI stack is configured

This changed in 12.1.0.2, it's mandatory to have GIMR and it's not supported to be turned off

  

What are the resources associated with Management Database?

The following resources from "crsctl stat res -t" are for Management Database: 

ora.mgmtdb
1 ONLINE ONLINE racnode1f Open,STABLE

ora.MGMTLSNR
1 ONLINE ONLINE racnode1f 169.254.118.96 10.3.0.70,STABLE

On OS level, the database "-MGMTDB" and listener MGMTLSNR are for Management Database: 

ps -ef| grep pmon_-MGMTDB

grid 3500 1 0 Jun04 ? 00:06:18 mdb_pmon_-MGMTDB

ps -ef| grep MGMTLSNR

grid 3308 1 0 Jun04 ? 00:00:55 /ocw/c101/bin/tnslsnr MGMTLSNR -no_crs_notify -inherit

 

How to start Management Database if it's down?

Management Database is managed by GI and should be up and running all the time automatically. In case it's down for some reason, the following srvctl command can be used to start it:

Usage: srvctl start mgmtdb [-startoption <start_option>] [-node <node_name>]
Usage: srvctl start mgmtlsnr [-node <node_name>]

 

How to "cd" to Management Database subdirectory to review trace file etc?

Generally speaking it's unnecessary to review trace file for Management Database. In case there's a need, as the database name starts with "-" sign, "./" needs to be specified to avoid the following error: 

cd -MGMTDB
-bash: cd: -M: invalid option
cd: usage: cd [-L|-P] [dir]

cd ./-MGMTDB        ==>> this will work as "./" is specified

more -MGMTDB_m000_9912.trc
more: unknown option "-M"
usage: more [-dflpcsu] [+linenum | +/pattern] name1 name2 ...

 

more ./-MGMTDB_m000_9912.trc
Trace file /home/grid/app/grid/diag/rdbms/_mgmtdb/-MGMTDB/trace/-MGMTDB_m000_9912.trc
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, Advanced Analytics and Management Database options

 

Is there any need to manually backup or tune Management Database?

As of now, there's no such need.

 

Will GIMR be created in Oracle Restart by default?

No, GIMR will not be created in Oracle Restart.

  

 

How much (shared) disk space should be allocated for the Management Database?

For:  Oracle Cluster Registry (OCR) with external redundancy and the Grid Infrastructure Management Repository

Minimum:  At least 5.2 GB for the OCR volume that contains the Grid Infrastructure Management Repository (4.5 GB + 300 MB voting files + 400 MB OCR), plus 500 MB for each node for clusters greater than four nodes. For example, a six-node cluster allocation should be 6.2 GB.

Reference:  http://docs.oracle.com/database/121/CWLIN/storage.htm#CHDDCAHD