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.

Similar Messages

  • Rman jobs "Suspended on Agent Unreachable"

    I don't know if this problem is coming from rman, EM, or jobs. The only time it occurs is when I create an "Oracle Recommended" backup job thorugh EM.
    The job status is immediately suspended with the message "agent unreachable."
    Other RMAN functions that run in jobs scheduled through EM work fine (crosscheck for example). It only happens with I schedule backups through the Oracle Recommended link in EM.
    In the meantime, I'm running backups manually at the RMAN prompt.
    There's hardly any literature on Metalink or on the forums about this. Can anyone shed some light?

    I just ran across this thread when I was looking for a solution for the same issue ("Suspended on Agent Unreachable") hat had just happened to me. In my case, it was on RAC. I got that error when I created custom job and submitted it against cluster. The backup went OK, however, when I picked up one node, and submitted the same custom backup job from the specific node.

  • Rman jobs "Suspended on Agent Unreachable" through EM

    Hi, all:
    when I schedule an RMAN backup in OEM, It has a
    suspended on agent unreachable status immediately. Deleting the job and creating a new one, and the new job became suspended even before it's first scheduled job
    I can manually backup through rman prompt, no problem.
    The database is RAC 10.2.0.3 on linux*86.
    I checked web found lots of friends had the same problem without solutions, is there anyone has experience to fix it?
    Thanks a lot

    Have you done anything to determine why the agent is unreachable such as checking its status with emctl or reading a log file?

  • Oracle Management Console 10g - Job Status - Suspended on Agent Unreachable

    Recently we updated our RDMS from 10.2.0.1 to 10.2.0.4.0 PATCH 25.
    Ever since we upgraded, we have had trouble with our RMAN backups. Now when a scheduled backup begins it never ends. Now whenever we schedule a job, from a backup to any simple system command, the status immediately returns "Suspended on Agent Unreachable".
    We can start and stop the dbconsole successfully, and I can use the OEM to monitor the database, and make changes to that. However, I cannot run any scheduled database jobs through the OEM. However, I can run the rman jobs via the command line.
    The database server, and the OEM console is on the save server. I am not running RAC. Everything database related is on this one server.
    Here are the results for emctl status agent:
    E:\oracle\product\10.2.0\db_1\BIN>emctl status agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
    Agent Version     : 10.1.0.6.0
    OMS Version       : 10.1.0.6.0
    Protocol Version  : 10.1.0.2.0
    Agent Home        : E:\oracle\product\10.2.0\db_1\content.mydomain.com_ORCL
    Agent binaries    : E:\oracle\product\10.2.0\db_1
    Agent Process ID  : 34372
    Agent URL         : http://content.mydomain.com:3938/emd/main
    Started at        : 2010-01-11 14:58:24
    Started by user   : SYSTEM
    Last Reload       : 2010-01-11 14:58:24
    Last successful upload                       : (none)
    Last attempted upload                        : (none)
    Total Megabytes of XML files uploaded so far :     0.00
    Number of XML files pending upload           :     5016
    Size of XML files pending upload(MB)         :    42.77
    Available disk space on upload filesystem    :    37.94%
    Agent is Running and ReadyHere are the results for emctl status agent:
    E:\oracle\product\10.2.0\db_1\BIN>emctl upload
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
    EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..I think the EMD upload error may be the problem, but I'm unsure how to resolve this.
    What do I need to do in order to resolve this issue?
    If any more info would be useful, please let me know and I will post it immediately.
    thanks.

    Rondeyli,
    Thanks, that was it. I followed your instructions, and was able to get the system to work. I had to alter the commands a bit to get them to work on my system, so here is what I did.
    I performed the following steps:
    1. Ran the following command:
            emctl stop dbconsole
    2. deleted all files in $AGENT_HOME/sysman/emd/upload and $AGENT_HOME/sysman/emd/state
    3. Ran the following command:
           emctl clearstate dbconsole
    4. Ran the following command:
           emctl secure dbconsole
    5. Ran the following command:
           emctl start dbconsoleThis got everything running for me.
    thanks.

  • Backup Suspended on Agent Unreachable - 11GR2 Windows

    Hi as the title suggests an RMAN backup has gone into a state of Suspended on Agent Unreachable.
    I have a 2 node RAC and have run emctl status dbconsole on each node. On node 1 I get a message: EM Daemon is running. On node 2 I get a message: Oracle enterprise Manager 11g is running.
    Why are these messages different? and could this be the reason why the job has gone into the state it has?
    Thanks in advance

    I strongly suggest to not using RMAN via OEM, but with the good old command line.
    The messages are different because on one node there is the real web app (oc4j...) while on the other one there is only the agent running so it is expected.
    Alessio

  • OEM 10g - Job Status - Suspended on Agent Unreachable

    Hi,
    I have checked out a few post on this forum which is similar to my problem.
    But could not get the exact workaround.
    The scheduled backup is not getting failed / successful since 29th January 2010.
    We have not made any changes on the database level. But there was a patching activity at application level.
    and as soon as I try to schedule a backup it shows the same status "suspended on agent unreachable"
    I have checked the emctl status and dbconsole status.
    E:\oracle\product\10.2.0\db_1\BIN>emctl status agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Agent Version : 10.1.0.6.0
    OMS Version : 10.1.0.6.0
    Protocol Version : 10.1.0.2.0
    Agent Home : e:\oracle\product\10.2.0\db_1\content.mydomain.de_aeb
    Agent binaries : e:\oracle\product\10.2.0\db_1
    Agent Process ID : 6104
    Agent URL : http://content.mydomain.de:3938/emd/main
    Started at : 2010-02-01 21:55:19
    Started by user : SYSTEM
    Last Reload : 2010-02-01 21:55:19
    Last successful upload : 2010-02-17 06:12:10
    Last attempted upload : 2010-02-17 06:12:25
    Total Megabytes of XML files uploaded so far : 323.40
    Number of XML files pending upload : 1
    Size of XML files pending upload(MB) : 0.01
    Available disk space on upload filesystem : 9.36%
    Agent is Running and Ready
    E:\oracle\product\10.2.0\db_1\BIN>emctl status dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    http://content.mydomain.de:1158/em/console/aboutApplication
    Oracle Enterprise Manager 10g is running.
    Logs are generated in directory e:\oracle\product\10.2.0\db_1/scontent.mydomain.de_AEB/sysman/log
    Upload also seems to be working fine.
    E:\oracle\product\10.2.0\db_1\BIN>emctl upload
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    EMD upload completed successfully
    What should I do ? Will restarting the agent help ? Will restarting the agent have any adverse effect on DB ?
    Any help would be a great help.
    Rushabh

    Hi,
    This is urgent.. Please help..
    I am not able to start the emctl...
    Below is the error that I am getting..
    E:\oracle\product\10.2.0\db_1\BIN>emctl stop agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    This will stop the Oracle Enterprise Manager 10g Database Control process. Conti
    nue [y/n] :y
    The OracleDBConsoleaeb service is stopping..........
    The OracleDBConsoleaeb service was stopped successfully.
    E:\oracle\product\10.2.0\db_1\BIN>emctl clearstate agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    EMD clearstate completed successfully
    E:\oracle\product\10.2.0\db_1\BIN>emctl secure agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Enter Agent Registration password :
    Agent is already stopped... Done.
    Securing agent... Started.
    Requesting an HTTPS Upload URL from the OMS... Failed.
    The OMS is not set up for Enterprise Manager Security.
    E:\oracle\product\10.2.0\db_1\BIN>emctl start agent
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    The service name is invalid.
    More help is available by typing NET HELPMSG 2185.
    When I try to secure agent it is asking for a password, but it is already saved I think..
    When I press enter it is showing the above error.
    What should I do now ?
    Regards,
    Rushabh
    Edited by: user650383 on Feb 16, 2010 10:44 PM

  • Suspended on agent unreachable

    Oracle 10.2.0.3.0
    From Enterprise Manager, I am attempting to Create Backup. After I create the job, I receive "Suspended on agent unreachable".
    When I run emctl status agent, it says, "Agent is running and ready."
    Short of deleting the agent and reinstalling it, is there anything else I can do to fix the problem?
    If I need to reinstall the agent, is there a location other than Metalink that I can download the software? My service identifier has expired and I'm not sure when I'll be able to get a new one.
    Thank You.

    have you tried the following:
    1. Stop the agent
    emctl stop agent
    2.remove some files on emd
    cd $ORACLE_HOME/sysman/emd
    rm agntstmp.txt
    rm lastupld.txt
    rm blackouts.xml
    rm -r upload/*
    rm -r state/*
    rm -r collection/*
    3. clear the agent and start it again.
    emctl clearstate agent (this should delete all state files but sometimes it is not enough, but I experienced that it is better to use this command after deletion of the files)
    emctl secure agent (optional depends if you using secure agent or not)
    emctl start agent
    Edited by: user480489 on Jan 5, 2011 3:32 PM

  • 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.

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

  • 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

  • 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 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

  • 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.

  • 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

Maybe you are looking for