Hi everybody, thank you for your replies. Here comes the solution. http://www.usn-it.de/index.php/2013/01/07/oracle-asm-error-failed-to-update-diskgroup-resource-ora-data-dg/ "Give your admin-made VIPs at least the ACL rights “-u user:oracle:r-x” to enable ASM hooking its resources into grid infrastructure. Definitely not documented, and thus, maybe nice to know." Took me a few days to find out this not very obvious fact, but it was worth the effort. :) Thansk again and best regards Martin Klier Marcin Przepiorowski schrieb: > On Mon, Oct 15, 2012 at 1:04 PM, Martin Klier <usn@xxxxxxxxx> wrote: >> Hi Fuad, >> >> we are talking about GI 11gR2 here. >> >> Usually, each existing diskgroup is represented as, for example, a GI >> service ora.ORADATA.dg. On 6 of my other systems, it works this way. >> This entry is created, as soon as I create the DG with asmca or SQL*PLUS. >> >> >> > Did you try to create a new DB and use srvctl to add DB to CRS and add this > diskgroup as dependency ? > If I remember correctly this should add diskgroup to CRS resources. > -- Usn's IT Blog for Linux, Oracle, Asterisk http://www.usn-it.de -- //www.freelists.org/webpage/oracle-l