11gR2 ASM Inside story Parte 6 (Crear de nuevo el servicio de alta disponibilidad y renombrar un grupo de discos)

Transcripción

1 11gR2 ASM Inside story Parte 6 (Crear de nuevo el servicio de alta disponibilidad y renombrar un grupo de discos)

2 Introducción: En el pasado articulo, hemos visto como leer un fichero de ASM a partir del sistema operativo. En este articulo, vamos a ver como recrear el servicio de alta disponibilidad, registrar los recursos y al final del articulo, cambiaremos el nombre de un grupo de discos. Este procedimiento se aplica a una base de datos 11gR2 bajo Oracle Enterprise Linux. 1- Recrear el servicio de alta disponibilidad: Problema: Después de reiniciar el servidor, los recursos de HA no arrancaban automáticamente. A partir de la versión 11gR2 es el servicio de Oracle restart que es el responsable del arranque automático de los recursos; como la base de datos, las instancias de ASM, etc.. Al comprobar los recursos, hemos recibido el siguiente error; [oracle@localhost.oracle]$ srvctl status asm PRCR-1070 : Failed to check if resource ora.asm is registered Cannot communicate with crsd [oracle@localhost.oracle]$ Ahora, intentamos arrancar el servicio de alta disponibilidad; [root@localhost bin]#./crsctl start has Failure at scls_scr_getval with code 1 Internal Error Information: Category: -2 Operation: opendir Location: scrsearch1 Other: cant open scr home dir scls_scr_getval System Dependent Information: 2 CRS-4000: Command Start failed, or completed with errors.

3 Solución: Para resolver el problema, he corregido el contenido del fichero /etc/hosts como estaba antes de reiniciar la maquina. Ahora, borro el servicio de alta disponibilidad, usando la opción -force; bin]# /u01/app/oracle/product/11.2.0/grid/perl/bin/perl -I /u01/app/oracle/product/11.2.0/grid/perl/lib -I /u01/app/oracle/product/11.2.0/grid/crs/install /u01/app/oracle/product/11.2.0/grid/crs/install/roothas.pl -delete -force :04:54: Checking for super user privileges :04:54: User has super user privileges :04:54: Parsing the host name Using configuration parameter file: /u01/app/oracle/product/11.2.0/grid/crs/install/crsconfig_params CRS-4639: Could not contact Oracle High Availability Services CRS-4000: Command Stop failed, or completed with errors. CRS-4639: Could not contact Oracle High Availability Services CRS-4000: Command Delete failed, or completed with errors. Failure at scls_scr_getval with code 1 Internal Error Information: Category: -2 Operation: opendir Location: scrsearch1 Other: cant open scr home dir scls_scr_getval System Dependent Information: 2 CRS-4544: Unable to connect to OHAS CRS-4000: Command Stop failed, or completed with errors. ACFS-9200: Supported Successfully deconfigured Oracle Restart stack Ahora, reconsideramos el servicio de alta disponibilidad de nuevo; [root@localhost bin]# /u01/app/oracle/product/11.2.0/grid/perl/bin/perl -I /u01/app/oracle/product/11.2.0/grid/perl/lib -I /u01/app/oracle/product/11.2.0/grid/crs/install /u01/app/oracle/product/11.2.0/grid/crs/install/roothas.pl :06:13: Checking for super user privileges :06:13: User has super user privileges :06:13: Parsing the host name Using configuration parameter file: /u01/app/oracle/product/11.2.0/grid/crs/install/crsconfig_params LOCAL ADD MODE Creating OCR keys for user 'oracle', privgrp 'oinstall'.. Operation successful. CRS-4664: Node 192 successfully pinned.

