Recover database

[Roshan]

Hi Erman,
Oracle Database 12c
Red Hat Linux 7

I have restored a backup from tape. During recovery process, Oracle requires for archive sequence #170249812269

SQL> recover database using backup controlfile until cancel;
ORA-00279: change 170249812269 generated at 06/03/2017 00:10:37 needed for
thread 2
ORA-00289: suggestion : /archicom/ora12c/oradata/2_6943_938705669.dbf
ORA-00280: change 170249812269 for thread 2 is in sequence #6943


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

When I do list archivelog all on test, the range of sequnce is
178881238 to 170214901740
hence, I am unable restore log sequence 6943(change 170249812269)

on production, list archivelog all includes sequnce 6943

6943    1    8815    A 02-JUN-17
        Name: +DATA1/CBS/ARCHIVELOG/2017_06_02/thread_1_seq_8815.4470.945567961



Can you please advise how to proceed?

Regards,
Roshan

[Roshan]

RMAN> run{
2> ALLOCATE CHANNEL CH1 TYPE 'SBT_TAPE';
3> ALLOCATE CHANNEL CH2 TYPE 'SBT_TAPE';
4> ALLOCATE CHANNEL CH3 TYPE 'SBT_TAPE';
5> ALLOCATE CHANNEL CH4 TYPE 'SBT_TAPE';
6> ALLOCATE AUXILIARY CHANNEL CH5 TYPE 'SBT_TAPE';
7>
8> SEND 'NSR_ENV=(NSR_SERVER=rhis-nwdd-1202,NSR_CLIENT=10.210.228.7)';
9> restore archivelog from sequence 6943;
 }
using target database control file instead of recovery catalog
allocated channel: CH1
channel CH1: SID=244 device type=SBT_TAPE
channel CH1: NMDA Oracle v8.2.3

allocated channel: CH2
channel CH2: SID=362 device type=SBT_TAPE
channel CH2: NMDA Oracle v8.2.3

allocated channel: CH3
channel CH3: SID=392 device type=SBT_TAPE
channel CH3: NMDA Oracle v8.2.3

allocated channel: CH4
channel CH4: SID=422 device type=SBT_TAPE
channel CH4: NMDA Oracle v8.2.3

allocated channel: CH5
channel CH5: SID=452 device type=SBT_TAPE
channel CH5: NMDA Oracle v8.2.3

sent command to channel: CH1
sent command to channel: CH2
sent command to channel: CH3
sent command to channel: CH4
sent command to channel: CH5

Starting restore at 04-JUN-17

