OSB / RMAN configuration for recovery area backup

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

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

Similar Messages

Step by Step RMAN configuration for full hot backup daily

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

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

RMAN CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET;

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

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

T500 - HDD for Ultrabay - can it be used for Recovery Media & Backups & Page File & data?

I'm learning to check first before buying things.
I am considering getting a generic ultrabay SATA adapter
http://cgi.ebay.com/SATA-adapter-IBM-THINKPAD-43N3412-R400-W500-X200S-R500-/130441260492
and a WD 7,200 HDD
http://www.newegg.com/Product/Product.aspx?Item=N82E16822136278
Can the ultrabay HDD be used for Recovery Media, and also Backups, page file, and other data?
And can the Backups on this HDD be deleted, so only the last backup is present?
Also, is it possible to use a HDD in the ultrabay slot, without an adpater? My T500 is a desktop replacement currently, so the HDD wouldn't need to be protected from movement or bumps.
Thanks for any ideas

For all of you who know less than I do, a HDD in the ultrabay slot can be used as a Recovery boot, and for the R&R backups.
These must both be put on the primary partition of the HDD.
I believe, but can't test or confirm, that another partition (logical partition) could be added to the drive and used for page filing and data.

Modifications to PFILE for recovery on backup system

This is a continuation from another thread, but I'm taking things one step at a time.
I'm starting with a complete RMAN backup and trying to bring the database up on a different machine. Both run Oracle 10gr2 Standard. One is a single-node RAC on Windows 2003, other is standalone on Windows 2008. I'm trying to follow the RMAN recovery steps and now it tells me to edit my PFILE. I have changed all the locations as per the directions, but it is giving me errors with the RAC stuff. Can someone point me at which lines to comment/change/remove? I've tagged the ones I think I need to change but would appreciate some guidance...
ts1.__db_cache_size=343932928   <--
ts1.__java_pool_size=209715200   <--
ts1.__large_pool_size=8388608   <--
ts1.__shared_pool_size=209715200   <--
ts1.__streams_pool_size=8388608   <--
*._optimizer_connect_by_cost_based=false
*.audit_file_dest='D:\Oracle\product\10.2.0\admin\TSBAK\ADUMP'
*.background_dump_dest='D:\Oracle\product\10.2.0\admin\TSBAK\BDUMP'
*.cluster_database=TRUE   <--
*.cluster_database_instances=1
*.compatible='10.2.0.1.0'
*.control_files='+DATA/tsbak/controlfile/current.260.591973329'
*.core_dump_dest='D:\Oracle\product\10.2.0\admin\TSBAK\CDUMP'
*.db_block_size=8192
*.db_create_file_dest='+DATA'
*.db_file_multiblock_read_count=16
*.db_files=1024# INITIAL
*.db_name='TS'   <--
*.global_names=FALSE
clustdb1.instance_name='TS1'   <--
*.instance_number=1
clustdb1.instance_number=1   <--
*.java_pool_size=209715200
*.job_queue_processes=10
*.large_pool_size=8388608
clustdb1.local_listener='LISTENER_TSBAK'   <--
*.local_listener='TSBAK'
*.log_archive_dest_1='LOCATION=+DATA/TSBAK/'
*.log_archive_format='ARC%S_%R.%T'
*.log_buffer=8192# INITIAL
*.log_checkpoint_interval=10000
*.max_dump_file_size='10240'# limit trace file size to 10 K each
*.nls_timestamp_format='YYYY-MM-DD HH24:MI.SS.FF'
*.open_cursors=300
*.open_links=4
*.parallel_max_servers=5
*.pga_aggregate_target=203423744
*.processes=250# INITIAL
*.remote_listener='LISTENERS_TSBAK'
*.remote_login_passwordfile='EXCLUSIVE'
clustdb1.remote_login_passwordfile='exclusive'   <--
*.sga_max_size=1317011456
*.sga_target=788529152
*.shared_pool_size=209715200
*.smtp_out_server='mail.mt.net:25'
*.thread=1
clustdb1.thread=1   <--
*.undo_management='AUTO'# For automatic undo management
*.undo_tablespace='UNDOTBS1'
clustdb1.undo_tablespace='UNDOTBS1'   <--
*.user_dump_dest='D:\Oracle\product\10.2.0\admin\TSBAK\UDUMP'