4 Adding daemon to inittab CRS-4123: Oracle High Availability Services has been started. ohasd is starting /07/30 14:07:28 /u01/app/oracle/product/11.2.0/grid/cdata/192/backup_ _ olr Successfully configured Oracle Grid Infrastructure for a Standalone Server [root@localhost bin]# Verificamos el estado de los recursos; [root@localhost bin]#./crsctl status res NAME=ora.cssd TYPE=ora.cssd.type TARGET=OFFLINE STATE=OFFLINE NAME=ora.diskmon TYPE=ora.diskmon.type TARGET=OFFLINE STATE=OFFLINE [root@localhost bin]# Añadimos, ASM como un recurso al servicio de alta disponibilidad; su - oracle srvctl status asm PRCR-1001 : Resource ora.asm does not exist srvctl add asm srvctl status asm ASM is not running. srvctl start asm srvctl status asm

5 ASM is running on 192 ps -edf grep ASM oracle :12? 00:00:00 asm_pmon_+asm oracle :12? 00:00:00 asm_vktm_+asm oracle :12? 00:00:00 asm_gen0_+asm oracle :12? 00:00:00 asm_diag_+asm oracle :12? 00:00:00 asm_psp0_+asm oracle :12? 00:00:00 asm_dia0_+asm oracle :12? 00:00:00 asm_mman_+asm oracle :12? 00:00:00 asm_dbw0_+asm oracle :12? 00:00:00 asm_lgwr_+asm oracle :12? 00:00:00 asm_ckpt_+asm oracle :12? 00:00:00 asm_smon_+asm oracle :12? 00:00:00 asm_rbal_+asm oracle :12? 00:00:00 asm_gmon_+asm oracle :12? 00:00:00 asm_mmon_+asm oracle :12? 00:00:00 asm_mmnl_+asm oracle :12 pts/1 00:00:00 grep ASM export ORACLE_HOME=$GRID_HOME export ORACLE_SID=+ASM sqlplus / as sysasm SQL*Plus: Release Production on Sat Jul 30 14:20: Connected to: Oracle Database 11g Enterprise Edition Release Production With the Automatic Storage Management option SQL> verificamos, el estado de la instancia de bases de datos y su recurso; srvctl status database -d ORAW PRCD-1120 : The resource for database ORAW could not be found. PRCR-1001 : Resource ora.oraw.db does not exist srvctl add database -d ORAW -o $ORACLE_HOME srvctl status database -d ORAW

6 Database is not running. Vale, ahora, tenemos que arrancar la instancia de bases de datos. sqlplus / as sysdba SQL*Plus: Release Production on Sat Jul 30 14:19: Connected to an idle instance. SQL> startup ORA-01078: failure in processing system parameters ORA-01565: error in identifying file '+DATA/ORAW/spfileORAW.ora' ORA-17503: ksfdopn:2 Failed to open file +DATA/ORAW/spfileORAW.ora ORA-15056: additional error message ORA-17503: ksfdopn:dgopenfile05 Failed to open file +DATA/oraw/spfileoraw.ora ORA-17503: ksfdopn:2 Failed to open file +DATA/oraw/spfileoraw.ora ORA-15001: diskgroup "DATA" does not exist or is not mounted ORA-06512: at line 4 SQL> exit Disconnected El error es explicito; tenemos que montar el grupo de discos DATA. asmcmd mount DATA source /home/oracle/.bash_profile sqlplus / as sysdba SQL*Plus: Release Production on Sat Jul 30 14:23: Connected to an idle instance. SQL> startup ORACLE instance started.

7 Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. ORA-01157: cannot identify/lock data file 5 - see DBWR trace file ORA-01110: data file 5: '+DATA_RAC/oraw/datafile/data_rac_read ' SQL> El error es también explicito; tenemos que montar el grupo de discos DATA_RAC. export ORACLE_HOME=$GRID_HOME export ORACLE_SID=+ASM asmcmd mount DATA_RAC source /home/oracle/.bash_profile sqlplus / as sysdba SQL*Plus: Release Production on Sat Jul 30 14:25: Connected to: Oracle Database 11g Enterprise Edition Release Production With the Partitioning, Automatic Storage Management, OLAP, Data Mining and Real Application Testing options SQL> alter database open; Database altered. SQL> Ahora, que tenemos la base de datos arrancada, tenemos también la infraestructura arrancada.

