Recover failed RMAN-06025

Hi everybody,
I'm trying to recover a DB in other server. I recreated all the path and up the instance. The restore work ok, but in the next step the recovery didn't work.
[oracle@camerun rdbms]$ rman target /
Recovery Manager: Versión 9.2.0.8.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
conectado a la base de datos destino: CUBA (DBID=2632031150)
RMAN> recover database;
Iniciando recover en 28/11/08
se utiliza el archivo de control de la base de datos destino en lugar del catálogo de recuperación
canal asignado: ORA_DISK_1
canal ORA_DISK_1: sid=12 devtype=DISK
canal asignado: ORA_DISK_2
canal ORA_DISK_2: sid=13 devtype=DISK
canal asignado: ORA_DISK_3
canal ORA_DISK_3: sid=14 devtype=DISK
canal asignado: ORA_DISK_4
canal ORA_DISK_4: sid=15 devtype=DISK
iniciando la recuperación del medio físico
Error Oracle:
ORA-01547: advertencia: RECOVER ha funcionado correctamente pero OPEN RESETLOGS obtendría el siguiente error
ORA-01152: el archivo 1 no se restauró de una copia de seguridad suficientemente antigua
ORA-01110: archivo de datos 1: '/opt/local/oradata/cuba/data/system01.dbf'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/28/2008 08:54:45
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 48528 scn 39528195963 found to restore
RMAN-06025: no backup of log thread 1 seq 48527 scn 39528118277 found to restore
RMAN-06025: no backup of log thread 1 seq 48526 scn 39528026897 found to restore
RMAN-06025: no backup of log thread 1 seq 48525 scn 39527934853 found to restore
RMAN-06025: no backup of log thread 1 seq 48524 scn 39527833293 found to restore
RMAN-06025: no backup of log thread 1 seq 48523 scn 39527485003 found to restore
RMAN-06025: no backup of log thread 1 seq 48522 scn 39527365249 found to restore
RMAN-06025: no backup of log thread 1 seq 48521 scn 39527239771 found to restore
RMAN-06025: no backup of log thread 1 seq 48520 scn 39527104069 found to restore
RMAN-06025: no backup of log thread 1 seq 48519 scn 39526956381 found to restore
RMAN-06025: no backup of log thread 1 seq 48518 scn 39526802502 found to restore
RMAN-06025: no backup of log thread 1 seq 48517 scn 39526652692 found to restore
RMAN-06025: no backup of log thread 1 seq 48516 scn 39526499824 found to restore
RMAN-06025: no backup of log thread 1 seq 48515 scn 39526345687 found to restore
RMAN-06025: no backup of log thread 1 seq 48514 scn 39526083192 found to restore
RMAN-06025: no backup of log thread 1 seq 48513 scn 39525875675 found to restore
RMAN-06025: no backup of log thread 1 seq 48512 scn 39525756447 found to restore
RMAN-06025: no backup of log thread 1 seq 48511 scn 39525639439 found to restore
RMAN-06025: no backup of log thread 1 seq 48510 scn 39525537393 found to restore
RMAN-06025: no backup of log thread 1 seq 48509 scn 39525440309 found to restore
RMAN-06025: no backup of log thread 1 seq 48508 scn 39524664364 found to restore
RMAN-06025: no backup of log thread 1 seq 48507 scn 39524562622 found to restore
RMAN-06025: no backup of log thread 1 seq 48506 scn 39524430331 found to restore
RMAN-06025: no backup of log thread 1 seq 48505 scn 39524311583 found to restore
RMAN-06025: no backup of log thread 1 seq 48504 scn 39524166698 found to restore
RMAN-06025: no backup of log thread 1 seq 48503 scn 39524007661 found to restore
RMAN-06025: no backup of log thread 1 seq 48502 scn 39523834492 found to restore
RMAN-06025: no backup of log thread 1 seq 48501 scn 39523683613 found to restore
RMAN-06025: no backup of log thread 1 seq 48500 scn 39523547489 found to restore
RMAN-06025: no backup of log thread 1 seq 48499 scn 39523319966 found to restore
RMAN-06025: no backup of log thread 1 seq 48498 scn 39523205046 found to restore
RMAN-06025: no backup of log thread 1 seq 48497 scn 39523110696 found to restore
RMAN-06025: no backup of log thread 1 seq 48496 scn 39523030945 found to restore
RMAN-06025: no backup of log thread 1 seq 48495 scn 39522965895 found to restore
RMAN-06025: no backup of log thread 1 seq 48494 scn 39522873879 found to restore
RMAN-06025: no backup of log thread 1 seq 48493 scn 39521007844 found to restore
RMAN-06025: no backup of log thread 1 seq 48492 scn 39518316231 found to restore
RMAN-06025: no backup of log thread 1 seq 48491 scn 39515396088 found to restore
RMAN-06025: no backup of log thread 1 seq 48490 scn 39511447459 found to restore
RMAN-06025: no backup of log thread 1 seq 48489 scn 39506579160 found to restore
RMAN-06025: no backup of log thread 1 seq 48488 scn 39501974065 found to restore
RMAN-06025: no backup of log thread 1 seq 48487 scn 39496518957 found to restore
RMAN-06025: no backup of log thread 1 seq 48486 scn 39491421982 found to restore
RMAN-06025: no backup of log thread 1 seq 48485 scn 39491411352 found to restore
RMAN-06025: no backup of log thread 1 seq 48484 scn 39491401321 found to restore
RMAN-06025: no backup of log thread 1 seq 48483 scn 39488446481 found to restore
RMAN-06025: no backup of log thread 1 seq 48482 scn 39486703268 found to restore
RMAN-06025: no backup of log thread 1 seq 48481 scn 39483194776 found to restore
RMAN-06025: no backup of log thread 1 seq 48475 scn 39478840463 found to restore
RMAN-06025: no backup of log thread 1 seq 48474 scn 39478770864 found to restore
RMAN-06025: no backup of log thread 1 seq 48473 scn 39478683063 found to restore
RMAN-06025: no backup of log thread 1 seq 48472 scn 39478580306 found to restore
RMAN-06025: no backup of log thread 1 seq 48471 scn 39478477376 found to restore
RMAN-06025: no backup of log thread 1 seq 48470 scn 39478350803 found to restore
RMAN-06025: no backup of log thread 1 seq 48469 scn 39477960776 found to restore
RMAN-06025: no backup of log thread 1 seq 48468 scn 39477820952 found to restore
RMAN-06025: no backup of log thread 1 seq 48467 scn 39477667627 found to restore
MAN-06025: no backup of log thread
RMAN>
Some idea?
I checked the rman files and there are all; the datafiles, the control files, and the archives files.
Cut & Paste the restore script:
#!/bin/bash
sqlplus -s "/ as sysdba" <<!
shutdown abort
exit
rman target / nocatalog <<!
startup nomount;
set dbid 2632031150;
set controlfile autobackup format for device type disk to '/backup/cuba/%F';
restore controlfile from autobackup maxdays 100;
alter database mount;
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 database;
recover database;
sql 'alter database noarchivelog';
alter database open resetlogs;
ERR=0
exit $ERR
Thank you very much!!
Ricardo

