RMAN backup job showing problems

We have scheduled RMAN backup jobs for Oracle full backups & incremental level 0 & level 1 backup. Among the recent status for jobs, I have found problems for incremental 0 backup for 2nd Dec ’13 and incremental 1 backup for 6th Dec’13. I would elaborate as below:
For 2nd Dec ’13:
The messages showing are-
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 12/02/2013 01:02:41
ORA-19502: write error on file "/orabackup/rman/snlprod/data_files/7voqfb9a_1_1", block number 763264 (block size=8192)
ORA-27072: File I/O error
For 6th Dec’13:
The messages showing are-
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 12/06/2013 01:12:00
ORA-19502: write error on file "/orabackup/rman/snlprod/data_files/8moqpt4r_1_1", block number 1135616 (block size=8192)
ORA-27072: File I/O error
Request you to please help me with the reason for these error messages.
I hope, my question is clear.
Please revert with the reply to my query.
Regards

Hi,
You should look at your systems logs (/var/log/messages on linux, errpt on AIX) to see which error you have exactly at the OS level.
As Sybrand_b said, it is an error while writing a block on disk, so either a filesystem full or a corrupted block on disk.
Do you have additional error message like follows?
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 112) There is not enough space on the disk
Regards,
Joseph

Similar Messages

RMAN backup job status not showing in OEM

Hi, I have created an RMAN backup job and scheduled it through OEM to run daily. The first run of this backup job completed today - however I do not see any entry for the job in OEM through SERVER - ORACLE SCHEDULER - JOBS
A lot of scheduler jobs are listed but not my backup job.
Has anyone else experienced this ?

Duplicate post. Please do not add to this thread.

Tracking RMAN Backup job details

