Online DBA

Posts

Showing posts with the label ASM Troubleshooting

How to Recover Diskgroup in Case of Transient Failures

<<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 ...

ORA-15106: missing or invalid operating system disk locator string

<<Back to Oracle ASM Main Page ORA-15106: missing or invalid operating system disk locator string +ASM2> alter diskgroup DATA add failgroup DATA_1 disk '/dev/mapper/oradata_s2_45', '/dev/mapper/oradata_s2_47', failgroup DATA_2 disk '/dev/mapper/oradata_s2_46', '/dev/mapper/oradata_s2_48' rebalance power 3; ERROR at line 3: ORA-15106: missing or invalid operating system disk locator string Cause: The command did not specify a valid operating system path for the device as a string. Troubleshooting TIPPS 1> Check if all the disks got correct permissions at OS level eg, ls -lrt /dev/mapper/oradata_s2_45 2> Verify the asm_diskstring parameter is set to discover the newly added disks SQL> show parameter string NAME TYPE VALUE asm_diskstring ...

ORA-59024: dropping mirror copy in disk group 'DATA' failed as the file split is complete

<<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

Point-In-Time Pluggable Database Cloning With Oracle ASM Flex Disk Groups

<<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 ...

ORA-15385: file group XXXX does not exist While Cloning PDB oracle 18c

<<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...

How to load oracleasm module

<<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...

INS-30508 Invalid ASM disks

<<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-...

ORA-15040: diskgroup is incomplete

<<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...

AFD managed devices does not match

<<Back to Oracle ASM Main Page ASMCMD-9512: failed to update AFD disk string in Oracle Local Repository. $ asmcmd afd_dsset '/dev/xvdd*' AFD managed disk '/dev/xvdc1' is not part of '/dev/xvdd*' AFD managed devices does not match '/dev/xvdd*' ASMCMD-9512: failed to update AFD disk string in Oracle Local Repository. Cause Trying to overwrite ASM_DISKSTRING parameter with the value which does not discovers ASM known disks on OS Solution Modify the command to include all ASM known disk strings. Find out the current ASM_DISKSTRING parameter value and include it in your command while overwriting the ASM_DISKSTRING value using afd_dsset command $ asmcmd afd_dsget AFD discovery string: /dev/xvc $ asmcmd afd_dsset '/dev/xvc*','/dev/xvdd*' $asmcmd afd_dsget AFD discovery string: /dev/xvc,/dev/xvdd*

ORA-15493: target ADVM compatibility xxxx exceeds ASM compatibility xxxx

<<Back to Oracle ASM Main Page ORA-15493: target ADVM compatibility (12.1.0.0.0) exceeds ASM compatibility (11.2.0.2.0) SQL> alter diskgroup DG_TEST set attribute 'compatible.advm'='12.1'; alter diskgroup DG_TEST set attribute 'compatible.advm'='12.1' * ERROR at line 1: ORA-15032: not all alterations performed ORA-15242: could not set attribute compatible.advm ORA-15493: target ADVM compatibility (12.1.0.0.0) exceeds ASM compatibility (11.2.0.2.0) Solution : Increase the compatible.asm minimum to a value you want compatible.advm to be. SQL> select NAME,VALUE from v$asm_attribute where name like '%com%' and GROUP_NUMBER=5; NAME VALUE ---------------------------------------- ---------------------------------------- compatible.asm ...

PRKO-2012 : filesystem object is not supported in Oracle Restart