Skip to main content

Dropping Quorum Disks in Exadata


<<Back to Exadata Main Page

How to Drop Quorum Disks in Exadata

There are certain circumstances, you might need drop the quorum disk. Some of them are listed below.
• When recreating a guest domU
• To correct certain configuration
• If you have lost the disk
Todays post is on this topic only which describes how you can drop the quorum disk cleanly including the target, device and configuration.
So lets start without any further delay.
Step1> identify the quorum disk to be dropped
[oracle@DB01]$ crsctl query css votedisk
##  STATE    File Universal Id                File Name Disk group
--  -----    -----------------                --------- ---------
 1. ONLINE   7802c66d58744feebffdf3b9340dce55 (..../DATAC3_CD_02_hw_cell01) [DATAC3]
 2. ONLINE   1797ab2fdeca4fc7bf9488b44760a217 (..../DATAC3_CD_02_hw_cell02) [DATAC3]
 3. ONLINE   34796cba31534f7fbf0f024d248ada04 (..../DATAC3_CD_02_hw_cell03) [DATAC3]
 4. ONLINE   ff198b7b1ff74fbcbf8a7baedd669b22 (/dev/exadata_quorum/QD_DATAC3_DB02) [DATAC3]
 5. ONLINE   3990c6fc37f44f2bbff3e31c23785803 (/dev/exadata_quorum/QD_DATAC3_DB01) [DATAC3]
Located 5 voting disk(s).
In my case I have 2 quorum disk and I wanted to drop both of them. The operation can be performed online because I have 5 voting disks (3 Votedisk + 2 Quorumdisk) in my diskgroup with HIGH redundancy and therefore I can wear the loss of 2 disks at any point of time without impacting the availability of the cluster.
SQL> select a.GROUP_NUMBER, b.name group_name,a.name,a.failgroup_type from v$asm_disk a, v$asm_diskgroup b where a.group_number = b.group_number and a.group_number = 1;
GROUP_NUMBER    GROUP_NAME   DISK_NUMBER   NAME                                              FAILGROUP_TYPE
------------                      ----------                 -----------              ------------------------------                     ---------------------
           1                         DATAC3                19                       QD_DATAC3_DB02                      QUORUM
           1                         DATAC3                18                       QD_DATAC3_DB01                      QUORUM
Step2>Force drop the quorum disk
ALTER DISKGROUP dg_name DROP QUORUM DISK disk_name FORCE;
SQL> ALTER DISKGROUP DATAC3 DROP QUORUM DISK QD_DATAC3_DB01 FORCE;
Diskgroup altered
SQL> ALTER DISKGROUP DATAC3 DROP QUORUM DISK QD_DATAC3_DB02 FORCE;
Diskgroup altered
Step3>Wait for the rebalancing operation to be completed 
SQL>select * from  v$asm_operation
no rows selected
ImpNote: if you are not using force option to drop the disk from asm diskgroup you will find the status of the disk dopping. In this case you have to wait until the disk is dropped or use the force option
SQL> select MOUNT_STATUS, HEADER_STATUS, MODE_STATUS, STATE, REDUNDANCY, NAME, FAILGROUP from v$asm_disk where STATE='DROPPING';
MOUNT_STATUS   HEADER  MODE_STATU  STATE      REDUNDANCY    NAME             FAILGROUP
-------------- ------  ----------  ---------- ------------  ---------------- ---------------
CACHED         MEMBER  ONLINE      DROPPING   UNKNOWN       QD_DATAC3_DB01   DB01                                                          
Step4> list down the target , device and configuration and delete them
[root@DB01~]#/opt/oracle.SupportTools/quorumdiskmgr --list --configOwner: oracle
Group: dba
ifaces: exadata_ib0 exadata_ib1
[root@DB01~]#/opt/oracle.SupportTools/quorumdiskmgr --list --deviceDevice path: /dev/exadata_quorum/QD_DATAC3_DB02
Host name: DB02
ASM disk group name: DATAC3
Size: 128 MB
Device path: /dev/exadata_quorum/QD_DATAC3_DB01
Host name: DB01
ASM disk group name: DATAC3
Size: 128 MB
[root@DB01~]# /opt/oracle.SupportTools/quorumdiskmgr --list --targetName: iqn.2015-05.com.oracle:QD_DATAC3_DB01
Host name: DB01
ASM disk group name: DATAC3
Size: 128 MB
Visible to: 192.168.10.45,192.168.10.46,192.168.10.47,192.168.10.48
Discovered by: 192.168.10.45,192.168.10.46,192.168.10.47,192.168.10.48
[root@Db02~]# /opt/oracle.SupportTools/quorumdiskmgr --list --target
Name: iqn.2015-05.com.oracle:QD_DATAC3_DB02
Host name: DB02
ASM disk group name: DATAC3
Size: 128 MB
Visible to: 192.168.10.45,192.168.10.46,192.168.10.47,192.168.10.48
Discovered by: 192.168.10.45,192.168.10.46,192.168.10.47,192.168.10.48
As root user from all the nodes
Step5> delete the device
[root@DB01~]# /opt/oracle.SupportTools/quorumdiskmgr --delete --device --host-name DB01
[Success] Successfully deleted device /dev/exadata_quorum/QD_DATAC3_DB01.
[root@DB02~]# /opt/oracle.SupportTools/quorumdiskmgr --delete --device --host-name DB01
[Success] Successfully deleted device /dev/exadata_quorum/QD_DATAC3_DB01
[root@DB02]# /opt/oracle.SupportTools/quorumdiskmgr --delete --device --host-name DB02[Success] Successfully deleted device /dev/exadata_quorum/QD_DATAC3_DB02.
[root@DB01]# /opt/oracle.SupportTools/quorumdiskmgr --delete --device --host-name DB02[Success] Successfully deleted device /dev/exadata_quorum/QD_DATAC3_DB02

