RMAN > recover DB with backup controlfile > RMAN-06025: no backup of...

Oracle Database 10g Enterprise Edition Release 10.2.0.2.0
on RHEL 5

I am trying to execute the following commands to RMAN in a TEST instance and receive errors. I don't have the archive logs in the test OS instance (they were deleted manually... "I know it's a big mistake). Is there a way to always run 'restore database using backup controlfile until Cancel' successfully?

Step 1:

SQL > restore database using backup controlfile until cancel;
ORA-00279: change 40600690589 September at 2010-04-18 19:38:24 to
thread 1
ORA-00289: suggestion: /u001/dbsvr/deverp1/arch_575406629_1_122104.arc
ORA-00280: change 40600690589 thread 1 is in sequence #122104

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

Auto

ORA-00308: cannot open archived log
' / u001/dbsvr/deverp1/arch_575406629_1_122104.arc'
ORA-27037: unable to get file status
Linux-x86_64 error: 2: no such file or directory
Additional information: 3


ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
ORA-01194: file 1 needs a recovery more match
ORA-01110: data file 1: '+ DATA2/prod/datafile/system.291.716736657 '.


==========================================================
Step 2:

rman target $ /.
RMAN >
run
{
allocate channel d1 type disk;
define archivelog destination to ' / u001/dbsvr/deverp1 / ";
restore the logseq 122104 than logseq 122204 thread 1 all archivelog;
output channel d1;
}

allocated channel: d1
channel d1: sid = 1971 devtype = DISK

executing command: SET DESTINATION ARCHIVELOG

From restoration to April 19, 10

output channel: d1
RMAN-00571:
RMAN-00569:
= FOLLOWS THE ERROR MESSAGE BATTERY =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the restore command at 19/04/2010 19:45:29
RMAN-06026: some targets not found - abandonment of restoration
RMAN-06025: no thread 1 122116 lowscn found 40607234921 seq log backup to restore
RMAN-06025: no thread 1 122115 lowscn found 40606700559 seq log backup to restore

RMAN >

Published by: CipherDBA on April 19, 2010 18:43

I see you are using ASM. In this case, I strongly suggest forgetting all about giving orders for recovery of any kind in SQL * more and make sure that you have completely mastered RMAN. RMAN is the only reliable tool that can be used to do anything in ASM. In general, it is a very bad idea to mix managed by users and managed by RMAN recovery mechanisms: you ask just for confusion all round!

Also, I see someone suggesting 'Restoration until the 122114 seq archivelog', but it is false. If you run the syntax in this way, eventually you recovery until the end of the log 122113 and not enforce a 122114 again, that seems to exist. Numbers you put in an rman command "set until" are not exhaustive, so if you are missing journal 115, it's that you defined up to the number. You do not go around off delimbing a 1 or so just in case where, unless you plan to perform a recovery more incomplete than you can actually go out with.

Overall, the most appropriate RMAN recovery command in this case would be, I would say:

crosscheck archivelog all;
crosscheck backup;
run {
set until logseq 122115;
restore database;
recover database;}

More seriously: I have no idea why you are trying to recover with a bit of 'backup controlfile' in your syntax. It is only necessary if you have actually lost the original control file and have restored a backup. But since I don't see you do that ('Restore automatic backup controlfile' would be the usual thing to do with RMAN), then there is no need to specify that little bit of syntax in your orders. Now that you once asked Oracle to think he's working with a backup controlfile, however, all bets are off, so if I were you, in view of this is that a test system, I put things in a working state, and then start your recovery from scratch test. Just say 'using backup controlfile' If you actually are. If you simply mount the original controlfile that has not been lost by the disaster, so there no need to mention and the above commands should work properly.

Tags: Database