released channel: CH1
released channel: CH2
released channel: CH3
released channel: CH4
released channel: CH5
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/04/2017 01:14:34
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8891 and starting SCN of 170264455488 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8890 and starting SCN of 170263564290 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8889 and starting SCN of 170262297047 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8888 and starting SCN of 170260978075 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8887 and starting SCN of 170259591545 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8886 and starting SCN of 170258301534 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8885 and starting SCN of 170257259863 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8884 and starting SCN of 170256122051 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8883 and starting SCN of 170254968118 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8882 and starting SCN of 170253877142 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8881 and starting SCN of 170253114746 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8880 and starting SCN of 170252554984 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8879 and starting SCN of 170251986984 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8878 and starting SCN of 170251487165 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8877 and starting SCN of 170250964827 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8876 and starting SCN of 170250387045 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 8875 and starting SCN of 170249888987 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7472 and starting SCN of 178716126 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7471 and starting SCN of 178672486 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7470 and starting SCN of 178630417 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7469 and starting SCN of 178588934 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7468 and starting SCN of 178574875 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7467 and starting SCN of 178533130 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7466 and starting SCN of 178490380 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7465 and starting SCN of 178447956 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7464 and starting SCN of 178440391 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7463 and starting SCN of 178399707 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7462 and starting SCN of 178357321 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7461 and starting SCN of 178314610 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7460 and starting SCN of 178299242 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7459 and starting SCN of 178259843 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7458 and starting SCN of 178218165 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7457 and starting SCN of 178174821 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7456 and starting SCN of 178154221 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7455 and starting SCN of 178118684 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7454 and starting SCN of 178075810 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7453 and starting SCN of 178034182 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7452 and starting SCN of 178009430 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7451 and starting SCN of 177980412 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7450 and starting SCN of 177955380 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7449 and starting SCN of 177913631 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7448 and starting SCN of 177888932 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7447 and starting SCN of 177851994 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7446 and starting SCN of 177843772 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7445 and starting SCN of 177799904 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7444 and starting SCN of 177757036 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7443 and starting SCN of 177719991 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7442 and starting SCN of 177704459 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7441 and starting SCN of 177664853 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7440 and starting SCN of 177622893 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7439 and starting SCN of 177580509 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7438 and starting SCN of 177559604 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7437 and starting SCN of 177524327 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7436 and starting SCN of 177483352 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7435 and starting SCN of 177440841 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7434 and starting SCN of 177415077 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7433 and starting SCN of 177385456 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7432 and starting SCN of 177343203 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7431 and starting SCN of 177301678 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7430 and starting SCN of 177270399 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7429 and starting SCN of 177246737 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7428 and starting SCN of 177203279 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7427 and starting SCN of 177160914 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7426 and starting SCN of 177125566 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7425 and starting SCN of 177101883 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7424 and starting SCN of 177058821 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7423 and starting SCN of 177014806 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7422 and starting SCN of 176981001 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7421 and starting SCN of 176953790 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7420 and starting SCN of 176912240 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7419 and starting SCN of 176870462 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7418 and starting SCN of 176835265 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7417 and starting SCN of 176814341 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7416 and starting SCN of 176771366 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7415 and starting SCN of 176728637 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7414 and starting SCN of 176690564 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7413 and starting SCN of 176673081 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7412 and starting SCN of 176629431 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7411 and starting SCN of 176586363 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7410 and starting SCN of 176545900 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7409 and starting SCN of 176529916 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7408 and starting SCN of 176486608 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7407 and starting SCN of 176444533 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7406 and starting SCN of 176403841 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7405 and starting SCN of 176400874 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7404 and starting SCN of 176357353 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7403 and starting SCN of 176314882 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7402 and starting SCN of 176272963 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7401 and starting SCN of 176256713 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7400 and starting SCN of 176218159 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7399 and starting SCN of 176175720 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7398 and starting SCN of 176134831 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7397 and starting SCN of 176109828 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7396 and starting SCN of 176081268 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7395 and starting SCN of 176039350 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7394 and starting SCN of 175995945 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7393 and starting SCN of 175963853 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 7392 and starting SCN of 175940040 found to restore

[ErmanArslansOracleBlog]

Copy that archive from production to your clone site, and apply it during the recovery process (when it asks you , provide the necessary archivelog by giving its full name) This is the easiest way.

[Roshan]

Thanks. If production database creashes, how can I recover from the backup tape?

[ErmanArslansOracleBlog]

You will restore basically.
But, you need to have all the db backups and archivelogs available in your tapes.

For ex, In this case, I think you have actual archivelogs in disk, but you don't have backups of them stored anywhere.

[Roshan]

The backups are on tape.
listarchives.log

The archivelogs on production are on on ASM disk
ASMCMD> ls
2017_06_01/
2017_06_02/
2017_06_03/
2017_06_04/
2017_06_05/

Is there a way to copy the archivelogs to filesystem or test environment?
Please advise

[ErmanArslansOracleBlog]

For copying archivelogs from ASM to disk, you can use asmcmd utility.

Take a look: https://learnwithme11g.wordpress.com/2011/01/09/copying-files-from-asm-to-file-system/

[ErmanArslansOracleBlog]

As for your question (rman restore recovery using backups+archivelogs from tape)
Use  'set until sequence' clause to restore the required archive logs and recover the database.

Here is an example run:

run
{
allocate channel t1 type 'sbt_tape';
allocate channel t2 type 'sbt_tape';
allocate channel t3 type 'sbt_tape';
set until sequence 272151; ==> (Max sequence + 1)
recover database;
release channel t1;
release channel t2;
release channel t3;
}