Why my RMAN to archivelog backups do not end in ORACLE_HOME/dbs?

DB version: 11.2
Platform: Solaris 10

I noticed that the elements of rman backup containing archivelogs end in $ORACLE_HOME/dbs directory despite using the format parameter. This happened for the level 0 AND level 1 backups.

I know that the backup files result in $ORACLE_HOME/dbs when you forget to specify the FORMAT. But the FORMAT is included in my Level0 and level 1 Scripts as shown below. Is there something else wrong with my scripts L0 and L1?

Here's my Level0 and level 1 backup scripts


-Level0
run
{
allocate channel LEVEL0_TBLQA device type disk;
crosscheck backup;
delete noprompt obsolete;
backup as backupset incremental level 0 database format='/u04/dbfiles/RMAN_bkp/tblqa/TBLQA_full_%U_%T.bkp' plus archivelog delete input;
release channel LEVEL0_TBLQA;
}
-Level 1
run {
backup as compressed backupset incremental level 1 database format='/u04/dbfiles/RMAN_bkp/tblqa/TBLQA_L1_%U_%T.bkp' plus archivelog delete all input;
}
This DB uses the control as a catalog file.

backup as backupset effective additional 0 database format='/u04/dbfiles/RMAN_bkp/tblqa/TBLQA_full_%U_%T.bkp' more entered archivelog delete;

backup as backupset effective additional 1 database format='/u04/dbfiles/RMAN_bkp/tblqa/TBLQA_L1_%U_%T.bkp Tablet ' more archivelog delete all entries;

This is because the format that you specified is good only until the database backup (backup format compressed backupset effective additional 1 database "... ") and not for the log archiving in your script. Therefore, the archivelog backups stored in the location of $ORACLE_HOME/dbs and the backup of the database gets stored in the format location you mentioned in your RMAN script.

Instead, you can use as below:

run
{
allocate channel LEVEL0_TBLQA device type disk format '/u04/dbfiles/RMAN_bkp/tblqa/TBLQA_full_%U_%T.bkp';
crosscheck backup;
delete noprompt obsolete;
backup as backupset incremental level 0 database plus archivelog delete input;
release channel LEVEL0_TBLQA;
}

Tags: Database

