Follow-up of RMAN backup job details

Version:11.2.0.3/Solaris 11

Follow the details of the work of backup RMAN, this point of view view/dyn.performance dictionary do you use?

In our store, we use the incremental update (progressive fusion). For details of the previous work of RMAN, I tried to use

v$ rman_status

and

v$ rman_backup_job_details

But the information provided by these 2 views do not match. For example, on June 26, 2013, there is an incremental backup and a backup archivelog. According to the v$ rman_status, both of them took 61 minutes (46 + 15)

According to v$ rman_backup_job_details, backup jobs took 96 minutes. It doesn't seem to provide all the info about archive newspaper bkp however.

The start_time and end_time provided by two of these points of view is not math!

Col starttime format a25

Col endtime format a25

Select the status, object_type, to_char (start_time, 'dd' / MY/yyyy:hh:mi:ss) as starttime,

TO_CHAR (end_time, 'dd' / my/yyyy:HH:mi:ss) as end time,

TO_NUMBER(end_time-start_time) * 24 * 60 duration_minutes

of sys.v$ rman_status where start_time > trunc (sysdate) - 20-operation = "BACKUP."

end_time desc order.

OBJECT_TYPE STARTTIME ENDTIME DURATION_MINUTES STATUS

----------------------- ------------- ------------------------- ------------------------- ----------------

FAILED ARCHIVELOG 07/JUN / 2013:08:47:44

ARCHIVELOG FINISHED 26/JUN / 2013:06:49:16 26/JUN / 2013:07:36:14 46.9666667

FINISHED THE INCR DB 26/JUN / 2013:06:33:18 26/JUN / 2013:06:49:16 15.9666667

ARCHIVELOG FINISHED 25/JUN / 2013:06:50:55 25/JUN / 2013:07:58:01 67.1

FINISHED THE INCR DB 25/JUN / 2013:06:25:06 25/JUN / 2013:06:50:55 25.8166667

ARCHIVELOG COMPLETED 24/JUN / 2013:06:15:42 24/JUN / 2013:07:07:54 52.2

FINISHED DB INCR 24/JUN / 2013:06:01:09 24/JUN / 2013:06:15:42 14.55

COMPLETED ARCHIVELOG 23/JUN / 2013:09:47:48 23/JUN / 2013:10:01:19 13.5166667

FINISHED THE DB INCR 23/JUN / 2013:09:40:27 23/JUN / 2013:09:47:48 7.35

ARCHIVELOG FINISHED 22/JUN / 2013:07:23:18 22/JUN / 2013:07:41:29 18.1833333

FINISHED INCR DB 22/JUN / 2013:07:15:35 22/JUN / 2013:07:23:17 7.7

COMPLETED ARCHIVELOG 21/JUN / 2013:07:30:33 21/JUN / 2013:09:05:50 95.2833333

FINISHED THE INCR DB 21/JUN / 2013:06:39:35 21/JUN / 2013:07:30:33 50.9666667

ARCHIVELOG FILLED 20/JUN / 2013:07:35:54 20/JUN / 2013:09:25:03 109.15

FINISHED THE INCR DB 20/JUN / 2013:06:55:08 20/JUN / 2013:07:35:54 40.7666667

ARCHIVELOG COMPLETED 19/JUN / 2013:07:20:10 19/JUN / 2013:08:27:28 67.3

FINISHED THE INCR DB 19/JUN / 2013:07:00:02 19/JUN / 2013:07:20:10 20.1333333

ARCHIVELOG COMPLETED 18/JUN / 2013:07:27:30 18/JUN / 2013:09:19:50 112.333333

FINISHED THE INCR DB 18/JUN / 2013:07:02:09 18/JUN / 2013:07:27:30 25,35

ARCHIVELOG COMPLETED 17/JUN / 2013:07:42:20 17/JUN / 2013:08:40:29 58,15

FINISHED DB INCR 17/JUN / 2013:07:22:29 17/JUN / 2013:07:42:20 19.85

ARCHIVELOG COMPLETED 17/JUN / 2013:06:28:16 17/JUN / 2013:07:42:44 74.4666667

FINISHED DB INCR 17/JUN / 2013:01:57:49 17/JUN / 2013:06:28:11 270.366667

ARCHIVELOG FINISHED 16/JUN / 2013:02:18:02 16/JUN / 2013:04:22:26 124.4

FINISHED DB INCR 16/JUN / 2013:01:48:18 16/JUN / 2013:02:18:02 29.7333333

ARCHIVELOG FINISHED 14/JUN / 2013:07:27:44 14/JUN / 2013:08:40:53 73.15

FINISHED DB INCR 14/JUN / 2013:07:01:19 14/JUN / 2013:07:27:43 26.4

