Why use RMAN CATALOG ?

Hi,
Anybody tell me why use RMAN CATALOG and what benifits if i have create catalog ?

No we have to configure it. I see. But did this user understand that when you quoted my reply ? We need to understand that a lot of users who post here need help and may not have the level of knowlege you have. So, a response like that adds more problems to the one they already have.
So even if you are using nocatalog, if it is not configured to auto backup and it is not backed up, you can still loose your RMAN repository.

Similar Messages

Doubt in taking backup using RMAN CATALOG

Hi,
when i was using RMAN CATALOG.
can i create separate database for catalog on server machin/backup server?
if create separate database for catalog?
how to create a separate database for catalog and plz give clear instruction one by one.
thanks

can i create separate database for catalog on server machin/backup server?
Yes.
and
also you create separate user to "recovery catalog" and "separate tablespace" for recovery catalog.
1.creation of recovery database catalog some like normal database catalog.
but after creation of database you create one user for recovery catalog.
Note :
"User that owns the recovery catalog schema. This is a user defined in the recovery catalog database that has been granted the RECOVERY_CATALOG_OWNER role."
http://download-west.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmcnctg002.htm

RMAN Backup using Rman Catalog

Hi
can we take backup of oracle9i database using oracle10g RMAN Catalog?
Thanks
With Regards
OH

I guess this is related to backward compatibility support principle. Target database's controlfile and RMAN catalog is synchronized and different version may have different structure and feature. When we need to completely restore an Oracle instance from backup, RMAN catalog must be able to support target database, and it may not be possible if RMAN catalog version is lower than target database. I hope I get the message across.
Pls anybody correct me if I am wrong

Question: Which is better and why....RMAN catalog or Flashback Recovery

Hey All,
Newly testing and reading up on 10g. I am on information overload and would appreciate pro's advice on which to choose and why.
Thanks,
d.

Different things, not necessarily alternative. That is, RMAN catalog is normally (at least should be) on another machine, and does not contain physical backups, but only information about them : physical backups are normally stored on external devices, like tapes.
Flashback Recovery technique is based on Flashback logs in Flash Recovery Area, which is a disk area on local machine, and so cannot be unlimited.
Therefore, Flashback Recovery is much faster than Media Recovery, since you don't need to restore anything, but you have limits in using that : your disks size.
On the other hand, RMAN backups are safer, being physically elsewhere.
See http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14220/backrec.htm#g1023042

Why do i get the following message when i attempt to open my backup file for lightroom cc? "Lightroom cannot use the catalog named "Lightroom Catalog" because it is not writable and cannot be opened". This message just started coming up after downloadi

why do i get the following message when i attempt to open my backup file for lightroom cc? "Lightroom cannot use the catalog named "Lightroom Catalog" because it is not writable and cannot be opened". This message just started coming up after downloading lightroom cc (previously using lightroom 5)...am i backing up properly or not???

Open Pictures folder and move the files named lrcat-journal and lrcat.lock to Desktop.
Make sure that , they are not inside Pictures folder any more and try to open backup from Lighrtroom and check..
Any LRcat file with .lock extension , move it to Desktop.

RMAN backup multiple database on multiple hosts using recovery catalog

I would like to know if I create one schema called "rman" is enough for repository for backing up multiple database on multiple machines using recovery catalog.
Or is there any better way to handle for reporting peposes.
Quick response is appreciated.
OS Solairs9.
Oracle 9i.
Thanks.
Srini

