Shulou(Shulou.com)05/31 Report--

This article will explain in detail how to solve the problem of RMAN-20207 error reporting. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

The solution to the RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time error is as follows:

When we do a RMAN recovery, we can use the list incarnation command to see which counterparts are contained in the control file.

When an incomplete recovery of Media Recover is done, the library is opened through resetlogs, and the Incarnation (database counterpart) represents the specific logical lifetime of the database.

DBA may sometimes need to restore the database using a backup made before the last resetlogs command to open the database, or you may need to restore to a point in time before the last resetlogs command.

For example, the following operation is to restore the database to the state it was on June 16, 2014.

Because we don't use catalog. So let's restore the control file first.

RMAN > restore controlfile from'/ db_backup/AJU_POST_CLONE/AJU_POST_BP23_EXP90/pajup/backupset_103_PAJUP_37pb14rh'

Starting restore at 21-JUL-14

Using target database control file instead of recovery catalog

Allocated channel: ORA_DISK_1

Channel ORA_DISK_1: SID=242 device type=DISK

Channel ORA_DISK_1: restoring control file

Channel ORA_DISK_1: restore complete, elapsed time: 00:00:03

Output file name=+DATA/pajup/control01.ctl

Output file name=+DATA/pajup/control02.ctl

Output file name=+DATA/pajup/control03.ctl

Finished restore at 21-JUL-14

Prepare to restore the database

RMAN > alter database mount

Database mounted

Released channel: ORA_DISK_1

RMAN > run {

2 > restore database

3 > set until time "to_date ('Jun 16-2014-23-15-21-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-12-13-12-13-12-12-12-12-

4 > recover database

Alter database open resetlogs

}

The following is the process of restore.

Starting restore at 21-JUL-14

Starting implicit crosscheck backup at 21-JUL-14

Allocated channel: ORA_DISK_1

Channel ORA_DISK_1: SID=242 device type=DISK

Crosschecked 72 objects

Finished implicit crosscheck backup at 21-JUL-14

Starting implicit crosscheck copy at 21-JUL-14

Using channel ORA_DISK_1

Finished implicit crosscheck copy at 21-JUL-14

Searching for all files in the recovery area

Cataloging files...

Cataloging done

List of Cataloged Files

=

File Name: + reco/pajup/ARCHIVELOG/2014_07_21/thread_2_seq_8.410521.853479197

File Name: + reco/pajup/ARCHIVELOG/2014_07_21/thread_1_seq_9.410522.853479197

File Name: + reco/pajup/ARCHIVELOG/2014_07_21/thread_1_seq_10.410523.853479215

File Name: + reco/pajup/ARCHIVELOG/2014_07_21/thread_1_seq_11.410576.853482583

File Name: + reco/pajup/ARCHIVELOG/2014_07_19/thread_1_seq_8.408628.853351343

File Name: + reco/pajup/ARCHIVELOG/2014_07_17/thread_2_seq_7.405955.853179347

File Name: + reco/pajup/ARCHIVELOG/2014_07_13/thread_1_seq_7.398318.852836481

File Name: + reco/pajup/ARCHIVELOG/2014_07_07/thread_2_seq_6.386816.852292813

File Name: + reco/pajup/ARCHIVELOG/2014_07_07/thread_1_seq_6.387446.852321621

File Name: + reco/pajup/ARCHIVELOG/2014_07_02/thread_1_seq_5.370578.851823445

File Name: + reco/pajup/ARCHIVELOG/2014_06_26/thread_2_seq_4.201949.851231251

File Name: + reco/pajup/ARCHIVELOG/2014_06_26/thread_1_seq_3.362093.851231251

File Name: + reco/pajup/ARCHIVELOG/2014_06_26/thread_1_seq_4.201943.851231313

File Name: + reco/pajup/ARCHIVELOG/2014_06_26/thread_2_seq_5.201969.851231313

File Name: + reco/pajup/ARCHIVELOG/2014_06_25/thread_1_seq_13.336310.851135615

File Name: + reco/pajup/ARCHIVELOG/2014_06_25/thread_1_seq_14.313117.851135615

