Online DBA

  <<Back to Oracle RAC Main Page How to recreate GIMR diskgroup oracle RAC CREATE DISKGROUP GIMR NORMAL REDUNDANCY SITE S1 FAILGROUP GIMR_S1 DISK 'AFD:DISK1' SITE S2 FAILGROUP GIMR_S2 DISK 'AFD:DISK2' ATTRIBUTE 'compatible.asm'='12.1.0.0' , 'compatible.rdbms'='12.1.0.0'; CREATE DISKGROUP GIMR * ERROR at line 1: ORA-15018: diskgroup cannot be created ORA-15030: diskgroup name "GIMR" is in use by another diskgroup Reason:  I dropped the disk group GIMR using sqlplus and tried to create it again with the same name ended with above error message  Solution Though the diskgroup does not exists I dropped it again using asmcmd . Created the diskgroup again it worked  ASMCMD>  dropdg -r -f GIMR;

  <<Back to Oracle RAC Main Page How to re-create oracle RAC -MGMTDB database  Verify Status of -MGMTDB  prompt@node1:~/ [+ASM1]  srvctl status mgmtdb Database is enabled Instance -MGMTDB is running on node node1 prompt@node1:~/ [+ASM1] export ORACLE_SID=-MGMTDB prompt@node1:~/ [-MGMTDB] sqlplus "/as sysdba" Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.16.0.0.0 SQL> show pdbs     CON_ID CON_NAME                       OPEN MODE  RESTRICTED ---------- ------------------------------ ---------- ----------          2 PDB$SEED                       READ ONLY  NO          3 MGMT_PDB_01                 READ WRITE NO SQL> select comp_id,status from dba_registry; COMP_ID  ...

  <<Back to Oracle ASM Main Page ASMCMD-9521: AFD is already configured while labeling the disk #export ORACLE_HOME=/u01/app/product/19c/grid #export ORACLE_BASE=/u01/app # $ORACLE_HOME/bin/asmcmd afd_label FRA_01_RAC_001  /dev/dm-10 --init   ASMCMD-9521: AFD is already configured After checking the disk status I found the disk is available to lable #$ORACLE_HOME/bin/asmcmd afd_lslbl /dev/dm-10 No devices to be scanned. The Permission is also fine # ls -lrt /dev/dm-10  lrwxrwxrwx 1 root root 8 Sep 28 10:19 /dev/dm-10  Lets read the header of this disk # $ORACLE_HOME/bin/kfed read /dev/dm-10  kfbh.endian:                          0 ; 0x000: 0x00 kfbh.hard:                            0 ; 0x001: 0x00 kfbh.type:                            0 ; 0x002: KFBT...

<<Back to Oracle ASM Main Page  Uses of  DISK_REPAIR_TIME and FAILGROUP_REPAIR_TIME Attribute DISK_REPAIR_TIME: DISK_REPAIR_TIME is an attribute for diskgroup and the default value is 3.6Hrs. If ASM unable to perform IO on any disk in the diskgroup it place taht disk offline and wait for time specified in DISK_REPAIR_TIME for the disks be back online. If the disk did not back online with in this time period Oracle ASM then drops that disk from the diskgroup.  SQL> select name,value from v$asm_attribute where group_number=1 and name like '%disk_repair_time%'; NAME                                     VALUE ---------------------------------------- -------------------------------------------------- disk_repair_time            ...

<<Back to Oracle ASM Main Page    Adding Dropped Disks Back into Diskgroup The steps documented in this post is helpful if you have dropped disks which is still hanging and ASM.repair_time parameter is already over.  Further select * from v$asm_operations shows error. Although the disk is still showing dropping but if you try to bring it online it fails. If you try to force drop it, it fails. Step 1: Identify the missing/dropped disk for a particular disk group select GROUP_NUMBER,NAME from  v$asm_diskgroup; select name,header_status,mount_status,path from v$asm_disk where GROUP_NUMBER=2; Step2: Find ASM disk level for each dropped disks A> Scan ASM log file for this info B> Check output of MD_BACKUP before the issue In my case it was FRA_01 Diskgroup where one of storage site went down causing the issue. After scanning ASM alertlog  I found the following ASM disks which were part of the ASM Disk group but Currently these are the disks which is appea...

