ASM TRICKS

Trick 1 Clean Up a Failed Grid Infrastructure Installation

How to clean up a failed Grid Infrastructure installation. It specifically focuses on what to do if the "root.sh" script fails during this process and you want to rewind and start again.

Grid Infrastructure

On all cluster nodes except the last, run the following command as the "root" user.

# perl $GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force

On the last cluster node, run the following command as the "root" user.

# perl $GRID_HOME/crs/install/rootcrs.pl -verbose -deconfig -force -lastnode

This final command will blank the OCR configuration and voting disk.
You should be in a position to rerun the "root.sh" file now, but if you are using ASM, you will need to prepare your ASM disks before doing so.

[INS-30043] The grid infrastructure home does not exist or is empty

I have gotten this error while attempting to re-install Oracle on the UNIX server.

The old version of Oracle was not de-installed properly, and so when new version was being installed, I got an error "[INS-30043] The grid infrastructure home '/u10/app/oracle/product/11.2.0/grid' does not exist or is empty".sion i was installing was 11.2.0.3 and the folder 11.2.0 didn't even exist.

The resolution was quite simple though - manually editing inventory.xml file. It can be found in $ORACLE_BASE/oraInventory/ContentsXML directory. I had to remove the entries pointing to the deleted folders and my issue was resolved.

inventory.xml file lists all the Oracle products installed on the machine and when directories are deleted manually, the entries are not removed from inventory.xml file. That's why it is a good idea to perform a deinstallation when removing any Oracle products from the server as opposed to just manually removing directores (applies to 11.2.0 and higher)

 ASM Disks (geldt voor Asmlib)

Once you attempt an installation, your ASM disks are marked as being used, so they can no longer be used as candidate disks. To revert them to candidate disk do the following.
Overwrite the header for the relevant partitions using the "dd" command.

# dd if=/dev/zero of=/dev/sdb1 bs=1024 count=100

Remove and create the ASM disk for each partition.

# /etc/init.d/oracleasm deletedisk DATA /dev/sdb1

# /etc/init.d/oracleasm createdisk DATA /dev/sdb1

The disks will now be available as candidate disks.
For more information see:

Trick 2. Hoe vind je mapping ASM disks to Physical Devices?

1.Login as root

# /etc/init.d/oracleasm listdisks
ASM1

2. Query Disk
[root@localhost dev]# oracleasm querydisk -d ASM1
Disk "ASM1" is a valid ASM disk on device /dev/sdc1[8,33]

oftewel sdc1

>>>PS. Dit werkt alleen als je met ASMlib werkt. Met Udev moet je andere stappen volgen

Trick 3: waar staat configuratiefile ASM

/etc/sysconfig/oracleasm

Trick 4: Hoe vind je mapping Asm disks to physical devices with UDEV

Op RHEL werkt de asmlib niet, dan via udev werken.

- kijk welke schijven er zijn met:
fdisk -l           (toont ook meteen de grootte van dschijven)

-haal van iedere schijf de scsi-id op:

sudo /sbin/scsi_id -g -u -d /dev/sdc

-Kijk adhv dit scsi-id in de file  /etc/udev/rules.d/99-oracle-asmdevices.rules:

  
KERNEL=="sd?1", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -d /dev/$parent", RESULT=="SATA_VBOX_HARDDISK_VBd306dbe0-df3367e3_", NAME="asm-disk1", OWNER="oracle", GROUP="dba", MODE="0660"

KERNEL=="sd?1", BUS=="scsi", PROGRAM=="/sbin/scsi_id -g -u -d /dev/$parent", RESULT=="SATA_VBOX_HARDDISK_VB46dec7e0-192e8000_", NAME="asm-disk2", OWNER="oracle", GROUP="dba", MODE="0660"

  
the ASM_DISKSTRING initialization parameter in the ASM instance can be set to '/dev/asm-disk*' to identify the ASM disks


Trick 5: Hoeveel ruimte heb ik nog op ASM schijf

optie1:  via commandline asmcmd lsdg       (zet wel ORACLE_SID en HOME)

optie 2: via sqlplus

SELECT name, free_mb, total_mb, free_mb/total_mb*100 as percentage 
     FROM v$asm_diskgroup