File Name: + reco/pajup/ARCHIVELOG/2014_06_25/thread_1_seq_12.313662.851135629

File Name: + reco/pajup/ARCHIVELOG/2014_06_25/thread_2_seq_10.336295.851135629

File Name: + reco/pajup/ARCHIVELOG/2014_06_25/thread_2_seq_11.313730.851135633

File Name: + reco/pajup/ARCHIVELOG/2014_06_25/thread_2_seq_9.336277.851135633

File Name: + reco/pajup/ARCHIVELOG/2014_06_25/thread_2_seq_1.313806.851135651

File Name: + reco/pajup/ARCHIVELOG/2014_06_25/thread_2_seq_2.244417.851199885

File Name: + reco/pajup/ARCHIVELOG/2014_06_25/thread_1_seq_1.244552.851199885

File Name: + reco/pajup/ARCHIVELOG/2014_06_25/thread_1_seq_2.359503.851199943

File Name: + reco/pajup/ARCHIVELOG/2014_06_25/thread_2_seq_3.245263.851199945

File Name: + reco/pajup/ARCHIVELOG/2014_06_24/thread_2_seq_10.361501.851124225

File Name: + reco/pajup/ARCHIVELOG/2014_06_23/thread_1_seq_10.368614.850989033

File Name: + reco/pajup/ARCHIVELOG/2014_06_23/thread_1_seq_11.368758.850989567

File Name: + reco/pajup/ARCHIVELOG/2014_06_23/thread_1_seq_12.368840.850990925

File Name: + reco/pajup/ARCHIVELOG/2014_06_23/thread_2_seq_8.368841.850990927

File Name: + reco/pajup/ARCHIVELOG/2014_06_23/thread_1_seq_13.368842.850990985

File Name: + reco/pajup/ARCHIVELOG/2014_06_23/thread_2_seq_9.368843.850990985

File Name: + reco/pajup/ARCHIVELOG/2014_06_21/thread_2_seq_5.364394.850786171

File Name: + reco/pajup/ARCHIVELOG/2014_06_21/thread_2_seq_6.364405.850786185

File Name: + reco/pajup/ARCHIVELOG/2014_06_21/thread_2_seq_7.364406.850786185

File Name: + reco/pajup/ARCHIVELOG/2014_06_21/thread_1_seq_9.364407.850786187

File Name: + reco/pajup/ARCHIVELOG/2014_06_20/thread_1_seq_7.364188.850780167

File Name: + reco/pajup/ARCHIVELOG/2014_06_20/thread_1_seq_8.364176.850780547

Using channel ORA_DISK_1

Channel ORA_DISK_1: starting datafile backup set restore

Channel ORA_DISK_1: specifying datafile (s) to restore from backup set

Channel ORA_DISK_1: restoring datafile 00003 to + DATA/pajup/datafile/undotbs01.dbf

Channel ORA_DISK_1: restoring datafile 00007 to + DATA/pajup/datafile/fa_oam.dbf

Channel ORA_DISK_1: restoring datafile 00008 to + DATA/pajup/datafile/fa_iassdpm.dbf

Channel ORA_DISK_1: restoring datafile 00012 to + DATA/pajup/datafile/fa_oimlob.dbf

Channel ORA_DISK_1: reading from backup piece / db_backup/AJU_BACKUP/POST_REL8FA_UPG/pajup/backupset_79_PAJUP_2fp8rnnk

Channel ORA_DISK_1: piece handle=/db_backup/AJU_BACKUP/POST_REL8FA_UPG/pajup/backupset_79_PAJUP_2fp8rnnk tag=FULL_ARCHIVE_TO_NFS

Channel ORA_DISK_1: restored backup piece 1

Channel ORA_DISK_1: restore complete, elapsed time: 00:00:26

Channel ORA_DISK_1: starting datafile backup set restore

Channel ORA_DISK_1: specifying datafile (s) to restore from backup set

Channel ORA_DISK_1: restoring datafile 00005 to + DATA/pajup/datafile/example01.dbf

