RMAN Backup keep forever

Hi all,
I want to keep Rman backup for forever.
But i dnt want to retian archive log .
Kindly suggest.
Regards

RMAN> BACKUP TAG Q107 DATABASE KEEP FOREVER;
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: "consistent, logs, nologs"
RMAN-01007: at line 1 column 38 file: standard input

Similar Messages

Backup keep forever with restore point!

Hi,
I backup my tablespace test and keep forever
rman>backup tablespace 'TEST' keep forever restore point 'GOOD_POINT' format '/u01/%U';
Now i want to restore to the restore point 'GOOD_POINT'
How can i do ?
Please help
Thank you!

See my example on 11.2.0.1 on Windows 7 Test instance :
SQL> create tablespace test datafile 'E:\APP\SERVERROOM\ORADATA\ORCL\TEST.DBF' size 10M;
Tablespace created.
SQL> create table testtbl (a number) tablespace test;
Table created.
SQL> insert into testtbl values (1);
1 row created.
SQL> insert into testtbl values (2);
1 row created.
SQL> commit;
Commit complete.
SQL> insert into testtbl values (3);
1 row created.
SQL> insert into testtbl values (4);
1 row created.
SQL> commit;
Commit complete.
SQL> select * from testtbl;
         A
         1
         2
         3
         4
SQL> exit
C:\Windows\system32>rman target scott/tiger catalog rman/rman@orcl
RMAN> sql 'alter tablespace test offline';
sql statement: alter tablespace test offline
starting full resync of recovery catalog
full resync complete
RMAN> backup tablespace 'TEST' keep forever restore point 'GOOD_POINT' format '/myfolder/%U';
Starting backup at 19-MAY-12
current log archived
using channel ORA_DISK_1
backup will never be obsolete
channel ORA_DISK_1: finished piece 1 at 19-MAY-12
piece handle=E:\MYFOLDER\0GNBCBOA_1_1 tag=TAG20120519T120519 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 19-MAY-12
RMAN>exit
SQL> insert into testtbl values(5);
1 row created.
SQL> insert into testtbl values(6);
1 row created.
SQL> insert into testtbl values(7);
1 row created.
SQL> commit;
Commit complete.
SQL> select * from testtbl;
         A
         1
         2
         3
         4
         5
         6
         7
7 rows selected.
RMAN> run
2> {
3> restore tablespace 'TEST' to restore point 'GOOD_POINT';
4> recover tablespace 'TEST' to restore point 'GOOD_POINT';
5> }
Starting restore at 19-MAY-12
using channel ORA_DISK_1
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 00007 to E:\APP\SERVERROOM\ORADATA\ORCL\TEST.DBF
channel ORA_DISK_1: reading from backup piece E:\MYFOLDER\0DNBCBO2_1_1
channel ORA_DISK_1: piece handle=E:\MYFOLDER\0DNBCBO2_1_1 tag=TAG20120519T120519
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
Finished restore at 19-MAY-12
Starting recover at 19-MAY-12
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 05/19/2012 12:35:02
RMAN-00600: internal error, arguments [5525] [point] [] [] []
This issue is fixed in 11.2.0.2 (Server Patch Set) --- Source: http://agstamy.blogspot.in/2011/01/tspitr-using-restore-point-on-10gr2.html
SQL> column name for a40;
SQL> column time for a40;
SQL> select name, scn , time
2 from v$restore_point where name='GOOD_POINT';
NAME                                            SCN TIME
GOOD_POINT                                  3423591 19-MAY-12 12.05.25.000000000 PM
RMAN> run
2> {
3> recover tablespace 'TEST' until scn 3423591 auxiliary destination = 'E:\APP\SERVERROOM\ORADATA\ORCL';
4> sql 'alter tablespace "TEST" online';
5> }
Starting recover at 19-MAY-12
using channel ORA_DISK_1
Creating automatic instance, with SID='tilr'
... Its a huge output screen, so i am removing it, to make post shorten !
auxiliary instance file E:\APP\SERVERROOM\ORADATA\ORCL\ORCL\DATAFILE\O1_MF_SYSTEM_7VGLTPFQ_.DBF deleted
auxiliary instance file E:\APP\SERVERROOM\ORADATA\ORCL\ORCL\CONTROLFILE\O1_MF_7VGLTD17_.CTL deleted
Finished recover at 19-MAY-12
sql statement: alter tablespace "TEST" online
starting full resync of recovery catalog
full resync complete
RMAN>
SQL> select * from testtbl;
         A
         1
         2
         3
         4
