Backup job status: Skipped?

hi, does anyone know what does that mean?
I found a backup job schedule day missing, checked the job, it says "Skipped", where could i check what happened, no additional info found.
Simon

At a guess the backup window closed before the backup started.
Was this status reported in your backup software?
Or, if the message was reported in the Oracle scheduler it was probably because it was delayed past it's start time by more than the specified threshold.
Message was edited by:
DBA in Scotland

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.

How to get status of a backup job

Hello everybody,
I scheduled our daily RMAN backup using the DBMS_SCHEDULER package. The DB job calls an external batch file which in turns calls rman's executable and passes it a command file containing the actual backup script. Similar to what's described here:
Problems with automated RMAN Backup in Oracle 11GR1 with DBMS_SCHEDULER
The backup works perfectly. The problem is that if I intentially corrupt the command file (simulating a backup failure) so that the backup fails, and then query the dba_scheduler_job_log view, I always get a status of SUCCEEDED. Regardless of the actual backup outcome, the job seems to always succeed. That's a problem for me, because I'd like to set up a user defined metric which would check the status of the job in dba_scheduler_job_log. If the job wasn't successfully executed, a mail would be sent.
Does anybody know why the job doesn't fail when it should? I also tried to execute the failing script manually and then checked the %ERRORLEVEL% environment variable. It has a value of 1, meaning error.
Btw, I know that if I schedule the same backup with Enterprise Manager's job system (instead of DBMS_SCHEDULER), the backup failure is correctly reported (and the metric works). The issue with EM is its limited scheduling capability - I do a full backup on Sunday, a cummulative incremental backup on Wednesday and all the other days a differential incremental backup. Since now I haven't found a way to define a schedule with an appropriate repeating interval. The only solution I figured out is to have 7 jobs, one for each day of the week....
Thanks in advance for any answers,
Jure

Hi,
@alanm: I completely forgot checking that view :-) Using it is a solution, but I should probably set up a job chain to handle that (run backup & chack status in the view afterwards)....if there isn't be another solution, maye I'll do that. But then, maybe using 7 EM jobs is a simpler solution.
@RnR: I tried to execute the batch file manually from the command line like that:
C:\>echo %errorlevel%
0
C:\>rman target / cmdfile=backup_full.rcv
Recovery Manager: Release 10.2.0.3.0 - Production on Sre Jul 2 09:46:37 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: TESTDB (DBID=2890535676)
RMAN> RUN
2> {
3> aa;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "allocate, alter, backup, beginline,
blockrecover, catalog, change, copy, convert, crosscheck, configure, duplicate, debug, delete, exec
ute, endinline, flashback, host, mount, open, plsql, recover, release, replicate, report, restore, r
esync, set, setlimit, sql, switch, startup, shutdown, send, show, transport, validate"
RMAN-01008: the bad identifier was: aa
RMAN-01007: at line 3 column 1 file: backup_full.rcv
C:\>echo %errorlevel%
1
So the if the script fails, I get an errorlevel of 1. Is it possible that the status isn't propagated back to the Oracle job?
@alanm: I'm already appending to the log, but I don't see how can that affect the outcome status of the job?
Thanks for your answers.
Regards,
Jure

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);

Error in Backup job scheduling in DB13

Hi All
Backup job scheduled in DB13 kicks error ,I am using Oracle as database and ERP6.0
database and application are on diffrent servers.Before it was working fine,I didn't changed any password
I can run backupjob sucessfully directly from BRtools on database server.Please provide any hint
Job started
Step 001 started (program RSDBAJOB, variant &0000000000060, user )
No application server found on database host - rsh/gateway will be used
Execute logical command BRBACKUP On host DLcSapOraG08
Parameters:-u / -jid INLOG20090120204230 -c force -t online -m incr -p initerd.sap -w use_dbv -a -c force -p in
iterd.sap -cds -w use_rmv
BR0051I BRBACKUP 7.00 (31)
BR0128I Option 'use_dbv' ignored for 'incr'
BR0055I Start of database backup: bdztcorv.ind 2009-01-20 20.42.31
BR0484I BRBACKUP log file: D:\oracle\ERD\sapbackup\bdztcorv.ind
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance ERD failed
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance ERD failed
BR0056I End of database backup: bdztcorv.ind 2009-01-20 20.42.32
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.32
BR0291I BRARCHIVE will be started with options '-U -jid INLOG20090120204230 -d disk -c force -p initerd.sap -cds -w use_rmv'
BR0002I BRARCHIVE 7.00 (31)
BR0181E Option '-cds' not supported for 'disk'
BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
BR0301W SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
BR0310W Connect to database instance ERD failed
BR0007I End of offline redo log processing: adztcorw.log 2009-01-20 20.42.32
BR0280I BRARCHIVE time stamp: 2009-01-20 20.42.33
BR0005I BRARCHIVE terminated with errors
BR0280I BRBACKUP time stamp: 2009-01-20 20.42.33
BR0292I Execution of BRARCHIVE finished with return code 3
External program terminated with exit code 3
BRBACKUP returned error status E
Job finished