8 2- Renombrar un grupo de discos ASM: Después de migrar mi RAC a una base de datos de simple instancia, he notado que había un grupo de discos que portaba el nombre de DATA_RAC. Ahora, quiero renombrar este grupo de discos, para tener mas sentido. Voy a renombrar lo a DATA_REPRTING. El seguinete procedimiento puede también ser aplicado a unas instancias de RAC. En aquel caso, se puede aplicar las etapas en todos los nodos del cluster. El primer etapa, incluye parar la instancia de bases de datos SQL> shutdown immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> exit Disconnected from Oracle Database 11g Enterprise Edition Release Production With the Partitioning, Automatic Storage Management, OLAP, Data Mining and Real Application Testing options Ahora, listamos los diferentes nombres de grupos de discos; export ORACLE_HOME=$GRID_HOME export ORACLE_SID=+ASM sqlplus / as sysasm SQL*Plus: Release Production on Sat Jul 30 14:29: Connected to: Oracle Database 11g Enterprise Edition Release Production With the Automatic Storage Management option SQL> SELECT NAME FROM V$ASM_DISKGROUP; NAME INDX

9 DATA_RAC DATA SQL> Desmontamos el grupo de discos, DATA_RAC; asmcmd umount DATA_RAC Verificamos que el grupo de discos esta realmente dismontado; asmcmd lsdg State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name MOUNTED NORMAL N N DATA/ Cambiamos el nombre del grupo de discos; renamedg phase=both dgname=data_rac newdgname=data_reporting verbose=true NOTE: No asm libraries found in the system Parsing parameters.. Parameters in effect: Old DG name : DATA_RAC New DG name : DATA_REPORTING Phases : Phase 1 Phase 2 Discovery str : (null) Clean : TRUE Raw only : TRUE renamedg operation: phase=both dgname=data_rac newdgname=data_reporting verbose=true Executing phase 1

10 Discovering the grupo Performing discovery with string: Identified disk UFS:/dev/raw/raw5 with disk number:0 and timestamp ( ) Identified disk UFS:/dev/raw/raw6 with disk number:1 and timestamp ( ) Checking for hearbeat... Re-discovering the grupo Performing discovery with string: Identified disk UFS:/dev/raw/raw5 with disk number:0 and timestamp ( ) Identified disk UFS:/dev/raw/raw6 with disk number:1 and timestamp ( ) Checking if the diskgroup is mounted Checking disk number:0 Checking disk number:1 Checking if diskgroup is used by CSS Generating configuration file.. Completed phase 1 Executing phase 2 Looking for /dev/raw/raw5 Modifying the header Looking for /dev/raw/raw6 Modifying the header Completed phase 2 Terminating kgfd context 0xb7e70050 Montamos el grupo de discos recien renombrado; asmcmd mount DATA_REPORTING Verificar que el grupo de discos esta realmente montado; asmcmd lsdg State Type Rebal Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name MOUNTED NORMAL N N DATA/ MOUNTED NORMAL N N DATA_REPORTING/

11 Ahora, deberemos arrancar la instancia de bases de datos; source /home/oracle/.bash_profile sqlplus / as sysdba SQL*Plus: Release Production on Sat Jul 30 14:34: Connected to an idle instance. SQL> startup ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. ORA-01157: cannot identify/lock data file 5 - see DBWR trace file ORA-01110: data file 5: '+DATA_RAC/oraw/datafile/data_rac_read ' Es la hora de renombrar los ficheros de bases de datos; SQL> alter database rename file '+DATA_RAC/oraw/datafile/data_rac_read ' 2 to 3 '+DATA_REPORTING/oraw/datafile/data_rac_read '; Database altered. SQL> alter database open; Database altered. SQL> Ahora tenemos nuestra bases de datos lista para ser usada, con unos nombres de grupos de discos mas significativos;