Incremental Backup of archivelog

Hi All,
I'm new in administration of Oracle and confused about the concept of backup and recovery.
1. The documentation said the archivelog can be deleted once the Backup has been performed. Is that true? But I want to keep them for 3 days
2. I did an incremental level 0 yesterday and level 1 backup today on the datafiles and archivelog. I found that the data file sizes of both days are quite small and different every day. But for the archivelog backup, the file size is very large and similar every day. What's the proper way to perform incremental level 1 backup on archivelog?
Thanks in advance!

1. The "DELETE INPUT" specification in the Backup command deletes ArchiveLogs immediately after the backup. If you do not want them deleted immediately, do not include the DELETE INPUT specification in your Backup command. (the default is to not delete archivelogs immediately).
To delete archivelogs seperately, you can add the command
delete archivelog until time='sysdate-3';to your RMAN backup script to be executed after the backup is completed.
2. The keyword "INCREMENTAL" in the BACKUP command properly applies to DataFiles (database files0 and not to archivelogs. This is a directive to backup blocks within the datafile that have changed since the last backup. In archivelogs, no blocks are changed within a file -- every file is new.
To prevent an archivelog being backed up again you can use the "NOT BACKED UP 1 TIMES" in your backup command.
Thus
backup archivelog all not backed up 1 times;will only backup new archivelogs that haven't been backed up at the last run.
See the Oracle Backup and Recovery Reference documentation.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Similar Messages

Is incremental backup possible for archivelog.

Hi expert
i want to plan weekly and daily backup with windows redundancy 14 days.
full archivelog backup script
run
BACKUP AS COMPRESSED BACKUPSET
INCREMENTAL LEVEL = 0
DEVICE TYPE DISK
TAG = 'WEEKLY_ARCHIVELOG'
FORMAT '/oracle/ITB/db/apps_st/rman_backup/weekly_archivelog_%d_t%t_s%s_p%p'
ARCHIVELOG FROM TIME 'SYSDATE-7';
daily backup script
run
BACKUP AS COMPRESSED BACKUPSET
INCREMENTAL LEVEL = 1
DEVICE TYPE DISK
TAG = 'DAILY_INCREMENTAL_ARCHIVELOG'
FORMAT '/oracle/ITB/db/apps_st/rman_backup/daily_incremental_archivelog_%d_t%t_s%s_p%p'
ARCHIVELOG FROM TIME 'SYSDATE-1';
my question that if i will take backup then, will be any gap in sequnce
and second question is that ---is there incremental backup possible for archivelog.
os =aix6 and database 10g2

afzal wrote:
Dear Sir,
ok question number 2 is clear that incremental backup is not possible but still confuse
about sequence
if i did take backup of 17 feb at 12 o'clock seq 1,2,3,4
after that i did take backup 18th fab 1 pm then it will take from 6,7,8-------seq 5 is missing
please please correct my archive log script for weekly and daily backup with windows redundancy 14 days
again please correct my script
thnaksWHy you think the archive log file number 5 will be missing? RMAN automatically archives current redo log files and backups it
Why you don't test your backup script by your own and check results? Never trust anyone on your critical databases' backups, do it by your own!
Kamran Agayev A.
Oracle ACE
My Oracle Video Tutorials - http://kamranagayev.wordpress.com/oracle-video-tutorials/

Does it necessary to put the "plus archivelog" in incremental backup?

Hi
Because RMAN is using the archivelog to create the incremental backup , does it necessary to put the "plus archivelog" in backup command?

VahidS wrote:
Hi
Because RMAN is using the archivelog to create the incremental backup , does it necessary to put the "plus archivelog" in backup command?
Please cite the documentation that says rman is using the archivelog to create the incremental backup.
Lacking documentation, please post a proof example.In your personal sandbox database, do the following:
1 - delete any existing archivelogs
2 - take a level 0 incremental backup
3 - generate a few archivelogs
4 - delete the generated archivelogs manually, using and os command
5 - take a level 1 incremental backup

Incremental Backups are Cumulative Vs Differential??

Dear all,
The followings are Weekly Full Backup and Daily Backup scripts:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
allocate channel ch1 type disk format '/u02/db/backup/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup incremental level 0 database plus archivelog delete all input;backup current controlfile;
backup spfile;
release channel ch1;
Daily Backup:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
allocate channel ch1 type disk format '/u02/db/BACKUP/RMAN/backup_%d_%t_%s_%p_%U.bck';
backup incremental level 1 cumulative database plus archivelog delete all input;delete noprompt obsolete;
delete noprompt archivelog all backed up 2 times to disk;
backup current controlfile;
backup spfile;
release channel ch1;
I will do the full backup on Sunday and daily backup on Mon to Sat.
Scenario 1:
Incremental Backups are cumulative, I need of sunday full backup and tuesday daily backup to restore the database if crash on wednesday.
Scenario 2:
Incremental Backups are differential, then I need of sunday full backup and all incremental backups until crash.
I am wondering which scenario (1 or 2) is for my scripts that I post on above? Because I have different answer from others.
Best Regards,
Amy

Your scripts are following the scenario 1. Incremental backups are by default
differential. Since you are using the keywork CUMULATIVE, it's the 1 scenario.
What made you doubtfull? Scripts are straight forward.......

About incremental backup

Dear Friends ,
We have a ORacle 10g database server which is 24x7 hours running . We take everyday RMAN full backup ,now we want to run "Incremental rman backup" 6 days in a week and "Full Backup" rest of the week . But in oracle article we read that
"RMAN can only create incremental backups of datafiles, not of archived redo log files or other files."
(source: http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup001.htm#BRBSC131)
In this moment I think , archivelog is very important for database recovery and it is necessary to take archivelog backup regularly .Now if we want to run Incremental backup then I think I cannot take "archivelog" backup using following script :
run
allocate channel t1 type 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
sql "alter system switch logfile";
backup incremental level 1 database plus archivelog;
Give me some idea plz ... ...what should I need to ?

Sorry Hemant ,
Accroding to ur advice , I run the script following way :
run
allocate channel t1 type disk;
backup incremental level 1 database;
sql "alter system switch logfile";
backup archivelog;
But I got the following ERROR :
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "all, from, high, like, logseq, low, scn, sequence, time, until"
RMAN-01007: at line 6 column 18 file: standard input
RMAN>
But when I use the following script , it shows no error :
run
allocate channel t1 type disk;
sql "alter system switch logfile";
backup incremental level 1 database plus archivelog;
I think here database is backup only using LEVEL 1 , but archivelog is backed up full . Here is the output :
RMAN> run
2> {
3> allocate channel t1 type disk;
4> sql "alter system switch logfile";
5> backup incremental level 1 database plus archivelog;
6> }
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: sid=159 devtype=DISK
sql statement: alter system switch logfile
Starting backup at 29-JUL-08
current log archived
channel t1: starting archive log backupset
channel t1: specifying archive log(s) in backup set
input archive log thread=1 sequence=2 recid=1 stamp=661354070
input archive log thread=1 sequence=3 recid=2 stamp=661354123
input archive log thread=1 sequence=4 recid=3 stamp=661354895
input archive log thread=1 sequence=5 recid=4 stamp=661354935
input archive log thread=1 sequence=6 recid=5 stamp=661355047
input archive log thread=1 sequence=7 recid=6 stamp=661355050
input archive log thread=1 sequence=8 recid=7 stamp=661355072
input archive log thread=1 sequence=9 recid=8 stamp=661355327
channel t1: starting piece 1 at 29-JUL-08
channel t1: finished piece 1 at 29-JUL-08
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\BACKUPSET\2008_07_29\O1_MF_ANNNN_TAG20080729T143725_48
channel t1: backup set complete, elapsed time: 00:00:06
Finished backup at 29-JUL-08
Starting backup at 29-JUL-08
channel t1: starting incremental level 1 datafile backupset
channel t1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSAUX01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\USERS01.DBF
channel t1: starting piece 1 at 29-JUL-08
channel t1: finished piece 1 at 29-JUL-08
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\BACKUPSET\2008_07_29\O1_MF_NNND1_TAG20080729T143732_48
channel t1: backup set complete, elapsed time: 00:00:15
Finished backup at 29-JUL-08
Starting backup at 29-JUL-08
current log archived
channel t1: starting archive log backupset
channel t1: specifying archive log(s) in backup set
input archive log thread=1 sequence=33 recid=32 stamp=661358270
channel t1: starting piece 1 at 29-JUL-08
channel t1: finished piece 1 at 29-JUL-08
piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\TESTDB\BACKUPSET\2008_07_29\O1_MF_ANNNN_TAG20080729T143751_48
channel t1: backup set complete, elapsed time: 00:00:02
Finished backup at 29-JUL-08
Starting Control File and SPFILE Autobackup at 29-JUL-08
piece handle=D:\RMAN_BACK\CFC-2444681464-20080729-0C comment=NONE
Finished Control File and SPFILE Autobackup at 29-JUL-08
released channel: t1
RMAN>
what u think , am i right ?

RMAN: Increment backup very slow

Hi All,
We have Datawarehouse database having size around 7TB. Increment backup performance is extremely poor it is taking approx 14hrs to complete the process. We have also enabled block change tracking but failed to meet target.
Below mentioned DB info & RMAN configuration parameters:
DB: 11.1.0.6
OS: Linux 2.6.18-128.el5 x86_64
System has 16 processor when more than two process per CPU i.e. 32
CONFIGURE RETENTION POLICY TO REDUNDANCY 5;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/d01copy/control_bkp/autobackup_control_file%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 13 BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
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 COMPRESSION ALGORITHM 'BZIP2';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.1.0/dbs/snapcf_PRODDB.f'; # default
Thanks in advance.

Thnaks for reply.
Have you configured Compressed backups?
--> Yes. with below command.
RMAN> backup as compressed backupset incremental level 1 tag=$v_tag database;
Have you allocated channels ?
--> Yes.
allocate channel backup_disk1 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk2 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk3 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk4 type disk format '$v_bdest/%U' maxpiecesize 10G;
allocate channel backup_disk5 type disk format '$v_bdest/%U' maxpiecesize 10G;
What is the Large pool size configured? try to increase.
--> large_pool_size=1073741824
Is backup to DISK or TAPE? mentioned in script?
--> Backup goes to DISK only.
How is DISK performance?
--> How can we calculate DISK performance on LINUX?
Regards,

Create standby using incremental backup

can I create standby database using a backup of primary which was created using below command? ( incremental backup level 0)
BACKUP INCREMENTAL LEVEL 0 AS COMPRESSED BACKUPSET DATABASE TAG 'mybackup_date' PLUS ARCHIVELOG DELETE INPUT;
v11.2.0.2
physical standby

Hello;
Probably not. The backup command is missing this key piece :
backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';Since you are using 11R2 you can use "Create a Standby database from an active database using RMAN"
Example :
http://www.visi.com/~mseberg/standby_creation_from_active_database_using_rman.html
Or
RMAN duplicate for Data Guard standby
http://www.visi.com/~mseberg/duprman2.html
Best Regards
mseberg

What are the steps applying incremental backups to standby database 11g

Hi All,
I have built 11g none ASM standby database from ASM RAC Database. Now I want to apply incremental backup to the standby database from primary but not sure how to do it. I tried following and I had an error “ORA-01103: database name 'ins-prim' in control file is not 'ins-sec'”
1- I have configured standby database with RMAN backup.
2- After finishing installation, I took a incremental backup from primary server(ins-prim) and moved incremental backup and control file to the standby (ins-sec) database
3- I stared standby database nomount mode
4- restore controlfile from “incremental backup location in standby database”
5- alter database mount; and got this error
“ORA-01103: database name 'ins-prim' in control file is not 'ins-sec'”
What are the steps applying incremental backups to standby database with 11g?
Thank you

I build the database from backup and changed from ASM to none ASM and changed location of data files and logfiles. I think this changes makes the standby database as logical one.
You can a have a physical standby with different locations for everything (redo/controlfiles/datafiles), ASM and no ASM etc. I have a such a configuration in production (10gR2)
I build the database from backup
Are you sure you have a standby ? Ins-sec receives the archivelog files from the primary ? How did you proceed to build this database ? I suspect you don't have a standby at all ! If you have duplicated the database ins-sec and ins-pri are independent databases and you won't be able to apply an incremental backup (your script was not correct but it is another story)

Restore Tablespace incremental backup is not work as after reimage oracle

TheTablespace incremental backup Restore is not work as after reimage the oracle database or restore tablespace in standby machine(another machine) is not working .its working in the same machine without reimage .after reimage not working please clarify me ,
I need the solution as soon as please reply as soon as .
Commnads used:
This is the step is followed but i am getting backup or control file not found error.Its works i the application server is not reimaged ;
please give your valuable suggestion .
Product Used:oracle 11g in linux environmnet
1)Before taking backup get SCN number for restore.
Command applied: Select current_scn from v$database;
2)running Full backup of database
Command applied:
configure controlfile autobackup on;
backup database plus archivelog;
CROSSCHECK BACKUP;
exit;
3)Running level 0 incremental backup
Before taking backup get SCN number for restore.
Command applied:
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 0 TAG ='WEEKLY' TABLESPACE TEST;
exit;
3) Running level 1 incremental backup
Before taking backup get SCN number for restore.
Command applied:
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 TAG ='DAILY' TABLESPACE TEST;
4)Before Restore(TSPITR) following procedure are applied under sysdba privilege
Command applied:
SQL 'exec dbms_backup_restore.manageauxinstance ('TSPITR',1)';
5)TSPITR Restore command
Command applied:
run
RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
SQL 'ALTER TABLESPACE TEST ONLINE';
please calrfiy my following question:
1. After reimage(reinstall oracle database with application ).The aboove scenario is not working
2. After fullbackup what are the files needs to copy from (opt/oraclle/base/flash_recovery_area/dbname/) to repository because daily cleanup script will keep the data as sysdate -1 .
For fullbacckup we are currently copying entire (flash_recovery_area/dbname) database folder to repoistory.
3. after incremental backup what are the files needs to copy from (opt/oraclle/base/flash_recovery_area/dbname/..) to repository because daily cleanup script will keep the data as sysdate -1
For incremenatl backup currently we are copying (flash_recovery_area/dbname/backupset/<currentdate> and flash_recovery_area/dbname/autobackup/<currentdate>) folder to repoistory.
4.During restore we are copy entire things from repository to flash_recovery_area finaly apply the above mentioned restore command.
Tabelspace incremenatl restore is possible after reimage application server(fresh database)/another server with same database(standby machine) ....?
If we missing something in backup side please clarify me how to retore the tablespace incremental / level 0 tablespacae after reinstallion of server/another standby server.
Any information please let me know .I need the solution as soon as please reply as soon as .

