RMAN - Backups are failing *URGENT*

Hi,
I have a 2 10g DB (CM and ODSPROD) on HP-UX B.11.23 and both are on the same box and I have configured different script for individual DB on that BOX
till yesterday the backups were working fine but today it errored as follows:
run
allocate channel c1 type 'SBT_TAPE';
send 'NB_ORA_POLICY=ODSPROD1_RMAN,NB_ORA_SERV=QUEBACKUP';
backup database format 'backup_of_%d_%s_%D_%M_%Y' plus archivelog format 'arch_of_%d_%s_%D_%M_%Y';
restore validate database;
++++++++++++++++++++++++++++++
run
allocate channel c1 type 'SBT_TAPE';
send 'NB_ORA_POLICY=ODSPROD1_RMAN,NB_ORA_SERV=QUEBACKUP';
backup database format 'backup_of_%d_%s_%D_%M_%Y' plus archivelog format 'arch_of_%d_%s_%D_%M_%Y';
restore validate database;
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 04/21/2009 22:24:17
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 04/21/2009 22:52:14
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog
Let me know if you require any info in this regards.

as others have said this is a netbackup media manager error. To be honest though the most likely cause is a bad tape. I still prefer if you've got the space, and I'd hazard a guess that you have since you are backing up the database and archivelogs all in one go by the looks of it, to backup to disk and then let the tape backup pickup the backupsets
Niall

