RMAN backup issue

Oracle 11.2.0.1
Windows 7 Home Premium
RMAN> backup database;
Starting backup at 05-MAR-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/05/2012 12:25:05
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 05-MAR-12
channel ORA_DISK_1: finished piece 1 at 05-MAR-12
piece handle=E:\APP\NISHA\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012_03_05\O1_MF_NCSNF_TAG20120305T122505_7O8RTBXJ_.BKP tag=TAG20120305T122505 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/05/2012 12:25:05
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
RMAN> 1.What is the problem in above scnerio ?
2.How to take RMAN backup when db is down ?
3.How to take RMAN backup when db is noarchivelog mode ?
Please help me. Thank you.

I am trying to do a full RMAN cold backup and am getting the following :
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
What’s the cause ?
Here’s the example
connected to target database (not started)
Oracle instance started
database mounted Total System Global Area 1610612736 bytes Fixed Size 2056504 bytes
Variable Size 603983560 bytes
Database Buffers 989855744 bytes
Redo Buffers 14716928 bytes using target database control file instead of recovery catalog
allocated channel: backup_disk1
channel backup_disk1: sid=4977 instance=TEST1 devtype=DISK Starting backup at 31-OCT-13
channel backup_disk1: starting full datafile backupset
channel backup_disk1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on backup_disk1 channel at 31/10/2013 20:18:45
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel backup_disk1: starting full datafile backupset
channel backup_disk1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:45
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel backup_disk1: starting full datafile backupset
channel backup_disk1: specifying datafile(s) in backupset
RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:46
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel backup_disk1: starting full datafile backupset
channel backup_disk1: specifying datafile(s) in backupset
released channel: backup_disk1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on backup_disk1 channel at 13/10/2013 20:18:47
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
RMAN>
The cause is simple, the database has not been shutdown cleanly. You will require to restart the database and shutdown again, if in a RAC you will have to shutdown all instances cleanly.
Disabing archive log and attempting to backup the database will demonstrate the cause.
SQL> startup force;
ORACLE instance started.
Total System Global Area 1235959808 bytes
Fixed Size 2175288 bytes
Variable Size 620760776 bytes
Database Buffers 603979776 bytes
Redo Buffers 9043968 bytes
Database mounted.
Database opened.
SQL> shutdown abort;
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 1235959808 bytes
Fixed Size 2175288 bytes
Variable Size 620760776 bytes
Database Buffers 603979776 bytes
Redo Buffers 9043968 bytes
Database mounted.
SQL>
Now we’ll try again to backup datafile 1.
RMAN> backup datafile 1;
Starting backup at 31-OCT-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=133 device type=DISK
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 13/10/2013 20:43:34
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
This is simply because we issue a shutdown abort on the instance. However, just preforming a recovery will allow you to backup as required.
SQL> recover database;
Media recovery complete.
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
C:UsersGary>rman target sys/passwd@db11g
Recovery Manager: Release 11.2.0.1.0 – Production on Thu  Oct 31 20:44:15 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: DB10G (DBID=3002158372, not open)
RMAN> backup datafile 1;
Starting backup at 06-DEC-10using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1channel ORA_DISK_1: SID=125 device type=DISK
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=C:APPGARYORACLEPRODUCT10.2.0DB_1ORADATADB10GSYSTEM01.DBF
channel ORA_DISK_1: starting piece 1 at 31-OCT-13
channel ORA_DISK_1: finished piece 1 at 31-OCT-13
piece handle=C:APPGARYORACLEPRODUCT10.2.0DB_1FLASH_RECOVERY_AREADB10GBACKUPSET2010_12_06O1_MF_NNNDF_TAG20101206T204423_6HTCR810_.BKP tag=TAG20101206T204423 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
Finished backup at 31-OCT-13
Starting Control File and SPFILE Autobackup at 31-OCT-13
piece handle=C:APPGARYORACLEPRODUCT10.2.0DB_1FLASH_RECOVERY_AREADB10GAUTOBACKUP2010_12_06O1_MF_S_737066556_6HTCSQVF_.BKP comment=NONE
Finished Control File and SPFILE Autobackup at 31-OCT-13
RMAN> exit
Interestingly, even with the recovery performed, we cannot switch back to archivelog mode without a clean shutdown.
SQL> alter database archivelog;
alter database archivelog*
ERROR at line 1:ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
SQL> recover database;
ORA-00283: recovery session canceled due to errors
ORA-00264: no recovery required
SQL> alter database archivelog;
alter database archivelog*
ERROR at line 1:ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
So we’ll startup and shutdown again. You cannot use the force option since that still does not perform a normal shutdown and you’ll get the same error.
SQL> alter database open;
Database altered.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 1235959808 bytes
Fixed Size 2175288 bytes
Variable Size 620760776 bytes
Database Buffers 603979776 bytes
Redo Buffers 9043968 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered.

