2 rman backup dump generating

Hi,
while taking rman level o backup two dumps generating.
Kindly help to generate only one dump.
My parameters are
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
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 '/home/oracle/oracle/dbs/snapcf_bmsddb01.f'; # default
Regards,

find the output
RMAN> list backup;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
1281 Incr 0 1023.70M DISK 00:00:17 28-JAN-11
BP Key: 1287 Status: AVAILABLE Compressed: NO Tag: DB_LVL0_BKP
Piece Name: /oradb/rman/rmnbkp/dbbackup/LVL0_BMSDDB01_28-01-2011_16m38uc3_1_1
List of Datafiles in backup set 1281
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 15220618476 28-JAN-11 /oradb/oradata/bmsddb01/system01.dbf
2 0 Incr 15220618476 28-JAN-11 /oradb/oradata/bmsddb01/undotbs01.dbf
3 0 Incr 15220618476 28-JAN-11 /oradb/oradata/bmsddb01/sysaux01.dbf
4 0 Incr 15220618476 28-JAN-11 /oradb/oradata/bmsddb01/users01.dbf
5 0 Incr 15220618476 28-JAN-11 /oradb/oradata/tivoli01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
1282 Incr 0 5.30M DISK 00:00:01 28-JAN-11
BP Key: 1288 Status: AVAILABLE Compressed: NO Tag: DB_LVL0_BKP
Piece Name: /oradb/rman/rmnbkp/dbbackup/LVL0_BMSDDB01_28-01-2011_17m38uct_1_1
Control File Included: Ckp SCN: 15220618488 Ckp time: 28-JAN-11
SPFILE Included: Modification time: 28-JAN-11
BS Key Size Device Type Elapsed Time Completion Time
1337 1.21M DISK 00:00:01 28-JAN-11
BP Key: 1342 Status: AVAILABLE Compressed: YES Tag: ARC_LVL0_BKP
Piece Name: /oradb/rman/rmnbkp/archives_bkp/ARCH_LVL0_BMSDDB01_28-01-2011-19m38udc_1_1
List of Archived Logs in backup set 1337
Thrd Seq Low SCN Low Time Next SCN Next Time
1 1 15220616183 28-JAN-11 15220618132 28-JAN-11
1 2 15220618132 28-JAN-11 15220618403 28-JAN-11
1 3 15220618403 28-JAN-11 15220618537 28-JAN-11

Similar Messages

Rman backup failure, and is generating a large number of files.

I would appreciate some pointers on this if possible, as I'm a bit of an rman novice.
Our rman backup logs indicated a failure and in the directory where it puts its files there appeared a large number of files for the 18th, which was the date of the failure. Previous days backups generated 5 files of moderate size. When it failed it generated between 30 - 40 G of files ( it looks like one for each database file ).
The full backup is early monday morning, and the rest incremental :
I have placed the rman log, the script and a the full directory file listing here : http://www.tinshed.plus.com/rman/
Thanks in advance - George
-rw-r----- 1 oracle dba 1073750016 Jan 18 00:03 database_f734055071_s244_s1
-rw-r----- 1 oracle dba 1073750016 Jan 18 00:03 database_f734055096_s245_s1
-rw-r----- 1 oracle dba 1073750016 Jan 18 00:03 database_f734573008_s281_s1
-rw-r----- 1 oracle dba 1073750016 Jan 18 00:03 database_f734055045_s243_s1
-rw-r----- 1 oracle dba 524296192 Jan 18 00:03 database_f734055121_s246_s1
-rw-r----- 1 oracle dba 1073750016 Jan 18 00:03 database_f734055020_s242_s1
-rw-r----- 1 oracle dba 4294975488 Jan 18 00:02 database_f734054454_s233_s1
-rw-r----- 1 oracle dba 4294975488 Jan 18 00:02 database_f734054519_s234_s1
-rw-r----- 1 oracle dba 4294975488 Jan 18 00:02 database_f734054595_s235_s1
-rw-r----- 1 oracle dba 4294975488 Jan 18 00:02 database_f734054660_s236_s1
-rw-r----- 1 oracle dba 4294975488 Jan 18 00:02 database_f734054725_s237_s1
-rw-r----- 1 oracle dba 4294975488 Jan 18 00:02 database_f734054790_s238_s1
-rw-r----- 1 oracle dba 209723392 Jan 18 00:02 database_f734055136_s247_s1
-rw-r----- 1 oracle dba 73408512 Jan 18 00:02 database_f734055143_s248_s1
-rw-r----- 1 oracle dba 67117056 Jan 18 00:02 database_f734055146_s249_s1
-rw-r----- 1 oracle dba 4194312192 Jan 18 00:02 database_f734054855_s239_s1
-rw-r----- 1 oracle dba 2147491840 Jan 18 00:02 database_f734054975_s241_s1
-rw-r----- 1 oracle dba 3221233664 Jan 18 00:02 database_f734054920_s240_s1
drwxr-xr-x 2 oracle dba 4096 Jan 18 00:00 logs
-rw-r----- 1 oracle dba 18710528 Jan 17 00:15 controlfile_c-1911789030-20110117-00
-rw-r----- 1 oracle dba 1343488 Jan 17 00:15 database_f740621746_s624_s1
-rw-r----- 1 oracle dba 2958848 Jan 17 00:15 database_f740621745_s623_s1
-rw-r----- 1 oracle dba 6415990784 Jan 17 00:15 database_f740620829_s622_s1
-rw-r----- 1 oracle dba 172391424 Jan 17 00:00 database_f740620814_s621_s1