SQL>If this answer your question, please close the thread, else continue.
Regards
Girish Sharma
Edited by: Girish Sharma on May 19, 2012 1:17 PM

Considerations for keeping RMAN Backup Retention to 1 Year

Dear All,
We are using 2-node 10gR2 RAC on Windows Server. We use Symentec Netbackup 7.5 for backing up Oracle databases. We want to change the retention period of RMAN backups to 1 year. Other than changing the RMAN Backup recovery window to 365, what are the other considerations (other configuration change, other point etc) we should be aware of?
Best regards,
Riaz

> Other than changing the RMAN Backup recovery window to 365, what are the other considerations (other configuration change, other point etc) we should be aware of?
Use RMAN Catalog.
How to restore your database if a storage failure occurs and all files on filesystem be lost and all rman files be at MML.
RMAN need a catalog to request files from MML (this catalog can be a controlfile, rman catalog or both), so if you lost your controlfile without RMAN Catalog you need manually find desired files on MML and restore it one by one if these files are not cataloged in that controlfile restored, since Oracle does not catalog files stored at MML. RMAN catalog files only stored on disk.

RMAN backup with no expiry

Hi,
We are using oracle 11gR2 on AIX 6.1,
We have to take the RMAN backup which should be never expired and we dont have any catalog,
for "KEEP FOREVER" option we require catalog,
any other way not to expire RMAN backup?
Thanks

Assuming this is a once off requirement, it is just a case of taking a cold backup of the database including the controlfile and any archivelogs and then storing these offline.
A copy of the pfile as well as a text copy of the controlfile (backup controlfile to trace) should also be taken.
As long as you have all of this , it should be possible to restore/recover your database to the start point.

RMAN backup and TSM question

We have rman backup file name contains the datetime so it is unique and easy to tell. But TSM keeps every file 4 versions, so the backup file (always 1 version because of unique name) will stay on tape forever. I have no idea about TSM, according to your experience, what is the normal solution here?

Dedicated forum for {forum:id=74}.
But quickly, in general, "DBA" and "TSM/Storage manager" need to agree on media manager use and setup the system accordingly.
Edited by: orafad on May 19, 2011 3:00 PM

RMAN backups and Flash Recovery Area

I have Oracle database 10.2.0.4 running on red hat 4.5 box. We are using a recovery catalog.A backup script runs everyday with option keep forever logs and retention policy is set to redendency 2.
We have Flash recovery area.
What will be criteria for Flash recovery area files to become obsolete?
Thanks

Is that mean that files in FRA are not effected by keep clause?
To be more specific Files which status is unavailable with RMAN are they eligible for automatic deletion policy in FRA?
Edited by: user11985663 on Dec 2, 2009 7:28 AM

Rman backup - how to preserve the file names exactly when backing up?

Hi,
I have been using RMAN for backup and I want to change things so that it is
easier to go back to the old tried-and-true method of recovery by recreating
a control file manually via the trace file, which lists the files out individually.
The first change - to change from compression to copy.. is fine.
But even then, rman names the files some weird name.
I am not trying this- using the disk format command is supposed to work..
rman nocatalog << EOF
connect target;
allocate channel for maintenance type disk parallelism 1 \
format '/agile/ora_flash_recovery_area/PECHA/backupset/backup/%U';
backup as copy database;
release channel;
but it still is using wierd (auto-generated) names for the data files as it backs up.
Has anyone else got this working? Thanks Marvin.