ARCHIVELOG COMPLETED 13/JUN / 2013:06:56:13 13/JUN / 2013:07:47:50 51.6166667

FINISHED THE INCR DB 13/JUN / 2013:06:42:11 13/JUN / 2013:06:56:13 14.0333333

ARCHIVELOG FILLED 12/JUN / 2013:07:12:43 12/JUN / 2013:08:12:10 59.45

FINISHED INCR DB 12/JUN / 2013:06:45:51 12/JUN / 2013:07:12:43 26.8666667

ARCHIVELOG FINISHED 11/JUN / 2013:07:21:36 11/JUN / 2013:08:46:11 84.5833333

FINISHED THE INCR DB 11/JUN / 2013:06:52:29 11/JUN / 2013:07:21:36 29.1166667

ARCHIVELOG COMPLETED 10/JUN / 2013:07:04:49 10/JUN / 2013:07:55:15 50.4333333

FINISHED THE INCR DB 10/JUN / 2013:06:49:10 10/JUN / 2013:07:04:49 15.65

COMPLETED ARCHIVELOG 09/JUN / 2013:08:10:13 09/JUN / 2013:09:04:10 53.95

FINISHED DB INCR 09/JUN / 2013:07:50:24 09/JUN / 2013:08:10:13 19.8166667

COMPLETED ARCHIVELOG 08/JUN / 2013:07:37:09 08/JUN / 2013:08:33:58 56.8166667

FINISHED DB INCR 08/JUN / 2013:07:17:56 08/JUN / 2013:07:37:09 19.2166667

COMPLETED ARCHIVELOG 07/JUN / 2013:08:32:01 07/JUN / 2013:09:34:11 62.1666667

FINISHED DB INCR 07/JUN / 2013:07:36:27 07/JUN / 2013:08:32:01 55.5666667

COMPLETED ARCHIVELOG 07/JUN / 2013:08:48:10 07/JUN / 2013:11:28:14 160.066667

42 selected lines.

-Output from v$ rman_backup_job_details

Select the State, input_type;

to_char(start_time,'dd/mm/yyyy:HH:mi:ss') as starttime,

to_char(end_time,'dd/mm/yyyy:HH:mi:ss') as end time,

TO_NUMBER(end_time-start_time) * 24 * 60 duration_minutes

V $ rman_backup_job_details

where start_time > trunc (sysdate) - 20

end_time desc order.

INPUT_TYPE STARTTIME ENDTIME DURATION_MINUTES STATUS

----------------------- ------------- ------------------- ------------------- ----------------

FAILED ARCHIVELOG 07/06 / 2013:08:47:44

FINISHED THE INCR DB 26/06 / 2013:06:00:09 26/06 / 2013:07:36:14 96.0833333

FINISHED THE INCR DB 25/06 / 2013:06:00:08 25/06 / 2013:07:58:01 117.883333

FINISHED THE INCR DB 24/06 / 2013:06:00:09 24/06 / 2013:07:07:54 67.75

FINISHED THE DB INCR 23/06 / 2013:08:07:56 23/06 / 2013:10:01:19 113.383333

FINISHED THE INCR DB 22/06 / 2013:06:00:10 22/06 / 2013:07:41:29 101.316667

FINISHED THE INCR DB 21/06 / 2013:06:00:12 21/06 / 2013:09:05:50 185.633333

FINISHED THE INCR DB 20/06 / 2013:06:00:12 20/06 / 2013:09:25:03 204.85

FINISHED THE INCR DB 19/06 / 2013:06:00:11 19/06 / 2013:08:27:28 147.283333

FINISHED THE INCR DB 18/06 / 2013:06:00:16 18/06 / 2013:09:19:50 199.566667

FINISHED THE INCR DB 17/06 / 2013:06:00:13 17/06 / 2013:08:40:29 160.266667

FINISHED THE INCR DB 16/06 / 2013:06:04:02 17/06 / 2013:07:42:44 818,7

FINISHED THE INCR DB 15/06 / 2013:06:05:12 16/06 / 2013:04:22:26 617.233333

FINISHED THE INCR DB 14/06 / 2013:06:00:09 14/06 / 2013:08:40:53 160.733333

FINISHED THE INCR DB 13/06 / 2013:06:00:09 13/06 / 2013:07:47:50 107.683333

FINISHED THE INCR DB 12/06 / 2013:06:00:10 12/06 / 2013:08:12:10 132

FINISHED THE INCR DB 11/06 / 2013:06:00:17 11/06 / 2013:08:46:11 165,9

FINISHED THE INCR DB 10/06 / 10/06 2013:06:00:14 / 2013:07:55:15 115.016667

