[root@otest]# /etc/init.d/oracleasm force-renamedisk CLONE1 CLONE1a
Renaming disk "CLONE1" to "CLONE1a": [ OK ]
[root@otest]# /etc/init.d/oracleasm force-renamedisk CLONE2 CLONE2a
Renaming disk "CLONE2" to "CLONE2a": [ OK ]
ASMCMD> mount CLONE
ASMCMD> lsdsk -G CLONE
select disk_number,name,label,path from v$asm_disk;SQL> SQL> SQL> SQL>
0 DATA CLONE1A ORCL:CLONE1A
1 LOGS CLONE2A ORCL:CLONE2A
One thing you might want to eliminate from your device/disk management is explicitly naming everything. Let Oracle handle it for you. when you get into extremely large databases, "where" things are located becomes a lot less important. I let Oracle name things and it really doesn't matter all that much - even using INTERVAL PARTITIONING where Oracle names the partitions. It knows where stuff is and sometimes trying to do stuff explicitly can screw up the optimizer causing severe performance problems.
What I understand is that I need to UNMOUNT the DISKGROUP and then MOUNT, right? It means its not possible ONLINE, all the datafiles in the Diskgroup will not be accessible during this rename time (unmount and mount)?