Ok here is why I would like exact filenames..
1) to speed the time of recovery. I am much more familiar with traditional recovery methods than RMAN, and while I myself installed and suggested RMAN for backups, our other (11i) database does not use RMAN and so I am more familiar with traditional recovery. So to be able to recover quickly I want to have these files as close as possible to the original names so that I can use my standard script (from a trace file) to recreate the control fiile. If I can get RMAN to spit out the filies with original names but keep RMAN for making the backup, I may ditch the rman bacjup script in chron and write a traditional hot backup script which copies the files the old fashioned way.
2) to reduce cloning time. The RMAN duplicate command is not as good as I thought. I was actually easier for me to restore RMAN backups first to a box that has all the same paths, and THEN shutdown (cold) these files and copy them cold to another server, and restore from there. Agaiin if I can get the original file names, I could choose to do recovery either way (RMAN or traditional) in a real emergency instead of being forced to use rman.
3) to be able to switch to a backup file in the FRA without having to rename it. Seems logical if it is already named correctly.
thanks ! Marvi

BB device deleting calendar entries dispite "Keep Forever" setting on

OK, here's my plight. I am using the latest o/s on my phones (Storm 9530 and a World Edition loaner, each of which exhibit the same problem) and Desktop Manager 5.0.1. I only perform "wired" syncs using the USB cord (I am NOT syncing wirelessly and I am not on an Enterprise Server). When trying to sync with Outlook 2007, my phone wants to delete hundreds of calendar items that I want to keep. When I cancel out of the sync, and check my phone, the items tagged for deletion are indeed already gone on the phone. All the posts that I have seen on this issue claim that "older" calendar items are being deleted by the user's phone, but mine seem to be indescriminate, in that some are old and some are quite recent. There doesn't seem to be any logic regarding which are chosen for deletion and which aren't. I've checked, and this doesn't seem to be a Memory Manager issue, as I have lots of room in my memory. I have my Keep Appointments setting set to "Keep Forever." My provider (Bell Mobility) is of little help on the issue, and conveniently claim that it is a data corruption problem. If that is true, wouldn't the problem occur consistently, on every sync? My problem seems to go away for days or weeks at a time, then pops up whenever, for whatever reason. Is anybody else experiencing this, and if so, any advice? Help!!!

Yep.. just happened for the several'th time to me also. I also am requesting BB support to identify the issue and rectify it please.. been around for a very long time from what I can see in the various forums.
BB support... please respond so we all can get this working.. Very frustrating to have to keep restoring my calendar.. very time consuming..
Just went through the process once again. It drops repeats though.. bit of a nuisance..
I ensure I regularly back up OUTLOOK calendar to comma DOS csv so I have it just in case.TIP.. ** Watch your Dates To Backup settings on the way through the wizard. Remember that what you put in the backup will be what BB will restore.. I went from 94 deleted to 243 added.. a tad excessive, but BB should clear 60 day stuff I think...
** make sure you haven't stored any calendar items on BB without duping to Outlook .. If there are, make sure you have written them down or something.. maybe write them up in OUTLOOK BEFORE you do the backup.. I ensure I have as few as possible entries only in for just this sort of situation**
Then clear the calendar on the BB..
Then restore your OUTLOOK calendar.
Then sync BB and it will pick up the entries you just restored.
I'm probably just sprouting info I have picked up from several forums, but it works for me.

Rman backup with different retention

Hi,
I have to write script on RMAN backup retentions and policies.
My requirement is as below:
Daily backup Name and retentions : db_daily_bkp_sun,db_daily_bkp_mon...with 7 days retension
Weekly backup Name and retentions : db_wkly_bkp_01,db_wkly_bkp_02...with 4 backup retension
Monthly backup Name and retentions : db_mnth_bkp_jan,db_mnth_bkp_feb...with 12 backups
Yearly backup Name and retentions : db_yearly_bkp_2010,db_yearly_bkp_2011,db_yearly_bkp_2012
All backups will be full online. We have to store backups in local disk.
We have created backup locations on disk as below.
Daily : /orabackup/daily
Weekly : /orabackup/weekly
Monthly: /orabackup/monthly
Yearly : /orabackup/yearly
So is it possible to take such backups in RMAN without using any third party software ? If possible then please provide me such script.
With Regards,
Khokhar Murtuja S
Database Administrator

Hi,
RMAN will make you have only one retention.
You can have more kind of retention using the option "keep until" in your backup command.
It'll certainly do what you need.
Greets,
Loïc

RMAN backups need info about available options

