Tablespace PIT recovery

Hi,
I m new to recovery . I have a case in which i have to recover set of tablespaces PIT(point in time) in production database.
Database Name: ERSP
Version: 10.2.0.4
Backup Mode : User Managed Hot Backup
Frequency of Backup : Daily
Archive Mode : ON
Archive log Backup: Daily 8 times
Can any1 please tell me how m i suppose to do a complete tablespaces PIT recovery using latest User Managed Hot Backup and latest Archive log Backup ?
Thanks in advance

thanks for the response, is there any way to restore and recover it on the production "ERSP" database directly
below some of the backup details of ERSP production database
Database Name: ERSP
Server Name: Keyfp
Version: 10.2.0.4
Backup Mode : Daily User Managed Hot Backup [Mon-Fri]
                             : Weekly User Managed Cold Backup [Sat]
                  : Monthly      User Managed Cold Backup [1st Sat of each month]
                  : Yearly User Managed Cold Backup [1st Sat of January]
Archive Mode : ON
Archive log Backup: Daily and Weekly 8 timesEdited by: 832812 on Sep 28, 2011 11:49 PM

Similar Messages

PIT recovery until time when database was in backup mode

Hello,
Is it possible to recover database until some point/time which is within "time window" when database tablespaces were still in online backup mode?
I was basicaly replicatying database from source to target DB by putting DB to online backup mode, then copy all datafiles, after copy of datafiles was finished I started applying redologs generated on source DB afterwards. After I applied tens of redologs with "recover database until cancel using backup controlfile" and then typed "CANCEL" after 10-20 redologs applied I still got an error that opening DB would get an error due to inconsistent datafile. When I ended backup mode on source DB and applied few of redologs after ending backup mode on source DB datafiles were consistent.....
Thx a lot for answer in advance.

Hello Hemant K Chitale ,
thats clear. I probably did not express it clearly, so I will describe it once again:
Teoreticall scenario 1:
I put 'source" database to backup mode and start copy datafiles to "target" db. When copy of all datafiles is succesfully finished (lets say it 5:00AM), I don't issue "end backup" on source DB but I keep tablespaces in backup mode until 7:00AM. On target DB I will start recovery and apply redologs from source system.
Question 1:Is it possible to recover database until time 6:00AM? At this time all datafiles were already succesfully copied, BUT source db was still in backup mode. Or will I be able to get target DB to consistent state only after 7:00AM (end backup issuied on source DB) and not in window 5:00AM-7:00AM?
Teoreticall scenario 2 (small correction comparing to scenario1):
I will put source DB to begin backup mode at 5:00AM on 20.february and let it in this state until 7:00AM on 20.february. On target DB I will restore backup from source DB performed day before (or few days before does not matter) that means on 19.february and start to apply redologs generated after this backup.
Question 2: Will I be able to recover DB until 6:00AM on 20.february and open database after recovery until this time? Or wont I be able to recover and open DB witin window 20.february 5:00AM-7:00AM (source db in backup mode)
Bear in mind this is just teoreticly (don't ask me why would you do it and why you don't do it this way etc...). I just want to understand how it really works ;)
Thx a lot!

Brtools, PIT recovery fails after roll forward, BR0301E SQL error -1722 at

Running R/3 6.20/0019 with Oracle 9.2.0.8 on AIX 5.3
Brtools to restore and recover to point in time, this rolls through 300+ archive logs, and a datafile was added to an index tablespace after the backup, but this appears to be delt with successfully when applying the logs.
when I try to open the database through brtools I get the error:
BR0280I BRRECOVER time stamp: 2007-03-26 11.57.22
BR0595I Selecting indexes with NOLOGGING created during or after the selected backup bduuxcqq.anf 2007-03-14 20.00.00 ...
BR0285I This function can take several seconds/minutes - be patient...
BR0280I BRRECOVER time stamp: 2007-03-26 11.57.28
BR0301E SQL error -1722 at location BrIndNologGet-8
ORA-01722: invalid number
BR0669I Cannot continue due to previous warnings or errors - you can go back to repeat the last action
I can open the database from SQLPLUS, but Brtools fails.
Thank you.

