DiskGroup GRID: Entendendo o seu conteúdo

Olá pessoal,

Neste post vamos explicar basicamente qual é o conteúdo do DiskGroup que é instalado por padrão quando você instala o Grid Infrastructure (GI) numa configuração de Cluster Stand Alone.

Este post se aplica à:

Versões:

12.2.0.1;
18c;
19c.

Ambientes:

OnPremises;
Cloud.

Quando você instala o cluster, você pode optar por criar um DiskGroup separado para o GIMR (Grid Infrastructure Management Repository). Neste post nós consideraremos que você não criou um DiskGroup separado para o GIMR, portanto, o GIMR será alocado no DiskGroup padrão criado na instalação do GI.

Bom, esclarecido isso, vamos identificar quais são os pré-requisitos de espaço em disco para o diskgroup que será criado por padrão quando você instalar o GI.

Vamos chamar o DiskGroup padrão de OBQ_GRID1. Apenas como exemplo.

Eu SEMPRE recomendarei que você crie o DiskGroup padrão com redundância HIGH ou NORMAL. Porque?

Quando você cria o DiskGroup OBQ_GRID com redundância externa (EXTERNAL), automaticamente será criado apenas 1 Voting Disk;
Quando você cria o DiskGroup OBQ_GRID1 com redundância normal (NORMAL) e o mesmo possui 3 discos de igual tamanho, serão criados automaticamente 3 Voting Disks;
Quando você cria o DiskGroup OBQ_GRID com redundância alta (HIGH) e o mesmo possui 5 discos de igual tamanho, serão criados automaticamente 5 Voting Disks;

O Voting Disk é um arquivo primordial para o funcionamento do cluster. Apesar de antigo, você pode ler um pouco sobre o Voting Disk neste meu post de 9 anos atrás, na época do Cluster 10g Release 2:

Oracle Clusterware – Arquitetura – Parte 2 – Principais Arquivos: Voting Disk e OCR

Sabendo que é um arquivo primordial para o cluster, o ideal é garantirmos redundância para este arquivo, e isso só é atingido se utilizarmos o DiskGroup com redundância NORMAL ou HIGH.

Você pode conferir isso também na documentação oficial:

Tendo esclarecido também esse item, vamos então verificar qual é o conteúdo do nosso DiskGroup padrão.

Com o usuário grid:

[grid@dbnode01 ~]$ asmcmd

ASMCMD> find +obq_grid1 *

+obq_grid1/ASM/

+obq_grid1/ASM/DATAFILE/

+obq_grid1/ASM/DATAFILE/sysaux.20190613142557.dbf.258.1010845615

+obq_grid1/ASM/DATAFILE/sysaux.20190613142557.dbf.263.1010845627

+obq_grid1/ASM/DATAFILE/sysaux.20190613142557.dbf.268.1010845639

+obq_grid1/ASM/DATAFILE/syscalogdata.20190613142557.dbf.270.1010845653

+obq_grid1/ASM/DATAFILE/sysgridhomedata.20190613142557.dbf.269.1010845649

+obq_grid1/ASM/DATAFILE/sysmgmtdata.20190613142557.dbf.281.1010845665

+obq_grid1/ASM/DATAFILE/sysmgmtdatachafix.20190613142557.dbf.279.1010845853

+obq_grid1/ASM/DATAFILE/sysmgmtdatadb.20190613142557.dbf.280.1010845687

+obq_grid1/ASM/DATAFILE/sysmgmtdataq.20190613142557.dbf.278.1010845951

+obq_grid1/ASM/DATAFILE/system.20190613142557.dbf.259.1010845605

+obq_grid1/ASM/DATAFILE/system.20190613142557.dbf.262.1010845633

+obq_grid1/ASM/DATAFILE/system.20190613142557.dbf.267.1010845645

+obq_grid1/ASM/DATAFILE/undotbs1.20190613142557.dbf.261.1010845621

+obq_grid1/ASM/DATAFILE/undotbs1.20190613142557.dbf.264.1010845625

+obq_grid1/ASM/DATAFILE/undotbs1.20190613142557.dbf.265.1010845637

+obq_grid1/ASM/DATAFILE/users.20190613142557.dbf.266.1010845649

+obq_grid1/ASM/PASSWORD/

+obq_grid1/ASM/PASSWORD/pwdasm.256.1010754289

+obq_grid1/ASM/PASSWORD/pwdasm.257.1010754749

+obq_grid1/_MGMTDB/