Similar Questions

  • Full RMAN and Archivelog backups

    I'm scripting rman of my stuff and it is a much larger part of an interview of Perl. I have all night and schedules of jobs. Every night will make a full and hourly backup will do archivelog backup. Full backups take about 2-3 hours.
    My question is: is there a problem with running in archivelog backups run while I do a full backup. If the system resources are not a problem, what are some arguments for or against?

    One of two simultaneous backups can sometimes fail with

    "ORA-00230: forbidden operation: snapshot control file queue unavailable."

    When you attempt to update the controlfile.

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

  • My "restore from backup" does not end as the screen lock appears

    I got a new iphone with 64Meg and OIS 9.3.3 6 operating system. Before putting in my business phone; I backed up my data on itunes using my PC with Windows 10. As I'm trying to "restore backup" on an iphone same 6, I was unable to do, when to halfway through the download process, the screen lock appears and disconnect the iphone from itunes and the download stops. It seems to be appx 29 minutes for download; but I never got rained only 7 minutes to download completion before the screen is locked or the battery at 100% load indicator disconnect the iphone.

    I have disabled all notifications, deleted my AOL Mail, set the screen saver to "never", off of password, all without success. Help!

    Hello, Franklytex!

    Welcome to the communities of Apple Support and post your first message! Looks like you have a problem to restore your backup from iTunes. I know how important it is that your iPhone can be restored properly! Read this article which has steps for you If your iTunes backup could not be completed or you can not restore from a backup. More precisely:

    Try again after each step

    1. Make sure you have the latest version of iTunes.
    2. Connect your device to your computer with a cable USB, then Select your device in iTunes. If your device does not appear in iTunes, you must correct this problem until you can continue. Or, if you have forgotten your password or your device is off, know what to do.
    3. Turn off your computer and your iPhone, iPad or iPod touch. Then turn on again them.
    4. If you use a Mac, skip this step. If you use a Windows PC and iTunes will not respond or never ends your backup, you may need to to update, edit, disable or uninstall your security software.
    5. If you have multiple computers, try to make a backup on your other Mac or PC. Otherwise, use iCloud for save your device and restore it from your backup to iCloud.
    6. If you see an alert indicating an error has occurred, your backup is corrupt or incompatibleor there is not enough disk space, find your error message below to learn what to do next.
    7. Contact Apple technical support.

    See you soon!

  • Why keep the Archivelogs after Archivelog backups?

    Greetings. I'm a long time SQL Server DBA operating on the dark side.

    So we are taking (AL) Archivelog backups every 30 minutes. However, it seems that it is not "empty" the former AL the way in which SQL Server would be "empty" when it backs up the transaction log. They still exist, consume space of course.

    The excerpt below shows me that it is not necessary for the latter to retain once they are saved. Of course this would free up space, but I guess there is a good reason not to want to delete them as well? My belief is that a restoration can occur faster with them still existing locally, but hoped someone could confirm / deny here? If this isn't the case, otherwise why would we want to keep them once they are saved?

    Thank you!

    http://docs.Oracle.com/CD/B19306_01/backup.102/b14192/bkup003.htm

    4.3.7.1.2 using BACKUP ARCHIVELOG with ENTRY REMOVE or REMOVE all THE ENTRIES

    You can specify the DELETE INPUT or DELETE ALL INPUT clauses for the BACKUP ARCHIVELOG command to delete the log files archived once they are saved, eliminating the separate step of manually delete the archived redo logs.

    > I guess that there is a good reason not to want to delete them as well

    No, not really. you do not raise a point that if you had to do a restore/recovery operation, it would be faster if they are already there, but this should be a rare operation?

    You may want to delete all saved archivelog 2 times (or 3 or 4, etc.) where your backup is bad - this way you ensure that you have several copies autour.

  • With RMAN for backup, but not with the archive logs

    We run a 10.2.0.4 database and the rest 11.2.0.3. All databases are on RHEL 5.7.

    Our backups are via RMAN, with the data files, controlfiles and spfile saved to disk, then each day, it is copied off site to a backup server.

    My question is around logs archiving and RMAN.
    Our current situation is:
    -We do not save the logs to archive via RMAN. for example: backup of the list of the archivelog all; gives "specification does not match backups in the repository.
    -We set the archive_lag_target so archiving logs is produced every 30 minutes.
    -a cron job running on a remote server runs periodically to synchronize data (rsync server) the directory of archives with a remote control.
    -daily archive logs on the server host are bzip. Purge of these newspapers is scheduled for more than 3 days rman 'window of recovery '.

    I'm interested in feedback as to if our strategy around archiving logs is correct or not.

    Should we be backup logs archiving via RMAN? Are there potential problems with our approach?
    We just kept our backups in this way the DBA in the past want to see newspapers archived as opposed to it while a backupset.

    Curious to know what others are doing.

    Hello

    Welcome to OTN!

    Archivelogs with RMAN backup is a better option. When the archives are supported by RMAN, RMAN would be aware of the backup items which are required at the time of the recovery archives. You don't have to do it manually.

    On the disk space, you can delete the archives once they were saved by RMAN.

    RMAN > delete any backup archivelog entry;

    This supports the archivelogs and then remove the archives from the disk.

    If you have a dataguard configured, you can set the deletion policy 'applied on Eve', which removes the archives as and when they are applied to the database ensures there by the management of disk space again.

    RMAN > configure archivelog political of deletion to applied pending;

  • Backup RMAN - ORA-19504 with archivelog backup all

    Hi all


    I'm working on the assignment to seam RMAN backup piece archivelog backup to a static element in the backup. That's what I'm trying to achieve. Please give me a solution for this.



    target of bash - $3.2 rman.

    Recovery Manager: release 10.2.0.5.0 - Production on Mon 19 dec 13:50:28 2011

    Copyright (c) 1982, 2007, Oracle. All rights reserved.

    connected to target database: INCR (DBID = 579267515)

    RMAN > archivelog backup all the format ' / tmp/abc.bkp ';

    From backup 2011-12-19 13:50:47
    Current archived log
    using the control file of the target instead of recovery catalog database
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid = 20 devtype = DISK
    channel ORA_DISK_1: from archive newspaper backupset
    channel ORA_DISK_1: specification of archive log backup set
    archive log entry thread = 1 sequence = 413 recid = 65 = 770058553 stamp
    archive log entry thread = 1 sequence = 414 recid = 66 = 770058553 stamp
    archive log entry thread = 1 sequence = 415 recid = 67 = 770058555 stamp
    archive log entry thread = 1 416 recid = 68 = 770058560 stamp = sequence
    archive log entry thread = 1 sequence = 417 recid = 69 = 770058560 stamp
    archive log entry thread = 1 sequence = 418 recid = 70 = 770058561 stamp
    archive log entry thread = 1 sequence = 419 recid = 71 = 770058561 stamp
    archive log entry thread = 1 sequence = 420 recid = 72 = 770058561 stamp
    archive log entry thread = 1 sequence = 421 recid = 73 = 770058664 stamp
    archive log entry thread = 1 sequence = 422 recid = 74 = 770058664 stamp
    archive log entry thread = 1 sequence 423 recid = 75 = 770058666 stamp =
    archive log entry thread = 1 sequence = 424 recid = 76 = 770058671 stamp
    archive log entry thread = 1 sequence = 425 recid = 77 = 770058671 stamp
    archive log entry thread = 1 sequence = 426 recid = 78 = 770058672 stamp
    archive log entry thread = 1 sequence = 427 recid = 79 = 770058672 stamp
    archive log entry thread = 1 sequence = 428 recid = 80 = 770058672 stamp
    archive log entry thread = 1 sequence = 429 recid = 81 stamp = 770058772
    archive log entry thread = 1 sequence = 430 recid = 82 stamp = 770058772
    archive log entry thread = 1 sequence = 431 recid = 83 stamp = 770058774
    archive log entry thread = 1 sequence = 432 recid = 84 = 770058779 stamp
    archive log entry thread = 1 sequence = 433 recid = 85 stamp = 770058779
    archive log entry thread = 1 sequence = 434 recid = stamp 86 = 770058780
    archive log entry thread = 1 sequence = 435 recid = stamp 87 = 770058780
    archive log entry thread = 1 sequence = 436 recid = 88 = 770058780 stamp
    archive log entry thread = 1 sequence = 437 recid = 89 stamp = 770072418
    archive log entry thread = 1 sequence = 438 recid = 90 = 770086824 stamp
    archive log entry thread = 1 sequence = 439 recid = 91 = 770090427 stamp
    archive log entry thread = 1 440 recid = 92 = 770094027 stamp = sequence
    archive log entry thread = 1 sequence = 441 recid = 93 stamp = 770108432
    archive log entry thread = 1 sequence = 442 recid = 94 stamp = 770122837
    archive log entry thread = 1 sequence = 443 recid = 95 stamp = 770140538
    channel ORA_DISK_1: from room 1 to 2011-12-19 13:50:48
    channel ORA_DISK_1: finished piece 1 to 2011-12-19 13:50:49
    piece handle=/tmp/abc.bkp tag = TAG20111219T135047 comment = NONE
    channel ORA_DISK_1: complete set of backups, time: 00:00:02
    channel ORA_DISK_1: from archive newspaper backupset
    channel ORA_DISK_1: specification of archive log backup set
    archive log entry thread = 1 sequence = 444 recid = 96 = 770155250 stamp
    archive log entry thread = 1 sequence = 445 recid = 97 stamp = 770170543
    archive log entry thread = 1 sequence = 446 recid = 98 stamp = 770177640
    archive log entry thread = 1 447 recid = 99 = 770184061 stamp = sequence
    archive log entry thread = 1 sequence = 448 recid = 100 = 770202008 stamp
    archive log entry thread = 1 sequence = 449 recid = 101 stamp = 770216414
    archive log entry thread = 1 sequence = 450 recid = 102 stamp = 770234420
    channel ORA_DISK_1: from room 1 to 2011-12-19 13:50:50
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 19/12/2011 13:50:51
    ORA-19504: could not create the file "/ tmp/abc.bkp".
    ORA-27038: created file already exists
    Additional information: 1

    Your format mask is incorrect. You don't have a backupset number and a number of inside backup piece.

    If the number of backup files exceeds the filesperset number that will create a new piece of backup. When you do that, you will get the error you are looking for in the documentation.
    In order to complete your "requirement", you would either need to set filesperset to a very high number, or know the amount of archivelogs beforehand.
    This would be the subject of RMAN to automate all obsolete. As rman will automatically process the correct backup items, the "requirement" to do everything in a single piece of backup serves no useful purpose.

    ----------
    Sybrand Bakker
    Senior Oracle DBA

  • RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

    Hi Oracle Community,

    I have a few databases (11.2.0.4 POWER 2 block and 12.1.0.2) with Data Guard. Back up this database with RMAN to ribbons, only on the primaries.

    During the backup, sometimes I got RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure

    By reason of this global warning to backup status is "COMPLETED WITH WARNINGS". Is it possible to remove this warning, or perhaps change RMAN configuration to avoid the appearance of this warning?

    Concerning

    J

    Where is the problem on these warnings? If you do not want to see such warnings, why not simply to perform the removal of the archivelogs in a separate step? For example:

    RMAN> backup database plus archivelog;