Randy,
This sounds like an issue with the BRTOOLs then. 1722 is a rare error where the SQL statement attempts to convert a string into a number - like a date in this instance.
You may need to open a ticket with SAP Support and have them look at the issue, as you may need a fix for the toolset itself.
Sorry I could not be of more assisatance Randy.
-Tim

PIT recovery

I was testing the differential incremental backups. This is what I did. I backup with the following manner and edit one record on each level before execute the backup.
level 0, level 1, level 2 and level 3.
I deleted the backupset level 2 and did a point in time recovery back to the time between level 2 and level 3. But I noticed that the recovery was successful, the record I edited on level 2 before the backup is recovered.
Is it suppose to be that way ? Cause I had an impression of if one backupset lost, recovery will only be successful right until the time before the backupset was lost?

Every backup I included the archivelog as well. This is what i did :
1) Edit one record at 12:47:05
- Backup incremental Level 0
2) Edit second record at 13:31:12
- Backup incremental Level 1
3) Edit third record at 13:40:52
- Backup incremental Level 2
4) Edit last record at 16:43:26
- Backup incremental Level 3
This time I deleted the backup incremental 2 including the backup archivelog. And I perform a PITR to 13:41:00 and I still be able to recover the record i edited in step 3.
Why is it so?
Thanks.

Question on recovery

Hello all,
I think the following recovery should be possible but I'm not sure. Appreciate if you could shed some light.
Scenario
1) SCOTT user accidentally drops a table in SCOTT tablespace when the SCN was 100.
2) FLASHBACK is not enabled for the database. No way to Flashback the database.
3) RECYCLEBIN is set to OFF. No way to "Flashback table <tabname> to before drop".
2) Other users are still using the database and the SCN has progressed to 150.
Resolution to recover the tablespace to a point in time before the drop
1) alter tablespace SCOTT offline;
2) Restore datafiles belonging to SCOTT tablespace from the recent backup.
3) Restore all required arch logs.
4) recover tablespace SCOTT util scn=99
5) alter tablespace SCOTT online;
Is incomplete recovery possible at tablespace level within the live database? If yes, how can Oracle maintain SCOTT datafile at SCN 99 and all others at SCN 150?
To resolve the above situation, I normally create an auxillary database by just restoring and recovering system,sysaux,undo and scott datafiles from the most recent backup and perform an incomplete PIT recovery of the auxillary database to a point in time before the actual drop. I would then export and import the table from the auxillary database to the live database.
Restoring and recovering an auxillary database is a time consuming process so I was wondering if I could just restore and recover the affected tablespace in the live database itself.
Thanks for your time.

Hi Aman,
Thanks for your reply and time given to my doubt. Actually my doubt has raised due to above posted blog entry; in which the writer has not mentioned anything about another db. He simply has written:
"Assuming we have the latest backup, just executing the following statement would do everything needed to get the entire *tablespace* to a point-in-time in the past. Believe me, you don't have to do anything other than just this statement!"
So, here my doubt is how he is able to perform RMAN TSPITR without other db, with he help of recover tablespace ... auxiliary destination ...
I mean, even Hemant sir has said for Incomplete recovery; we need other db... So it caused me doubt please.
Sorry sir, if i am missing/asking something irrlavent to the OP's question.
Regards
Girish Sharma

Problem in performing multiple Point-In-Time Database Recovery using RMAN

Hello Experts,
I am getting an error while performing database point in time recovery multiple times using RMAN. Details are as follows :-
Environment:
Oracle 11g, ASM,
Database DiskGroups : DG_DATA (Data files), DG_ARCH(Archive logs), DG_REDO(Redo logs Control file).
Snapshot DiskGroups :
Snapshot1 (taken at 9 am): SNAP1_DATA, SNAP1_ARCH, +SNAP1_REDO
Snapshot2 (taken at 10 am): SNAP2_DATA, SNAP2_ARCH, +SNAP2_REDO
Steps performed for point in time recovery:
1. Restore control file from snapshot 2.
     RMAN> RESTORE CONTROLFILE from '+SNAP2_REDO/orcl/CONTROLFILE/Current.256.777398261';
