Rman optimization conflicting with obsolete backups?

Hello,
Suppose I have the following configuration.
I have a partitioned table with each (month-)partition on a different tablespace. I need to keep 10yrs of data. Switch a tablespace with e.g. April2008 data to read-only.
Rman set REDUNDANCY 1 and OPTIMIZATION ON.
Now redundancy 1 should keep only 1 backup of each file wouldn't it?
I do a backup database: it backups every file.
I do a backup database again: it backups every file again.
I do a backup database third time: it says "skipping file n allready backed up 2 times".
Now I do a report obsolete: it marks one of the backups op my file with April2008 data as obsolete.
After performing a delete obsolete, it is gone.
Next day I do a backup database: it backups every file again, so I have two!! backups of file n.
I would like to have only 1 and just 1 backup of the file, and it should never be backed up anymore. The redundancy cannot be set to zero.
How to deal with this?

I think we disagree on this. I can make a single-partition rman backup if:
It is on it's own tablespace, on it's own datafile. No problem with that. It is only the redundancy-problem I have.
Even if I configure redundancy to 1, it makes two backups, and one of these is obsolete. This obsolete gets deleted in a 'delete obsolete' action, and a new obsolete will be created with the next backup.
How would you backup the database with 120 partitions as I described above? Each day a full backup??

Similar Messages

RMAN fails to delete obsolete backup in OSB

Hi All,
I am trying to delete my obsolete backups through RMAN and I get this error:
ORA-19511: Error received from media manager layer, error text:
sbt__rpc_cat_delete: delete failed for piece 0hmlsu6q_1_2 (Oracle Secure Backup error: user does not have sufficient rights)
I am not clear why Oracle Secure backup throws error that the user does not have sufficient rights./.
Below are the commands that I am using in the script:
3> ALLOCATE CHANNEL TAPE01 DEVICE TYPE SBT_TAPE;
4> CROSSCHECK BACKUP;
5> CROSSCHECK ARCHIVELOG ALL;
6> CROSSCHECK COPY;
7> report obsolete recovery window of 60 days device type
8> report obsolete recovery window of 7 days device type disk
9> delete noprompt obsolete recovery window of 60 days device type SBT_TAPE;
10> delete noprompt obsolete recovery window of 7 days device type DISK;
Any help is appreciated..
Thanks..

In my case, the problem was on OSB user permition.
On user you have to preauth. admin users to the host where database is located.
regards..
Virgilio

VSS snapshots for DPM 2010 Hyper-V backup conflict with SQL backup on a virtual SQL server

We currently use DPM 2010 to backup our virtual servers which reside on a 5 node Hyper-V clustered share volume. DPM uses the hardware VSS writer to backup the Hyper-V guests. Several of these Hyper-V guests are SQL servers (SQL 2008) and they
are all configured to run point in time SQL backups using SQL Management Plans.
The SQL backups are scheduled to run a full database backup on a Friday and differential backups on the other days of the week. Transaction backups are scheduled to run several times throughout the day.
However we have recently discovered that there is a conflict between these two methods as it seems as though when a restore is required using a differential SQL backup, it fails as the snapshot created by DPM forces SQL to believe it has had a full backup
carried out externally from the Management Plan and is therefore unable to perform the restore.
DPM backs up the Hyper-V guests on a daily basis from 8pm.
Can anyone provide any advice or guidance on this as we need both types of backup to run successfully. We are required to backup SQL with point in time backups and we also need to protect the Hyper-V guests in their entirety.

Thanks Mike,
I have tried this but unfortunately it has no effect. The VM has Oracle installed (although not the Oracle VSS Writer). It is the Oracle application server, not the database server, and the customer has a script that is used to stop and start
the Oracle application when required. Through troubleshooting this with them I have noticed that after the WLS_Reports service/process is stopped the backups run successfully but when it is running the backups fail.
I have also noticed that when I stop the Hyper-V Volume Shadow Copy Requestor the backup runs successfully, which I guess is as expected.
When the backups fail I get 2 errors in the application log:
Event Id 12293, VSS - Error calling a routine on a shadow copy provider {GUID for the Hyper-V IC Software Shadow Copy Provider}. Routine details PreFinalCommitSnapshots ({GUID}, 5) [hr = 0x800705b4, This operation returned because
the timeout period expired.]
Event Id 19, vmicvss - Not all the shadow volumes arrived in the guest operating system.
This is also part of the same problem I have posted here: Backup
fails for a Hyper-V guest with VSS Writer failures using DPM 2012 R2 - Hyper-V guest has Oracle application installed
Regards
Chris