FINISHED THE INCR DB 09/06 / 2013:06:00:10 09/06 / 2013:09:04:10 184

FINISHED THE DB INCR 08/06 / 08/06 2013:06:00:09 / 2013:08:33:58 153.816667

FINISHED THE DB INCR 07/06 / 2013:06:00:19 07/06 / 2013:09:34:11 213.866667

COMPLETED ARCHIVELOG 07/06 / 2013:08:48:10 07/06 / 2013:11:28:14 160.066667

22 selected lines.

When I run a full/incremental backup archivelog with it shows only as a job in v$ rman_backup_job_details. If I run explicitly just a backup archivelog all RMAN makes it appear separately as an ARCHIVELOG backup in v$ rman_backup_job_details.

rman_status indicates the individual pieces of the jobs. For example, for a full backup, it shows the db backup and the archivelog.

The start and end time in rman_status should match with $rman_backup_job_details.

Lets take the 25th, for example:

In man_backup_job_details

INPUT_TYPE STARTTIME ENDTIME DURATION_MINUTES STATUS

----------------------- ------------- ------------------- ------------------- ----------------

FINISHED THE INCR DB 25/06 / 2013:06:00:08 25/06 / 2013:07:58:01 117.883333

In v$ man_status:

OBJECT_TYPE STARTTIME ENDTIME DURATION_MINUTES STATUS

----------------------- ------------- ------------------------- ------------------------- ----------------

ARCHIVELOG FINISHED 25/JUN / 2013:06:50:55 25/JUN / 2013:07:58:01 67.1

FINISHED THE INCR DB 25/JUN / 2013:06:25:06 25/JUN / 2013:06:50:55 25.8166667

You should view your log files to see what rman was between 06:25:06 and 06:00:08 when work began at the start of the incremental backup.

You can see that the end time is the same in both views.

Not easy to explain but I hope that helps.

Tags: Database

Notification by e-mail for the owner

A Notification rule can be used by any administrator to receive notifications on this work. The owner can choose to receive e-mail notifications based on the values of selected below status. E-mail will be sent according to the timing of notification of the owner.

On-demand

running

suspended

succeeds in issues

Action required

TIP

Owners must apply the rules of the event to get notifications

On-demand

running

suspended

succeeds in

issues

Action required

TIP

No owners must apply the rules of the event to receive notifications on this work.

wit problem via rman backup
10 2 0 5 version
Windows xp

I am taking cold backup of test data without using the catalogue.

I mounted database and tried the following query, his throw errror below... Please help

RMAN > backup database;

From backup February 17, 11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 155 devtype = DISK
channel ORA_DISK_1: from full datafile backupset
channel ORA_DISK_1: specifying datafile (s) in backupset
RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 17/02/2011 15:56:28
ORA-19602: no backup or copy of current file in NOARCHIVELOG mode
continue other job steps, not a not working will not re-run
channel ORA_DISK_1: from full datafile backupset
channel ORA_DISK_1: specifying datafile (s) in backupset
including the current control in backupset file
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 to February 17, 11
channel ORA_DISK_1: finished piece 1 to February 17, 11
room handle=D:\ORACLE\PRODUCT1\10.2.0\FLASH_RECOVERY_AREA\CATALOG\BACKUPSET\2011_02_17\O1_MF_NCSNF_TAG20110217T155628_6OSXYQHK_. Tag BKP = comment TAG20110217T155628 = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:03
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================

RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 17/02/2011 15:56:28
ORA-19602: no backup or copy of current file in NOARCHIVELOG mode

Thanks and greetings
Arun
Was there a 'cancel the stop' or a crash before mount 'start '? If so start database, stop it properly and try again.

Werner

RMAN backup and cross-checking script
Hello

I just joined a new company this week. As would any s/n, I was going just through the RMAN backup scripts used in the new environment.
Here we run weekly RMAN backup complete for some of the databases that I am responsible for managing. The script and schedules are as follows.

Every Sunday from 21:00, we organize a weekly job overlap

Connect target username/pwd@DBNAME
Connect catalog username/pwd@DBNAME

Run {}
CROSS-CHECKING OF BACKUP;
DUPLICATION OF COPY;
OVERLAP BACKUPSET;
OVERLAP ARCHIVELOG ALL;
DELETE NOPROMPT OBSOLETE;
}

Every Sunday from 9:30, we run the RMAN backup command which is

Connect target username/pwd@DBNAME
Connect catalog username/pwd@DBNAME

run
{
CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
SQL 'alter system archive log current';
backup as backupset database include current controlfile;
SQL 'alter system archive log current';
ARCHIVELOG BACKUP of time ' SYSDATE-8';
DELETE ARCHIVELOG ALL COMPLETED BEFORE ' SYSDATE-15';
}