RMAN> delete noprompt archivelog all completed before 'sysdate-1';

  • RMAN-06059: expected archived log not found

    DB version: 11.1.0.7
    Operating system: Solaris 10

    Our cron job RMAN has met the following error.
    -First save attempt (complete bkp more archive log) done by connecting to the catalog
    Starting backup at 14-MAR-12
current log archived
released channel: ch00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 03/14/2012 08:09:58
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc
ORA-17503: ksfdopn:2 Failed to open file +PQWSP_ARCH01/pqwsp_arch/pqwsp_26530_1_764525298.arc
ORA-15173: entry 'pqwsp_26530_1_764525298.arc' does not exist in directory 'pqwsp_arch'
    Because I didn't share RMAN catalog schema password, I used the control as a catalog file and run the CROSSCHECK command.

    -Use the control as a catalog file
    $ rman target /

Recovery Manager: Release 11.1.0.7.0 - Production on Wed Mar 14 09:45:59 2012

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

connected to target database: PQWSP (DBID=1638594930)

RMAN> crosscheck archivelog all;

using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=429 instance=pqwsp1 device type=DISK
validation succeeded for archived log
archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26563_1_764525298.arc RECID=19019 STAMP=777888587
validation succeeded for archived log
archived log file name=+PQWSP_ARCH01/pqwsp_arch/pqwsp_26564_1_764525298.arc RECID=19022 STAMP=777890270
validation succeeded for archived log
.
.
.
.
.