+obq_grid1/_MGMTDB/8B23E8D5953F1741E053A138A8C05D72/

+obq_grid1/_MGMTDB/8B23E8D5953F1741E053A138A8C05D72/TEMPFILE/

+obq_grid1/_MGMTDB/8B23E8D5953F1741E053A138A8C05D72/TEMPFILE/TEMP.282.1010846037

+obq_grid1/_MGMTDB/8B24053869A92CB2E053A138A8C08983/

+obq_grid1/_MGMTDB/8B24053869A92CB2E053A138A8C08983/TEMPFILE/

+obq_grid1/_MGMTDB/8B24053869A92CB2E053A138A8C08983/TEMPFILE/TEMP.283.1010846043

+obq_grid1/_MGMTDB/CONTROLFILE/

+obq_grid1/_MGMTDB/CONTROLFILE/Current.277.1010845967

+obq_grid1/_MGMTDB/CONTROLFILE/ctrl.20190613142557

+obq_grid1/_MGMTDB/DATAFILE/

+obq_grid1/_MGMTDB/DATAFILE/PDB$SEED/

+obq_grid1/_MGMTDB/DATAFILE/PDB$SEED/sysaux.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/PDB$SEED/system.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/PDB$SEED/undotbs1.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/sysaux.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/syscalogdata.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/sysgridhomedata.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/sysmgmtdata.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/sysmgmtdatachafix.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/sysmgmtdatadb.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/sysmgmtdataq.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/system.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/undotbs1.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/users.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/sysaux.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/system.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/undotbs1.20190613142557.dbf

+obq_grid1/_MGMTDB/ONLINELOG/

+obq_grid1/_MGMTDB/ONLINELOG/group_1.276.1010845969

+obq_grid1/_MGMTDB/ONLINELOG/group_2.275.1010845969

+obq_grid1/_MGMTDB/ONLINELOG/group_3.273.1010845983

+obq_grid1/_MGMTDB/ONLINELOG/group_4.272.1010845985

+obq_grid1/_MGMTDB/ONLINELOG/group_5.271.1010845987

+obq_grid1/_MGMTDB/ONLINELOG/redo1.20190613142557.log

+obq_grid1/_MGMTDB/ONLINELOG/redo2.20190613142557.log

+obq_grid1/_MGMTDB/ONLINELOG/redo3.20190613142557.log

+obq_grid1/_MGMTDB/ONLINELOG/redo4.20190613142557.log

+obq_grid1/_MGMTDB/PARAMETERFILE/

+obq_grid1/_MGMTDB/PARAMETERFILE/spfile.20190613142557

+obq_grid1/_MGMTDB/PARAMETERFILE/spfile.260.1010845565

+obq_grid1/_MGMTDB/TEMPFILE/

+obq_grid1/_MGMTDB/TEMPFILE/PDB$SEED/

+obq_grid1/_MGMTDB/TEMPFILE/TEMP.274.1010846033

+obq_grid1/_MGMTDB/TEMPFILE/crsdrlq2db/

+obq_grid1/crsdrlq2db/

+obq_grid1/crsdrlq2db/ASMPARAMETERFILE/

+obq_grid1/crsdrlq2db/ASMPARAMETERFILE/REGISTRY.253.1010754285

+obq_grid1/crsdrlq2db/OCRFILE/

+obq_grid1/crsdrlq2db/OCRFILE/REGISTRY.255.1010754291

+obq_grid1/orapwasm

+obq_grid1/orapwasm_backup

Vamos segregar o conteúdo por diretório:

Na listagem abaixo vemos os datafiles do GIMR (MGMTDB):

+obq_grid1/ASM/

+obq_grid1/ASM/DATAFILE/

+obq_grid1/ASM/DATAFILE/sysaux.20190613142557.dbf.258.1010845615

+obq_grid1/ASM/DATAFILE/sysaux.20190613142557.dbf.263.1010845627

+obq_grid1/ASM/DATAFILE/sysaux.20190613142557.dbf.268.1010845639

+obq_grid1/ASM/DATAFILE/syscalogdata.20190613142557.dbf.270.1010845653

+obq_grid1/ASM/DATAFILE/sysgridhomedata.20190613142557.dbf.269.1010845649

+obq_grid1/ASM/DATAFILE/sysmgmtdata.20190613142557.dbf.281.1010845665

+obq_grid1/ASM/DATAFILE/sysmgmtdatachafix.20190613142557.dbf.279.1010845853

+obq_grid1/ASM/DATAFILE/sysmgmtdatadb.20190613142557.dbf.280.1010845687