This worked perfectly fine except for putting sbt in single quotes.
See the reults below.
You are just great Daljith.
Thanks and I do appreciate your help.
Still you did not answe my question.
How come I see backups from June and May even though they are from
diffierent catalog database?
RMAN> allocate channel for maintenance device type 'sbt';
allocated channel: ORA_MAINT_SBT_TAPE_1
channel ORA_MAINT_SBT_TAPE_1: sid=9 devtype=SBT_TAPE
channel ORA_MAINT_SBT_TAPE_1: VERITAS NetBackup for Oracle - Release 5.0GA (200)
RMAN> crosscheck backup;
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_2_1_624018818 recid=1 stamp=624018818
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_1_1_624018817 recid=2 stamp=624018818
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_3_1_624019733 recid=3 stamp=624019733
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_5_1_624020641 recid=4 stamp=624020642
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_4_1_624020641 recid=5 stamp=624020642
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_6_1_624020677 recid=6 stamp=624020677
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_8_1_624115253 recid=7 stamp=624115253
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_7_1_624115252 recid=8 stamp=624115253
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_9_1_624116161 recid=9 stamp=624116161
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_11_1_624117067 recid=10 stamp=624117068
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_10_1_624117067 recid=11 stamp=624117068
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_13_1_624365687 recid=12 stamp=624365687
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_12_1_624365686 recid=13 stamp=624365687
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=bk_14_1_624366605 recid=14 stamp=624366605
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_16_1_624367501 recid=15 stamp=624367502
crosschecked backup piece: found to be 'EXPIRED'
backup piece handle=al_15_1_624367501 recid=16 stamp=624367502
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_22_1_628264333 recid=17 stamp=628264333
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_21_1_628264333 recid=18 stamp=628264333
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_23_1_628265249 recid=19 stamp=628265249
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-00 recid=20 stamp=628266151
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_26_1_628266195 recid=21 stamp=628266196
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_25_1_628266195 recid=22 stamp=628266196
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-01 recid=23 stamp=628266233
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_29_1_628267004 recid=24 stamp=628267004
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_28_1_628267004 recid=25 stamp=628267004
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=bk_30_1_628267919 recid=26 stamp=628267920
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-02 recid=27 stamp=628268832
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_32_1_628268875 recid=28 stamp=628268876
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=al_33_1_628268875 recid=29 stamp=628268876
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=c-2926506834-20070718-03 recid=30 stamp=628268913
Crosschecked 30 objects
RMAN> delete expired backup;
List of Backup Pieces
BP Key BS Key Pc# Cp# Status Device Type Piece Name
11820 11804 1 1 EXPIRED SBT_TAPE bk_2_1_624018818
11821 11805 1 1 EXPIRED SBT_TAPE bk_1_1_624018817
11822 11806 1 1 EXPIRED SBT_TAPE bk_3_1_624019733
11823 11807 1 1 EXPIRED SBT_TAPE al_5_1_624020641
11824 11808 1 1 EXPIRED SBT_TAPE al_4_1_624020641
11825 11809 1 1 EXPIRED SBT_TAPE al_6_1_624020677
11826 11810 1 1 EXPIRED SBT_TAPE bk_8_1_624115253
11827 11811 1 1 EXPIRED SBT_TAPE bk_7_1_624115252
11828 11812 1 1 EXPIRED SBT_TAPE bk_9_1_624116161
11829 11813 1 1 EXPIRED SBT_TAPE al_11_1_624117067
11830 11814 1 1 EXPIRED SBT_TAPE al_10_1_624117067
11831 11815 1 1 EXPIRED SBT_TAPE bk_13_1_624365687
11832 11816 1 1 EXPIRED SBT_TAPE bk_12_1_624365686
11833 11817 1 1 EXPIRED SBT_TAPE bk_14_1_624366605
11834 11818 1 1 EXPIRED SBT_TAPE al_16_1_624367501
11835 11819 1 1 EXPIRED SBT_TAPE al_15_1_624367501
Do you really want to delete the above objects (enter YES or NO)? y
deleted backup piece
backup piece handle=bk_2_1_624018818 recid=1 stamp=624018818
deleted backup piece
backup piece handle=bk_1_1_624018817 recid=2 stamp=624018818
deleted backup piece
backup piece handle=bk_3_1_624019733 recid=3 stamp=624019733
deleted backup piece
backup piece handle=al_5_1_624020641 recid=4 stamp=624020642
deleted backup piece
backup piece handle=al_4_1_624020641 recid=5 stamp=624020642
deleted backup piece
backup piece handle=al_6_1_624020677 recid=6 stamp=624020677
deleted backup piece
backup piece handle=bk_8_1_624115253 recid=7 stamp=624115253
deleted backup piece
backup piece handle=bk_7_1_624115252 recid=8 stamp=624115253
deleted backup piece
backup piece handle=bk_9_1_624116161 recid=9 stamp=624116161
deleted backup piece
backup piece handle=al_11_1_624117067 recid=10 stamp=624117068
deleted backup piece
backup piece handle=al_10_1_624117067 recid=11 stamp=624117068
deleted backup piece
backup piece handle=bk_13_1_624365687 recid=12 stamp=624365687
deleted backup piece
backup piece handle=bk_12_1_624365686 recid=13 stamp=624365687
deleted backup piece
backup piece handle=bk_14_1_624366605 recid=14 stamp=624366605
deleted backup piece
backup piece handle=al_16_1_624367501 recid=15 stamp=624367502
deleted backup piece
backup piece handle=al_15_1_624367501 recid=16 stamp=624367502
Deleted 16 EXPIRED objects
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Tag
11895 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11896 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11897 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11916 B F A SBT_TAPE 18-JUL-07 1 1
11926 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T142315
11927 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T142315
11935 B F A SBT_TAPE 18-JUL-07 1 1
11939 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11940 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11941 B F A SBT_TAPE 18-JUL-07 1 1 HOT_DB_BK_LEVEL0
11960 B F A SBT_TAPE 18-JUL-07 1 1
11970 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T150755
11971 B A A SBT_TAPE 18-JUL-07 1 1 TAG20070718T150755
11977 B F A SBT_TAPE 18-JUL-07 1 1
RMAN>
Message was edited by:
user539835

