9 Replies Latest reply on Oct 25, 2013 2:58 AM by Lonion

Why it automatically recover current redo log in RMAN command window?

Lonion Aug 30, 2013 9:16 AM

Firstly, I restore controlfile and datafiles from a backupset.

Then when I recover database in RMAN command window like below:

RMAN> recover database;

Starting recover at 15-AUG-13

using target database control file instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: sid=156 devtype=DISK

starting media recovery

archive log thread 1 sequence 9 is already on disk as file /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd0slz_.arc

archive log thread 1 sequence 10 is already on disk as file

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90sd0tsb_.arc

archive log thread 1 sequence 11 is already on disk as file

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90sd110b_.arc

archive log thread 1 sequence 12 is already on disk as file

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90sd2ksr_.arc

archive log thread 1 sequence 13 is already on disk as file

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90sd2mc6_.arc

archive log thread 1 sequence 14 is already on disk as file

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90sd2qrm_.arc

archive log thread 1 sequence 15 is already on disk as file

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90sd2s0w_.arc

archive log thread 1 sequence 16 is already on disk as file /u01/app/oracle/oradata/lonion/redo03.log

archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd0slz_.arc thread=1 sequence=9

archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90sd0tsb_.arc thread=1 sequence=10

archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90sd110b_.arc thread=1 sequence=11

archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90sd2ksr_.arc thread=1 sequence=12

archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90sd2mc6_.arc thread=1 sequence=13

archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90sd2qrm_.arc thread=1 sequence=14

archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90sd2s0w_.arc thread=1 sequence=15

archive log filename=/u01/app/oracle/oradata/lonion/redo03.log thread=1 sequence=16

media recovery complete, elapsed time: 00:00:04

Finished recover at 15-AUG-13

RMAN>

But, when I recover database in SQL*Plus command window like below:

[oracle@lonion ~]$ uniread sqlplus /nolog

[uniread] Loaded history (2178 lines)

SQL*Plus: Release 10.2.0.1.0 - Production on Thu Aug 15 19:25:38 2013

SQL> conn /as sysdba

Connected.

SQL>

SQL> recover database;

ORA-00283: recovery session canceled due to errors

ORA-01610: recovery using the BACKUP CONTROLFILE option must be done

SQL> recover database using backup controlfile;

ORA-00279: change 2147842454 generated at 08/15/2013 18:34:28 needed for thread

ORA-00289: suggestion :

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_%u_.a

ORA-00280: change 2147842454 for thread 1 is in sequence #9

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

auto

ORA-00279: change 2147842651 generated at 08/15/2013 18:40:25 needed for thread

ORA-00289: suggestion :

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_%u_.

arc

ORA-00280: change 2147842651 for thread 1 is in sequence #10

ORA-00278: log file

'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd

0slz_.arc' no longer needed for this recovery

ORA-00279: change 2147842653 generated at 08/15/2013 18:40:26 needed for thread

ORA-00289: suggestion :

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_%u_.

arc

ORA-00280: change 2147842653 for thread 1 is in sequence #11

ORA-00278: log file

'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90s

d0tsb_.arc' no longer needed for this recovery

ORA-00279: change 2147842656 generated at 08/15/2013 18:40:32 needed for thread

ORA-00289: suggestion :

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_%u_.

arc

ORA-00280: change 2147842656 for thread 1 is in sequence #12

ORA-00278: log file

'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90s

d110b_.arc' no longer needed for this recovery

ORA-00279: change 2147842684 generated at 08/15/2013 18:41:21 needed for thread

ORA-00289: suggestion :

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_%u_.

arc

ORA-00280: change 2147842684 for thread 1 is in sequence #13

ORA-00278: log file

'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90s

d2ksr_.arc' no longer needed for this recovery

ORA-00279: change 2147842686 generated at 08/15/2013 18:41:23 needed for thread

ORA-00289: suggestion :

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_%u_.

arc

ORA-00280: change 2147842686 for thread 1 is in sequence #14

ORA-00278: log file

'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90s

d2mc6_.arc' no longer needed for this recovery

ORA-00279: change 2147842689 generated at 08/15/2013 18:41:27 needed for thread

ORA-00289: suggestion :

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_%u_.

arc

ORA-00280: change 2147842689 for thread 1 is in sequence #15

ORA-00278: log file

'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90s

d2qrm_.arc' no longer needed for this recovery

ORA-00279: change 2147842691 generated at 08/15/2013 18:41:28 needed for thread

ORA-00289: suggestion :

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_16_%u_.

arc

ORA-00280: change 2147842691 for thread 1 is in sequence #16

ORA-00278: log file

'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90s

g0or9_.arc' no longer needed for this recovery

ORA-00279: change 2147842986 generated at 08/15/2013 19:14:29 needed for thread