<<Back to Oracle ASM Main Page Changing Failgroup Of an ASM Disk In many situations its required to alter the failgroup of a disk in an ASM diskgroup, for example while adding the disk you did typo while typing the failgroup name and you realized only after the disk is added to wrong failgroup. There is no other way but only drop and add the disk to right failgroup. Steps are here Step1: Identify the disks in wrong failgroup. set line 200 col name format a20 col path format a40 select path,failgroup,mount_status,mode_status,header_status,state from v$asm_disk where GROUP_NUMBER=1 order by failgroup, path; Step2: Drop the disks (identified disks) in wrong failgroup ALTER DISKGROUP DATA DROP DISK  DC1_DISK11 REBALANCE POWER 20; Step3: Wait for Rebalance Operation to complete select GROUP_NUMBER,OPERATION,STATE,EST_WORK,EST_MINUTES from gv$asm_operation; Step4: Add the disk in correct failgroup ALTER DISKGROUP DATA ADD FAILGROUP DC01 DISK 'ORCL:DC01_DISK11' NAME DC01_DISK11 ...

<<Back to Oracle ASM Main Page SQL> ALTER PLUGGABLE DATABASE DROP MIRROR COPY PDB01_CLONE; ALTER PLUGGABLE DATABASE DROP MIRROR COPY PDB01_CLONE * ERROR at line 1: ORA-59024: dropping mirror copy 'PDB01_CLONE' in disk group 'DATA' failed as the file split is complete Cause Cloning process is completed Solution: No action required because you don't have to delete the mirror copy once you have completed the cloning  

<<Back to Oracle ASM Main Page Pluggable Database Cloning With Oracle ASM Flex Disk Group The feature is introduced with oracle 18c and following are prerequisites to use this feature  Point-in-time database clones are supported only in Oracle ASM flex and extended disk groups.  Point-in-time database clones are supported only with Oracle Database 18c, version 18.1 or higher.  Point-in-time database clones require disk group compatibility attributes COMPATIBLE.ASM and COMPATIBLE.RDBMS be set to 18.0 or higher.  The source database (parent) must be a pluggable database. The database clone (child) created is a pluggable database under the same container database. The Cloning is performed in 2 Steps. Preparing the Mirrored Copy Splitting the Mirrored Copy and Creating the Database Clone. Note: After preparing the   Mirrored Copy if you don't want to proceed for cloning you can drop the  Mirrored Copy. The drop action discards ...

<<Back to Oracle ASM Main Page Point-In-Time Database Cloning With Oracle ASM Flex Disk Groups  throwing ORA-15385: file group xxx  does not exist While testing the new 18c ASM feature I encountered this error. SQL> alter session set container=PDB01; Session altered. SQL> ALTER PLUGGABLE DATABASE PREPARE MIRROR COPY PDB01_CLONE; ALTER PLUGGABLE DATABASE PREPARE MIRROR COPY PDB01_CLONE * ERROR at line 1: ORA-15385: file group 'TST1T_PDB01' does not exist Cause Since the above feature requires the FLEX Diskgroup I converted my Normal Redundancy Diskgroup to FLEX Diskgroup and executed the PREPARE. The  PREPARE started throwing the error. ORA-15385: file group 'TST1T_PDB01' does not exist Solution : Restarting the database fixed the issue SQL> startup force; ORACLE instance started. Total System Global Area 2147482464 bytes Fixed Size                  8899...

<<Back to Oracle ASM Main Page oracleasm module not loaded or /dev/oracleasm not mounted # oracleasm createdisk  DATA1 /dev/xvdc11 oracleasm module not loaded or /dev/oracleasm not mounted. # oracleasm status Checking if ASM is loaded: no Checking if /dev/oracleasm is mounted: no Load the oracleasm module # oracleasm init Creating /dev/oracleasm mount point: /dev/oracleasm Loading module "oracleasm": oracleasm Configuring "oracleasm" to use device physical block size Mounting ASMlib driver filesystem: /dev/oracleasm Verify the oracleasm configuration # df -ha |grep -i oracleasm oracleasmfs                     0     0     0    - /dev/oracleasm # lsmod | grep oracleasm oracleasm              61440  1 Initialize the disks using oracleasm...