Version:11.2.0.3/Solaris 11
To track RMAN backup job details , what dictionary view/dyn.performance view do you use ?
In our shop , we use incrementally updated backup (incremental merge). To find the details of previous RMAN Jobs, I tried using
v$rman_status
and
v$rman_backup_job_details
But the details provided by these 2 views don't match. For example, on 26th of June 2013, there was an Incremental backup and an archivelog backup. As per 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 info on archive log bkp though.
The start_time and end_time provided by both of these views don't math either !
col starttime format a25
col endtime format a25
select status, object_type, to_char(start_time,'dd/MON/yyyy:hh:mi:ss') as starttime,
to_char(end_time,'dd/MON/yyyy:hh:mi:ss') as endtime ,
to_number(end_time-start_time)*24*60 duration_minutes
from sys.v$rman_status where start_time > trunc(sysdate) - 20 and operation = 'BACKUP'
order by end_time desc;
STATUS                  OBJECT_TYPE   STARTTIME                 ENDTIME                   DURATION_MINUTES
FAILED                  ARCHIVELOG    07/JUN/2013:08:47:44
COMPLETED               ARCHIVELOG    26/JUN/2013:06:49:16      26/JUN/2013:07:36:14            46.9666667
COMPLETED               DB INCR       26/JUN/2013:06:33:18      26/JUN/2013:06:49:16            15.9666667
COMPLETED               ARCHIVELOG    25/JUN/2013:06:50:55      25/JUN/2013:07:58:01                  67.1
COMPLETED               DB INCR       25/JUN/2013:06:25:06      25/JUN/2013:06:50:55            25.8166667
COMPLETED               ARCHIVELOG    24/JUN/2013:06:15:42      24/JUN/2013:07:07:54                  52.2
COMPLETED               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
COMPLETED               DB INCR       23/JUN/2013:09:40:27      23/JUN/2013:09:47:48                  7.35
COMPLETED               ARCHIVELOG    22/JUN/2013:07:23:18      22/JUN/2013:07:41:29            18.1833333
COMPLETED               DB INCR       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
COMPLETED               DB INCR       21/JUN/2013:06:39:35      21/JUN/2013:07:30:33            50.9666667
COMPLETED               ARCHIVELOG    20/JUN/2013:07:35:54      20/JUN/2013:09:25:03                109.15
COMPLETED               DB INCR       20/JUN/2013:06:55:08      20/JUN/2013:07:35:54            40.7666667
COMPLETED               ARCHIVELOG    19/JUN/2013:07:20:10      19/JUN/2013:08:27:28                  67.3
COMPLETED               DB INCR       19/JUN/2013:07:00:02      19/JUN/2013:07:20:10            20.1333333
COMPLETED               ARCHIVELOG    18/JUN/2013:07:27:30      18/JUN/2013:09:19:50            112.333333
COMPLETED               DB INCR       18/JUN/2013:07:02:09      18/JUN/2013:07:27:30                 25.35
COMPLETED               ARCHIVELOG    17/JUN/2013:07:42:20      17/JUN/2013:08:40:29                 58.15
COMPLETED               DB INCR       17/JUN/2013:07:22:29      17/JUN/2013:07:42:20                 19.85
COMPLETED               ARCHIVELOG    17/JUN/2013:06:28:16      17/JUN/2013:07:42:44            74.4666667
COMPLETED               DB INCR       17/JUN/2013:01:57:49      17/JUN/2013:06:28:11            270.366667
COMPLETED               ARCHIVELOG    16/JUN/2013:02:18:02      16/JUN/2013:04:22:26                 124.4
COMPLETED               DB INCR       16/JUN/2013:01:48:18      16/JUN/2013:02:18:02            29.7333333
COMPLETED               ARCHIVELOG    14/JUN/2013:07:27:44      14/JUN/2013:08:40:53                 73.15
COMPLETED               DB INCR       14/JUN/2013:07:01:19      14/JUN/2013:07:27:43                  26.4
COMPLETED               ARCHIVELOG    13/JUN/2013:06:56:13      13/JUN/2013:07:47:50            51.6166667
COMPLETED               DB INCR       13/JUN/2013:06:42:11      13/JUN/2013:06:56:13            14.0333333
COMPLETED               ARCHIVELOG    12/JUN/2013:07:12:43      12/JUN/2013:08:12:10                 59.45
COMPLETED               DB INCR       12/JUN/2013:06:45:51      12/JUN/2013:07:12:43            26.8666667
COMPLETED               ARCHIVELOG    11/JUN/2013:07:21:36      11/JUN/2013:08:46:11            84.5833333
COMPLETED               DB INCR       11/JUN/2013:06:52:29      11/JUN/2013:07:21:36            29.1166667
COMPLETED               ARCHIVELOG    10/JUN/2013:07:04:49      10/JUN/2013:07:55:15            50.4333333
COMPLETED               DB INCR       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
COMPLETED               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
COMPLETED               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
COMPLETED               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 rows selected.
-- Output of v$rman_backup_job_details
select status, 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 endtime,
to_number(end_time-start_time)*24*60 duration_minutes
From v$rman_backup_job_details
where start_time > trunc(sysdate) - 20
order by end_time desc;
STATUS                  INPUT_TYPE    STARTTIME           ENDTIME             DURATION_MINUTES
FAILED                  ARCHIVELOG    07/06/2013:08:47:44
COMPLETED               DB INCR       26/06/2013:06:00:09 26/06/2013:07:36:14       96.0833333
COMPLETED               DB INCR       25/06/2013:06:00:08 25/06/2013:07:58:01       117.883333
COMPLETED               DB INCR       24/06/2013:06:00:09 24/06/2013:07:07:54            67.75
COMPLETED               DB INCR       23/06/2013:08:07:56 23/06/2013:10:01:19       113.383333
COMPLETED               DB INCR       22/06/2013:06:00:10 22/06/2013:07:41:29       101.316667
COMPLETED               DB INCR       21/06/2013:06:00:12 21/06/2013:09:05:50       185.633333
COMPLETED               DB INCR       20/06/2013:06:00:12 20/06/2013:09:25:03           204.85
COMPLETED               DB INCR       19/06/2013:06:00:11 19/06/2013:08:27:28       147.283333
COMPLETED               DB INCR       18/06/2013:06:00:16 18/06/2013:09:19:50       199.566667
COMPLETED               DB INCR       17/06/2013:06:00:13 17/06/2013:08:40:29       160.266667
COMPLETED               DB INCR       16/06/2013:06:04:02 17/06/2013:07:42:44            818.7
COMPLETED               DB INCR       15/06/2013:06:05:12 16/06/2013:04:22:26       617.233333
COMPLETED               DB INCR       14/06/2013:06:00:09 14/06/2013:08:40:53       160.733333
COMPLETED               DB INCR       13/06/2013:06:00:09 13/06/2013:07:47:50       107.683333
COMPLETED               DB INCR       12/06/2013:06:00:10 12/06/2013:08:12:10              132
COMPLETED               DB INCR       11/06/2013:06:00:17 11/06/2013:08:46:11            165.9
COMPLETED               DB INCR       10/06/2013:06:00:14 10/06/2013:07:55:15       115.016667
COMPLETED               DB INCR       09/06/2013:06:00:10 09/06/2013:09:04:10              184
COMPLETED               DB INCR       08/06/2013:06:00:09 08/06/2013:08:33:58       153.816667
COMPLETED               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 rows selected.