george3 wrote:
Ok, perhaps its my understanding of RMAN that is at fault. From the logs :
Starting recover at 18-JAN-11
channel m1: starting incremental datafile backup set restore
channel m1: specifying datafile copies to recover
recovering datafile copy file number=00001
name=/exlibris1/rmanbackup/database_f734055020_s242_s1
recovering datafile copy file number=00002
name=/exlibris1/rmanbackup/database_f734055045_s243_s1
it seems to make backup copies of the datafiles every night, so the creation of these large files is normal ?Above results indicate that you have full (incremental level 0) backup(all datafiles copies ) and there happen update/recover (applying incremental level 1) backup.So there was happen applying */exlibris1/rmanbackup/database_f734055045_s243_s1* inremental backup to full(level 1) backup.And size should be normal
Why is it making copies of the datafiles even on days of incrementals ?
Because after getting level 1 backup and need applying and every day will apply one incremental backup.

RMAN backup finish with ORA-07445: exception encountered: core dump

Hi Group,
Repeatly we have problems with RMAN, showing this message, we need to know if this message is related to Oracle Database or is the backup software.
Thanks a lot
/pcpdci/oracle/product/920/admin/PCPDCI_bd/udump/pcpdci_ora_31187.trc
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
ORACLE_HOME = /pcpdci/oracle/product/920
System name:    Linux
Node name:      bd.copesa.cl
Release:        2.6.9-78.ELhugemem
Version:        #1 SMP Wed Jul 9 15:57:33 EDT 2008
Machine:        i686
Instance name: PCPDCI
Redo thread mounted by this instance: 1
Oracle process number: 948
Unix process pid: 31187, image: [email protected] (TNS V1-V3)
*** 2011-04-11 00:58:44.241
*** SESSION ID:(1519.515) 2011-04-11 00:58:44.240
SKGFQ OSD: Error in function sbtwrite2 on line 1031
SKGFQ OSD: Look for SBT Trace messages in file /pcpdci/oracle/product/920/admin/PCPDCI_bd/udump/sbtio.log
Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x126, PC: [0xf6abe90b, __GI_strlen()+11]
Registers:
%eax: 0x00000126 %ebx: 0xf6b7dff4 %ecx: 0x00000002
%edx: 0x00000000 %edi: 0x00000000 %esi: 0x00000126
%esp: 0xfeff6154 %ebp: 0xfeff6794 %eip: 0xf6abe90b
%efl: 0x00010202
__GI_strlen()+0 (0xf6abe900) mov 0x4(%esp),%ecx
__GI_strlen()+4 (0xf6abe904) mov %ecx,%eax
__GI_strlen()+6 (0xf6abe906) and $3,%ecx
__GI_strlen()+9 (0xf6abe909) je 0xf6abe933
__GI_strlen()+11 (0xf6abe90b) cmpb %ch,(%eax) __GI_strlen()+13 (0xf6abe90d) jz 0xf6abe9aa
__GI_strlen()+19 (0xf6abe913) inc %eax
__GI_strlen()+20 (0xf6abe914) xor $3,%ecx
__GI_strlen()+23 (0xf6abe917) je 0xf6abe933
*** 2011-04-11 00:58:44.570
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [__GI_strlen()+11] [SIGSEGV] [Address not mapped to object] [0x126] [] []
----- Call Stack Trace -----
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
ksedmp()+274         call     ksedst()             1 ? 0 ? 0 ? 1 ? 33396562 ?
===========================================================
Tracing started for:
   Application Client :   TDPO Linux86
              Version :   5.4.1.0
===========================================================
SBT-13207 07/12/2010 16:32:29 send2.cpp(412): sbtwrite2(): Exit - DSMSENDDATA() failed. dsmHandle = 1
===========================================================
Tracing started for:
   Application Client :   TDPO Linux86
              Version :   5.4.1.0
===========================================================
SBT-14436 07/12/2010 16:52:58 send2.cpp(412): sbtwrite2(): Exit - DSMSENDDATA() failed. dsmHandle = 1
===========================================================
Tracing started for:
   Application Client :   TDPO Linux86
              Version :   5.4.1.0
===========================================================
SBT-15110 07/12/2010 17:01:58 send2.cpp(412): sbtwrite2(): Exit - DSMSENDDATA() failed. dsmHandle = 1
===========================================================
Tracing started for:
   Application Client :   TDPO Linux86
              Version :   5.4.1.0