Hi All
In our new 10.2.0.3 RAC environment on windows 2003 os we have our database configured on ASM and oracle home placed on OCFS. As it is a prod environment, we do not have the comfort to shutdown the cold copy of the database and so we're running the daily rman full db backup .. however, in case of an event where the datafiles need a restore.. I am not sure if the rman backup i take will be sufficient.. I issue the below command to take the full database backup and I get a compressed back up set..
RMAN> backup up device type disk format 'd:\database\%U' database;
I do have the FRA configured on ASM DG but i see that this DG is almost free. could any please advice what are the options available for me to take the entire database backup (including files) which can help me restore the datafiles if necessary.. my database is about 70GB in size but is very critical for organisations functioning..
thanks!
Sarat.

Thanks for the quick reply steve and werner...
Because we are doing a daily Full database backup (compressed) I did not include the archive logs to be backed up. In our environment, we keep moving arc logs to another archive location regularly. and once back up is complete and successful we clean up all archives using another job as we no longer would need them in case if we need to restore from the RMAN backup.. and as we retain all archives between one rman bkp and the next one.. we are also not backing up these along with the database.. Is this dangerous? I thought we will always have one database copy (compressed) available on disk and can help us restore from it if required.. But my major concern is what if a datafile is accidentally deleted/ disk fails on ASM. In this case.. the RMAN backup will not be sufficient because if cannot create the physical structure.. in such a case, will configuring the FRA it self be sufficient? Do I need to perform any additional steps to ensure the physical structure can also be restored? Please advice..
rman is configured to backup control file and sp file and my exact script looks like below .. and we run it every day
crosscheck backup;
crosscheck backup of controlfile;
delete force noprompt obsolete;
delete backup;
backup device type disk format 'D:\oracle\DBBackUp\%U' database;
exit;

WHAT IS BEST STRATEGY FOR RMAN BACKUP CONFIGURATION

Hi all,
my database size is 50GB I want TAKe WEEKLY FULL BACKUP AND INCREMENTAL BACKUP
WITHOUT RECOVERY CATALOG.by follwing commands
weekly full database backup
run
backup as compressed backupset
incremental level=0
device type disk
tag "weekly_database"
format '/sw/weekly_database_%d_t%t_c%c_s%s_p%p'
database;
I want do CONFIGURE RMAN BY FOLLWING stragtegy
CONFIGURE RETENTION POLICY TO REDUNDANCY window of 14 days.
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO
'\SW\AUTOCFILE_'%F';
and other is by default
sql>alter system set control_file_record_keep_time=15 days;
os--aix6 and for two database 10g2 and 11g2
what is best configuration strategy for rman backup.AND BACKUP WITH RECOVERY CATALOG OR WITHOUT RECOVERY CATALOG
PLEASE TELL ME
Edited by: afzal on Feb 26, 2011 1:45 AM

For simply two databases, there really wouldn't be a need for a recovery catalog. You can still restore/recover without a controlfile and without a recovery catalog.
From this:
afzal wrote:
CONFIGURE RETENTION POLICY TO REDUNDANCY window of 14 days.I am assuming you want to keep two weeks worth of backups, therefore these:
alter system set control_file_record_keep_time=15 days;
CONFIGURE RETENTION POLICY TO REDUNDANCY window of 14 daysShould be:
RMAN> sql 'alter system set control_file_record_keep_time=22';
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14;22 would give you that extra layer of protection for instances when a problem occurs with a backup and you want to ensure that data doesn't get aged out.

Best practice for RAC RMAN backup

I have a 10gR2 RAC db that is 3.5TB. It is a 2 node cluster on AIX. Each instance is db1 on node1, and db2 on node2, the "world" database name is db.
Currently we are doing our backup from 1 node of the cluster, specifying that it connect to to db2, so this instance is doing all of the backup work. We allocate 14 channels to back this database up to tape (yes, we have plenty of tape resources, connecting to a tape machine with > 20 physical tape drives). Would it be better to have our rman script connect to the general database db and let the listener decide which instance to send the channel allocation to, or keep all the work on one node.

