tag:blogger.com,1999:blog-549043503714582179.post8761396379883407851..comments2024-03-13T16:27:52.280+11:00Comments on ASM Support Guy: ASM Disk DirectoryBane Radulovichttp://www.blogger.com/profile/07892013690973803072noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-549043503714582179.post-11432205602531349262013-02-05T10:33:28.584+11:002013-02-05T10:33:28.584+11:00There is no supported way to change the disk name ...There is no supported way to change the disk name inside the disk directory. It _may_ be possible to edit the relevant blocks directly with kfed, but before even considering this, it is required to understand what exactly the problem is and how you got the disk directory in in this state.<br /><br />If you can provide more details I would be happy to have a look. It may be best to email me directly to bane.radulovic at gmail.com and once we sort it out, we can post the solution here.<br /><br />Cheers,<br />Bane<br /><br />Bane Radulovichttps://www.blogger.com/profile/07892013690973803072noreply@blogger.comtag:blogger.com,1999:blog-549043503714582179.post-2347959618406815462013-02-05T03:17:38.848+11:002013-02-05T03:17:38.848+11:00We have databases that are regularly cloned for va...We have databases that are regularly cloned for various reason. The naming conventions that are used become wrong for the target device after a TimeFinder clone is performed.<br /><br />How could the diskname (kfddde[0].dskname) in the disk directory be changed so that it is accurate and within our standards for the clone target?<br /><br />Thanks! <br />Anonymousnoreply@blogger.com