RMAN Duplicate Corrupting Temp Files ORA-01187 ORA-01110
(Doc ID 2250889.1)
Last updated on JULY 07, 2020
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
- Rman duplicate completes without any error. Select or any Sort operation which uses tempfile fails with ORA-01187 or ORA-01110
- Files from Previous Rman duplicate still present.
- There is a requirement to do Rman duplicate using standard scripts every day to the auxiliary instance. Script uses a fix name for the tempfiles
- Prod and auxiliary on separate server but having same directory structure and on filesystem.
The purpose of this document is list various workarounds that can be used to Prevent this issue from Happening.
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
Few Best practice :-
Before you do a Rman duplicate ensure the datafiles /tempfiles from the Previous Rman duplicate are cleaned up.
Solution/Workaround (To Prevent this issue from Happening before duplicate is run)
Option 1 :- Use drop database.