RMAN Duplicate to ASM Failing With ORA-19870 ORA-19504 ORA-15012 ORA-17502 ORA-15080

RMAN Duplicate to ASM Failing With ORA-19870 ORA-19504 ORA-15012 ORA-17502 ORA-15080

RMAN Duplicate to ASM Failing With ORA-19870 ORA-19504 ORA-15012 ORA-17502 ORA-15080

Titleimage

Posted by Patrick Hamou on 2017:09:20 14:12:06

APPLIES TO: Oracle Database - Enterprise Edition

Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 27-NOV-2015***

 

SYMPTOMS: RMAN, ASM

RMAN duplicate to ASM is failing with these errors:

  channel D1: reading from backup piece /mnt/ora_ab12345678_a12_a1 
  ORA-19870: error reading backup piece /mnt/ora_ab12345678_a12_a1 
  ORA-19504: failed to create file "+DISK1/mydatafile01.dbf" 
  ORA-15012: ASM file 'mydatafile01.dbf' does not exist 
  ORA-17502: ksfdcre:5 Failed to create file +DISK1/mydatafile01.dbf
  ORA-15080: synchronous I/O operation to a disk failed

And you might see these errors too:

  RMAN-00571: ================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===
  RMAN-00571: ================================================
  RMAN-03002: failure of Duplicate Db command at 02/22/2007 10:01:36 
  RMAN-03015: error occurred in stored script Memory Script 
  RMAN-06026: some targets not found - aborting restore 
  RMAN-06023: no backup or copy of datafile 411 found to restore

The alert log shows these errors:

  Errors in file /mydb/udump/mydb/trace_864352.trc: 
  ORA-27091: unable to queue I/O 
  ORA-27041: unable to open file 
  IBM AIX RISC System/6000 Error: 13: Permission denied 
  Additional information: 3 

 

CAUSE: $ORACLE_HOME

Incorrect operating system permissions.  
The operating system owner of the $ORACLE_HOME for the TARGET database is different 
from the operating system owner of the $ORACLE_HOME for ASM instance. 
.
The file permissions show 744 for the ASM disks. 
Both the owner of the $ORACLE_HOME for ASM instance and the one for the TARGET instance 
have a group of DBA, but file permissions of 744 only allow for "read" access to the DBA group.


Cause justified by trace file showing errors:


 

ORA-27091: unable to queue I/O 
ORA-27041: unable to open file 
SVR4 Error: 13: Permission denied 
Additional information: 3

SOLUTION: chmod command

For the ASM disks seen at the operating system prompt, change the permissions for the group (usually DBA) 
to allow at least read and write by the group.

 

Set the owner:group for the 'TARGET' database home to the same as the 'ASM' home.

 

Contact your system administrator or your operating system vendor for details on the chmod command.

Return to Blog