A database that I will handle has been set up just over a week before I join.
28 FEV 21:00 - no set of backup/copy/backup of overlap. I hope it will be cuts across all archive logs available in the database. No obsolete backup/copy/backup/archivelogs to remove.
28 FEV 21:30 - sets the retention policy at 7 days, full backup of database backup and backup all archivelogs (sysdate-8). No newspaper archive to remove the database was created (migrated) less than 15 days back.

7 March 21:00 - contre-vérifie the backupset (taking the 28 fev 21:30). No backup/copy of overlap.
Question 1: Is there a backup obsolete here to delete?
Own thought: Recovery window is 7 days. RMAN needs a backup in order to recover the database in any time-7 days to the present time (7 March 21:00 - 7 days = 28 fev 21:00). No obsolete backup to delete.

7 March 21:30 - full database backup and fails to save all logs archiving (sysdate-8). No space in the Flash recovery disk group. As the archivelog backup failed and RMAN complete, it has not removed the archivelogs ' sysdate-15'.

Backup is running again on 14 March. Of course, it will fail because there is no enough space in the Group of recovery disks.

Future: I'm confused
March 14, 21:00: contre-vérifie the backupset (supported March February 21:30). No backup/copy of overlap.
Question 2: How do I know what is here obsolete? From the window of 7 days recovery, 14 March 21:00-7 days is March 7, 21:00. Last backup was taken on March 7, 21:30.
To get back to 21:00, RMAN makes keep the backup of 28 March?... Does this mean whenever I'll have copies of backup 3?...

14 March 21:30 - backup database... Log Archive backup will fail because there is no space. (I think to make a compressed backup).

Question 3: How those wise commands?
ARCHIVELOG BACKUP of time ' SYSDATE-8';
DELETE ARCHIVELOG ALL COMPLETED BEFORE ' SYSDATE-15';

If I take a successful backup of the archivelogs sysdate-8, why I need to keep the archivelogs before that? What could be the reason the previous DBA kept DELETE ARCHIVELOG COMPLETED BEFORE ANY 'SYSDATE-15 '; Rather than give DELETE ARCHIVELOG FINISHED FIRST and FOREMOST ' SYSDATE-8 "?

Thanks in advance for your help.

Published by: user8907052 on March 11, 2010 12:10
If your database to 9i and above, then you don't need to pass - sql 'alter system archive log current;' before you perform the backup as RMAN automatically archives the log during recovery.

RMAN backup permission problem
My RMAN backup is scheduled.

Even backup script fails sometimes and sometimes executed successfully
When fails, it gives the following error.

Your "cron" job the xxxx
/ U07/RMAN/scripts/call_arch_bkup. SCP

produces the following output:

Recovery Manager: release 9.2.0.1.0 - 64 bit Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

connected to target database: xxxx
connected to the recovery catalog database
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-00554: initialization of the package manager internal collection failed
RMAN-04005: target database error:
ORA-09925: cannot create the audit trail file
SVR4 error: 13: permission denied
Additional information: 9925

If there is permission problem then there a few times, it runs successfully.
It totally depends on your condition. Security can you move your old files to another location, course and then run your command?

RMAN backup location must change and remove obsolete