OKay. I was finally able to get things mounted. Here is the modified initialization file:
*.__db_cache_size=343932928
*.__java_pool_size=209715200
*.__large_pool_size=8388608
*.__shared_pool_size=209715200
*.__streams_pool_size=8388608
*._optimizer_connect_by_cost_based=false
*.audit_file_dest='D:\Oracle\product\10.2.0\admin\TSBAK\ADUMP'
*.background_dump_dest='D:\Oracle\product\10.2.0\admin\TSBAK\BDUMP'
*.cluster_database=FALSE
*.cluster_database_instances=1
*.compatible='10.2.0.1.0'
*.control_files='+DATA/tsbak/controlfile/current.260.591973329'
*.core_dump_dest='D:\Oracle\product\10.2.0\admin\TSBAK\CDUMP'
*.db_block_size=8192
*.db_create_file_dest='+DATA'
*.db_file_multiblock_read_count=16
*.db_files=1024# INITIAL
*.db_name='TS'
*.global_names=FALSE
##clustdb1.instance_name='TS1'
*.instance_number=1
##clustdb1.instance_number=1
*.java_pool_size=209715200
*.job_queue_processes=10
*.large_pool_size=8388608
##clustdb1.local_listener='LISTENER_TSBAK'
*.local_listener='LISTENER_TSBAK'
*.log_archive_dest_1='LOCATION=D:\Oracle\product\10.2.0\TSBAK\database\archive'
*.log_archive_format='ARC%S_%R.%T'
*.log_buffer=8192# INITIAL
*.log_checkpoint_interval=10000
*.max_dump_file_size='10240'# limit trace file size to 10 K each
*.nls_timestamp_format='YYYY-MM-DD HH24:MI.SS.FF'
*.open_cursors=300
*.open_links=4
*.parallel_max_servers=5
*.pga_aggregate_target=203423744
*.processes=250# INITIAL
*.remote_listener='LISTENER_TSBAK'
*.remote_login_passwordfile='EXCLUSIVE'
##clustdb1.remote_login_passwordfile='exclusive'
*.sga_max_size=1317011456
*.sga_target=788529152
*.shared_pool_size=209715200
*.smtp_out_server='mail.mt.net:25'
*.thread=1
##clustdb1.thread=1
*.undo_management='AUTO'# For automatic undo management
*.undo_tablespace='UNDOTBS1'
##clustdb1.undo_tablespace='UNDOTBS1'
*.user_dump_dest='D:\Oracle\product\10.2.0\admin\TSBAK\UDUMP'My advice for anyone else that has to do this:
1) manually create ALL the directories where the new files are going to go.
2) copy and paste the directories into the new initialization file.
3) make sure to keep a copy of the old one just in case.
4) syntax can be a booger. Check out the LOCATION= in the log_archive_dest_1 parameter...

Question - EM and OSB keystore configuration for encryption