Try the Recovery Manager (RMAN) instead. This forum is for feedback about the 11g XE Beta.

Restore using incremental backup with noarchivelog mode

Hello experts,
We are running SAP on Oracle databse(IN NOARCHIVELOG MODE) for which we are having full offline backup on every sunday and post which incremental backups on rest of the days. We have scenario to do restore db to the state till last friday's incremental backup.
Please let us know the procedure for restoring till that point. If possible using brtools utility(which is SAP specific).
Thank You
Regards,
Venkateshwar

If you do not want to read the whole doc This is the snippet for you.
Recovering a NOARCHIVELOG Database with Incremental Backups
Restoring a database running in NOARCHIVELOG mode is similar to restoring a database in ARCHIVELOG mode. The main differences are:
Only consistent backups can be used in restoring a database in NOARCHIVELOG mode.
Media recovery is not possible because no archived redo logs exist.
You can perform limited recovery of changes to a database running in NOARCHIVELOG mode by applying incremental backups. The incremental backups must be consistent, like all backups of a database run in NOARCHIVELOG mode, so you cannot make backups of the database when it is open.
When you are recovering a NOARCHIVELOG database, specify the NOREDO option on the RECOVER command to indicate that RMAN should not attempt to apply archived redo logs. Otherwise, RMAN returns an error.
To recover a NOARCHIVELOG database with incremental backups:
After connecting to the target database and the recovery catalog, place the database in a mounted state:
STARTUP FORCE MOUNT
Restore and recover the database.
For example, you can perform incomplete recovery with the following commands:
RESTORE DATABASE
FROM TAG "consistent_whole_backup";
RECOVER DATABASE NOREDO;
Open the database with the RESETLOGS option.
For example, enter the following command:
ALTER DATABASE OPEN RESETLOGS;