Dear Experts,
I'm working on the following environment,
Operating system: Windows server 2012 R2
Oracle version: 11.2.0.1.0 release
Type of RMAN backup: Cumulative (preferred by the direction and I can't change it in differential backup)
My current situation,
I set up RMAN and H: drive for purposes of backup and G: for Archivelog.
Recently, my city was covered by the flood waters and the server works not for a week so that we delete obsolete level 0 does not work.
Currently there is not enough space to run a level 1 and level 0, while I should change the backup location.
My Question is,
(1) I need to change this location of drive H: to G: drive backup backup correctly without error not enough space.
(2) after having taken a level 1 and level 0, depending on my 1 redundancy, RMAN mechanism should delete obsolete backup disk without failure G: and H:.
Kindly help me how to get to my need. This will help me, thanks in advance

You can

1. replace the DB_RECOVERY_FILE_DEST G:

2 run backups

3. wait for the DELETE OBSOLETE delete obsolete backups of H:

and then

4. change the DB_RECOVERY_FILE_DEST return h as it was more early

In this way, you don't have to use the FORMAT or CHANNEL of CONFIGURE commands (I was referring to CONFIGURE CHANNEL, not ALLOCATE CHANNEL) to change the destination of the backup

Hemant K Collette

RMAN backup gets already

Hi all;
RMAN > set the channel 1 device type disc format ' / u01/rmanbkp ";
new RMAN configuration settings:
CONFIGURE the CHANNEL 1 DEVICE TYPE DISK FORMAT ' / u01/rmanbkp ";
new RMAN configuration settings are stored successfully
output channel: ORA_DISK_1
RMAN > list backup;
specification does not match the backups in the repository
RMAN > backup database tag = "NORMAL_BKP_15_jul_15";
From 25 July 15 backup
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 20 type of device = DISK
channel ORA_DISK_1: from complete compressed datafile backup set
channel ORA_DISK_1: specifying datafile (s) in the backup set
Enter a number of file datafile = 00005 name=/u03/app/oracle/oradata/crms/tbs02.dbf
Enter a number of file datafile = 00001 name=/u02/app/oracle/oradata/crms/system01.dbf
Enter a number of file datafile = name=/u01/crmsx4.dbf 00024
channel ORA_DISK_1: starting piece 1 to July 25, 15
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 25/07/2015 10:30:26
ORA-19504: cannot create the file ' / u01/rmanbkp.
ORA-27038: created file already exists
Additional information: 1
There is no file physically in/u01/rmanbkp
DB version: 11.2.0.1 on (Redaht)

RMAN > set the channel 1 device type disc format ' / u01/rmanbkp ";

Specify format with extension, something like below

RMAN > set up the channel 1 device type disk format ' / u01/rmanbkp/backup%U';

http://docs.Oracle.com/CD/B28359_01/backup.111/b28273/rcmsubcl010.htm

How to restore RMAN backups

Hello
I tried to include works of RMAN Oracle 12 c
If I use the following command, I should have the backuppiece and the archivelog saved in a folder:
RMAN > BACKUP database DATA PLUS ARCHIVELOG;
If I ran this command in 4 different days, which I ended up having 4 folders with different inside files
I guess that, in these files, I have the data files and the archivelogs
Now I move these folders to tape, re-cutting the backups and delete expired
Say that in a month, I need one of these backups if I put a band records and I added start with 'c:\path_of _restored_folder _L', so I added all files in the folder that I restored from tape
Now, if I try to restore the basis of all is well but when I run the recover, it is missing some archiving logs it says
If I put all the files for 4 days then he finds the archivelog she needs and pick up without problem
on this basis I understand that in the folder containing a backuppiece of a specific day there is the newspaper of archive that I needed to recover from the DB, is that true? How can I know if the backups folder I need to replace in order to have all the required log archiving?
At the moment my DB retrieves only if I handed out the Ribbon last backup folder, if I handed out the previous, it restores, but is not recover
Also I have this configuration of the oracle recovery 3 days window maintains backups in order to be able to restore and recover the last 3 days and he simply deletes all obsolete if the FRA is full
I tried earlier to set up the window of 3 days as a test recovery
I ran a few backups and after that I ran the 5th FRA leak out of space and the backup fails
I expect rman to remove the old backup and make way for a new that I have 5 backuppiece and the FRA is full, why he not do?
Thank you

The default behavior of RECOVER is to make a full recovery - right until the transactions today. So it must all archivelogs.

If you want to restore and recover to a point in time, use the SET clause to THAT specify a sequence of the newspaper or time or SNA. Oracle will then not get beyond that point in time - that is to say he will not seek further archiving logs.

(Ideally, when you restore an old backup, I also begins to restore the old controlfile, then using this controlfile).

If you use the FRA in this way

a. set db_recovery_file_dest_size and db_recovery_file_dest

b. * not * used a FORMAT clause in the BACKUP command

Oracle will recognize all backups in the FRA (you can check by querying V$ FLASH_RECOVERY_AREA_USAGE before and after the backup).

In this case, Oracle can and will automatically purge outdated backups - that is to say any backup older than the retention period, provided that there is at least a L0 or backup complete closest to the retention period. You should see messages to this effect in the alert of the instance database log file.

Hemant K Collette

RMAN backup command gets failure

Hello;

Merry Christmas to all

It's the test database (10.2.0.1) on RHEL 4.8, Rman backup command was already.
I don't understand why I got the error? What was the reason?

RMAN > backup the database archivelog;
From backup 25 December 14
Current archived log
using the control file of the target instead of recovery catalog database
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 141 devtype = DISK
channel ORA_DISK_1: from archive newspaper backupset
channel ORA_DISK_1: specification of archive log backup set
archive log entry thread = 1 sequence 2 recid = 1 stamp = 867230647 =
archive log entry thread = 1 = 3 = 2 = 867233039 stamp recid sequence
archive log entry thread = 1 sequence 4 recid = 3 = 867233044 stamp =
archive log entry thread = 1 sequence 5 recid = 4 = 867233122 stamp =
archive log entry thread = 1 sequence = recid 6 = 5 = 867233128 stamp
archive log entry thread = 1 sequence = recid 7 = 6 = 867233214 stamp
archive log entry thread = 1 sequence 8 recid = 7 = 867233453 stamp =
archive log entry thread = 1 sequence 9 recid = 8 = 867233493 stamp =
archive log entry thread = 1 sequence 10 recid = 9 = 867233559 stamp =
channel ORA_DISK_1: starting piece 1 to December 25, 14
channel ORA_DISK_1: finished piece 1 to December 25, 14
piece handle=/home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/ORCL/backupset/2014_12_25/o1_mf_annnn_TAG20141225T101241_b9q5g4jo_.bkp tag = TAG20141225T101241 comment = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:16
Backup over at December 25, 14
From backup 25 December 14
using channel ORA_DISK_1
channel ORA_DISK_1: from full datafile backupset
channel ORA_DISK_1: specifying datafile (s) in backupset
input datafile fno = 00001 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/system01.dbf
input datafile fno = name=/home/oracle/oracle/product/10.2.0/oradata/orcl/sysaux01.dbf 00003
input datafile fno = 00005 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/example01.dbf
input datafile fno = name=/home/oracle/oracle/product/10.2.0/oradata/orcl/undotbs01.dbf 00002
input datafile fno = name=/home/oracle/oracle/product/10.2.0/oradata/orcl/users01.dbf 00004
channel ORA_DISK_1: starting piece 1 to December 25, 14
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of command thus backup archivelog to 2014/12/25 10:13:54
ORA-19502: write error on file ' / home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/ORCL/backupset/2014_12_25/o1_mf_nnndf_TAG20141225T101301_%u_.bkp ', blockno 8833 (blocksize = 8192)
ORA-27072: IO file error
Linux error: 2: no such file or directory
Additional information: 4
Additional information: 8833
Additional information: 348160
> > Physical directories are available
$ pwd
/Home/Oracle/Oracle/product/10.2.0/Db_1/flash_recovery_area/ORCL
[oracle@RAC1 ORCL] $ ls-l
total 12
drwxr-x - 3 oracle oinstall 4096 Dec 25 09:24 archivelog
drwxr-x - 3 oracle oinstall 4096 Dec 25 09:18 backupset
drwxr-x - 2 oracle oinstall 4096 Dec 24 17:16 onlinelog

ORA-19502: write error on file ' / home/oracle/oracle/flash_recovery_area/ORCL/backupset/2014_12_26/o1_mf_nnndf_TAG20141226T233412_%u_.bkp ', blockno 37505 (blocks ize = 8192)

I don't understand why is it taking over as "%u" rather than place a unique value for him. Is it the file with System FRA has enough space?

DF h/home/oracle/oracle/flash_recovery_area/ORCL/backupset.

Kind regards

Shivananda

RMAN backup error

Hello
I get an error when you try to run an Oracle database backup using a windows batch file that calls a settings file to execute RMAN commands. This is handled by the windows scheduler.
It's been in place for several months and worked fine until today.
Oracle Version - 11G 11.2.0.2.0
OS - Windows server 2008 R2
* Note *-I have changed for security reasons password and company information.
Here are the contents of the batch file:
echo: [email protected] > > \\CCCODS09\c$\Support\DB_Backup\Max.log
echo to: [email protected] > > \\CCCODS09\c$\Support\DB_Backup\Max.log
Echo subject: Max Backup log > > \\CCCODS09\c$\Support\DB_Backup\Max.log
RMAN @\\CCCODS09\c$\Support\DB_Backup\Max.txt > > \\CCCODS09\c$\Support\DB_Backup\Max.log
copy \\CCCODS09\c$\Support\DB_Backup\Max.log \\ccvmds51\c$\inetpub\mailroot\Pickup\email.txt
del \\CCCODS09\c$\Support\DB_Backup\Max.log
Here is the content of the Max.txt settings file:
connect sys/password@maxof target;
Run {}
backup as compressed backupset actual additional database tag 0 = = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-DATAFILE-%U.BKP';
backup as compressed backupset archivelog all delete tag all input = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-LOGFILE-%U.BKP';
backup as compressed backupset current controlfile tag = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-CONTROLFILE-%U.BKP";
}
"exit";
And here is the log file:
Recovery Manager: release 11.2.0.2.0 - Production on Mon Nov 17 05:30 2014
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN > Connect target *.
2 > run {}
3>           = backup as compressed backupset actual additional database tag 0 = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-DATAFILE-%U.BKP';
4>           backup as compressed backupset archivelog all delete tag all input = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-LOGFILE-%U.BKP';
5>           as a compressed backupset backup current controlfile tag = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-CONTROLFILE-%U.BKP ';
{6 >}
7 > exit;
connected to target database: MAX (DBID = 1234567890)
From backup 17 November 14
DBGSQL: TARGET > select nvl (max (al.recid), '0'), nvl (max (al.recid), 0) in : txtparmvalue,: parmvalue of al v$ archived_log where in al.status ('X', 'A') and al.is_recovery_dest_file = 'YES' and al.creator = "RMAN"
DBGSQL: SQLCODE = 1008
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the backup at 17/11/2014 05:30:16 command
RMAN-03014: implicit recovery catalog Resync failed
ORA-01008: not all variables
Complete recovery manager.
If you need more information please let me know.
Any help to fix this would be appreciated.
Thank you