I seem to remember that when I was reading up on RAC and RMAN a couple of years ago (maybe up to 4 years ago) that there was something about always doing backups from the same node in a RAC configuration i.e. you have logically 'db' in your network configuration and also direct names of 'db1' and 'db2', and you should always use one of 'db1' or 'db2' but never 'db'. And I also mean do not alternate between 'db1' and 'db2'. Pick one of them and always do your backups from that instance.
I think this was to do with things like the database identifier, and the instance identifier too, which RMAN reads and puts into the backup. It also affects things like reading the archive logs, which must be cross mounted to both nodes. I have this feeling that using the same node kept a kind of consistency within the backups, and meant that Oracle was getting all of the block images from one node i.e. from one of the SGAs. If you used both nodes simultaneously you could run into issues with their SGAs being out of sync. I know this does not make much sense, given that RAC is all about keeping the SGAs consistent with each other. But at the end of the day I do remember something about always using one node all the time to do your RMAN backups.
Not sure if these rules hold true if you are using ASM, which itself is shared in a RAC environment.
Things may have moved on since then, but that was still 10g Release 2 documentation, so I would guess it is still true. At the end of the day, it is not the backup that is important, but the recovery. You don't want to create any kind of inconsistent backup that RMAN cannot successfully recover, even though the backup may look good when you create it.
I'd check out the RMAN and RAC documentation further to see if this is supported.
John

About RMAN backup !!!!

Dear Friends,
Let my production server running starts from 1st June .
In 15 june , I take the First rman full (or level0) backup using the command :
RMAN> backup database plus archivelog;
In 20 June I take 2nd rman full backup using : RMAN> backup database plus archivelog;
Again in 30 June , I take the Third(3rd) rman full (or level 0) backup using the command :
RMAN> backup database plus archivelog;
And also my rman policy set as :
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
In the above scenario , I have the following questions :
1) When I take the Third(3rd) backup then is it the First RMAN backup goes to obsolete as per my rman policy ( RETENTION POLICY TO REDUNDANCY 1) ?
2) Is the above all RMAN backup make a link between them ?
3) If my first RMAN backup goes to obsolete and I have to delete the First RMAN backup , then which types of problem I face ? Can I go to previous state(suppose I need to back in 1st June) of my server if I delete First rman backup ?
4) when I take 3rd rman full backup , then is it all information from 1st january of the server are stored in the 3rd backup ? i.e., is the 3rd rman backup stores all the previous two rman backups information ?so that If I delete the previous two backup , then I get all information form 3rd rman backup .what is the actual scenario ......
plz help me to make clear concept about it .......
thx in advance .....

