Full backup and backup archive logs

Hello,
today in the early morning i did backup of my db with :
RMAN> backup as COMPRESSED BACKUPSET DATABASE format '/backup/%d_t%t_s%s_p%p';This command created two files :
[oracle@p1 backup]$ ls -l
total 1132680
-rw-r-----  1 oracle oinstall 1155940352 Sep 14 00:44 TEST_t697508918_s5_p1
-rw-r-----  1 oracle oinstall    2785280 Sep 14 00:44 TEST_t697509873_s6_p1Did i backed up archive logs also with this command ?
If I did not, do i have to i n order to have everything to do complete resterer and recovery ?
Is now to late to backup them?

Can you confirm that this backup will be placed in the FRA, it will backup all datafile, control files, spfile and control files all arhchivle logs and when backup finshes then will delete all archive logs ?+
after running that command yo can confirm it by yourself at RMAN prompt.
RMAN> list backup;
List of Backup Sets
===================
BS Key  Type LV Size       Device Type Elapsed Time Completion Time
200     Full    509.78M    DISK        00:01:03     15-FEB-07
        BP Key: 202   Status: AVAILABLE  Compressed: NO  Tag: TAG20070215T171219
        Piece Name: /disk2/PROD/backupset/2007_02_15/o1_mf_nnndf_TAG20070215T171219_2xb17nbb_.bkp
  List of Datafiles in backup set 200
  File LV Type Ckp SCN    Ckp Time  Name
  1       Full 421946     15-FEB-07 /disk1/oradata/prod/system01.dbf
  2       Full 421946     15-FEB-07 /disk1/oradata/prod/sysaux01.dbf
  3       Full 421946     15-FEB-07 /disk1/oradata/prod/undotbs01.dbf
  4       Full 421946     15-FEB-07 /disk1/oradata/prod/cwmlite01.dbf
  5       Full 421946     15-FEB-07 /disk1/oradata/prod/drsys01.dbf
  6       Full 421946     15-FEB-07 /disk1/oradata/prod/example01.dbf
  7       Full 421946     15-FEB-07 /disk1/oradata/prod/indx01.dbf
  8       Full 421946     15-FEB-07 /disk1/oradata/prod/tools01.dbf
  9       Full 421946     15-FEB-07 /disk1/oradata/prod/users01.dbf
BS Key  Type LV Size       Device Type Elapsed Time Completion Time
201     Full    7.98M      DISK        00:00:03     15-FEB-07
        BP Key: 203   Status: AVAILABLE  Compressed: NO  Tag: TAG20070215T171219
        Piece Name: /disk2/PROD/backupset/2007_02_15/o1_mf_ncsnf_TAG20070215T171219_2xb19prg_.bkp
  SPFILE Included: Modification time: 15-FEB-07
  SPFILE db_unique_name: PROD
  Control File Included: Ckp SCN: 421968       Ckp time: 15-FEB-07
BS Key  Size       Device Type Elapsed Time Completion Time
227     30.50M     SBT_TAPE    00:00:11     15-FEB-07
        BP Key: 230   Status: AVAILABLE  Compressed: NO  Tag: TAG20070215T171334
        Handle: 0bia4rtv_1_1   Media:
  List of Archived Logs in backup set 227
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  1    5       389156     15-FEB-07 411006     15-FEB-07
  1    6       411006     15-FEB-07 412972     15-FEB-07
  1    7       412972     15-FEB-07 417086     15-FEB-07
  1    8       417086     15-FEB-07 417114     15-FEB-07
  1    9       417114     15-FEB-07 417853     15-FEB-07
  1    10      417853     15-FEB-07 421698     15-FEB-07
  1    11      421698     15-FEB-07 421988     15-FEB-07list backup will show you everything.
Would then this be incremental level 0 backup ?
yes by default i think so.
so with this i must be able to flasback my database at least 3 day in the past if i understood correctly.
But i am little puzled about purging those flasback data ...
Can you point me please to some link or tell how can i purge logs that are not need for that flashback period... ?
please read this link
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/rpfbdb003.htm#sthref513
Khurram