Backup/restore using RMAN with no catalog

Hi all,
Can someone tell me if this is correct:
I have two identical machines, same configuration and same file structure, everything is the same.
On machine A, I have a 9.2.0.7 database running. I take a hot backup and try to restore it on machine B.
Note: I am using RMAN for backup/restore whith no catalog.
This is how I perform backup on machine A:
ALLOCATE CHANNEL C1 TYPE DISK;
SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP INCREMENTAL LEVEL=0 CUMULATIVE format '/backup/level0_%u' BACKUP CURRENT CONTROLFILE format '/backup/control_primary' FORCE;
SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP ARCHIVELOG ALL format '/backup/archivelogs_%s_%t';
On machine B, here is how I perform restore:
SET DBID 1221334455;
RESTORE CONTROLFILE FROM '/backup/control_primary';
ALTER DATABASE MOUNT;
RESTORE DATABASE VALIDATE;
RESTORE DATABASE;
Recover database;
Thanks,

You forgot to restore the spfile or pfile on the second node to go to nomount state.
OR
You can use RMAN Duplicate to do this.
Regards
Message was edited by:
Singh

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.

Doubt about database point in time recovery using rman

Hi Everyone,
I have been practising various rman restore and recovery scenarios . I have a doubt regarding database point in time recovery using rman. Imagine i have a full database backup including controlfile scheduled to run at 10 PM everyday. today is 20th dec 2013. imagine i want to restore the database to a prior point in time ( say 18th dec till 8 AM). so i would restore all the datafiles from 17th night's backup and apply archives till 8 AM of 18th dec . in this scenario should i restore the controlfile too from 17th dec bkp ( i am assuming yes we should ) or can we use the current controlfile ( assuming it is intact). i found the below from oracle docs.
Performing Point-in-Time Recovery with a Current Control File
The database must be closed to perform database point-in-time recovery. If you are recovering to a time, then you should set the time format environment variables before invoking RMAN. The following are sample Globalization Support settings:
NLS_LANG = american_america.us7ascii
NLS_DATE_FORMAT="Mon DD YYYY HH24:MI:SS"
To recover the database until a specified time, SCN, or log sequence number:
After connecting to the target database and, optionally, the recovery catalog database, ensure that the database is mounted. If the database is open, shut it down and then mount it:
2. SHUTDOWN IMMEDIATE;
3. STARTUP MOUNT;
4.
Determine the time, SCN, or log sequence that should end recovery. For example, if you discover that a user accidentally dropped a tablespace at 9:02 a.m., then you can recover to 9 a.m.--just before the drop occurred. You will lose all changes to the database made after that time.
You can also examine the alert.log to find the SCN of an event and recover to a prior SCN. Alternatively, you can determine the log sequence number that contains the recovery termination SCN, and then recover through that log. For example, query V$LOG_HISTORY to view the logs that you have archived.
RECID      STAMP      THREAD#    SEQUENCE# FIRST_CHAN FIRST_TIM NEXT_CHANG
         1 344890611          1          1      20037 24-SEP-02      20043
         2 344890615          1          2      20043 24-SEP-02      20045
         3 344890618          1          3      20045 24-SEP-02      20046