Hi,
not sure if the recommendations given will address this issue.
You are getting this error:
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-01017: invalid username/password; logon denied
the log file indicates:
> No application server found on database host - rsh/gateway will be used
This indicated that the user that is connecting from the AS to the DB server is not properly configured to perform the DB tasks on it.
So, first question would be to know if you have configured a gateway on the DB server and how, or if you are using remote shell.
Second question, you can do backups on the DB server.
> I can run backupjob sucessfully directly from BRtools on database server
How did you run exactly the backup job (what is the exact command line, what is the exact OS user that executed it)?
What is the OS of the DB server?
I have reread your post, your OS is windows therefore you fall in the "typical" error in Windows.
You have executed your backup as <sid>ADM and it works. Unfortunatelly, in windows, SAP is exectuted by SAPSERVICE<sid>, and this is the user who should be connecting to your DB server, and this is the user who cannot execute the backup.
The fact that you can run the backup with <sid>ADM in Windows does not means that you have SAPService<sid> properly configured.
For the error (see before) I think your ops$ user for this user is not properly configured in the DB server. take a look at the note mentioned by KT and pay attention to the SAPSERVICE<sid> configuration
Edited by: Fidel Vales on Jan 24, 2009 12:45 AM

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.

Online Backup Failed (Status Its shows Scheduling failed)

Dear all ,
OS AIX , DB Oracle , SAP ECC6.0 , Tivoli Storage Manager
Scheduled Online Backups are failed (Backups are fired through DB13)
JOB Status : Scheduling failed
Job Log:
02.12.2009     17:00:01     Job started
02.12.2009     17:00:01     Step 001 started (program RSDBAJOB, variant &0000000000657, user ID BASIS)
02.12.2009     17:00:01     No application server found on database host - rsh/gateway will be used
02.12.2009     17:00:01     Execute logical command BRBACKUP On host PRODORADB
02.12.2009     17:00:01     Parameters:-u / -jid ALLOG20091201170000 -c force -t online -m all -p initIRPoffsite.sap -a -c force -p initIRP
02.12.2009     17:00:01     offsite.sap -cds
02.12.2009     17:01:01     SXPG_STEP_XPG_START: is_local_host: rc = 403
02.12.2009     17:01:01     SXPG_STEP_XPG_START: host = PRODORADB
02.12.2009     17:01:01     SXPG_STEP_XPG_START: is_local_r3_host: rc = 802
02.12.2009     17:01:01     SXPG_STEP_XPG_START: RFC_TCPIP_CONNECTION_OPEN: rc = 1003
02.12.2009     17:01:01     SXPG_STEP_COMMAND_START: SXPG_STEP_XPG_START returned: 1.003
02.12.2009     17:01:01     SXPG_COMMAND_EXECUTE(LONG)
02.12.2009     17:01:01     <timestamp> = 20091202170101
02.12.2009     17:01:01     COMMANDNAME = BRBACKUP
02.12.2009     17:01:01     ADDITIONAL_PARAMETERS =
02.12.2009     17:01:01     -u / -jid ALLOG20091201170000 -c force -t online -
02.12.2009     17:01:01     m all -p initIRPoffsite.sap -a -c force -p initIRP
02.12.2009     17:01:01     offsite.sap -cds
02.12.2009     17:01:01     LONG_PARAMS
02.12.2009     17:01:01     OPERATINGSYSTEM = ANYOS
02.12.2009     17:01:01     TARGETSYSTEM = PRODORADB
02.12.2009     17:01:01     DESTINATION
02.12.2009     17:01:01     SY-SUBRC = 1003
02.12.2009     17:01:01     SXPG_COMMAND_EXECUTE failed for BRBACKUP - Reason: program_start_error: For More Information, See SYS
02.12.2009     17:01:01     Job cancelled after system exception ERROR_MESSAGE
Note :
when i execute immediately or through Command line backup is going fine
but when i scheduling backup it was Cancelled (Status shows Schudling Failed)
pls give me suggestion
sathessh