Similar Questions

  • RMAN-06025: no log backup archived for thread 1 with sequence - on double

    I tried to make a duplicate of a database, something I have done before, but this time I have run in to a problem.

    So, make a

    RMAN > list archivelog all;

    Shows that I have log sequence numbers 2600-2862 available.

    I have removed the expired archive logs and made an overlap and have issued the order on «alter system current archivelog» DB

    I did the pfile file and open the destination DB in nomount.

    The backup of the DB and the archivelogs seems to work fine without error.

    RMAN > backup as backupset = compressed database format ' / u04/tmpback/%u' tag "CLONE_TO_PPRD" include current controlfile;

    RMAN > backup as backupset archivelog Tablet all format = ' / u04/tmpback/al_%u' tag "CLONE_TO_PPRD_AL".

    Thus, with the environment on the destination DB (PPRD), opening a new rman to make the duplicate... "' rman target auxiliary sys@source_db /" "

    Then run the command

    target database duplicate to the PPRD until the SNA 2538794790;

    It seems to work fine, until this...

    Instance Oracle to close

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03002: failure of the command duplicate Db at 30/10/2014 14:46:22

    RMAN-05501: abandonment of duplicate target database

    RMAN-03015: an error has occurred in the script stored memory Script

    RMAN-06053: unable to perform the recovery of the media because of the missing journal

    RMAN-06025: no backup log archived for thread 1 with sequence 2599 and YVERT departure from 2500202517 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2598 and YVERT departure from 2500201335 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2597 and YVERT departure from 2500102904 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2596 and YVERT departure from 2499995595 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2595 and YVERT departure from 2499836289 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2594 and YVERT departure from 2499642775 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2593 and YVERT departure from 2499478641 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2592 and YVERT departure from 2499413468 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2591 and YVERT departure from 2499410632 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2590 and YVERT departure from 2499408867 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2589 and YVERT departure from 2499381186 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2588 and YVERT departure from 2499068021 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2587 and YVERT departure from 2498925555 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2586 and YVERT departure from 2498802786 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2585 and YVERT departure from 2498614939 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2584 and YVERT departure from 2498564861 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2583 and YVERT departure from 2498562153 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2582 and YVERT departure from 2498561088 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2581 and YVERT departure from 2498484636 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2580 and YVERT departure from 2498271487 found to restore

    RMAN-06025: no backup log archived for 1 with sequence 2579 threads and YVERT departure from 2498214991 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2578 and YVERT departure from 2498212309 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2577 and YVERT departure from 2498211201 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2576 and YVERT departure from 2498136750 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2575 and YVERT departure from 2498007880 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2574 and YVERT departure from 2497940390 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2573 and YVERT departure from 2497937659 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2572 and YVERT departure from 2497935694 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2571 and YVERT departure from 2497906173 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2570 and YVERT departure from 2497856983 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2569 and YVERT departure from 2497596547 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2568 and YVERT departure from 2497456509 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2567 and YVERT departure from 2497319931 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2566 and YVERT departure from 2497256972 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2565 and YVERT departure from 2497254201 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2564 and YVERT departure from 2497252909 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2563 and YVERT departure from 2497193527 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2562 and YVERT departure from 2496934735 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2561 and YVERT departure from 2496745593 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2560 and YVERT departure from 2496657121 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2559 and YVERT departure from 2496603411 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2558 and YVERT departure from 2496600720 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2557 and YVERT departure from 2496599649 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2556 and YVERT departure from 2496488543 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2555 and YVERT departure from 2495585865 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2554 and YVERT departure from 2495399778 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2553 and YVERT departure from 2495269888 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2552 and YVERT departure from 2495267113 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2551 and YVERT departure from 2495264943 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2550 and YVERT departure from 2495263264 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2549 and YVERT departure from 2495032426 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2548 and YVERT departure from 2494891192 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2547 and YVERT departure from 2494748475 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2546 and YVERT departure from 2494688135 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2545 and YVERT departure from 2494685342 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2544 and YVERT departure from 2494684167 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2543 and YVERT departure from 2494617350 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2542 and YVERT departure from 2494441823 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2541 and YVERT departure from 2494219188 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2540 and YVERT departure from 2494146694 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2539 and YVERT departure from 2494143651 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2538 and YVERT departure from 2494141374 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2537 and YVERT departure from 2494140316 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2536 and YVERT departure from 2494039070 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2535 and YVERT departure from 2493969002 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2534 and YVERT departure from 2493966234 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2533 and YVERT departure from 2493964141 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2532 and YVERT departure from 2493962603 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2531 and YVERT departure from 2493730362 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2530 and YVERT departure from 2493626024 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2529 and YVERT departure from 2493623327 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2528 and YVERT departure from 2493620995 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2527 and YVERT departure from 2493619424 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2526 and YVERT departure from 2493412146 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2525 and YVERT departure from 2493235154 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2524 and YVERT departure from 2493121677 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2523 and YVERT departure from 2493059844 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2522 and YVERT departure from 2493057083 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2521 and YVERT departure from 2493055871 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2520 and YVERT departure from 2492957915 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2519 and YVERT departure from 2492880955 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2518 and YVERT departure from 2492544076 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2517 and YVERT departure from 2492423758 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2516 and YVERT departure from 2492417400 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2515 and YVERT departure from 2492414719 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2514 and YVERT departure from 2492413908 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2513 and YVERT departure from 2492327128 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2512 and YVERT departure from 2492230125 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2511 and YVERT departure from 2491947217 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2510 and YVERT departure from 2491884830 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2509 and YVERT departure from 2491821845 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2508 and YVERT departure from 2491819116 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2507 and YVERT departure from 2491817468 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2506 and YVERT departure from 2491784652 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2505 and YVERT departure from 2491719981 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2504 and YVERT departure from 2487354643 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2503 and YVERT departure from 2487272304 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2502 and YVERT departure from 2487218716 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2501 and YVERT departure from 2487215968 found to restore

    RMAN-06025: no backup log archived for thread 1 with 2500 sequence and YVERT departure from 2487214915 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2499 and YVERT departure from 2487178867 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2498 and YVERT departure from 2475666929 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2497 and YVERT departure from 2475424798 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2496 and YVERT departure from 2475356185 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2495 and YVERT departure from 2475353406 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2494 and YVERT departure from 2475352071 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2493 and YVERT departure from 2475297238 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2492 and YVERT departure from 2475237220 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2491 and YVERT departure from 2475177867 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2490 and YVERT departure from 2475175065 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2489 and YVERT departure from 2475173911 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2488 and YVERT departure from 2475116250 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2487 and YVERT departure from 2475011369 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2486 and YVERT departure from 2474948383 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2485 and YVERT departure from 2474945180 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2484 and YVERT departure from 2474943701 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2483 and YVERT departure from 2474893025 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2482 and YVERT departure from 2474114073 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2481 and YVERT departure from 2473907191 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2480 and YVERT departure from 2473776113 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2479 and YVERT departure from 2473773241 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2478 and YVERT departure from 2473770145 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2477 and YVERT departure from 2473769454 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2476 and YVERT departure from 2473666106 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2475 and YVERT departure from 2473483998 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2474 and YVERT departure from 2473381579 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2473 and YVERT departure from 2473134334 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2472 and YVERT departure from 2473066760 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2471 and YVERT departure from 2473064023 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2470 and YVERT departure from 2473062119 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2469 and YVERT departure from 2473038503 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2468 and YVERT departure from 2472797901 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2467 and YVERT departure from 2472710532 found to restore

    RMAN-06025: no backup log archived for thread 1 with sequence 2466 and YVERT departure from 2472456854 found to restore

    RMAN-00567: Recovery Manager could not print error messages

    Why is it always get all these old newspapers archive? What should I do to get that continues. I'm sure miss me something small, but it is just eluding me.

    Thank you

    Rob

    Follow these steps:

    RMAN > crosscheck backup;

    RMAN > overlapping copy;

  • RMAN-06025 and double standby: no backup of the log 1 thread

    Hi all

    I use oracle 10.2.0.3.

    I tried to make a duplicate of standby restore/recovery
    from a band. The duplicate takes about 15 hours. So, upon arrival
    I got the following error:
    Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '+DATA/PROJ/datafile/system.346.764664523'

