Step by Step RMAN configuration for full hot backup daily

Dear experts,
i am new to oracle RMAN , i have gone through couple of RMAN guides for configuration ,
i have oracle e-business suite (R12.1.1) and database is ( 11.1.0.7) on red hat enterprise linux 5.3 . All of this is 64 bit.
i have a database about 175 gb which is as usual growing day by day as data entry is taking place.
Untill now we have a cold backup strategy in the midnight 3 am a script down the database and make abc.tar.gz file of 25 gb approx. . This process takes about 100 minutes. But now due to new sales system we want our database up 24/7 .
So we want to configure RMAN hot backup.
I want to take backup on disk.
daily full hot backup.
backupsets
currently database is in no-archivelog
plz help me to proceed with this .
Edited by: user13376823 on Feb 10, 2011 12:17 PM

user13376823 wrote:
Dear all,
i am using this script for my full hot backup ,
run
allocate channel c1 device type disk format '/opt/R12Backups/rman/%U';
allocate channel c2 device type disk format '/opt/R12Backups/rman/%U';
crosscheck backup;
BACKUP DATABASE FORMAT '/opt/R12Backups/rman/proddb_%u_%p_%c';
sql 'alter system switch logfile';
BACKUP ARCHIVELOG ALL DELETE INPUT FORMAT '/opt/R12Backups/rman/archlog%U';
DELETE NOPROMPT OBSOLETE REDUNDANCY =1 device type disk;
DELETE NOPROMPT EXPIRED BACKUPSET OF DATABASE device type disk ;
BACKUP AS COPY CURRENT CONTROLFILE FORMAT '/opt/R12Backups/rman/copy_of_cf_%U';
BACKUP SPFILE FORMAT '/opt/R12Backups/rman/spfile_%U';
release channel c1;
release channel c2;
1.please tell me that it is covering all aspects of a backup . Can i do complete recovery with this backup in case of disaster?
Define "all aspects".
2. i only get database and controlfile backup at my location. There is no backup of archivelogs , What happened with
that ?Without seeing the output that rman generated from running the above block, and without seeing all of the persistent rman settings, it is impossible to diagnose anything. I will say that your script looks overly complex.
Just to give you a point of comparison, here's my setup. First the persistent rman settings. Take note of anything that is NOT marked as "default";
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 3;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/ora00/app/oracle/product/10.2.0/db_1/dbs/snapcf_vlnxora1.f'; # defaultAnd here is my basic "full backup" script
[oracle@vmlnx01 bin]$ cat rman_full.scr
connect target /
show all;
run {
  backup incremental level 0 database tag='bkup_vlnxora1_full';
  backup archivelog all not backed up 2 times tag='bkup_vlnxora1_arch';
  delete noprompt archivelog all backed up 2 times to device type disk;
list backup summary;
report obsolete;
quit

Similar Messages

  • RMAN Full  Hot Backup Daily

    Hi,
    I have Production Database going to live this week..
    this is my RMAN Backup script for taking daily Full Hot Backup night 12pm...
    I have enabled FLASH_RECOVERY_AREA
    DB_RECOVERY_FILE_DEST=/backup/flash_recovery_area
    log_archive_dest=/backup/archivelog
    log_archive_format='arch_%d_%S_%T';
    =========================================================
    rman target=/
    configure controlfile autobackup on;
    run
    allocate channel c1 device type disk;
    crosscheck backup;
    backup as compressed backupset database;
    sql 'alter system switch logfile';
    crosscheck backup;
    release channel c1;
    exit
    ===========================================================
    Above script is scheduled usgin cron job...
    =============================================================
    Here I am not taking the archive logs backup...because..by default..archive logs are created in 2 places
    (a) FLASH RECOVERY AREA
    (b) /backup/archivelog
    so archive logs are created by date wise in Flash Recovery Area....
    I have flash recovery area structure like this for ever day
    /backup/flash_recovery_area/PROD/archivelog/29_09_2007
    /backup/flash_recovery_area/PROD/autobackup/29_09_2007
    /backup/flash_recovery_area/PROD/archivelog/30_09_2007
    /backup/flash_recovery_area/PROD/autobackup/30_09_2007
    Above are 2 days backups of 29th and 30th....
    I can simply send those 30_09_2007 and 29_09_2007 directories to TAPE Drive....
    =======================================================================
    When disaster recovery, i can restore those directories to flash_recovery_area and do the recovery using rman...
    =============================================
    Friends...am i goin in correct way..if anything wrong...please correct me..
    my doubt is..I am not used any command of backuping up archivelogs in rman script.......becasue..archive logs are created in flash_recovery_area by date wise......
    am i correct..

    Hi,
    Thanks for the reply,
    My requirement is......Full Hot Backup daily at 2 AM......Daily i have to take this...so i scheduled this using cron job......I need to maintain 7 days backup in backup location.....
    Here is my script
    # Export Environment Variables
    export ORACLE_HOME=/oradata/oracle
    export ORACLE_SID=PROD
    export PATH=$PATH:$ORACLE_HOME/bin
    # RMAN Full Backup
    rman target / catalog rman/rman << EOF
    configure controlfile autobackup on;
    configure retention policy to redundancy 7;
    run
    crosscheck backup;
    backup as compressed backupset database;
    sql 'alter system switch logfile';
    backup as compressed backupset archivelog all;
    backup as compressed backupset current controlfile;
    crosscheck backup;
    crosscheck archivelog all;
    delete noprompt obsolete;
    delete noprompt expired backup;
    exit=============================================================
    Can u please verify that, script is good or not
    Message was edited by:
    bsubbu
    Message was edited by:
    bsubbu

  • RMAN script for RAC Hot Backup

    Anyone who want to share an RMAN script to Hot Backup a 9i RAC Database.

    Try to remove the DURATION option in your script.
    Here more details about that part.
    http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta009.htm#i1010261
    Bye, Aron

  • OSB / RMAN configuration for recovery area backup

    Hi
    I am having trouble performing a recovery area backup to tape.
    Current config
    Media server - attached tape library (OSB installed as media server, admin and client - Contains RMAN Repository) - configured as per guide. I can see the library tapes and have tested an OSB filesystem backup to tape which was fine, this was done from the OSB GUI.
    Server 1 - databaseA, DatabaseB (OSB client installed) .
    ZFS device - Shared storage where the FRA for DatabaseA belongs. All databaseA backups go here (currently databaseA is running in nonarchivelog mode).
    I have set the tape details for databaseA, done a backup to the FRA but the backup recovery area to tape backup just hangs, no real errors and the job list through the obtool and list the job it always has state as 'retryable', I am wondering if I have missed some configuration somewhere? I am using Grid control for this.
    I did have a couple of RMAN messages tried to resolve this as per some metalink notes to no avail, I am assuming this is causing the problem? Or am I missing something else?
    specification does not match any archived log in the repository
    specification does not match any datafile copy in the repository
    Can anyone help?

    Rest the times on the servers and now get the following errors:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 10/28/2011 16:22:55
    ORA-19506: failed to create sequential file, name="16mq8bjj_1_2", parms=""
    ORA-27028: skgfqcre: sbtbackup returned error
    ORA-19511: Error received from media manager layer, error text:
    shmcheck: obscheduled reports that job 'oracle/16.1' has terminated with status 'failed'.
    The action at time of failure was 'wait_for_resource'.
    The error message was 'unknown'.
    exit;

  • Full Hot Backup using RMAN?

    Dear all,
    I want to take a full hot backup every week on sunday and the followings are the commands.
    run
    allocate channel ch1 type disk format '/db/BACKUP/RMAN/backup_%d_%t_%s_%p_%U.bck';
    backup
    incremental level 0
    database
    plus archivelog delete input;
    backup current controlfile;
    backup spfile;
    release channel ch1;
    I have the following questions:
    1) Am I need to define a directory named as "'/db/BACKUP/RMAN/backup_%d_%t_%s_%p_%U.bck", so that the backup copies will put it here,right?
    2) What format needs to be save in where and how to run it on weekly schedule basis?
    3) I saw above script with "channel ch1", can I change it to "channel ch2"?
    I am a beginner using RMAN, please let me know.
    Best Regards,
    amy

    Which database version on which OS (looks like Unix/Linux)?
    You have to create the directory '/db/BACKUP/RMAN', 'backup_%d...' is the filename created by RMAN.
    %d Specifies the name of the database;
    %t Specifies the backup set time stamp, which is a 4-byte value derived as the number of seconds elapsed since a fixed reference time. The combination of %s and %t can be used to form a unique name for the backup set;
    %s Specifies the backup set number. This number is a counter in the control file that is incremented for each backup set. The counter value starts at 1 and is unique for the lifetime of the control file. If you restore a backup control file, then duplicate values can result. Also, CREATE CONTROLFILE initializes the counter back to 1;
    %p Specifies the piece number within the backup set. This value starts at 1 for each backup set and is incremented by 1 as each backup piece is created;
    %U Specifies a system-generated unique filename (default).
    For scheduling a cron job could be defined or you use Enterprise Manager (10g and higher)
    Channel name doesn't matter.
    Werner

  • Incomplete Recovery Fails using Full hot backup & Archive logs !!

    Hello DBA's !!
    I am doing on Recovery scenario where I have taken One full hot backup of my Portal Database (EPR) and Restored it on New Test Server. Also I restored Archive logs from last full hot backup for next 6 days. Also I restored the latest Control file (binary) to their original locations. Now, I started the recovery scenario as follows....
    1) Installed Oracle 10.2.0.2 compatible with restored version of oracle.
    2) Configured tnsnames.ora, listener.ora, sqlnet.ora with hostname of Test server.
    3) Restored all Hot backup files from Tape to Test Server.
    4) Restored all archive logs from tape to Test server.
    5) Restored Latest Binary Control file from Tape to Test Server.
    6) Now, Started recovery using following command from SQL prompt.
    SQL> recover database until cancel using backup controlfile;
    7) Open database after Recovery Completion using RESETLOGS option.
    Now in Above scenario I completed steps upto 5) successfully. But when I execute the step 6) the recovery completes with Warning : Recovery completed but OPEN RESETLOGS may throw error " system file needs more recovery to be consistent " . Please find the following snapshot ....
    ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
    1
    ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
    ORA-00280: change 7001816252 for thread 1 is in sequence #9624
    ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
    for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
    SQL> SQL> SQL> SQL> SQL> SQL> SQL>
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
    Let me know What should be the reason behind recovery failure !
    Note : I tried to Open the database using Last Full Hot Backup only & not applying any archives. Then Database Opens successfully. It means my Database Installation & Configuration is OK !
    Please Let me know why my Incomplete Recovery using Archive logs Goes Fail ?
    Atul Patil.

    oh you made up a new thread so here again:
    there is nothing wrong.
    You restored your backup, archives etc.
    you started your recovery and oracle applyed all archives but the archive
    '/oracle/EPR/oraarch/1_9624_601570270.dbf'
    does not exist because it represents your current online redo log file and that is not present.
    the recovery process cancels by itself.
    the solution is:
    restart your recovery process with:
    recover database until cancel using backup controlfile
    and when oracle suggests you '/oracle/EPR/oraarch/1_9624_601570270.dbf'
    type cancel!
    now you should be able to open your database with open resetlogs.

  • FULL HOT Backup failing with a 6 on media management layer....

    Hi all,
    My thanks in advance for reading and any posts. Appologies for the long post, but wanted to make sure I got all information required into the post
    *******************The background*************************
    We are currently doing full hot backups of all production databases to tape. The database we use is RAC install (9.2.0.6.0) on Linux Redhat Enterprise 4 (database on OCFS). We use a seperate Solaris 8 box with 2 HP Ultium tape drives over a standard Cat5 line (100mb), we use Veritas Netbackup 5.1 as our media manager and we use an RMAN repositry on another box. Currently the backup is taking on average 17 hours to complete (something that I have been through with Oracle).
    We use the below rman script to do the full database backup.
    DATE=`date +%m%d%Y-%H%M%S`; export DATE
    USER=`id | cut -f2 -d"(" | cut -f1 -d")"`
    ORACLE_SID=ausl5; export ORACLE_SID
    ORACLE_USER=oracle; export ORACLE_USER
    ORACLE_HOME=/u01/oracle/product/9.2.0 export ORACLE_HOME
    #delete log files older than 35 days
    find /var/adm/netbackup -name "auslive*" -mtime +35 -type f -exec rm {} \;
    #if [ "${USER}" = "root" ]
    #then
    # su - ${ORACLE_USER} "cd /rac/DBA/scripts/BACKUP/" #-c "${CMD_STRING}"
    # SUCCESS=$?
    #else
    # eval "/rac/DBA/scripts/BACKUP"
    # SUCCESS=$?
    #fi
    <<EOF su - oracle
    <<EOF1 /u01/oracle/product/9.2.0/bin/rman msglog /var/adm/netbackup/AUSLIVE_b
    ackup.${DATE} append
    connect target sys/fowler@rman_ausl5
    connect catalog rman/rman@rman
    #change archivelog all validate;
    run {
    allocate channel ch1 type sbt_tape PARMS="BLKSIZE=1048576";
    #allocate channel ch2 type sbt_tape PARMS="BLKSIZE=1048576";
    #allocate channel ch3 type sbt_tape;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CHANNEL 1 DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 100000m
    CONNECT = 'SYS/fowler@rman_ausl5';
    #CONFIGURE CHANNEL 2 DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 100000m
    CONNECT = 'SYS/fowler@rman_ausl3';
    #CONFIGURE CHANNEL 3 DEVICE TYPE 'SBT_TAPE' CONNECT = 'SYS/fowle
    r@rman_ausl4';
    change archivelog all validate;
    ###=============== Veritas Calls =========================
    send "NB_ORA_CLASS=ORAhot_AUSLIVE";
    #send "NB_ORA_CLIENT=sunatlsunx008";
    send "NB_ORA_CLIENT=sunatlsunx008";
    send "NB_ORA_SCHED=full";
    ###=====================main backup sections =============
    backup
    incremental level=0
    filesperset 15
    format "bk_%s_%p_%t"
    tag "hot_${ORACLE_SID}_${DATE}"
    database;
    sql "alter system archive log current";
    change archivelog all validate;
    backup
    filesperset 10
    format "ct_%s_%p_%t"
    current controlfile;
    sql "alter system archive log current";
    backup
    filesperset 150
    format "al_%s_%p_%t"
    archivelog all not backed up 2 times;
    change archivelog all validate;
    backup
    filesperset 50
    format "al_%s_%p_%t"
    archivelog until time 'SYSDATE-4' delete input;
    change archivelog all validate;
    release channel ch1;
    #release channel ch2;
    #release channel ch3;
    exit
    EOF1
    EOF
    Now due to the backup taking so long, we often have archive log backups that kick off. We generally get Restore Validates of this backup once a week.
    *********************************Problem*******************************
    Getting to the problem, the media manager generally completes the job with a 6, which in Veritas means that the backup failed to back up the requested files. I guess that this could be something to do with the media manager layer. But myself and my colleagues are of the opinion that this is something to do with the archive log backups running inbetween (hence the change archivelog all validate; appearing so many times in the script).
    Has anyone got any ideas?
    Thanks again for any posts / ideas,
    Mark.

    No I mean, it really tries to backup everything; control file, archive logs etc...
    Yeah I will admit its a bit strange, didn't code it myself. The idea was to do a bit a of house keeping at the same time with the archived redo logs (hence the file system stuff with the archived redo logs).
    You see we thought that this might be causing the issue.
    any ideas are welcomed,
    thanks again,
    Mark.

  • RMAN CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET;

    I configure this , How i can clear this ?
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET;

    I assume you would have tried
    CONFIGURE DEVICE TYPE DISK CLEAR;(as described in the documentation) before asking the question.
    What about this does not work for you?

  • Estimating the backup size for full database backup?

    How to estimate the backup file size for the following backup command?
    Oracle 10g R2 on HPUX
    BACKUP INCREMENTAL LEVEL 0 DATABASE;
    Thank you,
    Smith

    Depends on the number of used blocks, block size etc. You could probably get a rough formula for backup size based on the contents of dba_tab_statistics (subtract empty_blocks), dba_ind_statistics etc.

  • PA-MC-STM1 card configuration for full bandwidth

    Hi
    We have PA-MC-STM1 CARD on 7600 series router. This card is for channelized E1 support.
    I need to configured full bandwidth on this card. How can i do that.
    I am connecting my router with service provider and at the other end second router is connectd with the same card. I need to configure backbone link between both the routers having full bandwidth(don't want channelised E1).
    Please let me know if some one has done this on the same card.
    Regards,
    Jatin

    Try:
    http://www.cisco.com/warp/public/105/dscpvalues.html
    http://www.cisco.com/warp/public/105/wantqos.html
    http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s28/12sl3ncd.htm

  • RMAN never deletes archive log backups

    Hi all,
    I have same problem as some of you have already faced.
    I have some instances 10.2.0.4 running un archive log mode.
    I take full hot backup daily.
    I setup a rman script to backup and delete obsolete backups according to the following policy:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    and then:
    run {
    ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
    BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/mnt/rman_202/pnetpres/db_pres_%U';
    CROSSCHECK ARCHIVELOG ALL;
    BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/mnt/rman_202/pnetpres/al_pres_%U';
    CROSSCHECK BACKUP;
    DELETE NOPROMPT OBSOLETE;
    DELETE NOPROMPT EXPIRED BACKUP;
    RELEASE CHANNEL RMAN_BACK_CH01;
    crosscheck archivelog all;
    delete noprompt archivelog all completed before 'sysdate -2';
    DB full backups are being deleted, however archive logs backups are not deleted.
    There are no tablespaces in backup or offline mode.
    How can I know the reason why some archive log backups are kept ?
    Even I clear the policy and perform a crosscheck and delete, those are not marked as obsolete neither deleted from disk.
    Thanks in advance.

    Hi Fernando,
    This are the ouputpus of the commands:
    RMAN> REPORT OBSOLETE;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    no obsolete backups found
    RMAN> LIST BACKUP OF ARCHIVELOG ALL;
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    1090 69.65M DISK 00:00:16 23-FEB-11
    BP Key: 1093 Status: AVAILABLE Compressed: YES Tag: TAG20110223T061511
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0jm5c6bf_1_1
    List of Archived Logs in backup set 1090
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 13 2173025156 21-FEB-11 2173028010 21-FEB-11
    1 14 2173028010 21-FEB-11 2173041730 21-FEB-11
    1 15 2173041730 21-FEB-11 2173041813 21-FEB-11
    1 16 2173041813 21-FEB-11 2173106066 22-FEB-11
    1 17 2173106066 22-FEB-11 2173108831 22-FEB-11
    1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
    1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
    1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
    1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1411 125.43M DISK 00:00:28 24-FEB-11
    BP Key: 1414 Status: AVAILABLE Compressed: YES Tag: TAG20110224T061643
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0mm5eqqb_1_1
    List of Archived Logs in backup set 1411
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
    1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
    1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
    1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1600 164.40M DISK 00:00:37 25-FEB-11
    BP Key: 1603 Status: AVAILABLE Compressed: YES Tag: TAG20110225T061643
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0pm5hf6b_1_1
    List of Archived Logs in backup set 1600
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1829 132.24M DISK 00:00:30 26-FEB-11
    BP Key: 1832 Status: AVAILABLE Compressed: YES Tag: TAG20110226T061627
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0sm5k3hr_1_1
    List of Archived Logs in backup set 1829
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2058 218.03M DISK 00:00:48 27-FEB-11
    BP Key: 2061 Status: AVAILABLE Compressed: YES Tag: TAG20110227T061628
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0vm5mnts_1_1
    List of Archived Logs in backup set 2058
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2298 205.39M DISK 00:00:45 28-FEB-11
    BP Key: 2301 Status: AVAILABLE Compressed: YES Tag: TAG20110228T061620
    Piece Name: /mnt/rman_202/pnetproy/al_pres_12m5pc9l_1_1
    List of Archived Logs in backup set 2298
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2546 180.29M DISK 00:00:39 01-MAR-11
    BP Key: 2549 Status: AVAILABLE Compressed: YES Tag: TAG20110301T061533
    Piece Name: /mnt/rman_202/pnetproy/al_pres_15m63to5_1_1
    List of Archived Logs in backup set 2546
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    2801 85.40M DISK 00:00:19 02-MAR-11
    BP Key: 2804 Status: AVAILABLE Compressed: YES Tag: TAG20110302T061613
    Piece Name: /mnt/rman_202/pnetproy/al_pres_18m66i5d_1_1
    List of Archived Logs in backup set 2801
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3058 137.93M DISK 00:00:30 03-MAR-11
    BP Key: 3061 Status: AVAILABLE Compressed: YES Tag: TAG20110303T061548
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1bm696gk_1_1
    List of Archived Logs in backup set 3058
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3324 138.96M DISK 00:00:31 04-MAR-11
    BP Key: 3327 Status: AVAILABLE Compressed: YES Tag: TAG20110304T061559
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1em6bqsv_1_1
    List of Archived Logs in backup set 3324
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3597 178.07M DISK 00:00:39 05-MAR-11
    BP Key: 3600 Status: AVAILABLE Compressed: YES Tag: TAG20110305T061543
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1hm6ef8f_1_1
    List of Archived Logs in backup set 3597
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3835 198.44M DISK 00:00:43 06-MAR-11
    BP Key: 3838 Status: AVAILABLE Compressed: YES Tag: TAG20110306T061548
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1km6h3kk_1_1
    List of Archived Logs in backup set 3835
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4131 185.94M DISK 00:00:40 07-MAR-11
    BP Key: 4134 Status: AVAILABLE Compressed: YES Tag: TAG20110307T061546
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1nm6jo0i_1_1
    List of Archived Logs in backup set 4131
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4435 161.37M DISK 00:00:35 08-MAR-11
    BP Key: 4438 Status: AVAILABLE Compressed: YES Tag: TAG20110308T061540
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1qm6mccc_1_1
    List of Archived Logs in backup set 4435
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4745 79.24M DISK 00:00:18 09-MAR-11
    BP Key: 4748 Status: AVAILABLE Compressed: YES Tag: TAG20110309T061555
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1tm6p0os_1_1
    List of Archived Logs in backup set 4745
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
    1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    5270 135.13M DISK 00:00:31 10-MAR-11
    BP Key: 5273 Status: AVAILABLE Compressed: YES Tag: TAG20110310T061603
    Piece Name: /mnt/rman_202/pnetproy/al_proy_20m6rl53_1_1
    List of Archived Logs in backup set 5270
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
    1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
    1 58 2174307679 09-MAR-11 2174353241 09-MAR-11
    1 59 2174353241 09-MAR-11 2174384330 10-MAR-11
    1 60 2174384330 10-MAR-11 2174387259 10-MAR-11
    RMAN>
    For example the backups of archivelog from Feb 21st will never be deleted unless I force the delete.
    I'd like to understand why it happens :-)
    Thanks a lot,
    Regards,
    Diego.

  • EDI configuration for automatic IV

    Hi,
    What all are the steps to do EDI configuration for automatic
    IV in an intercompany scenario. In an STO scenario I
    want the invoice to generated automatically in the receiving
    company based on the issuing company's invoice.
    regards
    Magi

    HI,
    I have done these setttings . I have done the settings for partner type KU (customer) and partner type LI (vendor) in
    WE20.
    But IDOCs are not getting generated. Is there anything else
    to do to trigger the generation of IDOCS?
    regards
    magi

  • Hot Backup for oracle database?

    Dear all,
    I want to change Cold Backup to Hot Backup. Does anyone how to do Hot Backup and has some simple document I can follow? If the database is running in ARCHIVELOG mode, is the size grow very fast or other effect will overcome?
    Please advice,
    Amy

    I want to change Cold Backup to Hot Backup. Does
    anyone how to do Hot Backup and has some simple
    document I can follow?online/hot backup don’t need to shutdown the database we can put the database in backup mode and then start taking backup even though users database activity read/write data going on. This strategy useful if ours database goes for 24x7.
    For online/hot backup the database should be in archive mode.
    I hope you know how to turn on archive.Before turning on check the archive on or not.
    SQL> archive log list
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence     1
    Next log sequence to archive   2
    Current log sequence           2
    SQL> you may also check it by connecting to database as sys
    SQL> select log_mode from v$database;
    LOG_MODE
    ARCHIVELOG
    SQL> if yours database is not in archive mode then first enable archive,please before turning on the archive take cold backup.
    SQL>shutdown immediate
    SQL>startup mount
    SQL>alter database archivelog
    SQL>alter database open;
    SQL> archive log list
    Now you are able to take hot/online backup ,its upto you you use user managed backup and recovery or use RMAN oracle own shipped free tool for backup and recovery ,however my recommendation would goes for RMAN.
    http://download-uk.oracle.com/docs/cd/A97630_01/server.920/a96572/toc.htm
    http://www.oracle.com/technology/deploy/availability/htdocs/rman_overview.htm
    ARCHIVELOG mode, is the size grow very fast or other
    effect will overcome?However, the growing size pace either fast or slow everyday can be impractical it alls depends on activity of yours database operation.You will have to observe it yourself by turning on archive log its vary database to database activity.
    Khurram

  • Shell scripting for hot backup

    Hi,
    can you please give me shell scripting and it's explanation for taking hot backup. and which shell scripts are frequently use in real time.
    thank a lot in advance.

    HAve you ever heard about RMAN ? Much better than reinvent the wheel.
    http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/rcmquick.htm
    Nicolas.

  • RMAN HOT BACKUP ON DISK

    Hi All,
    I want to take online full hot backup on disk through RMAN.
    Is it possible can any one provide me a sample script.
    Regards,
    Umair

    hi
    run
    crosscheck backup;
    delete noprompt obsolete;
    allocate channel ch1 type disk;
    allocate channel ch2 type disk;
    backup
    database tag='full_database_backup_and_ctl' include current controlfile fo
    rmat '/oracle/backup/rman_bk/fulldb_%u%s%p';
    sql "alter system switch logfile";
    backup
    archivelog all delete input format '/oracle/backup/rman_bk/arch_%u%s%p';
    backup current controlfile format '/oracle/backup/rman_bk/ctl_%u%s%p';
    Release channel ch1;
    Release channel ch2;
    Thanks
    Kuljeet Pal Singh

Maybe you are looking for

  • Virtual machines won't reboot

    I am having a problem with Windows XP guests hanging up when told to reboot remotely.  They start the process but then hang until I open the VMWare Server 2 console and actually launch the console of the guest machine.  As soon as I click in the gues

  • Nice footage in FCP, but washed out in export

    I've tried searching everywhere for a solution to this but I just don't know what to do anymore. I'm working with HD footage and when I export it to quicktime, most of the clips in the sequence become washed out, gain a bit of red color in certain ar

  • Disable a field at Item level for SC confirmation Screen

    Dear All , PLEase help me with a step by step instruction on how to disable field at Item level of  confirmation screen of SC . I tried in Webdynpro component : Web Dynpro Component:/SAPSRM/WDC_DODC_CONF_IBD in se80 and below is what I get ; When I c

  • Podcasts not showing

    All my vidio podcasts dont show, under the podcast folder in the vidio section.

  • Do I need mobile me to use find my iPad

    I want to use find my iPad but I found out that you can't subscribe to mobile me any more, what do I do?