Channel ORA_DISK_1: restoring datafile 00010 to + DATA/pajup/datafile/fa_ias_iau.dbf

Channel ORA_DISK_1: restoring datafile 00011 to + DATA/pajup/datafile/fa_oim.dbf

Channel ORA_DISK_1: restoring datafile 00015 to + DATA/pajup/datafile/rman_data_1_tbs.3263.839401565

Channel ORA_DISK_1: reading from backup piece / db_backup/AJU_BACKUP/POST_REL8FA_UPG/pajup/backupset_78_PAJUP_2ep8rnnk

Channel ORA_DISK_1: piece handle=/db_backup/AJU_BACKUP/POST_REL8FA_UPG/pajup/backupset_78_PAJUP_2ep8rnnk tag=FULL_ARCHIVE_TO_NFS

Channel ORA_DISK_1: restored backup piece 1

Channel ORA_DISK_1: restore complete, elapsed time: 00:00:35

Channel ORA_DISK_1: starting datafile backup set restore

Channel ORA_DISK_1: specifying datafile (s) to restore from backup set

Channel ORA_DISK_1: restoring datafile 00001 to + DATA/pajup/datafile/system01.dbf

Channel ORA_DISK_1: restoring datafile 00006 to + DATA/pajup/datafile/fa_iasoif.dbf

Channel ORA_DISK_1: restoring datafile 00013 to + DATA/pajup/datafile/fa_soainfra.dbf

Channel ORA_DISK_1: restoring datafile 00014 to + DATA/pajup/datafile/undotbs2.dbf

Channel ORA_DISK_1: reading from backup piece / db_backup/AJU_BACKUP/POST_REL8FA_UPG/pajup/backupset_80_PAJUP_2gp8rnnl

Channel ORA_DISK_1: piece handle=/db_backup/AJU_BACKUP/POST_REL8FA_UPG/pajup/backupset_80_PAJUP_2gp8rnnl tag=FULL_ARCHIVE_TO_NFS

Channel ORA_DISK_1: restored backup piece 1

Channel ORA_DISK_1: restore complete, elapsed time: 00:00:45

Channel ORA_DISK_1: starting datafile backup set restore

Channel ORA_DISK_1: specifying datafile (s) to restore from backup set

Channel ORA_DISK_1: restoring datafile 00002 to + DATA/pajup/datafile/sysaux01.dbf

Channel ORA_DISK_1: restoring datafile 00004 to + DATA/pajup/datafile/users01.dbf

Channel ORA_DISK_1: restoring datafile 00009 to + DATA/pajup/datafile/fa_mds.dbf

Channel ORA_DISK_1: reading from backup piece / db_backup/AJU_BACKUP/POST_REL8FA_UPG/pajup/backupset_77_PAJUP_2dp8rnnk

Channel ORA_DISK_1: piece handle=/db_backup/AJU_BACKUP/POST_REL8FA_UPG/pajup/backupset_77_PAJUP_2dp8rnnk tag=FULL_ARCHIVE_TO_NFS

Channel ORA_DISK_1: restored backup piece 1

Channel ORA_DISK_1: restore complete, elapsed time: 00:00:55

Finished restore at 21-JUL-14

Executing command: SET until clause

Starting recover at 21-JUL-14

Using channel ORA_DISK_1

RMAN-00571: =

RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =

RMAN-00571: =

RMAN-03002: failure of recover command at 07/21/2014 07:13:24

RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time

This is a common error message when preparing for recovery. Usually we can solve it through the following ways.

RMAN > list incarnation

List of Database Incarnations

DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time

-

1 1 PAJUP 2941400143 PARENT 1383125 29-JUL-13

2 2 PAJUP 2941400143 PARENT 32325998 13-FEB-14

4 4 PAJUP 2941400143 PARENT 34279940 11-APR-14

3 3 PAJUP 2941400143 ORPHAN 34279997 20-FEB-14

5 5 PAJUP 2941400143 PARENT 36067904 22-APR-14

8 8 PAJUP 2941400143 PARENT 43039998 16-JUN-14

9 9 PAJUP 2941400143 CURRENT 44911476 25-JUN-14