Reply from nagulan is correct. Our turned out to be an error with TSM. The disk pool had filled up and it was writing this to tape before allowing the backup to continue. The backup didn't handle the "pause" event well and failed out. We only get this with V9 RMAN, not V10 or V11 RMAN backups. This has to be addressed by the backup vendor for V9 as the Oracle RMAN software doesn't seem to handle it well. Maybe configuring a really large timeout for responses MAY fix this, depending on what the code returned from the backup software vendor is and why RMAN isn't happy with it.
In the end it is an issue between V9 RMAN and the backup software we run TSM. Maybe version incompatibility or maybe just V9 is not that robust.

Trace dumps when performing RMAN backups

Hi,
10g release 2
I'm not very experinced with oracle 10g, but on 9i I've never seen this before:
Every time i do a RMAN backup errors is written in the alert log pointing to the instances' trace file in the udump dir.
*** ACTION NAME:(0000018 STARTED16) 2006-09-01 12:07:50.993
*** MODULE NAME:(backup full datafile) 2006-09-01 12:07:50.993
*** SERVICE NAME:(instance_name) 2006-09-01 12:07:50.993
*** SESSION ID:(140.2064) 2006-09-01 12:07:50.993
*** ACTION NAME:(0000022 STARTED111) 2006-09-01 12:07:52.098
*** 2006-09-01 12:09:56.409
*** ACTION NAME:(0000094 STARTED111) 2006-09-01 12:09:56.409
*** MODULE NAME:(backup archivelog) 2006-09-01 12:09:56.409
*** 2006-09-01 12:14:22.122
*** ACTION NAME:(0000117 STARTED16) 2006-09-01 12:14:22.122
*** MODULE NAME:(backup full datafile) 2006-09-01 12:14:22.122
*** ACTION NAME:(0000121 STARTED111) 2006-09-01 12:14:23.238
to me it looks only informational, but i was wondering if anyone been experiencing similar behavior before, and if there are a way to avoid this? or is this an error i should take action on.
any ideas would be very much appricated!

This is a known bug # 4596065 with RMAN when controlfile autobackup is on and flash recovery area is enabled. Workaround is to ignore the trce files.

Why is RMAN backup of 2TB DB still 2TB when expdp dump was only 600mb ?

RDBMS version: 11.2.0.3/Oracle Linux 6.2
We took an RMAN backup of below mentioned DB.
Since DBA_SEGMENTS was showing 2TB , I thought RMAN backup size will be half of that .ie. 1TB . But the RMAN backup size was 1.95 TB!
expdp of the full DB was only 600mb !
SQL> select sum(bytes/power(1024,3)) from dba_segments;
SUM(BYTES/POWER(1024,3))
              2056.27728
SQL> select sum(bytes/power(1024,3)) sumbytesGB, sum(maxbytes/power(1024,3)) sumMaxBytes from dba_data_files;
SUMBYTESGB SUMMAXBYTES
      5451 427.998978
SQL> col file_name format a75
SQL> set pages 300
SQL> select file_name, bytes/power(1024,3) bytesGB, maxbytes/power(1024,3) from dba_data_files;
FILE_NAME                                                                      BYTESGB MAXBYTES/POWER(1024,3)
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_01.dbf                                20                      0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_02.dbf                                20                      0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_03.dbf                                20                      0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_04.dbf                                20                      0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_05.dbf                                20                      0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_06.dbf                                20                      0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_07.dbf                                20                      0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_08.dbf                                20                      0
+CMS_DATA/bcmsprd/datafile/users.271.803502221                                       6             31.9999847
+CMS_DATA/bcmsprd/datafile/undotbs1.265.803502221                                   20                     20
+CMS_DATA/bcmsprd/datafile/sysaux.272.803502221                                     10             31.9999847
+CMS_DATA/bcmsprd/datafile/system.260.803502221                                     10             31.9999847
+CMS_DATA/bcmsprd/datafile/undotbs2.261.803502407                                   20                     20
+CMS_DATA/bcmsprd/datafile/undotbs3.267.803502407                                   20                     20
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_09.dbf                                20                      0
+CMS_DATA/bcmsprd/datafile/cms_s_asset_xa_dat_10.dbf                                20                      0
<snipped>

RMAN does a backup of all formatted blocks --- even if rows have been deleted and the blocks are "logically empty". expdp, obviously, does not backup deleted rows. Similarly, if you've created a table and then subsequently truncated it, the blocks would remain formatted and be candidates for RMAN Backups. Truncated tables would be "empty" and would result in 0 rows exported.
So, you'd have this issue if you've deleted a large number of rows and/or issued truncates.
Hemant K Chitale

Problem in recovery from RMAN backup in case of disk failure

Hi
I have Oracle 9.2.0.1.0 on Windows. Full Hot RMAN backup of database is scheduled on daily basis. I am taking backup on disks. And then i do manually copy them on tapes. If any disk failure occurs than can i recover database completely in this scenario. If tried restoing that backup on different machine as given below
set ORACLE_SID=<name>
rman target sys/<pwd>@ORACLE_SID nocatalog
startup nomount
restore spfile
create pfile from spfile
startup nomount pfile
alter database mount
restore database
Everything worked fine till above steps. Now i will execute last step.
recover database
Here it gives error:-RMAN-06054: media recovery requesting unknown log: thread 1 scn 264750
Still i typed
alter database open resetlogs
Now i can open my database, But is it recovered completely? Or there is loss of some data? Why it is giving this error?
Thanks in advance. Waiting for reply.