Hi,
I do it, and the report don't give me information about the archives, the first five lines are about old rman control files.
RMAN> report obsolete;
se utiliza el archivo de control de la base de datos destino en lugar del catálogo de recuperación
la política de retención de RMAN se aplicará al comando
la política de retención de RMAN está definida en una redundancia 1
el archivo de control no es actual - la lista de archivos obsoletos puede estar incompleta
Informe de copias de seguridad y copias obsoletas
Tipo Clave Hora Finalización Nom.Archivo/Manejador
Juego de copias de seguridad 9770 18/11/08
Parte de copia de seguridad 13625 18/11/08 /backup/cuba/c-2632031150-20081118-00
Juego de copias de seguridad 9786 19/11/08
Parte de copia de seguridad 13641 19/11/08 /backup/cuba/c-2632031150-20081119-00
Juego de copias de seguridad 9802 20/11/08
Parte de copia de seguridad 13657 20/11/08 /backup/cuba/c-2632031150-20081120-00
Juego de copias de seguridad 9818 21/11/08
Parte de copia de seguridad 13673 21/11/08 /backup/cuba/c-2632031150-20081121-00
Juego de copias de seguridad 9834 22/11/08
Parte de copia de seguridad 13740 22/11/08 /backup/cuba/c-2632031150-20081122-00
Copia del Archivo de Control 2 30/11/06 /opt/local/app/oracle/cuba/product/9.2/dbs/stby_cuba.ctl
Copia del Archivo de Control 3 11/08/07 /opt/local/app/oracle/cuba/product/9.2/dbs/standby_cuba2.ctl
Copia del Archivo de Control 4 05/06/08 /opt/local/app/oracle/cuba/product/9.2/dbs/control_bck.ctl
Copia del Archivo de Control 8 28/07/08 /tmp/stby_cfile.ctl
Copia del Archivo de Control 9 29/07/08 /tmp/control01.ctl
Copia del Archivo de Control 10 23/09/08 /backup/cuba/stby_cfile.ctl
RMAN>
I check the physicall files, and all there are in the the correct place:
[root@camerun cuba]# cd /backup/cuba
[root@camerun cuba]# ls
c-2632031150-20081118-00 CUBA_9911_1_0 CUBA_9917_1_0 CUBA_9923_1_1 CUBA_9948_1_1
c-2632031150-20081119-00 CUBA_9911_2_0 CUBA_9917_2_0 CUBA_9924_1_1 CUBA_9949_1_1
c-2632031150-20081120-00 CUBA_9911_3_0 CUBA_9917_3_0 CUBA_9925_1_1 CUBA_9950_1_1
c-2632031150-20081121-00 CUBA_9911_4_0 CUBA_9917_4_0 CUBA_9926_1_1 CUBA_9951_1_1
c-2632031150-20081122-00 CUBA_9912_1_0 CUBA_9917_5_0 CUBA_9927_1_1 CUBA_9952_1_1
c-2632031150-20081123-00 CUBA_9912_2_0 CUBA_9918_1_0 CUBA_9928_1_1 CUBA_9953_1_A
CUBA_9907_1_0 CUBA_9912_3_0 CUBA_9918_2_0 CUBA_9929_1_1 CUBA_9956_1_1
CUBA_9907_2_0 CUBA_9912_4_0 CUBA_9918_3_0 CUBA_9930_1_1 CUBA_9957_1_1
CUBA_9907_3_0 CUBA_9913_1_0 CUBA_9918_4_0 CUBA_9931_1_1 CUBA_9958_1_1
CUBA_9907_4_0 CUBA_9913_2_0 CUBA_9918_5_0 CUBA_9932_1_1 CUBA_9959_1_1
CUBA_9908_1_0 CUBA_9913_3_0 CUBA_9918_6_0 CUBA_9933_1_1 CUBA_9960_1_1
CUBA_9908_2_0 CUBA_9913_4_0 CUBA_9918_7_0 CUBA_9934_1_1 CUBA_9961_1_1
CUBA_9908_3_0 CUBA_9914_1_0 CUBA_9918_8_0 CUBA_9935_1_1 CUBA_9962_1_1
CUBA_9908_4_0 CUBA_9914_2_0 CUBA_9918_9_0 CUBA_9936_1_1 CUBA_9963_1_1
CUBA_9908_5_0 CUBA_9914_3_0 CUBA_9919_1_0 CUBA_9937_1_A CUBA_9964_1_1
CUBA_9908_6_0 CUBA_9914_4_0 CUBA_9919_2_0 CUBA_9939_1_1 CUBA_9965_1_1
CUBA_9909_1_0 CUBA_9915_1_0 CUBA_9919_3_0 CUBA_9940_1_1 CUBA_9966_1_1
CUBA_9909_2_0 CUBA_9915_2_0 CUBA_9920_1_0 CUBA_9941_1_1 CUBA_9967_1_1
CUBA_9909_3_0 CUBA_9915_3_0 CUBA_9920_2_0 CUBA_9942_1_1 CUBA_9968_1_1
CUBA_9909_4_0 CUBA_9915_4_0 CUBA_9920_3_0 CUBA_9943_1_1 CUBA_9969_1_1
CUBA_9910_1_0 CUBA_9916_1_0 CUBA_9920_4_0 CUBA_9944_1_1 CUBA_9970_1_A
CUBA_9910_2_0 CUBA_9916_2_0 CUBA_9920_5_0 CUBA_9945_1_1 lost+found
CUBA_9910_3_0 CUBA_9916_3_0 CUBA_9920_6_0 CUBA_9946_1_1
CUBA_9910_4_0 CUBA_9916_4_0 CUBA_9921_1_A CUBA_9947_1_1
Archivers between the rman backup finish are in the files named CUBA_XXXX_X_A.
I'm checking the sequences of the archivers, and seems that rman is asking for old archivers.

