My Oracle Support Banner

RMAN-06003: ORACLE Error from Target Database: ORA-01152: File x was not Restored from a Sufficiently Old Backup (Doc ID 207324.1)

Last updated on NOVEMBER 19, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 9.0.1.0 and later
Information in this document applies to any platform.

Symptoms

 RMAN-06003: ORACLE error from target database: ORA-01152: file 3 was not restored from a sufficiently old backup

 

### Restore Scripts used ###

RMAN> run {
run allocate channel t1 type disk;
restore controlfile;
}

RMAN> run {
allocate channel t1 type disk;
alter database mount;
restore database;
set until logseq=398 thread=1;
recover database;
alter database open resetlogs;
release channel t1;
}

 

### RMAN Errorstack ###

 

Recover 3 is where the 1st error occurred. In recover(3) phase we are looking
for any redo that can be applied to the files. In this case we need to apply
sequence# 398 to roll datafile 3 forward.

### From list backup of archivelog ###

List of Backup Sets
Key Recid Stamp LV Set Stamp Set Count Completion Time
------- ---------- ---------- -- ---------- ---------- ----------------------
50661 123 469324996 0 469324995 124 08-AUG-02

List of Backup Pieces
Key Pc# Cp# Status Completion Time Piece Name
------- --- --- ----------- ---------------------- ------------------------
50663 1 1 AVAILABLE 08-AUG-02 /<backuppiece path/name>

List of Archived Logs Included
Thrd Seq Low SCN Next SCN Low Time Next Time
---- ------- ---------- ---------- --------------- ---------------
1 395 411815 413762 07-AUG-02 07-AUG-02
1 396 413762 416226 07-AUG-02 07-AUG-02
1 397 416226 419415 07-AUG-02 07-AUG-02
1 398 419415 419900 07-AUG-02 08-AUG-02

The 'set until logseq 398 thread 1' will stop after log sequence 397 has been
applied so 398 will not be applied for recovery. The highest change# in that
case will be 419414 (Next SCN-1).

### Alert.log ###

Verify the checkpoint change# of the restored datafile.

Thu Aug 8 08:02:29 2002
Full restore complete of datafile 3 /<path>/<file_name>.dbf
checkpoint is 419897

The alert.log shows the change# for all restored files so we can use this
value to verify that the correct 'set until' was used.

 

 

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!


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