When I run an full/incremental backup with archivelog it only shows as one job in v$rman_backup_job_details. Only if I explicitly run just a backup archivelog all in RMAN does it show up separately as an ARCHIVELOG backup in v$rman_backup_job_details.
rman_status shows the individual parts of the jobs. For example for a full backup it shows the db backup and the archivelog backup.
The start and end time in rman_status should match up with $rman_backup_job_details.
Lets take the 25th as an example:
In man_backup_job_details
STATUS                  INPUT_TYPE    STARTTIME           ENDTIME             DURATION_MINUTES
COMPLETED               DB INCR       25/06/2013:06:00:08 25/06/2013:07:58:01       117.883333
In v$man_status:
STATUS                  OBJECT_TYPE   STARTTIME                 ENDTIME                   DURATION_MINUTES
COMPLETED               ARCHIVELOG    25/JUN/2013:06:50:55      25/JUN/2013:07:58:01                  67.1
COMPLETED               DB INCR       25/JUN/2013:06:25:06      25/JUN/2013:06:50:55            25.8166667
You need to view your logfiles to see what rman was doing between 6:00:08 when the job started and 06:25:06 when the incremental backup started.
You can see that the end time is the same in both views.
Not easy to explain but I hope that helps.

Which views have RMAN backup jobs information?

Hi there,
I use EM to schedule the db backup using RMAN.
I can view the jobs in the EM.
But I can not find out which views have RMAN backup jobs information in sqlplus.
like dba_scheduler_jobs.
Your advice will be appreciated.
Thanks,
SZ

Hi,
V$RMAN_STATUS - Shows the success/failure status of all recently completed RMAN jobs.
V$RMAN_OUTPUT
Displays messages reported by an RMAN job in progress
If you want to monitor then go the following :-
Monitoring RMAN Job Progress :- view V$SESSION_LONGOPS.
first Step :-
Before starting the job, create a script file (called, for this example, longops) containing the following SQL statement:
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
After connecting to the target database and, if desired, the recovery catalog database, start an RMAN job. For example, enter:
RESTORE DATABASE;
While the job is running, start SQL*Plus connected to the target database, and execute the longops script to check the progress of the RMAN job. If you repeat the query while the restore progresses, then you see output such as the following:
SQL> @longops
SID SERIAL# CONTEXT SOFAR TOTALWORK %_COMPLETE
8 19 1 10377 36617 28.34
SQL> @longops
SID SERIAL# CONTEXT SOFAR TOTALWORK % COMPLETE
8 19 1 21513 36617 58.75
Cheers
Pavan Kumar N

Automating RMAN backup jobs in Windows