RMAN - Incremental backup / NOARCHIVELOG / Restore & Recover Until Cancel

I'm testing out a weekly plan as follows:
Sun : Shutdown db, RMAN level 0 Incremental Backup
Mon-Sat: Shutdown db, RMAN level 1 Incremental Backup.
The database is NOARCHIVELOG mode and is 10.2 XE.
I then run a restore (which I understand to be to move the datafiles from the backup set to their online location). My next aim is to do a recover.
I'm really confused at this point. Say I take the backup the night before (either a level 0 or 1, I'm assuming that this makes no difference) then in the morning I drop a table accidentally. Okay - I want to go back to the position after the backup. When I do recover, I understand that Oracle applies redo logs written since the backup.
So I don't want a recover, I want a recover until cancel. When I issue this command it is suggesting that I use an archive log file. Well obviously I don't have any of those so I press cancel thinking that this will bring me back to the point EXACTLY AFTER THE NIGHTLY BACKUP and with my table back. But it doesn't!
I would be really grateful if anyone has a definitive answer to this - what are the steps to recover a database to the point after the backup was taken ignoring any changes since the backup.
Thanks all.
Tom.

Hi Werner
Do you mean if the online logs are available with the changes after the last backup until the database restore then there is a possibility to apply changes? Ie at this point I could put in the redo log names instead of the archive log names.
If they have been overwritten since the backup (ie cycled round completely) then is the behaviour to restore the database and then not apply any logs?
Do you know if this is documented anywhere? There seems to be an emphasis on ARCHIVELOG mode only, especially in the books I have seen.
Thanks,
Tom