<<Back to Oracle ASM Main Page Installing and Configuring ASM in Silent Mode Using ASMLib Provisioned Disks # oracleasm listdisks DISK01 DISK02 # ls -lrt /dev/oracleasm/disks/ total 0 brw-rw---- 1 oracle oinstall 202, 39 Jan 21 13:25 DISK01 brw-rw---- 1 oracle oinstall 202, 40 Jan 21 13:26 DISK02 # sudo su - oracle cd $ORACLE_HOME/bin $ ./asmca -silent -configureASM -diskString '/dev/oracleasm/disks/*' -sysAsmPassword ***** -asmsnmpPassword ******  -diskGroupName DG_TEST_DATA -diskList '/dev/oracleasm/disks/DISK01' -redundancy EXTERNAL Disk groups created successfully. Check /u01/grid/cfgtoollogs/asmca/asmca-190123AM104712.log for details. Related Posts: Installing Grid Infrastructure for a Standalone Server in Silent Mode Step by Step How to Install and Configure Oracle asmlib

<<Back to Oracle ASM Main Page [FATAL] [INS-30508] Invalid ASM disks.    CAUSE: The disks [/dev/xvdc8] were not valid.    ACTION: Please choose or enter valid ASM disks. Solution: Solution of  this problem is to provide valid ASM disks. You can provide ASM instance a valid ASM disks in following ways. Solution1: Configure udev rules for raw devices and use them for ASM disk #cd /etc/udev/rules.d #vi 60-raw.rules and add entry like this in 60-raw.rules. Make one entry for each disk ACTION=="add", KERNEL=="xvdc9", RUN+="/bin/raw /dev/raw/raw9 %N" ACTION=="add", KERNEL=="raw*", OWNER=="oracle", GROUP=="oinstall",MODE=="0660" save and exit Start Udev Service # start_udev Starting udev:                                             [  OK  ] # udevadm control --reload-rules # ls -ltr /dev/raw/raw9 crw-rw-...

<<Back to Oracle ASM Main Page How to Install and Configure oracleasmlib To use oracleasmlib to prepare disks for ASM you need to download and install these 2 packages. oracleasmlib-2.0.12-1.el7.x86_64.rpm oracleasm-support-2.1.8-3.el7.x86_64.rpm you can download them here Installing Oracle ASMLIB and Oracle ASM-SUPPORT use rpm command to install the packages. #rpm -ivh oracleasmlib-2.0.12-1.el7.x86_64.rpm  #rpm -ivh oracleasm-support-2.1.8-3.el7.x86_64.rpm Configure Oracle ASMLIB Once you are done with the package Installation you can configure asm libraries using below command #/etc/init.d/oracleasm configure How to Create ASM disk Using ASMLIB Utility #oracleasm createdisk disk1 /dev/sdb5 How to find the Disks created using ASM Lib #oracleasm listdisks #ls -lrt /dev/oracleasm/disk* How to discover or scan ASM disks #oracleasm scandisks Verify the Permission of ASM Disks # ls -lrt /dev/oracleasm/disks/ ...

<<Back to Oracle ASM Main Page ORA-15040: diskgroup is incomplete SQL> startup ORA-00099: warning: no parameter file specified for ASM instance ASM instance started Total System Global Area 1140850688 bytes Fixed Size                  8629704 bytes Variable Size            1107055160 bytes ASM Cache                  25165824 bytes ORA-15110: no diskgroups mounted Reason: The reason of this error is simply the ASM is not able to find the some or all the disks. Solution: Investigate and make all the disks available to ASM to mount the disk group. Make sure the disks has proper permissions. If you are using AFD check following services are online oracleacfs oracleadvm oracleoks  oracleafd   Source of Problem : Issue started af...