Hello

This is considered to be a bug for 11.2.0.2 version.

Please see this document of MOS

ORA-01008: RMAN backup does not work with assorted errors 11.2.0.2 If cursor sharing is turned on (Doc ID 1472116.1)

Kind regards

Shivananda

It is advisable to use RMAN backups?

Hello
Currently in our production databases, they took only the export dumps in every day.
Is it advisable if we use RMAN backups?
Expdp/impdp we can import the dump and create a database in UAT as same as production.
If we opt for RMAN, is it possible to restore the backup as expdp to test if necessary?
Thanks in advance.

2

679362 wrote:

Hello

Currently in our production databases, they took only the export dumps in every day.

Is it advisable if we use RMAN backups?

As others have said or implied, it is MORE than advisable. I would declare it like this: If you want to stay independent as a DBA, it is mandatory. Without him, there will come a time where you will lose data. And which violates the Prime Directive for the DBA.

Expdp/impdp we can import the dump and create a database in UAT as same as production.

Which may or may not be very well to "Refresh" a test database, but it is not acceptable for the recovery of a database of lost output unless you accept BOTH of the following:

(1) potentially to recreate an 'empty' database to replace the lost production database.

1 a) potentially lose required components of database and/or configurations because you have forgotten/don't do them after the recreation of the empty database