7 7 PAJUP 2941400143 ORPHAN 45126273 04-JUN-14

6 6 PAJUP 2941400143 ORPHAN 45404604 06-JUN-14

RMAN > reset database to incarnation 8

Database reset to incarnation 8

RMAN > run {

2 > restore database

3 > set until time "to_date ('Jun 16 2014 23 14 21 DD YYYY HH24:MI:SS' 26 minutes Mon DD YYYY HH24:MI:SS')"

4 > recover database

Alter database open resetlogs

} 5 > 6 >

Starting restore at 21-JUL-14

Using channel ORA_DISK_1

Skipping datafile 1; already restored to file + DATA/pajup/datafile/system01.dbf

Skipping datafile 6; already restored to file + DATA/pajup/datafile/fa_iasoif.dbf

Skipping datafile 13; already restored to file + DATA/pajup/datafile/fa_soainfra.dbf

Skipping datafile 14; already restored to file + DATA/pajup/datafile/undotbs2.dbf

Skipping datafile 2; already restored to file + DATA/pajup/datafile/sysaux01.dbf

Skipping datafile 4; already restored to file + DATA/pajup/datafile/users01.dbf

Skipping datafile 9; already restored to file + DATA/pajup/datafile/fa_mds.dbf

Skipping datafile 3; already restored to file + DATA/pajup/datafile/undotbs01.dbf

Skipping datafile 7; already restored to file + DATA/pajup/datafile/fa_oam.dbf

Skipping datafile 8; already restored to file + DATA/pajup/datafile/fa_iassdpm.dbf

Skipping datafile 12; already restored to file + DATA/pajup/datafile/fa_oimlob.dbf

Skipping datafile 5; already restored to file + DATA/pajup/datafile/example01.dbf

Skipping datafile 10; already restored to file + DATA/pajup/datafile/fa_ias_iau.dbf

Skipping datafile 11; already restored to file + DATA/pajup/datafile/fa_oim.dbf

Skipping datafile 15; already restored to file + DATA/pajup/datafile/rman_data_1_tbs.3263.839401565

Restore not done; all files read only, offline, or already restored

Finished restore at 21-JUL-14

Executing command: SET until clause

Starting recover at 21-JUL-14

Using channel ORA_DISK_1

Starting media recovery

Archived log for thread 1 with sequence 13 is already on disk as file + RECO/pajup/archivelog/2014_05_21/thread_1_seq_13.327534.848158501

Archived log for thread 2 with sequence 9 is already on disk as file + RECO/pajup/archivelog/2014_05_21/thread_2_seq_9.327535.848158501

Archived log for thread 1 with sequence 1 is already on disk as file + RECO/pajup/archivelog/2014_06_16/thread_1_seq_1.358127.850419155

Archived log for thread 1 with sequence 2 is already on disk as file + RECO/pajup/archivelog/2014_06_16/thread_1_seq_2.358128.850419159

Archived log for thread 1 with sequence 3 is already on disk as file + RECO/pajup/archivelog/2014_06_16/thread_1_seq_3.358331.850429549

Archived log for thread 1 with sequence 4 is already on disk as file + RECO/pajup/archivelog/2014_06_16/thread_1_seq_4.358332.850429567

Archived log for thread 1 with sequence 5 is already on disk as file + RECO/pajup/archivelog/2014_06_16/thread_1_seq_5.358553.850432819

Archived log for thread 1 with sequence 6 is already on disk as file + RECO/pajup/archivelog/2014_06_16/thread_1_seq_6.358556.850432877

Archived log for thread 1 with sequence 7 is already on disk as file + RECO/pajup/archivelog/2014_06_20/thread_1_seq_7.364188.850780167

Archived log for thread 2 with sequence 1 is already on disk as file + RECO/pajup/archivelog/2014_06_16/thread_2_seq_1.358123.850419045

Archived log for thread 2 with sequence 2 is already on disk as file + RECO/pajup/archivelog/2014_06_16/thread_2_seq_2.358201.850425435