First off: THANK YOU to Ahmer Mansoor, EdStevens, and jgarry for helping me get my RMAN backup jobs up and running in this thread: Oracle 10g on Windows Server off-line database backup - a few questions You were a big help and provided very valuable advice!
Now I'd like to automate it. My plan is below - please let me know what you think. The four files will be run in this order.
ShutdownDB1.bat
set oracle_sid = pldg
C:\oracle\product\10.2.0\bin\sqlplus.exe /nolog @c:\oraclebackup\shutdowndb2.sql
ShutdownDB2.sql (called by the previous batch file)
set echo on
spool C:\oraclebackup\ShutdownDB.log
connect /@pledgemaker as sysdba
shutdown immediate
spool off
exit<Here there will be a thirty minute window or so while I XCOPY the Oracle Inventory and Oracle Home directories. I'll only do this about once a week or so.>
RMANBackup1.bat
set oracle_sid=pldg
C:\oracle\product\10.2.0\BIN\rman.exe target / cmdfile = 'c:\oraclebackup\rmanbackup2.scr' log = 'c:\oraclebackup\RMANBackup.log'
RMANBackup2.scr (called by the previous batch file)
startup mount
backup database
alter database open
exit

Ahmer Mansoor wrote:
why shutting down from sqlplus ?
You can include shutdown immediate in the RMANBackup2.scr file and remove the ShutdownDB1.bat and ShutdownDB2.sql.Okay, so how about just this?
RMANBackup1.bat
set oracle_sid=pldg
set echo off
C:\oracle\product\10.2.0\BIN\rman.exe target / cmdfile = 'c:\oraclebackup\rmanbackup2.bat' log = 'c:\oraclebackup\RMANBackup.log'
RMANBackup2.bat
RUN {
     shutdown immediate;
     startup mount;
     backup database;
     alter database open;
     exit;> }
exit;

Speeding up RMAN backup job

Hi,
Is there anyway to increase the speed of the RMAN backup job where the job is already started running?
Regards,
007

007 wrote:
Hi CKPT,
I am using Oracle Database 11g(11.2.0.1).
Regards,
0071) If your backup is not streaming to tape, then make sure that the RATE parameter is not set on the
ALLOCATE CHANNEL or CONFIGURE CHANNEL commands.
2) Check init.ora/spfile parameters and confirm if async IO is configured:
DISK_ASYNCH_IO=TRUE (or defaulted): native async io is assumed to be in use
DISK_ASYNCH_IO=FALSE and DBWR_IO_SLAVES > 1: async io is simulated with disk IO slaves
BACKUP_TAPE_IO_SLAVES=TRUE: tape IO slave is used
DB_WRITER_PROCESSES - if >1 this is NOT compatible with DBWR_IO_SLAVES > 1
3) If You Fail to Allocate Shared Memory, Set LARGE_POOL_SIZE
LARGE_POOL_SIZE = number_of_allocated_channels *
(16 MB + ( 4 * size_of_tape_buffer ) )
4) Allocate 4 channels if backing up to disks, increase it further if required.
5) Use rman backup operation during off business hours, to give more resource to rman jobs.

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 job fails after changing sys, system passwords

Hello Oracle community,
11.1g
After we changed the passwords for sys, system and sysman the backup jobs fails. this is my error log:
Recovery Manager: Release 11.1.0.7.0 - Production on Mo Aug 30 11:16:29 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-12532: TNS: Ungültiges Argument
RMAN>
Echo einstellen ein
RMAN> set command id to 'BACKUP_MEGALON.INT_083010111617';
Befehl wird ausgeführt: SET COMMAND ID
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Fehler bei set Befehl auf 08/30/2010 11:16:29
RMAN-06171: Nicht bei Zieldatenbank angemeldet
RMAN> backup device type disk tag 'BACKUP_MEGALON.INT_083010111617' database;
Starten backup um 30.08.10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Fehler bei backup Befehl auf 08/30/2010 11:16:29
RMAN-06171: Nicht bei Zieldatenbank angemeldet
RMAN> backup device type disk tag 'BACKUP_MEGALON.INT_083010111617' archivelog all not backed up;
Starten backup um 30.08.10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: Fehler bei backup Befehl auf 08/30/2010 11:16:29
RMAN-06171: Nicht bei Zieldatenbank angemeldet
RMAN> exit;
Recovery Manager abgeschlossen.
Ikrischer

Hello Tychos,
I am able to make a sqlplus connection, but your hint send me in the correct direction. I had a special character "@" in the password and I think that was the reason for my problems with RMAN.
Ikrischer

Rman backup jobs does not start automatically