released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: ac1
released channel: ac2
released channel: ac3
released channel: ac4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/28/2011 01:19:11
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 35000 lowscn 74343144157 found to restore
.
.
.
    Well,.

    The duplicate database is restored. It remains only the archivelogs.
    If I try to backup all archivelogs again and to run the double once more,
    The data files already restored are underwritten, or RMAN ALL restart again, RESTORE
    ALL DATA FILES?
    The database has 600 GB. So, if I start again, it's a big problem.

    What can I do to fix this?

    Thank you very much!!!

    This is an Enterprise edition? Have you configured in Eve and dataguard on primary configuration?
    Which command you gave to duplicate?
    RMAN > target database duplicate for standby?

    then start MRP from sleep mode: -.
    SQL > recover database managed altert disonnect waiting database session;

    Main post office: -.
    Select the code from ds.dest_id
    ad.status
    ds.database_mode db_mode
    type ad.archiver
    ds.recovery_mode
    ds.protection_mode
    , ds.standby_logfile_count 'LAR '.
    Active ds.standby_logfile_active
    ds.archived_seq #.
    v $ archive_dest_status ds
    , announcement of v$ archive_dest
    where ds.dest_id = ad.dest_id
    and ad.status! = 'INACTIVE '.
    order by
    DS.dest_id
    /

    The duplicate database is restored. It remains only the archivelogs.
    If I try to backup all archivelogs again and to run the double once more,
    The data files already restored are underwritten, or RMAN ALL restart again, RESTORE
    ALL DATA FILES?
    The database has 600 GB. So, if I start again, it's a big problem.

    First thing is that you can make two copies because the database is already mounted...
    Why you want to restore again?

    Just start MRP and post if no errors.

  • Failed to retrieve RMAN-06025

    Hello world

    I'm trying to recover a DB in another server. I've recreated all the path and up to the instance. The restoration works ok, but to the next step, the recovery did not work.

    rman target $ [oracle@camerun RDBMS].

    Recovery Manager: Version 9.2.0.8.0 - 64 bit Production

    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

    Conectado has the database destination: CUBA (DBID = 2632031150)

    RMAN > restore database;

    Iniciando recover en 28/11 / 08
    to use el archivo of control of the database in lugar recuperacion catalogo del destino
    asignado channel: ORA_DISK_1
    channel ORA_DISK_1: sid = 12 devtype = DISK
    asignado channel: ORA_DISK_2
    channel ORA_DISK_2: sid = 13 devtype = DISK
    asignado channel: ORA_DISK_3
    channel ORA_DISK_3: sid = 14 devtype = DISK
    asignado channel: ORA_DISK_4
    channel ORA_DISK_4: sid = 15 devtype = DISK

    iniciando recuperacion del medio fisico

    Oracle error:
    ORA-01547: advertencia: RECOVERY ha funcionado pero OPEN RESETLOGS obtendria el siguiente error correctamente
    ORA-01152: el archivo 1 without is restauro una copia seguridad suficientemente antigua
    ORA-01110: data file 1: ' / opt/local/oradata/cuba/data/system01.dbf'

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the command recover to 2008-11-28 08:54:45
    RMAN-06053: unable to perform the recovery of the media because of the missing journal
    RMAN-06025: no backup log thread 1 seq 48528 SNA 39528195963 found to restore
    RMAN-06025: no backup log thread 1 seq 48527 SNA 39528118277 found to restore
    RMAN-06025: no backup log thread 1 seq 48526 SNA 39528026897 found to restore
    RMAN-06025: no backup log thread 1 seq 48525 SNA 39527934853 found to restore
    RMAN-06025: no backup log thread 1 seq 48524-SNA 39527833293 found to restore
    RMAN-06025: no backup log thread 1 seq 48523 SNA 39527485003 found to restore
    RMAN-06025: no backup log thread 1 seq 48522 SNA 39527365249 found to restore
    RMAN-06025: no backup log thread 1 seq 48521 SNA 39527239771 found to restore
    RMAN-06025: no backup log thread 1 seq 48520 SNA 39527104069 found to restore
    RMAN-06025: no backup log thread 1 seq 48519 SNA 39526956381 found to restore
    RMAN-06025: no backup log thread 1 seq 48518 SNA 39526802502 found to restore
    RMAN-06025: no backup log thread 1 seq 48517 SNA 39526652692 found to restore
    RMAN-06025: no backup log thread 1 seq 48516 SNA 39526499824 found to restore
    RMAN-06025: no backup log thread 1 seq 48515 SNA 39526345687 found to restore
    RMAN-06025: no backup log thread 1 seq 48514 SNA 39526083192 found to restore
    RMAN-06025: no backup log thread 1 seq 48513 SNA 39525875675 found to restore
    RMAN-06025: thread 1 48512 SNA 39525756447 seq log backup not found to restore
    RMAN-06025: no backup log thread 1 seq 48511 SNA 39525639439 found to restore
    RMAN-06025: no backup log thread 1 seq 48510 SNA 39525537393 found to restore
    RMAN-06025: no backup log thread 1 seq 48509 SNA 39525440309 found to restore
    RMAN-06025: no backup log thread 1 seq 48508 SNA 39524664364 found to restore
    RMAN-06025: no backup log thread 1 seq 48507 SNA 39524562622 found to restore
    RMAN-06025: no backup log thread 1 seq 48506 SNA 39524430331 found to restore
    RMAN-06025: no backup log thread 1 seq 48505 SNA 39524311583 found to restore
    RMAN-06025: thread 1 48504 SNA 39524166698 seq log backup not found to restore
    RMAN-06025: no backup log thread 1 seq 48503 SNA 39524007661 found to restore
    RMAN-06025: no backup log thread 1 seq 48502 SNA 39523834492 found to restore
    RMAN-06025: no backup log thread 1 seq 48501 SNA 39523683613 found to restore
    RMAN-06025: no backup log thread 1 seq 48500 SNA 39523547489 found to restore
    RMAN-06025: no backup log thread 1 seq 48499 SNA 39523319966 found to restore
    RMAN-06025: no backup log thread 1 seq 48498 SNA 39523205046 found to restore
    RMAN-06025: thread 1 48497 SNA 39523110696 seq log backup not found to restore
    RMAN-06025: no backup log thread 1 seq 48496 SNA 39523030945 found to restore
    RMAN-06025: no backup log thread 1 seq 48495 SNA 39522965895 found to restore
    RMAN-06025: no backup log thread 1 seq 48494 SNA 39522873879 found to restore
    RMAN-06025: no backup log thread 1 seq 48493 SNA 39521007844 found to restore
    RMAN-06025: no backup log thread 1 seq 48492 SNA 39518316231 found to restore
    RMAN-06025: no backup log thread 1 seq 48491 SNA 39515396088 found to restore
    RMAN-06025: no backup log thread 1 seq 48490 SNA 39511447459 found to restore
    RMAN-06025: no backup log thread 1 seq 48489 SNA 39506579160 found to restore
    RMAN-06025: no backup log thread 1 seq 48488 SNA 39501974065 found to restore
    RMAN-06025: no backup log thread 1 seq 48487 SNA 39496518957 found to restore
    RMAN-06025: no backup log thread 1 seq 48486 SNA 39491421982 found to restore
    RMAN-06025: no backup log thread 1 seq 48485 SNA 39491411352 found to restore
    RMAN-06025: no backup log thread 1 seq 48484 SNA 39491401321 found to restore
    RMAN-06025: log thread 1 48483 scn 39488446481 seq no backup found to restore
    RMAN-06025: no backup log thread 1 seq 48482 SNA 39486703268 found to restore
    RMAN-06025: no backup log thread 1 seq 48481 SNA 39483194776 found to restore
    RMAN-06025: no backup log thread 1 seq 48475 SNA 39478840463 found to restore
    RMAN-06025: no backup log thread 1 seq 48474 SNA 39478770864 found to restore
    RMAN-06025: no backup log thread 1 seq 48473 SNA 39478683063 found to restore
    RMAN-06025: no backup log thread 1 seq 48472 SNA 39478580306 found to restore
    RMAN-06025: no backup log thread 1 seq 48471 SNA 39478477376 found to restore
    RMAN-06025: no backup log thread 1 seq 48470 SNA 39478350803 found to restore
    RMAN-06025: no backup log thread 1 seq 48469 SNA 39477960776 found to restore
    RMAN-06025: no backup log thread 1 seq 48468 SNA 39477820952 found to restore
    RMAN-06025: no backup log thread 1 seq 48467 SNA 39477667627 found to restore
    MAN-06025: no backup of the log thread
    RMAN >

    Any idea?

    I checked the rman files and there is all. data files, control files and archive files.

    Cut and paste the restore script:

    #! / bin/bash

    If sqlplus "/ as sysdba" < <!
    the judgment
    output
    !

    RMAN target / nocatalog < <!
    startup nomount;
    the value of dbid 2632031150;
    Controlfile autobackup format of disc type of the device set to ' / backup/cuba/%F';
    Restore maxdays 100 autobackup controlfile;
    change the editing of the database;
    Run {}
    ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
    ALLOCATE CHANNEL c2 DEVICE TYPE DISK;
    ALLOCATE CHANNEL c3 DEVICE TYPE DISK;
    ALLOCATE CHANNEL c4 DEVICE TYPE DISK;
    restore the database;
    recover the database;
    }
    SQL 'alter database noarchivelog;
    ALTER database open resetlogs;
    !

    ERR = 0

    output $ERR


    Thank you very much!!
    Ricardo

    You have copied (backed up and restored) archivelog files outside of RMAN (that is to say that they were not in the RMAN backup set).

    When you use the commands to RESTORE DATABASES and RECOVER in RMAN, RMAN will only restore the database files and then to RETRIEVE, restore and apply ArchiveLogs that he is aware of. In your case, RMAN ignores the archivelogs.

    What you need to do is:
    a. use RMAN to RESTORE the DATABASE: you have already done and do not need to re-do
    b. use SQLPlus to the command to RECOVER the DATABASE:

        connect / as sysdba
    recover database using backup controlfile until cancel;

    This will require the archivelogs interactively. You can provide the archivelog file names and even the AUTOMATIC value for this to apply all archivelogs could find after you provided the first archivelog
    NOTE: If no archivelogs aren't in your copy of manual but in the backupset RMAN, you will need to use RMAN, ARCHIVELOG RESTORE... archivelogspecifiers
    c. After you apply the last archivelog available / necessary (IE until you need), in the SQLPlus session

         CANCEL

    d. If Oracle does NOT return an error when you CANCEL after the last archivelog, you HAVE a compatible database recovered at this point in time. IF it returns errors, it would mean that the backup of database time is always beyond the last archivelog that you applied and you must apply the archivelogs more (with another command RECOVER database using BACKUP CONTROLFILE until CANCEL).
    e. following the SQLPlus command prompt

        ALTER DATABASE OPEN RESETLOGS;

    f. after that, you need to add tempfiles to all temporary tablespaces in the database

        ALTER TABLESPACE TEMP ADD TEMPFILE 'path_to_tempfile' SIZE 1000M;

    other users would get errors that the tablespace temp is empty.

    Hemant K Collette
    http://hemantoracledba.blogspot.com

  • Issue of recovery RMAN-06025

    Hi all

    I did a full backup of a server.

    BACKUP INCREMENTAL LEVEL 0 DATABASE FORMAT would be: \Backup\ %n in %T (FullDayIncremental_base) %U. BKP ' TAG = "incr_level0" MORE ARCHIVELOG DELETE all THE ENTRIES.

    Restore everything without any problems on the remote server. I get an error at the time of the recovery:

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03002: fallo del comando recover en 03/02 / 2015 21:12:04

    RMAN-06053: no to ha could realize una recuperaci¾n del medio Fysico porque falta a log

    RMAN-06025: no to ha sown none copia seguridad del archive log para el wire 1 con the sequence 2

    66 y el dinna 29011076673 SNA para restore

    RMAN-06025: no to ha sown none copia seguridad del archive log para el wire 1 con the sequence 2

    65 y el dinna 29011074785 SNA para restore

    What it means?

    How can I solve this problem?

    Thank you!

    When you are able to open your database and access, it does mean that recovery is no longer necessary.

    You don't have to restore again or even get it back.

    As stated in my previous post, you face the RMAN error because the sequence of journal 266 was not at the time wherever you took the backup on the source database. Your database is recovered successfully until 265 sequence, open with resetlogs and access.

    If you think that your problem is resolved, if it please consider closing the thread marking it as useful or answered!

    Kind regards

    Shivananda

  • RMAN-06025 during replication

    Hello list,


    IAM trying to duplicate a database to a new host, it's my script

    ______________________________
    double-target database orcl pfile='D:\oracle\product\10.2.0\db_3\database\Clone\initorcl.ora'
    size of the logfile "D:\oracle10g\orcl\redo01.dbf" 50 m,
    *'D:\oracle10g\orcl\redo02.dbf"size 50 m, *.
    *'D:\oracle10g\orcl\redo03.dbf"size 50 m; *
    _________________________________

    I copied a backup of database to three days before the coated and the archivelogs generated since the last backup of both duplication to the new host.

    In vain the duplication during recovery to this statement:

    RMAN-06025: no s Log-Threads 1 seq 214 lowscn 2683354 restore backup not found
    RMAN-06025: Kein backup logs-Threads 1 seq 213 lowscn 2656377 zur found time.

    Here's my question: during duplication, rman sees only the archivelogs in backupup if iam replication to a remote host?
    and how I will duplicate the last archiving genrated log if I copied all archivelogs just before I start replication?, I don't want to take a new backup simply always use the last generated backup.

    Windows 2003 Server
    Database 10g SE.

    Thanks for your advice.

    Hey Walker,
    (Q)
    RMAN apply archive logs, even if they are not saved but copied to the remote host?
    It depends on the settings for the destination of the newspaper archive and archive log format side auxiliary if rman can apply to your archive logs.

    (I normally use rman to back up the archive logs and use the pieces to the auxiliary copy.) During the recovery phase of the cloning process files from archive get restored to the auxiliary archivelog dest and get the format as set out in the pfile (s) on the auxiliary)

    Kind regards
    Tycho

  • RECOVER, DATABASE using backup controlfile until the

    Hello
    in 10g R2, may this work:
    RECOVER DATABASE using backup controlfile until '2009-05-21:12:47:30';
    Thank you.

    GregX wrote:
    In fact, it should say something like this:

    until time ' to_date (May 19, 2009 10:30 "," dd-mm-yyyy hh24:mi:ss') ";

    No, you needn't.
    Doc http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/osrecov.htm#i1007361
    "+ If recovery up to one hour, the time is always specified using the following format, delimited by single quotes: 'YYYY-MM-' DD:HH24:MI:SS. '. + »

    Nicolas.

  • Error recovering hot cloning backup - 10 g

    Hello
    I use oracle 10g (10.2.0.1) with linux4
    I'm cloning a database with hot backup

    but I get an error when I run the

    RECOVER THE DATABASE BACKUP USING BACKUP CONTROLFILE UNTIL CANCEL.


    See my procedure:

    start of the db
    ALTER database begin backup
    take backup of the file redologs, data files and archiving of newspapers as well, spfile and pfile.
    ALTER database backup controlfile to trace.
    alter database end backup;
    -so far the hot backup is done.



    now, I copied the backup files to the new directory clone db structure. The structure just like any other db directory structure.

    Now, I created a new pfile from the existing database.
    start-up of the new db clone with the new pfile in phase nomount

    Now, I created the new control file.
    the control file is created successfully
    copy the backup control file to the udump directory in the new comic book of clone.

    Now, I want to apply new clone db archives.

    When I start the

    RECOVER THE DATABASE BACKUP USING BACKUP CONTROLFILE UNTIL CANCEL.

    I get a message saying that there is an inconsistency in the wire sequence



    Tried both possibilities such as specifying the redo logs and the location of the newspapers archives from the back to the top and the new clone system, but I can't solve it.

    can someone help me what to do

    Thanks in advance.

    Reference:-http://oracleinstance.blogspot.in/2009/05/backup.html

  • Satellite A300 Vista - will not start cd/DVD with backup

    Hello world

    I have a big problem with Toshiba a300. Windows Vista is not starts.

    Watch only the menu with 2 options: first "fix the system" - when I choose this option 10 seconds later I see messeage: click OK to turn off the computer.
    When I choose the second option in my laptop restart every time.

    I tried after turning on the computer, press F8, but all the option in this menu do NOT fix the problem.
    I have no CV/DVD to my computer.
    After the first time I don't burn DVD with backup.

    I have really now how can I install system with recovery patriction. What softwere I need and how do I do it?

    Thanks for help

    Hello

    Sat A300 and other new models of laptops are equipped with HARD drive recovery option. This HARD drive recovery should allow you to recover the laptop without the use of all disks.
    In order to start the procedure for HARD drive recovery, you need to press F8. Then choose the first option called fix my computer. Then new window pops up and there you have to choose Toshiba HDD recovery. All that s.

    But if this procedure don't work (no matter why) then you will need to use the Toshiba recovery disc. If you n t create a floppy disk for recovery of a hand and the laptop will not start, then you will have to buy a drive for recovery of this page:
    https://backupmedia.Toshiba.EU/landing.aspx

    Good bye

  • iPhone (with iOS9.1) initialize with backup using iOS9.1: incompatibility problem

    Hi guys.

    I bought an iphone 6s (mounting iOS 9.1) and tried to initialize with the iCloud backup made with my previous iphone 5 using iOS9.2.

    When I try to choose the back upward, I got a message saying "no backup is compatible with iOS 9.1 present on this phone.

    What can I do to solve the problem?

    Thank you

    A typo in in the subject...

    iPhone (with iOS9.1) initialize with backup using iOS9. 2: incompatibility problem

  • I save by mistake several times my C drive to the D drive and this resulted in my D drive is almost full with backups of 150 GB. How can I delete the backups of my D drive?

    I make mistake and have backed up all my C drive on my D drive contains and this resulted in my D drive is almost full with backups of 150 GB drive C. How can I clean all my backups of my D drive?

    Hi, Mr. flame.

    What is your operating system?

    If you have been creating full backups, the backup only that you keep is the last.

    Data backup file: offers the possibility to delete backups of data on the target files to free up space.

    Backup disk space management

    http://blogs.technet.com/b/filecab/archive/2009/11/23/managing-backup-disk-space.aspx

    You can also delete them using disk cleanup

    http://Windows.Microsoft.com/en-us/Windows7/delete-files-using-disk-cleanup

  • System Restore (with backup) for Windows XP how to restore the files from here?

    I saw the other posts for this but they have not answered the question. When I look in the C drive, and open the folder backup (backup C:\My--01/12/23 1134 AM), my photos, videos and documents are not available or are invisisble. When I tried to make hidden files visible, all my desktop icons and all the Start Menu program buttons disappear. I can see the files when I search with a software such as jdiskreport - 1.4.0, but I'm unable to move with this program. When I tried to move them with jdisk... they is locked in the tree of files of jdiskreport. Whenever these trees of missing or file icons has locked, I had to restore to the good previous restore point. In my view, the full restoration of the system (with backup) fails and should be avoided at all costs.

    So, if someone knows a way to access these files, I would appreciate the help of course. And please, no answers don't like "cannot not you just copy and paste?" because it is not currently a solution until the files are visible without erasing my desktop and the Start Menu.

    Hello

    Select the advanced restore options to restore the files. See the steps in the following article.

    http://www.Microsoft.com/resources/documentation/Windows/XP/all/proddocs/en-us/restore_overview.mspx?mfr=true

  • A backup made with "Backup And Restore" on xperia z2 cannot be downloaded to a synchronization service?

    I backed up my xperia messages, contacts and more... (checked eveything) in "Backup And Restore" application and I chose to go back to my sd card. Now, when I go to the command file and look for the back up, I can't find (the file is that contains all the data that I saved), also it is not present in my memory. The reason why I want to find is that I want to upload to syncing like Dropbox or Mega service, because it takes so much space on my sd card.

    I tried to find the backup also file to manage the files from the device to the computer, but it is not found, and if I browse the application backup and restore on my xperia, I see that I can restore the backup that I did.

    However, is it possible that I can download the backup that I did with backup and restore application on my xperia to a synchronization service?

    @uliwooly @Alam1998

    I have passed this:

    https://talk.sonymobile.com/T5/Xperia-Z5-Z5-compact-Z5-premium/online-backup/m-p/1082198#U1082198

    Maybe when I get information I can update this thread too.

    EDIT: The solution can be found in the link above.

  • BlackBerry Q10 maintains the factory restore setting whenever it restarts. It cannot be restored with backup files too.

    Can someone help me with this problem. His cannot be restored with backup files. each time it ends with the restoration with previous backup it went back to the factory setting. its so annoying. Help me.

    http://www.BlackBerry.com/BTSC/KB36747 found this in another thread. the problem with this software.

  • DVD how much we need for the files backup with backup and restore program?

    Hello how are you?
    DVD how much we need for the files backup with backup and restore program? Y at - it large differences in the time and space between write backups on DVD and external hard drive?

    I do not understand your question.  Asked how the space has been used on your C: drive and you answered 60 GB.  Now you say your PARTITION C: is 60 GB with only 20 GB used?  I really don't understand what you're so confused.  It's simple arithmetic grade 3rd.  What is space you USED on the C: drive, that multiply by 0.7 to obtain the amount of space will be used on your backup disk after compression.  Divide this number by 4.7 and round.  That's how many DVDs you'll need if you insist on the use of DVDs for backup.  Then

    (1) If you are using 60 GB, the answer is (60 x.7) / 4.7 = 8.936.  I rounded up to 9 and added 1 just to be sure.

    (2) If you use only 20 GB, the answer is (20 x.7) / 4.7 = 2.97 rounded up to 3.  Add 1 and get 4.

    If you use only 20 GB, I am very surprised, because almost any important installation of Windows 7 is going to take more than 20 GB.

    All of this assumes that you do NOT use the Windows backup and restore program, but one that I recommended.  When I used the windows one, the results were several times the space that I used on my C: partition.

    Good luck.

Maybe you are looking for

  • Can I transfer Thunderbird to earthlink to gmail?

    Will soon get Google Fiber and already have a new gmail address, which will become my only when Google Fiber is installed. I would like to keep Thunderbird as my mail server. Thank you.

  • I forgot password of icloud forever

    Salvation; I lost my password to iCloud and no way I am able to restore. Our country does not have Apple Bank. My iphone 5s can be used?

  • SImple pass does not load? Want to register Fingprints

    Yesterday, I decided to do a clean boot since my startup has been slow. Now, for some reason, I can't to my fingerprint reader, even if I downloaded again the file at hp support here and installed the program. Here is a picture of the screen: it keep

  • MSN error codes

    What is error 1225?

  • 2.4 GHz Wireless and the problem of USB 3.0 with WRT1900ACS

    Hi people I guess I discovered a new "buggy" feature on my new ultra buggy router. When I plug my WD mybook external hard drive usb 3.0 on the slot usb 3.0 on the Router 2.4 GHz and 2.4 GHz-comments off immediately. When I unplung the hard drive the