Similar Messages

  • RMAN-06053 RMAN-06025 on Standby Database

    Dear community,
    we have an problem on our standby database (11.2.0.3 64Bit). We use the following RMAN script on the standby side:
    connect target *
    crosscheck archivelog all;
    crosscheck backup;
    delete noprompt expired archivelog all;
    delete noprompt expired backup;
    recover database;
    exit;In the alertlog of the standby database we found following:
    Thu Sep 20 12:05:33 2012
    alter database recover datafile list clear
    Completed: alter database recover datafile list clear
    alter database recover datafile list
    1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10 , 11 , 12 , 13 , 14 , 15 , 16 , 17 , 18 , 19 , 20
    Completed: alter database recover datafile list
    1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10 , 11 , 12 , 13 , 14 , 15 , 16 , 17 , 18 , 19 , 20
    alter database recover datafile list
    241 , 242 , 243 , 244 , 245 , 246 , 247 , 248 , 249 , 250 , 251 , 252 , 253 , 254
    Completed: alter database recover datafile list
    241 , 242 , 243 , 244 , 245 , 246 , 247 , 248 , 249 , 250 , 251 , 252 , 253 , 254
    alter database recover if needed
    start until cancel using backup controlfile
    Media Recovery Start
    started logmerger process
    Parallel Media Recovery started with 12 slaves
    ORA-279 signalled during: alter database recover if needed
    start until cancel using backup controlfile
    Thu Sep 20 12:05:58 2012
    alter database recover cancel
    Media Recovery Canceled
    Completed: alter database recover cancel In the RMAN Logfile will be logged:
    archived log for thread 2 with sequence 3693 is already on disk as file /u03/fast_recovery_area/DBDB/archivelog/2012_09_20/2_3693_766974880.dbf
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 09/20/2012 12:05:52
    RMAN-06053: unable to perform media recovery because of missing log
    RMAN-06025: no backup of archived log for thread 2 with sequence 2984 and starting SCN of 840244104 found to restore
    RMAN-06025: no backup of archived log for thread 2 with sequence 2983 and starting SCN of 840041348 found to restore
    RMAN-06025: no backup of archived log for thread 2 with sequence 2982 and starting SCN of 840021178 found to restore
    RMAN-06025: no backup of archived log for thread 2 with sequence 2981 and starting SCN of 839974659 found to restoreCan you please help me to understand why protocoll the database these RMAN-Errors and what is false configured?
    Best regards

    Do you mean the backup on the primary side was not been done?No. Backups created at primary site are not available to the standby of course, so that wont see them.
    The standby database is left behind and the required archivelogs for recovery are not available anymore, and it doesnt know anything about the backups.
    - you can restore the archivelogs on primary site from backups then let the standby fetch and apply them - can take a lot of time
    - you can make the backups made at primary site available to the standby and register the backup pieces - can be problematic with 3rd party backup solutions
    - you can create and incremental backup of primary site to roll forward the standby: http://docs.oracle.com/cd/E11882_01/server.112/e10700/rman.htm#CIHIAADC

  • Backup set in the tape. copied into disk. how to recover using RMAN

    I have backup set in the tape. copied into disk. how to recover using RMAN
    any link and steps please

    It should be something like the following, but really you should read and understand the rman documentation first ...
    1. restore the controlfile
    sqlplus / as sysdba
    startup nomount
    exit
    rman
    connect target /
    restore controlfile from '/path to the controlfile backup piece';
    exit
    sqlplus / as sysdba
    alter database mount
    exit
    2. catalog the backup pieces
    rman
    connect target /
    catalog start with '/path to backup pieces';
    3. restore the database
    rman
    connect target /
    restore database
    4. recover the database
    rman
    connect target /
    recover database
    5. open the database
    sqlplus / as sysdba
    alter database open resetlogs;

  • Cleaning up ASM disk group after failed rman duplicate session?

    I am using rman duplicate to create a clone of a production database. The rman duplicate failed in phase 1 (retoration of datafiles) and my datafile are being restored to an ASM diskgroup.
    I read in the metalink note Manual Completion of a Failed RMAN Duplicate [ID 360962.1] the following...
    Note : From 10g onwards, if duplicate failed during step 1, which is the restore of datafiles, it is probably best to restart the duplicate process. Any files that have already been restored will be skipped and the duplicate process can continue without manual intervention
    So I followed the advice in the note and started the rman duplcate script over again from the beggining. I am hoping it will have the intelligence to skip any files that have already been restored but if it is not since this is 10.1.0.3 and I cannot use the asmcmd command to connect to the ASM instance to delete any files that have been created then how can I delete and of the files since the database instance never got created correctly and cannot open?
    Any thought on how I can now cleanup the files in the ASM disk group? Also, has anyone started an rman duplicate again after it has previously failed and did it actually skip the files that are already there as stated in the metalink note?
    Thanks.

    Unfortunately the v$asm_file does not have the entire file name or path it just gives you the follwing...
    SQL> desc v$asm_file
    Name Null? Type
    GROUP_NUMBER NUMBER
    FILE_NUMBER NUMBER
    COMPOUND_INDEX NUMBER
    INCARNATION NUMBER
    BLOCK_SIZE NUMBER
    BLOCKS NUMBER
    BYTES NUMBER
    SPACE NUMBER
    TYPE VARCHAR2(64)
    REDUNDANCY VARCHAR2(6)
    STRIPED VARCHAR2(6)
    CREATION_DATE DATE
    MODIFICATION_DATE
    This really stinks I wish I didn't have to work with 10gr1 at all but the database I am trying to move to a ew server and new storage is running this version and we did not want to upgrade the existing database first before attempting the migration because it is reliant upon tape backups which I do not have alot of confidence in...

  • Failed RMAN Duplicate from NON-RAC to RAC-ASM

    Hi All!
    Is it possible to resume a failed RMAN Duplicate? Database is 10gR2.
    Please advice...
    Regards,
    cmadiam

    Once you fix the disk group name you can run the duplicatie, it should work fine.
    Please refer the link
    http://www.oracleracexpert.com/2009/10/migrate-database-to-asm-using-rman.html
    Hope this helps,
    Regards
    http://www.oracleracexpert.com
    Duplicate RAC DB using RMAN
    http://www.oracleracexpert.com/2009/12/duplicate-rac-database-using-rman.html

  • Logical Standby recover with RMAN

    Hi All,
    I have a test environment with Primary DB Server, Physical Standby and Logical Standby.
    The Logical Standby DB (cur_log_stdb) is backed up every evening by RMAN and I have a question:
    If I recover my Logical Standby DB from backup and switch replication to new Logical Standby DB (new_log_stdb) it will work or not?
    My steps e.g.:
    1. Make a new server for my new_log_stdb and repair structure of catalogs;
    2. Repair listener.ora and tnsnames.ora files from cur_log_stdb to new_log_stdb;
    3. Restore DB with RMAN from backup to new_log_stdb;
    4. On cur_log_stdb execute "alter database stop logical standby apply";
    5. Change a DNS name from cur_log_stdb to new_log_stdb;
    6. On new_log_stdb execute "alter database start logical standby apply immediate";
    I'm not sure that archivelogs will apply to the new_log_stdb for period since rman backup was created.
    But if this plan won't work how can I restore Logical Standby DB from RMAN backup and resume replication from Primary?
    Configuration:
    Oracle Linux 6.4
    Oracle Database 11.2.0.3
    Primary and Physical with Data Guard

    Hello;
    The only way to know for sure is to test it. You are asking somebody you don't know to confirm a recovery test for you. You have to perform the test yourself to be certain.
    If your plan does not work you can always rebuild the Standby.
    Best Regards
    mseberg

  • Resume a failed RMAN incremental 0 cold backup to disk

    Linux x86-64 10.2.0.4
    I'm taking an incremental 0 backup to disk of a database that's mounted. I'm backing up the database to an NFS volume. I lost the NFS mount. Is there any way to resume a backup where it left off at? It complains "ORA-27038: created file already exists" if I restart it. RMAN can easily resume a restore. I don't have the time to redo the whole thing all again. The database is over 10TB. The target isn't up. Is there anything I could do?

    Hemant K Chitale wrote:
    I lost the NFS mount point, as in it was no longer mounted to the host. If it was any other scenario, I wouldn't be attempting to resume it.and
    I still have the previously restored files. I wouldn't be recieving "ORA-27038: created file already exists" otherwise. I am still confused.
    I guess that you are talking of a BACKUP not a RESTORE (unlike the sentence that says "previously restored files").I meant backup. I'm also doing a restore for another purpose, so it was on my mind. It was some sort of phsychological slip.
    >
    "The NFS mount point is no longer mounted.". So what happened to the files that did get written to the NFS mount point ? Did you copy them to tape before the NFS mount point got unmounted ? Or is the NFS server still up and running, with the partial backup intact on it, except that the remote mount is disabled ?
    We had a network problem and we lost the NFS mount. Most of the files are there, just not the whole database. I didn't copy them to tape. The whole purpose was to use the backup as a clone by manually recreating the controlfle, and pulling it into another ASM instance on another cluster. We first need to pull it out of the current ASM instance. The NFS volume was remounted, but my concern is being able to resume the backup from where it left off at.
    How about running
    BACKUP ... NOT BACKED UP SINCE TIME 'date_string'From the documentation : "This option is a convenient way to back up files that were not backed up during a previous failed backup. For example, you back up the database, but the instance fails halfway through. You can restart the backup with the NOT BACKED UP SINCE TIME clause and avoid backing up those files that you already backed up."I'll have to give that a try. It sounds promising.
    >
    Hemant K Chitale
    http://hemantoracledba.blogspot.com

  • Database recover fail

    Hi Gurus
    When I was starting my database I found it failed and asked for media recovery , I did it despite that not able to recover
    My database oracle 10.2.0.3
    OS : AIX
    Error is as under :
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/oradata/pblprod/system01.dbf'
    SQL> recover datafile 1;
    ORA-00279: change 68423924625 generated at 03/09/2012 13:24:30 needed for thread 1
    ORA-00289: suggestion : /archivefs/pblprod/pblprod_arch_1_50365_687531539.arc
    ORA-00280: change 68423924625 for thread 1 is in sequence #50365
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /archivefs/pblprod/pblprod_arch_1_50365_687531539.arc
    ORA-00283: recovery session canceled due to errors
    ORA-00368: checksum error in redo log block
    ORA-00353: log corruption near block 9379976 change 68425552562 time 03/09/2012 16:02:25
    ORA-00334: archived log: '/archivefs/pblprod/pblprod_arch_1_50365_687531539.arc'
    ORA-01112: media recovery not started
    SQL>
    Regards
    Rabi

    Hi,
    What you want to show from the thread .... I didn't get ...
    >
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 368263168 bytes
    Fixed Size 1374668 bytes
    Variable Size 230688308 bytes
    Database Buffers 130023424 bytes
    Redo Buffers 6176768 bytes
    Database mounted.
    SQL> alter system switch logfile;
    alter system switch logfile
    ERROR at line 1:
    ORA-01109: database not open
    >
    --neeraj                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Issues trying to recover failed Exchange Server 2013 in a DAG

    Having several issues attempting to recover a failed Exchange Server 2013. To start out, the failed server was mounted on a virtual server using hyper-v. The virtual server failed due to some hard drive partition issues and would no longer boot. As there
    really was no purpose to having Exchange on a Virtual Server I decided to rename the host to the same name as the virtual server. I reset the name in AD and proceeded to rename the server. Then made sure all the necessary things were installed and proceeded
    to do a recovery installation. I neglected to properly delete the old databases belonging to that server. I simply deleted the files off the hard drive instead of doing it properly. I should mention this is a two node plus witness server installation.Now,
    it seems I cannot delete the former server in either ECP or command line. I have attempted to clean up the mess with the old databases but there is one that was mounted only on the failed server that I cannot remove. It seems until I can remove that, I cannot
    remove the failed server from the DAG and do a recovery install. The steps shown in the tech net articles to remove a failed database have also failed. At this point I am wondering if I should just give up on the server name and do an install on a new server
    name or if someone can give me some information on how to clean up the mess, that would be better I am sure. Here is a list of the things I have tried.
    https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx and in this article, the item mentioned is not in ADSIedit.
    http://exchangeserverpro.com/unable-remove-failed-server-dag-exchange-server-2010/
    http://exchangeserverpro.com/exchange-2013-how-to-remove-dag-member/ This
    article describes one of the problems I am having but the solution is not there.
    Thanks to any and all who can offer advice.
    Ronald C. Pope

    Thank you for your answer. Running that command results in the following:
    [PS] C:\Windows\system32>Remove-MailboxDatabase "Mailbox Database 0939719168"
    This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes or
    arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database"Mailbox Database 0939719168". To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of
    archive mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Archive. To get a list of all
    public folder mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -PublicFolder. To get a
    list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Arbitration.
    To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox
    <Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox
    <Mailbox ID> -Archive. To disable a public folder mailbox so that you can delete the mailbox database, run the command
    Disable-Mailbox <Mailbox ID> -PublicFolder. Arbitration mailboxes should be moved to another server; to do this, run
    the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command
    Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox.
    Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID>
    -Database "Mailbox Database 0939719168".
        + CategoryInfo          : InvalidOperation: (Mailbox Database 0939719168:DatabaseIdParameter) [Remove-MailboxDatab
       ase], AssociatedUserMailboxExistException
        + FullyQualifiedErrorId : [Server=EX01,RequestId=69b60793-fc4f-4dac-beb9-8c9afe381a36,TimeStamp=1/26/2015 6:28:34
       PM] 2BA41E0C,Microsoft.Exchange.Management.SystemConfigurationTasks.RemoveMailboxDatabase
        + PSComputerName        : ex01.<domain>com
    I was able to disable the one mailbox that was listed for the database. I got the following error when attempting the command Get-Mailbox -Database"Mailbox Database 0939719168"
    [PS] C:\Windows\system32>Get-MailboxPlan Database "Mailbox Database 0939719168"
    Get-MailboxPlan : The term 'Get-MailboxPlan' is not recognized as the name of a cmdlet, function, script file, or
    operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
    again.
    At line:1 char:1
    + Get-MailboxPlan Database "Mailbox Database 0939719168"
    + ~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (Get-MailboxPlan:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException
    the public folder and archive switch simply return a command prompt leading me to believe that there are no public or archive boxes on that database.
    Ron

  • How to recover the rman catalog

    all,
    I have created a recovery catalog and back it up using the control file and the nocatalog option - see below
    rman nocatclog target=rman
    run{
    backup database;
    backup (archivelog all delete input);
    How do I recover the catalog if it dies?
    rgds
    alan

    hi,
    thanks for the response. I will give it a try, but at a cistomer site doing this and they have no test server to try it on. Production only so need to be sure of what is going to happen.
    rgds
    alan

  • Database Recover Using RMAN

    Dear All(s)
    Recently i am managing oracle 10.2.0 database, and doing database coloning and data dumping. Also doing full backup trrough RMAN. Now i want to know what happend if i take only RMAN backup, full and incremental, and how recover it.
    1. How i can recover database if i loose entire server machine (in case i have only RMAN backup)
    2. How i can build full database using RMAN backup on another server.
    Thanks
    Waiting for response
    Edited by: Naeem Sheeraz on Dec 5, 2008 11:47 AM

    +1. How i can recover database if i loose entire server machine (in case i have only RMAN backup)+
    If you loose entire server machine its just like the same you make disaster recovery or restore database to another machine.
    +2. How i can build full database using RMAN backup on another server.+
    10g rman
    Khurram                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Step to Recover Failed Database Move

    Hi All,
      I'm trying to move the one production Database with some critical mailboxes to a new drive.
     How do i recover if the move failed in the middle or verse case scenario? what is the basic steps.
     This is a VM and backing using veeam software.
    AS

    Hi,
    You can restore mailbox database from backup, however, when restoring Exchange data, all backed up databases must be restored together. You can't restore a single database.
    To restore the individual database, you can refer to the workaround provided in the following article.
    You cannot restore an individual database by using Windows Server Backup in Exchange 2010 or in Exchange Server 2007
    http://support.microsoft.com/kb/2735099
    More information about restoring mailbox database for your reference.
    Exchange 2010 Mailbox Database Backup and Restore with Windows Server Backup
    http://exchangeserverpro.com/exchange-2010-mailbox-database-backup-restore-windows-server-backup/#restore
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Hope this helps.
    Best regard,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Recover with RMAN

    Hi Experts,
    I have a question
    i have a backup strategy with rman that create a data file copy and some backupset for other next days
    i can restore and recover my database until last exist ARCHIVE LOG without any problem.
    now i want to know how can i recover database again until last transaction in redo log if i had db redo log file???
    can rman recover from redo log until last transaction register in redolog??
    if yes how can i do this?
    Thanks
    Best Regards

    Hi,
    1) I think with 3 kind of backup file i have my DB until last transaction that save in online redolog file. is it true?
    suppose that we restore database from full backup.
    so we have a DB from time full backup time without transactions in archivelogs and redolog file.
    now we want recover database until last transaction.we can use two command for this goal:
    a. RECOVER DATABASE UNTIL SEQUENCE [last archivelog sequence# + 1];
    this command complete successfully and we can open database with resetlogs. but data is until last archive log so u don't have transaction in redolog file.
    b. RECOVER DATABASE;
    this command always complete with error that says sequence number [last archivelog sequence# + 1 ] not found.
    so we found out that this command only see archivelogs, not archivelogs and redolog files.
    and i don't know if we can open this database with resetlogs option.
    As mentioned by before poster, the redolog files are not backed up and there is needless to take a backup of the redolog and transfer it to the new server. n
    2) please tell me how can i introduce redologs to rman?  should i copy them in the same address with their address in control file??
    In the RMAN command you must archive the current redolog  file before backing up the archivelogs, which will ensure you will have a upto date  backup. Let me share one of my coding:
    RUN
    ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
    ALLOCATE CHANNEL RMAN_BACK_CH02 TYPE DISK;
    ALLOCATE CHANNEL RMAN_BACK_CH03 TYPE DISK;
    BACKUP
    AS BACKUPSET
    TAG 'FULL_DATABASE'
    FORMAT '/u01/backup/DBFILES_%F’;
    DATABASE
    SQL 'ALTER SYSTEM SWITCH LOGFILE';
    SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';
    RUN
    BACKUP
    AS BACKUPSET
    TAG 'ARCHIVELOGS_ALL'
    FORMAT '/u01/backup/ARCHIVELOGS_%F’
    DELETE INPUT;
    ARCHIVELOG ALL
    Hope this helps!
    Thanks &
    Best Regards,

  • Help on failing RMAN backup please.

    I have setup a nightly backup with the following script.
    run {
    allocate channel oem_backup_disk1 type disk format 'd:\mad3_nightly_backups\%U';
    backup incremental level 1 cumulative as BACKUPSET tag 'MAD3_CUMULATIVE_BA_040506080003' database include current controlfile;
    recover copy of database;
    backup as BACKUPSET tag 'MAD3_CUMULATIVE_BA_040506080003' archivelog all not backed up delete all input;
    report obsolete;
    crosscheck backup;
    crosscheck copy;
    report need backup;
    report unrecoverable;
    release channel oem_backup_disk1;
    But everytime I try to run this via OEM's nightly backup shedule, I get the error in the log below. But not able to identify what is causing the problem.
    My database is currently about 300GB.
    DB_RECOVERY_FILE_DEST_SIZE = 2GB
    FLASHBACK_ON = NO
    Shoud I try and increase the DB_RECOVERY_FILE_DEST_SIZE? If so to what? I would appriciate any help guys. Thanks.
    channel oem_backup_disk1: starting incremental level 1 datafile backupset
    channel oem_backup_disk1: specifying datafile(s) in backupset
    input datafile fno=00005 name=+MAD3ASM/mad3/datafile/madattrib.277.586366645
    .......SNIPED
    input datafile fno=00025 name=+MAD3ASM/mad3/datafile/mmdatalive.419.586257801
    input datafile fno=00027 name=+MAD3ASM/mad3/datafile/mmattrindexlive.421.586258381
    input datafile fno=00028 name=+MAD3ASM/mad3/datafile/mmattrindexlive.422.586258471
    input datafile fno=00026 name=+MAD3ASM/mad3/datafile/mmspindexlive.420.586258363
    input datafile fno=00029 name=+MAD3ASM/mad3/datafile/mmdataarchive.423.586258563
    input datafile fno=00030 name=+MAD3ASM/mad3/datafile/mmspindexarchive.424.586258581
    input datafile fno=00031 name=+MAD3ASM/mad3/datafile/mmattrindexarchive.425.586258599
    input datafile fno=00001 name=+MAD3ASM/mad3/datafile/system.256.583260945
    input datafile fno=00003 name=+MAD3ASM/mad3/datafile/sysaux.257.583260945
    input datafile fno=00002 name=+MAD3ASM/mad3/datafile/undotbs1.258.583260945
    input datafile fno=00004 name=+MAD3ASM/mad3/datafile/users.259.583260947
    channel oem_backup_disk1: starting piece 1 at 05-APR-06
    channel oem_backup_disk1: finished piece 1 at 05-APR-06
    piece handle=D:\MAD3_NIGHTLY_BACKUPS\3SHFPDMM_1_1 tag=MAD3_CUMULATIVE_BA_040506080003 comment=NONE
    channel oem_backup_disk1: backup set complete, elapsed time: 01:33:55
    channel oem_backup_disk1: starting incremental level 1 datafile backupset
    channel oem_backup_disk1: specifying datafile(s) in backupset
    including current control file in backupset
    including current SPFILE in backupset
    channel oem_backup_disk1: starting piece 1 at 05-APR-06
    channel oem_backup_disk1: finished piece 1 at 05-APR-06
    piece handle=D:\MAD3_NIGHTLY_BACKUPS\3THFPJ6P_1_1 tag=MAD3_CUMULATIVE_BA_040506080003 comment=NONE
    channel oem_backup_disk1: backup set complete, elapsed time: 00:00:04
    Finished backup at 05-APR-06
    Starting recover at 05-APR-06
    no copy of datafile 6 found to recover
    no copy of datafile 7 found to recover
    ....SNIPED (from 8 to 29)
    no copy of datafile 30 found to recover
    no copy of datafile 31 found to recover
    channel oem_backup_disk1: starting incremental datafile backupset restore
    channel oem_backup_disk1: specifying datafile copies to recover
    recovering datafile copy fno=00001 name=+MAD3ASM/mad3/datafile/system.392.586209619
    recovering datafile copy fno=00002 name=+MAD3ASM/mad3/datafile/undotbs1.395.586209667
    recovering datafile copy fno=00003 name=+MAD3ASM/mad3/datafile/sysaux.391.586209645
    recovering datafile copy fno=00004 name=+MAD3ASM/mad3/datafile/users.396.586209669
    recovering datafile copy fno=00005 name=+MAD3ASM/mad3/datafile/madattrib.768.586383235
    channel oem_backup_disk1: reading from backup piece D:\MAD3_NIGHTLY_BACKUPS\3SHFPDMM_1_1
    released channel: oem_backup_disk1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 04/05/2006 21:34:30
    ORA-19870: error reading backup piece D:\MAD3_NIGHTLY_BACKUPS\3SHFPDMM_1_1
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 13904117760 bytes disk space from 2147483648 limit
    exit;
    Recovery Manager complete.

    Take a look at this metalink note: 305812.1
    Flash Recovery area - Space management Warning & Alerts: https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=305812.1
    SELECT object_type, message_type, message_level, reason, suggested_action
    FROM dba_outstanding_alerts;
    The following actions can be done to resolve the space issue :
    - Add disk space to the Flash Recovery Area.
    - Back up your files to a tertiary device.
    - Delete the files from the Flash Recovery Area using RMAN.
    - Changing RMAN retention policy.
    Bye, Aron

  • XAResource.recover failed, with XAException

    when using jdbc 10.2.* to recover an appending transaction using xaresource interface, it's failed. but the jdbc10.1.* can work.
    how to solve this problem with jdbc 10.2.*

    when using jdbc 10.2.* to recover an appending transaction using xaresource interface, it's failed. but the jdbc10.1.* can work.
    how to solve this problem with jdbc 10.2.*

Maybe you are looking for

  • COST ELEMENTS IN ACCOUNT BASED COPA

    Hi all, 1. I understand that all FI/GL accounts correspond to COST   ELEMENTS in COPA. 2. I also understand that there are NO value fields in an Account Based Profitability Analysis.So there is no VALUE FIELD to KEY FIGURE mapping. 3. My question is:

  • Connecting with mysql database

    in order to place the component in the JFrame. we need to take the location (cooridinates values) of the component from the available mysql database. how to connect the database field values with our java program??? give me some suggestion pls.....

  • Why won't photoshop cc run portraiture 2

    why won't photoshop cc run portraiture 2?? Am I doing something wrong?

  • WRT54G2 with WAP54G

    Hi all, I have a wrt54g2 router downstairs which has ps3 xbox 360 and pc connected via ethernet. I am wanting to move the ps3, 360 and PC upstairs to another room. My plan was to purchase a WAP54G place in the upstairs room and put it into repeater m

  • Background job RDDIMPDP is not scheduled. Please run report RDDNEWPP.

    Dear Guru's,                  I am having a problem during transportation. i am not able to transport to quality system.And the tp system logs shows following error messages:- WARNING: System GNQ. Warning.        20071105123442 : ERROR:       Backgro