Dear Yoganand.V
thanks for your immediate response
and still i am facing this issue
the Backups are triggered from DB13 and Scheduled from Central Instance not Application Server and Auto Script is running at OS level and pls look FINISHED BACKUP LOG for your Reference
08.12.2009     17:50:18     Job started
08.12.2009     17:50:18     Step 001 started (program RSDBAJOB, variant &0000000000717, user ID S2K_BASIS)
08.12.2009     17:50:18     No application server found on database host - rsh/gateway will be used
08.12.2009     17:50:18     Execute logical command BRBACKUP On host PRODORADB
08.12.2009     17:50:18     Parameters:-u / -jid ALLOG20091208175017 -c force -t online -m all -p initIRPdaily.sap -a -c force -p initIRPda
08.12.2009     17:50:18     ily.sap -cds
08.12.2009     18:29:23     BR0051I BRBACKUP 7.00 (34)
08.12.2009     18:29:23     BR0055I Start of database backup: becbwhwk.anf 2009-12-08 17.50.18
08.12.2009     18:29:23     BR0484I BRBACKUP log file: /oracle/IRP/sapbackup/becbwhwk.anf
08.12.2009     18:29:23     BR0477I Oracle pfile /oracle/IRP/102_64/dbs/initIRP.ora created from spfile /oracle/IRP/102_64/dbs/spfileIRP.ora
08.12.2009     18:29:23
08.12.2009     18:29:23     BR0280I BRBACKUP time stamp: 2009-12-08 17.50.19
08.12.2009     18:29:23     BR0319I Control file copy created: /oracle/IRP/sapbackup/cntrlIRP.dbf 15122432
08.12.2009     18:29:23
08.12.2009     18:29:23     BR0280I BRBACKUP time stamp: 2009-12-08 17.50.20
08.12.2009     18:29:23     BR0057I Backup of database: IRP
08.12.2009     18:29:23     BR0058I BRBACKUP action ID: becbwhwk
08.12.2009     18:29:23     BR0059I BRBACKUP function ID: anf
08.12.2009     18:29:23     BR0110I Backup mode: ALL
08.12.2009     18:29:23     BR0077I Database file for backup: /oracle/IRP/sapbackup/cntrlIRP.dbf
08.12.2009     18:29:23     BR0061I 42 files found for backup, total size 141794.742 MB
08.12.2009     18:29:23     BR0143I Backup type: online
08.12.2009     18:29:23     BR0130I Backup device type: util_file_online
08.12.2009     18:29:23     BR0109I Files will be saved by backup utility
08.12.2009     18:29:23     BR0142I Files will be switched to backup status during the backup
08.12.2009     18:29:23     BR0289I BRARCHIVE will be started at the end of processing
08.12.2009     18:29:23     BR0134I Unattended mode with 'force' active - no operator confirmation allowed
08.12.2009     18:29:23
08.12.2009     18:29:23     BR0280I BRBACKUP time stamp: 2009-12-08 17.50.20
08.12.2009     18:29:23     BR0229I Calling backup utility with function 'backup'...
08.12.2009     18:29:23     BR0278I Command output of '/usr/sap/IRP/SYS/exe/run/backint -u IRP -f backup -i /oracle/IRP/sapbackup/.becbwhwk.lst -t file_onli
08.12.2009     18:29:23
08.12.2009     18:29:23     Data Protection for SAP(R)
08.12.2009     18:29:23
08.12.2009     18:29:23     Interface between BR*Tools and Tivoli Storage Manager
08.12.2009     18:29:23     - Version 5, Release 5, Modification0.0 for AIX LF 64-bit -
08.12.2009     18:29:23     Build: 316B compiled on Oct 23 2007
08.12.2009     18:29:23     (c) Copyright IBM Corporation, 1996, 2007, All Rights Reserved.
08.12.2009     18:29:23
08.12.2009     18:29:23     BKI2027I: Using TSM-API version 5.5.1.0 (compiledwith 5.3.0.0).
08.12.2009     18:29:23     BKI2000I: Successfully connected to ProLE on porttdpr3ora64.
08.12.2009     18:29:23     BKI0005I: Start of program at: Tue Dec 8 17:50:20 IST 2009 .
08.12.2009     18:29:23
08.12.2009     18:29:23
08.12.2009     18:29:23     -- Parameters --
08.12.2009     18:29:23     Input File            : /oracle/IRP/sapbackup/.becbwhwk.lst
08.12.2009     18:29:23     Profile               : /oracle/IRP/102_64/dbs/initIRPdaily.utl
08.12.2009     18:29:23     Configfile            : /oracle/IRP/102_64/dbs/initIRP.bki
08.12.2009     18:29:23     Manual sorting file   : disabled
08.12.2009     18:29:23     Tracefile             : disabled
08.12.2009     18:29:23     Traceflags            : disabled
08.12.2009     18:29:23     Parallel sessions     : 1
08.12.2009     18:29:23     Multiplexed files     : 1
08.12.2009     18:29:23     RL compression        : 0
08.12.2009     18:29:23     Exit on error         : disabled
08.12.2009     18:29:23     BATCH                 : enabled
08.12.2009     18:29:23     Buffer size           : 131072
08.12.2009     18:29:23     Buffer Copy Mode      : SIMPLE
08.12.2009     18:29:23     Redologcopies         : disabled
08.12.2009     18:29:23     Versioning            : enabled
08.12.2009     18:29:23     Current Version      : 581
08.12.2009     18:29:23     Versions to keep     : 6
08.12.2009     18:29:23     Delete Versions      : <= 575
08.12.2009     18:29:23     Backup Type           : file_online
08.12.2009     18:29:23     TSM log server        : disabled
08.12.2009     18:29:23     TSM server            : [email protected] with 2 sessions configured, using 1 session
08.12.2009     18:29:23     TSM client node      : PRODORADB_TDP
08.12.2009     18:29:23     Days for backup      : Sun Mon Tue Wed Thu Fri Sat
08.12.2009     18:29:23     Backup mgmt class    : DAILYMGMTCLASS
08.12.2009     18:29:23     Archiv mgmt class    : DAILYMGMTCLASS
08.12.2009     18:29:23
08.12.2009     18:29:23
08.12.2009     18:29:23     BR0280I BRBACKUP time stamp: 2009-12-08 18.24.44
08.12.2009     18:29:23     BR0232I 8 of 8 files saved by backup utility
08.12.2009     18:29:23     BR0230I Backup utility called successfully
08.12.2009     18:29:23
08.12.2009     18:29:23     BR0056I End of database backup: becbwhwk.anf 2009-12-08 18.24.44
08.12.2009     18:29:23     BR0280I BRBACKUP time stamp: 2009-12-08 18.24.44
08.12.2009     18:29:23     BR0052I BRBACKUP completed successfully
08.12.2009     18:29:23
08.12.2009     18:29:23     BR0280I BRBACKUP time stamp: 2009-12-08 18.24.44
08.12.2009     18:29:23     BR0291I BRARCHIVE will be started with options '-U -jid ALLOG20091208175017 -d util_file -c force -p initIRPdaily.sap -cds'
08.12.2009     18:29:23
08.12.2009     18:29:23     BR0280I BRBACKUP time stamp: 2009-12-08 18.29.23
08.12.2009     18:29:23     BR0292I Execution of BRARCHIVE finished with return code 0
08.12.2009     18:29:23     Job finished
regards

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.

