RMAN full backup - size SPFile Total 0.00 K

Hello, I do some tests and I need help to understand if there is something wrong in what I'm trying to do (a full backup with RMAN, DB is 11 GR 2).

If I perform a simple full DB Backup, all past file and it completes successfully. No errors.

Controlfile Autobackup is enabled, so I expect to find the control file and SPFile included in the backup, too.

But if I go to Console 'EM-> availability-> backup reports

It is reported the following:

---
Entry summary

Data file
Backup files 8
Separate files 8
Tablespaces separate 7
Total size 11.16 G
More former Checkpoint time Aug 29, 2011 01:00:29
Most recent Checkpoint time Aug 29, 2011 01:04:37

Control file
Backup files 1
Separate files 1
Total 22.95 M size
More former Checkpoint time Aug 29, 2011 01:05:44
Most recent Checkpoint time Aug 29, 2011 01:05:44

SPFile
Backup files 1
Separate files 1
Size total 0.00 K
More old time change Aug 29, 2011 01:02:12
Last Modification time Aug 29, 2011 01:02:12
---


Looks SPFile size on backup is '0' and not what I was expecting (SPFile is actually being used and it is not empty).

Should what kind of verification I do to see if everything is OK? Maybe a non-destructive.

Thank you very much!

Hello R,

(1) the SPFile will be restored in a custom location / name of my choice ("spfile_restore.ora")
which may be different from the ACTIVE SPFile

I would say that must be different from the current spfile...

(2) the SPFile ACTIVE will always be in place and will always be that "in use" even after restoring

Correct the restored spfile will not be part of any oracle process.
Kind regards
Tycho

Tags: Database