Archived log for thread 2 with sequence 3 is already on disk as file + RECO/pajup/archivelog/2014_06_16/thread_2_seq_3.358554.850432821

Archived log for thread 2 with sequence 4 is already on disk as file + RECO/pajup/archivelog/2014_06_16/thread_2_seq_4.358557.850432877

Archived log for thread 2 with sequence 5 is already on disk as file + RECO/pajup/archivelog/2014_06_21/thread_2_seq_5.364394.850786171

Archived log file name=+RECO/pajup/archivelog/2014_05_21/thread_1_seq_13.327534.848158501 thread=1 sequence=13

Archived log file name=+RECO/pajup/archivelog/2014_05_21/thread_2_seq_9.327535.848158501 thread=2 sequence=9

Archived log file name=+RECO/pajup/archivelog/2014_06_16/thread_1_seq_1.358127.850419155 thread=1 sequence=1

Archived log file name=+RECO/pajup/archivelog/2014_06_16/thread_2_seq_1.358123.850419045 thread=2 sequence=1

Archived log file name=+RECO/pajup/archivelog/2014_06_16/thread_1_seq_2.358128.850419159 thread=1 sequence=2

Archived log file name=+RECO/pajup/archivelog/2014_06_16/thread_2_seq_2.358201.850425435 thread=2 sequence=2

Archived log file name=+RECO/pajup/archivelog/2014_06_16/thread_1_seq_3.358331.850429549 thread=1 sequence=3

Archived log file name=+RECO/pajup/archivelog/2014_06_16/thread_1_seq_4.358332.850429567 thread=1 sequence=4

Archived log file name=+RECO/pajup/archivelog/2014_06_16/thread_2_seq_3.358554.850432821 thread=2 sequence=3

Archived log file name=+RECO/pajup/archivelog/2014_06_16/thread_1_seq_5.358553.850432819 thread=1 sequence=5

Archived log file name=+RECO/pajup/archivelog/2014_06_16/thread_1_seq_6.358556.850432877 thread=1 sequence=6

Archived log file name=+RECO/pajup/archivelog/2014_06_16/thread_2_seq_4.358557.850432877 thread=2 sequence=4

Archived log file name=+RECO/pajup/archivelog/2014_06_20/thread_1_seq_7.364188.850780167 thread=1 sequence=7

Archived log file name=+RECO/pajup/archivelog/2014_06_21/thread_2_seq_5.364394.850786171 thread=2 sequence=5

Media recovery complete, elapsed time: 00:00:23

Finished recover at 21-JUL-14

Database opened

Check the results of the recovery.

RMAN > validate database check logical

Starting validate at 21-JUL-14

Using channel ORA_DISK_1

Channel ORA_DISK_1: starting validation of datafile

Channel ORA_DISK_1: specifying datafile (s) for validation

Input datafile file number=00002 name=+DATA/pajup/datafile/sysaux01.dbf

Input datafile file number=00011 name=+DATA/pajup/datafile/fa_oim.dbf

Input datafile file number=00001 name=+DATA/pajup/datafile/system01.dbf

Input datafile file number=00003 name=+DATA/pajup/datafile/undotbs01.dbf

Input datafile file number=00012 name=+DATA/pajup/datafile/fa_oimlob.dbf

Input datafile file number=00014 name=+DATA/pajup/datafile/undotbs2.dbf

Input datafile file number=00005 name=+DATA/pajup/datafile/example01.dbf

Input datafile file number=00008 name=+DATA/pajup/datafile/fa_iassdpm.dbf

Input datafile file number=00013 name=+DATA/pajup/datafile/fa_soainfra.dbf

Input datafile file number=00015 name=+DATA/pajup/datafile/rman_data_1_tbs.3263.839401565

Input datafile file number=00009 name=+DATA/pajup/datafile/fa_mds.dbf

Input datafile file number=00007 name=+DATA/pajup/datafile/fa_oam.dbf

Input datafile file number=00006 name=+DATA/pajup/datafile/fa_iasoif.dbf

Input datafile file number=00010 name=+DATA/pajup/datafile/fa_ias_iau.dbf

Input datafile file number=00004 name=+DATA/pajup/datafile/users01.dbf