Crosschecked 14 objects
    Cannot find objects expired in the output above. I had * "validation succeeded" * message to arch all newspapers.

    So I ran a
    BACKUP ARCHIVELOG ALL DELETE ALL INPUT;
    and this backup was successful.

    No idea why the first attempt failed when there were not all logs archived expired? If I run the command of OVERLAP by connecting to the catalog, I could find out of date newspapers?

    No idea why the first attempt failed when there were not all logs archived expired?
    this case is not releated archivelog expired, however it seems the requested archivelog 26530 isn't available on destinationas, that it can be removed manually or another taking backup operation the backup and deleted if the execution of the whole.

    crosscheck updated detail that its not available for backup... Check the output of you overlap cmd to 26530 archivelog.

    Thank you
    Tylay Singh

  • ARCHIVELOG backup failed

    Hello

    We have the oracle 10.2.0.2 database that is being backed up online every day, we want to have a minimal loss of data in case of failure of a comprehensive support (including the control/Redo/data files & Archivelogs).
    CRD files in an ASM diskgroup and Archivelogs are FRA, which is in an another ASM diskgroup.
    The two start meet normal redundancy, God forbid if full happens of the failure of a support and loss of all the CRD & Archivelogs, we must rely on the backup to the recovery process, but we have a full online backup at night and if we have an accident DB at 2 PM, then we need to get up to this time , but we won't archivelogs which were after the online backup, so we want to plan backups periodicals archivelog minumum for data loss.

    I know that a full recovery not won't happen if you lose Controlfile & current redolog file, but by taking the archivelogs backup we will reduce the loss of data.

    To achieve this, I tried to run the backup as the commands below.

    backup format ' % s: % t: %p orcl_ > .dbf ' archivelog not saved 1 time; does not work.

    RMAN > run {}
    allocate channel 'dev_0' type disk
    SQL 'alter system archive log current';
    backup format ' % s: % t: %p orcl_ > .dbf ' archivelog not saved 1 time;
    }

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-00558: error occurred during parsing of order entry
    RMAN-01009: syntax error: 'no': expected an of: "all, of, like, high logseq, low, SNA, sequence, time, up to the.
    RMAN-01007: column 84 line 6 file: entry standard

    RMAN >
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-00558: error occurred during parsing of order entry
    RMAN-01009: syntax error: found '} ': expected an of: "assign, change, save, beginline, blockrecover, catalog, change, connect, copy, convert, create, duplication, configure, duplicate, debug, delete, drop, leave, endinline, flashback, host, {, library, list, mount, open, print, quit smoking, recover, registry, release, replace, report, renormalize, reset, restore, resync, rman, run, rpctest, together, setlimit, sql, switch, coil, start, stop, send, display, test, transport, upgrade}» unsubscribe, validate.
    RMAN-01007: line 1 column 1 file: entry standard

    See the error message you got:

    syntax error: 'no': expected an of: "all, of, like, high logseq, low, SNA, sequence, time, up to the.

    'ALL' or 'FROM' or 'LIKE' etc must follow the keyword 'ARCHIVELOG.

    For example, the command would be

    backup format 'orcl_%s:%t:%p.dbf' archivelog all not backed up 1 times'

    (I wonder why you have the sign "superior to" in the format specifier)

    Hemant K Collette

  • 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.

  • RMAN-06023: no backup or copy of datafile 407 found to restore

    Hi all

    Database 11.1.0.7 on OUL5x64
    just did a full backup and check the log file, the backup was good, he saved on a NFS mount.


    It is the error in the log file

    # Release target DB info, catalog DB, catalog schema & RMAN executable: #.
    11.1.0.7
    Winding began in the log file: /tmp/rman_gold.log

    Recovery Manager11.1.0.7.0

    RMAN > run {}
    2 > set up what SNA 5976539071832.
    3 > restore database;
    4 > restore database;
    {5 >}
    executing command: SET until clause
    using the control file of the target instead of recovery catalog database

    From restoration to 1 April 10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID = 1632 type device = DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID = 1655 type device = DISK

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================

    RMAN-03002: failure of the restore command at 01/04/2010 11:11:12
    RMAN-06026: some targets not found - abandonment of restoration
    RMAN-06023: no backup or copy of datafile 407 found to restore
    RMAN-06023: no backup or copy of datafile 406 found to restore
    RMAN-06023: no backup or copy of datafile 405 found to restore
    RMAN-06023: no backup or copy of file 404 found to restore
    RMAN-06023: no backup or copy of datafile 403 found to restore
    RMAN-06023: no backup or copy of datafile 402 found to restore
    RMAN-06023: no backup or copy of datafile 401 found to restore
    RMAN-06023: no backup or copy of datafile 400 found to restore
    RMAN-06023: no backup or copy of datafile 399 found to restore
    RMAN-06023: no backup or copy of datafile 398 found to restore
    RMAN-06023: no backup or copy of datafile 397 found to restore
    RMAN-06023: no backup or copy of datafile 396 found to restore
    RMAN-06023: no backup or copy of datafile 395 found to restore
    RMAN-06023: no backup or copy of datafile 394 found to restore
    RMAN-06023: no backup or copy of datafile 393 found to restore
    RMAN-06023: no backup or copy of datafile 392 found to restore
    RMAN-06023: no backup or copy of datafile 354 found to restore
    RMAN-06023: no backup or copy of datafile 353 found to restore
    # Specific details of the problem encountered during the RMAN session: #.
    the database backup point also complete a NFS mount. then delete the database, startup nomount database and restore the controlfile then stop and start frame.
    connecting to rman as
    RMAN target /.
    run
    backup from the list; and the backup from the list of the archivelog all;
    get the number of SCN and restore in the above script.
    If failed the first time with message

    RMAN-06026: some targets not found - abandonment of restoration
    RMAN-06023: no backup or copy of datafile 407 found to restore
    RMAN-06023: no backup or copy of datafile 406 found to restore
    RMAN-06023: no backup or copy of datafile 405 found to restore
    RMAN-06023: no backup or copy of file 404 found to restore
    .........................

    After that he failed
    Then I added everything backup as
    RMAN >
    Catalogue backuppiece ' / rman/backup/ph2/xxxxxxxxxx.dbf';
    .......................
    ......................

    Then, run the restore again.
    It fails with the above error.

    I check, all backup elements are there.
    Why the rman could not locate the backup pieces.

    Can someone please have a suggestion.

    Thanks in advance!

    PLS, try this command without SNA 5976539071832 such as

    Run {}
    restore the database;
    recover the database;
    }

  • Double sequence of many archivelogs backup

    Hello guys,.

    When I wrote:

    backup from the list of the archivelog all, I got this:

    Time of accomplishment time BS key size Device Type

    ------- ---------- ----------- ------------ ---------------

    2889 M DISK 00:00:09 55,28 28 DECEMBER 15

    BP key: 2919 situation: AVAILABLE Tablet: YES Tag: BKP_ARCHIVES

    Part name: /u01/arc_BD_20151228_3257_1.arc

    List of newspapers archived in defined backup 2889

    The next time that THRD Seq YVERT low low time next YVERT

    ---- ------- ---------- --------- ---------- ---------

    1 4347 94585857 27 December 15 94586734 27 December 15

    1 4348 94586734 27 December 15 94586930 27 December 15

    1 4349 94586930 27 December 15 94586933 27 December 15

    1 4350 94586933 27 December 15 94586936 27 December 15

    Time of accomplishment time BS key size Device Type

    ------- ---------- ----------- ------------ ---------------

    2891 M DISK 00:00:10 56,04 28 DECEMBER 15

    BP key: 2921 location: AVAILABLE Tablet: YES Tag: BKP_ARCHIVES

    Part name: /u01/arc_BD_20151228_3259_1.arc

    List of newspapers archived in defined backup 2891

    The next time that THRD Seq YVERT low low time next YVERT

    ---- ------- ---------- --------- ---------- ---------

    1 4347 94585857 27 December 15 94586734 27 December 15

    1 4348 94586734 27 December 15 94586930 27 December 15

    1 4349 94586930 27 December 15 94586933 27 December 15

    1 4350 94586933 27 December 15 94586936 27 December 15

    RMAN > backup from the list of the archivelog sequence 4347 summary;

    Backup list

    ===============

    S LV TY Device Type delay #Pieces compressed #Copies Tag key

    2849. A DECEMBER 27, 15 1 DISC 1 YES BKP_ARCHIVES

    NO. 2851 DISC 27 DECEMBER 15 1 1 YES BKP_ARCHIVES

    2853. A DECEMBER 27, 15 1 DISC 1 YES BKP_ARCHIVES

    2855 DISC 27 DECEMBER 15 1 1 YES BKP_ARCHIVES

    2857. A DECEMBER 27, 15 1 DISC 1 YES BKP_ARCHIVES

    2859. A DECEMBER 27, 15 1 DISC 1 YES BKP_ARCHIVES

    2861. A DECEMBER 28, 15 1 DISC 1 YES BKP_ARCHIVES

    2863. A DECEMBER 28, 15 1 DISC 1 YES BKP_ARCHIVES

    2865. A DECEMBER 28, 15 1 DISC 1 YES BKP_ARCHIVES

    2867. A DECEMBER 28, 15 1 DISC 1 YES BKP_ARCHIVES

    2869. A DECEMBER 28, 15 1 DISC 1 YES BKP_ARCHIVES

    2871. A DECEMBER 28, 15 1 DISC 1 YES BKP_ARCHIVES

    2873. A DECEMBER 28, 15 1 DISC 1 YES BKP_ARCHIVES

    2875 DISC 28 DECEMBER 15 1 1 YES BKP_ARCHIVES

    2877. A DECEMBER 28, 15 1 DISC 1 YES BKP_ARCHIVES

    2879. A DECEMBER 28, 15 1 DISC 1 YES BKP_ARCHIVES

    2881 DISC 28 DECEMBER 15 1 1 YES BKP_ARCHIVES

    2883. A DECEMBER 28, 15 1 DISC 1 YES BKP_ARCHIVES

    2885. A DECEMBER 28, 15 1 DISC 1 YES BKP_ARCHIVES

    2887 DISC 28 DECEMBER 15 1 1 YES BKP_ARCHIVES

    2889. A DECEMBER 28, 15 1 DISC 1 YES BKP_ARCHIVES

    2891 DISC 28 DECEMBER 15 1 1 YES BKP_ARCHIVES

    If you look above, I have several sequences (duplicate) in many archivelogs thrown...

    What is the problem?


    My backup script is:

    Run {}

    ARCHIVELOG backup all the format ' / u01/arc_%d_%Y%M%D_%s_%p.arc' tag = "BKP_ARCHIVES";

    delete noprompt archivelog all backed up 1 times on peripheral drive completed before ' sysdate - 1';

    }

    3059845 skrev:

    If you look above, I have several sequences (duplicate) in many archivelogs thrown...

    What is the problem?

    My backup script is:

    Run {}

    ARCHIVELOG backup all the format ' / u01/arc_%d_%Y%M%D_%s_%p.arc' tag = "BKP_ARCHIVES";

    delete noprompt archivelog all backed up 1 times on peripheral drive completed before ' sysdate - 1';

    }

    If you want to have 24 hours of archived recovery writes to the disk, you can ignore the backup in the same sequence over and over by configuring RMAN backup optimization. Then RMAN ignore archived redo logs that has already been backed up.

    Note configuration of backup optimization also ignores "identical data files" which has already been backed up as well. http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV113

    Another way would be to edit your script a little

    run

    {

    backup ARCHIVELOG all not saved 1 time format ' / u01/arc_%d_%Y%M%D_%s_%p.arch' tag = "BKP_ARCHIVES";

    delete noprompt archivelog all completed before ' sysdate-1' saved 1 time to device type disk.»

    }

    Concerning

    AJ

  • During the backup archivelog backups online

    Hello

    Oracle 11.2.0.4

    Linux SLES 11 SP2


    During our backup window, some batches are executed generate an amount of redo. Completion of our hot backup, it backs up all records generated and removes all the. We are afraid to fill our archivelog files before the end of hot backup. It's going to be any problem if I back up and delete the archivelogs during the backup hot (using a different RMAN command)?  For the moment, we are unable to add space for the file archive system.


    These are the rman commands executed:


    Hot backup


        RUN{
                ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch02 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch03 TYPE 'SBT_TAPE';
                SEND 'NB_ORA_SERV=$NB_ORA_SERV,NB_ORA_CLIENT=$NB_ORA_CLIENT,NB_ORA_POLICY=$NB_ORA_POLICY';
                BACKUP
                       $BACKUP_TYPE
                       SKIP INACCESSIBLE
                       TAG $BTAG$(date +"%Y%m%d%H%M%S")
                       FILESPERSET 1
                       FORMAT 'bk_%U_%t'
                       DATABASE;
                sql 'alter system archive log current';
                RELEASE CHANNEL ch00;
                RELEASE CHANNEL ch01;
                RELEASE CHANNEL ch02;
                RELEASE CHANNEL ch03;
                # backup all archive logs
                ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
                BACKUP
                        filesperset 20
                        TAG $BTAGAR$(date +"%Y%m%d%H%M%S")
                        FORMAT 'al_%s_%p_%t'
                        ARCHIVELOG ALL DELETE INPUT;
                RELEASE CHANNEL ch00;
                RELEASE CHANNEL ch01;
        }


    Archives


          RUN{
                # backup all archive logs
                ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch02 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch03 TYPE 'SBT_TAPE';
                ALLOCATE CHANNEL ch04 TYPE 'SBT_TAPE';
                SEND 'NB_ORA_SERV=$NB_ORA_SERV,NB_ORA_CLIENT=$NB_ORA_CLIENT,NB_ORA_POLICY=$NB_ORA_POLICY';
                BACKUP
                        filesperset 10
                        TAG $BTAGAR$(date +"%Y%m%d%H%M%S")
                        FORMAT 'al_%s_%p_%t'
                        ARCHIVELOG ALL DELETE INPUT;
                RELEASE CHANNEL ch00;
                RELEASE CHANNEL ch01;
                RELEASE CHANNEL ch02;
                RELEASE CHANNEL ch03;
                RELEASE CHANNEL ch04;
        }


    Thank you for your time.

    Kind regards

    Ferran

    If you delete the archivelogs that have not been funded until you lose the ability to recover your database using incremental backups hot. When you make a hot backup, you'll need archivelogs to recover data files to recover the database in a consistent state. As long as you have archivelogs in any backupset should not be a problem. Archivelogs are always in their own backupset. You can use additional settings when you perform the backup of the archivelogs, such as 'no saved' or 'skip inaccessible', in order to avoid the mistakes of rman backup.

  • Obsolete backups are not deleted

    Hello

    I am facing the following problem:

    System: 11.2.0.1.0 not patched on Windows Server 2008 R2 (this is a customers machine and it has no interest in patching-_-)

    RMAN> show all;

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:\db_backup\rman\XXX\%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   'F:\db_backup\rman\XXX\backup_%U';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\11.2.0\DATABASE\XXX.ORA';

    NAMETYPEVALUE

    ------------------------------------ ----------- ------------------------------

    control_file_record_keep_timeinteger7

    My script for the work:

    @echo off