I have the next question:
When I run such script in RMan:
RUN
ALLOCATE CHANNEL c1 DEVICE TYPE sbt;
SEND 'OB_MEDIA_FAMILY mf_rman';
BACKUP archivelog all;
It creates job on OSB server:
ob> lsj
Job ID Sched time Contents State
oracle10/6 none database cbs3 (dbid=2397799862) processed; Oracle job(s) scheduled
oracle10/6.1 none archivelog backup retryable at 2010/10/01.23:05 ("lsjob --log oracle10/6.1" for details)
But it doesn't statrt immediatelly at the same time, so I has to run the job manually:
ob> runj -n oracle10/6.1 -d Drive2
ob> lsj
Job ID Sched time Contents State
oracle10/6 none database cbs3 (dbid=2397799862) processed; Oracle job(s) scheduled
oracle10/6.1 none archivelog backup running since 2010/10/01.17:10
How to make Rman start backup job at once?
Edited by: OraSun on 01.10.2010 4:44

If you have created a database storage selector, you don't need to include media manager parameters in the RMAN script. You would include media manager parameters in script, if you want to override the database storage selector settings. For example, in the database storage selector you have indicated that the media family is mf_rman...OSB will automatically use that media family based on database storage selector settings. Per the RMAN script, you want this backup operation to use mf_rman...since database storage selector already defines this, you don't need to include it in the RMAN script. If your database storage selector defines use of mf_rman media family but you want a particular backup to use "foo" media family, then you would include that parameter in your script so it would override the database storage selector.

How to ensure the rman backup is successful?

Hi,
we have scheduled rman backup jobs.
1. But how do we ensure all the rman backups are successful?
2. if the rman writes directly to tape, how do we ensure all tape backups are successful?
thanks
andrew