Step6> delete target
[root@DB01~]# /opt/oracle.SupportTools/quorumdiskmgr --delete --target
[Success] Successfully deleted target iqn.2015-05.com.oracle:QD_DATAC3_DB01.
[root@DB02]# /opt/oracle.SupportTools/quorumdiskmgr --delete --target
[Success] Successfully deleted target iqn.2015-05.com.oracle:QD_DATAC3_DB02.
Step7> delete Configuration
[root@DB01]# /opt/oracle.SupportTools/quorumdiskmgr --delete --config
'import site' failed; use -v for traceback
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
[Success] Successfully deleted quorum disk configurations
[root@DB02]#  /opt/oracle.SupportTools/quorumdiskmgr --delete --config
'import site' failed; use -v for traceback
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
[Success] Successfully deleted quorum disk configurations
Note: You can ignore the above warning.
Step8> verify the existence of device, target and configuration file on all nodes
[root@DB02]# ls -lrt /dev/exadata_quorum/QD_DATAC3_DB02
ls: cannot access /dev/exadata_quorum/QD_DATAC3_DB02: No such file or directory
[root@DB02]# ls -lrt /etc/udev/rules.d/99-exadata-asmdevices.rules
ls: cannot access /etc/udev/rules.d/99-exadata-asmdevices.rules: No such file or directory
Step8> verify the voting disk status
[oracle@DB01$ crsctl query css votedisk;
##  STATE    File Universal Id                File Name Disk group
--  -----    -----------------                --------- --------- 
1. ONLINE   674bb2f267934fd9bfd84eaef62774e5 (....../DATAC3_CD_00_hw_cell01) [DATAC3]
 2. ONLINE   ed2002bfe8644fb9bf3b857c66748262 (....../DATAC3_CD_00_hw_cell02) [DATAC3]
 3. ONLINE   7802c66d58744feebffdf3b9340dce55 (....../DATAC3_CD_02_hw_cell01) [DATAC3]
 4. ONLINE   1797ab2fdeca4fc7bf9488b44760a217 (....../DATAC3_CD_02_hw_cell02) [DATAC3]
 5. ONLINE   34796cba31534f7fbf0f024d248ada04 (....../DATAC3_CD_02_hw_cell03) [DATAC3]
Located 5 voting disk(s).

NOTE: As you can see I still have a 5 Voting disks. Exadata automatically added 2 temporary disks to the diskgroup to keep 5 Voting disks in case of HIGH redundancy. Isn't it cool. At this moment I don't have much knowledge about this. It is just happened in my case. Please feel free to provide addition detail or explanation



Comments

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the serve...
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco...
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry...
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02          ...
7 comments
Read more

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected  SQL> alter session set container=PDB02; Session alt...
Post a Comment
Read more