标签：fails Doc CREATE DB 2078790.1 tablespace FILE RMAN TSPITR

TSPITR fails With RMAN-06553 (Doc ID 2078790.1)

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.4 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata 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

TSPITR fails With RMAN-06553 when the tablespace (using OMF files) is dropped including contents and datafiles

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/22/2015 16:43:08
RMAN-03015: error occurred in stored script Memory Script
RMAN-06553: DB_CREATE_FILE_DEST must be set for SET NEWNAME … TO NEW

CHANGES

 DB_CREATE_FILE_DEST is no longer defined.  

CAUSE

Expected behavior based on the following documentation:

"Auxiliary set data files can have Oracle Managed Files (OMF) in the target and can use Automatic Storage Management (ASM) or non-ASM storage. TSPITR performs name conversion differently when the DB_FILE_NAME_CONVERT initialization parameter is set and the OMF files are in ASM or non-ASM storage."

Problem occurs because DB_CREATE_FILE_DEST is not defined.  It is needed when tablespace is dropped including contents and datafiles.  When tablespace is dropped including contents but datafiles are kept then DB_CREATE_FILE_DEST is not needed since RMAN is aware of the location of the datafile. 

This behaviour can be demonstrated using the following simple tests:

Test 1:
1. Create a new tablespace and add an OMF datafile
2. Unset DB_CREATE_FILE_DEST
3. Backup database to include the new tablespace
4. Drop the newly created tablespace including contents but keep the datafile
5. Do TSPITR - the process should be flawless

Test 2:
1. Create a new tablespace and add a OMF datafile
2. Unset DB_CREATE_FILE_DEST
3. Backup database to include the new tablespace
4. Drop the newly created tablespace including contents and datafile
5. Do TSPITR - the process fails with error
RMAN-03002: failure of recover command at 11/16/2015 22:20:35
RMAN-03015: error occurred in stored script Memory Script
RMAN-06553: DB_CREATE_FILE_DEST must be set for SET NEWNAME … TO NEW

SOLUTION

Use "SET NEWNAME FOR DATAFILE <df_number> to "/<desired_path>", where <df_number> is the datafile number and <desired_path> is the desired destination and datafile name.   

For example: 

RUN
{
SET NEWNAME FOR DATAFILE 4 TO "/<desired location>/users.dbf";
RECOVER TABLESPACE users UNTIL TIME "to_date('02-nov-2015 12:53:08','dd-mon-yyyy hh24:mi:ss')" AUXILIARY DESTINATION '/<desired location>/';
}

标签：fails,Doc,CREATE,DB,2078790.1,tablespace,FILE,RMAN,TSPITR
来源： https://www.cnblogs.com/zylong-sys/p/12005983.html

本站声明： 1. iCode9 技术分享网（下文简称本站）提供的所有内容，仅供技术学习、探讨和分享；
2. 关于本站的所有留言、评论、转载及引用，纯属内容发起人的个人观点，与本站观点和立场无关；
3. 关于本站的所有言论和文字，纯属内容发起人的个人观点，与本站观点和立场无关；
4. 本站文章均是网友提供，不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属；如您发现该文章侵犯了您的权益，可联系我们第一时间进行删除；
5. 本站为非盈利性的个人网站，所有内容不会用来进行牟利，也不会利用任何形式的广告来间接获益，纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。