Hello everyone,
I've been configuring EM and OSB's security key provider by using the manuals ( [Setting keystores|http://download.oracle.com/docs/cd/E14571_01/web.1111/b32511/setup_config.htm#WSSEC1970] ) but I came up with a problem. In both configurations the tools require an encryption key, however in my case I receive soap requests with X.509 client certificates in them (and so their public, encryption key). So, potentially every request will have a different encryption key, not a single hard one like the configurations require. How should I configure this scenario??
Thanks !

short answer: Using a policy will force the wsdl to include the server's public key to be used for message encryption. So the incoming message should have a Security element in its header and is encrypted with the server's public key. Since the server has the private key, it can decrypt the message.
soapUI ( 3.5 ) gives a good view of the client side of the process.

RMAN script for RAC Hot Backup

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

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

EMERGENCY: List of files in Recovery Area not managed by the database

Hi,
this is an emergency request....
I have this data guard set up. And i accidently dropped online redo logs, standby logs and the archive log except the current online redolog.
i actually ran to cleanup the whole directory which included the controlfile and the datafiles (was on the wrong location on ASM)
but the controlfile and the datafiles did not get deleted. i can still see them on the ASM.
and now when i am trying to restore the archive logs, but i keep getting error as shown below...
WARNING: A file of type ARCHIVED LOG may exist in
db_recovery_file_dest that is not known to the database.
Use the RMAN command CATALOG RECOVERY AREA to re-catalog
any such files. This is most likely the result of a crash
during file creation.
so when i did the below i was getting error as:
RMAN> CATALOG RECOVERY AREA;
using target database control file instead of recovery catalog
searching for all files in the recovery area
no files found to be unknown to the database
List of files in Recovery Area not managed by the database
==========================================================
File Name: +DATA/afcpdg/controlfile/controlfile01.ctl
RMAN-07526: Reason: File is not an Oracle Managed File
File Name: +DATA/afcpdg/onlinelog/group_1.304.718194815
RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter
number of files not managed by recovery area is 82, totaling 168.10GB
But i do see those data files that RMAN is complaining as shown above in the ASM.
I HOPE I DID NOT MESS UP THE CONTROLFILE and the DATFILES
CAN SOMEONE HELP ME FIX THIS MISTAKE THAT I DID.
Right now the data guard is running fine, the logs are getting shipped from primary and the getting applied at the DG.
And i am able to see all the redo logs got deleted.
But not sure how the deleted redo logs got created in the ASM (i did not create them manually)
Thanks.
Philip.
Edited by: user8898644 on May 5, 2010 8:52 AM
Edited by: user8898644 on May 5, 2010 9:16 AM
Edited by: user8898644 on May 5, 2010 11:43 AM

Yes this happened on the standby database.
I had to restore the archive logs because i deleted all the archive logs which got shipped from the primary.
I did re-create the standby logs. But when i checked back the redo logs that i deleted came back again.
I have no idea how they can back again. is it a feature of ASM where a mirrored copy of the files are stored on ASM and they re-create them when accidently dropped.
Can you help me understand how the redologs got created again automatically.
Right now the data guard is running fine but i do see the error
WARNING: A file of type ARCHIVED LOG may exist in
db_recovery_file_dest that is not known to the database.
Use the RMAN command CATALOG RECOVERY AREA to re-catalog
any such files. This is most likely the result of a crash
during file creation.
and when i do the following
RMAN> catalog recovery area;
i do see errors as below...
List of files in Recovery Area not managed by the database
==========================================================
File Name: +DATA/afcpdg/controlfile/controlfile01.ctl
RMAN-07526: Reason: File is not an Oracle Managed File
File Name: +DATA/afcpdg/onlinelog/group_1.304.718194815
RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter
File Name: +DATA/afcpdg/onlinelog/group_2.372.718194833
RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter
File Name: +DATA/afcpdg/datafile/system.596.715610261
RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter
File Name: +DATA/afcpdg/datafile/undotbs1.571.715603525
number of files not managed by recovery area is 82, totaling 168.10GB
we do have the db_create_file_dest and db_recovery_file_dest pointing to the same location as +DATA
How do i fix the above error?
Thanks in advance.

Problem with recovery area

Hi everybody
I have a problem in a RAC environment
This is my environment:
Oracle RAC 10.2.0.4 with 3 nodes
RHEL 5.5
The node 3 stopped working and the alert log shows me the following:
Fri Mar 4 16:24:38 2011
ORA-19816: WARNING: Files may exist in db_recovery_file_dest that are not known to database.
ORA-27041: unable to open file
Linux Error: 13: Permission denied
Additional information: 2
Fri Mar 4 16:24:38 2011
WARNING: A file of type ARCHIVED LOG may exist in
db_recovery_file_dest that is not known to the database.
Use the RMAN command CATALOG RECOVERY AREA to re-catalog
any such files. This is most likely the result of a crash
during file creation.
I ran CATALOG RECOVERY AREA command in RMAN and the result indicates that some headers of archivelogs are corrupted.
The DB service was hung and I stoped the instance in node 3.
Now my DB is operative but i have fear that if start the instance in node 3 the service will be hung.
Any idea?
Thanks so much
pd: sorry for my english

SQL> show parameter db_recovery_file_dest
NAME                         TYPE      VALUE
db_recovery_file_dest               string      /u01/app/oracle/flash_recovery
                               _area
db_recovery_file_dest_size          big integer 4000M

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

How to use Flash recovery area only for flashback database feature

I would like to use flash recovery area only for flashback database feature, which means, flash recovery area will store only flashback logs.
I dont want to use that file system for any other files, like archive log files, database backups, control file copies, multiplex redo log, etc
is it possible? I want to use this feature only for flashback database option and hence i dont want to disturb any existing configuration in my database
including backup jobs. Is it required to store archive redo log files also in flash recovery area to use the flashback database feature?
I certainly can't afford to have a copy of entire database in this file system as size of my DB is more than the flash recovery area file system I have.
Thanks
Sarayu

user13312943 wrote:
Aman,
I think i was not clear in my question. Let me try again
My only requirement is to use flashback database feature (or be prepared to use if required). I dont want to create a large file system to use this FRA to store all these files. Out of all the files being stored here copy of data files seems to be consuming more space. I see these files are classified as transient and permanent files. I am okay with permanent files. I fear that this file system may consume more space if i store backup files on disk. I want database backups to go to tapes, not to the FRA disk. Is it possible?
Thanks for your reply
Okay, well in that case you can use RMAN and push the backups to the tape drives. FLB logs would be stored on the FRA.
Aman....

Retention policy for archivelogs in the flash recovery area

I am using the flash recovery area for all my backup files (archive logs, data and control files). I want to use the redundancy retention policy because it is easy to calculate the space requirement. However, I am not clear how the retention policy applies to archive logs.
Say I set the retention policy to be "keeping 3 backups". How does it affect the archive logs? Will archive logs in the flash recovery area be deleted automatically or I need to do it manually. If they are deleted automatically just like dataset files, what is the "retention policy" for them? I do not have a tape device so all archive logs are going to be stay in disk.
Thanks.

I am using the flash recovery area for all my backup
files (archive logs, data and control files). I want
to use the redundancy retention policy because it is
easy to calculate the space requirement. However, I
am not clear how the retention policy applies to
archive logs.
RMAN> show retention policy
2> ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> list backup
2> ;
RMAN>AS documentation says
"Besides affecting datafile and control file backups, the retention policy affects archived logs and archived log backups.
First, RMAN decides which datafile and control file backups are obsolete. Then, RMAN considers as obsolete all archived
log backups that are older than the oldest datafile or control file backup that must be retained."
Now i connect to SQL and create two big table for filling the redo log file and then get it archived.Please
consider it here that i am getting archived before any taking backup i.e backup database in order to make
archive older then the oldest datafile.
SQL> show parameter control_file_record_keep_time
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
SQL> create table a1 as select * from all_objects
2 /
Table created.
SQL> create table a2 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
03/17/2008 03:44 PM    <DIR>          .
03/17/2008 03:44 PM    <DIR>          ..
03/17/2008 03:44 PM         9,750,528 O1_MF_1_15_3XWLVK6T_.ARC
               1 File(s)      9,750,528 bytes
               2 Dir(s) 62,714,875,904 bytes free
Now i take backup
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups found
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Archive Log          402    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARCYou can see the obsolete archived files which is the older then the oldest file which has been obsolete.It also
does'nt make sense to keep the archived log files which is older then the oldest file cause it will no longer
be useful for recovery process.
now back to pavillion
RMAN> delete obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Archive Log          402    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC
Do you really want to delete the above objects (enter YES or NO)? yes
deleted archive log
archive log filename=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\ARCHIVELO
G\2008_03_17\O1_MF_1_15_3XWLVK6T_.ARC recid=402 stamp=649611842
Deleted 1 objects
RMAN> delete backup
2> ;
using channel ORA_DISK_1
RMAN> list backup
2> ;
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 03:59 PM    <DIR>          .
03/17/2008 03:59 PM    <DIR>          ..
               0 File(s)              0 bytes
               2 Dir(s) 62,724,440,064 bytes freenow this time what i did i created the archived log files after first backup in order to not to make it older
then the oldest datafile backup.
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundnow i come to at SQL and make redo log file filled by creating 2 big tables in order to get it archived
SQL> create table a3 as select * from all_objects
2 /
Table created.
SQL> create table a4 as select * from all_objects
2 /
Table created.
C:\>dir C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_03_17
Volume in drive C is khurram
Volume Serial Number is F49D-FF2B
Directory of C:\oracle\product\10.1.0\flash_recovery_area\ORCL\ARCHIVELOG\2008_
03_17
03/17/2008 04:09 PM    <DIR>          .
03/17/2008 04:09 PM    <DIR>          ..
03/17/2008 04:09 PM         9,751,552 O1_MF_1_16_3XWNCGRS_.ARC
               1 File(s)      9,751,552 bytes
               2 Dir(s) 62,563,205,120 bytes free
RMAN> backup database
2> ;
Starting backup at 17-MAR-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
no obsolete backups foundYou can see no archived logs get obsolete yet cause the archivelog O1_MF_1_16_3XWNCGRS_.ARC
is not older then oldest datafile backup.
But this archivelog file will get obsolete if its beyond the retention policy,lest see how ,just take one more
backup ,as i have already taken two time backup and the moment i go to take third backup it will cross ours
retetnion policy from the period of 2.
RMAN> backup database
2> ;
RMAN> report obsolete
2> ;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 2
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
Backup Set           240    17-MAR-08
Backup Piece       231    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NNNDF_TAG20080317T160604_3XWN4WTB_.B
KP
Backup Set           241    17-MAR-08
Backup Piece       232    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\BACKUPSET\2008_03_17\O1_MF_NCSNF_TAG20080317T160604_3XWN6Z95_.B
KP
Archive Log          403    17-MAR-08          C:\ORACLE\PRODUCT\10.1.0\FLASH_RE
COVERY_AREA\ORCL\ARCHIVELOG\2008_03_17\O1_MF_1_16_3XWNCGRS_.ARCKhurram

Disk array configurations with oracle redo logs and flash recovery area.

Dear Oracle users,
We are planning to buy the new server for oracle database 10g standard edition. We put oracle database file, redo logs, and flash recovery area on each of disk array. My question is what is the best disk array configuration for redo logs and flash recovery area? RAID 10 or RAID 1? Is that possible we can duplicate Flash recovery area to the other location (such as net work drive) at the same time? Since we only have single disk array controller to connect to the disk arrays, I am try to avoid the single failure that will lose archive logs and daily backup.
thanks,
Belinda

Thank you so much for the suggestion. Could you please let me know the answer for my question of FRA redundancy?
“Is that possible we can duplicate Flash recovery area to the other location (such as net work drive) at the same time? Since we only have single disk array controller to connect to the disk arrays, I am try to avoid the single failure that will lose archive logs and daily backup.”

Recommendations for recovery catalog database backup

Hi
We are using IBM Tivoli Storage Manager for our 9i db on AIX 5.2.
I would like us to consider using rman but I am not sure of the best way we would go about backing up the database we would use for our recovery catalog.
This database that hold all the metadata would need to be backed up after every rman backup. The rman backup would go to tape, so I am assuming that the recovery catalog would be backed up on tape also.
What are the common procedures for this in other shops ?

Dan A wrote:
Aman. That doc does help, and indeed it does explain
Back up the recovery catalog with the same frequency that you back up the target database.
We would be doing nightly backups, so we would have to back up the catalog with the same frequency.
The doc explains that we would use rman for these backups also, but that it would be in NOCATALOG mode so that the repository is in the control file.
And then what? Just copy this to tape? Seems that with rman there is then a need to do two backups - one of the target db and one of the recovery catalog.
Thanks.I shall suggest to take an export of the underlying schema which is holding the info in the recovery catalog. That's all which is basically required to be safe. In case , everything gets burnt regarding the catalog db,you can immediately create another db, import the user back there and things are in place. This should be a quick and easy way out of the backup of recovery catalog.
Yes if you are going to take backups every night than backup of recovery catalog schema/db nightly will be a good option. Docs are meant to promote people for RMAN so indeed they would talk about it. But its not at all a compulstion to use RMAN for recovery catalog schema's backup. If its a big catalog maintaining lots of database's info than using RMAN with all its features is a good option. If a single db is a part of it than it may not be that much big and export of teh schema alone may serve the purpose too.
HTH
Aman....

Adding new hard drive for Flash recovery area

i am adding new hard drive for flash recovery area. How i can make single directory on that flash recovery area & how i can test that i am accessing that rightly , to that directory & flash back recovery area disk?

Are you on Windows or Unix? And are you using ASM?
I'll assume you are on Windows....So after allocating the drive, you will format it say as F drive. Then you can create a directory T:\Flash. The parameter determining the location of the flash recovery area is db_recovery_file_dest. But you also need to set the size of the flash recovery area as well. After that's done. You can do your backups to Flash and see if the directory is populated.

OSB / RMAN configuration for recovery area backup

Similar Messages

Maybe you are looking for