11gR2 ASM Inside story Partie 6 (Recréer le service de haute disponibilité et renommer un groupe de disque)

Transcription

1 11gR2 ASM Inside story Partie 6 (Recréer le service de haute disponibilité et renommer un groupe de disque)

2 Introduction: Dans l'article précédent de l'histoire de ASM, nous avons vu comment lire un fichier ASM depuis le système opératif. Dans cet article, nous allons voir comment recréer le service de haute disponibilité, comment register les ressources et enfin, comment renommer un groupe de disques ASM. Cette procédure est appliquée à une bases de données 11gR2, sous Oracle Enterprise Linux. 1- Recréer le service de haute disponibilité : Problème et besoin: Après le redémarrage du serveur de bases de données, les ressources de haute disponibilité ne se redémarrent pas automatiquement. Il faut se rappeler que à partir de la version 11gR2, Oracle Restart est responsable de redémarrage automatiques des ressources; ASM, instances de bases de données, listeners, etc... Voici l'erreur que j'ai reçu; [oracle@localhost.oracle]$ srvctl status asm PRCR-1070 : Failed to check if resource ora.asm is registered Cannot communicate with crsd [oracle@localhost.oracle]$ Maintenant, nous allons essayer de redémarrer les services de haute disponibilité manuellement; [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 Solution et démarche à suivre: Pour résoudre le problème, j'aurais du modifier le contenu du fichier /etc/hosts. Maintenant, j'ai supprimé le service de haute disponibilité, en utilisant l'option -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 Maintenant, nous démarrons le service de haute disponibilité; [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

4 Creating OCR keys for user 'oracle', privgrp 'oinstall'.. Operation successful. CRS-4664: Node 192 successfully pinned. 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]# Vérifions, l'état des ressources; [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]# Ajoutons ASM comme une ressource au service haute disponibilité su - oracle srvctl status asm PRCR-1001 : Resource ora.asm does not exist srvctl add asm srvctl status asm ASM is not running.

5 srvctl start asm srvctl status asm 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> Vérifions, l'état de l'instance de bases de données et ses ressources; 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

6 srvctl add database -d ORAW -o $ORACLE_HOME srvctl status database -d ORAW Database is not running. Ok, maintenant, nous devons démarrer l'instance de bases de données. 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 Analyzons l'erreur, il faut monter le groupe de disques, 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

7 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 ' SQL> Aussi, montons le groupe de disques, 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> Maintenant, nous avons la base de données démarrée, aussi bien que la infrastructure

8 2- Renommer le groupe de disques ASM: Après avoir migré ma base de données en RAC à une base de données d'instance unique; J'ai noté qu'il y' a un groupe de disques nommé DATA_RAC. Ce nom de groupe de disques n'a plus de sens maintenant dans un environnement d'instance unique. Donc, je vais le renommer en DATA_REPORTING; 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 On va vérifier les noms de groupes de disques; 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 DATA_RAC DATA SQL>

9 On va démonter le groupe de disques, DATA_RAC; asmcmd umount DATA_RAC Le groupe de disque est bien démonté; asmcmd lsdg State Type Rebal Hector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name MOUNTED NORMAL N N DATA/ Changeons le nom de groupe de disques; 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 Discovering the group 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 ( )

10 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 On doit monter maintenant le groupe de diques; asmcmd mount DATA_REPORTING vérifions que le groupe renommé est bien monté; 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/ Démarrons l'instance de bases de données;

11 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 ' Il faudrait renommer les fichiers de données; 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> Miantenant, nous avons des groups de disques avec des noms plus cohérents et logique.