11G R2 How to stop the backup job totally

I have a third party application connected to 11G R2 database and is having issue every morning at 2. After applying the patch from the third part application, most of the issues are resolved. Unfortunately, I still get an ORA-12528 error - Failed to connect to database instance. Look like the third party application is having issue with the backup job. I have tried the command "alter tablespace tsname flashback off", but I check the alert log, the backup job is still running. I may have turn on the backup job during the database installation. How do I stop it?
Thanks for any help!
- Johnny

Sorry, I forgot to add "alter database flashback off "command on top of the other one. The third party application is basically a monitoring and scheduler tool. It uses JBOSS and TOMCAT connecting to the database using both jdbc and odcb. It doesn't store a lot of data. Here is the alert email I got this morning:
Target Name=MEDIAMGR
Target Type=Database Instance
Host=mediamgr2-db
Metric=Status
Metric Value=0
Timestamp=Jan 4, 2012 2:01:12 AM PST
Severity=Critical
Message=Failed to connect to database instance: ORA-12528: TNS:listener: all appropriate instances are blocking new connections (DBD ERROR: OCIServerAttach).
Notification Rule Name=Database Availability and Critical States
Notification Rule Owner=SYSMAN
Notification Count=1
as for backup, I have already disabled the archive logs and flashback database. A few minutes ago, I just turn off RMAN autoback. What else can I turn off related to backup?
Thanks,
- Johnny