Similar Messages

  • Database backups are failing

    Hello Experts,
    Database backups are failing due to compatibility issue, The target database version is 10.2.0.1., therefore the RMAN version is running on 10.2.0.4.0, i have no idea how that was happened and who has did that before, now i have to take of this issue .. could you please give me suggestions on how to bring RMANback to 10.2.0.1 version.

    Hello Marcus,
    Thank you for the update..
    here is the output of RMAN
    =====================================================
    Recovery Manager: Release 10.2.0.4.0 - Production on Mon Jun 3 09:19:38 2013
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    RMAN> connect target *
    2> run {
    3> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
    4> CONFIGURE CONTROLFILE AUTOBACKUP ON;
    5> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'E:\Oracle\testdb\backup\cf_%d_%F';
    6> CONFIGURE BACKUP OPTIMIZATION ON;
    7> CONFIGURE DEVICE TYPE disk PARALLELISM 3;
    8> CONFIGURE DEFAULT DEVICE TYPE TO disk;
    9> CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT 'E:\Oracle\testdb\backup\b_%d_%U';
    10> CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT 'E:\Oracle\testdb\backup\b_%d_%U';
    11> CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT 'E:\Oracle\testdb\backup\b_%d_%U';
    12>
    13> BACKUP DATABASE PLUS ARCHIVELOG DELETE INPUT;
    14> }
    15>
    16> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK;
    17> CROSSCHECK BACKUP;
    18> DELETE NOPROMPT EXPIRED BACKUP;
    19> DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK;
    20> CROSSCHECK ARCHIVELOG ALL;
    21> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
    22> DELETE FORCE NOPROMPT OBSOLETE;
    23>
    PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
    PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
    connected to target database: TEST(DBID=123412352)
    using target database control file instead of recovery catalog
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of configure command at 06/03/2013 09:19:41
    ORA-06550: line 1, column 2273:
    PLS-00302: component 'GETRANGEALBACKUP' must be declared
    ORA-06550: line 1, column 2238:
    PL/SQL: Statement ignored
    ORA-06550: line 1, column 2453:
    PLS-00302: component 'RESTORECMD_T' must be declared
    ORA-06550: line 1, column 2424:
    PL/SQL: Statement ignored
    Recovery Manager complete.

  • Hot Backups are Failing

    I am running Oracle 7.3.4.4 on Compaq Tru64 and Digital Unix 4.0F. Our hot backups are failing with the following errors:
    1)from $OBK_HOME/bin/backup_PROD.log
    EBU-3135: SQL error during:
    select state from obk_bfs where bfsid = :objid and jobid = :jobid
    with error:
    ORA-03113: end-of-file on communication channel
    on 20-AUG-02 01:59 [ 29701 : brsupiopn ]
    EBU-3135: SQL error during:
    select state from obk_bfs where bfsid = :objid and jobid = :jobid
    with error:
    ORA-01041: internal error. hostdef extension doesn't exist
    on 20-AUG-02 01:59 [ 29701 : brsupiclo ]
    2)from brd.log:
    Instance Manager (BRD) with pid=32158 successfully started on 20-AUG-02 00:59
    EBU-3135: SQL error during:
    /* Obtain all jobs that are currently running s[0] */ ...
    with error:
    ORA-03113: end-of-file on communication channel
    on 20-AUG-02 01:59 [ 32158 : brsupiopn ]
    EBU-3108: Query error reported from Catalog Database
    on 20-AUG-02 01:59 [ 32158 : brdlookjobs ]
    EBU-1504: Error while retrieving active jobs from Catalog Database
    on 20-AUG-02 01:59 [ 32158 : brdlookjobs ]
    We are running Oracle7 Enterprise Backup Utility: Release 2.2.0.6.0. I have tried to reboot both target and catalog databases and machines and still no luck. Anybody have any ideas as to what may be wrong?
    Thanks,
    Bea Cary
    Database Administrator

    I am running Oracle 7.3.4.4 on Compaq Tru64 and Digital Unix 4.0F. Our hot backups are failing with the following errors:
    1)from $OBK_HOME/bin/backup_PROD.log
    EBU-3135: SQL error during:
    select state from obk_bfs where bfsid = :objid and jobid = :jobid
    with error:
    ORA-03113: end-of-file on communication channel
    on 20-AUG-02 01:59 [ 29701 : brsupiopn ]
    EBU-3135: SQL error during:
    select state from obk_bfs where bfsid = :objid and jobid = :jobid
    with error:
    ORA-01041: internal error. hostdef extension doesn't exist
    on 20-AUG-02 01:59 [ 29701 : brsupiclo ]
    2)from brd.log:
    Instance Manager (BRD) with pid=32158 successfully started on 20-AUG-02 00:59
    EBU-3135: SQL error during:
    /* Obtain all jobs that are currently running s[0] */ ...
    with error:
    ORA-03113: end-of-file on communication channel
    on 20-AUG-02 01:59 [ 32158 : brsupiopn ]
    EBU-3108: Query error reported from Catalog Database
    on 20-AUG-02 01:59 [ 32158 : brdlookjobs ]
    EBU-1504: Error while retrieving active jobs from Catalog Database
    on 20-AUG-02 01:59 [ 32158 : brdlookjobs ]
    We are running Oracle7 Enterprise Backup Utility: Release 2.2.0.6.0. I have tried to reboot both target and catalog databases and machines and still no luck. Anybody have any ideas as to what may be wrong?
    Thanks,
    Bea Cary
    Database Administrator

  • Since upgrading to Lion, my time machine backups are failing - error message: The backup disk image "/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska's MacBook.sparsebundle" could not be accessed (error -1). Any ideas?

    Since upgrading my Macbook to Lion, the time machine backups are failing - error message: "The backup disk image “/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska’s MacBook.sparsebundle” could not be accessed (error -1)."  I have rebooted the TIme Capsule and it worked OK, but don't want to do that every time.  Any suggestions?  Thanks

    Any new info on this? 
    I had the exact same problem and went crazy and spent a hecka lot of time trying to deal with my brand new 2TB Time Capsule and almost brand new MacBook Pro.  Then I thought I fixed it...and I tried SO MANY things, I don't really know what did it...except taking out any apostrophe's in names of stuff that Apple puts in there...BUT...now it's back.
    Grrr...

  • As my computer is telling me my backups are failing why is this happening and what do I do?

    What do I do when my computer tells me that my backups are failing and why is this happeneing?

    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    The title of the Console window should be All Messages. If it isn't, select
    SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
    View ▹ Show Log List
    from the menu bar at the top of the screen.
    In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the word "Starting" (without the quotes.) You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard."
    Each message in the log begins with the date and time when it was entered. Note the timestamp of the last "Starting" message that corresponds to the beginning of an an abnormal backup. Now
    CLEAR THE WORD "Starting" FROM THE TEXT FIELD
    so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressingcommand-V.
    ☞ If all you see are messages that contain the word "Starting," you didn't clear the text field.
    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    ☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. Don't post more than is requested.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    ☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Dpm 2010 exchange 2010 backups are failing

    Hi, I'm getting an error which does not seem to match in the DPM 2010 ID codes. Randomly, I have backups of an exchange 2010 DAG that are failing. The backup will run for a short time (5mints..up to 10minuts) and then will fail with the following error:
    Type: Recovery point
    Status: Failed
    Description: Backup failed as another copy of 'user' database is currently being backed up. (ID 32628 Details: Internal error code: 0x80990D51)
     More information
    End time: 4/25/2011 10:37:27 PM
    Start time: 4/25/2011 10:26:55 PM
    Time elapsed: 00:10:31
    Data transferred: 0 MB
    Cluster node -
    Recovery Point Type Incremental Sync
    Source details: 06001
    Protection group: EXCH2010 - 06001
    I've tried restarting the DPM server to troubleshoot. I say this happens randomly because I've had some backups successfully complete against the same exchange server. The only other item that seems odd is when creating protection groups against the DAG,
    the intial lookup seems to take forever. Not sure what to try next. 

    Hello,
    As DPM relies on the exchange writer to take the snapshot for the backup, if the backupinprogress flag is set to true and it does not seem get out of this state even when there is no actual backup in place, then at this point DPM is the victim.
    As far as I am aware the only way is to clear that flag is to:
    a.) Reboot the exchange server
    or
    b.) Restart the information store
    In some cases even:
    1.) Either Activate all other databases on another Node except for the Problem Database, and Dismount the Problem database temporarily
    Or:
    1.)Dismount all Databases on this Node including the problem database
    2.)Restart the Exchange Information Store Service.
    3.)Mount any dismounted databases
    You may want to redirect this question below to the exchange 2010 forum of:
    "if the backupinprogress is set to true when it should be set to false as there really is no backup being taken, then how can I reset it without having to perform:
    a.) reboot of exchange
    b.) restart of the information store"
    http://social.technet.microsoft.com/Forums/en-US/exchange2010/threads
    Regards, Shane. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. This posting
    is provided "AS IS" with no warranties, and confers no rights.

  • RMAN Backup job fails after changing sys, system passwords

    Hello Oracle community,
    11.1g
    After we changed the passwords for sys, system and sysman the backup jobs fails. this is my error log:
    Recovery Manager: Release 11.1.0.7.0 - Production on Mo Aug 30 11:16:29 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    RMAN>
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    ORA-12532: TNS: Ungültiges Argument
    RMAN>
    Echo einstellen ein
    RMAN> set command id to 'BACKUP_MEGALON.INT_083010111617';
    Befehl wird ausgeführt: SET COMMAND ID
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: Fehler bei set Befehl auf 08/30/2010 11:16:29
    RMAN-06171: Nicht bei Zieldatenbank angemeldet
    RMAN> backup device type disk tag 'BACKUP_MEGALON.INT_083010111617' database;
    Starten backup um 30.08.10
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: Fehler bei backup Befehl auf 08/30/2010 11:16:29
    RMAN-06171: Nicht bei Zieldatenbank angemeldet
    RMAN> backup device type disk tag 'BACKUP_MEGALON.INT_083010111617' archivelog all not backed up;
    Starten backup um 30.08.10
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: Fehler bei backup Befehl auf 08/30/2010 11:16:29
    RMAN-06171: Nicht bei Zieldatenbank angemeldet
    RMAN> exit;
    Recovery Manager abgeschlossen.
    Ikrischer

    Hello Tychos,
    I am able to make a sqlplus connection, but your hint send me in the correct direction. I had a special character "@" in the password and I think that was the reason for my problems with RMAN.
    Ikrischer

  • Backups are failing.

    Hi Gurus,
    We are taking the backup of Essbase application files like .tct, .pag, .ind, .esm, .db. .dbb files, we are facing some issue with the backups from last few days like .esm, .tct, .pag and .ind files are failing while exporting them using windows NT batch. With an error message as these files are used by some other process. where as i am checking in applicaion event logs i found no process are running at that time..
    please let me know what are the process(like dataloading, running calculations) will restrict these files to export.
    Thanks in advance.

    Look ty my MAXL BAckup script (for example )
    msh $vWorkDir/ess/_login.mxl ;
    spool off ;
    shell  mkdir $vBackupFolder ;
    shell  mkdir $vBackupFolder/$vCurrApp ;
    shell  mkdir $vBackupFolder/bin ;
    spool on to  "$vBackupFolder/$vLogFileName.$vCurrApp.mxl" ;
    set vDbFolder = $ARBORPATH/app/$vCurrApp/$vCurrDB ;
    set vBinFolder = $ARBORPATH/bin  ;
    iferror 'ExitError';
    /* Unload Level 0 data  */
    alter database $vCurrBackAppDB enable cache_pinning;
    iferror 'ExitError';
    alter system logout session on application $vCurrApp force ;
    alter system logout session on application $vCurrApp force ;
    alter system logout session on application $vCurrApp force ;
    iferror 'ExitError';
    alter application $vCurrApp enable startup  ;
    iferror 'ExitError';
    alter application $vCurrApp enable commands ;
    iferror 'ExitError';
    alter application $vCurrApp enable updates  ;
    iferror 'ExitError';
    alter application $vCurrApp enable connects ;
    iferror 'ExitError';
    alter application $vCurrApp enable security ;
    iferror 'ExitError';
    alter system load application $vCurrApp ;
    iferror 'ExitError';
    alter application  $vCurrApp load database $vCurrDB ;
    iferror 'ExitError';
    alter system logout session on application $vCurrApp force ;
    alter system logout session on application $vCurrApp force ;
    iferror 'ExitError';
    export database $vCurrBackAppDB all data to data_file "$vBackupFolder/$vCurrApp.$vJobNumber.all.txt" ;
    iferror 'ExitError';
    export database $vCurrBackAppDB level0 data to data_file "$vBackupFolder/$vDb.level0.txt" ;
    export database $vCurrBackAppDB input data to data_file "$vBackupFolder/$vDb.input.txt" ;
    /* ShutDown Applications */
    drop lock on system all ;
    iferror 'ExitError';
    alter application $vCurrApp disable startup ;
    iferror 'ExitError';
    alter application $vCurrApp disable commands ;
    iferror 'ExitError';
    alter application $vCurrApp disable updates ;
    iferror 'ExitError';
    alter application $vCurrApp disable connects ;
    iferror 'ExitError';
    alter application $vCurrApp disable security ;
    iferror 'ExitError';
    alter database $vCurrBackAppDB unlock all objects ;
    iferror 'ExitError';
    alter system logout session on application $vCurrApp force ;
    iferror 'ExitError';
    alter application  $vCurrApp unload database $vCurrDB ;
    iferror 'ExitError';
    alter system unload application $vCurrApp ;
    iferror 'ExitError';
    /* copy system binary files */
    shell cp $vBinFolder/\*.sec $vBackupFolder/bin 1>/dev/null  2>/dev/null ;
    shell cp $vBinFolder/\*.cfg $vBackupFolder/bin 1>/dev/null  2>/dev/null ;
    shell cp $vBinFolder/\*.sh  $vBackupFolder/bin 1>/dev/null  2>/dev/null ;
    shell cp $vBinFolder/\*.ini $vBackupFolder/bin 1>/dev/null  2>/dev/null ;
    /* copy applications binary files */
    shell cp $vDbFolder/\*.otl  $vBackupFolder/$vDb 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/\*.rul  $vBackupFolder/$vDb 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/\*.txt  $vBackupFolder/$vDb 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/\*.csc  $vBackupFolder/$vDb 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/\*.db   $vBackupFolder/$vDb 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/\*.dbb  $vBackupFolder/$vDb 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/\*.ind  $vBackupFolder/$vDb 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/\*.pag  $vBackupFolder/$vDb 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/\*.esm  $vBackupFolder/$vDb 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/\*.tct  $vBackupFolder/$vDb 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/../\*.app  $vBackupFolder/ 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/../\*.apb  $vBackupFolder/ 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/../\*.xml  $vBackupFolder/ 1>/dev/null  2>/dev/null ;
    shell cp $vDbFolder/../\*.jar  $vBackupFolder/ 1>/dev/null  2>/dev/null ;
    shell mkdir $vBackupFolder/scripts ;
    shell cp  $vWorkDir/\*  $vBackupFolder/scripts/ 1>/dev/null  2>/dev/null ;
    shell mkdir $vBackupFolder/scripts/ess ;
    shell cp -r  $vWorkDir/ess/\*  $vBackupFolder/scripts/ess 1>/dev/null  2>/dev/null ;
    /* Deleted tempory files */
    shell rm -f $vDbFolder/\*.otn ;
    shell rm -f $vDbFolder/\*.inn ;
    shell rm -f $vDbFolder/\*.esn ;
    shell rm -f $vDbFolder/\*.pan ;
    shell rm -f $vDbFolder/\*.tcu ;
    shell rm -f $vDbFolder/\*.esn ;
    shell rm -f $vDbFolder/\*.pan ;
    shell rm -f $vDbFolder/\*.inn ;
    shell rm -f $vDbFolder/\*.tcu ;
    shell rm -f $vDbFolder/\*.otn ;
    /* RESTRUCTURE  applications  */
    alter database $vCurrBackAppDB enable cache_pinning;
    iferror 'ExitError';
    alter application $vCurrApp enable startup;
    iferror 'ExitError';
    alter application $vCurrApp enable commands;
    iferror 'ExitError';
    alter application $vCurrApp enable updates;
    iferror 'ExitError';
    alter application $vCurrApp enable connects;
    iferror 'ExitError';
    alter application $vCurrApp enable security;
    iferror 'ExitError';
    alter system load application $vCurrApp ;
    iferror 'ExitError';
    alter application  $vCurrApp load database $vCurrDB ;
    iferror 'ExitError';
    alter database $vCurrBackAppDB force restructure ;
    iferror 'ExitError';
    define label 'ExitError';
    /* Start applications  */
    alter database $vCurrBackAppDB enable cache_pinning;
    alter application $vCurrApp enable startup;
    alter application $vCurrApp enable commands;
    alter application $vCurrApp enable updates;
    alter application $vCurrApp enable connects;
    alter application $vCurrApp enable security;
    alter system load application $vCurrApp ;
    alter application  $vCurrApp load database $vCurrDB ;
    logout;
    /* Create Archives  */
    shell cp "$vBackupFolder/$vLogFileName.$vCurrApp.mxl"   "$vWorkDir/log/bck/$vLogFileName.$vCurrApp.mxl" ;
    shell cp "$vBackupFolder/$vLogFileName.$vCurrApp.err"   "$vWorkDir/log/bck/$vLogFileName.$vCurrApp.err" ;
    shell tar --remove-files -cz -f $vBackupFolder.tar.gz $vRelativeBackupFolder  ;
    shell rm -r  $vBackupFolder ;
    shell scp $vBackupFolder.tar.gz oracle@hypdb:~/backup & ;

  • LR5 Backups are failing

    For a couple of years I've had LR set to ask to back up every day. It still tries to, but about 3 weeks ago it began failing to be able to back up. The "checking catalog integrity" box stays up for a long time (maybe a minute) and maybe the process doesn't even succeed because then that box is replaced by this error message.
    I never changed anything about folder permissions and the drive has plenty of free space. (It's my internal drive, which only has a few files and my apps on it; I save most of my files to an EHD.) Choosing a different back up folder gives the same error message. About a week ago I upgraded to OS X Yosemite on my Mac, but the problem persisted exactly the same.
    Please can someone help?

    Thank you for the quick reply. It didn't work though.
    I looked in Finder at the folder where my backups were being stored and it still says "read and write" under privileges.
    And I found the disk utility and the button that said "repair permissions" and clicked on that. It took a few minutes and showed many results about other things but not Lightroom.  I copied it and saved it in case that would be useful.  Let me know; I won't post it now because it's long.
    Unfortunately, even after restarting my computer, Lightroom is still failing to back up, giving the same error message as I posted above.
    Anything else I can do? 
    Would a screen shot of the folder where my Lightroom backups are stored help?  Next to the Backups folder, which I created 2 years ago, I notice another folder called "Corrupt Catalogs" which I don't think I made myself. According to file info, it was created December 18, 2013.  It has 5 catalogs in it, the latest dated July 13, 2014. I have no idea if this is related to my backup problem; just mentioning it just in case.
    As for the Backup folder, it has 3 backups in it dated 9/30, 10/02, and 10/05.

  • RMAN backups are slow with TSM

    Hi,
    I encountered a problem using RMAN with TSM to backup a database. It seems that the RMAN channel doesn't use the entire bandwidth to the TSM (or whatever) and is idle most of the time. This makes the database backup really slow.
    As a comparison, we backup also filesystem and SQL Server, they both use very few channels and each channel backup about X5 more data per second than Oracle. For example, SQL Server uses 5 channels to the TSM, and we get a total of around 100MB/s. When we configure Oracle to backup using 5 channels we get about 20MB/s and we see that the SQL Server is writing to the TSM all the time while Oracle is idle a large portion of the time.
    Any ideas? Known configuration issues?
    I hope I'm clear about the problem.
    Thanks,
    Liron

    Hi,
    Thanks for everybody for your responses, I'll try to sum the answers here:
    1. Yes, we backup the filesystem, and everything works fine. The problem is only with RMAN backups
    2. Resources are not an issue, it happens on strong and weak servers (and several O/S as well)
    3. Database versions are not the issue, it happens on 10.2 as well as 11.2
    My feeling is that this has something to do with the integration, either oracle setting or TSM setting, but I can't be sure until I solve this.
    For those of you who backup with TSM, did you notice that filesystem / SQL Servers are being backed up faster? Did you check the Oracle wait events and TSM status while you run the backup?
    Thanks
    BTW Girish, great comment, I wish I had all the answers... :)

  • Does RMAN backups are OS independent.

    Can I use RMAN backup of windows based oracle to construct solaris based oracle db.
    Thanks
    Naveen

    Can I use RMAN backup of windows based oracle to construct solaris based oracle db.As Justin has already said, by default NO. To use rman for closs platform migration you will have to check the ENDIAN format of the both the platforms since, the principal restriction on cross-platform transportable database is that the source and destination platform must share the same endian format.
    An example of Cross-Platform Migration Using Rman ( Windows 32-bit to Linux 32-bit ) is on metalink.You can check it out
    Doc ID: Note:414878.1
    You can also refer to Doc ID: Note:413586.1
    Regards,
    Anand

  • My laptop is hooked up to a time capsule via an ethernet network.  Recently, my backups are failing due to: "...sparsebundle is already in use."  What does this mean and how do I fix it?

    Lately my time machine backups have been failing because "...the sparsebundle is already in use."  What does this mean, and how can I fix it?

    What does this mean
    It means that there are bugs in the Time Machine software
    how can I fix it?
    A rather complex procedure....
    Pull the power cord from the back of the Time Capsule
    Count to ten
    Plug the power cord back into the the back of the Time Capsule

  • How to find RMAN backups are successful

    Hi,
    I am using RMAN for 10g databases. How can i ensure that the backups am taking thru RMAN are successful? is there any command.

    select
    SESSION_KEY, INPUT_TYPE, STATUS,
    to_char(START_TIME,'mm/dd/yy hh24:mi') start_time,
    to_char(END_TIME,'mm/dd/yy hh24:mi') end_time,
    round((end_time-start_time)*1440,2) "Minutes"
    from V$RMAN_BACKUP_JOB_DETAILS
    order by session_key desc;
    Regards
    Asif Kabir

  • RMAN backup got failed with the error ORA-19566

    Hi,
    One of database, while taking backup using RMAN, it failed with the following error:
    RMAN-03009: failure of backup command on DISK4 channel at 11/28/2012 09:47:29
    ORA-19566: exceeded limit of 0 corrupt blocks for file <faile_name>
    I used DBV to identify the number of blocks corrupted.
    I referred the Metalink iD 457422.1 & 336133.1. But it did not help since the corrupted blocks have got object in it.
    I could able to find the object as well. it is one of the table in the datafile.
    I used 'ALTER TABLE ... MOVE..' command to see if that helps. But again getting the same error while taking the backup and corrupted blocks still exists.
    DB Version : 10.2.0.5
    OS Version : RHEL 5.6
    Please help me out to get this fixed.

    Here it is:
    SQL> Select * from v$database_block_corruption ;
    FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTION_TYPE
    13 3988352 128 0 ALL ZERO

  • Rman Backups Failing

    Hi All,
    we have hot backups of DB scheduled(DB Full backup) thru RMAN for all prod DBs.. but since some days all the backups are failing with similar error.. the sample output of one of the backup job run is given below:
    set command id to 'BACKUP_PRSAL41_FUL_091007040002';
    echo set on
    executing command: SET COMMAND ID
    connected to recovery catalog database
    connected to target database: PRSAL41 (DBID=3043389771)
    input datafile fno=00002 name=/prddb02/u12/oradata/prsal41/undotbs01.dbf
    input datafile fno=00007 name=/prddb02/u12/oradata/prsal41/autodba8601dat0101.dbf
    input datafile fno=00008 name=/prddb02/u12/oradata/prsal41/autodba8601idx0101.dbf
    input datafile fno=00004 name=/prddb02/u12/oradata/prsal41/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 10-SEP-07
    input datafile fno=00006 name=/prddb02/u12/oradata/prsal41/IIS_INDEX_01.dbf
    input datafile fno=00005 name=/prddb02/u12/oradata/prsal41/IIS_DATA_01.dbf
    input datafile fno=00003 name=/prddb02/u12/oradata/prsal41/sysaux01.dbf
    input datafile fno=00001 name=/prddb02/u12/oradata/prsal41/system01.dbf
    channel ORA_DISK_1: specifying datafile(s) in backupset
    channel ORA_DISK_1: starting compressed full datafile backupset
    channel ORA_DISK_1: sid=147 devtype=DISK
    allocated channel: ORA_DISK_1
    Starting backup at 10-SEP-07
    backup device type disk tag 'BACKUP_PRSAL41_FUL_091007040002' da
    Starting Control File and SPFILE Autobackup at 10-SEP-07
    Finished backup at 10-SEP-07
    channel ORA_DISK_1: backup set complete, elapsed time: 00:02:25
    piece handle=/back01/prsal41/5oiricui_1_1 tag=BACKUP_PRSAL41_FUL_091007040002 comment=NONE
    channel ORA_DISK_1: finished piece 1 at 10-SEP-07
    Finished Control File and SPFILE Autobackup at 10-SEP-07
    piece handle=/back01/prsal41/c-3043389771-20070910-00 comment=NONE
    backup device type disk tag 'BACKUP_PRSAL41_FUL_091007040002' ar
    Starting backup at 10-SEP-07
    current log archived
    released channel: ORA_DISK_1
    allocated channel: ORA_MAINT_DISK_1
    channel ORA_MAINT_DISK_1: sid=147 devtype=DISK
    delete noprompt obsolete device type disk;
    allocate channel for maintenance type disk;
    Additional information: 3
    Linux-x86_64 Error: 2: No such file or directory
    ORA-27037: unable to obtain file status
    ORA-19625: error identifying file /hubudorap1/arch01/prsal41/1_132_626515083.arc
    RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
    RMAN-03002: failure of backup command at 09/10/2007 04:02:55
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 2 days
    Deleting the following obsolete backups and copies:
    Type Key Completion Time Filename/Handle
    Archive Log 275349 18-JUL-07 /hubudorap1/arch01/prsal41/1_132_626515083.arc
    Archive Log 275350 18-JUL-07 /hubudorap1/arch01/prsal41/1_133_626515083.arc
    Backup Set 383337 15-AUG-07
    Backup Piece 383340 15-AUG-07 /back01/prsal41/44ipdr6h_1_1
    Backup Set 383353 15-AUG-07
    Backup Piece 383362 15-AUG-07 /back01/prsal41/c-3043389771-20070815-00
    Backup Set 500971 07-SEP-07
    Backup Piece 500974 07-SEP-07 /back01/prsal41/5iirafql_1_1
    Archive Log 501025 07-SEP-07 /hubudorap1/arch01/prsal41/1_404_626515083.arc
    Backup Set 500987 07-SEP-07
    Backup Piece 500996 07-SEP-07 /back01/prsal41/c-3043389771-20070907-00
    Archive Log 505768 07-SEP-07 /hubudorap1/arch01/prsal41/1_405_626515083.arc
    Archive Log 505769 07-SEP-07 /hubudorap1/arch01/prsal41/1_406_626515083.arc
    Archive Log 505770 07-SEP-07 /hubudorap1/arch01/prsal41/1_407_626515083.arc
    Archive Log 505771 08-SEP-07 /hubudorap1/arch01/prsal41/1_408_626515083.arc
    deleted backup piece
    backup piece handle=/back01/prsal41/5iirafql_1_1 recid=178 stamp=632635222
    deleted archive log
    archive log filename=/hubudorap1/arch01/prsal41/1_404_626515083.arc recid=373 stamp=632635334
    archive log filename=/hubudorap1/arch01/prsal41/1_405_626515083.arc recid=374 stamp=632661717
    deleted archive log
    backup piece handle=/back01/prsal41/c-3043389771-20070907-00 recid=179 stamp=632635329
    deleted backup piece
    deleted archive log
    archive log filename=/hubudorap1/arch01/prsal41/1_408_626515083.arc recid=377 stamp=632718235
    Deleted 7 objects
    RMAN-06207: WARNING: 4 objects could not be deleted for DISK channel(s) due
    RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
    RMAN-06210: List of Mismatched objects
    RMAN-06211: ==========================
    archive log filename=/hubudorap1/arch01/prsal41/1_407_626515083.arc recid=376 stamp=632705451
    deleted archive log
    archive log filename=/hubudorap1/arch01/prsal41/1_406_626515083.arc recid=375 stamp=632685605
    deleted archive log
    RMAN-06212: Object Type Filename/Handle
    RMAN-06214: Backup Piece /back01/prsal41/c-3043389771-20070815-00
    RMAN-06214: Backup Piece /back01/prsal41/44ipdr6h_1_1
    RMAN-06214: Archivelog /hubudorap1/arch01/prsal41/1_133_626515083.arc
    RMAN-06214: Archivelog /hubudorap1/arch01/prsal41/1_132_626515083.arc
    RMAN-06213: --------------- ---------------------------------------------------
    release channel;
    exit;
    released channel: ORA_MAINT_DISK_1
    I am not able to detect why the archive log is missing... can anyone help me on this please..?
    btw, DBs are oracle 10g R2 non-rac
    Backup type : DB Full via RMAN.
    Thanks

    Hi,
    Have you used the CROSSCHECK command?
    I am not able to detect why the archive log is missing... can anyone help me on this please..?Could someone removed them through O/S commands (manually) ?
    Adith

Maybe you are looking for