Tras una instalación vimos en un cliente que no estaba la base de datos del MGMTDB creada pero que tenía el diskgroup.
Revisando la nota «MDBUtil: GI Management Repository configuration tool (Doc ID 2065175.1)» decidimos añadirla a mano.
Comprobamos que no existe:
[root@nodo01 tmp]# crsctl stat res -w "NAME = ora.mgmtdb"
Comprobamos el diskgroup sobre el que lo instalaremos:
[root@nodo01 sfw]# crsctl stat res -t -w "TYPE = ora.diskgroup.type"
--------------------------------------------------------------------------------
Name Target State Server State details
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.PROADMIN.dg(ora.asmgroup)
1 ONLINE ONLINE nodo01 STABLE
2 ONLINE ONLINE nodo02 STABLE
ora.PRODATA.dg(ora.asmgroup)
1 ONLINE ONLINE nodo01 STABLE
2 ONLINE ONLINE nodo02 STABLE
ora.PROFRA.dg(ora.asmgroup)
1 ONLINE ONLINE nodo01 STABLE
2 ONLINE ONLINE nodo02 STABLE
ora.PROMGMTDB.dg(ora.asmgroup)
1 ONLINE ONLINE nodo01 STABLE
2 ONLINE ONLINE nodo02 STABLE
ora.PROVOTOCR.dg(ora.asmgroup)
1 ONLINE ONLINE nodo01 STABLE
2 ONLINE ONLINE nodo02 STABLE
--------------------------------------------------------------------------------
[root@nodo01 sfw]# asmcmd lsdg PROMGMTDB
State Type Rebal Sector Logical_Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED NORMAL N 512 512 4096 4194304 547200 543608 136800 203404 0 N PROMGMTDB/
Importante tener el script copiado en el resto de nodos del cluster en la misma ubicación y con permisos de ejecución!
Creamos la base de datos GIMR como usuario oracle:
[oracle@nodo01 sfw]$ ./mdbutil.pl --addmdb --target=+PROMGMTDB
mdbutil.pl version : 1.98
2019-07-19 11:25:38: I Starting To Configure MGMTDB at +PROMGMTDB...
2019-07-19 11:26:13: I Container database creation in progress... for GI 19.0.0.0.0
2019-07-19 12:22:38: I Plugable database creation in progress...
2019-07-19 12:35:24: I Executing "/tmp/mdbutil.pl --addchm" on nodo01 as root to configure CHM.
root@nodo01's password:
2019-07-19 12:49:54: I Executing "/tmp/mdbutil.pl --addchm" on nodo02 as root to configure CHM.
root@nodo02's password:
2019-07-19 12:51:57: I MGMTDB & CHM configuration done!
Chequeamos el status de la GIMR:
[oracle@nodo01 sfw]$ ./mdbutil.pl --status
mdbutil.pl version : 1.98
2019-07-19 12:55:25: I Checking CHM status...
2019-07-19 12:55:52: I Listener MGMTLSNR is configured and running on nodo01
2019-07-19 12:56:03: I Database MGMTDB is configured and running on nodo01
2019-07-19 12:56:04: I Cluster Health Monitor (CHM) is configured and running
--------------------------------------------------------------------------------
CHM Repository Path = +PROMGMTDB/_MGMTDB/8E072DBEAB6C786EE0550221F648E09F/DATAFILE/sysmgmtdata.287.1014035611
MGMTDB space used on DG +PROMGMTDB = 23562 Mb
--------------------------------------------------------------------------------
Comprobamos que ahora ya sí existe:
[root@nodo01 tmp]# crsctl stat res -w "NAME = ora.mgmtdb"
NAME=ora.mgmtdb
ENGINE=ora.mgmtdb.type
TARGET=ONLINE
STATE=ONLINE on nodo01
En caso de que diera algún error se puede lanzar en modo debug con la opción «-debug».