Incremental Backup -- Archive Logs

When we take incremental backups do we need archive logs?
Here is the scenario if I delete archive log's and then take a incremental level=1 backup of the database, is my database still recoverable?

Hi,
>>If a successful incremental backup was performed AFTER the archive log was deleted, you should be OK. If the archive log was deleted after the incremental backup, you should take another incremental backup.
if the archivelog was deleted that are generated before starting the backup then u don't need that archivelog after sucessfully completion of backup and if this is generated after the backup then u loss the data.So in that case u should take another backup.
Thanks
Kuljeet

Apply problem after sync with incremental backup

Hello all,
I have primary as rac with 4 nodes and one physical (all have asm)
I made incremental backup to re-sync my primary with physical standby and when i tried to start DG process the shiping is working but apply not workin : check please :
THREAD#,Last Standby Seq Received
1,29598
2,22308
3,27230
4,21868
THREAD#,Last Standby Seq Applied
1,28634
2,21227
3,25780
4,21104
when i run apply command i see in alert log file this :
Media Recovery Waiting for thread 4 sequence 1
Fetching gap sequence in thread 4, gap sequence 1-100
Tue Apr 07 12:06:49 2015
FAL[client]: Failed to request gap sequence
GAP - thread 4 sequence 1-100
DBID 1722434320 branch 849356882
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that's sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
the system searching for gab started with seq 1 in node 4 !!!!
how can i deal with that please ??