I can understand the confusion with this whole concept.
What I meant by all archivelogs is all the archivelogs that were backed up with the backup itself. Again, it is essential to ensure that you archive the current redo log AFTER the backup is performed and then back those archivelogs too. Good thing is, RMAN will take care of this for you if you backup the archivelogs with the BACKUP DATABASE command and/or backup the archivelogs AFTER you run the BACKUP DATABASE command.
Once you've mounted the controlfile and CATALOG the archivelogs, you can go into SQL*Plus and issue the following query:
select SEQUENCE#, FIRST_CHANGE#, NEXT_CHANGE# from v$archived_log
order by FIRST_TIME;This will tell you what archivelog is the latest. Logs generated during the backup may also provide the necessary information. Performing Disaster Recovery should help to understand the full process.
The ONLINELOG directory in FRA is only populated if you've configured your redo logs to be stored there. However, you are on 9i...right? If so 9i doesn't utilize a FRA.
HTH
Edited by: ebrian on Oct 3, 2008 1:08 PM

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

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

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

Rman backup archive log

Hi Guys,
Can advise on the syntax to perform rman backup of archive logs generated in last 2 days?
Should it be 1 or 2?
thanks!
1. BACKUP ARCHIVELOG UNTIL TIME 'SYSDATE-2';
2. BACKUP ARCHIVELOG FROM TIME 'SYSDATE-2';

What prevents you from trying both?
I'm not trying to be difficult here but why take the time to ask people in a forum, not even supplying a version number, and not just find out?
It took me less than 60 seconds to cut-and-paste both of your command lines into RMAN and look at the output.
Edited by: damorgan on Jan 19, 2013 4:11 PM

RMAN backup and restore for Disaster Recovery

Hi Guys,
I am very new to Oracle and have a question about RMAN backup and restore feature. I am simulating a disaster recovery scenario by having two VMs running oracle 11g, say hosta and hostb, hosta is sort of production db and the other a disaster recovery db (one that will be made primary when disaster occurs). My goal is to backup production db using RMAN and restore it on the other machine. For some reason when I restore the db on hostb, the command restores the previous backup but not the most recent one e.g. I took a backup yesterday (09/20) and applied it to the hostb that worked fine, but when I try to apply a fresh backup from today (09/21) it always picks up the old backup. Here's a dump of the screen:
Starting restore at 21-SEP-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /oracle/app/dev/oradata/forums/s
ystem01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /oracle/app/dev/oradata/forums/s
ysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /oracle/app/dev/oradata/forums/u
ndotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /oracle/app/dev/oradata/forums/u
sers01.dbf
channel ORA_DISK_1: reading from backup piece /oracle/app/dev/flash_recovery_are
a/FORUMS/backupset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp
channel ORA_DISK_1: piece handle=/oracle/app/dev/flash_recovery_area/FORUMS/back
upset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp tag=TAG20110920T040950
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:05
Finished restore at 21-SEP-11
Notice that it reads the backup piece from this location /oracle/app/dev/flash_recovery_are
a/FORUMS/backupset/
whereas my latest backups are stored at a different location.
I am executing following steps at the RMAN prompt on hosta and hostb:
hosta (production site)
backup as compressed backupset database plus archivelog
backup current controlfile format'/oracle/oracle_bkup/ctl_%U'
backup spfile
hostb (Disaster site)
set dbid=13732232063
startup force nomount
restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/2011_09_21/o1_mf_nnsnf_TAG20110921T114945_77ndg9ys_.bkp'
shutdown immediate
/* create a init<db_name>.ora file with SPFILE= /oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora */
startup force pfile='/export/home/dev/restore_db/initforums.ora' nomount
restore controlfile from '/export/home/dev/restore_db/backupset/2011_09_21/ctl_1hmn3mic_1_1'
/* restart rman here */
quit
alter database mount;
catalog start with '/export/home/dev/restore_db/backupset/2011_09_21' noprompt;
/* call the next two commands on run */
restore database;
recover database;
alter database open resetlogs
quit
Any help will be greatly appreciated.
Thanks,
Rajesh