2. For 2nd recovery, reset incarnation of database to snapshot 2 incarnation (Say 2).
3. Catalog data files from snapshot 1.
4. Catalog archive logs from snapshot 2.
5. Perform point in time recovery till given time.
     STARTUP MOUNT;
     RUN {
          SQL "ALTER SESSION SET NLS_DATE_FORMAT = ''dd-mon-yyyy hh24:mi:ss''";
          SET UNTIL TIME "06-mar-2013 09:30:00";
          RESTORE DATABASE;
          RECOVER DATABASE;
          ALTER DATABASE OPEN RESETLOGS;
Results:
Recovery 1: At 10.30 am, I performed first point in time recovery till 9:30 am, it was successful. Database incarnation was raised from *2* to *3*.
Recovery 2: At 11:10 am, I performed another point in time recovery till 9:45 am, while doing it I reset the incarnation of DB to *2*, it failed with following error :-
Starting recover at 28-FEB-13
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 03/06/2013 11:10:57
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
start until time 'MAR 06 2013 09:45:00'
ORA-00283: recovery session canceled due to errors
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+DG_REDO/orcl/onlinelog/group_1.257.807150859'
ORA-17503: ksfdopn:2 Failed to open file +DG_REDO/orcl/onlinelog/group_1.257.807150859
ORA-15012: ASM file '+DG_REDO/orcl/onlinelog/group_1.257.807150859' does not exist
Doubts:
1. Why did recovery failed 2nd time, but not 1st time and why is RMAN looking for online redo log group_1.257.807150859 in 2nd recovery ?
3. I tried restoring control file from AutoBackup, in that case both 1st and 2nd recovery succeeded.
However for this to work, I always need to keep the AutoBackup feature enabled.
How reliable is control file AutoBackup ? Is there any alternative to using AutoBackup, can I restore control file from snapshot backup only ?
4. If I restore control file from AutoBackup, then from what point of time/SCN does RMAN restores the control file ?
Please help me out in this issue.
Thanks.

992748 wrote:
Hello experts,
I'm little newbie to RMAN recovery. Please help me in these doubts:
1. If I have datafiles, archive logs & control files backup, but current online REDO logs are lost, then can I perform incomplete database recovery ?yes, if you have backups of everything else
2. Till what maximum time/scn can incomplete database recovery be performed ??Assuming the only thing lost is the redo logs, you can recover to the last scn in the last archivelog.
3. What is role of online REDO logs in incomplete database recovery ? They provide the final redo changes - the ones that have not been written to archivelogs
Are they required for incomplete recovery ?It depends on how much incomplete recovery you need to do.
Think of all of your changes as a constant stream of redo information. As a redolog fills, it is copied to archive, then (eventually) reused. over time, your redo stream is in archivelog_1, continuing into archvivelog_2, then to 3, and eventually, when you get to the last archivelog, into the online redo. A recovery will start with the oldest necessary point in the redo stream and continue forward. Whether or not you need the online redo for a PIT recovery depends on how far forward you need to recover.
But you should take every precaution to prevent loss of online redo logs .. starting with having multiple members in each redo group ... and keeping those multiple members on physically separate disks.

Config recovery catalog database

dear all.
i had read several documents about "create recovery catalog", but all of that start with statement
CREATE TABLESPACE
...and continue with CREATE USER, etc.
I want to create a NEW database for recovery catalog, this database what characteristics must to have ?? Anyone have a link or document where explain me how to create a database (only i need database creation) for recovery catalog.???
thanks
The version is ORacle 10gr2

hi,
the recovery catalog is just a normal database with a schema called rman or whatever you choose.
it should ideally be on a separate server to your target database. The RMAN database as with any other database should have multiplexed control files and redo files.
schema creation assumming windows O/S
-- Create tablepsace to hold repository
CREATE TABLESPACE "RMAN"
DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
-- Create rman schema owner
CREATE USER rman IDENTIFIED BY rman
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE rman
QUOTA UNLIMITED ON rman;
GRANT connect, resource, recovery_catalog_owner TO rman;
then create the recovery catalog
C:>rman catalog=rman/rman@w2k1
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
recovery catalog is not installed
RMAN> create catalog tablespace "RMAN";
recovery catalog created
RMAN> exit
Recovery Manager complete.
C:>
then register your database
C:>rman catalog=rman/rman@w2k1 target=sys/password@w2k2
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: W2K2 (DBID=1371963417)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete
RMAN>
let us know how you get on.
rgds
alan

How to recover tools tablespace???

Hi,
actually i was playing my database,where i have done few things like..
1.i manually delete backups of my database.
2.create autobackup of control file and and restore autobackup controlfiles which replcae previous controlfile.
3.after restoring my autobackup controlfile i tried to open the database,but then i recived a error in which the rman says that my system tablespace need recovery.i couden't able to perform this task because of no backup of my database.
4.aftre i thoght i decided to recreate a controlfile because at that time it seems the only option to get my database back any sort of life.
5.i made all the required changes which was needed to create a ctlfile.fortunatly i got sucess in creating a controlfile abd i thought i've done it,but when i tried to open my database it says that the file was inconsistent
due to failed media recovery and this won't allow to me open the database until unless i recover my tools tablesapce.
6.now the quesion i want to ask is weather i can able to recover my tools tablespace,or i again need to recreate a ctlfile withought having tools datafile in my ctlfile.i wish if there is any hope so i able to open my database withough loosing system tablespace.
your help would highly appriciated.
thanks
Alok Kumar.

Asif Kabir,
The OP cannot recover the dropped tablespace into the current database as the tablespace no longer belongs to the database.
He will have to do a Point In Time Recovery and then copy data back.
Even the method documented here (as TSPITR) will not work
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmtspit.htm#i1014116
He has to do a manual restore and recover the database (e.g to an alternate server / database name) to a point before the DROP. And then export data from that recovered instance and import it into the production database.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Recovery scenarios

Hi,
I am doing testing on recovery. Can some one guide me to a link where I can find some good recovery scenarios.
I have gone through the following one:
http://docs.oracle.com/cd/B12037_01/server.101/b10735/recov.htm
Appreciate ur help

What I would do is setup a test recovery database.
Then I would document "How the failure scenario was setup" and the recovery plan.
I would start with something like this :
RMAN Block Media Recovery
RMAN Cancel Based Recovery
RMAN Duplicate Database on new Host
RMAN Log Sequence based recovery
RMAN loss of all Control files No Catalog
RMAN Loss of all Control Files
RMAN loss of all database files including SPFILE
RMAN Loss of data file and no Catalog
RMAN Loss of file containing Online Undo Segment
RMAN Loss of INACTIVE Online Redo Log Group
RMAN Loss of Media
RMAN Recovering Archived Logs Only
RMAN Recovering Datafile for which no backup exist
RMAN recovery from loss of all online redo log files
RMAN Recovery of a Datafile to a different location
RMAN Recovery of Databases with Read-Only Tablespaces
RMAN Recovery of LOSS SYSTEM TABLESPACE
RMAN Recovery of Read-Only Tablespace and Control file
RMAN Tablespace Point in Time Recovery
RMAN Time Based Recovery
You can google on some of these to get idea's for scenario's.
I would do a cold backup in case the RMAN test fails.
Make sure you have a method of adding data before/during the "failure" so you can test the results of the recovery.
Also stop and think about recoveries I have not listed.
Happy testing.
Best Regards
mseberg

Can RMAN do table-level recovery

Hi,
I know that you can do database and tablespace level recovery using RMAN. Can you also do table-level recovery? How granular can you get?
Thanks

For table level recovery you can use flashback features:
Flashback Drop - Oracle now provides a way to use flashback to restore tables that were dropped accidentally.
Flashback Table - This feature introduces the FLASHBACK TABLE statement in SQL, which lets you quickly recover a table to a previous point in time without restoring a backup.
etc
Oracle Database has a group of features, known collectively as flashback, that provide ways to view past states of database objects, or to return database objects to a previous state, without using traditional point-in-time recovery.
Flashback features of the database can be used to:
* Perform queries that return past data.
* Perform queries that return metadata showing a detailed history of changes to the database.
* Recover tables or individual rows to a previous point in time.
Flashback features use the Automatic Undo Management system to obtain metadata and historical data for transactions. They rely on undo data: records of the effects of individual transactions. Undo data is persistent and survives a database malfunction or shutdown. Using flashback features, you employ undo data to query past data or recover from logical corruptions. Besides your use of it in flashback operations, undo data is used by Oracle Database to do the following:
* rollback active transactions
* recover terminated transactions using database or process recovery
* provide read consistency for SQL queries
Please refer here: http://www.stanford.edu/dept/itss/docs/oracle/10g/appdev.101/b10795/adfns_fl.htm
And an other method is, if table is very important and your db is working archive mod, you can recovery your database (skip unnecessary tablespaces which is not needed for saving space cost) to another host (disaster recovery), then take export that table, import to your working db or create database link between this databases insert into user.table1 as select * from user.table1@recoevered_database;

Three questions about replication/security

Hello,
We are currently planning to build software for our sales persons using C#. Each sales person has a laptop and should be able to sync the client information when he/she has access to the internet/intranet. Sales person can update client information and the local database will be synced back to master server when the user is connected to the internet/intranet. My option was to go with Oracle lite (as client DB) and Oracle enterprise (Server DB). But after readying the posts in this forum, I believe Oracle XE can do the trick. Am I right?
Second question is about the security of the replication. Sales persons can connect using the internet to sync the information back and forth. Is there a built in mechanism to secure the connection between the two DBs ( Oracle XE and EE)?
Third question is about the recovery options. I read Marks post about the feature of Oracle XE. I understood that PIT recovery and achivelog mode are supported. But, the post also says that Tablespace PIT is not supported. Can some tell me the difference between PITR and TSPITR? If PITR is supported, can I restore the database to a specific date and time (i.e. Dec 2, 2005 2:00PM)?
Thanks a lot

Comments inline
Hello,
We are currently planning to build software for our sales persons using C#. Each sales person has a laptop and should be able to sync the client information when he/she has access to the internet/intranet. Sales person can update client information and the local database will be synced back to master server when the user is connected to the internet/intranet. My option was to go with Oracle lite (as client DB) and Oracle enterprise (Server DB). But after readying the posts in this forum, I believe Oracle XE can do the trick. Am I right?
Yes - except that Oracle Lite comes with the synchronization built in, and it's tested to handle all the weird corner cases you have to deal with. XE will give you basic replication, however, you will have to build the connect, replicate (refresh materialized views), disconnect logic yourself (and test it). Personally I would spend the $100 on the Oracle Lite option
Second question is about the security of the replication. Sales persons can connect using the internet to sync the information back and forth. Is there a built in mechanism to secure the connection between the two DBs ( Oracle XE and EE)?
It depends by what you mean secure. When you connect XE to Enterprise Edition, it will use a database link to refresh the materialized views (replicated tables). Userids/passwords across the database link will be sent in an encrypted form. The data will not. I'm guessing you could use Oracle's Advanced Security option to secure the database links from XE to EE, but I'm not 100% sure. Tom may be able to give us a clue on this one. Also, note that DBLinks by default use the TCP/IP transport, so thats a hole you would have to kick in the firewall if the EE database was behind it (as it should be). Although replication can use HTTP as a transport mechanism
(You can see all the issues you start to get into - the $100 dollars per Oracle Lite deployment is looking real goo to me right about now)
Third question is about the recovery options. I read Marks post about the feature of Oracle XE. I understood that PIT recovery and achivelog mode are supported. But, the post also says that Tablespace PIT is not supported. Can some tell me the difference between PITR and TSPITR? If PITR is supported, can I restore the database to a specific date and time (i.e. Dec 2, 2005 2:00PM)?
Yes - you can roll forward the entire database to a given point in time using RMAN (which will be in production). You cannot however roll forward just a subset of tablespaces (i.e a subset of the data) in XE. Tablespace PITR is an EE feature (and not for the faint hearted).
Thanks a lot

Related to flash point in cg02

Hi,
what is table and field name from which we get the value of flash point in case of dangerous and non dangerous goods? no F1 help available for that.
thanx in advance.
regards
saurabh

992748 wrote:
Hello experts,
I'm little newbie to RMAN recovery. Please help me in these doubts:
1. If I have datafiles, archive logs & control files backup, but current online REDO logs are lost, then can I perform incomplete database recovery ?yes, if you have backups of everything else
2. Till what maximum time/scn can incomplete database recovery be performed ??Assuming the only thing lost is the redo logs, you can recover to the last scn in the last archivelog.
3. What is role of online REDO logs in incomplete database recovery ? They provide the final redo changes - the ones that have not been written to archivelogs
Are they required for incomplete recovery ?It depends on how much incomplete recovery you need to do.
Think of all of your changes as a constant stream of redo information. As a redolog fills, it is copied to archive, then (eventually) reused. over time, your redo stream is in archivelog_1, continuing into archvivelog_2, then to 3, and eventually, when you get to the last archivelog, into the online redo. A recovery will start with the oldest necessary point in the redo stream and continue forward. Whether or not you need the online redo for a PIT recovery depends on how far forward you need to recover.
But you should take every precaution to prevent loss of online redo logs .. starting with having multiple members in each redo group ... and keeping those multiple members on physically separate disks.

Help resolve please

Hi all,
Please can anyone help with resolving the errors below?
SQL> shutdown abort
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 118255568 bytes
Fixed Size 282576 bytes
Variable Size 83886080 bytes
Database Buffers 33554432 bytes
Redo Buffers 532480 bytes
Database mounted.
SQL> alter database open;
Database altered.
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-01124: cannot recover data file 1 - file is in use or recovery
ORA-01110: data file 1: 'E:\ORACLE9I\ORADATA\ORACLE\SYSTEM01.DBF'

The only reason why you would do a database recover it's because you are not able to open it, and v$recover_file dynamic view shows there are files not synchronized.
In this specific case, there are no critical files that need recovery (SYSTEM or UNDO), but other non-critical files would allow you to start database, but still would need recovery. Check the above referred view and ensure there are no rows, otherwise, perform a datafile/tablespace level recovery.
~ Madrid

Recover from full backup

Hi,
I want to recover a tablespace from a RMAN full backup. Now the related schema has many truncated objects (in a bach process), so normal tablespace restore, recovery won't help. Have to go for TSPITR. But the time I can't fix. Is there any other way to recover the tablespace other than point-in-time recovery ?

Hi Hemant,
When I run the TSIPTR recovery I am getting error,
RMAN> run {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
SEND 'NB_ORA_CLIENT=UBIHQ,NB_ORA_SERV=UBIHQ';
RECOVER TABLESPACE PD811T UNTIL TIME "to_date('02-JUL-2010 23:00:00','DD-MON-YYYY HH24:MI:SS')";
auxiliary destination '/tmp';
}2> 3> 4> 5>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "auxiliary": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, copy, convert, crosscheck, configure, duplicate, debug, delete, execute, endinline, flashback, host, mount, open, plsql, recover, release, replicate, report, restore, resync, }, set, setlimit, sql, switch, startup, shutdown, send, show, transport, validate"
RMAN-01007: at line 5 column 1 file: standard input

Delete old and backed up archive log,

Hi all,
Am trying to modify our RMAN backup script to delete old and backed up archive logs off the disk.
We run daily Incremental L0 or L1 backups, with 3 daily archive log backups. Currently we delete archive logs as they are backed up (backup archivelog all delete input). However, we are considering leaving x days worth of archive logs on disk, just in case, quick restore is needed (e.g. tablespace media recovery etc. etc.)
For example,
We can delete archive logs old tha n x (where x=no_days depending on database) by,
delete archivelog until time 'sysdate-15';
We can also delete archive logs that have been backed up to disk by,
delete archivelog all backed up 1 times to disk;
Questions,
1) Why does 'backed up 1 times to disk' require the 'all' in the statement ?
2) Is there any way to combine the 2 statements ? (backed up 1 times and older than x days ?). Just being a bit extra cautious to ensure that we have everything backed up. In real-world shouldn't be a problem, as we will be alerted to any backup failures, but trying to cater for the very worst situation.
Thanks for your help and insight.

Hi,
Scratch the questions. Found the answer in another thread. Seems when I tried to combine the statements initally, I had a typo.
It is now working as expected.
Thanks and regards,

Tablespace PIT recovery

Similar Messages

Maybe you are looking for