Thanks Stefan , kindly find below the output for both primary and standby :
1- select NAME,RESETLOGS_CHANGE#, CHECKPOINT_CHANGE#,CONTROLFILE_CHANGE#,CURRENT_SCN,RECOVERY_TARGET_INCARNATION# from v$database
Primary :
ORACLE,925702,3231069178,3231935937,3231937322,2
Standby :
ORACLE,925702,3096376393,3096507373,3096507372,2
2- list incarnation
Primary :
List of Database Incarnations
DB Key Inc Key DB Name DB ID            STATUS Reset SCN Reset Time
1       1       ORACLE   1722434320       PARENT 1          24-AUG-13
2       2       ORACLE   1722434320       CURRENT 925702     04-JUN-14
Standby:
List of Database Incarnations
DB Key Inc Key DB Name DB ID            STATUS Reset SCN Reset Time
1       1       ORACLE   1722434320       PARENT 1          24-AUG-13
2       2       ORACLE   1722434320       CURRENT 925702     04-JUN-14
3- select FILE#,RESETLOGS_CHANGE#,RESETLOGS_TIME, CHECKPOINT_CHANGE#,CHECKPOINT_TIME from v$datafile_header;
FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
         1            925702 04-JUN-14         3231779881 08-APR-15
         2            925702 04-JUN-14         3231779881 08-APR-15
         3            925702 04-JUN-14         3231779881 08-APR-15
         4            925702 04-JUN-14         3231779881 08-APR-15
         5            925702 04-JUN-14         3231779881 08-APR-15
         6            925702 04-JUN-14         3231779881 08-APR-15
         7            925702 04-JUN-14         3231779881 08-APR-15
         8            925702 04-JUN-14         3231779881 08-APR-15
         9            925702 04-JUN-14         3231779881 08-APR-15
        10            925702 04-JUN-14         3231779881 08-APR-15
        11            925702 04-JUN-14         3231779881 08-APR-15
     FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
        12            925702 04-JUN-14         3231779881 08-APR-15
        13            925702 04-JUN-14         3231779881 08-APR-15
        14            925702 04-JUN-14         3231779881 08-APR-15
        15            925702 04-JUN-14         3231779881 08-APR-15
        16            925702 04-JUN-14         3231779881 08-APR-15
        17            925702 04-JUN-14         3231779881 08-APR-15
        18            925702 04-JUN-14         3231779881 08-APR-15
        19            925702 04-JUN-14         3231779881 08-APR-15
        20            925702 04-JUN-14         3231779881 08-APR-15
        21            925702 04-JUN-14         3231779881 08-APR-15
        22            925702 04-JUN-14         3231779881 08-APR-15
     FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
        23            925702 04-JUN-14         3231779881 08-APR-15
        24            925702 04-JUN-14         3231779881 08-APR-15
        25            925702 04-JUN-14         3231779881 08-APR-15
        26            925702 04-JUN-14         3231779881 08-APR-15
        27            925702 04-JUN-14         3231779881 08-APR-15
        28            925702 04-JUN-14         3231779881 08-APR-15
        29            925702 04-JUN-14         3231779881 08-APR-15