Thanks guys, I really appreciate all your help here. I redid everything all over again to get all the information you guys wanted. Since I noticed that more eyes are looking into this I am going to reiterate my steps one more time followed by specific answers to questions. My first backup on Host B is located under ..../restore_db/backupset whereas the subsequent one is under .../restore_db/backupset/backupset2.
I take backup on Host A using:
rman target /
backup as compressed backupset database plus archivelog;
backup spfile;
quit;
I restore the backup on Host B using:
set dbid=13732232063;
startup force nomount;
restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/o1_mf_nnsnf_TAG20110928T171830_787gbpxh_.bkp'
shutdown immediate;
startup force nomount;
restore controlfile from '/export/home/dev/restore_db/backupset/o1_mf_ncsnf_TAG20110928T171638_787gbkxn_.bkp'
quit;
/* restart rman here */
alter database mount;
catalog start with '/export/home/dev/restore_db/backupset' noprompt;
restore database;
recover database;
alter database open resetlogs;
quit;
I take another backup on Host A using (notice no spfile backup this time):
backup as compressed backupset database plus archivelog;
quit;
I restore the database on Host B using:
alter database mount;
catalog start with '/export/home/dev/restore_db/backupset/backupset2' noprompt;
recover database;
alter database open;
quit;
Output of List Backup of database (I have done this after I recovered the second time, also note that it is referring to backupset2 which is were my second backup is stored)
RMAN> list backup of database;
using target database control file instead of recovery catalog
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
89 Full 261.87M DISK 00:01:37 28-SEP-11
BP Key: 91 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
Piece Name: /export/home/dev/restore_db/backupset/o1_mf_nnndf_TAG2011092
8T171638_787g77rx_.bkp
List of Datafiles in backup set 89
File LV Type Ckp SCN Ckp Time Name
1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
97 Full 259.16M DISK 00:00:00 28-SEP-11
BP Key: 100 Status: AVAILABLE Compressed: YES Tag: TAG20110928T18352
7
Piece Name: /export/home/dev/restore_db/backupset/backupset2/o1_mf_nnndf
TAG20110928T183527787lv0nb_.bkp
List of Datafiles in backup set 97
File LV Type Ckp SCN Ckp Time Name
1 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
2 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
3 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
4 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
Output of list backup (done after restoring the control file)
RMAN> list backup;
BS Key Size Device Type Elapsed Time Completion Time
87 89.20M DISK 00:00:26 28-SEP-11
BP Key: 87 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
_28/o1_mf_annnn_TAG20110928T171526_787g50bm_.bkp
List of Archived Logs in backup set 87
Thrd Seq Low SCN Low Time Next SCN Next Time
1 34 1302253 20-SEP-11 1306439 20-SEP-11
1 35 1306439 20-SEP-11 1307647 20-SEP-11
1 36 1307647 20-SEP-11 1307701 20-SEP-11
1 37 1307701 20-SEP-11 1311393 20-SEP-11
1 38 1311393 20-SEP-11 1311511 20-SEP-11
1 39 1311511 20-SEP-11 1332479 20-SEP-11
1 40 1332479 20-SEP-11 1344418 20-SEP-11
1 41 1344418 20-SEP-11 1350409 20-SEP-11
1 42 1350409 20-SEP-11 1350449 20-SEP-11
1 43 1350449 20-SEP-11 1350854 21-SEP-11
1 44 1350854 21-SEP-11 1350895 21-SEP-11
1 45 1350895 21-SEP-11 1353114 21-SEP-11
1 46 1353114 21-SEP-11 1353254 21-SEP-11
1 47 1353254 21-SEP-11 1353865 21-SEP-11
1 48 1353865 21-SEP-11 1353988 21-SEP-11
1 49 1353988 21-SEP-11 1375403 21-SEP-11
1 50 1375403 21-SEP-11 1376149 21-SEP-11
1 51 1376149 21-SEP-11 1376206 21-SEP-11
1 52 1376206 21-SEP-11 1376246 21-SEP-11
1 53 1376246 21-SEP-11 1379990 21-SEP-11
1 54 1379990 21-SEP-11 1380229 21-SEP-11
1 55 1380229 21-SEP-11 1380266 21-SEP-11
1 56 1380266 21-SEP-11 1380528 21-SEP-11
1 57 1380528 21-SEP-11 1380724 21-SEP-11
1 58 1380724 21-SEP-11 1380861 21-SEP-11
1 59 1380861 21-SEP-11 1381033 21-SEP-11
1 60 1381033 21-SEP-11 1381077 21-SEP-11
1 61 1381077 21-SEP-11 1402243 22-SEP-11
1 62 1402243 22-SEP-11 1423341 22-SEP-11
1 63 1423341 22-SEP-11 1435456 22-SEP-11
1 64 1435456 22-SEP-11 1454415 23-SEP-11
1 65 1454415 23-SEP-11 1490903 23-SEP-11
1 66 1490903 23-SEP-11 1491266 23-SEP-11
1 67 1491266 23-SEP-11 1491347 23-SEP-11
1 68 1491347 23-SEP-11 1492761 23-SEP-11
1 69 1492761 23-SEP-11 1492891 23-SEP-11
1 70 1492891 23-SEP-11 1493678 23-SEP-11
1 71 1493678 23-SEP-11 1493704 23-SEP-11
1 72 1493704 23-SEP-11 1494741 23-SEP-11
1 73 1494741 23-SEP-11 1494790 23-SEP-11
1 74 1494790 23-SEP-11 1510154 23-SEP-11
1 75 1510154 23-SEP-11 1514286 23-SEP-11
1 76 1514286 23-SEP-11 1531967 24-SEP-11
1 77 1531967 24-SEP-11 1543266 24-SEP-11
1 78 1543266 24-SEP-11 1558427 24-SEP-11
1 79 1558427 24-SEP-11 1566924 24-SEP-11
1 80 1566924 24-SEP-11 1578292 24-SEP-11
1 81 1578292 24-SEP-11 1596894 25-SEP-11
BS Key Size Device Type Elapsed Time Completion Time
88 84.03M DISK 00:00:30 28-SEP-11
BP Key: 88 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
_28/o1_mf_annnn_TAG20110928T171526_787g63s9_.bkp
List of Archived Logs in backup set 88
Thrd Seq Low SCN Low Time Next SCN Next Time
1 82 1596894 25-SEP-11 1609028 25-SEP-11
1 83 1609028 25-SEP-11 1622303 25-SEP-11
1 84 1622303 25-SEP-11 1626430 25-SEP-11
1 85 1626430 25-SEP-11 1634486 25-SEP-11
1 86 1634486 25-SEP-11 1648398 25-SEP-11
1 87 1648398 25-SEP-11 1669259 26-SEP-11
1 88 1669259 26-SEP-11 1686820 26-SEP-11
1 89 1686820 26-SEP-11 1686959 26-SEP-11
1 90 1686959 26-SEP-11 1689168 26-SEP-11
1 91 1689168 26-SEP-11 1704759 26-SEP-11
1 92 1704759 26-SEP-11 1719597 27-SEP-11
1 93 1719597 27-SEP-11 1740407 27-SEP-11
1 94 1740407 27-SEP-11 1750125 27-SEP-11
1 95 1750125 27-SEP-11 1765592 27-SEP-11
1 96 1765592 27-SEP-11 1781498 28-SEP-11
1 97 1781498 28-SEP-11 1802311 28-SEP-11
1 98 1802311 28-SEP-11 1811009 28-SEP-11
1 99 1811009 28-SEP-11 1813811 28-SEP-11
BS Key Type LV Size Device Type Elapsed Time Completion Time
89 Full 261.87M DISK 00:01:37 28-SEP-11
BP Key: 89 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
_28/o1_mf_nnndf_TAG20110928T171638_787g77rx_.bkp
List of Datafiles in backup set 89
File LV Type Ckp SCN Ckp Time Name
1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf

How can I backup archivelog generated in the last 5 minutes ?

Version: 11.2.0.3
Platform : RHEL 6.2
How can I backup archivelog generated in the last 5 minutes ? Following is what I've attempted so far ?
RMAN> backup archivelog all format '/rman_backups/Nov21Bkp/archiveTest_%U' UNTIL TIME 'sysdate-5/1440';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "until": expecting one of: "archivelog, auxiliary, backupset, backup, channel, controlfilecopy, copy, current, database, datafilecopy, datafile, db_recovery_file_dest, delete, diskratio, filesperset, force, format, from, include, keep, maxsetsize, noexclude, nokeep, not, plus, pool, recovery, reuse, section, skip readonly, skip, spfile, tablespace, tag, to, comma, (, ;"
RMAN-01007: at line 1 column 81 file: standard input
RMAN> backup archivelog all UNTIL TIME 'sysdate-5/1440' format '/rman_backups/Nov21Bkp/archiveTest_%U';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "until": expecting one of: "archivelog, auxiliary, backupset, backup, channel, controlfilecopy, copy, current, database, datafilecopy, datafile, db_recovery_file_dest, delete, diskratio, filesperset, force, format, from, include, keep, maxsetsize, noexclude, nokeep, not, plus, pool, recovery, reuse, section, skip readonly, skip, spfile, tablespace, tag, to, (, ;"
RMAN-01007: at line 1 column 23 file: standard input

HemantKChitale wrote:
You shouldn't specify both "ALL" and "FROM/UNTIL TIME"
Also if you want the archivelogs generated in the last 5 minutes, you should be using FROM TIME.
If you want the archivelogs generated until 5minutes ago (and not the latest archivelogs), you should be using UNTIL TIME.
Hemant K Chitale
I've wondered about the utility of the FROM and UNTIL options for backup of archivelogs. If one is going to back them up, why would one use an option that distinctly introduces the possibility of having gaps - un-backed-up archivelogs? Why would one not simply back up all archives not previously backed up at least once?
I'm sure you'll give me a valid response for a situation for which my imagination fails to see.

10.1.0.2.0 RMAN backup- What would cause RMAN to hang?