Cannot find details of completed DPM backup job

I ran a DPM backup job successfully but now cannot find the job log to review the details. I can only see the start time, time elapsed, and data transferred on the jobs tab. Where is the detailed job log?
Any help would be appreciated...
Thanks.
Dave W

After jobs run in DPM there is only limited information (status) given in the gray box at the bottom of the Jobs tab. With many of the other backup applications that I deal with I get a lot more information. DPM only gives limited information
such as how long the backup took (backup time), the size of the backup, and where the backup target is. But I am looking for much more information than these basics.
For instance:
what was the duration of the backup (HH:MM:SS)
how many objects or files/folders were selected and how many completed the backup
what backup target was used
what was the throughput of the backup (MB/s or GB/s)
what was the compression ratio attained
what is the native remaining capacity on the target device
how many streams were used during the backup
etc.
The DPM GUI does not show this information and I cannot find or produce a log file that does either.
If you have any other suggestions on how I can get this data please let me know.
Many thanks in advance and thank you for your cooperation.
Dave W

Backup jobs failing

We are using 12c oms and I just submitted some backup jobs for several databases. I have both 10g and 11g databases with backup jobs configured to run. I had no problems submitting the jobs but when I checked the status the next day I get this weird error message. Any help sorting this out would be appreciated. This is the error: Checking RMAN repository settings...
Starting blackout...
ORA-20221: Only superusers can create a new reason
ORA-06512: at "SYSMAN.MGMT_BLACKOUT", line 167
ORA-06512: at line 1

Hi,
Have you recently upgraded the DB plugin to 12.1.0.3?
As we have a similar issue addressed in the following bug:
Bug 16475904: BACKUPS IN OEM 12C NOT WORKING POST ORACLE DATABASE PLUGIN 12.1.0.3 UPGRADE
Same error stack was observed in the bug as well.
Regards,
Venkat

How to find backup job

In Oracle 11g2, how can I find jbackup obs configured through OEM. I want to find out the job steps, commands, and status (failed or succeeded). These are not seen in V$RMAN_BACKUP_JOB_DETAILS and V$RMAN_BACKUP_SUBJOB_DETAILS. There are field COMMAND_ID in these view, but how to join these to find the actual commands.
Thanks

Hi,
how can I find jbackup obs configured through OEMfrom Home page -> maintanance -> backup reports -> here you can find all the backup jobs.
and check in
select * from v rman_backup_job_details;Thanks

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

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

Check The Job Status

Hi SAPsimhas,
My requirement is as below.
I will loop through an internal table and create some files with background processing method.(JOB_OPEN,SUBMIT & JOB_CLOSE)
Now once this job is triggered I need to check the status for that job after maximum 10 mins. Its not neccessary that each job will take 10 mins. only,It can be finished in 2 mins also.
Once the job is finished then I will XCOM that file.
So my question is how to code such timer which will check the job status for that job? I have a FM BP_JOB_READ which returns the job status.
Reply is highly appriciated.

Try this way
do.
    call function 'SHOW_JOBSTATE'
      exporting
        jobcount         = p_jobc
        jobname          = p_jobn
      importing
        aborted          = v_aborted
        finished         = v_finished
        ready            = v_ready
        running          = v_running
        scheduled        = v_scheduled
      exceptions
        jobcount_missing = 1
        jobname_missing = 2
        job_notex        = 3
        others           = 4.
    if v_aborted eq 'X'.
      exit.
    endif.
    if v_finished eq 'X'.
      select single * from tbtcp into wa_tbtcp1
                 where jobname eq p_jobn
                   and jobcount eq p_jobc.
      if sy-subrc eq 0.
        move wa_tbtcp1-listident to p_spono.
      endif.
      exit.
    endif.
    if v_count le 10.
      call function 'ENQUE_SLEEP'
        exporting
          seconds = 60.
      v_count = v_count + 1.
    endif.
enddo.
a®

Backup job status: Skipped?

Similar Messages

Maybe you are looking for