Perform the following operations within a RUN command:
Set the end recovery time, SCN, or log sequence. If specifying a time, then use the date format specified in the NLS_LANG and NLS_DATE_FORMAT environment variables.
If automatic channels are not configured, then manually allocate one or more channels.
Restore and recover the database.
The following example performs an incomplete recovery until November 15 at 9 a.m.
RUN
SET UNTIL TIME 'Nov 15 2002 09:00:00';
# SET UNTIL SCN 1000;       # alternatively, specify SCN
# SET UNTIL SEQUENCE 9923; # alternatively, specify log sequence number
RESTORE DATABASE;
RECOVER DATABASE;
If recovery was successful, then open the database and reset the online logs:
5. ALTER DATABASE OPEN RESETLOGS;
I did not quiet understand why the above scenario is using current controlfile as the checkpoint scn in the current controlfile and the checkpoint scn in the datafile headers do not match after the restore and recovery. Thanks in Advance for your help.
Thanks
satya

Thanks for the reply ... but what about the checkpoint scn in the controlfile . my understanding is that unless the checkpoint scn in the controlfile and datafiles do not match the database will not open. so assuming the checkpoint scn in my current controlfile is 1500 and i want to recover my database till scn 1200. so the scn in the datafiles (which is 1200) is not not matching with the scn in the controlfile(1500). so will the database open in such cases.
Thanks
Satya

Schedule a crontab in rman catalog