(2) lose all data that has been added to the database once your instant export has been taken.

Do you think all the foregoing as an acceptable risk for your organization?

If we opt for RMAN, is it possible to restore the backup as expdp to test if necessary?

Definitely. Why wouldn't be? With rman for your primary backup strategy does not prevent you to export for any purpose you want to do with them.

I have 4 key production databases. For three of them, I update their counterparts in test with rman backups. For the fourth, I use exports.

Thanks in advance.

Why RMAN backup tablespace UNDO?

DB version: 11.2.0.4
OS: Oracle Linux 6.4
I found the following log RMAN backup Level0. Is the UNDO data in the tablespace, undo being saved really useful during the restoration?
If the UNDO data are not used for recovery, then these data impossible recreated duing ALTER DATABASE OPEN files just like the REDO Log files and Temp tablespace?
Enter a number of file datafile = name=+STG_DATA/ctgsprd/datafile/undotbs1_5.dbf 00024
ch04 chain: total departure from 1 to 30 - SEP-2014 00:59:18
channel ch10: finished piece 1 to 30 - SEP-2014 01:01:03
piece handle = STGlv0_23191_1_20140710 tag = comment STG_BK_LEVEL0_140709 = Version of the API 2.0, MMS Version 1.1.1.0
channel ch10: complete set of backups, time: 00:41:21
channel ch10: start the incremental level 0 datafile backup set
channel ch10: specification-datafile in the backup set (s)
Enter a number of file datafile = name=+STG_DATA/ctgsprd/datafile/undotbs2_2.dbf 00025
channel ch10: total departure from 1 to 30 - SEP-2014 01:01:03
channel ch11: finished piece 1 to 30 - SEP-2014 01:01:48
piece handle = STGlv0_23201_1_20140710 tag = comment STG_BK_LEVEL0_140709 = Version of the API 2.0, MMS Version 1.1.1.0
channel ch11: complete set of backups, time: 00:23:18
channel ch11: start the incremental level 0 datafile backup set
channel ch11: specification-datafile in the backup set (s)
Enter a number of file datafile = name=+STG_DATA/ctgsprd/datafile/undotbs2_3.dbf 00026

You must include the UNDO Tablespace in backup. You NEED restored and used in the database to recover.

At any time, there will be transactions not yet validated. The CANCELLATION option maintains this information. The open air after a recovery must be able to restore uncommitted operations and it must be able to read the CANCELLATION.

Hemant K Collette

Oracle 10.2.0.3 move an rman backup

We do a rman level 0 every weekend and level 1 every day. I want to keep away the last copies of weeks on another hard drive to save space. I guess that is done from rman? If so, can what commands I use?

jdaniel1127 wrote:

Currently have 10.2.0.3 on Windows Server 2008...

I have configured the channels as follows:

channel 1 device type disk format='f:\rman_backups\rman%u.bus' (this corresponds to the current files on g:\backups\)

Channel 2 device type disk format='f:\archive_logs\arc%s%r.%t' (this corresponds to the current archive on g:\oracle\ora10gtemp\database\)

I have 11 files in the backup (3 to 7/29, 1 for 7/30, 3 for 8/2, 2 for the 8/7 and 8/8 2) 8/7 and 8/8 are incremental...

I had 80 files from 2012 until today of the archive logs (10 M each...)

I'm moving all archive logs and files backup of G: that 652 g free to F: which has 4.6 free...

RMAN > backup backupset disk device;

From backup 8 August 14

allocated channel: ORA_DISK_1

channel ORA_DISK_1: sid = 146 devtype = DISK

entry count = 4 = 787850080 = July 5, 12 creation_time stamp backupset

channel ORA_DISK_1: starting piece 1 to August 8, 14

channel ORA_DISK_1: backup G:\ORACLE\ORA10GTEMP\DATABASE\C-4285664692-2012 piece

0705-00

room handle=F:\RMAN_BACKUPS\RMAN04NFB8R0_1_4.BUS comment = NONE

channel ORA_DISK_1: finished piece 1 to August 8, 14

channel ORA_DISK_1: complete set of backups, time: 00:00:03

entry count = 5 stamp = 787850384 = July 5, 12 creation_time backupset

channel ORA_DISK_1: starting piece 1 to August 8, 14

channel ORA_DISK_1: backup G:\BACKUPS\RMAN05NFB94G_1_1.BUS piece

RMAN-00571: ===========================================================

RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

RMAN-00571: ===========================================================

RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 11:40 08/08/2014:

17

ORA-19505: impossible to identify the file 'G:\BACKUPS\RMAN05NFB94G_1_1.BUS '.

ORA-27041: could not open the file

04002 - OSD: could not open the file

S/O-error: (OS 2) the system cannot find the file specified.

ORA-19600: input file is backup piece (G:\BACKUPS\RMAN05NFB94G_1_1.BUS)

ORA-19601: output file is backup piece (F:\RMAN_BACKUPS\RMAN05NFB94G_1_2.BUS)

It seems that your element of backup G:\BACKUPS\RMAN05NFB94G_1_1.BUS gone "bath of crowd". In other words, a person removed at the OS level... and so rman always think it is, but finds then this isn't.

You cannot change the format of RMAN backup

Hello!
I am trying to restore a backup of the database controlfiles in a new host solaris11 with RMAN in oracle 10 g. I have a solaris10 box where I installed database10g. As far as I know what I have to do is this:
> define the dbid = 718308982;
> startup nomount;
> set controlfile autobackup format of disc type of the device of ' / u01/app/oradata/ACBET/%F';
> Restore controlfile autobackup.
However when I try to change the format, nothing happens.
RMAN > set controlfile autobackup format of disc type of the device of ' / u01/app/oradata/ACBET/%F';
executing command: SET CONTROLFILE AUTOBACKUP FORMAT
RMAN > show all.
RMAN configuration parameters are:
CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
CONFIGURE BACKUP OPTIMIZATION # by default
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP # by default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # default < = same configuration by default...
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
And when I try to do the restore command I get the following error:
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 1626 devtype = DISK
field of recovery destination: / u01/app/oradata/ACBET/backup
name of database (or unique name of database) used for research: ACBET
channel ORA_DISK_1: no record not found in the recovery area
channel ORA_DISK_1: looking for autobackup day: 20131115
channel ORA_DISK_1: looking for autobackup day: 20131114
channel ORA_DISK_1: looking for autobackup day: 20131113
channel ORA_DISK_1: looking for autobackup day: 20131112
channel ORA_DISK_1: looking for autobackup day: 20131111
channel ORA_DISK_1: looking for autobackup day: 20131110
channel ORA_DISK_1: looking for autobackup day: 20131109
channel ORA_DISK_1: found no autobackup in 7 days
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the restore command at 11/15/2013 10:50:22
RMAN-06172: no autobackup couldn't find or handle specified is not a valid copy or a piece
It seems he's looking for in the right path of recovery of the area, but I don't know why it's a failure.
Thank you in advance,
Nock

Hello world

The problem with this restoration has been far from my knowledge. The real problem was that the backup files that they sent were made in a different boutien than the one I used in the new host. For the sake of those who find this post in the future, you can not use rman to make. Until the date of this post, he must either use a simple import/export (with pump data if you like) or using transportable tablespaces to move a database between the hosts with another platform.

Thanks for all the help.

Nock

Follow-up of RMAN backup job details

Similar Questions

Notification by e-mail for the owner

Maybe you are looking for