Oracle gurus- Fellow in trouble, need your guidance.
I have a serious issue that has no direct error to examine or fix.
I have a replicated offline server that has a scripted RMAN backup to run nightly, but the backup times flux from what should be only 1 hour 30 minutes. Every other day it takes up to 10 hours to complete a backup that normally takes 1 hr 30 minutes. There is no difference in data loads- the server is offline and the data has not changed to any effect. I use database control instead of grid control, and I turn off emctl every night before the rman backup- I thought maybe emctl was hogging resources. There is nothing else running on the server except replication inserting a couple of rows of data on three tables every other minute.
Where would I look to see where the problem exists when no errors are generated?
Does RMAN wait to backup files if they are being accessed?
Here is my backup script (the OS is Linux AS3) I run an AT job nightly.
at -f /path/path/rman_backup 0600 tomorrow
rman target/
run {
backup database plus archivelog;
delete noprompt obsolete;
sql 'alter system archive log current';
exit;
The Administrators are running a Legato Jukebox backup? a tape backup that backs up my DB files nightly. They run the Legato backup 3 hours after my RMAN backup- the problem is that my RMAN backup may be running during the Legato backup- so I assume that contention occurs and both backups fight for the DB files. This is not an issue when RMAN plays nice and finishes in the normal 1 hour 30 minutes, but when it exceeds 3 hours- we have serious issues, both RMAN and Legato backups take 10 hours.
Please help, I am really puzzled. This is causing me major headaches, how can I assure that RMAN has a consistent backup time to completion. Is there anyway to script it to use more resources to ensure it finishes quickly?

Have you monitored CPU and I/O during this process? Are there any other processes running during this time? You mentioned the server is offline, but you also mentioned replication is taking place ?
You could query V$BACKUP_ASYNC_IO and look at EFFECTIVE_BYTES_PER_SECOND, WAITS and IO_COUNT.
During the backup, you can run the following query to monitor RMAN:
SELECT sid, serial#, context, sofar, totalwork,
     round(sofar/totalwork*100,2) "% Complete"
     FROM v$session_longops
     WHERE opname LIKE 'RMAN%'
     AND opname NOT LIKE '%aggregate%'
     AND totalwork != 0
     AND sofar <> totalwork;If the % Complete doesn't seem to be increasing, you should run the following select to determine what waits exist:
SELECT sid, seconds_in_wait AS sec_wait, event FROM v$session_wait
     WHERE wait_time = 0
     ORDER BY sid;

Rman backup job Suspended on Agent Unreachable

Hi,
I have Oracle 10.2.0 installed on windows 2003 server. i configure oracle suggested rman backup which works fine till now. but now it shows
Suspended on Agent Unreachable message and backup doesn't happen.
if check like
C:\Documents and Settings\Administrator>emctl status agen
Oracle Enterprise Manager 10g Database Control Release 10
Copyright (c) 1996, 2005 Oracle Corporation. All rights
Agent is Not Running
C:\Documents and Settings\Administrator>emctl start agent
Oracle Enterprise Manager 10g Database Control Release 10
Copyright (c) 1996, 2005 Oracle Corporation. All rights
These Windows services are started:
   Application Experience Lookup Service
   Application Management
   Automatic Updates
   COM+ Event System
   COM+ System Application
   Computer Browser
   Cryptographic Services
   DCOM Server Process Launcher
   DefWatch
   Distributed File System
   Distributed Transaction Coordinator
   DNS Client
   DNS Server
   Error Reporting Service
   Event Log
   File Replication Service
   FTP Publishing Service
   HTTP SSL
   IIS Admin Service
   Indexing Service
   Intel PDS
   Intersite Messaging
   IPSEC Services
   Kerberos Key Distribution Center
   Logical Disk Manager
   LogMeIn
   LogMeIn Maintenance Service
   Net Logon
   Network Connections
   Network Location Awareness (NLA)
   NT LM Security Support Provider
   OracleDBConsoleneo
   OracleOraDb10g_home1iSQL*Plus
   OracleOraDb10g_home1TNSListener
   OracleServiceNEO
   Plug and Play
   Print Spooler
   Protected Storage
   Remote Access Connection Manager
   Remote Procedure Call (RPC)
   Remote Registry
   Secondary Logon
   Security Accounts Manager
   Server
   Shell Hardware Detection
   SQL Server (MSSQLSERVER)
   SQL Server Agent (MSSQLSERVER)
   SQL Server Analysis Services (MSSQLSERVER)
   SQL Server FullText Search (MSSQLSERVER)
   SQL Server Integration Services
   SQL Server Reporting Services (MSSQLSERVER)
   Symantec AntiVirus Server
   System Event Notification
   Task Scheduler
   TCP/IP NetBIOS Helper
   Telephony
   Terminal Services
   Windows Management Instrumentation
   Windows Search
   Windows Time
   Workstation
   World Wide Web Publishing Service
The command completed successfully.means my agent was stop but now i start it.
i find on Google that this type of error happen when you change in database like ip address, sid etc but i haven't do any change.
i am facing same problem so many times.
Now how to reschedule the existing backup job so that it starts work again.
thanks
umesh

thanks for reply
i do it.
C:\Documents and Settings\Administrator>emctl status dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
http://Techwave:5500/em/console/aboutApplication
EM Daemon is not running.
Logs are generated in directory C:\oracle\product\10.2.0\db_1/Techwave_neo/sysman/log
C:\Documents and Settings\Administrator>emctl stop dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
http://Techwave:5500/em/console/aboutApplication
The OracleDBConsoleneo service is stopping.....
The OracleDBConsoleneo service was stopped successfully.
C:\Documents and Settings\Administrator>emctl start dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
http://Techwave:5500/em/console/aboutApplication
Starting Oracle Enterprise Manager 10g Database Control ...The OracleDBConsoleneo service is starting................
The OracleDBConsoleneo service was started successfully.now it is working fine.
now issue is how i reschedule my suspended job.
i got this error.
Edit is not supported for this job type, only general information about the job can be updated No scheduled executions - this job can not be modified.

RMAN backup slow

Hi,
I have a Production Database (10204) running on HP Unix (B.11.11).
Daily morning 6AM, a full RMAN backup runs. The db size is only around 225GB. But it takes 4.5 hours to complete.
The syntax which I use is given below.
RMAN> run {
     allocate channel ch1 type "sbt_tape";
     allocate channel ch2 type "sbt_tape";
     allocate channel ch3 type "sbt_tape";
send
'NB_ORA_CLIENT=jjcprd04-back.backup.ncsus.jnj.com,NB_ORA_POLICY=JJCPRD04-RMAN';
     backup
     format 'bk_%s_%p_%t'
     (database include current controlfile);
     sql 'alter system archive log current';
     backup
     format 'arch_%d_%s_%p_%t'
     (archivelog all delete input );
Is there a way to increase the speed of this backup? Currently the backup is way too slow as it takes 4.5 hours to copy 225GB of data!
Thanks!

I'll start by stating that backups directly to tape are generally quite slow.
I'd still recommend moving to disk backups though... and just archiving it to a tape...Hi Jony,
You can of course backup to disk. Thats a common solution. But you have to deal with space more than everything. In addition to that backing up to disk does not free you from moving/copying your data - depending on your backup strategy - to a long-term storage.
So you have two different and not conjunct backup operations: the rman backup itself and the job which backups the rman area to another media.
In recovery cases you might end up with RMAN requesting older backupsets which are not on disk anymore. This will most probably lead to recovery failures and manual intervention which is not desirable in recovery scenarios.
Another point is the control of the data flow. Backing up via a MML (i.e. "to tape") does not necessarily mean "to tape". Instead it means "to the backup software" which is responsible for managing the backup data. Common scenarios involve backing up the full backups via SAN directly to tape and backing up the archivelogs or incremental backups over LAN which will be stored by the backup software on a hard disk and later copied and/or moved on to tape. The data flow (to SAN / to disk / whereever) is solely controlled by the backup software.
The advantage here is one continuous backup and restore job. The backup software deals with "where is my saveset located" and requests automatically the needed tapes or disks in recovery scenarios. This makes recoveries far more flexible and comfortable.
Regarding the throughput i have set up a rather large OLTP database ( 12 TB currently) which is backed up with EMC Networker. Full backups are written via SAN directly to tape. The average speed with four LTO-3 drives is approx. 550 MB/s (the tape drives compress the data in hardware; the database itself is text-only and seems rather good compressable). I guess thats not too bad.
you can also compress the BACKUPSETS (this generates a little more CPU but less network IO)He said he is on HP-UX. These kind of CPUs tend to be not that fast. Using compression is an option worth testing but there is another point to test when doing compressed backups: The RESTORE TIME.
Ronny Egner
My Blog: http://blog.ronnyegner-consulting.de

RMAN backup and restore in network

Hi,
I have already did cold backup of database using RMAN in the same disk on a linux OS. It was successful.
Now i want to do the same backup in a different disk on a another system. Both the systems are in same network.
Please help me

You can name the NFS mount point anything meaningful.
In your RMAN Backup script, you would use the FORMAT clause to specify the location where the backups are to go to.
For example, if the filesystem from linux2 is NFS-mounted on linux as as /NFS_backup your RMAN command would be
BACKUP DATABASE FORMAT '/NFS_backup/%U';
BACKUP ARCHIVELOG ALL FORMAT '/NFS_backup%U' DELETE INPUT ;Look up the syntax of the formatSpec in the Backup and Recovery Reference for formats other than %U. %U generates a Unique File Name.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Implications of losing ArchivedLogs and RMAN Backup directory.

DB version:10gR2
We have a test database which is important since it is a pre-production DB used by the application team for their final testing .
Currently this DB is not in Archivelog mode. Every night a cronjob runs to create the expdp datapump dump of the schemas in this DB.
We want to test online RMAN backups in this DB. So we are going to put this db in ARCHIVELOG mode for a week.
The RMAN backup pieces will be stored in +/u03/data1/orabkp+ and the Archived logs will be stored in +/u04/ach_logs+ directory.
We want to know the impact of /u04/ach_logs , the archived logs directory getting accidently deleted. I know that the accidental deletion of RMAN backup directory shouldn't impact the normal running of the database. But we want to know the if the accidental deletion of Archived redo logs directory will impact the DB.
Edited by: user10633418 on Sep 25, 2009 2:53 AM

NO, it will not impact in the database. If you delete any archive log files database will run normally. But you won't restore your database in point in time. For recovery you need your full backup of all datafiles + archivelogs + online redo log files.
For a backup policy of any production database where you don't want to lose any transaction you must reserve your archive logs files by rman backup.
Regards
Asif Kabir

2 rman backup dump generating

Similar Messages

Maybe you are looking for