Hi,
I am trying to schedule a crontab in rman catalog side but it wasn't work.
I prepared a scripts and I dont know why it was not worked.
Please can anyone tell me how can I schedule my crontab in rman.
The scripts is this,
00 01 * * 0 ksh /u01/app/oracle/product/10.2.0/bin/ora_rman.sh >/dev/null 2>&1
vi ora_rman.sh
ORACLE_SID=p001
ORACLE_BASE=/orahome/p001
ORACLE_HOME=$ORACLE_BASE/10.0.2
PATH=$ORACLE_HOME/bin:$PATH
$ORACLE_HOME/bin/rman catalog rman/rman target sys/sys$pwd@p001 /u01/app/oracle/product/10.2.0/bin/ora_rman.sh <<EOF
run {
backup incremental level 0 as compressed backupset database plus archivelog;
delete noprompt archivelog all completed before 'sysdate-7';
00 19 * * * ksh /u01/app/oracle/product/10.2.0/bin/ora01_rman.sh >/dev/null 2>&1
vi ora01_rman.sh
ORACLE_SID=p001
ORACLE_BASE=/orahome/p001
ORACLE_HOME=$ORACLE_BASE/10.0.2
PATH=$ORACLE_HOME/bin:$PATH
$ORACLE_HOME/bin/rman catalog rman/rman target sys/sys$pwd@p001 u01/app/oracle/product/10.2.0/bin/ora01_rman.sh <<EOF
run {
backup incremental level 1 as compressed backupset database plus archivelog;
delete noprompt archivelog all completed before 'sysdate-7';
waiting for your replies,
Thanks & Regards

Here's my working stuff:
I use an .env file. Here's the crontab entry, script and env file.
00 16 * * 0-6 /u01/app/oracle/dba_tool/PRIMARY/db_rman_full.sh > /tmp/PRIMARY_rmanfull.out
#!/bin/bash
# Name: db_rman_full.sh
# Purpose: Database rman backup
# Usage : db_rman_full <DBNAME>
. /u01/app/oracle/dba_tool/env/PRIMARY.env
echo "Starting RMAN..."
$ORACLE_HOME/bin/rman target / catalog <catalog_user>/@<catalog_db> << EOF
run { allocate channel d1 type disk;
backup full as compressed backupset
database plus archivelog;}
crosscheck backup;
delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-5';
DELETE noprompt BACKUP COMPLETED BEFORE 'SYSDATE-2' DEVICE TYPE DISK;
exit
EOF
echo `date`
echo
echo 'RMAN Full on PRIMARY Complete'
env
ORACLE_BASE=/u01/app/oracle
ULIMIT=unlimited
ORACLE_SID=PRIMARY
ORACLE_HOME=$ORACLE_BASE/product/11.2.0
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
LIBPATH=$LD_LIBRARY_PATH:/usr/lib
TNS_ADMIN=$ORACLE_HOME/network/admin
PATH=$ORACLE_HOME/bin:$ORACLE_BASE/dba_tool/bin:/bin:/usr/bin:/usr/ccs/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin:/usr/lbin:/GNU/bin/make:/u01/app/oracle/dba_tool/bin:/home/oracle/utils/SCRIPTS:/usr/local/bin:.
export TERM=vt100
export ORACLE_BASE ORACLE_SID ORACLE_TERM ULIMIT
export ORACLE_HOME
export LIBPATH LD_LIBRARY_PATH ORA_NLS33
export TNS_ADMIN
export PATH
----If you find this helpful please mark it so----

ArchiveLog deletion using RMAN

Hi,
My backup failed for some time due to disk space issue which I was able to fix using setting db_recovery_file_dest_size but after the completion of backup script it didn't delete all the archivelog files. I still have log files from 05 Jan 2011 - 20 Feb 2011, but log files from 21 Feb 2011 - 18 Apr 2011 were deleted, When I run "crosscheck archivelog all;" it didn't show me archivelogs between 05 Jan 2011 - 20 Feb 2011 in the results but physically they are present in the archive folder.
1 How to delete these archive files to free up disk space?
2 Can I restore my database from last backup which was successful?
3 Why the RMAN was unable to delete my archivelog files?
My retention policy is set to Redundancy 1.
Thanks,
Prashanth

The older archivelogs are no longer in the control file if they are not being reported by CROSSCHECK.
Normally, when the FRA is close to 100% usage, Oracle can automatically purge known obsolete files. However, if you resized the FRA before the files were auto-purged and, subsequently, they became older than the keep time, Oracle became "unaware" of them.
You could re-CATALOG them with a CATALOG command and then DELETE them, with a DELETE command.
Hemant K Chitale

Controlfile vs. RMAN Catalog

Hey, my controlfile is increasing really fast. So I have to recreate the the controlfile on a regular basis. Its growing nearly 150 MB in one month.
Therefore the backups are getting slow, also a logswitch is impacting my database performance. I am using a physical standby so the db parameter archive_lag_target is set to 600 (sec), so every 10 minutes a logswitch occurs.
v$controlfile_record_section is showing archivelogs are the most space consuming part.
Now the question:
Is it an appriopate way to switch from controlfile to rman catalog ? Will this help me to keep the controlfile tiny ?
Chris

Hi Christian,
Why is the size of the controlfile a problem for you?
There are other points to keep in mind if you use controlfile or rman catalog.
For example if you would like to use standby databases so Oracle recommend to use an rman catalog.
For me it is not a problem of the size it is your decision to make a matrix and look about the pros and cons
between controlfile and rman catalog.
But if it is a production environment it is a good idea to use a rman catalog.
regards
SPA2

Rman catalog files

We have 11g rac one node implemented on windows 2008, i took complete backup using rman from the production database and I copied the files to the test server and when am doing
restore database validate it is still pointing to production backup location :
c:\rman\ (test location)
e:rman (production location)
Am getting the error :
channel ORA_DISK_1: reading from backup piece E:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
channel ORA_DISK_2: reading from backup piece E:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
Wondering why am getting the above error as I didn't catalog any backup piece on that location and the location is taken from production.
test worklog
RMAN> restore controlfile from 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
Starting restore at 26-JAN-12
using channel ORA_DISK_1
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output file name=C:\APP\ADMINISTRATOR\ORADATA\medt\CONTROL\CONTROL01.CTL
output file name=C:\APP\ADMINISTRATOR\ORADATA\medt\CONTROL\CONTROL02.CTL
Finished restore at 26-JAN-12
RMAN> catalog backuppiece 'C:\rman\DATA_73_1_29N1OG00_1_1.BAK';
released channel: ORA_DISK_1
cataloged backup piece
backup piece handle=C:\RMAN\DATA_73_1_29N1OG00_1_1.BAK RECID=34 STAMP=773622357
RMAN> catalog backuppiece 'C:\rman\'DATA_74_1_2AN1OG00_1_1.BAK';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "comma, ;"
RMAN-01008: the bad identifier was: DATA_74_1_2AN1OG00_1_1
RMAN-01007: at line 1 column 31 file: standard input
RMAN> catalog backuppiece 'C:\rman\DATA_74_1_2AN1OG00_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_74_1_2AN1OG00_1_1.BAK RECID=35 STAMP=773622388
RMAN> catalog backuppiece 'C:\rman\DATA_75_1_2BN1OG00_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_75_1_2BN1OG00_1_1.BAK RECID=36 STAMP=773622401
RMAN> catalog backuppiece 'C:\rman\DATA_76_1_2CN1OG01_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK RECID=37 STAMP=773622413
RMAN> catalog backuppiece 'C:\rman\DATA_77_1_2DN1OG02_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK RECID=38 STAMP=773622427
RMAN> catalog backuppiece 'C:\rman\DATA_78_1_2EN1OG02_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK RECID=39 STAMP=773622439
RMAN> catalog backuppiece 'C:\rman\DATA_79_1_2FN1OG02_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK RECID=40 STAMP=773622501
RMAN> catalog backuppiece 'C:\rman\DATA_80_1_2GN1OG02_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK RECID=41 STAMP=773622513
RMAN> catalog backuppiece 'C:\rman\DATA_81_1_2HN1OG03_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK RECID=42 STAMP=773622525
RMAN> catalog backuppiece 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_82_1_2IN1OG3N_1_1.BAK RECID=43 STAMP=773622546
RMAN> catalog backuppiece 'C:\rman\DATA_83_1_2JN1OG3N_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_83_1_2JN1OG3N_1_1.BAK RECID=44 STAMP=773622560
RMAN> catalog backuppiece 'C:\rman\DATA_84_1_2KN1OG75_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_84_1_2KN1OG75_1_1.BAK RECID=45 STAMP=773622574
RMAN> restore database validate;
Starting restore at 26-JAN-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=350 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=407 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=466 device type=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: SID=524 device type=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: SID=582 device type=DISK
allocated channel: ORA_DISK_6
channel ORA_DISK_6: SID=640 device type=DISK
channel ORA_DISK_1: starting validation of datafile backup set
channel ORA_DISK_2: starting validation of datafile backup set
channel ORA_DISK_3: starting validation of datafile backup set
channel ORA_DISK_4: starting validation of datafile backup set
channel ORA_DISK_5: starting validation of datafile backup set
channel ORA_DISK_6: starting validation of datafile backup set
channel ORA_DISK_1: reading from backup piece E:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
channel ORA_DISK_2: reading from backup piece E:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
channel ORA_DISK_3: reading from backup piece C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK
channel ORA_DISK_4: reading from backup piece C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK
channel ORA_DISK_5: reading from backup piece C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK
channel ORA_DISK_6: reading from backup piece C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK
channel ORA_DISK_1: errors found reading piece handle=E:\RMAN\DATA_80_1_2GN1OG02
_1_1.BAK
channel ORA_DISK_1: failover to piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
tag=TAG20120126T174849
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: validation complete, elapsed time: 00:00:46
channel ORA_DISK_2: errors found reading piece handle=E:\RMAN\DATA_81_1_2HN1OG03
_1_1.BAK
channel ORA_DISK_2: failover to piece handle=C:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
tag=TAG20120126T174849
channel ORA_DISK_2: restored backup piece 1
channel ORA_DISK_2: validation complete, elapsed time: 00:00:56
channel ORA_DISK_6: piece handle=C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK tag=TAG20120
126T174849
channel ORA_DISK_6: restored backup piece 1
channel ORA_DISK_6: validation complete, elapsed time: 00:01:26
channel ORA_DISK_3: piece handle=C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK tag=TAG20120
126T174849
channel ORA_DISK_3: restored backup piece 1
channel ORA_DISK_3: validation complete, elapsed time: 00:01:36
channel ORA_DISK_5: piece handle=C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK tag=TAG20120
126T174849
channel ORA_DISK_5: restored backup piece 1
channel ORA_DISK_5: validation complete, elapsed time: 00:01:36
channel ORA_DISK_4: piece handle=C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK tag=TAG20120
126T174849
channel ORA_DISK_4: restored backup piece 1
channel ORA_DISK_4: validation complete, elapsed time: 00:02:07
Finished restore at 26-JAN-12Kai

Those "prod" locations are found in the backup controlfile:
>
RMAN> restore controlfile from 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
>
>
channel ORA_DISK_1: errors found reading piece handle=E:\RMAN\DATA_80_1_2GN1OG02
_1_1.BAK
channel ORA_DISK_1: failover to piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
tag=TAG20120126T174849
>
You can see how RMAN noticed it couldn't find that piece and then found one that you had previously cataloged. Looks good to me.

Weird RMAN catalog issue

I am on 10.2.0.4, RMAN + RMAN catalog + Data Gurad and I am desporate :)
My db crashed with the following:
ORA-27063: number of bytes read/written is incorrect
SVR4 Error: 49: Disc quota exceeded
A look in the FRA showed that it was 100% full. Archived logs take all of the space. I delete archived logs via OS method and then do delete expired archvied log all. If I am connected to recovery catalog while doing this, Oracle DOES NOT delete archieved logs from FRA (I don't see them on diks, but FRA stays full). If I connect to target only and do not connect to the catalog and do the same thing, FRA gets emptied out. WHY???? Thank you for any input!!!
p.s. Here is my delete archvied log script:
#!/bin/ksh -x
# Script to delete archive logs older then 4 days
find /data/archive/PROD/archivelog -mtime +4 -exec rm -r {} \;
. /data/app/oracle/.profile
export ORACLE_SID=PROD
export DATESTAMP="`date +"%y:%m:%d"`"
rman <<EOF
SPOOL MSGLOG TO '/data/app/home/dba/backup_files/archive_logs/PROD_clear_a
rch${DATESTAMP}.log'
@/data/app/home/dba/scripts/connect_nocat.rman
run {
allocate channel d1 device type disk;
crosscheck archivelog all;
delete noprompt expired archivelog all;
release channel d1;
EXIT;
EOF

hi,
you wrote: +"...Oracle DOES NOT delete archieved logs from FRA..."+
If you try to delete needed files (depends on your retention policy:
show RETENTION POLICY;
report need backup;
restore archivelog all preview summary;
) you may have to use "force" option in the statement. Even if they don't exist on disk, RMAN will throw errors.
What is the output of:
crosscheck archivelog all;
delete noprompt expired archivelog all;
P.S. it's better not to delete oracle files in OS if RMAN handles B&R policy ;-)

SQL Reports Bad Idea Against RMAN Catalog?

11.2.0.1 SPARC 64
We use OEM to manage/execute our backups. The MML is NetBackup. One downside to this is that the "job" within OEM executes the backup for 20+ databases. In a serial fashion the backups occur in NetBackup...but most are queued - they throttle through and over time they complete. To this end, we have no way of seeing the true backup duration. We know the rman start and completion times, but they're not "actual."
I started looking at creating a sql statement/report/[pl/sql] block that would give us the granular informatin on the true timings of the backup "pieces" as they relate to a "set."
Research out on the wire shows a number of high level solutions, but nothing to which a report shows the data files, etc. Usually when I see this I start to question..."hey, is this even a good approach?"
I do realize that through the RMAN utility there are a number of reports which are available...this post, however, is focused on the idea of sql reports against the rman catalog.
Any advice would be welcome.
Conceptual report:
-> INCREMENTAL LEVEL 0
--> BACKUP SET
---> BACKUP PIECE
----> HANDLE, TAG, DATAFILE, START, COMPLETION
I'm NOT looking for the sql...I can work that out, I just want to know if this is a smart approach or best to stay out of the catalog.
-abe
Boulder, Colorado
Edited by: user10863631 on Mar 10, 2011 7:43 AM
Edited by: user10863631 on Mar 10, 2011 7:56 AM

I think this is the wrong forum for such a question. The Database - General (General Database Discussions might be better suited. Or maybe the RMAN forum (Recovery Manager (RMAN)

Why use RMAN CATALOG ?

Similar Messages

Maybe you are looking for