ORA-00289: suggestion :

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_.

arc

ORA-00280: change 2147842986 for thread 1 is in sequence #17

ORA-00278: log file

'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_16_90s

g0os5_.arc' no longer needed for this recovery

ORA-00308: cannot open archived log

'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_

.arc'

ORA-27037: unable to obtain file status

Linux Error: 2: No such file or directory

Additional information: 3

SQL> recover database using backup controlfile;

ORA-00279: change 2147842986 generated at 08/15/2013 19:14:29 needed for thread

ORA-00289: suggestion :

/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_.

arc

ORA-00280: change 2147842986 for thread 1 is in sequence #17

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

/u01/app/oracle/oradata/lonion/redo01.log ---- Yon see, proceeding this process, it can't automatically apply the current redo log.

Log applied.

Media recovery complete.

SQL>

Question Coming:

Now, my question is that 「Why it automatically recover current redo log in RMAN command window but not in SQL*Plus」?

BTW: Please pay attention to the red font.

1. Re: Why it automatically recover current redo log in RMAN command window?

Lonion Aug 31, 2013 9:41 AM (in response to Lonion)

Why nobody answer?
Like Show 0 Likes(0)

Actions
2. Re: Why it automatically recover current redo log in RMAN command window?

Hemant K Chitale Sep 2, 2013 2:09 AM (in response to Lonion)

From the SQLPlus command line, the command is "RECOVER AUTOMATIC DATABASE"

Hemant K Chitale
Like Show 0 Likes(0)

Actions

3. Re: Why it automatically recover current redo log in RMAN command window?

Lonion Oct 25, 2013 2:09 AM (in response to Hemant K Chitale)

It also seems not work.

SQL> recover automatic database using backup controlfile;
ORA-00279: change 2148632889 generated at 09/26/2013 12:45:22 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_.
arc
ORA-00280: change 2148632889 for thread 1 is in sequence #48
ORA-00278: log file
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
.arc' no longer needed for this recovery
ORA-00308: cannot open archived log
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3




Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3




ORA-00308: cannot open archived log
'/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file









or directory
Additional information: 3




SQL>

It must specify the redo log.

SQL> recover database using backup controlfile;
ORA-00279: change 2148632889 generated at 09/26/2013 12:45:22 needed for thread
1
ORA-00289: suggestion :
/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_.
arc
ORA-00280: change 2148632889 for thread 1 is in sequence #48




Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/oradata/lonion/redo02.log 
Log applied.
Media recovery complete.
SQL>

4. Re: Why it automatically recover current redo log in RMAN command window?

Hemant K Chitale Oct 25, 2013 2:16 AM (in response to Lonion)

RECOVER AUTOMATIC can only prompt for expected *archive* logs. Not an online redo log that hasn't been archived. You've used an online redo log that hadn't been archived.

Hemant K Chitale
1 person found this helpful
Like Show 0 Likes(0)

Actions
5. Re: Why it automatically recover current redo log in RMAN command window?

Lonion Oct 25, 2013 2:20 AM (in response to Hemant K Chitale)

It means I should specify the online redo log by manual?
Like Show 0 Likes(0)

Actions
6. Re: Why it automatically recover current redo log in RMAN command window?

Hemant K Chitale Oct 25, 2013 2:31 AM (in response to Lonion)

Yes, if you are recovering to a point in time that is beyond the last archive log -- is in the online redo log -- you need to supply the online redo log.
RMAN, in your first example, automatically identifies that the recovery is a complete recovery (because you didn't specify any UNTIL clause) so it also applies the online redo log file. The SQL command does not have this "feature".

Hemant K Chitale
Like Show 0 Likes(0)

Actions
7. Re: Why it automatically recover current redo log in RMAN command window?

Lonion Oct 25, 2013 2:50 AM (in response to Hemant K Chitale)

> because you didn't specify any UNTIL clause
According this, if i specify UNTIL clause in RMAN, it also need specify the online redo log file at last?
Like Show 0 Likes(0)

Actions
8. Re: Why it automatically recover current redo log in RMAN command window?

Hemant K Chitale Oct 25, 2013 2:52 AM (in response to Lonion)

Your SET UNTIL might specify a time that is in an archivelog or in an online redo log. RMAN should be able to recover with the online redo log if the SET UNTIL is in an online redo log --- but I haven't tried this.

Hemant K Chitale
Like Show 0 Likes(0)

Actions
9. Re: Why it automatically recover current redo log in RMAN command window?

Lonion Oct 25, 2013 2:58 AM (in response to Hemant K Chitale)

Thank you for replying patiently.

Can you help me to answer this question?
How to choose scan ip for scan listener?
Like Show 0 Likes(0)

Actions

Go to original post

Join the world’s largest interactive community dedicated to Oracle technologies.