+obq_grid1/ASM/DATAFILE/sysmgmtdataq.20190613142557.dbf.278.1010845951

+obq_grid1/ASM/DATAFILE/system.20190613142557.dbf.259.1010845605

+obq_grid1/ASM/DATAFILE/system.20190613142557.dbf.262.1010845633

+obq_grid1/ASM/DATAFILE/system.20190613142557.dbf.267.1010845645

+obq_grid1/ASM/DATAFILE/undotbs1.20190613142557.dbf.261.1010845621

+obq_grid1/ASM/DATAFILE/undotbs1.20190613142557.dbf.264.1010845625

+obq_grid1/ASM/DATAFILE/undotbs1.20190613142557.dbf.265.1010845637

+obq_grid1/ASM/DATAFILE/users.20190613142557.dbf.266.1010845649

Na listagem abaixo vemos o password file do ASM:

+obq_grid1/ASM/PASSWORD/

+obq_grid1/ASM/PASSWORD/pwdasm.256.1010754289

+obq_grid1/ASM/PASSWORD/pwdasm.257.1010754749

Na listagem abaixo vemos os datafiles, tempfiles, controlfiles e online redo logs do GIMR/MGMTDB:

+obq_grid1/_MGMTDB/

+obq_grid1/_MGMTDB/8B23E8D5953F1741E053A138A8C05D72/

+obq_grid1/_MGMTDB/8B23E8D5953F1741E053A138A8C05D72/TEMPFILE/

+obq_grid1/_MGMTDB/8B23E8D5953F1741E053A138A8C05D72/TEMPFILE/TEMP.282.1010846037

+obq_grid1/_MGMTDB/8B24053869A92CB2E053A138A8C08983/

+obq_grid1/_MGMTDB/8B24053869A92CB2E053A138A8C08983/TEMPFILE/

+obq_grid1/_MGMTDB/8B24053869A92CB2E053A138A8C08983/TEMPFILE/TEMP.283.1010846043

+obq_grid1/_MGMTDB/CONTROLFILE/

+obq_grid1/_MGMTDB/CONTROLFILE/Current.277.1010845967

+obq_grid1/_MGMTDB/CONTROLFILE/ctrl.20190613142557

+obq_grid1/_MGMTDB/DATAFILE/

+obq_grid1/_MGMTDB/DATAFILE/PDB$SEED/

+obq_grid1/_MGMTDB/DATAFILE/PDB$SEED/sysaux.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/PDB$SEED/system.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/PDB$SEED/undotbs1.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/sysaux.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/syscalogdata.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/sysgridhomedata.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/sysmgmtdata.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/sysmgmtdatachafix.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/sysmgmtdatadb.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/sysmgmtdataq.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/system.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/undotbs1.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db/users.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/sysaux.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/system.20190613142557.dbf

+obq_grid1/_MGMTDB/DATAFILE/undotbs1.20190613142557.dbf

+obq_grid1/_MGMTDB/ONLINELOG/

+obq_grid1/_MGMTDB/ONLINELOG/group_1.276.1010845969

+obq_grid1/_MGMTDB/ONLINELOG/group_2.275.1010845969

+obq_grid1/_MGMTDB/ONLINELOG/group_3.273.1010845983

+obq_grid1/_MGMTDB/ONLINELOG/group_4.272.1010845985

+obq_grid1/_MGMTDB/ONLINELOG/group_5.271.1010845987

+obq_grid1/_MGMTDB/ONLINELOG/redo1.20190613142557.log

+obq_grid1/_MGMTDB/ONLINELOG/redo2.20190613142557.log

+obq_grid1/_MGMTDB/ONLINELOG/redo3.20190613142557.log

+obq_grid1/_MGMTDB/ONLINELOG/redo4.20190613142557.log

+obq_grid1/_MGMTDB/PARAMETERFILE/

+obq_grid1/_MGMTDB/PARAMETERFILE/spfile.20190613142557

+obq_grid1/_MGMTDB/PARAMETERFILE/spfile.260.1010845565

+obq_grid1/_MGMTDB/TEMPFILE/

+obq_grid1/_MGMTDB/TEMPFILE/PDB$SEED/

+obq_grid1/_MGMTDB/TEMPFILE/TEMP.274.1010846033

+obq_grid1/_MGMTDB/TEMPFILE/crsdrlq2db/