Similar Messages

  • Is RMAN only way to take backup and delete Archive Logs?

    On primary db:
    ===============
    OS: Windows 2003 server 32-bit
    Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
    On Physical standby db:
    ===============
    OS: Windows 2003 server 32-bit
    Oracle: Oracle 10g (10.2.0.1.0) R2 32-bit
    Data Guard just configured. Archive Logs are properly being shipped to standby db. Is RMAN only way to take backup and delete Archive Logs from both primary and standby db? What other command can be used?
    Thanks

    No, but anything else is way more work. Without using RMAN you would have to find another way to keep track of applied logs.
    RMAN make this very simple :
    RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;Using another method would be like using the handle of your screwdriver as a hammer.
    See "RMAN Recipes for Oracle Database 11g" ISBN 978-1-5959-851-1
    Best Regards
    mseberg

  • How to recover datafile in Oralcle 10g...? No backups and No archive log

    All,
    I need to recover the datafile 2 which is for undo tablespace and it is in recover state and i need to recover the data files now .
    But the bad thing is We dont have backup at all and we dont have archive logs (Archive log disabled in the database)...
    In this situation how can i recover the datafile ...?
    SQL> select a.file#,a.name,a.status from v$datafile a,v$tablespace b where a.ts#=b.ts#;
    FILE# NAME STATUS
    1 /export/home/oracle/flexcube/product/10.2.0/db_1/oradata/bwfcc73/system01.dbf SYSTEM
    *2 /export/home/oracle/logs/bw/undotbs01.dbf RECOVER*
    3 /export/home/oracle/flexcube/product/10.2.0/db_1/oradata/bwfcc73/sysaux01.dbf ONLINE
    4 /export/home/oracle/datafiles/bw/bwfcc73.dbf ONLINE
    5 /export/home/oracle/datafiles/bw/bwfcc73_01.dbf ONLINE
    SQL> archive log list;
    Database log mode No Archive Mode
    Automatic archival Disabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 4940
    Current log sequence 4942

    Hi,
    First of all you must Open a ticket with oracle Support and explore the options
    You can use this note to fix it:
    RECOVERING FROM A LOST DATAFILE IN A UNDO TABLESPACE [ID 1013221.6]
    If you is Unable to Drop Undo tablespace Since Undo Segment is in Needs Recovery
    You can Upload the following trace file while opening the ticket
    SQL>Alter session set tracefile_identifier='corrupt';
    SQL>Alter system dump undo header "<new of undo segment in recover status>";
    Go to udump
    ls -lrt *corrupt*
    Upload this trace file
    Also upload the alert log fileRegards,
    Levi Pereira
    Edited by: Levi Pereira on Nov 29, 2011 1:58 PM

  • Database backup with lost archive logs

    How can I get a database backup when all the archive logs have been lost?

    here's the full test of the backup:
    Recovery Manager: Release 9.2.0.7.0 - 64bit Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    RMAN>
    connected to target database: ESKHDEV1 (DBID=4075873486)
    using target database controlfile instead of recovery catalog
    RMAN>
    echo set on
    RMAN> run {
    2> allocate channel oem_backup_disk1 type disk format '/sbdbarc/backups/eskhdev1/%U' maxpiecesize 2000 M;
    3> backup filesperset = 3 tag 'BACKUP_ESKHDEV1_00_101008022533' database;
    4> backup filesperset = 3 tag 'BACKUP_ESKHDEV1_00_101008022533' archivelog all not backed up;
    5> release channel oem_backup_disk1;
    6> }
    allocated channel: oem_backup_disk1
    channel oem_backup_disk1: sid=18 devtype=DISK
    Starting backup at 10-OCT-08
    channel oem_backup_disk1: starting full datafile backupset
    channel oem_backup_disk1: specifying datafile(s) in backupset
    input datafile fno=00013 name=/spte/oracle/oradata/ESKHDEV1/leafdat02.dbf
    input datafile fno=00011 name=/spte/oracle/oradata/ESKHDEV1KLXTEMP.dbf
    input datafile fno=00001 name=/spte/oracle/oradata/ESKHDEV1/system01.dbf
    channel oem_backup_disk1: starting piece 1 at 10-OCT-08
    channel oem_backup_disk1: finished piece 1 at 10-OCT-08
    piece handle=/sbdbarc/backups/eskhdev1/2jjsq87q_1_1 comment=NONE
    channel oem_backup_disk1: backup set complete, elapsed time: 00:00:45
    channel oem_backup_disk1: starting full datafile backupset
    channel oem_backup_disk1: specifying datafile(s) in backupset
    input datafile fno=00002 name=/spte/oracle/oradata/ESKHDEV1/undotbs01.dbf
    input datafile fno=00008 name=/spte/oracle/oradata/ESKHDEV1/tools01.dbf
    input datafile fno=00005 name=/spte/oracle/oradata/ESKHDEV1/example01.dbf
    channel oem_backup_disk1: starting piece 1 at 10-OCT-08
    channel oem_backup_disk1: finished piece 1 at 10-OCT-08
    piece handle=/sbdbarc/backups/eskhdev1/2kjsq897_1_1 comment=NONE
    channel oem_backup_disk1: starting piece 2 at 10-OCT-08
    channel oem_backup_disk1: finished piece 2 at 10-OCT-08
    piece handle=/sbdbarc/backups/eskhdev1/2kjsq897_2_1 comment=NONE
    channel oem_backup_disk1: backup set complete, elapsed time: 00:01:20
    channel oem_backup_disk1: starting full datafile backupset
    channel oem_backup_disk1: specifying datafile(s) in backupset
    input datafile fno=00017 name=/spte/oracle/oradata/ESKHDEV1/parentidx01.dbf
    input datafile fno=00015 name=/spte/oracle/oradata/ESKHDEV1/lral3201.dbf
    input datafile fno=00010 name=/spte/oracle/oradata/ESKHDEV1/xdb01.dbf
    channel oem_backup_disk1: starting piece 1 at 10-OCT-08
    channel oem_backup_disk1: finished piece 1 at 10-OCT-08
    piece handle=/sbdbarc/backups/eskhdev1/2ljsq8bn_1_1 comment=NONE
    channel oem_backup_disk1: backup set complete, elapsed time: 00:01:05
    channel oem_backup_disk1: starting full datafile backupset
    channel oem_backup_disk1: specifying datafile(s) in backupset
    input datafile fno=00012 name=/spte/oracle/oradata/ESKHDEV1/leafdat01.dbf
    input datafile fno=00006 name=/spte/oracle/oradata/ESKHDEV1/indx01.dbf
    input datafile fno=00003 name=/spte/oracle/oradata/ESKHDEV1/cwmlite01.dbf
    channel oem_backup_disk1: starting piece 1 at 10-OCT-08
    channel oem_backup_disk1: finished piece 1 at 10-OCT-08
    piece handle=/sbdbarc/backups/eskhdev1/2mjsq8dp_1_1 comment=NONE
    channel oem_backup_disk1: backup set complete, elapsed time: 00:01:15
    channel oem_backup_disk1: starting full datafile backupset
    channel oem_backup_disk1: specifying datafile(s) in backupset
    input datafile fno=00014 name=/spte/oracle/oradata/ESKHDEV1/leafidx.dbf
    input datafile fno=00009 name=/spte/oracle/oradata/ESKHDEV1/users01.dbf
    input datafile fno=00004 name=/spte/oracle/oradata/ESKHDEV1/drsys01.dbf
    channel oem_backup_disk1: starting piece 1 at 10-OCT-08
    channel oem_backup_disk1: finished piece 1 at 10-OCT-08
    piece handle=/sbdbarc/backups/eskhdev1/2njsq8g4_1_1 comment=NONE
    channel oem_backup_disk1: backup set complete, elapsed time: 00:01:15
    channel oem_backup_disk1: starting full datafile backupset
    channel oem_backup_disk1: specifying datafile(s) in backupset
    input datafile fno=00016 name=/spte/oracle/oradata/ESKHDEV1/parentdat01.dbf
    input datafile fno=00007 name=/spte/oracle/oradata/ESKHDEV1/odm01.dbf
    channel oem_backup_disk1: starting piece 1 at 10-OCT-08
    channel oem_backup_disk1: finished piece 1 at 10-OCT-08
    piece handle=/sbdbarc/backups/eskhdev1/2ojsq8if_1_1 comment=NONE
    channel oem_backup_disk1: backup set complete, elapsed time: 00:01:35
    Finished backup at 10-OCT-08
    Starting backup at 10-OCT-08
    current log archived
    channel oem_backup_disk1: starting archive log backupset
    channel oem_backup_disk1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=1260 recid=1236 stamp=667755183
    channel oem_backup_disk1: starting piece 1 at 10-OCT-08
    channel oem_backup_disk1: finished piece 1 at 10-OCT-08
    piece handle=/sbdbarc/backups/eskhdev1/2pjsq8lf_1_1 comment=NONE
    channel oem_backup_disk1: backup set complete, elapsed time: 00:00:02
    Finished backup at 10-OCT-08
    Starting Control File and SPFILE Autobackup at 10-OCT-08
    piece handle=/sbdbarc/backups/eskhdev1/c-4075873486-20081010-02 comment=NONE
    Finished Control File and SPFILE Autobackup at 10-OCT-08
    released channel: oem_backup_disk1
    RMAN> delete noprompt obsolete device type disk;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=18 devtype=DISK
    Deleting the following obsolete backups and copies:
    Type Key Completion Time Filename/Handle
    Backup Set 2 17-MAR-08
    Backup Piece 2 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_10_1_649591917.rbp
    Backup Set 6 17-MAR-08
    Backup Piece 6 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_14_1_649594217.rbp
    Backup Set 7 17-MAR-08
    Backup Piece 7 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_16_1_649594217.rbp
    Backup Set 8 17-MAR-08
    Backup Piece 8 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_17_1_649594353.rbp
    Backup Set 9 17-MAR-08
    Backup Piece 9 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_19_1_649595236.rbp
    Backup Set 10 17-MAR-08
    Backup Piece 10 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_18_1_649595236.rbp
    Backup Set 11 17-MAR-08
    Backup Piece 11 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_20_1_649595236.rbp
    Backup Set 12 17-MAR-08
    Backup Piece 12 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_21_1_649595381.rbp
    Backup Set 13 17-MAR-08
    Backup Piece 13 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_24_1_649595445.rbp
    Backup Set 14 17-MAR-08
    Backup Piece 14 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_22_1_649595445.rbp
    Backup Set 15 17-MAR-08
    Backup Piece 15 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_23_1_649595445.rbp
    Backup Set 16 17-MAR-08
    Backup Piece 16 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_25_1_649595471.rbp
    Backup Set 17 17-MAR-08
    Backup Piece 17 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_27_1_649604714.rbp
    Backup Set 18 17-MAR-08
    Backup Piece 18 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_26_1_649604714.rbp
    Backup Set 19 17-MAR-08
    Backup Piece 19 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_28_1_649604714.rbp
    Backup Set 20 17-MAR-08
    Backup Piece 20 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_29_1_649604850.rbp
    Backup Set 21 17-MAR-08
    Backup Piece 21 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_31_1_649604923.rbp
    Backup Set 22 17-MAR-08
    Backup Piece 22 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_30_1_649604923.rbp
    Backup Set 23 17-MAR-08
    Backup Piece 23 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_33_1_649606774.rbp
    Backup Set 24 17-MAR-08
    Backup Piece 24 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_32_1_649606774.rbp
    Backup Set 25 17-MAR-08
    Backup Piece 25 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_34_1_649606774.rbp
    Backup Set 26 17-MAR-08
    Backup Piece 26 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_35_1_649606900.rbp
    Backup Set 27 17-MAR-08
    Backup Piece 27 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_37_1_649606970.rbp
    Backup Set 28 17-MAR-08
    Backup Piece 28 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_36_1_649606970.rbp
    Backup Set 29 17-MAR-08
    Backup Piece 29 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_39_1_649607591.rbp
    Backup Set 30 17-MAR-08
    Backup Piece 30 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_38_1_649607591.rbp
    Backup Set 31 17-MAR-08
    Backup Piece 31 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_40_1_649607591.rbp
    Backup Set 32 17-MAR-08
    Backup Piece 32 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_41_1_649607707.rbp
    Backup Set 33 17-MAR-08
    Backup Piece 33 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_43_1_649607785.rbp
    Backup Set 34 17-MAR-08
    Backup Piece 34 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_42_1_649607785.rbp
    Backup Set 35 17-MAR-08
    Backup Piece 35 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_45_1_649609650.rbp
    Backup Set 36 17-MAR-08
    Backup Piece 36 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_44_1_649609650.rbp
    Backup Set 37 17-MAR-08
    Backup Piece 37 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_46_1_649609650.rbp
    Backup Set 38 17-MAR-08
    Backup Piece 38 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_47_1_649609777.rbp
    Backup Set 39 17-MAR-08
    Backup Piece 39 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_49_1_649609840.rbp
    Backup Set 40 17-MAR-08
    Backup Piece 40 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_48_1_649609840.rbp
    Backup Set 41 17-MAR-08
    Backup Piece 41 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_51_1_649611229.rbp
    Backup Set 42 17-MAR-08
    Backup Piece 42 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_50_1_649611229.rbp
    Backup Set 43 17-MAR-08
    Backup Piece 43 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_52_1_649611229.rbp
    Backup Set 44 17-MAR-08
    Backup Piece 44 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_53_1_649611355.rbp
    Backup Set 45 17-MAR-08
    Backup Piece 45 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_55_1_649611419.rbp
    Backup Set 46 17-MAR-08
    Backup Piece 46 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_54_1_649611419.rbp
    Backup Set 47 17-MAR-08
    Backup Piece 47 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_57_1_649612920.rbp
    Backup Set 48 17-MAR-08
    Backup Piece 48 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_56_1_649612920.rbp
    Backup Set 49 17-MAR-08
    Backup Piece 49 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_58_1_649612920.rbp
    Backup Set 50 17-MAR-08
    Backup Piece 50 17-MAR-08 /spte/oracle/backups/eskhdev1/df_ESKHDEV1_59_1_649613075.rbp
    Backup Set 51 17-MAR-08
    Backup Piece 51 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_61_1_649613158.rbp
    Backup Set 52 17-MAR-08
    Backup Piece 52 17-MAR-08 /spte/oracle/backups/eskhdev1/al_ESKHDEV1_60_1_649613158.rbp
    Backup Set 66 10-OCT-08
    Backup Piece 68 10-OCT-08 /sbdbarc/backups/eskhdev1/2bjsppct_1_1
    Backup Set 67 10-OCT-08
    Backup Piece 69 10-OCT-08 /sbdbarc/backups/eskhdev1/2cjsppea_1_1
    Backup Piece 70 10-OCT-08 /sbdbarc/backups/eskhdev1/2cjsppea_2_1
    Backup Set 68 10-OCT-08
    Backup Piece 71 10-OCT-08 /sbdbarc/backups/eskhdev1/2djsppgq_1_1
    Backup Set 69 10-OCT-08
    Backup Piece 72 10-OCT-08 /sbdbarc/backups/eskhdev1/2ejsppir_1_1
    Backup Set 70 10-OCT-08
    Backup Piece 73 10-OCT-08 /sbdbarc/backups/eskhdev1/2fjsppl6_1_1
    Backup Set 71 10-OCT-08
    Backup Piece 74 10-OCT-08 /sbdbarc/backups/eskhdev1/2gjsppnh_1_1
    Backup Set 72 10-OCT-08
    Backup Piece 75 10-OCT-08 /sbdbarc/backups/eskhdev1/c-4075873486-20081010-00
    Backup Set 73 10-OCT-08
    Backup Piece 76 10-OCT-08 /sbdbarc/backups/eskhdev1/c-4075873486-20081010-01
    deleted backup piece
    backup piece handle=/sbdbarc/backups/eskhdev1/2bjsppct_1_1 recid=68 stamp=667739549
    deleted backup piece
    backup piece handle=/sbdbarc/backups/eskhdev1/2cjsppea_1_1 recid=69 stamp=667739594
    deleted backup piece
    backup piece handle=/sbdbarc/backups/eskhdev1/2cjsppea_2_1 recid=70 stamp=667739639
    deleted backup piece
    backup piece handle=/sbdbarc/backups/eskhdev1/2djsppgq_1_1 recid=71 stamp=667739674
    deleted backup piece
    backup piece handle=/sbdbarc/backups/eskhdev1/2ejsppir_1_1 recid=72 stamp=667739739
    deleted backup piece
    backup piece handle=/sbdbarc/backups/eskhdev1/2fjsppl6_1_1 recid=73 stamp=667739814
    deleted backup piece
    backup piece handle=/sbdbarc/backups/eskhdev1/2gjsppnh_1_1 recid=74 stamp=667739889
    deleted backup piece
    backup piece handle=/sbdbarc/backups/eskhdev1/c-4075873486-20081010-00 recid=75 stamp=667739965
    deleted backup piece
    backup piece handle=/sbdbarc/backups/eskhdev1/c-4075873486-20081010-01 recid=76 stamp=667742372
    Deleted 9 objects
    RMAN-06207: WARNING: 48 objects could not be deleted for DISK channel(s) due
    RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status
    List of Mismatched objects
    ==========================
    Object Type Filename/Handle
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_10_1_649591917.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_14_1_649594217.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_16_1_649594217.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_17_1_649594353.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_19_1_649595236.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_18_1_649595236.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_20_1_649595236.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_21_1_649595381.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_24_1_649595445.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_22_1_649595445.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_23_1_649595445.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_25_1_649595471.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_27_1_649604714.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_26_1_649604714.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_28_1_649604714.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_29_1_649604850.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_31_1_649604923.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_30_1_649604923.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_33_1_649606774.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_32_1_649606774.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_34_1_649606774.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_35_1_649606900.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_37_1_649606970.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_36_1_649606970.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_39_1_649607591.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_38_1_649607591.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_40_1_649607591.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_41_1_649607707.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_43_1_649607785.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_42_1_649607785.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_45_1_649609650.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_44_1_649609650.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_46_1_649609650.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_47_1_649609777.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_49_1_649609840.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_48_1_649609840.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_51_1_649611229.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_50_1_649611229.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_52_1_649611229.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_53_1_649611355.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_55_1_649611419.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_54_1_649611419.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_57_1_649612920.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_56_1_649612920.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_58_1_649612920.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/df_ESKHDEV1_59_1_649613075.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_61_1_649613158.rbp
    Backup Piece /spte/oracle/backups/eskhdev1/al_ESKHDEV1_60_1_649613158.rbp
    RMAN> release channel;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of release command at 10/10/2008 15:33:09
    RMAN-06474: maintenance channels are not allocated
    RMAN> exit;
    Recovery Manager complete.

  • APO Livecache DB Backup and Livecache Auto Log Backup

    Hi Guys,
    Could you please help me here which tranaction code we use to  check APO Livecache DB Backup and Livecache Auto Log Backup
    Thank you

    Hi,
    Livecache DB and log back up looks like can not be accessed from SAP. Database Manager GUI is used.
    Please check the below link for helpful information.
    http://help.sap.com/saphelp_nw04/helpdata/en/f7/499e3c1fbe8c15e10000000a114084/content.htm
    Regards,
    Saravanan V

  • HT4972 i already follow the instruction that u told, but all my apps gone and i need to re-install it. how can i find that backup, and backup my phone?

    i already follow the instruction that u told, but all my apps gone and i need to re-install it. how can i find that backup, and backup my phone?

    Who is "u", and how could the rest of us know what "instructions" you followed or how you backed up your phone??

  • Oracle Restore from Online backup without any archive logs

    Hi,
    May be a dumb question. If I have a good online backup (say it took 2 hours to do that. And there is database activity while backup is going on), and lost all the archive logs happened after the online backup, is it possible at all to do the restore using that backup? complete or incomplete? and bring back the database to normal operation mode? Some details on this.
    Thanks.

    Let us see the reasoning behind this.
    Database:WORLDDB
    WORLDDB configuration:-
    TBSP_WDB
    ->TBSP_WDB_01.dbf
    ->TBSP_WDB_02.dbf
    SYSTEM
    ->SYSTEM.dbf
    USERS
    and so on for the tablespaces.
    CASE 1:-
    User managed backup.
    You issue
    ALTER TABLESPACE TBSP_WDB BEGIN BACKUP;
    DB keeps working all transactions are recorded in the redo stream, the scn information is not updated in the file header.
    Also note that the other tablespaces were been continuously worked on hence their scn numbers are a moving target.
    http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96572/osbackups.htm#10012
    So if you begin tablespace TBSP_WDB backup at time t1 and by the time you are done with your backups you are at time t2, you will need all of the archive log's between time t1 and t2.
    CASE 2:-
    If we do with rman, rman takes care of the file header update information and goes on its merry way, those details are hidden from the end user. If one of the tablespace is fractured, updated while backups are going on , rman knows about it and will re-read the affected blocks in question.
    My thinking would be that you might need archive logs, unless it is a cold backup, with switch logfiles in between.
    If you do hot backups you need archivelogs is my thought. The number of archivelogs required will be decreased considerably through rman.
    http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmconc1.htm#458821
    Summary:-
    Either way archivelogs are needed.

  • Full format and backup everytime?

    is it possible to have time machine simply erase everything and backup a fresh full backup every time instead of backing up dates and etc?
    or should i just use superduper?

    ERROR
    This backup is too large for the backup disk. The backup requires 95.40 GB but only 84.67 GB are available.
    Latest successful backup: 3/14/10 at 3:35 AM
    here's what i got in the system.log
    May 20 13:12:49 users-macbook-pro com.apple.backupd[40687]: Starting standard backup
    May 20 13:12:50 users-macbook-pro com.apple.backupd[40687]: Backing up to: /Volumes/My Passport/Backups.backupdb
    May 20 13:12:52 users-macbook-pro com.apple.backupd[40687]: Event store UUIDs don't match for volume: Macintosh HD
    May 20 13:12:52 users-macbook-pro com.apple.backupd[40687]: Forcing deep traversal on source: "Macintosh HD" (mount: '/' fsUUID: 35800EAF-6F2C-3877-9CFA-E3D39B55252C eventDBUUID: 40309C01-31B4-47DC-A329-57B974E37E3C), {1, 1, 1, 0}
    May 20 13:12:53 users-macbook-pro com.apple.backupd[40687]: Node requires deep traversal:/ reason:must scan subdirs|require scan|
    May 20 13:22:54 users-macbook-pro com.apple.backupd[40687]: Starting pre-backup thinning: 88.85 GB requested (including padding), 78.86 GB available
    May 20 13:22:54 users-macbook-pro com.apple.backupd[40687]: No expired backups exist - deleting oldest backups to make room
    May 20 13:22:54 users-macbook-pro com.apple.backupd[40687]: Error: backup disk is full - all 0 possible backups were removed, but space is still needed.
    May 20 13:22:54 users-macbook-pro com.apple.backupd[40687]: Backup Failed: unable to free 88.85 GB needed space
    May 20 13:22:59 users-macbook-pro com.apple.backupd[40687]: Backup failed with error: Not enough available disk space on the target volume.

  • Rman backup and restore noarchive log

    Hi,
    We are changing our backup tools from exp to rman. For this I am trying to do
    restoration in test server of oracle db running on 9.2 noarchive log.
    Step 1. Taken complete backup with rman with nocatalog and include controlfile
    nput datafile fno=00008 name=D:\ORACLE\ORADATA\TOTO\TOOLS01.DBF
    channel ORA_DISK_1: starting piece 1 at 09-MAR-06
    channel ORA_DISK_1: finished piece 1 at 09-MAR-06
    piece handle=D:\DBBACKUPS\T1.BKP comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
    Finished backup at 09-MAR-06
    Step 2. Deleted database files and control files from database directory.
    Step 3. Restore controlfiles
    RMAN> restore controlfile from 'd:\dbbackups\t1.bkp';
    Starting restore at 09-MAR-06
    using channel ORA_DISK_1
    channel ORA_DISK_1: restoring controlfile
    channel ORA_DISK_1: restore complete
    replicating controlfile
    input filename=D:\ORACLE\ORADATA\TOTO\CONTROL01.CTL
    output filename=D:\ORACLE\ORADATA\TOTO\CONTROL02.CTL
    output filename=D:\ORACLE\ORADATA\TOTO\CONTROL03.CTL
    Finished restore at 09-MAR-06
    Step 3. after database mount, try to restore datafiles, which is failed
    restoring datafile 00024 to D:\ORACLE\ORADATA\TOTO\DIN36\TESTUNV1.ORA
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 03/09/2006 17:24:25
    ORA-19505: failed to identify file "D:\DBBACKUPS\TOTOBKP.RMAN"
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    Why it is looking old backup totobkp.rman which is not existing on disk ? My
    backup name is t1.bkp.
    Will you pl tell me where I have gone wrong ? Secondly what are the correct
    steps to be followed for taking cold backup and restoration.
    thanks & regards
    pjp

    Okay let us ponder this for a moment:-
    DB NOARCHIVELOG
    It does not matter when you take the backup of controlfile because the database is in mount state and no changes are allowed to the db ( Checkpoints etc. )
    DB ARCHIVELOG
    It does not matter when you take the backup of controlfile because the database is continuously writing to the archivelog's.
    End result should not be significantly different as to worry about whether to take backup of control file before or after backup.
    Thanks
    Gopal

  • Primary/standby and 3rd archive log destination?

    Running Oracle EE 10.2.0.4 linux 64 bit. I have a primary and standby configuration using data guard, with appropriate LOG_ARCHIVE_DEST_1, LOG_ARCHIVE_DEST_2 for the primary and standby - all works as expected. I want to multiplex the log files by adding a 3rd archive log destination to a different disk. I'm not clear on whether or not specifying a second 'primary' archive destination will write to both dest_1 and dest_3 or just alternate between the 2? I want to make sure that both DEST_1 and DEST_3 are written to (there can be a lag for DEST_3) -
    Is the following all I need or are there additional parameters to LOG_ARCHIVE_DEST_n I'm missing?
    LOG_ARCHIVE_DEST_3 = 'valid_for=(ONLINE_LOGFILE,ALL_ROLES)', 'location="/myThirdLoc"'
    Thanks -

    The database hang because of the redo log file is full. my test database is 16.7G and I gave the recovery filesystem 19 G for the redo log. Apparently it is not enough. After i set up the backup with daily incremental and run for 5 days, the recovery is full and db hang. How do you free up the space or set up the backup so that it can recycle the space? My DB is 10g r2 on RHEL3.

  • How can I move the download backups and backups folder to a new location

    I am using Lightroom 4.3 on a windows 7 64 windows computer with two hard drives.  One dedicated to running programs and the larger one for storage of all my other stuff.  Well my backups and download backups folders are on the smaller drive and I need to move them to the other larger drive. Can I do this without totally freaking Lightroom out?  Thank you so much for your help.

    I am not familiar with the technical term "freaking Lightroom out", however, Lightroom doesn't care where the backups are. You can do anything you want with them, and Lightroom will work fine.

  • Compress and Ship Archive Logs to DR

    I am currently working on Oracle 10.2.0.3, Linux 5.5 DR Setup. DR is at a remote location. Automatic Synchronous Archive shipping is enabled. As the DR is at a remote location transferring 500MB archive logs has a load on the bandwitdh. Is there anyway I can compress and send the archivelogs to DR? I am aware of the 11g parameter Compression=enabled, but i guess theres nothing on similiar lines for 10g.
    Kindly help!
    Regards,
    Bhavi Savla.

    AliD wrote:
    What is "Automatic Synchronous Archive shipping"? Do you mean your standby is in MAXPROTECTION or MAXAVAILABILITY mode? I fail to see how transfering only 500MB of data to anywhere is a problem. Your system should be next to idle!
    Compression is an 11g feature and is licensed (advanced compression license). Also if I'm not mistaken, 10.2.0.3 is out of support. You should plan to upgrade it as soon as possible.
    Edit - It seems you mean your archivelogs are 500MB each not total of 500MB for the day. In that case to eliminate the peaks in transfer, use LGWR in async mode.
    Edited by: AliD on 10/05/2012 23:24It is a problem as we have archives generating very frequently!!!

  • Dataguard sync and applying archive log

    Just did a check on my primary and standby using:
    Primary:
    SELECT max(sequence#) AS "PRIMARY" FROM v$log_history;
    PRIMARY
    45527
    Standby:
    SELECT max(sequence#) AS "STANDBY", applied FROM v$archived_log GROUP BY applied:
    STANDBY APP
    45476 NO
    45528 YES
    My question is how do I fix my sync?

    SQL> select OPEN_MODE  from v$database;
    OPEN_MODE
    MOUNTED
    SQL> recover standby database until cancel;
    ORA-01153: an incompatible media recovery is active
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    Database altered.
    SQL> recover standby database until cancel;
    ORA-00279: change 4558008 generated at 08/21/2010 14:02:39 needed for thread 1
    ORA-00289: suggestion : /data_gpfs/oracle/archivelogs/1_112_726952005.dbf
    ORA-00280: change 4558008 for thread 1 is in sequence #112
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    */data_gpfs/oracle/archivelogs/2_118_726952005.dbf*
    ORA-00325: archived log for thread 1, wrong thread # 2 in header
    ORA-00334: archived log: '/data_gpfs/oracle/archivelogs/2_118_726952005.dbf'

  • Automated Backup and Backup Jobs

    While I install oracle 11g release 2 the installer asked me :-
    if I want to enable or disable automated backups for my database. if enabled, then the backup jobs uses
    the specified recovery area storage
    Please help me to get knowledge about
    1- the automated backups
    2- the recovery area storage
    Thanks a lot.

    1)If you configure automated backups, oracle will run rman daily backup to backup all datafiles to flash recovery area
    http://docs.oracle.com/html/B14399_01/install_overview.htm
    2)configure flash recovery area using db_recovery_file_dest and db_recovery_file_dest_size.
    Flash recovery area is the area where you can store permanent and transient files (like backups)
    http://docs.oracle.com/cd/B19306_01/backup.102/b14192/setup005.htm

  • What is your backup and/or archive workflow?

    I am a wedding photographer who has been using Ap for a few months now, and am trying to come up with a good backup system and a method to archive projects to save space on my MacBook Pro.
    Here is my simple workflow. I'd appreciate any recommendations for improving it.
    1. After a shoot I import all images directly into Aperture (managed). A typical wedding will yield 10-20 gigs of raw files (depends on number of shooters and how long).
    2. After importing, I update my Ap Vault on a 500gb external FW800 drive.
    3. As I work on the image the next few weeks I update my vault every day.
    4. When I'm completely done with the project I export the whole project to an "archives" folder on my external drive, and then delete it from my aperture library.
    5. I then update my vault again.
    6. Therefore, my vault only contains a backup of projects I'm currently working on (and are in my main aperture library), and I have a file with a growing number of individual projects that have been archived. If I want to access pictures from another project I have to re-import that project into my main library, and then delete it when I'm done.
    QUESTIONS:
    - Would it be easier for me to put all those archived projects into a second library for fast retrieval? How would you do that (I've noticed you can directly drag-n-drop them into the Apperture package...)?
    - Would your recommend also backing up to an optical media, even though the projects are so large (20gb)?
    - How can I use multiple vaults and/or libraries to make my life easier?
    Thanks in advance for your help!

    After all your advice, I think I definitely will start referencing to my images on an external drive. I'll keep current projects on my local HDD, but after I'm done with one I'll move the referenced images to an external drive for archival purposes. I'll also use a combination of external drives and DVDs to backup (I'll never use solely optical media as I've had to learn the hard way about the long-term integrity of optical discs....)
    When all is said an done, I imagine my workflow will work something like this:
    1. Shoot a wedding, importing all images into Aperture and referencing to all masters in a local folder.
    2. After the wedding, immediately backup the project (including referenced files) to a portable firewire drive.
    3. When I'm done working with the images, move the referenced files to an external "archive" drive.
    4. Export the project (including referenced files) to a double layer DVD and stick it in the clients folder with other paperwork, etc.
    5. Update my Aperture Vault (including referenced images) to a separate "backup" drive.
    This way I will have all my older images on an "archive" drive and linked to AP for easy reference. I'll also have DVD backups of each project, plus a huge backup drive with my AP vault with ALL projects and images. When this drive fills up, I'll buy a new one. Hard drives are cheap, and getting cheaper. Besides, that's just the cost of doing business.
    Hopefully future version of AP will have integrated DVD burning, and the ability to span a project across multiple discs.

Maybe you are looking for