Port 9000 conflicts with McAfee Backup utility

I am having a problem with my McAfee Backup utility. I receive a .NET conflict for port 9000 when it attempts to load. I was told by McAfee Tech Support that the Oracle Forms port utilizes port 9000. If this is true, how do I get around this problem. I was unsure whether to post this message on this forum or the forms forum. Please post where appropriate. Thank you

I am having a problem with my McAfee Backup utility. I receive a .NET conflict for port 9000 when it attempts to load. I was told by McAfee Tech Support that the Oracle Forms port utilizes port 9000. If this is true, how do I get around this problem. I was unsure whether to post this message on this forum or the forms forum. Please post where appropriate. Thank you

Is it possible to restore DB from Obsolete backup?

Hi,
Is it possible to restore DB from Obsolete backup? If yes. How?
Thanks
Rajesh

Catalog your backup again to restore it. Please read the below paragraph.
Cataloging Older Files in the Recovery Catalog
If you have datafile copies, backup pieces or archive logs on disk, you can catalog them in the recovery catalog using the CATALOG command. When using a recovery catalog, cataloging older backups that have aged out of the control file lets RMAN use the older backups during restore operations. For example:
RMAN> CATALOG DATAFILECOPY '/disk1/old_datafiles/01_01_2003/users01.dbf';
RMAN> CATALOG ARCHIVELOG '/disk1/arch_logs/archive1_731.dbf',
'/disk1/arch_logs/archive1_732.dbf';
RMAN> CATALOG BACKUPPIECE '/disk1/backups/backup_820.bkp';
You can also catalog multiple backup files in a directory at once, using the CATALOG START WITH command, as shown in this example:
RMAN> CATALOG START WITH '/disk1/backups/';
RMAN lists the files to be added to the RMAN repository and prompts for confirmation before adding the backups.
Be careful when creating your prefix for CATALOG START WITH. RMAN scans all paths for all files on disk which begin with your specified prefix. The wrong prefix may include more files than you intend. For example, a group of directories /disk1/backups , /disk1/backups-year2003, /disk1/backupsets, and /disk1/backupsets/test and so on, all contain backup files. The command
RMAN> CATALOG START WITH '/disk1/backups';
catalogs all files in all of these directories, because /disk1/backups is a prefix for the paths for all of these directories. In order to catalog only backups in the /disk1/backups directory, the correct command would be:
RMAN> CATALOG START WITH '/disk1/backups/';
Regards
Asif Kabir

RMAN Recovery Window 7 days setting - shows no obsolete backups

Hi All. Quick question about RMAN retention policy....
I have the current backup strategy:
Full backup (0) -> Sunday
Incremental backup (1) -> Monday - Saturday
Archive log backups -> every hour
This is a new database I just started taking backups on last month. (1st full backup was run October 4th)
I currently have not deleted any of them.
The old RMAN RETENTION POLICY was set to REDUNDANCY = 1
REPORT OBSOLETE lists all of them up to the last full which ran this past Sunday (Nov 1st)
I just switched the RMAN RETENTION POLICY to RECOVERY WINDOW of 7 DAYS
REPORT OBSOLETE lists no backups obsolete...
Shouldn't I see all the backups prior to a week ago or does it only take affect for backups run under the new policy?
Any help/replies are apprecitaed.
Thanks

Ran crosscheck with no problems:
Crosschecked 200 objects
But still same results for:
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
no obsolete backups found
Am I missing something here? Or like I mentioned is this expected behaviour because all of my other backups were run with REDUNDANCY = 1 retention policy?
Thanks

RMAN-05001 auxiliary .... conflicts with a file used by the target database