But what is incremental merge, couldn't find in the 10g manual?check it out on http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmquick.htm#BRADV89354
do you use image backup in real production environment?Of course. We have a standard to to use image copies that way.
what do you suggest to do with rman normal way of backup or go for image backup?Depends on your specific situation. Like anything else, I prefer to provide some rationale on the recommendation.
Image Copies with Incremental Merge
Pros:
(1) one one full backup taken ever; no need to take another full backup
(2) the restore time is the same, regardless of the day of the week the db failed
(3) every day the incremental merge's success means the backup was good - an automatic validation
(4) it allows you to quickly switch to copy, rather than restore
Cons:
(1) Space requirement is more (since it's a bit to bit copy)
(2) can't do a point in time recovery from the disk alone
(3) can't go to the tape directly; must be a disk based backup.
Backupsets with Incremental Backup
Pros:
(1) space requirement is lower (since only never-used blocks are not copied)
(2) point in time recovery is possible
(3) direct backup to tape possible (no need for disk backup)
Cons:
(1) restore time varies depending on the day of the week the db failed
(2) you have to take a full backup regularly, perhaps once a week
(3) no validation unless you use validate backupset (takes resources)
So, as you can see, there are pros and cons to each approach. You have to decide for yourself which one weighs more (or less) to come to a conclusion.
Hope this helps.
Arup Nanda

Date of execution of rMAN BACKUP

Hi,
can you explaine me please :
I launched a RMAN backup job from OEM (9.2.0). When I verify the output I see date of 2005 :
RMAN>
connected to target database: OEADP (DBID=24391298)
RMAN>
connected to recovery catalog database
RMAN>
RMAN> run {
2> allocate channel Channel1 type disk format 'e:\oracle\rman\oeadb\bck_OEADB_LV0_%u_%p_%c';
3> backup incremental level 0
4> ( database include current controlfile );
5>
6> backup ( archivelog all delete input );
7>
8> }
allocated channel: Channel1
channel Channel1: sid=14 devtype=DISK
Starting backup at DEC 18 2005 00:00:02
channel Channel1: starting incremental level 0 datafile backupset
channel Channel1: specifying datafile(s) in backupset
I'm astonnished. On OMS server and target machine system date is 12/14/2006.
Any way the backup is not done and the job is failed but in output every thing is OK unless date :
input datafile fno=00005 name=E:\ORADATA\OEADB\TOOLS01.DBF
channel Channel1: starting piece 1 at DEC 18 2005 00:00:03
channel Channel1: finished piece 1 at DEC 18 2005 00:08:08
piece handle=E:\ORACLE\RMAN\OEADB\BCK_OEADB_LV0_1FH6IHO3_1_1 comment=NONE
channel Channel1: backup set complete, elapsed time: 00:08:05
Finished backup at DEC 18 2005 00:08:08
Starting backup at DEC 18 2005 00:08:09
current log archived
Many thanks.

thank you. I have already checked. It is OK. I rediscovered the noad again. Now when I submit a job there is no output.
Regards.

Duration of RMAN Backup

Hi,
I am using Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit on Solaris SPARC.
I weekly take level 0 backup on sunday, and then incremental level 1 backup each day in the week and archive log backups daily every after 3 hours.
I want to know that how much time my level 0 backup on last sunday (i.e. 17april) took, how much incremental level 1 on 19april took, and how much time archivelog took during the date 20 april.
I dont have log files of those RMAN backups so unable to get that info from the log files. I would appreciate if you share any query.
would you please guide in that regard?
regards

select
sid,
start_time,
totalwork
sofar,
(sofar/totalwork) * 100 pct_done
from
   v$session_longops
where
   totalwork > sofar
AND
   opname NOT LIKE '%aggregate%'
AND
   opname like 'RMAN%';
select
   sid,
   spid,
   client_info,
   event,
   seconds_in_wait,
   p1, p2, p3
from
   v$process p,
   v$session s
where
   p.addr = s.paddr
and
   client_info like 'rman channel=%';
Yousef Rifai has published this RMAN monitoring script, quite handy when you need to monitor the status of a long running RMAN backup job:
REM RMAN Progress
alter session set nls_date_format='dd/mm/yy hh24:mi:ss'
select SID, START_TIME,TOTALWORK, sofar, (sofar/totalwork) * 100 done,
sysdate + TIME_REMAINING/3600/24 end_at
from v$session_longops
where totalwork > sofar
AND opname NOT LIKE '%aggregate%'
AND opname like 'RMAN%'
REM RMAN wiats
set lines 120
column sid format 9999
column spid format 99999
column client_info format a25
column event format a30
column secs format 9999
SELECT SID, SPID, CLIENT_INFO, event, seconds_in_wait secs, p1, p2, p3
FROM V$PROCESS p, V$SESSION s
WHERE p.ADDR = s.PADDR
and CLIENT_INFO like 'rman channel=%'
/reference and source:-
http://www.dba-oracle.com/t_monitor_rman_script.htm

Error: Sheduled Backup Job Problem

Dear all.
I've been getting a problem with a scheduled backup job through OEM since yesterday which I'm not able to find out why as it was working fine. When I access OEM I can see that I have a problem execution and when I investigate why it says "Unable to perform the backup because the database is closed". But my db is open for sure and I'm able to execute the backup from RMAN command line normally. I shut my db down and started it up again but didn't work. Does anybody know why this is happening?
OS: Oracle Enterprise Linux 5
DB: Oracle Database 10g
Thanks a lot.

**** Job Definition ****
Status: Scheduled
Scheduled: 09-Jun-2009 20:00:00 o'clock GMT-03:00
Repeating: Daily beginning 09-Jun-2009 20:00:00 (because I changed to do tests)
Type: Database Backup
Owner: SYS
Description: Whole Database Backup
Database Connect String: (DESCRIPTION=(ADDRESS_LIST=(ADDR...
Version 10g or higher: YES
Backup Strategy: advanced
Offline Backup: NO
Blackout: NO
Database Name: ORCL
**** Script ****
$rman_script="backup incremental level 0 cumulative device type disk filesperset = 3 tag '%TAG' database;
backup device type disk filesperset = 3 tag '%TAG' archivelog all not backed up;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
&br_save_agent_env();
&br_prebackup($l_db_connect_string, $l_is_cold_backup, $l_use_rcvcat, $l_db_10_or_higher, $l_backup_strategy, "TRUE");
my $result = &br_backup();
exit($result);

Block corruption problem in alert and rman/dbv no show errors

Hello, I'm new in Oracle's world. I have one problem with Oracle 10.2.0.4 (RHEL 5.6) x64. Archive redo-log enable
In the alert.log, three days ago show (the server have kernel panic & rebooted):
Mon Sep 24 18:18:17 2012
Hex dump of (file 17, block 669888) in trace file xxxxxxxxxx.trc
Corrupt block relative dba: 0x044a38c0 (file 17, block 669888)
Bad check value found during buffer read
Data in bad block:
type: 6 format: 2 rdba: 0x044a38c0
last change scn: 0x0000.14eb5309 seq: 0x1 flg: 0x04
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x53090601
check value in block header: 0x6ea3
computed block checksum: 0x2
Reread of rdba: 0x044a38c0 (file 17, block 669888) found same corrupted data
Mon Sep 24 18:18:19 2012
Corrupt Block Found
TSN = 23, TSNAME = TABLE_TSD1
RFN = 17, BLK = 669888, RDBA = 71973056
OBJN = 86908, OBJD = 86908, OBJECT = SYS_C0040110, SUBOBJECT =
SEGMENT OWNER = SCHEMA1, SEGMENT TYPE = Index Segment
Yesterday, we detected this error because SQL don't execute.
The error repeat 47times and there is 6 different file-block combination (4 index of schemas, 1 of sys and ¡2 tables!)
First, I launched expdp and exp of the one problematic schema. The export was fine, no errors while exporting, but in the alert.log show one block corruption. Should exp and expd show error and stop?
Next, I used dbv and verify all dbfs. Only show 2 blocks error in two datafiles (indexes).
Next, I used RMAN:
A) check database: no error.
B) validate database: error in two blocks (logical error) and different from the 6 in alert.log. This two blocks are indexes.
I re-create this two indexes. When i re-create, the block error disappear (not inmediate, suppose that disappear when block was rewrite). Now dbv and rman show no error.
I have read one note about types of error, other about procedures if db is in archivelog/noarchivelog. Also if object is index or table. But I find anything about auto-repair corrupt blocks in Oracle or why now the 6 block error are solved. I don't know if two tables with two block corrupt lost rows or not.
Appreciate any help.
Regards

Hello Fran. Result of query before rebuild problematic INDEXES:
SQL> select * from V$database_block_corruption;
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
3 98857 1 390928740 LOGICAL
9 48632 1 390325900 LOGICAL
When I ran RMAN first time to check blocks, it filled V$database_block_corruption with two bad blocks. Different from the 6 errors from alert.:
RMAN> backup validate check logical database;
Error backing up file 9, block 48632: logical corruption
Error backing up file 3, block 98857: logical corruption
I extracted index name from each block and I re-created it. Also, I created a temporary table in tablespace's datafile to fill blocks empty. Problem solved. Rman / dbv show no error.
I'm searching for similar experiences and found: Re: Data in bad block
First 6 bad checksum errors in alert.log disappear with any visible problem?
Can I sure that DB is fine if RMAN and DBV show no errors?
Thank you very much
Edited by: user7755509 on 27-sep-2012 5:43

Backup jobs and password changing problem

Hi
I have created few rman job in my db (11.2) to backup database.
I my company i have to change all system passwords (os - oracle, system, syman, etc...) every 90 days.
When i changing password for user who created backup jobs, this jobs stop working.
I,ve got "Invalid username and/or passworderror writing input to command" error.
Of course after changing passords i always setup "Preferred Credentials" but that dosn't help.
What am i doing wrog? What am i missing ?
Please advice.

If you use Preferred Credentials to authorize a Job, it will use the current credentials on the moment it is dispatched for execution.
This means that in case passwords changes, you just need to modify you preferred credentials
This is something you can do using EMCLI (command line interface) in a script for instance (or just use the GUI to modify)
checkout:
Oracle® Enterprise Manager Command Line Interface
11g Release 1 (11.1)
http://download.oracle.com/docs/cd/E11857_01/em.111/e16185/toc.htm
regards
Rob
http://oemgc.wordpress.com

RMAN backup job showing problems

Similar Messages

Maybe you are looking for