Hello All.  Our Database Team along with Storage Team does Databases Migration from old storage to new storage. In general , when new disks from new storage are presented, mapping of new disks and creation of hdisk and mknod is done. Then they execute Disk group balancing in the ASM during times of lower transactional load.

Data is migrated successfully. However, after the migration we can't reclaim the old storage disks, as although old disks are no longer belong to the ASM, but at the time of removing them from the lpar (server) it is not possible because some services are still running on these disks. This situation has happened to us in many activities of this type and the only solution is to execute a controlled restart of both nodes so that these tied disks are released.  

Please advise, how others are managing this part of the ASM Balancing Migration.   Thanks in advance.    Best.

What processes do you see when you run fuser /dev/<raw_device_name> ?

If they are Oracle processes, that means that the DB has not yet completely released them.

Sudhir,

did you lock the device? Try to unlock it before removing it:

lkdev -l hdiskX -d