Similar Messages

  • RMAN Backup Issue when Full backup file was missing

    Hi,
    On : 11.2.0.2 version, Recovery Manager
    RMAN Backup issue
    Last week we had the NFS Issue where we backup the files onto NFS.
    The problem occurred in the below sequence
    Saturday the backup was successful
    Saturday before deleting the backup files they are copied to tape
    Deleting the backup files via OS command
    Sunday Full backup started but due the NFS issue backup failed(Killed the instance and restarted)
    Did the RMAN Incremental backup which worked on Monday
    On Tuesday RMAN started complaining and started doing the Full backup.
    no parent backup or copy of datafile 1 found
    no parent backup or copy of datafile 3 found
    no parent backup or copy of datafile 24 foundSony any idea why the Incremental backup worked on Monday but not on Tuesday
    Regards
    NM

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

  • Issue Creating Duplicate Database on Different host using RMAN Backup

    HI friends..
    I m trying to create a duplicate db on different host ....... 27
    i have live production db on ............. 15
    its up 24*7.
    i know how to create dup db using cold backup..but dont know how to create it using RMAN Backup..
    I have googled..but getting issues..
    Steps Taken till now
    Note- I dont have catalog created on live db..
    I already have set the tnsnames.ora on both servers
    1) Took full backup plus archivelog plus control file on 15
    2) moved it to another host..ie 27
    3) now on live db..
    I conected to rman target /
    so i m now connected to prod db
    than i try to conect to rman auxiliary sys/sys@dubpd..
    But it gives me insufficient privilages error..
    Can you tell me what to do next..Coz unless i get into mount phase on sever 27( new server)..i cannot use the control file from backup).my dupdb is up in nomount phase..but what enxt i can do..to restore the control file and than restore the backup after cataloging them to right path..
    Thanks in advance frieds...

    sai121 wrote:
    Nope ..on live db..
    @comand prompt when i type sqlplus sys/sys@dupdb..
    its says 0ra-12518...Listener cannot hand off client connection..
    My tns name for live server is..*primary* on live server .. whose ip is 15..(lIVE SERVER).
    i also have another entery with tns names- standby .on live server .. whose ip is 27..(other server for duplicated db).
    now @command prompt..@live server.. i did sqlplus sys/sys@standby
    It gives me ORA-12518
    Am i missing something..1- It could be a network problem. You may enable tracing on listener (and examine the logs).
    2- Add "DIRECT_HANDOFF_TTC_LISTENER=OFF" to listener.ora, then reload the listener
    3- You may want to increase "large_pool_size"

  • RMAN BACKUPS AND ARCHIVED LOG ISSUES

    제품 : RMAN
    작성날짜 : 2004-02-17
    RMAN BACKUPS AND ARCHIVED LOG ISSUES
    =====================================
    Scenario #1:
    1)RMAN이 모든 archived log들을 삭제할 때 실패하는 경우.
    database는 두 개의 archive destination에 archive file을 생성한다.
    다음과 같은 스크립트를 수행하여 백업후에 archived redo logfile을 삭제한다.
    run {
    allocate channel c1 type 'sbt_tape';
    backup database;
    backup archivelog all delete input;
    Archived redo logfile 삭제 유무를 확인하기 위해 CROSSCHECK 수행시 다음과
    같은 메시지가 발생함.
    RMAN> change archivelog all crosscheck;
    RMAN-03022: compiling command: change
    RMAN-06158: validation succeeded for archived log
    RMAN-08514: archivelog filename=
    /oracle/arch/dest2/arcr_1_964.arc recid=19 stamp=368726072
    2) 원인분석
    이 문제는 에러가 아니다. RMAN은 여러 개의 arhive directory중 하나의
    directoy안에 있는 archived file들만 삭제한다. 그래서 나머지 directory안의
    archived log file들은 삭제되지 않고 남게 되는 것이다.
    3) 해결책
    RMAN이 강제로 모든 directory안의 archived log file들을 삭제하게 하기 위해서는
    여러 개의 채널을 할당하여 각 채널이 각 archive destination안의 archived file을
    백업하고 삭제하도록 해야 한다.
    이것은 아래와 같이 구현될 수 있다.
    run {
    allocate channel t1 type 'sbt_tape';
    allocate channel t2 type 'sbt_tape';
    backup
    archivelog like '/oracle/arch/dest1/%' channel t1 delete input
    archivelog like '/oracle/arch/dest2/%' channel t2 delete input;
    Scenario #2:
    1)RMAN이 archived log를 찾을 수 없어 백업이 실패하는 경우.
    이 시나리오에서 database를 incremental backup한다고 가정한다.
    이 경우 RMAN은 recover시 archived redo log대신에 incremental backup을 사용할
    수 있기 때문에 백업 후 모든 archived redo log를 삭제하기 위해 OS utility를 사용한다.
    그러나 다음 번 backup시 다음과 같은 Error를 만나게 된다.
    RMAN-6089: archive log NAME not found or out of sync with catalog
    2) 원인분석
    이 문제는 OS 명령을 사용하여 archived log를 삭제하였을 경우 발생한다. 이때 RMAN은
    archived log가 삭제되었다는 것을 알지 못한다. RMAN-6089는 RMAN이 OS 명령에 의해
    삭제된 archived log가 여전히 존재하다고 생각하고 백업하려고 시도하였을 때 발생하게 된다.
    3) 해결책
    가장 쉬운 해결책은 archived log를 백업할 때 DELETE INPUT option을 사용하는 것이다.
    예를 들면
    run {
    allocate channel c1 type 'sbt_tape';
    backup archivelog all delete input;
    두 번째로 가장 쉬운 해결책은 OS utility를 사용하여 archived log를 삭제한 후에
    다음과 같은 명령어를 RMAN prompt상에서 수행하는 것이다.
    RMAN>allocate channel for maintenance type disk;
    RMAN>change archivelog all crosscheck;
    Oracle 8.0:
         RMAN> change archivelog '/disk/path/archivelog_name' validate;
    Oracle 8i:
    RMAN> change archivelog all crosscheck ;
    Oracle 9i:
    RMAN> crosscheck archivelog all ;
    catalog의 COMPATIBLE 파라미터가 8.1.5이하로 설정되어 있으면 RMAN은 찾을 수 없는
    모든 archived log의 status를 "DELETED" 로 셋팅한다. 만약에 COMPATIBLE이 8.1.6이상으로
    설정되어 있으면 RMAN은 Repository에서 record를 삭제한다.

    Very strange, I issue following command in RMAN on both primary and standby machine, but it they don't delete the 1_55_758646076.dbf, I find in v$archived_log, this "/home/oracle/app/oracle/dataguard/1_55_758646076.dbf" had already been applied.
    RMAN> connect target /
    RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    old RMAN configuration parameters:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    new RMAN configuration parameters:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
    new RMAN configuration parameters are successfully stored
    RMAN>
    ----------------------------------------------------------------------------------

  • Can not recover table from rman backup

    For testing I want to recover deleted table from rman backup.
    I have make vm of oracle 11g.  the following step i have applied but could not recover the table.
    rman> backup database ;
    On sqlplus create login as scott/tiger
    create table scott.emp1(col1 varchar2(10));
    insert into emp1(col1) value('Yasir ') ;
    commit ;
    select * from emp1 ;
    it shows me one row successfully.
    Now i have login the  sys as sysdba
    sqlplus> alter system switch logfile ;
    after this i have drop the table .
    Now to recover the table i have restored database on same vm.
    rman>restore database ;
    rman> recover database ;
    rman> alter database open ;
    on sqlplus i have issued
    sqlplus> select * from scott.emp1 ;
    table or view does not exist.
    any help how to recover the deleted table from rman backup

    Hi,
    Check this test case
    SQL> create table TEST2 as select * from emp;
    Table created.
    SQL> select count(*) from TEST2;
      COUNT(*)
            15
    SQL> select TO_CHAR(SYSDATE,'DD-MON-YYYY HH24:MI:SS') from dual;
    TO_CHAR(SYSDATE,'DD-
    10-SEP-2013 10:57:05
    SQL> alter system switch logfile;
    System altered.
    SQL> drop table TEST2 purge;
    Table dropped.
    SQL> shu immediate
    [oracle@vnode MYSHELL]$ rman target /
    Recovery Manager: Release 11.2.0.2.0 - Production on Tue Sep 10 10:58:39 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: DDTEST (DBID=1667776968, not open)
    RMAN> run{
    set until time "to_date('2013 Sep 10 10:57','yyyy mon dd hh24:mi')";
    restore database;
    recover database;
    alter database open resetlogs;
    }2> 3> 4> 5> 6>
    media recovery complete, elapsed time: 00:00:02
    Finished recover at 10-SEP-13
    database opened
    RMAN> exit
    SQL> set lin 200 pages 100
    SQL> select count(*) from test2;
      COUNT(*)
            15
    HTH

  • Unable to restore and recover my Database from RMAN Backup

    Dear All,
    Iam practicing RMAN in Windows environment.
    My configurations are
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION ON; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'F:\Backup\%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\ORACLE\DATABASE\SNCFORCL.ORA';
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'F:\Backup\%U.bak';
    Then i took the RMAN backup, now iam shutdown my DB and removed one logfile..
    then i tried to startup the DB but it is saying
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: 'E:\ORADATA\ORCL\REDO03.LOG'
    So i tried to restore the Database with my rman backup
    RMAN> restore database;
    But i am unable to restore my logfile in the Datafiles location where as all other datafiles are restored but redo logfiles are not restored.
    So, i am unable to recover my DB
    Please tell me whether i am doing any mistake, what is the solution for my problem.
    Thanks in advance
    Mahi

    All you restored was your datafiles.
    Now issue recover database and that will apply the archive logs.
    This is in the oracle documentation.
    "You must restore backups of these archived logs for recovery to proceed. You can restore either to the default or nondefault location. If you do not have backups, then you must performing incomplete recovery up to an SCN before the first missing redo log and open RESETLOGS."
    http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/osrecvry.htm
    In this case after issuing restore database in RMAN, then issue this.
    "Recover database"
    It will then be an incomplete recovery. They should have been multiplexed. Did you restore your controlfile with this backup? You may have to issue an "Alter database open resetlogs;"

  • I am getting below error while taking RMAN backup.

    Friends,
    I am getting below error while taking RMAN backup.
    The issue is related with a lock while trying to backup the controlfile.
    The lock is more likely caused by the autobackup controlfile process started just before RMAN process was also trying the backup controlfile as shown in the following alert.log excerpt.
    Starting Control File and SPFILE Autobackup at 2009-04-07 09:24:58
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 04/07/2009 09:25:03
    ORA-00230: operation disallowed: snapshot control file enqueue unavailable
    Is there anyway to solve this issue?Thanks in advance.

    Hi,
    SQL> SELECT s.sid, username AS "User", program, module, action, logon_time "Logon", l.*
    FROM v$session s, v$enqueue_lock l
    WHERE l.sid = s.sid and l.type = 'CF' AND l.id1 = 0 and l.id2 = 2; 2 3
    no rows selected
    Oracle version : 10.2.0.3
    I am getting this error once in a month not everyday.
    Starting Control File and SPFILE Autobackup at 2009-04-07 09:24:58
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_DISK_1 channel at 04/07/2009 09:25:03
    ORA-00230: operation disallowed: snapshot control file enqueue unavailable
    Please suggest me based on this..Thanks in advance..

  • Standby database from RMAN backup

    I have been assigned to create a standby database from our RMAN backups in a different machine, as this is my first attempt at recovering, I am struggling a bit. I would appreciate if someone can throw any light on what dumb mistakeI am doing here. I ahve absolutely no control over the back up script which is done by my vendor, but can do anything in the reocvery portion. I did try going through the documentaiton and other help available for the last 2 days.
    Database : Oracle 10G R2
    OS : Windows Server 2003
    My backup script is
    configure channel device type disk format 'J:\RMAN\RMAN_df_%U' maxpiecesize 2048M;
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    backup database;
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    backup current controlfile for standby FORMAT='J:\RMAN\RMAN_sc_%U';
    For recovery of a standby database,
    I have copied the the back up pieces and the archive logs to the standby server where I have just created an instance with the same name as production db.
    set ORACLE_SID=NGINPROD
    set dbid 820336652
    STARTUP NOMOUNT
    RESTORE STANDBY CONTROLFILE FROM 'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
    CATALOG BACKUPPIECE 'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_2_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_3_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_4_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_5_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_6_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_7_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_2_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_3_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_4_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2TMIUJLN_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
    RESTORE DATABASE;
    Till this step I do not encounter any issues, but when i try to recover the database I am hit with the below error.
    RMAN> recover database;
    Starting recover at 16-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    starting media recovery
    unable to find archive log
    archive log thread=1 sequence=253340
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/16/2011 09:31:57
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 253340 lowscn 4696173517
    ------------------------------------------------------------------------------------------------------------------------------------------------

    Here's the standard dcoumentation on the procedure :
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm#i636377
    Appendix "F Creating a Standby Database with Recovery Manager" of the "Oracle® Data Guard Concepts and Administration" guide.
    I don't see ArchiveLog backups being done by the vendor's script. How do you backup the ArchiveLogs ?
    In your post you state that you have copied the ArchiveLogs. Are they copied to the same log_archive_dest location ? RMAN needs to be "aware" of them. You can use the "CATALOG" command in RMAN to register them into the controlfile.
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta011.htm#sthref230
    A Standby Database uses a Standby Controlfile which is created from the Primary (with the "ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'locaion';" command) and then copied over to the Standby server.
    Hemant K Chitale

  • Problem in recovery from RMAN backup in case of disk failure

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

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

  • NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES

    제품 : RMAN
    작성날짜 : 2004-05-20
    NEW 9I RMAN: BACKUP OPTIMIZATION AND RETENTION POLICIES
    =======================================================
    오라클 9i RMAN 에서는 백업을 보다 효율적으로 할 수 있는 기능을 보강 했다.
    지금 소개할 "Retention Policies" 기능을 통해서 보다 효율적인 RMAN 백업
    전략을 세울 수 있다.
    1. 백업 화일 최적화 방법 (Backup File Optimization)
    백업 화일 최적화란 백업에 소요되는 공간을 최소화 하는 전략이다. RMAN
    백업시에 같은 정보 (dbid, checkpoint, and resetlogs data 등등) 를 가지고 있는
    화일이 이미 존재하는 백업 셋 내부에 있는지 체크하게 된다. 만일 같은 화일이
    이미 백업 되어 있다면 BACK UP 명령은 해당 화일에 대해서는 백업을 하지 않게
    된다.
    이때 같은 화일이라고 판단하는 기준은 다음과 같다.
    * Datafile: 같은 DBID, checkpoint SCN, resetlogs SCN 과 time. 데이타 화일은
    반드시정상적으로 offline 되었거나, read-only 이거나, 또는 정상적 으로 close
    되어야 함.
    * Archived redo log: 같은 thread, sequence number, 그리고 같은 Resetlogs
    SCN 과 time.
    * Backup Set: 같은 Backup Set recid 와 stamp.
    RMAN 이 백업을 수행하다가 위와 같은 조건의 화일이 이미 존재함을 확인하면
    이것은 건너뛰게 될 화일의 대상이다. 하지만 이때 바로 Skip 을 결정하지 않고
    정해진 Retention Policies 를 조사 한후에 Skip 여부를 결정 하게 된다.
    만일 백업 명령에 DELETE INPUT option 이 사용되면 RMAN 은 백업이 Skip
    되어도 화일을 지우게 된다.
    RMAN 은 모든 화일에 대한 백업이 Skip 되어도 에러메시지나 경고를 보내지
    않는다.
    그러나 만일 데이터 화일에 대한 백업이 recovery policy window 보다 오래
    된 것 이면 RMAN 은 새로운 백업 화일을 만들기 위해서 화일을 백업 하게 된다.
    Note:
    자체적인 expirations policy 를 가지고 있는 media manager 를 사용할 경우에는
    이런 백업 최적화 정책을 사용하는 것에 신중을 기해야 한다.
    백업 최적화 를 사용하기 위해서는 CONFIGURE 명령을 사용한다. CONFIGURE
    명령은 명령 수행 이후에 이루어지는 모든 백업에 대해 적용이 된다.
    예:
    CONFIGURE BACKUP OPTIMIZATION ON; # default 는 OFF
    2. Backup Optimization에 Retention Policies 적용 하기
    Retention Policy 로 백업 최적화를 조절 할 수 있다. 그러나 retention policy를
    사용하지 않기 위해서는 'CONFIGURE RETENTION POLICY TO NONE' 을
    이용해서 명시적으로 retention policy를 사용하지 않는다고 해야 한다. 디폴트로
    REDUNDANCY = 1 이 적용 된다.
         a. Recovery Window 를 이용한 Backup Optimization
    만일 백업 최적화가 enable 되어 있고 Recovery Window 가 retention policy
    적용을 위해서 셋업 되어 있으면 RMAN 은 항상 가장 최근의 백업이 Recovery
    Window 보다 오래된 데이터 화일을 백업한다.
    예를 들면 다음과 같은 조건에서
    o Today is February 21.
    o The recovery window is 7 days.
    o The most recent backup of tablespace tbs2 to tape is January 3.
    o Tablespace tbs2 is read-only.
    2월 21일에 tbs2 테이블 스페이스를 테이프로 백업을 하라는 명령을 내리면,
    RMAN 은 이 화일이 1월3일 이후에 변경 사항이 없는데도 불구 하고 백업을 하게
    된다. 이로써 RMAN 은 최근 7일 동안에 최소한 한번의 백업이 있어야 된다는
    조건을 지키게 된다.
    이러한 작동 방식은 media manager 가 오래된 테잎을 제거 해도 되도록 한다.
    그렇지 않다면, media manager 는 1월 3일의 백업을 무한정 가지고 있게 된다.
    2월 21일에 tbs2 테이블 스페이스의 보다 최근의 백업을 만듦으로 써, RMAN 은
    media manager 가 1월 3일에 백업 했던 테입을 지워도 되도록 한다.
         b. Redundancy 를 이용한 Backup Optimization
    Retention policy 로 Redundancy 를 채택 한 경우에 RMAN 은 Redundancy
    에 1을 더한 갯수를 초과하는 오프라인 또는 읽기 전용 화일의 백업을 건너뛴다.
    이때 'CONFIGURE RETENTION POLICY TO REDUNDANCY n' 명령어로
    Redundancy의 갯수를 정한다.
    아래와 같은 백업 최적화 명령을 내린 경우를 예로 든다:
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    아카이브 테이블스페이스를 한번도 백업을 받은적이 없고 다음의 작업을 1주일
    동안 한다고 하자.
    Day Action Result Redundant Backup
    Monday Take tablespace archive offline clean.
    Tuesday Run BACKUP DATABASE. The archive tablespace is backed up.
    Wednesday Run BACKUP DATABASE. The archive tablespace is backed up.
    Thursday Run BACKUP DATABASE. The archive tablespace is backed up. Tuesday backup.
    Friday Run BACKUP DATABASE. n/a Tuesday backup.
    Saturday Run BACKUP DATABASE. n/a Tuesday backup.
    Sunday Run DELETE OBSOLETE. The Tuesday backup is deleted.
    Monday Run BACKUP DATABASE. The archive tablespace is backed up. Wednesday backup.
    화요일, 수요일, 그리고 목요일의 백업은 아카이브 테이블 스페이스를 복사 해서
    3개의 백업이 반드시 존재 해야 한다는 조건을 충촉 시킨다. (1+Redundancy)
    금요일과 토요일에는 백업 최적화 조건에 의해서 아카이브 테이블 스페이스를
    복사하지 않게 된다.
    RMAN 은 일요일에는 유효기간이 지난 백업 화일을 지우게 된다. 따라서 화요일에
    만든 백업은 삭제 된다. 월요일의 전체 백업은 3개의 백업이 존재 해야 한다는 조건
    때문에 아카이브 테이블 스페이스를 또 다시 백업하게 된다. 이런 방식으로 백업
    사이클이 진행 된다.
    3. RETENTION POLICY NONE vs. DEFAULT
    주의 사항:
    'CONFIGURE RETENTION POLICY TO NONE' 과 'CONFIGURE RETENTION
    POLICY TO DEFAULT' 는 그 의미가 같지 않다. 전자는 RETENTION POLICY
    자체가 존재 하지 않는다는 의미 이며 백업은 expire 되지 않으며 'DELETE
    OBSOLETE' 명령은 사용 할 수 없게 된다. 후자는 디폴트 RETENTION POLICY
    (REDUNDANCY 1) 를 사용하게 된다는 의미 이다.
    'DELETE OBSOLETE' 명령은 RETENTION POLICY 기준으로 expire 된 백업을
    제거 하라는 명령이다.
    보다 자세한 내용은 Oracle9i Recovery Manager User's Guide and
    Reference의 Backup Optimization 부분을 참고 하시기 바랍니다.
    --------------THE END----------------------------------------------

    Hi,
    Backup optimisation = +- do not copy empty space.
    So, when you issue your BACKUP statement, it backs up the datafile. dot. nothing more.
    In order to achieve what you're testing, look into TFM for BACKUP INCREMENTAL LEVEL x .
    Regards,
    Yoann.

  • Need inputs on RMAN Backup n Recovery for multiple restore of clean backup

    I will explain my scenario below:
    We have the requirement of performance testing of our proposed production platform, for this i am asked to take RMAN backup of clean position (Say Day0 or baseline backup) and restore it multiple times for few rounds of testing. My question is after 1st restore (with set until time of day0 position) if i open the database with resetlogs, would i be able to restore same clean backup again? I am using control file in the environment instead of RMAN catalog database. What i can do to make this scenario work? I am already in preperation of setting rman catalog database.
    Please suggest me the best way forward...
    Many Thanks
    Nukesh

    Hi Asif,
    I tried to make it work but seems there are still issue with my recovery, can you have a look and point out the shortcommings. i am totally lost here
    RMAN> list incarnation;
    using target database control file instead of recovery catalog
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 MYTEST 2433328848 PARENT 1 19-DEC-06
    2 2 MYTEST 2433328848 PARENT 564488 04-NOV-10
    3 3 MYTEST 2433328848 CURRENT 693719 06-NOV-10
    RMAN> exit
    TEST1DB-> rman target sys@MYTEST1
    Recovery Manager: Release 10.2.0.3.0 - Production on Sun Nov 7 11:43:01 2010
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    target database Password:
    connected to target database: MYTEST (DBID=2433328848, not open)
    RMAN> reset database to incarnation 2;
    using target database control file instead of recovery catalog
    database reset to incarnation 2
    RMAN> run {
    2> restore database until scn 10000;
    3> recover database until scn 10000;
    4> alter database open resetlogs;
    5> };
    Starting restore at 07-NOV-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=191 instance=MYTEST1 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=190 instance=MYTEST1 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/07/2010 11:45:18
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, c onnect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, l ibrary, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rm an, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, va lidate"
    RMAN-01007: at line 0 column 2 file: standard input
    RMAN>
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanbackup/MYTEST/ora_cf%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rmanbackup/MYTEST/ora_df%t_s%s_s%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10g/dbs/snapcf_MYTEST1.f'; # default
    RMAN> exit
    SQL> select name from v$database;
    NAME
    MYTEST
    SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME
    NAME TYPE VALUE
    control_file_record_keep_time integer 7
    SQL>

  • 10.1.0.2.0 RMAN backup- What would cause RMAN to hang?

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

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

  • RMAN backup is getting failed after oracle 11g upgarde (11.2.0.2)

    Hi Basis Expert,
    We have done oracle 11g ugrade (11.2.0.2) in our Dev BI system.
    But after the upgrade the RMAN backup is failing. The backup use to work fine when we were on 10g (10.2.0.4).
    Has anyone face this issue earlier.
    Appreciate your help.
    Regards,
    Anil Shenoy

    Hello Anil,
    Syntax is -
    ln -s /path/to/original/ /path/to/linkName
    Output will be -
    linkName --> original
    In your case, 112_64 is the link name according to above SAP Note and 11202 is the original/physical path. So, the command should be -
    ln -s /oracle/<DBSID>/11202 /oracle/<DBSID>/112_64
    And the Result should be, 112_64 --> 11202 (in short)
    So, I think you should change the existing link, 11202->112_64
    Thanks

  • Oracle 9i RMAN backup filling up all disk and failing at the very end

    Hello to all and thank you in advance for any input from any of you.
    I am new in oracle and the only one in my company with a little bit of oracle knowledge, which is not a whole lot.
    I inherited a few servers (Linux and Windows based). We mostly run all our production environment on a Linux box hosting oracle 10g release 10.2.0.1 but we had a legacy application server that still runs on 9i release 9.2.0.1.0. This server is a windows 2003 box, the previous DBA or someone else with admin rights to this machine compressed the whole drive where oracle resides, when I started summarying the oracle assets, I saw this server with no backups scheduled and a compressed disk with very limited space after this compression, only 13 GB left, the database if uncompressed would definitively filled up all the disk. The machine is in used and cannot be taken down for more than a couple of hours. We tried adding another disk but the machine only accept it as a hot spare. The database is in archive mode, when I tried to run a RMAN backup, it start filling up the database drive until it's empty and it crashes the whole machine, it seems like the buffer is growing and growing until it fills up the whole drive. The only way to get the server up and running again is to reboot the machine since the server is more than 6 years old we are not please with this action because we are afraid the machine would go south in one of those reboots.
    Has anyone heard of similar issues when running RMAN on a compressed drive? Can the compressed disk have any involvement in this kind of odd behaviour? I tried running the backup in debug mode and creating a log in a different disk (the one where the backup is going to) and still the same issue. Again any help is much appreciate,
    Sincerely,
    Alex

    Sybrand,
    Thank you for your fast response, I am going to use your previous post to answer one by one your question,
    1 The Oracle binaries --- on a compressed drive > Yes
    2 The Oracle database control files redo log files and datafiles on that same compressed drive? > Yes
    3 The archived redo log ditto? > Yes
    I know for a fact (as I have been using that in 9i) you can create a RMAN backup on a compressed drive, and you can have your archived redo go to a compressed drive. No problemo! > Excellent good news!!!
    But I would never touch the data files. Please note backup sets are multiplexed files consisting of multiple datafiles, so RMAN would need to do some calculations to decompress several blocks at the same time and to calculate a new block and compress it.
    Do you have enough space to:
    a) (preferred) to make datafile copies instead of a backup >
    Not in the drive that hosts the oracle instance but yes on an external usb drive (1TB) I attached to use as a backup repository, maybe this is why I am having these issues. I only have 13 GB left on that drive where the oracle instance resides (actually as I explained in a previous reply to Mark, the server only has 3 slots for disks, two of them as configured as RAID 1 and the other is a hot spare because the RAID configuration manager cannot can only added as hot-spare. The raided disk are partitioned in two, one small partition is for the OS and the other is for the oracle instance). When you said make a copy of the datafiles, I assumed you are talking about doing manual backups, and copying the database after using using "alter tablespace tablespace_name begin backup; then copy the file; alter tablespace tablespace_name end backup;
    b) use filesperset=1 on the backup command line, so the multiplexing (and associated calculations) stop. I have not tried the option of fileperset yet but I can tryi it and see if that helps.
    Can you post the last few lines of the RMAN log where RMAN bombs out? Note: the last few lines. Not all of it, or you must send some paracetamol in conjunction! >
    When I ran the debug option, I stopped the backup at less than 20% because I didn't want to reboot the system in the middle of the production time, the backup consumed at least 3 GB during the time was running. The times I ran the RMAN backup I didn't used the debug option so I don't have a log long enough to send unless you want the last few lines of what I have.
    Thanks again for your input,
    Sincerely,
    Alex

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

Maybe you are looking for