Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 
 

ORA-01187 from RMAN copy command tips

Oracle Tips by Burleson Consulting

 

Question:  I copied a database using the RMAN copy utility, and when I tried to open the database I got the ORA-01187 error, pointing to a temp file.

 

Is there an issue with copying temp tablespaces using RMAN?

 

Answer: Yes, there is!  MOSC note Note:167135.1, titled "How to Incorporate Locally Managed Temporary Tablespaces into the Backup Strategy" and dated 21-MAR-2006 notes that locally managed temporary tablespaces do not need to be backed up, and the ORA-01187 is related to other "issues" with backing-up TEMP tablespaces:

 

ORA-03217: Invalid option for alter of TEMPORARY TABLESPACE


Cause: Alter database and alter tablespace will not work on locally managed tempfiles as they have no reference in the data dictionary. There is no need to back up the tempfiles as they are used and destroyed every time you start up and shut down the database.
 

The MOSC notes says that there is no need to backup the temporary locally managed tablespaces for these reasons:

1. Locally managed tempfiles are always set to NOLOGGING mode. So thus will have no undo.

2. Extents are managed by bitmap in each datafile to keep track of free or used status of blocks in that datafile.

3. The data dictionary does not manage the tablespace.

4. Rollback information is not generated because there is no update on the data dictionary.

5. Media recovery does not recognize tempfiles.
 

Hence, this is expected behavior and you should drop and recreate your TEMP tablespace in the target database!


 

 

��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.