Thursday, October 6, 2016

RMAN Restore failed with error ORA-19870,ORA-19504, ORA-27086



RMAN Restore failed with error ORA-19870,ORA-19504, ORA-27086 Permission denied Restore to different host




ORA-27086 Permission denied

Backup Taken in Lab Server 1

and Restoration tested in different Server.

Below is the error noticed and restoration completed for other peice but not completed for one peice

ORA-19870: error reading backup piece ORACLEDB_DB_07rhckp9_61447_1
ORA-19504: failed to create file "/u01/oracle/xyz_app01_2.dbf"
ORA-27086: unable to lock file - already in use
Linux : 13: Permission denied

ORA-19870: error reading backup piece ORACLEDB_DB_07rhckp9_61447_1
ORA-19507: failed to retrieve sequential file, handle="ORACLEDB_DB_07rhckp9_61447_1 ", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
   Backup file not found in DISK 
failover to previous backup

But backup peice is available in backed up location


====

After analysing  below error
ORA-19870: error reading backup piece bk_ug4p912_s98820_p1_t855090210
ORA-19504: failed to create file "/u01/oracle/xyz_app01_2.dbf"
ORA-27086: unable to lock file - already in use
Linux : 13: Permission denied

Resolved the issue

One source Server backup was taken the datafile xyz_app01_2.dbf name was repeated but if different mount point. like below

File # 70 belongs to /u01/oracle/xyz_app01_2.dbf  ------ belongs to /u01/oracle
File # 89 belongs to /u01/oracle/xyz_app01_2.dbf  ------ belongs to /u02/oracle

When restoring the file it restores to same destination in /u01 and throws below error
ORA-19870: error reading backup piece ORACLEDB_DB_07rhckp9_61447_1
ORA-19504: failed to create file "/u01/oracle/xyz_app01_2.dbf"
ORA-27086: unable to lock file - already in use
Linux : 13: Permission denied



Solution
=====

Set newname to datafile 89 to '/u01/oracle/xyz_app01_2_2.dbf'; solved the issue.

For datafile 70 let datafile to be same.

After doing all these issues got fixed and database restored successfully


No comments: