Cuando queremos crearnos una maqueta de 12.2 no podemos prescindir del repositorio de Cluster Health Monitor, la base de datos -MGMTDB. Para crear esta base de datos el instalador requiere de 40GB de diskgroup.
A continuación os dejo el procedimiento para hacer el resize de esa base de datos y dejarla en unos 3G.
Version: 12.2.0.1
Referencias:
MDBUtil: GI Management Repository configuration tool (Doc ID 2065175.1)
How to Move/Recreate GI Management Repository (GIMR / MGMTDB) to Different Shared Storage (Diskgroup, CFS or NFS etc) (Doc ID 1589394.1)
-- Deshabilitamos CHM
crsctl stop res ora.crf -init
crsctl modify res ora.crf -attr ENABLED=0 -init
ALTER SESSION SET CONTAINER = GIMR_DSCREP_10;
CREATE USER MOGU identified by temporal1;
GRANT CONNECT TO MOGU;
GRANT DBA TO MOGU;
CREATE OR REPLACE DIRECTORY EXPORT AS '/export/home/oracle/export';
GRANT WRITE, READ ON DIRECTORY EXPORT TO MOGU;
GIMR_DSCREP_10 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.163.1.100)(PORT = 1525))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = gimr_dscrep_10)
)
)
-- como backup
expdp MOGU/temporal1@GIMR_DSCREP_10 dumpfile=exp_schema_cha.dmp directory=export nologfile=yes schemas=CHA
ALTER SESSION SET CONTAINER = GIMR_DSCREP_10;
DROP USER CHA CASCADE;
DROP TABLESPACE SYSMGMTDATACHAFIX INCLUDING CONTENTS AND DATAFILES;
CREATE TABLESPACE SYSMGMTDATACHAFIX DATAFILE SIZE 200M;
impdp MOGU/temporal1@GIMR_DSCREP_10 dumpfile=exp_schema_cha.dmp directory=export nologfile=yes schemas=CHA;
GRANT READ ON SYS.V_$ASM_DISKGROUP TO CHA;
GRANT READ ON SYS.V_$EVENT_NAME TO CHA;
GRANT READ ON SYS.V_$SESSION TO CHA;
GRANT READ ON SYS.DBA_DATA_FILES TO CHA;
GRANT EXECUTE ON DBMS_CRYPTO TO CHA;
GRANT EXECUTE ON DBMS_LOCK TO CHA;
GRANT EXECUTE ON DBMS_SYSTEM TO CHA;
ALTER PACKAGE CHA.CHA_CAL_DATA COMPILE;
ALTER PACKAGE CHA.CHA_LCMGMT COMPILE;
ALTER PACKAGE CHA.CHA_TEMP_MODEL COMPILE;
ALTER PACKAGE CHA.FTE_MGMT COMPILE;
ALTER PROCEDURE CHA.GLOBAL_LOCK COMPILE;
ALTER DATABASE DATAFILE '+DATA2/_MGMTDB/78F606F9409B08BDE054080027A68F12/DATAFILE/sysmgmtdata.282.990353579' RESIZE 200M;
ALTER DATABASE DATAFILE '+DATA2/_MGMTDB/78F606F9409B08BDE054080027A68F12/DATAFILE/syscalogdata.281.990353553' RESIZE 100M;
ALTER DATABASE DATAFILE '+DATA2/_MGMTDB/78F606F9409B08BDE054080027A68F12/DATAFILE/sysmgmtdatadb.283.990353639' RESIZE 200M;
-- Redimensionamos los redologs.
ALTER DATABASE ADD LOGFILE SIZE 100M;
ALTER DATABASE ADD LOGFILE SIZE 100M;
ALTER DATABASE ADD LOGFILE SIZE 100M;
ALTER DATABASE DROP LOGFILE GROUP 2;
ALTER DATABASE DROP LOGFILE GROUP 3;
alter system switch logfile;
alter system checkpoint;
ALTER DATABASE DROP LOGFILE GROUP 1;
Validamos el tamaño:
/*
Diskgroup / DB Name File Type Space MB Sys?
---------------------------------------- ------------------ ------------------ ----
+DATA2/ASM PASSWORD 0 Y
**************************************** ------------------
0
+DATA2/clmds OCRFILE 160 Y
OCRBACKUP 8 Y
ASMPARAMETERFILE 1 Y
**************************************** ------------------
169
+DATA2/_mgmtdb DATAFILE 3,308 Y
TEMPFILE 246 Y
ONLINELOG 306 Y
CONTROLFILE 24 Y
PARAMETERFILE 1 Y
**************************************** ------------------
3,885
+DATA2/orapwasm PASSWORD 0 N
**************************************** ------------------
0
+DATA2/orapwasm_backup PASSWORD 0 N
**************************************** ------------------
0
------------------
Grand Total: 4,054
*/
-- Intentamos parar la instancia -MGMTDB
su - grid
export ORACLE_SID=-MGMTDB
SQL> shutdown immediate
crsctl status resurce ora.mgmtdb -p
srvctl disable mgmtdb
Oracle Live 