1.
MGMTDB is a container used to store the
diagnostic information collected by Cluster Health Monitor (CHM).
2.
It is the single instance database managed by
Oracle clusterware in Oracle 12c, in 11g we used to have Berkley database for
the same purpose.
3.
Having MGMTDB is optional in 12.1.0.1, you can choose
whether to have it or not during the time of Clusterware setup or upgrade from
older versions to 12.1.0.1. But in 12.1.0.2 it become mandatory to have MGMTDB.
4.
MGMTDB runs on the master node (i.e. on which
node MGMTDB runs, we can consider that as Master node).
5.
If the node where Management Database running
crashes, automatically MGMTDB will be failed over to another node.
6.
Management database will be stored on the same
storage as OCR and VOTING disks. So, if you go with MGMTDB option in 12c, you
should have more than 5GB space for OCR and VOTING disks.
If you use the small size disks it will not
allow you to setup/upgrade clusterware.
Commands on MGMTDB
1.
Finding on which node MGMTDB is running:
$
oclumon manage -get MASTER
Master = rac1
2.
Status of the MGMTDB
$srvctl status mgmtdb
Database is enabled
Instance -MGMTDB is
running on node rac1
3.
Configuration of ManagementDB (MGMTDB)
$ srvctl config mgmtdb
Database unique
name: _mgmtdb
Database name:
Oracle home: <CRS
home>
Oracle user: oragrid
Spfile:
+OCR_VOTE/_MGMTDB/PARAMETERFILE/spfile.268.915007725
Password file:
Domain:
Start options: open
Stop options: immediate
Database role:
PRIMARY
Management policy:
AUTOMATIC
Type: Management
PDB name:
crs_linux
PDB service:
crs_linux
Cluster name:
crs-linux
Database instance:
-MGMTDB
4.
Location of Cluster Health Monitor (CHM)
repository
$ oclumon manage -get reppath
CHM Repository Path
= +OCR_VOTE/_MGMTDB/FD9B43BF6A646F8CE043B6A9E80A2815/DATAFILE/sysmgmtdata.269.915007863
5.
CHM Repository size
$ oclumon manage -get repsize
CHM Repository Size
= 136320 seconds
No comments:
Post a Comment