SET ORACLE_HOME=D:\Oracle\11.2.0
SET ORACLE_SID=XXXX
SET NLS_LANG=GERMAN_GERMANY.WE8MSWIN1252
SET NLS_DATE_FORMAT=yyyy-mm-dd:hh24:mi:ss
SET BACKUPDIR=D:\db_backup\rman\XXX
SET SCRIPTDIR=D:\db_backup\scripts
SET LOGDIR=D:\db_backup\logs

%ORACLE_HOME%\bin\rman.exe target / cmdfile=%SCRIPTDIR%\rman_command.rman msglog %LOGDIR%\%ORACLE_SID%_backup.log

exit

    The rman_command.rman file:

    sql 'alter system archive log current';
crosscheck backup;
crosscheck archivelog all;
delete noprompt obsolete device type disk;
delete noprompt expired backup;
backup database plus archivelog delete input;
exit

    So I want to keep only the backups that have less than 3 days. And the older then 3 days should be discarded. But my problem is, that sometimes rman stops just delete old backups. And keeps all old backups. I also noticed that overnight stop to delete older backups is the same when the database has rebounded. For example, if the database has rebounded on June 28, 2015, then after June 28, rman always delete the backups. So I have now all bakups since that data. What I also noticed that rman stops remove the actual backups but don't not continue delete the backup control file.

    Is this a bug?

    OK, I got it. There is a corruption of block in the database which prevents the full backup at some point in its execution.

    Guys, thanks a lot for your help!

  • RMAN change the backup of data files directory

    Hi all!

    I have question for RMAN. My backups keep in fast_recovery_area (/ opt/oracle/fast_recovery_area). I want to change the path of my fast_recovery_area to another location. I've changed that through SQL more command: ALTER SYSTEM SET DB_RECOVERY_FILE_DEST = ' / opt/oracle/backup ' SCOPE = BOTH SID ='* ';

    Now, my fast_recovery_area is in this path/opt/oracle/backup. In the fast_recovery_area, I have 4 folders (archivelog, autobackup, backupset datafile). All folder is created in the new location and RMAN write successfully the file on the new location except a single file (datafile). How can I change this option for this folder that writes to the new location. P.S datafile directroy have * dbf files backed up nightly.

    Thank you!

    You use an incremental update strategy of backup.  The level 1 backup is always aware of the 'previous' 0 level backup in the old location, so it is not a fee L0 backup in the new location.  You can remove the old backup, run a BACKUP DUPLICATION and OVERLAPPING COPY OF DATABASE for Oracle to be aware that the L0 backup no longer exists.  Then, run a fresh backup for Oracle create a new backup of L0.

    Hemant K Collette

Maybe you are looking for