29 rows selected.
Standby:
FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
         1            925702 04-JUN-14         3065328471 25-MAR-15
         2            925702 04-JUN-14         3065328464 25-MAR-15
         3            925702 04-JUN-14         3065328464 25-MAR-15
         4            925702 04-JUN-14         3065328461 25-MAR-15
         5            925702 04-JUN-14         3065328471 25-MAR-15
         6            925702 04-JUN-14         3065328471 25-MAR-15
         7            925702 04-JUN-14         3065328461 25-MAR-15
         8            925702 04-JUN-14         3065328471 25-MAR-15
         9            925702 04-JUN-14            1016743 04-JUN-14
        10            925702 04-JUN-14            1020278 04-JUN-14
        11            925702 04-JUN-14            1020681 04-JUN-14
     FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
        12            925702 04-JUN-14            1021083 04-JUN-14
        13            925702 04-JUN-14            1021086 04-JUN-14
        14            925702 04-JUN-14            1021877 04-JUN-14
        15            925702 04-JUN-14            1021880 04-JUN-14
        16            925702 04-JUN-14            1021883 04-JUN-14
        17            925702 04-JUN-14            1021886 04-JUN-14
        18            925702 04-JUN-14            1031089 04-JUN-14
        19            925702 04-JUN-14            1031555 04-JUN-14
        20            925702 04-JUN-14            1032064 04-JUN-14
        21            925702 04-JUN-14            1032525 04-JUN-14
        22            925702 04-JUN-14            1032922 04-JUN-14
     FILE# RESETLOGS_CHANGE# RESETLOGS CHECKPOINT_CHANGE# CHECKPOIN
        23            925702 04-JUN-14            1033338 04-JUN-14
        24            925702 04-JUN-14            1033731 04-JUN-14
        25            925702 04-JUN-14            1034126 04-JUN-14
        26            925702 04-JUN-14           90283375 09-JUL-14
        27            925702 04-JUN-14           90291448 09-JUL-14
        28            925702 04-JUN-14         3065328471 25-MAR-15
        29            925702 04-JUN-14         3065328461 25-MAR-15