Similar Questions

  • Need to restore only 1 scheme of rman full backup

    Hi all

    Database version: 11.1
    Linux x86_64

    I dropped one of the user of our existing OEM repository database.
    I want to restore it from the backup rman I know you cannot restore only 1 user in the rman.
    I have not any expdp for users.
    can I use rman restore time and recovery point
    Please guide me with step by step restoration.
    also only the user schemas has been deleted and not the tablespace or anything like that.
    No flashback created restore point.

    Thank you

    Hello again;

    The binaries would be the Oracle software. This will not affect that.

    Make a full stop and then the four commands that I listed before replacing your Date / time.

    Also called a "recovery incomplete rman.

    Best regards

    mseberg

  • RMAN how to handle simple full backups every day with the archivelogs



    Hello

    My use of Oracle DB is about 200 GB on a file system 1 TB from a NetApp file server. (i.e. 20% currently use)

    I'm not so attracted to use the RMAN catalog for the love of simplicity.

    Also, I have an affinity to run a full backup "Instant NetApp" every day, without running all the incremental backups.

    My snapshots of NetApp have a framework for the retention of 7 days.

    I think to implement a RMAN full backup script that includes the following to run every night:

    Run {}

    delete archivelog all;                    (to clean up the archive logs that are accumulated for each day)

    backup database;                          (for a full backup every night)

    }

    This will be a good idea?

    Will this coverage to back up all that I could restore if there is a problem.


    Part of the great mystery for me is on the restoration of the data that is generated during the execution of the "backup database" command in the RMAN.

    Any advice would be appreciated.

    Thank you!

    -Steve

    If you perform the backup in this order, you will get in big trouble.

    It is preferable to run the backup as follows:

    (1) the following parameters, you have to do only once:

    configure backup optimization

    Configure retention policy to recovery of 7-day window;

    Configure controlfile autobackup on;

    (2) backup every day:

    backup database more entered archivelog delete;

    delete noprompt obsolete;

    unrecoverable report;

    RMAN automatically takes care of cleaning the old backups<7 days="" and="" saved="">

    Concerning

    Patrick

  • Full backup to optimize backup RMAN

    Hi gurus,

    I wanted to implement the functionality of rman backup optimization. I did a little test to verify its use and not found helpful whenever I do a full backup to backup all data files and nothing is ignored.

    According to the ORACLE notes as below, ideally, once I backup the database, the backup else should jump not all files.


    If you enable Backup Optimization and then the BACKUP command ignores backup files when the identical file has already been saved on the specified device type.


    Please note that it's my test server and no connections are on the DB. Listener is broken. If no point of change Yvert. I'm missing here something?

    Oracle - 11.2.0.4 version

    RMAN > run

    2 > {allocate channel ch1 type

    3 > disc format ' / oraback/RMAN/%d_DB_%u_%s_%p';

    4 > backup database;

    {5 >}

    allocated channel: ch1

    channel ch1: SID = 172 type device = DISK

    From April 28, 15 backup

    channel ch1: start the backup set full datafile

    channel ch1: specification-datafile in the backup set (s)

    Enter a number of file datafile = 00001 name=/u01/oradata/nmsdata/system01.dbf

    Enter a number of file datafile = name=/u04/oradata/nmsdata/NMSINFO_DATA01_02.dbf 00006

    Enter a number of file datafile = 00005 name=/u04/oradata/nmsdata/NMSINFO_DATA01_01.dbf

    Enter a number of file datafile = name=/u03/oradata/nmsdata/NMSINFO_INDX01.dbf 00007

    Enter a number of file datafile = name=/u01/oradata/nmsdata/undotbs01.dbf 00003

    Enter a number of file datafile = name=/u01/oradata/nmsdata/sysaux01.dbf 00002

    channel ch1: from room 1 to 28 April 15

    channel ch1: finished piece 1 at 28 April 15

    total, handle = / oraback/RMAN/NMSDATA_DB_ngq5g2vv_71408_1 tag = comment TAG20150428T042431 = NONE

    channel ch1: complete set of backups, time: 00:00:25

    channel ch1: start the backup set full datafile

    channel ch1: specification-datafile in the backup set (s)

    Enter a number of file datafile = name=/u01/oradata/nmsdata/users01.dbf 00004

    channel ch1: from room 1 to 28 April 15

    channel ch1: finished piece 1 at 28 April 15

    total, handle = / oraback/RMAN/NMSDATA_DB_nhq5g30o_71409_1 tag = comment TAG20150428T042431 = NONE

    channel ch1: complete set of backups, time: 00:00:01

    Backup finished April 28, 15

    From control file and SPFILE Autobackup 28 April 15

    room handle=/opt/app/oracle/product/11.2.0.4_ee/dbs/c-3349937142-20150428-00 comment = NONE

    File control finished and Autobackup SPFILE to 28 April 15

    output channel: ch1

    RMAN > show all.

    RMAN settings for database with db_unique_name CHNMCPRDB1_NMSDATA are:

    CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;

    CONFIGURE BACKUP OPTIMIZATION # by default

    SET UP DEFAULT DISK DEVICE TYPE; # by default

    CONFIGURE CONTROLFILE AUTOBACKUP ON;

    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F"

    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default

    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default

    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default

    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 1 ' ${backup_dir}/${ORACLE_SID}/%d_t%t_s%s_p%p';}

    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / oraback/RMAN;

    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default

    CONFIGURE ENCRYPTION OF DATABASE # by default

    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default

    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default

    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default

    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / tmp/nmsdata_snapshot_arch.ctl ';

    RMAN > set UP OPTIMIZATION BACKUP;

    new RMAN configuration settings:

    CONFIGURE BACKUP OPTIMIZATION

    new RMAN configuration settings are stored successfully

    RMAN > run

    {allocate channel ch1 type

    disc format ' / oraback/RMAN/%d_DB_%u_%s_%p';

    backup database;

    }

    2 > 3 > 4 > 5 >

    allocated channel: ch1

    channel ch1: SID = 172 type device = DISK

    From April 28, 15 backup

    channel ch1: start the backup set full datafile

    channel ch1: specification-datafile in the backup set (s)

    Enter a number of file datafile = 00001 name=/u01/oradata/nmsdata/system01.dbf

    Enter a number of file datafile = name=/u04/oradata/nmsdata/NMSINFO_DATA01_02.dbf 00006

    Enter a number of file datafile = 00005 name=/u04/oradata/nmsdata/NMSINFO_DATA01_01.dbf

    Enter a number of file datafile = name=/u03/oradata/nmsdata/NMSINFO_INDX01.dbf 00007

    Enter a number of file datafile = name=/u01/oradata/nmsdata/undotbs01.dbf 00003

    Enter a number of file datafile = name=/u01/oradata/nmsdata/sysaux01.dbf 00002

    channel ch1: from room 1 to 28 April 15

    channel ch1: finished piece 1 at 28 April 15

    total, handle = / oraback/RMAN/NMSDATA_DB_njq5g509_71411_1 tag = comment TAG20150428T045849 = NONE

    channel ch1: complete set of backups, time: 00:00:25

    channel ch1: start the backup set full datafile

    channel ch1: specification-datafile in the backup set (s)

    Enter a number of file datafile = name=/u01/oradata/nmsdata/users01.dbf 00004

    channel ch1: from room 1 to 28 April 15

    channel ch1: finished piece 1 at 28 April 15

    total, handle = / oraback/RMAN/NMSDATA_DB_nkq5g512_71412_1 tag = comment TAG20150428T045849 = NONE

    channel ch1: complete set of backups, time: 00:00:01

    Backup finished April 28, 15

    From control file and SPFILE Autobackup 28 April 15

    piece handle=/opt/app/oracle/product/11.2.0.4_ee/dbs/c-3349937142-20150428-01 comment = NONE

    File control finished and Autobackup SPFILE to 28 April 15

    output channel: ch1

    RMAN > exit

    LANCERIQUE wrote:

    Hi Tom,

    Well well, then that contradicts what oracle mentioned in the docs?

    Not at all.  It does that contradict your understanding of what constitutes a data file "changed."

    Also, I pulled data backup and not backup tablespace.

    Is not serious. The principle is the same.

    Also check your statement my understand that if there are 100 files of data and rarely used, Yvert will be updated for each of them?

    If they are not unalterable, then Yes.  That's how oracle ensures consistency between the data files.

    Kind regards

    Nikhil Mehta.

  • Why is iCloud nearly full storage? My backup size is only 2.2 GB.

    During the last two weeks I received emails from [email protected] saying:

    "Your iCloud-storage space is almost full. You have 440.1 MB remaining 5 GB of total storage. »

    Yet, as shown in the photo below, my iPhone backup size is only 2.2 GB. I use iOS 9.3.2 and have only an iPhone 6 64 GB, which is not jail broken, on the iCloud account. I iCloud drive, but I use it for only four apps and the total size of their files is only 14.2 MB. I do not use iCloud photo library, My Photo Stream or iCloud, photo sharing.

    What can be using the other 2.7 + GB of storage iCloud?

    Do you have other devices using the same Apple ID?

    They can use some of your iCloud space.

  • Problem with the archive log when you use RMAN for backup and restore (11g 2)

    Hello world
    Please help me solve this problem.
    I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
    -First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:
    run{
    allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ;
    backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile;
    backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input;
    crosscheck archivelog all;
    crosscheck backup;
    delete noprompt obsolete;
    release channel bkp;
    }


    D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:

    run{
    allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ;
    backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile;
    backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input;
    crosscheck archivelog all;
    crosscheck backup;
    delete noprompt obsolete;
    release channel bkp;
    }

    Repeat 7 times (Monday-> Saturday). And I got these files:

    [oracle@rac ~]$ ls -l /u01/backup/
    total 400280
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 07:23 c-1428943247-20160120-01
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:04 c-1428943247-20160120-02
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:05 c-1428943247-20160120-03
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:06 c-1428943247-20160120-04
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-05
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-06
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:09 c-1428943247-20160120-07
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:32 c-1428943247-20160120-08
    -rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1
    -rw-r----- 1 oracle oinstall   2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1
    -rw-r----- 1 oracle oinstall   4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1
    -rw-r----- 1 oracle oinstall  11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1
    -rw-r----- 1 oracle oinstall    146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1
    -rw-r----- 1 oracle oinstall    884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1
    -rw-r----- 1 oracle oinstall     82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1
    -rw-r----- 1 oracle oinstall    294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1
    -rw-r----- 1 oracle oinstall     18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1
    -rw-r----- 1 oracle oinstall    155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1
    -rw-r----- 1 oracle oinstall    131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1
    -rw-r----- 1 oracle oinstall    647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1
    -rw-r----- 1 oracle oinstall      8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1
    -rw-r----- 1 oracle oinstall   2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1
    -rw-r----- 1 oracle oinstall   1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1
    -rw-r----- 1 oracle oinstall    327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1

    And
    RMAN> list backup summary;
    List of Backups
    ===============
    Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
    ------- -- -- - ----------- --------------- ------- ------- ---------- ---
    80      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
    81      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
    82      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
    83      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
    84      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
    85      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T072332
    86      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    87      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    88      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    89      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080440
    90      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    91      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    92      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    93      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080545
    94      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    95      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    96      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    97      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080657
    98      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    99      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    100     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    101     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080801
    102     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    103     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    104     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    105     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080844
    106     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    107     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    108     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC

    My configuration of rman:
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name ORCL are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    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   '/u01/backup/backup_df%t_s%s_s%p';
    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 '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default

    - Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here.
    RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08';
    Starting restore at 20-JAN-16
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=18 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=20 device type=DISK
    channel ORA_DISK_2: skipped, AUTOBACKUP already found
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:09
    output file name=/u01/app/oracle/oradata/orcl/control01.ctl
    output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl
    Finished restore at 20-JAN-16

    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    released channel: ORA_DISK_2

    RMAN> restore database;
    Starting restore at 20-JAN-16
    Starting implicit crosscheck backup at 20-JAN-16
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=20 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=18 device type=DISK
    Crosschecked 29 objects
    Finished implicit crosscheck backup at 20-JAN-16

    Starting implicit crosscheck copy at 20-JAN-16
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    Finished implicit crosscheck copy at 20-JAN-16

    searching for all files in the recovery area
    cataloging files...
    no files cataloged

    using channel ORA_DISK_1
    using channel ORA_DISK_2

    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
    channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
    channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
    channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf
    channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf
    channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1
    channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:15
    Finished restore at 20-JAN-16

    -Fourth, the problem here, I got the database;
    .. .every oky until this line...
    starting media recovery

    channel ORA_DISK_1: starting archived log restore to default destination
    channel ORA_DISK_1: restoring archived log
    archived log thread=1 sequence=15
    channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1
    channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15
    unable to find archived log
    archived log thread=1 sequence=1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 01/20/2016 08:50:22
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841

    The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?)
    RMAN> list backup of archivelog all;
    List of Backup Sets
    ===================
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    82      2.16M      DISK        00:00:00     20-JAN-16     
            BP Key: 82   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
            Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1

      List of Archived Logs in backup set 82
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
    1    1       1154833    20-JAN-16 1177422    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    83      3.88M      DISK        00:00:00     20-JAN-16     
            BP Key: 83   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
            Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1

      List of Archived Logs in backup set 83
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
    1    1       1162729    20-JAN-16 1188784    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    84      10.68M     DISK        00:00:01     20-JAN-16     
            BP Key: 84   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
            Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1

      List of Archived Logs in backup set 84
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    2       1177422    20-JAN-16 1201833    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    88      1.81M      DISK        00:00:01     20-JAN-16     
            BP Key: 88   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1

      List of Archived Logs in backup set 88
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    3       1201833    20-JAN-16 1204844    20-JAN-16
      1    4       1204844    20-JAN-16 1204893    20-JAN-16
      1    5       1204893    20-JAN-16 1204958    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    92      143.00K    DISK        00:00:00     20-JAN-16     
            BP Key: 92   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1

      List of Archived Logs in backup set 92
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    6       1204958    20-JAN-16 1205034    20-JAN-16
      1    7       1205034    20-JAN-16 1205253    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    96      80.00K     DISK        00:00:00     20-JAN-16     
            BP Key: 96   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1

      List of Archived Logs in backup set 96
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    8       1205253    20-JAN-16 1205354    20-JAN-16
      1    9       1205354    20-JAN-16 1205433    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    100     18.00K     DISK        00:00:00     20-JAN-16     
            BP Key: 100   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1

      List of Archived Logs in backup set 100
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    10      1205433    20-JAN-16 1205519    20-JAN-16
      1    11      1205519    20-JAN-16 1205559    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    104     128.00K    DISK        00:00:00     20-JAN-16     
            BP Key: 104   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1

      List of Archived Logs in backup set 104
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    12      1205559    20-JAN-16 1205624    20-JAN-16
      1    13      1205624    20-JAN-16 1205739    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    108     8.00K      DISK        00:00:00     20-JAN-16     
            BP Key: 108   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1

      List of Archived Logs in backup set 108
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    14      1205739    20-JAN-16 1205796    20-JAN-16
      1    15      1205796    20-JAN-16 1205840    20-JAN-16


    If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.

    Sorry for a long post.

    > 1 and from the 1205841 SNA sequence

    The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840).

    The message

    channel ORA_DISK_1: restoring archives Journal

    Archives journal thread = 1 sequence = 15

    channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading

    channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC

    indicates that he has restored the sequence up to 15

    You can check the log file alert database instance for messages on the fact of recovery.

    He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15.

    Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve.  An uncomitted transaction is cancelled.

    Hemant K Collette

  • RMAN incremental backup continue to make backups "complete"?

    Hello, I am new to RMAN. I used only the full backup by RMAN, and it was OK. Now, due to lack of disk space, I decided to make incremental backups.

    I put 'to recovey retention policy window of 3 days; then made a new backup (by MS) job, looks like:

    $rman_script = ' backup database cumulative device type disk tag '% TAG' extra strength 1;

    backup disc tag '% TAG' type device archivelog all not saved delete all entries;

    But, always visible, size of the backup is the same all the time as a full backup? Where is my mistake?

    This is a backup log:

    RMAN > database backup incremental level 1 cumulative device type disk tag "BACKUP_DB10_00002_070413021501".

    From backup 4 July 13

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: sid = 1043 devtype = DISK

    channel ORA_DISK_1: additional start-up compressed 1 datafile backupset

    channel ORA_DISK_1: specifying datafile (s) in backupset

    input datafile fno = name=/database/app/oracle/oradata/db/tablespace1.dbf 00007

    input datafile fno = name=/database/app/oracle/oradata/db/tablespace2.dbf 00002

    ...

    channel ORA_DISK_1: starting total, 1 to 4 July 13

    channel ORA_DISK_1: finished piece 1 to 4 July 13

    piece handle=/backup/oracle/flash_recovery_area/db/backupset/2013_07_04/o1_mf_nnnd1_BACKUP_DB10_00002_0_8x9d45f5_.bkp tag = BACKUP_DB10_00002_070413021501 comment = NONE

    channel ORA_DISK_1: complete set of backups, time: 00:41:15

    Backup finished on 4 July 13

    > database backup incremental level 1 cumulative device type disk tag "BACKUP_DB10_00002_070413021501".

    There is a Note of support Oracle ' size of level 1 or level 1 cumulative backup greater than level 0 backups [ID 1534691.1].

    which applies if you use the DUNGEON and change the tag.

    I note that you change the tag every day, but do not use the clause to KEEP this note should not apply.

    Why not explicitly run EXTRA STRENGTH 0 backup once and then monitor subsequent LEVEL 1 backups?

    Hemant K Collette

  • RMAN bypass backup can be taken from question?

    Hi all

    pretty simple question (I hope that ):

    I use the suite at the moment for example:

    run
    {
    Backup CONFIGURATION DEVICE TYPE DISK PARALLELISM 2 to compressed backupset;
    TIME 01:00 PARTIAL minimize THE time data BACKUP FILESPERSET 1;
    }

    But I was wondering if there is some way to this running as a backup script planned to restart backup, if it does not (due to problems of space file etc.)

    run
    {

    Configure the disk channel CH1 device type format ' / alternate/path/for_backup/%d_DB_%M%D%Y_%p_%s_%U';
    Configure the disk channel CH2 device type format ' / alternate/path/for_backup/%d_DB_%M%D%Y_%p_%s_%U';


    TIME 01:00 PARTIAL minimize THE time of BACKUP data
    NOT BACKED UP SINCE TIME ' SYSDATE - 1' fileperset 1;    < < < I know it won't work like that but y at - it another way to accomplish this? (work around to restart the backup time and the option to reduce time?)


    cleaning etc release channels

    }

    PS: question side bonus points

    who can tell me more about the loss of speed MB/S compared to the rate of compression: low/medium/high?

    I hope that there are some brilliant minds out there willing to help!

    Thanks in advance.



    The themes you mention seem to be covered in the Advanced documentation of RMAN:

    http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmbckad.htm#BRADV89540

    I don't know if anyone can really give you an opinion about which compression will have the best size vs time full report. But the next test by using a simple vanilla ORCL database shows the result of the compression of 'low '. It was done on sub Oracle 11 GR 2 one running a VirtualBox VM. As you can see there is a reduction of the large size of the backupset, which however has taken so long to complete as to the 'no' compression.

    RMAN> CONFIGURE COMPRESSION ALGORITHM clear;
    
    RMAN> backup database;
    RMAN> list backup;
    
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    ------- ---- -- ---------- ----------- ------------ ---------------
    40      Full    1.20G      DISK        00:00:08     22-JUN-15
            BP Key: 40   Status: AVAILABLE  Compressed: NO  Tag: TAG20150622T123329
    
    RMAN> CONFIGURE COMPRESSION ALGORITHM 'LOW';
    RMAN> backup as compressed backupset database;
    RMAN> list backup;
    
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    ------- ---- -- ---------- ----------- ------------ ---------------
    44      Full    400.38M    DISK        00:00:08     22-JUN-15
            BP Key: 44   Status: AVAILABLE  Compressed: YES  Tag: TAG20150622T123811
    

    Why did you write that I know that it won't work like that? According to the example below, I don't see the problem. As you can see on the 2nd run of the backup command, it ignores the data files that he has previously treated.

    RMAN> BACKUP DURATION 1:00 PARTIAL MINIMIZE TIME database NOT BACKED UP SINCE TIME 'SYSDATE -1' FILESPERSET 1;
    
    Starting backup at 22-JUN-15
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=+DATA/orcl1/datafile/system.256.862871041
    channel ORA_DISK_1: starting piece 1 at 22-JUN-15
    channel ORA_DISK_1: finished piece 1 at 22-JUN-15
    piece handle=+DATA/orcl1/backupset/2015_06_22/nnndf0_tag20150622t121929_0.283.883052369 tag=TAG20150622T121929 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00005 name=+DATA/orcl1/datafile/example.269.862871121
    channel ORA_DISK_1: starting piece 1 at 22-JUN-15
    channel ORA_DISK_1: finished piece 1 at 22-JUN-15
    piece handle=+DATA/orcl1/backupset/2015_06_22/nnndf0_tag20150622t121929_0.275.883052373 tag=TAG20150622T121929 comment=NONE
    ...etc...
    
    RMAN> delete backupset 29,30,34;
    
    RMAN> BACKUP DURATION 1:00 PARTIAL MINIMIZE TIME database NOT BACKED UP SINCE TIME 'SYSDATE -1' FILESPERSET 1;
    
    Starting backup at 22-JUN-15
    using channel ORA_DISK_1
    skipping datafile 2; already backed up on 22-JUN-15
    skipping datafile 3; already backed up on 22-JUN-15
    skipping datafile 4; already backed up on 22-JUN-15
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=+DATA/orcl1/datafile/system.256.862871041
    channel ORA_DISK_1: starting piece 1 at 22-JUN-15
    channel ORA_DISK_1: finished piece 1 at 22-JUN-15
    piece handle=+DATA/orcl1/backupset/2015_06_22/nnndf0_tag20150622t122021_0.308.883052421 tag=TAG20150622T122021 comment=NONE
    ...etc...
    
  • FULL backup and LEVEL 0

    Hello
    on the 11g on Win 2008 R2.
    I backup in NOCATALOG.
    When I run the backup from the command list I have:
     
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time 
    ------- ---- -- ---------- ----------- ------------ --------------- 
    6       Incr 0  3.73G ;     DISK        00:09:50     23/04/12 
            BP Key: 6   Status: AVAILABLE  Compressed: YES  Tag: TAG20120423T134319 
    
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time 
    ------- ---- -- ---------- ----------- ------------ --------------- 
    3       Full    1.05M ;     DISK        00:00:01     23/04/12 
            BP Key: 3   Status: AVAILABLE  Compressed: YES  Tag: TAG20120423T132033 
    So, what is the difference between Type = FULL and Type = 0 Incr?

    Thank you.
    Context:
    I ran first full backup:
    compressed backup backupset format '% WORK_DIR%\%DB%\rman\full/df_%%d_%%T_%%s_%%p' database;

    And then ran incremental:

    compressed backup backupset format '% WORK_DIR%\%DB%\rman\incr/df_%%d_%%T_%%s_%%p' INCREMENTAL level 1 data base;

    And for the second he showed me:
    no backup or copy of the data file nn parent was found.

    A level 0 incremental backup is identical to the contents of a full backup, but unlike a full backup, the level 0 backup is considered a part of the incremental backup strategy.

    A level 1 incremental backup can be one of the following types:

    A differential incremental backup, which backs up all blocks changed after the last incremental backup at level 1 or 0

    A cumulative incremental backup, which backs up all blocks changed after the last incremental backup at level 0

    Incremental backups are differential by default.

  • Archive newspaper vs. Full Backup Concept

    Hello

    I just need some clarification on how backups and Archives Records work. Lets say from 13:00 I have archive records 1,2,3,4,5 and then I perform a full backup at 18:00.

    I take then generate logs archiving at 18:00 to get newspapers 6,7,8,9,10. Then, I stop at 23:00.

    If my interpretation is correct, the archive logs should allow me to restore oracle to a point in time anywhere between 13:00 and 23:00. But if I have only the full backup, then I can only restore to a single point, which is from 18:00. My understanding is correct?

    Archive logs only applied to data files during backup or only during a restore? There is no archive newspaper applied on the fly.

    Thanks in advance.

    thelok wrote:
    Thanks for the great explanation! If I can do a restore time to any time point since the data changed files have been written (or when I have the last set of data files backed up more archive logs). What you say, I can force the data files to write about recovery logs (by a control point with 'alter set archive current log' or 'backup database more archivelog'), and then I can delete all archive logs have an SCN less than the SNA control point on the data files. Is this true? It would be for the purpose of preservation of disk space.

    Hello

    See this example. I hope this explains your doubt.

    # My current date is 06-11-2011 17:15
    # I not have backup of this database
    # My retention policy is to have 1 backup 
    
    # I start listing  archive logs.
    RMAN> list archivelog all;
    
    using target database control file instead of recovery catalog
    
    List of Archived Log Copies
    Key     Thrd Seq     S Low Time            Name
    ------- ---- ------- - ------------------- ----
    29      1    8       A 29-10-2011 12:01:58 +HR/dbhr/archivelog/2011_10_31/thread_1_seq_8.399.766018837
    30      1    9       A 31-10-2011 23:00:30 +HR/dbhr/archivelog/2011_11_03/thread_1_seq_9.409.766278025
    31      1    10      A 03-11-2011 23:00:23 +HR/dbhr/archivelog/2011_11_04/thread_1_seq_10.391.766366105
    32      1    11      A 04-11-2011 23:28:23 +HR/dbhr/archivelog/2011_11_06/thread_1_seq_11.411.766516065
    33      1    12      A 05-11-2011 23:28:49 +HR/dbhr/archivelog/2011_11_06/thread_1_seq_12.413.766516349
    
    ## See I have archive logs from time "29-10-2011 12:01:58" until "05-11-2011 23:28:49" but I dont have any backup of database.
    
    # So I perfom backup of database including archive logs.
    
    RMAN> backup database plus archivelog delete input;
    
    Starting backup at 06-11-2011 17:15:21
    
    ## Note above RMAN forcing archive current log, this archivelog generated will be usable only for previous backup.
    ## Is not my case... I don't have backup of database.
    
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=159 devtype=DISK
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=8 recid=29 stamp=766018840
    input archive log thread=1 sequence=9 recid=30 stamp=766278027
    input archive log thread=1 sequence=10 recid=31 stamp=766366111
    input archive log thread=1 sequence=11 recid=32 stamp=766516067
    input archive log thread=1 sequence=12 recid=33 stamp=766516350
    input archive log thread=1 sequence=13 recid=34 stamp=766516521
    channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:15:23
    channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:15:38
    piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525 tag=TAG20111106T171521 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=+HR/dbhr/archivelog/2011_10_31/thread_1_seq_8.399.766018837 recid=29 stamp=766018840
    archive log filename=+HR/dbhr/archivelog/2011_11_03/thread_1_seq_9.409.766278025 recid=30 stamp=766278027
    archive log filename=+HR/dbhr/archivelog/2011_11_04/thread_1_seq_10.391.766366105 recid=31 stamp=766366111
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_11.411.766516065 recid=32 stamp=766516067
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_12.413.766516349 recid=33 stamp=766516350
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_13.414.766516521 recid=34 stamp=766516521
    Finished backup at 06-11-2011 17:15:38
    
    ## RMAN finish backup of Archivelog and Start Backup of Database
    ## My backup start at "06-11-2011 17:15:38"
    
    Starting backup at 06-11-2011 17:15:38
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=+HR/dbhr/datafile/system.386.765556627
    input datafile fno=00003 name=+HR/dbhr/datafile/sysaux.396.765556627
    input datafile fno=00002 name=+HR/dbhr/datafile/undotbs1.393.765556627
    input datafile fno=00004 name=+HR/dbhr/datafile/users.397.765557979
    input datafile fno=00005 name=+BFILES/dbhr/datafile/bfiles.257.765542997
    channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:15:39
    channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:16:03
    piece handle=+FRA/dbhr/backupset/2011_11_06/nnndf0_tag20111106t171539_0.269.766516539 tag=TAG20111106T171539 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:24
    Finished backup at 06-11-2011 17:16:03
    
    ## And finish at "06-11-2011 17:16:03", so I can recovery my database from this time.
    ## I will need archivelogs (transactions) which was generated during backup of database.
    ## Note during backup some blocks are copied others not. The SCN is inconsistent state.
    ## To make it consistent I need apply archivelog which have all transactions recorded.
    
    ## Starting another backup of archived log generated during backup.
    Starting backup at 06-11-2011 17:16:04 
    
    ## So automatically RMAN force another "checkpoint" after backup finished,
    ## forcing archive current log, because this archivelog have all transactions to bring database in a consistent state.
    
    current log archived
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=14 recid=35 stamp=766516564
    channel ORA_DISK_1: starting piece 1 at 06-11-2011 17:16:05
    channel ORA_DISK_1: finished piece 1 at 06-11-2011 17:16:06
    piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171604_0.272.766516565 tag=TAG20111106T171604 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=+HR/dbhr/archivelog/2011_11_06/thread_1_seq_14.414.766516565 recid=35 stamp=766516564
    Finished backup at 06-11-2011 17:16:06
    
    ## Note: I can recover my database from time "06-11-2011 17:16:03" (finished backup full)
    ##  until "06-11-2011 17:16:04" (last archivelog generated) that is my recover window in this scenary.
    
    ## Listing Backup I have:
    ## Archive Logs in backupset before backup full start - *BP Key: 40*
    ## Backup Full database in backupset - *BP Key: 41*
    ##  Archive Logs in backupset after backup full stop - *BP Key: 42*
    
    RMAN> list backup;
    
    List of Backup Sets
    ===================
    
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ -------------------
    40      196.73M    DISK        00:00:15     06-11-2011 17:15:37
            *BP Key: 40*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171521
            Piece Name: +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525
    
      List of Archived Logs in backup set 40
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      ---- ------- ---------- ------------------- ---------- ---------
      1    8       766216     29-10-2011 12:01:58 855033     31-10-2011 23:00:30
      1    9       855033     31-10-2011 23:00:30 896458     03-11-2011 23:00:23
      1    10      896458     03-11-2011 23:00:23 937172     04-11-2011 23:28:23
      1    11      937172     04-11-2011 23:28:23 976938     05-11-2011 23:28:49
      1    12      976938     05-11-2011 23:28:49 1023057    06-11-2011 17:12:28
      1    13      1023057    06-11-2011 17:12:28 1023411    06-11-2011 17:15:21
    
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    ------- ---- -- ---------- ----------- ------------ -------------------
    41      Full    565.66M    DISK        00:00:18     06-11-2011 17:15:57
            *BP Key: 41*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171539
            Piece Name: +FRA/dbhr/backupset/2011_11_06/nnndf0_tag20111106t171539_0.269.766516539
      List of Datafiles in backup set 41
      File LV Type Ckp SCN    Ckp Time            Name
      ---- -- ---- ---------- ------------------- ----
      1       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/system.386.765556627
      2       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/undotbs1.393.765556627
      3       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/sysaux.396.765556627
      4       Full 1023422    06-11-2011 17:15:39 +HR/dbhr/datafile/users.397.765557979
      5       Full 1023422    06-11-2011 17:15:39 +BFILES/dbhr/datafile/bfiles.257.765542997
    
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ -------------------
    42      3.00K      DISK        00:00:02     06-11-2011 17:16:06
            *BP Key: 42*   Status: AVAILABLE  Compressed: NO  Tag: TAG20111106T171604
            Piece Name: +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171604_0.272.766516565
    
      List of Archived Logs in backup set 42
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      ---- ------- ---------- ------------------- ---------- ---------
      1    14      1023411    06-11-2011 17:15:21 1023433    06-11-2011 17:16:04
    
    ## Here make sense what I trying explain
    ## As I don't have backup of database before of my Last backup, all archivelogs generated before of my backup full is useless.
    
    ## Deleting what are obsolete in my env, RMAN choose backupset 40 (i.e all archived logs generated before my backup full)
    
    RMAN> delete obsolete;
    
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    using channel ORA_DISK_1
    Deleting the following obsolete backups and copies:
    Type                 Key    Completion Time    Filename/Handle
    -------------------- ------ ------------------ --------------------
    *Backup Set           40*     06-11-2011 17:15:37
      Backup Piece       40     06-11-2011 17:15:37 +FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525
    
    Do you really want to delete the above objects (enter YES or NO)? yes
    deleted backup piece
    backup piece handle=+FRA/dbhr/backupset/2011_11_06/annnf0_tag20111106t171521_0.268.766516525 recid=40 stamp=766516523
    Deleted 1 objects
    

    In the example above, I could before running Backup "archivelog all delete" because they are not necessary, but as an example, I followed this unnecessarily. (archivelog backup and deletion after)

    Kind regards
    Levi Pereira

    Published by: Levi Pereira on November 7, 2011 01:02

  • Can not do a full backup

    I have 10 items on Windows 7.  When I try to do a full backup on an external hard drive, I see ' calculating size total media "and execution bar stops at 96% and nothing else happens.  I waited for an hour, nothing.  My CPU usage meter shows no activity.  It is as if he is suspended.  I can't cancel, I have to click the x button.  At some point in the past that works because I had three all backup files on my external hard drive (which I deleted before you do).

    What's wrong?

    OK people.  I think I got it fixed!

    I went with the support of Adobe paid ($39) and after a few days (almost a week), it seems to be fixed.  At least, I can now make a backup.  I have not tried to restore from it again (or I will cause that creates a whole new level of complexity.)  Suffice it to say the part of my backup procedure is now doing a copy of catalog file and my photos on an external drive.

    After several calls to whom we did much basically the same things that you, dear friends suggested I do, Adobe said they would get back to me within 48 hours while they esclated it.  It was last Wednesday.  On Tuesday (6 days later, but over the weekend), they were recalled to work.  We all seemed to agree that the catalog is corrupt.  They wanted me to download the catalog offending on their ftp server, we did.  Either way, the level of expertise on the line this time was considerably higher than last week.

    Apparently, as they climbed over the issue, some backroom engineer asked to have my catalog sent to them so they could watch.

    The next day, I get a call and download us the catalog sets down to my PC and I have successfully completed a top backup.  It looked like it had been fixed very quickly yesterday.

    So there is an answer.  I suggested it, they try to put the fix in their catalogue of repair service, but...

    Meanwhile, I discovered that many of my pictures already had the tags written for them.  Many do not have.  Since I've never used tags writing to photo option keyword, I was wondering when and how the tags wrote.  I asked Adobe and they said that if you have photos to analyize it can also write the tags.  And you were correct, that the tags on the files are the last 'editorial '.  Any changes to the tags that make you in the organizer do not appear in the files to what rewrite you for them.

    Hope this helps other people.

    And THANKS a lot for all the help and expertise you gave me.

    See you soon,.

    Eric

  • Why backup size don't add up?

    I have a problem to backup my phone.

    If I'm going to manage storage

    Documents and data: 43.6 MB

    Mailing address: 17.5 MB

    If I go into my iPhone

    Backup size: 3.7 GB

    Then back up size: 0 bytes

    I have most of the applications off including photo library.

    What is eating up 3.7 GB for backup for iCloud?

    I also tried to delete the backup to my phone.

    When I save, the size was 3.7 GB.

    Thank you!

    I thought that partially the problem.

    I have an iPhone, iPad and Macbook which use the same space to iCloud. Apparently the messages take place backup, and there is no way to turn it off unless you remove all the messages.

    I deleted all of the messages on my Mac, iPad and iPhone, and I was able to free 3 GB space iCloud.

    Even after deleting my messages, it did not free space immediately. I had to delete the backups and backup fresh spring. Then the size reflects the changes.

    I guess that if send you / receive a lot of picture messages and you have multiple devices using the same iMessage, you end up losing iCloud spaces. I could be wrong, but they seemed all backed up separately, even if they are the same messages.

    Anyway, there is always a mystery. After you delete the messages, iPhone and iPad now only mix 800 MB. However, if I go to iCloud on my Mac, it says I have 600 MB of documents.

    I have almost nothing on my player iCloud, less than 30 MB. Where are the documents of this mystery? I also deleted all my messages on my Mac, and photo library is not checked.

    Now my iPhone uses 600 MB, iPad use 200 MB and mystery documents use 600 MB. Full use is 1.4 GB and I have 3.6 GB free.

    Someone know where I can find the documents of mystery?

    Thank you!

  • Cannot perform a full backup of my drive hard using a 16 GB Flash drive

    Original title: backup

    I am trying to perform a full backup of my hard drive using a 16 GB Flash disk. Windows does not allow me to do so; or he will put in the form of USB key when prompted to do so.  Help me Mr Wizard.

    Hello
     
    1. which is the version of Windows installed on the computer? For example, Windows 7, Vista
    2. do you use the Windows backup feature to backup?
    3. What is the size of the data you want to save on the Flash drive?
    4. what happens when you perform the backup? You get an error as well?
     
    If you use Windows 7, check out these links.
     
    See: how much space storage do I need back up files?
     
    See also:
     
    Hope the information is useful.
     
  • I still do the full backup after using Data Guard?

    In our system, there is a physical database standby data protection configuration. Is it still necessary to do a full backup and an incremental backup?

    Jackliusr wrote:
    In our system, there is a physical database standby data protection configuration. Is it still necessary to do a full backup and an incremental backup?

    Preferred to have full backup of every day.
    May be you can perform failover of your sleep, in which case there is no availability on the primary database. So do you think that the stability of the monitoring system is the same as elementary school and can give the same performance?
    location of Eve may be too far and it's only disaster.
    Allows another case, suppose that your wait is behind that primary for 4-5 days due to some problems. At the same time your production crashed while you have the chance of data fo loose 4-5 days. Recommended to have a full backup still database primary.

    If you check the stability of database daily watch and able to check your data by opening properly and you want RMAN backup, it is fine. But it is highly recommended to have RMAN backup.

    BTW, you can have RMAN backup full standby, if you want to avoid the resources to be used on the primary

  • full backup

    Hello
    I have create this shell script for rman for Oracle version 8i for full backup (database + controlfile archivelog):
    rman nocatalog <<EOF >> $LOG 2>&1
    connect target sys/password@sid
    run {
    allocate channel c1 type disk format '/backup_full/backup%d_DB_%u_%s_%p';
    backup database;
     sql 'alter system archive log current';
    backup format 'backup%d_CL_%u_%s_%p' current controlfile;
    backup format 'backup%d_AR_%u_%s_%p' archivelog all delete input;
    release channel c1;
        }
    Now I need rman script to Oracle 10.2.0.5 for full backup (database + controlfile archivelog).

    Is this right? Should I change?


    Thanks in advance!

    RAF Royal wrote:
    I have create this shell script:

    MY_PATH="/backup_rman_full/"
    export MY_PATH
    
    rman nocatalog <> $LOG 2>&1
    connect target
    run {
    allocate channel c1 type disk format '${MY_PATH}back%d_%u_%s_%p';
    backup database;
    sql 'alter system archive log current';
    backup format '${MY_PATH}back%d_C_%u_%s_%p' current controlfile;
    backup format '${MY_PATH}back%d_A_%u_%s_%p' archivelog all delete input;
    release channel c1;
    }
    exit
    EOF
    

    Is to correct the syntax?

    Hello

    Your script above looks perfect with the exception of '$LOG' which is not defined. But I prefer to add ORACLE_HOME and ORACLE_SID in your script and also change the format specifier "%u" "%U" while RMAN generates the uniqueness in the backup files. Here's the updated script for you.

    ORACLE_HOME=
    export ORACLE_HOME
    ORACLE_SID=
    export ORACLE_SID
    MY_PATH="/backup_rman_full/"
    export MY_PATH
    
    rman nocatalog <
    

    Think of your son of fence by providing appropriate points if you think they have been answered. Please clean the forum.

Maybe you are looking for