I can´t recreate my physical standby.
It worked in the past.
Now I reinstalled the 3 standbyclients.
Copied the spfile from the primary - modified the entries and did a rman backup.
But when issuing the duplicate database command - it comes up with the error above
SPFILE standyby db:
*.db_file_name_convert='+DATA/prim/','+DATA/stdy/','+RECOVERY/prim','+RECOVERY/stdy'
*.log_file_name_convert='+DATA/prim/','+DATA/stdy/','+RECOVERY/prim','+RECOVERY/stdy'
Starting restore at 15-APR-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle/stage/33lb65n2_1_1
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/oracle/stage/33lb65n2_1_1 tag=TAG20100415T102434
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:11
output filename=+REDO1/stdy/controlfile/current.262.716293055
output filename=+REDO2/stdy/controlfile/backup.262.716293055
Finished restore at 15-APR-10
sql statement: alter database mount standby database
released channel: ORA_AUX_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/15/2010 10:31:46
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename DATA/prim/datafile/system.262.715097535 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/sysaux.263.715097499 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs3.269.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs2.270.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/example.272.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/users.268.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/sysaux.273.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs1.271.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/system.264.710521021 conflicts with a file used by the target database+

Hi ,
I feel you are using ASM but still check the below details:
Cause
Production and Auxiliary have same directory structure and are running on two different machines. RMAN must be told not check that the target datafiles are sharing the same names as the duplicated files being created. Otherwise, the following errors will be returned:
RMAN-05001: auxiliary filename /qmaxnt/u04/qmaxntorafiles/table/QMAXAD08_03.dbf
conflicts with a file used by the target database
RMAN-05001: auxiliary filename /qmaxnt/u04/qmaxntorafiles/table/QMAXAD08_02.dbf
Solution
To implement the solution, please use nofilenamecheck in syntax as follows:
1. Connect to Target, auxiliary, and rman catalog and
2. use script as
run{
set until time "to_date('2005/09/17 14:00:00','yyyy/mm/dd HH24:MI:SS')";
allocate auxiliary channel aux1 type 'sbt_tape';
allocate auxiliary channel aux2 type 'sbt_tape';
duplicate target database for standby dorecover nofilenamecheck;
Make sure to use auxiliary type of channel so RMAN restore take place at auxiliary database.
Thanks,
Rafi.
http://rafioracledba.blogspot.com/

RMAN not obsoleting backup

Hi,
In my 10gR2 database, level1 backup is taken every nigh except sunday, retention policy is set to redundancy 1.
but rman not considering previous backup as obsolete.
below is level1 backup script.
{color:#0000ff}cp $ORACLE_HOME/dbs/orapworampls /backup/RMANBACKUP/orapworampls_backup
# start the rman backup
# only use the next line if this script needs run via root CRON
#su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/rman 'target /'"<< EOF
$ORACLE_HOME/bin/rman 'target /' catalog rman/rman@rman<< EOF
configure retention policy to redundancy 1;
resync catalog;
configure backup optimization on;
configure controlfile autobackup on;
configure default device type to Disk;
configure device type Disk parallelism 2;
configure channel device type Disk format '/backup/RMANBACKUP/%d_LEVEL1_DATAFILE_%s_%p_%D_%M_%Y.bak';
configure maxsetsize to unlimited;
configure snapshot controlfile name to '/backup/RMANBACKUP/ORAMPLS_SNAPCF.f';
set controlfile autobackup format for device type Disk to '/backup/RMANBACKUP/ORAMPLS_CONTROLFILE_%F';
show all;
run {
allocate channel ch1 type Disk maxpiecesize = 1024M;
allocate channel ch2 type Disk maxpiecesize = 1024M;
backup
format '/backup/RMANBACKUP/ORAMPLS_CONTROLFILE_%u_%p_%c' (current controlfile);
backup
incremental level 1
tag 'ORAMPLS_DATAFILE_LEVEL_1'
format '/backup/RMANBACKUP/%d_LEVEL1_DATAFILE_%s_%p_%D_%M_%Y.bak' (database);
release channel ch1;
release channel ch2;
run {
delete noprompt backup of archivelog all completed before 'sysdate - 1';
run {
allocate channel ch1 type Disk maxpiecesize = 1024M;
allocate channel ch2 type Disk maxpiecesize = 1024M;
backup archivelog all
delete all input
format '/backup/RMANBACKUP/%d_ARCHIVELOG_%s_%p_%D_%M_%Y.bak'
tag 'ORAMPLS_ARCHIVELOG_FULL';
release channel ch1;
release channel ch2;
delete noprompt obsolete;
list backup of database;
quit
{color}{color:#000000}id i manually take backup of any datafile twice, its obsoleting older one.
{color}

Retention policy will not affect incremental level 1 backups directly ,it will become obsoleted when its full backups obsoleted ,backup retention policy directly affect only full,level 0 and controlfile backups,archivlelog as well level 1 backup retention policy will affect indirectly.
For detail read that link i have created some sample cases over here within this threads debate
Re: About RMAN backup !!!!
Khurram

Delete obsolete causing issue with archivelog backups......or is it?

Hi, hoping someone will have the answer for me.
Oracle 10g R2 on Windows 2003 R2 Sever.
The start of my RMAN script runs, i do crosschecks and delete obsolete backups from type disk. My redundancy is set to 1. I then run compressed backups of the datafiles and archivelogs with 2 channels. This leaves me with two days of full backups on disk (i have months worth on netbackup) the only problem is that one of the archivelog channel backups from the previous day is missing when i know it was there before the delete obsolete was run.
here is the script:
run{
CROSSCHECK BACKUP;
CROSSCHECK archivelog all;
CROSSCHECK COPY;
CROSSCHECK backup of database;
CROSSCHECK backup of controlfile;
delete noprompt obsolete device type disk;
run {
allocate channel ch1 type disk format 'Z:\backup\rman\orcl\%d_%T_%U';
allocate channel ch2 type disk format 'Z:\backup\rman\orcl\%d_%T_%U';
backup as COMPRESSED BACKUPSET
     format='Z:\backup\rman\orcl\full_%d_%T_%U'
     tag='full_DBbackup_ris'
     database;
backup as COMPRESSED BACKUPSET
     format='Z:\backup\rman\orcl\arch_%d_%T_%U'
     tag='full_ARCHbackup_ris'
archivelog all not backed up delete all input;
sql "alter database backup controlfile to trace as ''Z:\backup\rman\orcl\controlfile_backup_trace.txt''";
release channel ch1;
release channel ch2;
This is my (simplified) list of backups on disk:
Full_day1_chan1
Full_day1_chan2
Arc_day1_chan1
Arc_day1_chan2
Full_day2_chan1
Full_day2_chan2
Arc_day2_chan1
It looks like channel2, days2, archivelog backup is missing. Is this correct? If not does anyone have an idea how to fix this?
thanks in advance.
Steven.

Hi Steven,
The data backed up by rman is written to backup pieces.
Are you missing pieces containing archive logs?
Could it be there was only 1 arc file available so the second channel could not create any backup piece?
Did you could check the output of the backup in v$rman_output?
Regards,
Tycho

RMAN-06067: RECOVER DATABASE required with a backup or created controlfile

Hi,
DB:9.2.0.8
OS: AIX 5.3
I am restoring DB with until time(12/06/2012) for needed tablespaces.
I restored the 12th date controlfile ,which is backed up with archivedlogs. I also have one more controlfile which backed up with full DB..
Restore of tablespaces are completed..
When recovery is going , failed with following error..
allocated channel: c7
channel c7: sid=22 devtype=SBT_TAPE
channel c7: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
allocated channel: c8
channel c8: sid=21 devtype=SBT_TAPE
channel c8: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
executing command: SET until clause
Starting recover at 23-06-2012 02:00:15
released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: c5
released channel: c6
released channel: c7
released channel: c8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 06/23/2012 03:36:57
RMAN-06067: RECOVER DATABASE required with a backup or created controlfile
RMAN>
Restore Script:
connect target /
connect catalog rmanc/recom@lgn_rmanc
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
allocate channel c9 type 'SBT_TAPE';
allocate channel c10 type 'SBT_TAPE';
allocate channel c11 type 'SBT_TAPE';
allocate channel c12 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
release channel c9;
release channel c10;
release channel c11;
release channel c12;
Recover Script:
connect catalog rmanc/recom@lgn_rmanc
connect target /
run {
allocate channel c1 type 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channel c3 type 'SBT_TAPE';
allocate channel c4 type 'SBT_TAPE';
allocate channel c5 type 'SBT_TAPE';
allocate channel c6 type 'SBT_TAPE';
allocate channel c7 type 'SBT_TAPE';
allocate channel c8 type 'SBT_TAPE';
set until time '12-06-2012 00:01:26';
recover tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
release channel c5;
release channel c6;
release channel c7;
release channel c8;
Any suggestion in this is helpful to me..
Thanks in advance,

Hello;
I read your post and here's the thoughts that came to mind : ( my largest concern is you might restore something that damages your current system )
1. So you want to restore the whole DB back to 12/06/2012 to get some tablespaces from then right?
2. Are you restoring to a different system?
3. How did you start the database ( NOMOUNT, MOUNT )
4. If you are restoring the whole DB back to 12/06/2012 how did you restore the control file?
5. Your command shows :
restore tablespace SYSTEM,UNDO_GEN01,UNDO_GEN02,TAB_80K_GENCON,TAB_25M_GENCON;
COMMENT : Generally I use recover tablespace for point in time recovery and use an auxilary destination.
Meaning I don't use restore at all, in fact using restore may cause an issue.
SUMMARY : I don't see how this will work as is.
It seems you want data from five tablespaces from about six months ago including the SYSTEM tablespace.
This is an Incomplete Recovery. I believe I would rethink this completely.
Give the time that has past I would consider restoring the whole database to a different server where cannot damage anything.
Once this is done I would decide how to get the data I need.
Or I would check for a daily export file and recover the tablespace data that way.
So you have some good details on your question but it seems the plan is either missing something or you need to add a few more details.
Example
I'm recovering old tablespaces into a test system.
Here's how I'm not damaging my current production system.
I don't have an export from that date.
So take a step back and either rethink or give a few more details on how this is safe.
Best Regards
mseberg

Rman backup command hangs for datafile ,works with archivelogs backup.

Issue is archivelogs backup is going fine ,But when we go for datafile backup its hanging there from oracle side as not able to give file handle.
RMAN session started with debug it gives only
DBGRPC: ENTERED krmqgns [expect.cpp/673]
16:00:40.19 DBGRPC: krmqgns: looking for work for channel default (krmqgns) [expect.cpp/673]
16:00:40.19 DBGRPC: krmqgns: commands remaining to be executed: (krmqgns) [expect.cpp/673]
16:00:40.19 DBGRPC: CMD type=backup cmdid=1 status=STARTED [expect.cpp/673]
16:00:40.19 DBGRPC: 1 STEPstepid=1 cmdid=1 status=STARTED [expect.cpp/673]
16:00:40.19 DBGRPC: krmqgns: no work found for channel default (krmqgns) [expect.cpp/673]
16:00:40.19 DBGRPC: (krmqgns) [expect.cpp/673]
16:00:40.19 DBGRPC: EXITED krmqgns with status 1 [expect.cpp/673]
16:00:40.19 DBGRPC: krmxpoq - returning rpc_number: 17 with status: STARTED16 for channel sqlbt_ch1 [expect.cpp/673]
16:00:40.19 DBGRPC: krmxr - sleeping for 10 seconds [expect.cpp/673]
Is any body seen this type of message from rman.
Thanks
Shirish

OK. Did you miss the second Oracle document?
RMAN Debug For Backup Shows "krmxr: sleeping for x seconds" [ID 458259.1]
Also a ton of information here :
RMAN backup database as copy from file system to ASM diskgroup very slow
and here :
RMAN Error > Please assist!
and here :
RMAN and Amazon Web Services
http://oravdba.blogspot.com/2011_01_01_archive.html
Best Regards
mseberg

Does Time Machine conflict with Crashplan offline backup for Macs?

Hello,
Has anyone experienced Time Machine on Macs conflicting with Crashplan offline backup for Macs? I would like to run both on my iMac... Time Machine for local backup to my E-drive and Crashplan for a backup to their servers.
Thanks

This article may be of help to you:
http://support.crashplan.com/doku.php/articles/time_machine
I also want to point out that CrashPlan also supports local backup.

RMAN-06067: RECOVER DATABASE required with a backup or created control file

Hi,
Oracle version :10.2.04
I recovered control files
RMAN> restore controlfile to '/oracle/ora10gr4/dbs/nis.ctl';
Starting restore at 21-AUG-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: restoring control file
output filename=/oracle/ora10gr4/dbs/nis.ctl
channel ORA_DISK_1: reading from backup piece /data_idx1/ORAMIG/OMIGTEST/cfc-260103938-20120821-03
channel ORA_DISK_1: restored backup piece 1
piece handle=/data_idx1/ORAMIG/OMIGTEST/cfc-260103938-20120821-03 tag=TAG20120821T152259
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
Finished restore at 21-AUG-12after this i got the below error when i tried to open DB.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1:
'/data_idx1/ORAMIG/OMIGTEST/DATA_FILES/system_1_OMIGTEST.dbf'So i tried the following.
RMAN> restore datafile '/data_idx1/ORAMIG/OMIGTEST/DATA_FILES/system_1_OMIGTEST.dbf';
Starting restore at 21-AUG-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /data_idx1/ORAMIG/OMIGTEST/DATA_FILES/system_1_OMIGTEST.dbf
channel ORA_DISK_1: reading from backup piece /data_idx1/ORAMIG/OMIGTEST29_1_791910787
channel ORA_DISK_1: restored backup piece 1
piece handle=/data_idx1/ORAMIG/OMIGTEST29_1_791910787 tag=TAG20120821T151306
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
Finished restore at 21-AUG-12
RMAN> recover datafile '/data_idx1/ORAMIG/OMIGTEST/DATA_FILES/system_1_OMIGTEST.dbf';
Starting recover at 21-AUG-12
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/21/2012 16:21:45
RMAN-06067: RECOVER DATABASE required with a backup or created control fileCan anyone pls help me with this error?
Thanks

Hi,
Try this command after restore control file.
RMAN> restore database;
RMAN> recover database;
RMAN> alter database open resetlogs;Paste here result, if you are get error.
Regards
Mahir M. Quluzade
www.mahir-quluzade.com

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

Auxiliary filename conflicts with a file used by the target database

Hi,
I am using RMAN backup to duplicate my prod database.
My database is 10g on Linux.
My RMAN script is like this
connect auxiliary /;
connect catalog rman/rman@catalog;
connect target sys/sys@prod;
sql "alter session set optimizer_mode=RULE";
run {
allocate auxiliary channel dup1 type disk;
allocate auxiliary channel dup2 type disk;
allocate auxiliary channel dup3 type disk;
set newname for datafile 1 to '/d05/u08/oracle/qadata/system01.dbf';
set newname for datafile 2 to '/d05/u08/oracle/qadata/system02.dbf';
set newname for datafile 3 to '/d05/u08/oracle/qadata/system03.dbf';
set newname for tempfile 1 to '/d05/u09/oracle/qadata/temp01.dbf';
set newname for tempfile 2 to '/d05/u09/oracle/qadata/temp02.dbf';
set newname for tempfile 3 to '/d05/u09/oracle/qadata/temp03.dbf';
set newname for tempfile 4 to '/d05/u09/oracle/qadata/temp04.dbf';
duplicate target database to qa logfile
group 1 ('/d05/u09/oracle/qadata/log1a.log',
'/d05/u09/oracle/qadata/log1b.log') size 50m,
group 2 ('/d05/u09/oracle/qadata/log2a.log',
'/d05/u09/oracle/qadata/log2b.log') size 50m,
group 3 ('/d05/u09/oracle/qadata/log3a.log',
'/d05/u09/oracle/qadata/log3b.log') size 50m;
I am getting the following error in the middle
Starting Duplicate Db at 18-SEP-10
released channel: dup1
released channel: dup2
released channel: dup3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/18/2010 11:32:07
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename /db01/u08/oracle/proddata/GRCM.dbf conflicts with a file used by the target database
Recovery Manager complete.
Previously the duplicate db was successful, but now it is giving error.
How can I solve this.
Thanks,
Kavitha

5001, 1, "auxiliary file name %s conflicts with a file used by the target database"
// *Cause: RMAN is attempting to use the specified file name as a restore
//         destination in the auxiliary database, but this name is already
//         in use by the target database.
// *Action: Use the CONFIGURE AUXNAME command to specify a name for the data
//          file that does not conflict with a file name in use by the
//          target db.

Rman optimization conflicting with obsolete backups?

Similar Messages

Maybe you are looking for