29 rows selected.
4- select name,CHECKPOINT_CHANGE#,CHECKPOINT_TIME, UNRECOVERABLE_CHANGE# ,UNRECOVERABLE_TIME from v$datafile
Prmairy :
NAME
CHECKPOINT_CHANGE#
CHECKPOINT_TIME
UNRECOVERABLE_CHANGE#
UNRECOVERABLE_TIME
+ASM_ORADATA/oracle/datafile/system.274.849356797
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/sysaux.260.849356797
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/undotbs1.263.849356799
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/users.269.849356799
3232100160
04/08/2015 10:07:12
404,796,458
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/example.272.849356895
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/undotbs2.262.849357043
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/undotbs3.261.849357043
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/undotbs4.267.849357045
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/asd01.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/dev01.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/feed01.dbf
3232100160
04/08/2015 10:07:12
404,790,786
08/25/2014 22:36:42
+ASM_ORADATA/oracle/datafile/indx01.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/indx02.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/website01.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/website02.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/website03.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/website04.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/users01.dbf
3232100160
04/08/2015 10:07:12
404,796,505
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users02.dbf
3232100160
04/08/2015 10:07:12
404,796,502
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users03.dbf
3232100160
04/08/2015 10:07:12
404,796,499
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users04.dbf
3232100160
04/08/2015 10:07:12
404,796,496
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users05.dbf
3232100160
04/08/2015 10:07:12
404,796,493
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users06.dbf
3232100160
04/08/2015 10:07:12
404,796,490
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users07.dbf
3232100160
04/08/2015 10:07:12
404,796,487
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/users08.dbf
3232100160
04/08/2015 10:07:12
404,796,505
08/25/2014 22:36:50
+ASM_ORADATA/oracle/datafile/feed02.dbf
3232100160
04/08/2015 10:07:12
134,340,010
07/16/2014 22:06:21
+ASM_ORADATA/oracle/datafile/indx03.dbf
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/oracle/datafile/system_2_01
3232100160
04/08/2015 10:07:12
0
+ASM_ORADATA/catalog01
3232100160
04/08/2015 10:07:12
0
Standby :
NAME
CHECKPOINT_CHANGE#
CHECKPOINT_TIME
UNRECOVERABLE_CHANGE#
UNRECOVERABLE_TIME
+DATA/oracledrs/datafile/system.3248.875795981
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/sysaux.3244.875796111
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/undotbs1.3249.875796547
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/users.3255.875796621
3096432811
03/30/2015 07:55:20
404,796,458
08/25/2014 22:36:50
+DATA/oracledrs/datafile/example.3258.875796817
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/undotbs2.3256.875796823
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/undotbs3.3253.875796869
3096432811
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/undotbs4.3247.875797223
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/asd01.dbf
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/dev01.dbf
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/feed01.dbf
3096432813
03/30/2015 07:55:21
404,790,786
08/25/2014 22:36:42
+DATA/oracledrs/datafile/indx01.dbf
3096432803
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/indx02.dbf
3096432803
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/website01.dbf
3096432813
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/website02.dbf
3096432811
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/website03.dbf
3096432811
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/website04.dbf
3096432811
03/30/2015 07:55:20
0
+DATA/oracledrs/datafile/users01.dbf
3096432811
03/30/2015 07:55:20
404,796,505
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users02.dbf
3096432803
03/30/2015 07:55:20
404,796,502
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users03.dbf
3096432803
03/30/2015 07:55:20
404,796,499
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users04.dbf
3096432814
03/30/2015 07:55:21
404,796,496
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users05.dbf
3096432813
03/30/2015 07:55:21
404,796,493
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users06.dbf
3096432803
03/30/2015 07:55:20
404,796,490
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users07.dbf
3096432811
03/30/2015 07:55:20
404,796,487
08/25/2014 22:36:50
+DATA/oracledrs/datafile/users08.dbf
3096432814
03/30/2015 07:55:21
404,796,505
08/25/2014 22:36:50
+DATA/oracledrs/datafile/feed02.dbf
3096432813
03/30/2015 07:55:21
134,340,010
07/16/2014 22:06:21
+DATA/oracledrs/datafile/indx03.dbf
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/system_2_01
3096432814
03/30/2015 07:55:21
0
+DATA/oracledrs/datafile/catalog.288.873258217
3096432811
03/30/2015 07:55:20
0
Thanks in advance,

