My Oracle Support Banner

Rman Restore Table Fails with ORA-29283 RMAN-06962 RMAN-06960 ORA-31626 in 12c (Doc ID 2231855.1)

Last updated on JUNE 16, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

========

Disclaimer:

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

 

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:


Auxiliary Database:
DB_NAME: test, DB_unique_name=pitr_pitr_test

========

 

Rman restore table fails with Below error during the export phase of the recovery table


When trying to restore a table the following error occurs

Could not delete auxiliary instance file tspitr_test.dmp
ORACLE error from target database:
ORA-29283: invalid file operation

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 02/06/2017 10:21:10
RMAN-06962: Error received during export of metadata
RMAN-06960: EXPDP> ORA-31626: job does not exist
ORA-31637: cannot create job TSPITR_EXP_test for user SYS
ORA-39062: error creating master process DM00
ORA-31613: Master process DM00 failed during startup.

 

Script used :-

RECOVER TABLE <schema>.sales UNTIL SCN 60678405 AUXILIARY DESTINATION '< omf directory >' REMAP TABLE '<schema>.'sales':'sales_new';

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.