ORA-17502 and ORA-15001

 If you are creating a file on an ASM diskgroup, and you receive ORA-17502 along with ORA-15001, there is one reason of ORA-15001 already explained here. Also check if diskgroup mounted. But, if diskgroup is mounted and yet you receive this error, another reason of this could be the ownership set for “oracle” executable found under the $ORACLE_HOME from where ASM instance is running. When we install Grid Infrastructure and RDBMS softwares using different users, (GI home owned by grid user and RDBMS home and oracle user), then it is required that group ownership of “oracle” executable under RDBMS home is set to SYSASM privilege OS group which is ASMADMIN.

ORA-19504: failed to create file "+ORADATA/control01.ctl"

As we can see, duplicate database command is failing with ORA-19504.

RMAN> duplicate target database for standby; Starting Duplicate Db at 2018-02-14 10:45:31 using target database control file instead of recovery catalog allocated channel: ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: SID=2 device type=DISK contents of Memory Script: {    restore clone standby controlfile; } executing Memory Script   Starting restore at 2018-02-14 10:45:33 using channel ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: starting datafile backup set restore channel ORA_AUX_DISK_1: restoring control file channel ORA_AUX_DISK_1: reading from backup piece /backup/control_standby.bak channel ORA_AUX_DISK_1: ORA-19870: error while restoring backup piece /backup/control_standby.bak ORA-19504: failed to create file "+ORADATA/control01.ctl" ORA-17502: ksfdcre:3 Failed to create file +ORADATA/control01.ctl ORA-15001: diskgroup "ORADATA" does not exist or is not mounted ORA-15040: diskgroup is incomplete ORA-15040: diskgroup is incomplete ORA-15040: diskgroup is incomplete ORA-15040: diskgroup is incomplete ORA-15040: diskgroup is incomplete ORA-15040: diskgroup is incomplet failover to previous backup   channel ORA_AUX_DISK_1: starting datafile backup set restore channel ORA_AUX_DISK_1: restoring control file channel ORA_AUX_DISK_1: reading from backup piece /backup/ctl_2vsr6t3f_1_1.rbf RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00601: fatal error in recovery manager RMAN-03004: fatal error during execution of command RMAN-10041: Could not re-create polling channel context following failure. RMAN-10024: error setting up for rpc polling RMAN-10005: error opening cursor RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE

After seeing above error, when I checked the permissions on $ORACLE_HOME/bin/oracle, I saw following

[root]# ls –l /u01/app/oracle/product/11204/db_1/bin/oracle -rwsr-s--x  1 oracle oinstall 239924707 Jun 23    2017 /u01/app/oracle/product/11204/db_1/bin/oracle

 As we can see, group ownership is “oinstall”. It was supposed to be “asmadmin”. To fix the problem, change the group ownership by executing following as root.

[root]# chgrp asmadmin /u01/app/oracle/product/11204/db_1/bin/oracle [root]# ls –l /u01/app/oracle/product/11204/db_1/bin/oracle -rwsr-s--x  1 oracle asmadmin 239924707 Jun 23    2017 /u01/app/oracle/product/11204/db_1/bin/oracle

 After changing the ownership, files creation on ASM diskgroups should start working.