1) When I take the Third(3rd) backup then is it the First RMAN backup goes to obsolete as per my rman policy ( RETENTION POLICY TO REDUNDANCY 1) ?The REDUNDANCY parameter of the CONFIGURE RETENTION POLICY command specifies how many backups of each datafile and control file that RMAN should keep. In other words, if the number of backups for a specific datafile or control file exceeds the REDUNDANCY setting, then RMAN considers the extra backups as obsolete.So as in your case the redundancy is 1 so the 1st and 2nd backup are obsolete.
To check the obsolete backups run
rman> report obsolete;
To delete them
rman> delete obsolete;
Link:[http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/setup005.htm#BRBSC400]
Is the above all RMAN backup make a link between them ?I am not very much clear with the question.The RMAN information is stored in the controlfile.You can also create a new recovery catalog and register the target database. The RMAN repository records in the control file will be copied to the new recovery catalog.
when I take 3rd rman full backup , then is it all information from 1st january of the server are stored in the 3rd backup ? i.e., is the 3rd rman backup stores all the previous two rman backups information ?so that If I delete the previous two backup , then I get all information form 3rd rman backupThe 3rd RMAN backup will contain all the information of the DB from the very 1st day.You will get all the information in the 3rd rman backup as its a level 0 or what we say a FULL DATABASE BACKUP.If suppose the 3rd rman backup would have been a incremental backup, then you would have required a full backup, previous to the incremental one, so that after restoring the full backup, you restore the incremental to recover the DB completely.
Link:[http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/part1.htm#i996723]
[http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm#BRBSC133]
Forgot to answer the 3rd question
3) If my first RMAN backup goes to obsolete and I have to delete the First RMAN backup , then which types of problem I face ? Can I go to previous state(suppose I need to back in 1st June) of my server if I delete First rman backup ?well, i am not very much sure , but i think is , if you have the 1st rman backup pieces physically present on the disk, you can catalog it and then use the rman command to restore the data from it of till 1st june.
To catalog the backup pieces use
rman> catalog backuppiece 'filename';
Link: [http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/maint007.htm]
HTH
Anand
Edited by: Anand... on Oct 15, 2008 10:51 AM

RMAN BACKUPS TAKING A LONG TIME IN 11.1.0.6

Its almost 4 days since the RMAN Full Backup is running and it has completed almost 91% and is stuck at this point since last 2 days, so now we killed the RMAN backup Process and started the RMAN Full Backup on Disk. We need to take the RMAN Backups on Tapes.
When we take the RMAN Full Backup to Tape manually with the same script attached, the Backup runs successfully withing Hours. While if the RMAN Full Backup is running through Cronjobs , then it takes days and it gets hung.
Initially it happened with Full backup , now Incremental Backup is also not working.
Log File of Current RMAN Incremental Backup Running and in Hung state
Recovery Manager: Release 11.1.0.6.0 - Production on Mon Nov 5 20:00:02 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: ZSBO (DBID=4052190355)
RMAN>
2>
3>
4> run{
5> allocate channel t1 type 'SBT_TAPE'
6> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
7> allocate channel t2 type 'SBT_TAPE'
8> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
9> allocate channel t3 type 'SBT_TAPE'
10> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
11> allocate channel t4 type 'SBT_TAPE'
12> parms 'ENV=(NSR_SERVER=sa-backup01,NSR_CLIENT=sa-dm03b)';
13> backup
14> incremental level 2
15> format 'Incremental_zsbo_%U_%t'
16> (database);
17> sql "alter system archive log current";
18> backup
19> format 'arch_zsbo_%d_%s_%p_%t'
20> (archivelog from time 'sysdate-1' all delete input);
21> release channel t1;
22> release channel t2;
23> release channel t3;
24> release channel t4;
25> }
26>
using target database control file instead of recovery catalog
allocated channel: t1
channel t1: SID=2086 device type=SBT_TAPE
channel t1: NMO v4.5.0.0
allocated channel: t2
channel t2: SID=2075 device type=SBT_TAPE
channel t2: NMO v4.5.0.0
allocated channel: t3
channel t3: SID=2069 device type=SBT_TAPE
channel t3: NMO v4.5.0.0
allocated channel: t4
channel t4: SID=2061 device type=SBT_TAPE
channel t4: NMO v4.5.0.0
Starting backup at 05-NOV-12
channel t1: starting incremental level 2 datafile backup set
channel t1: specifying datafile(s) in backup set
input datafile file number=00096 name=/data13/oradata/zsbo/A0186LA2591_00_CURR_12.dbf
input datafile file number=00058 name=/data17/oradata/zsbo/A0436IL2022_00_PREV_01.DBF
input datafile file number=00014 name=/data7/oradata/zsbo/A1225NY2502_00_TEMP_01.dbf
input datafile file number=00087 name=/data7/oradata/zsbo/A1086IL2502_00_PREV_01.dbf
input datafile file number=00045 name=/data7/oradata/zsbo/A1143BO2515_00_CURR_IDX_01.dbf
input datafile file number=00130 name=/data7/oradata/zsbo/A0171LA2034_01_DEMO_IDX_01.dbf
input datafile file number=00080 name=/data7/oradata/zsbo/A0436IL2022_00_CURR_IDX_02.DBF
input datafile file number=00119 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_05.dbf
input datafile file number=00136 name=/data5/oradata/zsbo/A1225NY2502_00_TEMP_11.dbf
channel t1: starting piece 1 at 05-NOV-12
channel t2: starting incremental level 2 datafile backup set
channel t2: specifying datafile(s) in backup set
input datafile file number=00095 name=/data12/oradata/zsbo/A0186LA2591_00_CURR_11.dbf
input datafile file number=00075 name=/data17/oradata/zsbo/A0186LA2591_00_CURR_IDX_02.dbf
input datafile file number=00094 name=/data6/oradata/zsbo/A0186LA2591_00_CURR_10.dbf
input datafile file number=00151 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_06.dbf
input datafile file number=00148 name=/data8/oradata/zsbo/A1143BO2515_00_PREV_02.dbf
channel t2: starting piece 1 at 05-NOV-12
channel t3: starting incremental level 2 datafile backup set
channel t3: specifying datafile(s) in backup set
input datafile file number=00127 name=/data8/oradata/zsbo/A1143BO2515_00_PREV_01.dbf
input datafile file number=00018 name=/data15/oradata/zsbo/A1225NY2502_00_TEMP_05.dbf
input datafile file number=00062 name=/data15/oradata/zsbo/A0436IL2022_00_TEMP_02.dbf
input datafile file number=00081 name=/data15/oradata/zsbo/A1110CH2505_00_PREV_01.dbf
input datafile file number=00137 name=/data7/oradata/zsbo/A1225NY2502_00_TEMP_12.dbf
input datafile file number=00065 name=/data18/oradata/zsbo/A1086IL2003_00_CURR_01.dbf
input datafile file number=00103 name=/data2/oradata/zsbo/A0186LA2591_00_PREV_05.dbf
channel t3: starting piece 1 at 05-NOV-12
channel t4: starting incremental level 2 datafile backup set
channel t4: specifying datafile(s) in backup set
input datafile file number=00059 name=/data6/oradata/zsbo/A0436IL2022_00_PREV_02.DBF
input datafile file number=00068 name=/data5/oradata/zsbo/A0186LA2591_00_CURR_01.dbf
input datafile file number=00071 name=/data9/oradata/zsbo/A0186LA2591_00_CURR_04.dbf
input datafile file number=00078 name=/data10/oradata/zsbo/A0136NJ2533_00_CURR_01.dbf
channel t4: starting piece 1 at 05-NOV-12 ----> No Progress since last 10 hours
Any help will be appreciated.
Regards,
Mohit
Edited by: 969777 on Nov 6, 2012 4:29 AM

Hi,
We have upgraded our database from 10.2.0.3 to 11.1.0.6.
The Script runs fine when we take command line backup on disk which we took 6 days backup, but when we schedule the same on cronjob RMAN Full Backup completes till 91% and it hangs forever. Everything was running fine with Incremental backup which we took 2 days before and it ran successfully but the above log is of Incremental Backup which is still in Hang state from the last 10 Hours , but still showing no Errors.
Please let me know if anything you want to confirm.
Thanks for ur prompt response,
Mohit

Delete RMAN backup

Oracle 11.2.0.1
Windows
I takes RMAN backup at D:\RMAN_BAKCUP of our test database. Now there is space problem, I have to allocate some space to other folder. I shall take cold backup of database by shutdown. How do I start to delete RMAN backup from above location. It is incremental backup. What precautions should be there while deleting RMAN backup with archive logs.
Can I delete all archive logs too after consistent backup by shutting down the database ?
I am facing space problem, thats why I though that I shall take cold backup of db and now no need of rman backup as well as archive logs. Am I correct ?
Thanks.

user12050217 wrote:
Oracle 11.2.0.1
Windows
I takes RMAN backup at D:\RMAN_BAKCUP of our test database. Now there is space problem, I have to allocate some space to other folder. I shall take cold backup of database by shutdown. How do I start to delete RMAN backup from above location. It is incremental backup. What precautions should be there while deleting RMAN backup with archive logs.
Can I delete all archive logs too after consistent backup by shutting down the database ?
I am facing space problem, thats why I though that I shall take cold backup of db and now no need of rman backup as well as archive logs. Am I correct ?
Thanks.Given what else I've read in this thread (test database, no need for point in time recovery, etc.) A 'cold' backup may be appropriate, but I'd still use rman to do it. I have a similar situation right now with one of my test databases. I took an rman cold backup (database is open MOUNT) with KEEP UNTIL 'SYSDATE + 60'. Once, sometimes twice, a day the developer asks for a restore to the backup. Piece of cake with rman, especially with a little script all ready to go. Would be a bit more difficult with a 'user managed' backup.

RMAN Backup keep forever

Similar Messages

Maybe you are looking for