Channel ORA_DISK_1: validation complete, elapsed time: 00:00:15

List of Datafiles

=

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

1 OK 0 12976 98617 43263327

File Name: + DATA/pajup/datafile/system01.dbf

Block Type Blocks Failing Blocks Processed

Data 0 64570

Index 0 14789

Other 0 6225

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

2 OK 0 18614 185673 43263403

File Name: + DATA/pajup/datafile/sysaux01.dbf

Block Type Blocks Failing Blocks Processed

Data 0 57085

Index 0 53422

Other 0 56479

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

3 OK 0 1 74252 43263402

File Name: + DATA/pajup/datafile/undotbs01.dbf

Block Type Blocks Failing Blocks Processed

Data 0 0

Index 0 0

Other 0 74239

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

4 OK 0 18 667 1540593

File Name: + DATA/pajup/datafile/users01.dbf

Block Type Blocks Failing Blocks Processed

Data 0 91

Index 0 39

Other 0 492

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

5 OK 2179 31362 44244 43237510

File Name: + DATA/pajup/datafile/example01.dbf

Block Type Blocks Failing Blocks Processed

Data 0 4418

Index 0 1148

Other 0 7312

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

6 OK 0 37 7682 1190254

File Name: + DATA/pajup/datafile/fa_iasoif.dbf

Block Type Blocks Failing Blocks Processed

Data 0 5

Index 0 14

Other 0 7624

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

7 OK 0 337 12815 43242072

File Name: + DATA/pajup/datafile/fa_oam.dbf

Block Type Blocks Failing Blocks Processed

Data 0 2194

Index 0 1887

Other 0 8382

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

8 OK 0 358 38412 42846314

File Name: + DATA/pajup/datafile/fa_iassdpm.dbf

Block Type Blocks Failing Blocks Processed

Data 0 121

Index 0 71

Other 0 37850

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

9 OK 0 6449 19219 43241292

File Name: + DATA/pajup/datafile/fa_mds.dbf

Block Type Blocks Failing Blocks Processed

Data 0 1766

Index 0 4339

Other 0 6646

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

10 OK 0 49 7681 1104562

File Name: + DATA/pajup/datafile/fa_ias_iau.dbf

Block Type Blocks Failing Blocks Processed

Data 0 38

Index 0 28

Other 0 7565

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

11 OK 2834 7482 115201 43243571

File Name: + DATA/pajup/datafile/fa_oim.dbf

Block Type Blocks Failing Blocks Processed

Data 0 49738

Index 0 16023

Other 0 41957

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

12 OK 0 2111 64002 43038970

File Name: + DATA/pajup/datafile/fa_oimlob.dbf

Block Type Blocks Failing Blocks Processed

Data 0 0

Index 0 876

Other 0 61013

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

13 OK 0 542 25601 43038980

File Name: + DATA/pajup/datafile/fa_soainfra.dbf

Block Type Blocks Failing Blocks Processed

Data 0 188

Index 0 85

Other 0 24785

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

14 OK 01 53362 43260164

File Name: + DATA/pajup/datafile/undotbs2.dbf

Block Type Blocks Failing Blocks Processed

Data 0 0

Index 0 0

Other 0 53359

File Status Marked Corrupt Empty Blocks Blocks Examined High SCN

-

15 OK 01 25601 1638736

File Name: + DATA/pajup/datafile/rman_data_1_tbs.3263.839401565

Block Type Blocks Failing Blocks Processed

Data 0 0

Index 0 0

Other 0 25599

Channel ORA_DISK_1: starting validation of datafile

Channel ORA_DISK_1: specifying datafile (s) for validation

Including current control file for validation

Including current SPFILE in backup set

Channel ORA_DISK_1: validation complete, elapsed time: 00:00:01

List of Control File and SPFILE

= =

File Type Status Blocks Failing Blocks Examined

--

SPFILE OK 0 2

Control File OK 0 614

Finished validate at 21-JUL-14

RMAN > exit

This is the end of the article on "how to solve the problem of RMAN-20207 error reporting". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.