My Oracle Support Banner

Creating DBaaS Instance From Long Term Backup Fails (Doc ID 2445755.1)

Last updated on FEBRUARY 04, 2019

Applies to:

Oracle Database Cloud Service - Version N/A to N/A [Release 1.0]
Information in this document applies to any platform.

Symptoms

While creating new instance using Initialize Data From Backup option fails.

Also, created a new deployment and tried to replace the database from the backup. That also failed.

The dbda log shows long term backup was used to replace the database:


list backup summary tag = JAAS20180817T064859;
list backup summary tag = JAAS20180817T064859;
set echo off;
quit;
2018-08-20 06:22:51 - RMAN OUTPUT:

Recovery Manager: Release 12.2.0.1.0 - Production on Mon Aug 20 06:22:33 2018

Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.

RMAN-06193: connected to target database (not started)

RMAN>
RMAN-03029: echo set on


RMAN> startup mount;
RMAN-06196: Oracle instance started
RMAN-06199: database mounted

Total System Global Area   22280142848 bytes

Fixed Size                    12343608 bytes
Variable Size               2818574024 bytes
Database Buffers           19327352832 bytes
Redo Buffers                 121872384 bytes


RMAN> list backup summary tag = JAAS20180817T064859;
RMAN-06009: using target database control file instead of recovery catalog
RMAN-06345: List of Backups
RMAN-06346: ===============
RMAN-06347: Key     TY LV S Device Type Completion Time #Pieces #Copies
Compressed Tag
RMAN-06348: ------- -- -- - ----------- --------------- ------- -------
---------- ---
RMAN-06349: 62      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 63      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 64      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 65      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 66      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 67      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 68      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 69      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 70      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 71      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 72      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 73      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 74      B  A  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 75      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859
RMAN-06349: 76      B  F  A SBT_TAPE    17-AUG-18       1       1       NO    
     JAAS20180817T064859

..
2018-08-20 06:23:31 - dbda::INFO restore_database:      RMAN-03002: failure
of restore command at 08/20/2018 06:23:31
2018-08-20 06:23:31 - dbda::INFO restore_database:      RMAN-06026: some
targets not found - aborting restore
2018-08-20 06:23:31 - dbda::INFO restore_database:      RMAN-06023: no backup
or copy of datafile 70 found to restore
2018-08-20 06:23:31 - dbda::INFO restore_database:      RMAN-06023: no backup
or copy of datafile 69 found to restore
2018-08-20 06:23:31 - dbda::INFO restore_database:      RMAN-06023: no backup
or copy of datafile 68 found to restore
2018-08-20 06:23:31 - dbda::INFO restore_database:      RMAN-06023: no backup
or copy of datafile 53 found to restore
2018-08-20 06:23:31 - dbda::INFO restore_database:      RMAN-06023: no backup
or copy of datafile 52 found to restore
2018-08-20 06:23:31 - dbda::INFO restore_database:      RMAN-06023: no backup
or copy of datafile 51 found to restore
2018-08-20 06:23:31 - dbda::INFO restore_database:      
2018-08-20 06:23:31 - dbda::INFO restore_database:      RMAN>
2018-08-20 06:23:31 - dbda::INFO restore_database:      
2018-08-20 06:23:31 - dbda::INFO restore_database:      Recovery Manager
complete.


In this log, we see
 dbda::INFO restore_controlfile: RMAN INPUT : RESTORE UNTIL TIME
"to_date('08/20/2018 23:59:59','MM/DD/YYYY HH24:MI:SS')" CONTROLFILE FROM
AUTOBACKUP MAXDAYS 2;

whereas the tag is JAAS20180817T064859.

Changes

 

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
Changes
Cause
Solution
References


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