Script for daily Incremental Backup with Weekly full back?

Hi Can abybody plz give me the scrip for the daily incremental backup and weekly full backup.
Do we need 2 different scripts each for Incrmental and Full Backup or one will do.
Thanx in advance
Gagan

I will suggest you always
-backup archivelog daily when after yours backup database completion
-keep two days archivelog out of yours database storage to others device or
always take frequent archivelog to tape cartrideg after an hour depends yours
database activity pace.
You should also include archivelog backup within these backup scripts to others teriotry device i.e tape cartridge as well keep frequent archivelog backup if you think yours backup storage space is an issue or if you dont trust on yours backup storage media,keep an alternate tape cartridge for archivleog for frequent archivelog backup after every one hours depends the pace of yours database activity.Either backup archivelog frequently or multiplex the archvivelog to other devices.
Now you probably may confuse thats why i need archivelog backup command within this script when i am going to take incremental/full backup, its due to some thing happened with yours last backup got corrupted then you have alternate to restore before last backup.
Mon      Incremental + Archivelogs
Tue       Incremental + Archvielogs
Wed      Yours Database files got smokesWhat will you do
You will restore Tue backup and will apply alls redo from archivelogs which are generated to other devices yours data chances to be lost is minumum.You may lose only the current archivelog which is not yet to be log switched.If yours archivelog destination devices may corrupt then you have alternate to restore from tape cartridge.
If yours Tue backup cannot be restored even though you validate it after backup then you will have alternate to restore monday backup and you have backup of tue archivelog as well yours two days archivelog is also at another device then you may also recover the database till before crash.In this case you may lose only the current archivelog which is not yet to be log switched.
You cannot pile up archivelog to others device cause they begin to take a serious issue on disk thats why i mentioned two days archivelog to other device.
I hope now you clear why archivelog backup is essential with daily backup either its incremental or non incremental.
Khurram

Question about using an incremental backup to update a standby

We have a 2TB Oracle 10g database with a standby and the application that uses it is about to be updated. We're using cumulative incremental backups with block change tracking to back it up with weekly level 0 backups. The application upgrade will be making a lot of changes (several hundred GB) and we have stop the standby during the upgrade process as a quick way to get back (we don't have the space for a flashback recovery) in the event that there are issues with the upgrade. We can just let the archivelogs back up and get them over to the standby and applied once they decide they like the upgrade but, it looks like it would be simpler and perhaps quicker to use an incremental backup to update the standby. I probably won't but, If we do that, it looks like we can turn off archivelogs in the primary and not deal with them at all. I've never tried this but, I do have some questions.
Does it make sense to take this approach?
If we were to turn off archivelogs in the primary, would that have any effect on block change tracking? I don't see why it would but, had to ask. Of course, we would turn archivelogs back on and take a level 1 backup after the upgrade.
Thanks in advance for the education.

Funny you should mention that rolling upgrade, I'm actually planning to do that in another environment. My testing says it works pretty well and I'll be able to move a 400GB database to new hardware and upgrade it to 11g with very little downtime. However, in this case, the database is not being upgraded. The application is. It's just that, as part of that upgrade, there are a lot of updates and I'd just as soon not deal with the archivelogs for that. Here's what I was thinking about:
Set logs shipping to defer in the primary.
Stop log apply in the standby.
Turn off archivelogs in the primary.
Do the application update.
If they like the results, turn archivelogs back on in the primary.
Take an rman incremental backup from scn in the primary.
Apply the incremental backup to the standby.
Start log log apply in the standby.
Start log shipping in the primary.
The process for getting and using the incremental is described here:
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmdupdb.htm#BGBCEBJG
This isn't your regular incremental backup.
So, am I the only crazy one? Has anyone else tried this?

Incremental Backup of archivelog

Similar Messages

Maybe you are looking for