Mas ora, se a primeira listagem trazia os arquivos do GIMR/MGMTDB, como temos novamente esta listagem? Bom, todos os datafiles listados em +obq_grid1/mgmtdb/datafile são aliases apontando para os arquivos físicos propriamente ditos em +obq_grid1/asm/datafile. Vamos verificar?

ASMCMD> cd +obq_grid1/_MGMTDB/DATAFILE/

ASMCMD> ls -l

Type      Redund  Striped  Time             Sys  Name

                                            N    PDB$SEED/

                                            N    crsdrlq2db/

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    sysaux.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/sysaux.20190613142557.dbf.258.1010845615

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    system.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/system.20190613142557.dbf.259.1010845605

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    undotbs1.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/undotbs1.20190613142557.dbf.261.1010845621

ASMCMD> cd +obq_grid1/_MGMTDB/DATAFILE/PDB$SEED/

ASMCMD> ls -l

Type      Redund  Striped  Time             Sys  Name

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    sysaux.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/sysaux.20190613142557.dbf.263.1010845627

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    system.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/system.20190613142557.dbf.262.1010845633

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    undotbs1.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/undotbs1.20190613142557.dbf.264.1010845625

ASMCMD> cd +obq_grid1/_MGMTDB/DATAFILE/crsdrlq2db

ASMCMD> ls -l

Type      Redund  Striped  Time             Sys  Name

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    sysaux.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/sysaux.20190613142557.dbf.268.1010845639

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    syscalogdata.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/syscalogdata.20190613142557.dbf.270.1010845653

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    sysgridhomedata.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/sysgridhomedata.20190613142557.dbf.269.1010845649

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    sysmgmtdata.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/sysmgmtdata.20190613142557.dbf.281.1010845665

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    sysmgmtdatachafix.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/sysmgmtdatachafix.20190613142557.dbf.279.1010845853

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    sysmgmtdatadb.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/sysmgmtdatadb.20190613142557.dbf.280.1010845687

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    sysmgmtdataq.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/sysmgmtdataq.20190613142557.dbf.278.1010845951

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    system.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/system.20190613142557.dbf.267.1010845645

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    undotbs1.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/undotbs1.20190613142557.dbf.265.1010845637

DATAFILE  MIRROR  COARSE   JUN 13 14:00:00  N    users.20190613142557.dbf => +OBQ_GRID1/ASM/DATAFILE/users.20190613142557.dbf.266.1010845649

Bom, nós podemos concluir que todos os arquivos do primeiro bloco de listagem estão também neste bloco.

Continuando, na listagem abaixo temos o spfile do ASM e o OCR:

+obq_grid1/crsdrlq2db/

+obq_grid1/crsdrlq2db/ASMPARAMETERFILE/

+obq_grid1/crsdrlq2db/ASMPARAMETERFILE/REGISTRY.253.1010754285

+obq_grid1/crsdrlq2db/OCRFILE/

+obq_grid1/crsdrlq2db/OCRFILE/REGISTRY.255.1010754291

Na listagem abaixo temos o alias do password file do ASM que aponta para o arquivo físico propriamente dito:

 +obq_grid1/orapwasm
 +obq_grid1/orapwasm_backup

Vamos verificar se realmente é alias?

ASMCMD> ls -l +obq_grid1/orapwasm

Type      Redund  Striped  Time             Sys  Name

PASSWORD  HIGH    COARSE   JUN 12 13:00:00  N    orapwasm => +OBQ_GRID1/ASM/PASSWORD/pwdasm.256.1010754289

Bom, neste post identificamos exatamente quais são os arquivos que estão dentro do DiskGroup ASM padrão criado na instalação do GI.

Voltaremos em breve com outro post sobre este assunto.

Um abraço!

Vinicius

Referências:

Blog Post

Sobre

Blog reconhecido pela:

Disclaimer

Busca

Archive

Blogroll Internacional

Blogroll Nacional

Links

Visitantes

Blog Post

DiskGroup GRID: Entendendo o seu conteúdo

Related posts

CLSRSC-180: An error occurred while executing the command ‘/bin/rpm -qf /sbin/init’ durante o postpatch

Oracle Clusterware – Arquitetura – Parte 1 – Daemons e Processos

Oracle Clusterware – Rotinas Administrativas – Parte 8 – Análise e Troubleshooting

Movendo o MGMTDB para outro DiskGroup

OGB Appreciation Day: CLSRSC-667: found multiple ASM password files under GRID_HOME/dbs

Oracle Clusterware – Rotinas Administrativas – Parte 1 – Start e Stop

Deixe um comentário Cancelar resposta