ORA-279

when i am trying to recover the database i am getting ora-279 can any one help me how to go about this. Below is the snapshot from my alertlog file:
alter database recover if needed
start until cancel using backup controlfile
Media Recovery Start
ORA-279 signalled during: alter database recover if needed
start until cancel using backup controlfile
Mon Jul 9 16:19:08 2007
alter database recover cancel
Mon Jul 9 16:19:10 2007
Media Recovery Canceled
Completed: alter database recover cancel

Error: ORA 279
Text: change <num> generated at <name> needed for thread <num>
Cause: The requested log is required to proceed with recovery.
Action: Please specify the requested log in the command or cancel recovery.
Oracle Metalink Doc ID: Note:18348.1
Adith

Similar Messages

  • ORA-279 signalled during recovery of standby database

    Hi All,
    I am preparing standby database after taking hot backup and copying those datafiles to standby,
    taken controlfile standby controlfile backup from primary
    mounted the standby database using standby controlfile using
    startup nomount pfile='/u01/stand.ora'
    alter database mount standby database;
    Now I have started applying archives on standby database after copying all archives from primary to standby box the archives generated during backup using..
    recover standby database;
    But I am getting the below warning on the recovery screen...
    ORA-00279: change 51667629050 generated at 07/02/2009 00:59:43 needed for
    thread 1
    ORA-00289: suggestion : /nodal-archive/archive/1_55118_652209172.arc
    ORA-00280: change 51667629050 for thread 1 is in sequence #55118
    ORA-00278: log file '/nodal-archive/archive/1_55117_652209172.arc' no longer
    needed for this recovery
    ORA-00279: change 51667703096 generated at 07/02/2009 01:06:04 needed for
    thread 1
    ORA-00289: suggestion : /nodal-archive/archive/1_55119_652209172.arc
    ORA-00280: change 51667703096 for thread 1 is in sequence #55119
    ORA-00278: log file '/nodal-archive/archive/1_55118_652209172.arc' no longer
    needed for this recovery
    ORA-00279: change 51667767649 generated at 07/02/2009 01:12:28 needed for
    thread 1
    ORA-00289: suggestion : /nodal-archive/archive/1_55120_652209172.arc
    ORA-00280: change 51667767649 for thread 1 is in sequence #55120
    ORA-00278: log file '/nodal-archive/archive/1_55119_652209172.arc' no longer
    needed for this recovery
    ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for
    thread 1
    ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc
    ORA-00280: change 51667831821 for thread 1 is in sequence #55121
    ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer
    needed for this recovery
    and I am getting the below warning on the alert log..........
    Sun Jul 5 18:37:36 2009
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Sun Jul 5 18:37:36 2009
    Media Recovery Log /nodal-archive/archive/1_55256_652209172.arc
    Sun Jul 5 18:40:31 2009
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Sun Jul 5 18:40:31 2009
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Sun Jul 5 18:40:31 2009
    Media Recovery Log /nodal-archive/archive/1_55257_652209172.arc
    Please suggest what to do now.............
    Thanks in Advance,
    Sukanta Paul.

    Hi Sukanta,
    I didn't really understand what the problem is...
    Let me explain, hope it will be clear.
    You created a standby control file, and backed up the database (it doesn't matter in which order). Now, you have a standby database that is ready to apply logs. It will be able to apply log forever, until we will stop it.
    The messages you see say the following:
    ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for thread 1 {color:blue} - this says that the recovery process is now at scn 51667831821 {color}
    ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc {color:blue} - the information needed for the recover is in this file (this is only the default name, you can choose other name if the file is called differently) {color}
    ORA-00280: change 51667831821 for thread 1 is in sequence #55121 {color:blue} - same here, the needed archive is sequence 55121 {color}
    ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer needed for this recovery {color:blue} - this message is after Oracle has applied the log, and it means that this log is no longer needed {color}
    Now it will wait for the next log. Again, this process is endless, this is how it is made to allow the standby database to be always synched with the primary.
    Liron Amitzi
    Senior DBA consultant
    [www.dbsnaps.com]
    [www.orbiumsoftware.com]

  • ORA-279 signalled during: ALTER DATABASE RECOVER  automatic standby databas

    Hi,
    oracle server:8.1.7.0.0
    os:solaris 5.9
    we created standby server by taking coldbackup of primary server and we are using rsync to syschronize the archive log files between production and standby servers but every over we recover the standby server by executing
    sql>recover automatic standby database:
    but in alert log file i am getting the following error :
    but when i googled for ora-279 error some people says it is default behaviour and can it be ignored and why it is asking next logfile.
    Media Recovery Log /oratranslog/arch_1_1701118.arc
    Wed Mar 26 21:35:34 2008
    Media Recovery Log /oratranslog/arch_1_1701119.arc
    Wed Mar 26 21:35:54 2008
    Media Recovery Log /oratranslog/arch_1_1701120.arc
    ORA-279 signalled during: ALTER DATABASE RECOVER automatic standby database...
    Wed Mar 26 21:36:24 2008
    ALTER DATABASE RECOVER CANCEL
    Wed Mar 26 21:36:24 2008
    Media Recovery Cancelled
    Completed: ALTER DATABASE RECOVER CANCEL
    Thanks and Regards
    Prakash
    juniour oracle dba

    damorgan,
    He is running 8.1.7.0. "DataGuard" scripts were initially available for 9i and then
    backported (and available as a seperate download) for 8i. Many 8i implementations
    did not and do not use DataGuard.
    Even if it is "Jurassic" {which it certainly is NOT}, they obviously do have a good
    reason for setting up a standby -- they DO have data of value. So, maybe they have
    not upgraded to 9i or 10g. There could be a dozen reasons
    1. Server HW/OS doesn't support 9i/10g, not budgetting for Server upgrade
    2. Application using Forms 2.x or 4.5 and not tested on 9i / 10g (4.5 not certified
    on 9i)
    3. Low end client PCs working perfectly with Character-mode forms, not powerful
    enought to run Jinitiator and Forms 6i / 9i
    Just because someone hasn't upgraded to 10g doesn't mean that they are at fault
    when you do NOT know the reason why they have not upgraded.
    Surely, they do know that 8i is desupported. Don't you think that their management
    has undertaken due diligence / cost-benefit analysis in considering whether they
    should upgrade to 10g ?
    Maybe they have another project implementing 10g in parallel and will be able
    to shutdown this environment soon. Maybe they don't need to do so.
    Do understand that people are intelligent enough to make their own decisions
    considering their particular circumstances and don't go shooting off with your
    assumption that anyone not running 10g is a dinosaur.

  • 10g standard edition, create a manual standby without ORA-279 and ORA-308.

    Hi,
    I have a 10 g database 10g r2 on linux rhel 5.2. I've create a standby database from an rman backup on another server (same name, same path....).
    every 10 minutes , i switch log on primary database and rsync them to the stanby path on stanby server.
    every 10 minutes, i apply the new received archive to the standby database with this script :
    sqlplus /nolog
    connect / as sysdba
    recover database until cancel using backup controlfile;
    AUTO
    recover database until cancel using backup controlfile;
    CANCEL
    exit
    this script gives some ORA errors like this :
    2010/03/31 Wed 11:30:03 Media Recovery Log /v4/db/oradata/LFEX/archives/1_61705_640182036.dbf
    2010/03/31 Wed 11:30:03 ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    2010/03/31 Wed 11:30:04 ORA-279 signalled during: ALTER DATABASE RECOVER database until cancel using backup controlfile ...
    2010/03/31 Wed 11:40:01 ORA-279 signalled during: ALTER DATABASE RECOVER database until cancel using backup controlfile ...
    I understand this error, the script is searching the next archive, which doesn't exist at this time, that's OK.
    To avoid to have this error, i believe that i can do something like that:
    sqlplus /nolog
    connect / as sysdba
    recover database until time 'sysdate-1/(24*4)' using backup controlfile;
    AUTO
    exit
    i'm searching to replay the archive and stop 15 minutes before sysdate, Is it possible?
    when i try this, i have this message :
    SQL> recover database until time 'sysdate-1/(24*4)' using backup controlfile;
    ORA-01841: L'année (complète) doit être comprise entre -4713 et +9999 et être
    différente de 0.
    I'm trying to change nls_date_format, nls_lang without any success.
    thx.
    Antoine.

    i found a script to do an automatic recover script like this :
    recover database until time '2010-04-01:16:49:05' using backup controlfile;
    ORA-00279: changement 2456430208 généré à 04/01/2010 16:31:01 requis pour thread 1
    ORA-00289: suggestion : /v4/db/oradata/LFEX/archives/1_61853_640182036.dbf
    ORA-00280: le changement 2456430208 pour le thread 1 se trouve au no de séquence 61853
    ORA-00279: changement 2456432030 généré à 04/01/2010 16:39:01 requis pour thread 1
    ORA-00289: suggestion : /v4/db/oradata/LFEX/archives/1_61854_640182036.dbf
    ORA-00280: le changement 2456432030 pour le thread 1 se trouve au no de séquence 61854
    ORA-00278: le fichier journal
    '/v4/db/oradata/LFEX/archives/1_61853_640182036.dbf' n'est plus nécessaire pour cette récupération
    So i continue to have some error like ORA-278.... but no more ORA-308 error, it's better, because ORA-278 279 and 280 are only information messages, so i can ignore it in alert.log files.
    Only ORA-308 in this case interresting me, to see if an archive is really missing.
    thx.
    PS : the script standby_recover generate the recover.sql script :
    [dblegu@dbback SQL]$ cat $PGLEGU/SQL/standby_recover.sql
    connect sys/password as sysdba
    set trimspool on linesize 200 head off feedback off sqlprompt "--" verify off
    spool &1/SQL/recover.sql
    select 'connect sys/password as sysdba'||chr(10)||
    'set autorecovery on'||chr(10)||
    'recover database until time '''||
    to_char(sysdate - 1/(24*4),'YYYY-MM-DD:HH24:MI:SS')||''' using backup controlfile;'||chr(10)||
    'exit;' from dual;
    spool off
    exit
    the resul in recover.sql is :
    connect sys/password as sysdba
    set autorecovery on
    recover database until time '2010-04-01:16:49:05' using backup controlfile;
    exit;
    i found this on site : http://erkanorclog.blogspot.com/2007/08/batch-scripts-to-set-up-asyncronous.html.
    Edited by: fleuron on 1 avr. 2010 09:04

  • 恢复报错ORA-01139

    恢复报错ORA-01139
    从oracle 10g RAC （操作系统Enterprise Linux Enterprise Linux AS release 4 64bit)，数据库版本10.2.0.4环境中将数据备份恢复到相同环境的异机。
    向各位大牛请教！
    在做完不完全恢复时。
    recover database是正常的
    RMAN> sql'alter database open resetlogs';
    sql statement: alter database open resetlogs
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    ORA-01092: ORACLE instance terminated. Disconnection forced
    RMAN-03009: failure of sql command on default channel at 04/28/2013 09:09:05
    RMAN-11003: failure during parse/execution of SQL statement: alter database open resetlogs
    ORA-01041: internal error. hostdef extension doesn't exist
    ORACLE error from target database:
    ORA-03114: not connected to ORACLE
    接着我
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery。
    警告日志如下alter.log
    alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_2_47509_8qrwzjdm_.arc'
    Sun Apr 28 08:57:23 2013
    Media Recovery Log /home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_2_47509_8qrwzjdm_.arc
    ORA-279 signalled during: alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_2_47509_8qrwzjdm_.arc'...
    Sun Apr 28 08:57:23 2013
    alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_1_85650_8qrwz1b1_.arc'
    Sun Apr 28 08:57:23 2013
    Media Recovery Log /home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_1_85650_8qrwz1b1_.arc
    ORA-279 signalled during: alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_1_85650_8qrwz1b1_.arc'...
    Sun Apr 28 08:57:31 2013
    alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_1_85651_8qrwz1hk_.arc'
    Sun Apr 28 08:57:31 2013
    Media Recovery Log /home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_1_85651_8qrwz1hk_.arc
    ORA-279 signalled during: alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_1_85651_8qrwz1hk_.arc'...
    Sun Apr 28 08:57:31 2013
    alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_2_47510_8qrwzjm2_.arc'
    Sun Apr 28 08:57:31 2013
    Media Recovery Log /home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_2_47510_8qrwzjm2_.arc
    ORA-279 signalled during: alter database recover logfile '/home/backup/flash_recovery_area/LD/archivelog/2013_04_28/o1_mf_2_47510_8qrwzjm2_.arc'...
    Sun Apr 28 08:57:31 2013
    alter database recover cancel
    Sun Apr 28 08:57:37 2013
    Media Recovery Canceled
    Completed: alter database recover cancel
    Sun Apr 28 09:04:15 2013
    alter database rename file '+DATADG/ld/redo01a.log' to '/home/backup/oradata/ld/redo1a.log'
    Sun Apr 28 09:04:15 2013
    Starting control autobackup
    ******************** WARNING ***************************
    The errors during Server autobackup are not fatal, as it
    is attempted after sucessful completion of the command.
    However, it is recomended to take an RMAN control file
    backup as soon as possible because the Autobackup failed
    with the following error:
    ORA-00236: snapshot operation disallowed: mounted control file is a backup
    with the following error:
    ORA-00236: snapshot operation disallowed: mounted control file is a backup
    ******************** END OF WARNING *******************
    Completed: alter database rename file '+DATADG/ld/redo03a.log' to '/home/backup/oradata/ld/redo3a.log'
    Sun Apr 28 09:05:32 2013
    alter database rename file '+DATADG/ld/redo03b.log' to '/home/backup/oradata/ld/redo3b.log'
    Starting control autobackup
    ******************** WARNING ***************************
    The errors during Server autobackup are not fatal, as it
    is attempted after sucessful completion of the command.
    However, it is recomended to take an RMAN control file
    backup as soon as possible because the Autobackup failed
    with the following error:
    ORA-00236: snapshot operation disallowed: mounted control file is a backup
    ******************** END OF WARNING *******************
    Completed: alter database rename file '+DATADG/ld/redo03b.log' to '/home/backup/oradata/ld/redo3b.log'
    Sun Apr 28 09:05:42 2013
    alter database rename file '+DATADG/ld/redo04a.log' to '/home/backup/oradata/ld/redo4a.log'
    Sun Apr 28 09:05:42 2013
    Starting control autobackup
    ******************** WARNING ***************************
    The errors during Server autobackup are not fatal, as it
    is attempted after sucessful completion of the command.
    However, it is recomended to take an RMAN control file
    backup as soon as possible because the Autobackup failed
    with the following error:
    ORA-00236: snapshot operation disallowed: mounted control file is a backup
    ******************** END OF WARNING *******************
    Completed: alter database rename file '+DATADG/ld/redo04a.log' to '/home/backup/oradata/ld/redo4a.log'
    Sun Apr 28 09:05:50 2013
    alter database rename file '+DATADG/ld/redo04b.log' to '/home/backup/oradata/ld/redo4b.log'
    Starting control autobackup
    ******************** WARNING ***************************
    The errors during Server autobackup are not fatal, as it
    is attempted after sucessful completion of the command.
    However, it is recomended to take an RMAN control file
    backup as soon as possible because the Autobackup failed
    with the following error:
    ORA-00236: snapshot operation disallowed: mounted control file is a backup
    Sun Apr 28 09:10:00 2013
    Successful mount of redo thread 1, with mount id 2474343140
    Sun Apr 28 09:10:00 2013
    Database mounted in Exclusive Mode
    Completed: ALTER DATABASE MOUNT
    Sun Apr 28 09:10:09 2013
    alter database open resetlogs
    ORA-1139 signalled during: alter database open resetlogs...
    xx_ora_30570.trc日志如下
    /opt/app/oracle/admin/ld/udump/xx_ora_30570.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORACLE_HOME = /opt/app/oracle/product/10.2.0/db_1
    System name:     Linux
    Node name:     ldTest
    Release:     2.6.9-67.0.0.0.1.ELsmp
    Version:     #1 SMP Sun Nov 18 01:06:10 EST 2007
    Machine:     x86_64
    Instance name: ld
    Redo thread mounted by this instance: 1
    Oracle process number: 14
    Unix process pid: 30570, image: oracle@ldTest (TNS V1-V3)
    *** 2013-04-27 20:39:32.112
    *** ACTION NAME:(0000005 STARTED124) 2013-04-27 20:39:32.112
    *** MODULE NAME:(rman@ldTest (TNS V1-V3)) 2013-04-27 20:39:32.112
    *** SERVICE NAME:() 2013-04-27 20:39:32.112
    *** SESSION ID:(542.8) 2013-04-27 20:39:32.112
    Control file resized from 4322 to 4412 blocks
    kccrsd_append: rectype = 13, lbn = 2161, recs = 1000
    *** 2013-04-27 22:47:07.275
    *** ACTION NAME:(0000139 STARTED60) 2013-04-27 22:47:07.275
    2013-04-27 22:47:07.275: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:07.279: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:07.279: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:07.279: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:07.279: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/system01.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/system01.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000140 STARTED60) 2013-04-27 22:47:07.375
    2013-04-27 22:47:07.375: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:07.375: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:07.375: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:07.375: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:07.375: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/undotbs01.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/undotbs01.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000141 STARTED60) 2013-04-27 22:47:07.462
    2013-04-27 22:47:07.462: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:07.462: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:07.462: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:07.462: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:07.462: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/sysaux01.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/sysaux01.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000142 STARTED60) 2013-04-27 22:47:07.538
    2013-04-27 22:47:07.538: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:07.538: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:07.538: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:07.538: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:07.538: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/undotbs02.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/undotbs02.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000143 STARTED60) 2013-04-27 22:47:07.603
    2013-04-27 22:47:07.603: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:07.604: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:07.604: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:07.604: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:07.604: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/users01.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/users01.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000144 STARTED60) 2013-04-27 22:47:07.660
    2013-04-27 22:47:07.660: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:07.660: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:07.660: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:07.660: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:07.660: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/sale_ix01.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale_ix01.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000145 STARTED60) 2013-04-27 22:47:07.741
    2013-04-27 22:47:07.741: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:07.741: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:07.741: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:07.741: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:07.741: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/sale01.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale01.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000146 STARTED60) 2013-04-27 22:47:07.829
    2013-04-27 22:47:07.829: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:07.829: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:07.829: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:07.829: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:07.829: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/cpc01.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/cpc01.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000147 STARTED60) 2013-04-27 22:47:07.974
    2013-04-27 22:47:07.974: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:07.974: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:07.974: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:07.974: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:07.974: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/cpc_ix01.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/cpc_ix01.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000148 STARTED60) 2013-04-27 22:47:08.073
    2013-04-27 22:47:08.073: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:08.073: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:08.073: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:08.073: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:08.073: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/sale02.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale02.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000149 STARTED60) 2013-04-27 22:47:08.168
    2013-04-27 22:47:08.168: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:08.168: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:08.168: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:08.168: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:08.168: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/sale_ix02.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale_ix02.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000150 STARTED60) 2013-04-27 22:47:08.295
    2013-04-27 22:47:08.295: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:08.295: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:08.295: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:08.295: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:08.295: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/sale03.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale03.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000151 STARTED60) 2013-04-27 22:47:08.396
    2013-04-27 22:47:08.396: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:08.396: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:08.396: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:08.396: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:08.396: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/sale04.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale04.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000152 STARTED60) 2013-04-27 22:47:08.488
    2013-04-27 22:47:08.488: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:08.488: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:08.488: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:08.488: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:08.488: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/sale05.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/sale05.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000153 STARTED60) 2013-04-27 22:47:08.587
    2013-04-27 22:47:08.587: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:08.587: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:08.587: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:08.587: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:08.587: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/f_data01.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/f_data01.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000154 STARTED60) 2013-04-27 22:47:08.669
    2013-04-27 22:47:08.669: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:08.669: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:08.669: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:08.669: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:08.670: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/f_data02.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/f_data02.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000155 STARTED60) 2013-04-27 22:47:08.771
    2013-04-27 22:47:08.771: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:08.771: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:08.771: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:08.771: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:08.771: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/f_ix01.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/f_ix01.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000156 STARTED60) 2013-04-27 22:47:08.886
    2013-04-27 22:47:08.886: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:08.886: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:08.886: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:08.886: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:08.886: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/f_ix02.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/f_ix02.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000157 STARTED60) 2013-04-27 22:47:08.999
    2013-04-27 22:47:08.999: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:08.999: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:08.999: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:08.999: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:08.999: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/f_data03.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/f_data03.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000158 STARTED60) 2013-04-27 22:47:09.096
    2013-04-27 22:47:09.096: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:09.096: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:09.096: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:09.096: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:09.096: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/f_data04.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/f_data04.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    *** ACTION NAME:(0000159 STARTED60) 2013-04-27 22:47:09.150
    2013-04-27 22:47:09.150: [  OCROSD]utgdv:2:ocr loc file cannot be opened
    2013-04-27 22:47:09.150: [  OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file
    2013-04-27 22:47:09.150: [  OCRRAW]proprinit: Could not open raw device
    2013-04-27 22:47:09.150: [ default]a_init:7!: Backend init unsuccessful : [33]
    2013-04-27 22:47:09.150: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization
    kgxgncin: CLSS init failed with status 21
    ORA-19625: error identifying file +DATADG/users02.dbf
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/users02.dbf
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    ORA-29701: unable to connect to Cluster Manager
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/home/backup/oradata/ld/redo1b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/home/backup/oradata/ld/redo1a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/home/backup/oradata/ld/redo1b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/home/backup/oradata/ld/redo1a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    logfile 1 open failed:313
    *** 2013-04-28 09:08:35.897 3950 kcrr.c
    Archiving online redo logfile /home/backup/oradata/ld/redo2b.log
    WARNING: Archival will be performed using 2 passes.
    The first pass will attempt to determine the end-of-file
    of the online redo logfile. The end-of-file is determined
    by identifying what is described as a "corrupt" block
    header. This will be reported as an ORA-00354 error.
    However, this is not really a corrupt block - it is the
    end of the redo data.
    The second pass will then archive the online redo logfile
    using the identified end-of-file information.
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/home/backup/oradata/ld/redo2b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/home/backup/oradata/ld/redo2a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/home/backup/oradata/ld/redo2b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/home/backup/oradata/ld/redo2a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    logfile 2 open failed:313
    *** 2013-04-28 09:08:35.898 3950 kcrr.c
    Archiving online redo logfile /home/backup/oradata/ld/redo3b.log
    WARNING: Archival will be performed using 2 passes.
    The first pass will attempt to determine the end-of-file
    of the online redo logfile. The end-of-file is determined
    by identifying what is described as a "corrupt" block
    header. This will be reported as an ORA-00354 error.
    However, this is not really a corrupt block - it is the
    end of the redo data.
    The second pass will then archive the online redo logfile
    using the identified end-of-file information.
    请教如何解决ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery。谢谢

    Hello Aman,
    Sorry couldn't give all information in frustration.
    Oracle version is 9.2.0.1.0 running on Red Hat 4
    Actually i did TPITR and have to open database with resetlogoption recovery was successful but while opening received this error.
    Database dismounted.
    ORACLE instance shut down.
    SQL> STARTUP NOMOUNT PFILE=/oracle/prdtpi/pfile/prdtpi;
    ORACLE instance started.
    Total System Global Area 798040164 bytes
    Fixed Size 454756 bytes
    Variable Size 478150656 bytes
    Database Buffers 318767104 bytes
    Redo Buffers 667648 bytes
    SQL> alter database mount clone database;
    SQL> RECOVER AUTOMATIC DATABASE UNTIL CHANGE 3997955 USING BACKUP CONTROLFILE;
    ORA-00283: recovery session canceled due to errors
    ORA-00264: no recovery required
    SQL> alter database datafile 1 online;
    Database altered.
    SQL> ed
    Wrote file afiedt.buf
    1* alter database datafile 12 online
    SQL> /
    Database altered.
    SQL> ed
    Wrote file afiedt.buf
    1* alter database datafile 13 online
    SQL> /
    Database altered.
    SQL> RECOVER AUTOMATIC DATABASE UNTIL CHANGE 3997955 USING BACKUP CONTROLFILE;
    Media recovery complete.
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    SQL> ALTER DATABASE OPEN RESETLOGS;
    ALTER DATABASE OPEN RESETLOGS
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery

  • ERROR in 9i standby - ORA-01153

    Hi,
    I am getting error while firing
    "recover standby database " command in my 9i standby.
    We are manually moving the archivelogs to standby from production, and firing the above command. All are done thru scheduled scripts .
    We have a recovery_run log file, with the detailed description of the recovery process running at standby.
    ----------The following is an extract from the alert log file.---------------
    Media Recovery Log /oracle/P71/saparch/P71arch1_334825.dbf
    Wed Dec 7 13:46:16 2005
    ALTER DATABASE RECOVER standby database
    Wed Dec 7 13:46:16 2005
    ORA-1153 signalled during: ALTER DATABASE RECOVER standby database ...
    Wed Dec 7 13:46:18 2005
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Wed Dec 7 13:46:18 2005
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Media Recovery Log /oracle/P71/saparch/P71arch1_334826.dbf
    Wed Dec 7 13:47:03 2005
    ALTER DATABASE RECOVER standby database
    Wed Dec 7 13:47:03 2005
    ORA-1153 signalled during: ALTER DATABASE RECOVER standby database ...
    Wed Dec 7 13:47:27 2005
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Wed Dec 7 13:47:27 2005
    --------The following is an extract from the Recovery_run log file.----------
    SQL*Plus: Release 9.2.0.5.0 - Production on Wed Dec 7 13:51:29 2005
    SQL> Connected.
    SQL> ORA-01153: an incompatible media recovery is active
    SQL> SP2-0042: unknown command "auto" - rest of line ignored.
    SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
    With the Partitioning option
    JServer Release 9.2.0.5.0 - Production
    Wed Dec 7 13:51:31 NFT 2005
    SQL*Plus: Release 9.2.0.5.0 - Production on Wed Dec 7 13:52:00 2005
    SQL> Connected.
    SQL> ORA-01153: an incompatible media recovery is active
    SQL> SP2-0042: unknown command "auto" - rest of line ignored.
    SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
    With the Partitioning option
    JServer Release 9.2.0.5.0 - Production
    Wed Dec 7 13:52:01 NFT 2005
    -------------The following is extract from the script that fires the recovery command-------------
    auto_recover()
    echo "connect / as sysdba" > /tmp/reco.sql
    echo "recover standby database " >> /tmp/reco.sql
    echo "auto" >> /tmp/reco.sql
    echo "exit" >> /tmp/reco.sql
    su - ${ORAUSER} -c sqlplus "/NOLOG" < /tmp/reco.sql | grep -v "Corpo" | grep -v "Manager"
    i checked the v$lock, and found that there is only one active session, which is holding the MR locks.
    It was working fine, and today we started getting this error
    Any idea about what is happening over here?
    Thanks in advance,
    Don

    At the standby, i also checked
    SQL> select max(sequence#) from v$log_history;
    And the max sequence number is getting incremented.
    That means, the archive logs are getting applied in the standby perfectly... right?
    But, how can that happen, since we are getting error while this command is run from the script?
    please help me out , to solve this issue.
    Thanks in advance,
    Don

  • MANAGED RECOVERY AT STANDBY DATABASE REQURING OLD ARCHIVELOGS ORA-00308

    Oracle 9.2.0.4
    HP-UX 11.11i
    The database in Archivelog mode, single standby database in managed recovery
    mode.
    keeping standby in sync with manual applying the ARCHIVELOG from primary to
    standby database.
    primary database was 3 REDO log members of 100 MB with 1 member each.
    what i did, 1 drop and re-create the INACTIVE REDO group for all three, and
    make them
    5 REDO logs of 200 MB with 1 member each,
    then in order to keep fresh copy of primary database onto standby database, i
    send the cold backup after 15 days (last week) with standby controlfile.
    now, with that standby controlfile and the database, i can mount the database
    but while to open the database, receives messages as , it requiring the
    ARCHIVELOGS generated log time ago.
    changes the REDO groups from 3 to 5 and size 100 to 200 MB at INACTIVE state
    ### Workarounds Used ###
    SQL> alter database mount standby database;
    Database altered.
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-16004: backup database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/user01/oracle9i/oradata/iobasprd/system01.dbf'
    SQL> alter database recover automatic standby database;
    alter database recover automatic standby database
    ERROR at line 1:
    ORA-00279: change 1655989696 generated at 08/12/2005 12:46:25 needed for thread
    1
    ORA-00289: suggestion :
    /user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf
    ORA-00280: change 1655989696 for thread 1 is in sequence #16849
    ORA-00278: log file
    '/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf' no longer needed
    for this recovery
    ORA-00308: cannot open archived log
    '/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf'
    ORA-27037: unable to obtain file status
    HP-UX Error: 2: No such file or directory
    Additional information: 3
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /user02/oracle9i/oradata/iobasprd/archive
    Oldest online log sequence 53052
    Next log sequence to archive 53056
    Current log sequence
    53056
    -----------------------AlertIOBASPRD.log----------------------------
    alter database mount standby database
    Mon Oct 24 12:05:05 2005
    Successful mount of redo thread 1, with mount id 3283884781.
    Mon Oct 24 12:05:05 2005
    Standby Database mounted.
    Completed: alter database mount standby database
    Mon Oct 24 12:05:12 2005
    alter database open read only
    ORA-16004 signalled during: alter database open read only...
    Mon Oct 24 12:05:23 2005
    alter database recover automatic standby database
    Mon Oct 24 12:05:23 2005
    Media Recovery Start
    Starting datafile 1 recovery in thread 1 sequence 52617
    Datafile 1: '/user01/oracle9i/oradata/iobasprd/system01.dbf'
    Starting datafile 2 recovery in thread 1 sequence 52617
    Datafile 2: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_005.dbf'
    Starting datafile 3 recovery in thread 1 sequence 52617
    Datafile 3: '/user01/oracle9i/oradata/iobasprd/drsys01.dbf'
    Starting datafile 4 recovery in thread 1 sequence 52617
    Datafile 132: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_002.dbf'
    Starting datafile 133 recovery in thread 1 sequence 52617
    Datafile 133: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_003.dbf'
    Starting datafile 134 recovery in thread 1 sequence 52617
    Datafile 134: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_004.dbf'
    Media Recovery Log
    Media Recovery Log /user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf
    Errors with log /user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf.
    ORA-279 signalled during: alter database recover automatic standby database...
    Mon Oct 24 12:06:01 2005
    Restarting dead background process QMN0
    QMN0 started with pid=9
    The snap of alertIOBASPRD.log can understand me that it requiring the
    ARCHIVELOG 52617 only
    and its lying in LOG_ARCHIVE_DET location also as
    $ pwd
    /user02/oracle9i/oradata/iobasprd/archive
    $ ls archive_5261*.dbf
    archive_52610.dbf archive_52613.dbf archive_52616.dbf archive_52619.dbf
    archive_52611.dbf archive_52614.dbf archive_52617.dbf
    archive_52612.dbf archive_52615.dbf archive_52618.dbf
    $
    now, even the files are lying , why ORACLE requing the old archive logs ?????

    You haven't given any usefuly information on your problem.
    show parameter log_archive_dest
    show parameter fal
    show parameter dg
    What errors are in your alert logs ?
    What command are you using to recover ?
    Check the contents of v$archived_log
    # run on primary to detect failures :-
    select destination, status, fail_date, valid_now
    from v$archive_dest
    where status != 'VALID' or VALID_NOW != 'YES';
    # run on standby to get exact position of rollforward :-
    select thread#, to_char(snapshot_time,'dd-mon-yyyy:hh24:mi'),
    to_char(applied_time,'dd-mon-yyyy:hh24:mi'),
    to_char(newest_time,'dd-mon-yyyy:hh24:mi') from V$STANDBY_APPLY_SNAPSHOT;
    Are you using dataguard broker ?

  • Crash - recovery problem - ora-1113

    Hi,
    Because of the hardware problems, my database server has crashed. Database (8.1.7) works in archive log.
    Before the crash, the last log switch seq# was 17173:
    ARC2: Beginning to archive log# 12 seq# 17173
    ARC2: Completed archiving log# 12 seq# 17173
    After the crash I tried to open it, counting on automatic revovery. SMON started to do roll-forward etc., but suddenly got an error:
    alter database open
    ORA-1113 signalled during: alter database open ...
    I tried to use until cancel recovery:
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Media Recovery Log F:\ORACLE\PEL\SAPARCH\PELARCHARC17171.001
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Tue Jul 01 22:51:27 2003
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Media Recovery Log F:\ORACLE\PEL\SAPARCH\PELARCHARC17172.001
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Tue Jul 01 22:51:32 2003
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Media Recovery Log F:\ORACLE\PEL\SAPARCH\PELARCHARC17173.001
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Tue Jul 01 22:51:38 2003
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Media Recovery Log F:\ORACLE\PEL\SAPARCH\PELARCHARC17174.001
    ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...Tue Jul 01 22:51:38 2003
    ALTER DATABASE RECOVER CANCEL
    ORA-1547 signalled during: ALTER DATABASE RECOVER CANCEL...
    The problem is, that the redo-log seq# 17174 do not exists...
    I do not understand, what happened, why the information couldn't be read from online redo logs if they exist...?
    I had to do point-in-time recovery, now the database works OK, but still don't know why Oracle wanted to use log #17174? Any ideas?
    James

    The ORa-1113 error means that your Backup implementation ("Retrospect") does an ALTER TABLESPACE BEGIN BACKUP and END BACKUP for each tablespace.
    In 8i, you would not have the "ALTER DATABASE END BACKUP" command. Nor the "ALTER DATABASE DATAFILE .. END BACKUP".
    What you would do is :
    1. Start the service.
    2. Go to Windows command line prompt as the Administrator or account in the OS_DBA group (with the right ORACLE_SID, ORACLE_HOME and PATH)
    3. sqlplus / as sysdba
    4. startup mount -- or ALTER DATABASE MOUNT if it did get started but not mounted
    5. ALTER TABLESPACE (tablespacename_that_was_in_backup_mode) END BACKUP ;
    (if there were multiple tablespaces in backup mode, issue the END BACKUP for each one of them)
    6. ALTER DATABASE OPEN ;
    The other option to step 5 is the "RECOVER DATABASE" . Oracle may apply archivelogs to synchronise the datafiles back.

  • ORA-00308: cannot open archived log '+DATA'

    Hello all,
    I created new physical standby but I facing problem with shipping archived file between primary and standby.
    Primary : RAC (4 nodes)
    Standby : single node with ASM
    when I run :
    alter database recover managed standby database disconnect from session;
    in alert log file :
    Managed Standby Recovery not using Real Time Apply
    Parallel Media Recovery started with 24 slaves
    Waiting for all non-current ORLs to be archived...
    All non-current ORLs have been archived.
    Media Recovery Waiting for thread 1 sequence 25738
    Tue Mar 03 12:21:13 2015
    Completed: alter database recover managed standby database disconnect from session
    and when i checked archived files by
    select max(sequence#)  from v$archivanded_log;
    It was null.
    I understand thatno shipping between primary and standby till this point i deiced to use manual recovery by :
    alter database recover automatic standby database;
    But i get this error in alert log file :
    alter database recover automatic standby database
    Media Recovery Start
    started logmerger process
    Tue Mar 03 12:38:38 2015
    Managed Standby Recovery not using Real Time Apply
    Parallel Media Recovery started with 24 slaves
    Media Recovery Log +DATA
    Errors with log +DATA
    Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4989.trc:
    ORA-00308: cannot open archived log '+DATA'
    ORA-17503: ksfdopn:2 Failed to open file +DATA
    ORA-15045: ASM file name '+DATA' is not in reference form
    ORA-279 signalled during: alter database recover automatic standby database..
    when i opened oracledrs_pr00_4989.trc: file i find :
    *** 2015-03-03 12:38:39.478
    Media Recovery add redo thread 4
    ORA-00308: cannot open archived log '+DATA'
    ORA-17503: ksfdopn:2 Failed to open file +DATA
    ORA-15045: ASM file name '+DATA' is not in reference form
    When I created i set these parameter in duplicate command:
    set db_file_name_convert='+ASM_ORADATA/oracle','+DATA/oracledrs'
    set log_file_name_convert='+ASM_ARCHIVE/oracle','+DATA/oracledrs','+ASM_ORADATA/oracle','+DATA/oracledrs'
    set control_files='+DATA'
    set db_create_file_dest='+DATA'
    set db_recovery_file_dest='+DATA'
    What please the mistake here
    Thanks in advance,

    Yes I have datafiles under +DATA
    ASMCMD> cd +DATA/ORACLEDRS/DATAFILE
    ASMCMD> ls
    ASD.282.873258045
    CATALOG.288.873258217
    DEVTS.283.873258091
    EXAMPLE.281.873258043
    FEED.260.873227069
    FEED.279.873257713
    INDX.272.873251345
    INDX.273.873252239
    INDX.278.873257337
    SYSAUX.262.873227071
    SYSTEM.277.873256531
    SYSTEM_2.280.873257849
    TB_WEBSITE.284.873258135
    TB_WEBSITE.285.873258135
    TB_WEBSITE.286.873258181
    TB_WEBSITE.287.873258183
    UNDOTBS1.275.873253421
    UNDOTBS2.276.873255247
    UNDOTBS3.261.873227069
    UNDOTBS4.271.873245967
    USERS.263.873227071
    USERS.264.873235507
    USERS.265.873235893
    USERS.266.873237079
    USERS.267.873238225
    USERS.268.873243661
    USERS.269.873244307
    USERS.270.873244931
    USERS.274.873252585
    asd01.dbf
    catalog01
    dev01.dbf
    example.dbf
    feed01.dbf
    feed02.dbf
    indx01.dbf
    indx02.dbf
    indx03.dbf
    sysaux01.dbf
    system01.dbf
    system02.dbf
    undotbs01.dbf
    undotbs02.dbf
    undotbs03.dbf
    undotbs04.dbf
    user1.dbf
    users01.dbf
    users02.dbf
    users03.dbf
    users04.dbf
    users05.dbf
    users06.dbf
    users07.dbf
    users08.dbf
    website01.dbf
    website02.dbf
    website03.dbf
    website04.dbf
    ASMCMD>
    Standby :
    [root@oracledrs ~]# id oracle
    uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)
    Primary :
    [root@dbn-prod-1 disks]# id oracle
    uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)
    1- yes i have needed archived files at my primary
    2-  select inst_id,thread#,group# from gv$log;
    Primary :
    INST_ID,THREAD#,GROUP#
    1,1,1
    1,1,2
    1,2,3
    1,2,4
    1,3,5
    1,3,6
    1,4,7
    1,4,8
    1,1,9
    1,2,10
    1,3,11
    1,4,12
    3,1,1
    3,1,2
    3,2,3
    3,2,4
    3,3,5
    3,3,6
    3,4,7
    3,4,8
    3,1,9
    3,2,10
    3,3,11
    3,4,12
    2,1,1
    2,1,2
    2,2,3
    2,2,4
    2,3,5
    2,3,6
    2,4,7
    2,4,8
    2,1,9
    2,2,10
    2,3,11
    2,4,12
    4,1,1
    4,1,2
    4,2,3
    4,2,4
    4,3,5
    4,3,6
    4,4,7
    4,4,8
    4,1,9
    4,2,10
    4,3,11
    4,4,12
    Standby :
    INST_ID,THREAD#,GROUP#
    1,1,9
    1,1,2
    1,1,1
    1,2,3
    1,2,4
    1,2,10
    1,3,5
    1,3,6
    1,3,11
    1,4,12
    1,4,7
    1,4,8
    3- That's sample from alert log since i started the standby (for standby and primary)
    Standby :
    alter database mount standby database
    NOTE: Loaded library: /opt/oracle/extapi/64/asm/orcl/1/libasm.so
    NOTE: Loaded library: System
    SUCCESS: diskgroup DATA was mounted
    ERROR: failed to establish dependency between database oracledrs and diskgroup resource ora.DATA.dg
    ARCH: STARTING ARCH PROCESSES
    Tue Mar 03 18:38:16 2015
    ARC0 started with pid=128, OS id=4461
    ARC0: Archival started
    ARCH: STARTING ARCH PROCESSES COMPLETE
    ARC0: STARTING ARCH PROCESSES
    Tue Mar 03 18:38:17 2015
    Successful mount of redo thread 1, with mount id 1746490068
    Physical Standby Database mounted.
    Lost write protection disabled
    Tue Mar 03 18:38:17 2015
    ARC1 started with pid=129, OS id=4464
    Tue Mar 03 18:38:17 2015
    ARC2 started with pid=130, OS id=4466
    Tue Mar 03 18:38:17 2015
    ARC3 started with pid=131, OS id=4468
    Tue Mar 03 18:38:17 2015
    ARC4 started with pid=132, OS id=4470
    Tue Mar 03 18:38:17 2015
    ARC5 started with pid=133, OS id=4472
    Tue Mar 03 18:38:17 2015
    ARC6 started with pid=134, OS id=4474
    Tue Mar 03 18:38:17 2015
    ARC7 started with pid=135, OS id=4476
    Completed: alter database mount standby database
    Tue Mar 03 18:38:17 2015
    ARC8 started with pid=136, OS id=4478
    Tue Mar 03 18:38:17 2015
    ARC9 started with pid=137, OS id=4480
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC8: Becoming the 'no FAL' ARCH
    ARC2: Becoming the heartbeat ARCH
    ARC2: Becoming the active heartbeat ARCH
    Tue Mar 03 18:38:18 2015
    Starting Data Guard Broker (DMON)
    ARC9: Archival started
    ARC0: STARTING ARCH PROCESSES COMPLETE
    Tue Mar 03 18:38:23 2015
    INSV started with pid=141, OS id=4494
    Tue Mar 03 18:39:11 2015
    alter database recover managed standby database disconnect from session
    Attempt to start background Managed Standby Recovery process (oracledrs)
    Tue Mar 03 18:39:11 2015
    MRP0 started with pid=142, OS id=4498
    MRP0: Background Managed Standby Recovery process started (oracledrs)
    started logmerger process
    Tue Mar 03 18:39:16 2015
    Managed Standby Recovery not using Real Time Apply
    Parallel Media Recovery started with 24 slaves
    Waiting for all non-current ORLs to be archived...
    All non-current ORLs have been archived.
    Media Recovery Waiting for thread 1 sequence 25738
    Completed: alter database recover managed standby database disconnect from session
    Tue Mar 03 18:41:17 2015
    WARN: ARCH: Terminating pid 4476 hung on an I/O operation
    Killing 1 processes with pids 4476 (Process by index) in order to remove hung processes. Requested by OS process 4224
    ARCH: Detected ARCH process failure
    Tue Mar 03 18:45:17 2015
    ARC2: STARTING ARCH PROCESSES
    Tue Mar 03 18:45:17 2015
    ARC7 started with pid=127, OS id=4586
    Tue Mar 03 18:45:18 2015
    Fatal NI connect error 12170.
      VERSION INFORMATION:
            TNS for Linux: Version 11.2.0.4.0 - Production
            Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
      Time: 03-MAR-2015 18:45:18
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12535
    TNS-12535: TNS:operation timed out
        ns secondary err code: 12560
        nt main err code: 505
    TNS-00505: Operation timed out
        nt secondary err code: 0
        nt OS err code: 0
      Client address: <unknown>
    ARC7: Archival started
    ARC2: STARTING ARCH PROCESSES COMPLETE
    Tue Mar 03 18:47:14 2015
    alter database recover managed standby database cancel
    Tue Mar 03 18:48:18 2015
    Fatal NI connect error 12170.
      VERSION INFORMATION:
            TNS for Linux: Version 11.2.0.4.0 - Production
            Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
      Time: 03-MAR-2015 18:48:18
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12535
    TNS-12535: TNS:operation timed out
        ns secondary err code: 12560
        nt main err code: 505
    TNS-00505: Operation timed out
        nt secondary err code: 0
        nt OS err code: 0
      Client address: <unknown>
    Tue Mar 03 18:51:18 2015
    Fatal NI connect error 12170.
      VERSION INFORMATION:
            TNS for Linux: Version 11.2.0.4.0 - Production
            Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
      Time: 03-MAR-2015 18:51:18
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12535
    TNS-12535: TNS:operation timed out
        ns secondary err code: 12560
        nt main err code: 505
    TNS-00505: Operation timed out
        nt secondary err code: 0
        nt OS err code: 0
      Client address: <unknown>
    Error 12170 received logging on to the standby
    FAL[client, USER]: Error 12170 connecting to oracle for fetching gap sequence
    MRP0: Background Media Recovery cancelled with status 16037
    Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4500.trc:
    ORA-16037: user requested cancel of managed recovery operation
    Recovery interrupted!
    Tue Mar 03 18:51:18 2015
    MRP0: Background Media Recovery process shutdown (oracledrs)
    Tue Mar 03 18:51:19 2015
    Managed Standby Recovery Canceled (oracledrs)
    Completed: alter database recover managed standby database cancel
    Tue Mar 03 18:51:56 2015
    alter database recover automatic standby database
    Media Recovery Start
    started logmerger process
    Tue Mar 03 18:51:56 2015
    Managed Standby Recovery not using Real Time Apply
    Parallel Media Recovery started with 24 slaves
    Media Recovery Log +DATA
    Errors with log +DATA
    Errors in file /u01/app/oracle/diag/rdbms/oracledrs/oracledrs/trace/oracledrs_pr00_4617.trc:
    ORA-00308: cannot open archived log '+DATA'
    ORA-17503: ksfdopn:2 Failed to open file +DATA
    ORA-15045: ASM file name '+DATA' is not in reference form
    ORA-279 signalled during: alter database recover automatic standby database...
    Tue Mar 03 18:53:06 2015
    db_recovery_file_dest_size of 512000 MB is 0.13% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Primary :
    Tue Mar 03 17:13:43 2015
    Thread 1 advanced to log sequence 26005 (LGWR switch)
      Current log# 1 seq# 26005 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 17:13:44 2015
    Archived Log entry 87387 added for thread 1 sequence 26004 ID 0x66aa5a0d dest 1:
    Tue Mar 03 18:00:18 2015
    Thread 1 advanced to log sequence 26006 (LGWR switch)
      Current log# 2 seq# 26006 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Tue Mar 03 18:00:18 2015
    Archived Log entry 87392 added for thread 1 sequence 26005 ID 0x66aa5a0d dest 1:
    Tue Mar 03 18:55:33 2015
    Thread 1 advanced to log sequence 26007 (LGWR switch)
      Current log# 9 seq# 26007 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26007 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Tue Mar 03 18:55:33 2015
    Archived Log entry 87395 added for thread 1 sequence 26006 ID 0x66aa5a0d dest 1:
    Tue Mar 03 19:14:22 2015
    Dumping diagnostic data in directory=[cdmp_20150303191422], requested by (instance=4, osid=10234), summary=[incident=1692472].
    Dumping diagnostic data in directory=[cdmp_20150303191425], requested by (instance=4, osid=10234), summary=[incident=1692473].
    Tue Mar 03 20:00:06 2015
    Thread 1 advanced to log sequence 26008 (LGWR switch)
      Current log# 1 seq# 26008 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 20:00:07 2015
    Archived Log entry 87401 added for thread 1 sequence 26007 ID 0x66aa5a0d dest 1:
    Tue Mar 03 21:00:02 2015
    Thread 1 advanced to log sequence 26009 (LGWR switch)
      Current log# 2 seq# 26009 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Tue Mar 03 21:00:03 2015
    Archived Log entry 87403 added for thread 1 sequence 26008 ID 0x66aa5a0d dest 1:
    Thread 1 advanced to log sequence 26010 (LGWR switch)
      Current log# 9 seq# 26010 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26010 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Tue Mar 03 21:00:06 2015
    Archived Log entry 87404 added for thread 1 sequence 26009 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:00:00 2015
    Setting Resource Manager plan SCHEDULER[0x32DA]:DEFAULT_MAINTENANCE_PLAN via scheduler window
    Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
    Tue Mar 03 22:00:00 2015
    Starting background process VKRM
    Tue Mar 03 22:00:00 2015
    VKRM started with pid=184, OS id=4838
    Tue Mar 03 22:00:07 2015
    Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
    Tue Mar 03 22:00:25 2015
    Thread 1 advanced to log sequence 26011 (LGWR switch)
      Current log# 1 seq# 26011 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 22:00:26 2015
    Archived Log entry 87408 added for thread 1 sequence 26010 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:00:58 2015
    Thread 1 advanced to log sequence 26012 (LGWR switch)
      Current log# 2 seq# 26012 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Tue Mar 03 22:01:00 2015
    Archived Log entry 87412 added for thread 1 sequence 26011 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:02:37 2015
    Thread 1 cannot allocate new log, sequence 26013
    Checkpoint not complete
      Current log# 2 seq# 26012 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Thread 1 advanced to log sequence 26013 (LGWR switch)
      Current log# 9 seq# 26013 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26013 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Tue Mar 03 22:02:41 2015
    Archived Log entry 87415 added for thread 1 sequence 26012 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:03:26 2015
    Thread 1 cannot allocate new log, sequence 26014
    Checkpoint not complete
      Current log# 9 seq# 26013 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26013 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Thread 1 advanced to log sequence 26014 (LGWR switch)
      Current log# 1 seq# 26014 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 22:03:29 2015
    Archived Log entry 87416 added for thread 1 sequence 26013 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:05:50 2015
    Thread 1 cannot allocate new log, sequence 26015
    Checkpoint not complete
      Current log# 1 seq# 26014 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 22:05:52 2015
    End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
    Thread 1 advanced to log sequence 26015 (LGWR switch)
      Current log# 2 seq# 26015 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Tue Mar 03 22:05:54 2015
    Archived Log entry 87418 added for thread 1 sequence 26014 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:07:29 2015
    Thread 1 cannot allocate new log, sequence 26016
    Checkpoint not complete
      Current log# 2 seq# 26015 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Thread 1 advanced to log sequence 26016 (LGWR switch)
      Current log# 9 seq# 26016 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26016 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Tue Mar 03 22:07:33 2015
    Archived Log entry 87421 added for thread 1 sequence 26015 ID 0x66aa5a0d dest 1:
    Thread 1 cannot allocate new log, sequence 26017
    Checkpoint not complete
      Current log# 9 seq# 26016 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26016 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Thread 1 advanced to log sequence 26017 (LGWR switch)
      Current log# 1 seq# 26017 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 22:07:39 2015
    Archived Log entry 87422 added for thread 1 sequence 26016 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:16:36 2015
    Thread 1 advanced to log sequence 26018 (LGWR switch)
      Current log# 2 seq# 26018 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_2.270.849356883
    Tue Mar 03 22:16:37 2015
    Archived Log entry 87424 added for thread 1 sequence 26017 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:30:06 2015
    Thread 1 advanced to log sequence 26019 (LGWR switch)
      Current log# 9 seq# 26019 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_9.295.853755983
      Current log# 9 seq# 26019 mem# 1: +ASM_ARCHIVE/oracle/onlinelog/group_9.10902.853755985
    Tue Mar 03 22:30:07 2015
    Archived Log entry 87427 added for thread 1 sequence 26018 ID 0x66aa5a0d dest 1:
    Tue Mar 03 22:30:18 2015
    Thread 1 advanced to log sequence 26020 (LGWR switch)
      Current log# 1 seq# 26020 mem# 0: +ASM_ORADATA/oracle/onlinelog/group_1.271.849356883
    Tue Mar 03 22:30:19 2015
    Archived Log entry 87428 added for thread 1 sequence 26019 ID 0x66aa5a0d dest 1:
    Tue Mar 03 23:07:27 2015
    Dumping diagnostic data in directory=[cdmp_20150303230727], requested by (instance=4, osid=25140), summary=[incident=1692496].
    Dumping diagnostic data in directory=[cdmp_20150303230730], requested by (instance=4, osid=25140), summary=[incident=1692497].
    Thanks in advance sir ,

  • Standby Database gives error ORA-03113:ORA-03114

    Hi
    I am using oracle 9iR2 on standby database when i recover it return errors like
    SQL> recover standby database;
    ORA-00279: change 8209765386 generated at 07/18/2008 12:10:41 needed for thread
    1
    ORA-00289: suggestion : J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86548.ARC
    ORA-00280: change 8209765386 for thread 1 is in sequence #86548
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00279: change 8209782309 generated at 07/18/2008 12:22:05 needed for thread
    1
    ORA-00289: suggestion : J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86549.ARC
    ORA-00280: change 8209782309 for thread 1 is in sequence #86549
    ORA-00278: log file 'J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86548.ARC' no
    longer needed for this recovery
    ORA-03113: end-of-file on communication channel
    ORA-03114: not connected to ORACLE
    Alert log display
    Starting datafile 1 recovery in thread 1 sequence 86551
    Datafile 1: 'E:\ORANT\ORADATA\APR1\SYSTEM01.DBF'
    Starting datafile 3 recovery in thread 1 sequence 86551
    Datafile 3: 'E:\ORANT\ORADATA\APR1\CWMLITE01.DBF'
    Starting datafile 4 recovery in thread 1 sequence 86551
    Datafile 4: 'E:\ORANT\ORADATA\APR1\DRSYS01.DBF'
    Starting datafile 5 recovery in thread 1 sequence 86551
    Datafile 5: 'E:\ORANT\ORADATA\APR1\EXAMPLE01.DBF'
    Starting datafile 6 recovery in thread 1 sequence 86551
    Datafile 6: 'E:\ORANT\ORADATA\APR1\INDX01.DBF'
    Starting datafile 7 recovery in thread 1 sequence 86551
    Datafile 7: 'E:\ORANT\ORADATA\APR1\ODM01.DBF'
    Starting datafile 8 recovery in thread 1 sequence 86551
    Datafile 8: 'E:\ORANT\ORADATA\APR1\TOOLS01.DBF'
    Starting datafile 9 recovery in thread 1 sequence 86551
    Datafile 9: 'J:\ORACLE\ORADATA\APR1\USERS01.DBF'
    Starting datafile 10 recovery in thread 1 sequence 86551
    Datafile 10: 'E:\ORANT\ORADATA\APR1\XDB01.DBF'
    Starting datafile 11 recovery in thread 1 sequence 86551
    Datafile 11: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_E.DBF'
    Starting datafile 12 recovery in thread 1 sequence 86549
    Datafile 12: 'J:\ORACLE\ORADATA\APR1\APR_DATA4_C.DBF'
    Starting datafile 13 recovery in thread 1 sequence 86550
    Datafile 13: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_D.DBF'
    Starting datafile 14 recovery in thread 1 sequence 86550
    Datafile 14: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_A.DBF'
    Starting datafile 15 recovery in thread 1 sequence 86548
    Datafile 15: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_B.DBF'
    Starting datafile 16 recovery in thread 1 sequence 86550
    Datafile 16: 'J:\ORACLE\ORADATA\APR1\APR_DATA1_A.DBF'
    Starting datafile 17 recovery in thread 1 sequence 86550
    Datafile 17: 'J:\ORACLE\ORADATA\APR1\APR_DATA1_B.DBF'
    Starting datafile 18 recovery in thread 1 sequence 86550
    Datafile 18: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_A.DBF'
    Starting datafile 19 recovery in thread 1 sequence 86549
    Datafile 19: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_B.DBF'
    Starting datafile 20 recovery in thread 1 sequence 86549
    Datafile 20: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_C.DBF'
    Starting datafile 25 recovery in thread 1 sequence 86550
    Datafile 25: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_A.DBF'
    Starting datafile 26 recovery in thread 1 sequence 86550
    Datafile 26: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_B.DBF'
    Starting datafile 27 recovery in thread 1 sequence 86550
    Datafile 27: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_C.DBF'
    Starting datafile 28 recovery in thread 1 sequence 86550
    Datafile 28: 'J:\ORACLE\ORADATA\APR1\APR_MVIEWS_A.DBF'
    Starting datafile 29 recovery in thread 1 sequence 86550
    Datafile 29: 'J:\ORACLE\ORADATA\APR1\BLOB_A.DBF'
    Starting datafile 30 recovery in thread 1 sequence 86549
    Datafile 30: 'J:\ORACLE\ORADATA\APR1\HR_DATA1_A.DBF'
    Starting datafile 31 recovery in thread 1 sequence 86548
    Datafile 31: 'J:\ORACLE\ORADATA\APR1\HR_DATA2_A.DBF'
    Starting datafile 32 recovery in thread 1 sequence 86550
    Datafile 32: 'J:\ORACLE\ORADATA\APR1\HR_INDX1_A.DBF'
    Starting datafile 33 recovery in thread 1 sequence 86550
    Datafile 33: 'J:\ORACLE\ORADATA\APR1\HR_INDX2_A.DBF'
    Starting datafile 34 recovery in thread 1 sequence 86548
    Datafile 34: 'J:\ORACLE\ORADATA\APR1\INVENTORY_A.DBF'
    Starting datafile 35 recovery in thread 1 sequence 86550
    Datafile 35: 'J:\ORACLE\ORADATA\APR1\INVENTORY_INDX_A.DBF'
    Starting datafile 36 recovery in thread 1 sequence 86550
    Datafile 36: 'E:\ORANT\ORADATA\APR1\SAMPLE_DATA1_A.DBF'
    Starting datafile 37 recovery in thread 1 sequence 86550
    Datafile 37: 'J:\ORACLE\ORADATA\APR1\VMS_DATA1_A.DBF'
    Starting datafile 38 recovery in thread 1 sequence 86550
    Datafile 38: 'J:\ORACLE\ORADATA\APR1\APR_MMS_A.DBF'
    Starting datafile 39 recovery in thread 1 sequence 86550
    Datafile 39: 'J:\ORACLE\ORADATA\APR1\AUDIT_DATA_A.DBF'
    Starting datafile 40 recovery in thread 1 sequence 86549
    Datafile 40: 'J:\ORACLE\ORADATA\APR1\UNDOTBS.DBF'
    Starting datafile 41 recovery in thread 1 sequence 86550
    Datafile 41: 'J:\ORACLE\ORADATA\APR1\APR_DATA1_C.DBF'
    Starting datafile 42 recovery in thread 1 sequence 86549
    Datafile 42: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_E.DBF'
    Starting datafile 43 recovery in thread 1 sequence 86548
    Datafile 43: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_C.DBF'
    Starting datafile 44 recovery in thread 1 sequence 86550
    Datafile 44: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_E.DBF'
    Starting datafile 46 recovery in thread 1 sequence 86550
    Datafile 46: 'E:\ORANT\ORADATA\APR1\SYSTEM02.DBF'
    Starting datafile 47 recovery in thread 1 sequence 86550
    Datafile 47: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_A.DBF'
    Starting datafile 48 recovery in thread 1 sequence 86549
    Datafile 48: 'J:\ORACLE\ORADATA\APR1\APR_DATA4.DBF'
    Starting datafile 49 recovery in thread 1 sequence 86550
    Datafile 49: 'J:\ORACLE\ORADATA\APR1\APR_DATA4_A.DBF'
    Starting datafile 50 recovery in thread 1 sequence 86548
    Datafile 50: 'J:\ORACLE\ORADATA\APR1\APR_DATA4_B.DBF'
    Starting datafile 51 recovery in thread 1 sequence 86550
    Datafile 51: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_B.DBF'
    Starting datafile 52 recovery in thread 1 sequence 86550
    Datafile 52: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_A.DBF'
    Starting datafile 53 recovery in thread 1 sequence 86550
    Datafile 53: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_B.DBF'
    Starting datafile 54 recovery in thread 1 sequence 86550
    Datafile 54: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_C.DBF'
    Starting datafile 55 recovery in thread 1 sequence 86550
    Datafile 55: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_D.DBF'
    Starting datafile 56 recovery in thread 1 sequence 86549
    Datafile 56: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_C.DBF'
    Starting datafile 57 recovery in thread 1 sequence 86550
    Datafile 57: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_F.DBF'
    Starting datafile 58 recovery in thread 1 sequence 86550
    Datafile 58: 'J:\ORACLE\ORADATA\APR1\APR_DATA6_A.DBF'
    Starting datafile 59 recovery in thread 1 sequence 86548
    Datafile 59: 'J:\ORACLE\ORADATA\APR1\APR_DATA6_B.DBF'
    Starting datafile 60 recovery in thread 1 sequence 86549
    Datafile 60: 'J:\ORACLE\ORADATA\APR1\APR_DATA6_C.DBF'
    Starting datafile 61 recovery in thread 1 sequence 86549
    Datafile 61: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_D.DBF'
    Starting datafile 62 recovery in thread 1 sequence 86550
    Datafile 62: 'J:\ORACLE\ORADATA\APR1\APR_INDX5_A.DBF'
    Starting datafile 63 recovery in thread 1 sequence 86550
    Datafile 63: 'J:\ORACLE\ORADATA\APR1\APR_INDX5_B.DBF'
    Starting datafile 64 recovery in thread 1 sequence 86550
    Datafile 64: 'E:\ORANT\ORADATA\APR1\USERS01_A.DBF'
    Starting datafile 65 recovery in thread 1 sequence 86550
    Datafile 65: 'J:\ORACLE\ORADATA\APR1\GMT1_DATA.DBF'
    Starting datafile 66 recovery in thread 1 sequence 86548
    Datafile 66: 'J:\ORACLE\ORADATA\APR1\GMT1_INDX.DBF'
    Starting datafile 67 recovery in thread 1 sequence 86550
    Datafile 67: 'J:\ORACLE\ORADATA\APR1\APR_DATA7.DBF'
    Starting datafile 68 recovery in thread 1 sequence 86550
    Datafile 68: 'J:\ORACLE\ORADATA\APR1\APR_INDX7A.ORA'
    Starting datafile 69 recovery in thread 1 sequence 86550
    Datafile 69: 'J:\ORACLE\ORADATA\APR1\APR_INDX8_A.DBF'
    Starting datafile 70 recovery in thread 1 sequence 86550
    Datafile 70: 'J:\ORACLE\ORADATA\APR1\APR_INDX8_B.DBF'
    Media Recovery Log
    ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
    Wed Jul 23 11:26:24 2008
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Wed Jul 23 11:26:24 2008
    Media Recovery Log J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86548.ARC
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Wed Jul 23 11:26:25 2008
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Media Recovery Log J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86549.ARC
    Wed Jul 23 11:26:53 2008
    Some recovered datafiles maybe left media fuzzy
    Media recovery may continue but open resetlogs may fail
    Wed Jul 23 11:26:53 2008
    ARC0: terminating instance due to error 472
    Instance terminated by ARC0, pid = 2100
    Tell me the solution.
    Thanks in advance

    I think your database is not going in begin backup mode...
    this is my standby database server Pratap is there any method to check backup mode .
    Thanks

  • Issue on physical standby database

    Hi
    I've a problem on standby database.
    I recently added a datafile on primary database, then I scp'ed the data file to physical standby database.On physical standby database I tried performing recovery.
    I get following message in my alert log
    WARNING! Recovering data file 88 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
    how can I fix this now.
    We keep physical standby database 2 day behind, and apply logs manually.
    Physical standby database is maintained manually.
    Could someone help me in getting out of this problem.
    Oracle 9.2.0.7
    solaris

    Versus keeping it in manual mode, you can specify a time "delay" for the application of the logs:
    From http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1022811
    6.2.2 Specifying a Time Delay for the Application of Archived Redo Log Files
    In some cases, you may want to create a time lag between the time when redo data is received from the primary site and when it is applied to the standby database. You can specify a time interval (in minutes) to protect against the application of corrupted or erroneous data to the standby database. When you set a DELAY interval, it does not delay the transport of the redo data to the standby database. Instead, the time lag you specify begins when the redo data is completely archived at the standby destination.
    Note:
    If you define a delay for a destination that has real-time apply enabled, the delay is ignored.
    Specifying a Time Delay
    You can set a time delay on primary and standby databases using the DELAY=minutes attribute of the LOG_ARCHIVE_DEST_n initialization parameter to delay applying archived redo log files to the standby database. By default, there is no time delay. If you specify the DELAY attribute without specifying a value, then the default delay interval is 30 minutes.
    Canceling a Time Delay
    You can cancel a specified delay interval as follows:
    For physical standby databases, use the NODELAY keyword of the RECOVER MANAGED STANDBY DATABASE clause:
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY;
    For logical standby databases, specify the following SQL statement:
    SQL> ALTER DATABASE START LOGICAL STANDBY APPLY NODELAY;
    These commands result in log apply services immediately beginning to apply archived redo log files to the standby database, before the time interval expires. Also, see:
    Section 12.8, "Using a Physical Standby Database with a Time Lag"
    Oracle Database SQL Reference for the DELAY attribute of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement

  • Data Guard Related Problem

    We are using oracle 9.2, i am facing a problem in the dataguard is that i want to know whether the log have been applied or not.....below are the outputs....
    we are using manual data guard......
    SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
    no rows selectedwhen i fire the above query it is not showing any result......
    pls suggest me ..
    SQL> show parameter stand
    NAME                                 TYPE        VALUE
    standby_archive_dest                 string      /arch/log
    standby_file_management              string      MANUAL
    SQL> SELECT THREAD#, MAX(SEQUENCE#) AS "LAST_APPLIED_LOG"
      2  FROM V$LOG_HISTORY
      3  GROUP BY THREAD#;
       THREAD# LAST_APPLIED_LOG
             1             1724
             2             1537
    SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
    no rows selected

    we are using a manual standby database.......
    SQL> select  DATABASE_ROLE, SWITCHOVER_STATUS,DATAGUARD_BROKER from v$database;
    DATABASE_ROLE    SWITCHOVER_STATUS  DATAGUAR
    PHYSICAL STANDBY SESSIONS ACTIVE    DISABLED
    SQL> show parameter stand
    NAME                                 TYPE        VALUE
    standby_file_management              string      MANUALso pls suggest me how would i know whether the archives have been applied or not.....
    although i have posted the query which i was using for the same
    and one more thing i am getting an error in alert log file also...
    Sun Aug 10 12:28:09 2008
    ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
    Sun Aug 10 12:28:09 2008
    ALTER DATABASE RECOVER    CONTINUE DEFAULT
    Sun Aug 10 12:28:09 2008
    Media Recovery Log /arch/log/1_1724.dbf
    Sun Aug 10 12:31:09 2008
    ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
    Sun Aug 10 12:31:09 2008
    ALTER DATABASE RECOVER    CONTINUE DEFAULT
    Sun Aug 10 12:31:09 2008
    Media Recovery Log /arch/log/1_1725.dbf
    Errors with log /arch/log/1_1725.dbf
    ORA-308 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
    Sun Aug 10 12:31:09 2008
    ALTER DATABASE RECOVER CANCEL
    Sun Aug 10 12:31:09 2008
    Media Recovery Cancelled
    Completed: ALTER DATABASE RECOVER CANCEL
    Sun Aug 10 12:33:09 2008
    alter database open read only
    Sun Aug 10 12:33:09 2008
    SMON: enabling cache recovery
    Sun Aug 10 12:33:09 2008
    Database Characterset is WE8ISO8859P1
    replication_dependency_tracking turned off (no async multimaster replication fou
    nd)
    Completed: alter database open read only
    #

  • How to recover from one corrupted redo log file in NOARCHIVE mode?

    Oracle 10.2.1.
    The redo log file was corrupted and Oracle can't work.
    When I use STARTUP mount, I got no error msg.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 1652555776 bytes
    Fixed Size 1251680 bytes
    Variable Size 301991584 bytes
    Database Buffers 1342177280 bytes
    Redo Buffers 7135232 bytes
    Database mounted.
    But I have some applications which are depended on Oracle can't be started.
    So, I tried STARTUP open. But I got error msg.
    SQL> startup open
    ORACLE instance started.
    Total System Global Area 1652555776 bytes
    Fixed Size 1251680 bytes
    Variable Size 301991584 bytes
    Database Buffers 1342177280 bytes
    Redo Buffers 7135232 bytes
    Database mounted.
    ORA-00368: checksum error in redo log block
    ORA-00353: log corruption near block 497019 change 42069302 time 11/07/2007
    23:43:09
    ORA-00312: online log 4 thread 1:
    'G:\ORACLE\PRODUCT\10.2.0\ORADATA\NMDATA\REDO04.LOG'
    So, how can I restore and recover my database?
    If use RMAN, how to do that?
    Any help will be appreciated.
    Thanks.

    Hi, Yingkuan,
    Thanks for the helps.
    Actually, I have 10 redo log files exists. All of them are here.
    I tried your suggestion:
    alter database clear unarchived logfile group 4;
    The error msg I got is the same as before:
    SQL> alter database clear unarchived logfile group 4;
    alter database clear unarchived logfile group 4
    ERROR at line 1:
    ORA-01624: log 4 needed for crash recovery of instance nmdata (thread 1)
    ORA-00312: online log 4 thread 1:
    'G:\ORACLE\PRODUCT\10.2.0\ORADATA\NMDATA\REDO04.LOG'
    Compared to losing all the data, it is OK for me lose some of them.
    I have more than 1 TB data stored and 99.9% of them are raster images.
    The loading of these data were the headache. If I can save them, I can bear the lost.
    I want to grasp the last straw.
    But I don't know how set the parameter: allowresetlogs_corruption
    I got the error msg:
    SQL> set allowresetlogs_corruption=true;
    SP2-0735: unknown SET option beginning "_allow_res..."
    I have run the command:
    Recover database until cancel
    Alter database open resetlogs
    The error msg I got is the following:
    SQL> recover database until cancel
    ORA-00279: change 41902930 generated at 11/05/2007 22:01:48 needed for thread 1
    ORA-00289: suggestion :
    D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\NMDATA\ARCHIVELOG\2007_11_09\O1_MF_
    1_1274_%U_.ARC
    ORA-00280: change 41902930 for thread 1 is in sequence #1274
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\NMDATA\SYSTEM01.DBF'
    ORA-01112: media recovery not started
    SQL>
    From the log file, I got the following:
    ALTER DATABASE RECOVER database until cancel
    Fri Nov 09 00:12:48 2007
    Media Recovery Start
    parallel recovery started with 2 processes
    ORA-279 signalled during: ALTER DATABASE RECOVER database until cancel ...
    Fri Nov 09 00:13:20 2007
    ALTER DATABASE RECOVER CANCEL
    Fri Nov 09 00:13:21 2007
    ORA-1547 signalled during: ALTER DATABASE RECOVER CANCEL ...
    Fri Nov 09 00:13:21 2007
    ALTER DATABASE RECOVER CANCEL
    ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...
    Thank you very much. and I am looking forward to your followup input.

  • Recover Standby Database suggests wrong filename

    Hi,
    I am running Oracle Database 10g Release 10.2.0.3.0 - 64bit Production Standard Edition on Linux version 2.6.9-42.0.8.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3))
    I've created a physical standby database, but since I am running Standard Edition, I am not using the DataGuard features. I use the rsync utility to copy over the archivelogs to the standby database, and I apply them periodically to the standby database.
    The standby database is started this way :
    startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
    alter database mount standby database;
    And the archives are applied this way :
    recover standby database;
    AUTO
    (AUTO for the command to apply all available archive logs automatically, using the suggested paths and filenames)
    My problem is that once in a while (maybe once every 2-3 weeks), the suggested filename does not have the same format as the rest of the time. I then have to manually specify the correct filename and it goes fine after that.
    Example :
    In this example, you will see that it is first looking for sequence 22907 (o1_mf_1_22907_5n3m1xrf_.arc), then 22908 (o1_mf_1_22908_5n3m4kf0_.arc) [Notice the format of the file name] and then tries to look for sequence 22909, but looks for filename ".o1_mf_1_22909_5n3md1h5_.arc.qXMz5s"
    Mon Jan 4 06:22:01 2010
    ALTER DATABASE RECOVER standby database
    Media Recovery Start
    Managed Standby Recovery not using Real Time Apply
    ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
    Mon Jan 4 06:22:02 2010
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Mon Jan 4 06:22:02 2010
    Media Recovery Log /oraarch/oracle/flash_recovery_area/GIGA10G/archivelog/2010_01_04/o1_mf_1_22907_5n3m1xrf_.arc
    Mon Jan 4 06:24:20 2010
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Mon Jan 4 06:24:20 2010
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Mon Jan 4 06:24:20 2010
    Media Recovery Log /oraarch/oracle/flash_recovery_area/GIGA10G/archivelog/2010_01_04/o1_mf_1_22908_5n3m4kf0_.arc
    Mon Jan 4 06:24:46 2010
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Mon Jan 4 06:24:46 2010
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Mon Jan 4 06:24:46 2010
    Media Recovery Log /oraarch/oracle/flash_recovery_area/GIGA10G/archivelog/2010_01_04/.o1_mf_1_22909_5n3md1h5_.arc.qXMz5s
    Errors with log /oraarch/oracle/flash_recovery_area/GIGA10G/archivelog/2010_01_04/.o1_mf_1_22909_5n3md1h5_.arc.qXMz5s
    ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Mon Jan 4 06:24:46 2010
    ALTER DATABASE RECOVER CANCEL
    Mon Jan 4 06:24:46 2010
    Media Recovery Canceled
    Completed: ALTER DATABASE RECOVER CANCEL
    Can someone explain to me why is this happening please ?
    Thanks a lot,
    Mat

    @fjfranken
    Yes. If I manually enter the name of the file for the sequence requested instead of passing the suggested fielname, it works fine.
    And the log_archive_format is not defined, I am using the flash_recovery_area and let Oracle manage this automatically.
    @Hemant K Chitale
    Unfortunately, those sequences are not listed anymore in the V$ARCHIVED_LOG view.
    Well, I think the the problem might be related to files that are being written to at some time...
    Thanks,
    Mat

  • Corrupting the block to continue recovery in physical standby

    Hi,
    Just like to inquire how I will be able to corrupt the block to be able to continue the recovery in the physical standby.
    DB Version: 11.1.0.7
    Database Type: Data Warehouse
    The setup we have is primary database and standby database, we are not using dataguard, and our standby setup is another physical copy of production which act as standby and being sync using script that being run from time to time to apply the archive log came from production (its not configured to sync using ARCH or LGWR and its corresponding configurations).
    Then, the standby database is not sync due to errors encountered while trying to apply the archive log, error is below:
    Fri Feb 11 05:50:59 2011
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Media Recovery Log /u01/archive/<sid>/1_50741_651679913.arch
    Fri Feb 11 05:52:06 2011
    Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0, kdr9ir2rst0()+326]
    Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc (incident=631460):
    ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
    Incident details in: /u01/app/oracle/diag/rdbms/<sid>/<sid>/incident/incdir_631460/<sid>pr0028085_i631460.trc
    Fri Feb 11 05:52:10 2011
    Trace dumping is performing id=[cdmp_20110211055210]
    Fri Feb 11 05:52:14 2011
    Sweep Incident[631460]: completed
    Fri Feb 11 05:52:17 2011
    Slave exiting with ORA-10562 exception
    Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc:
    ORA-10562: Error occurred while applying redo to data block (file# 36, block# 1576118)
    ORA-10564: tablespace <tablespace name>
    ORA-01110: data file 36: '/u02/oradata/<sid>/<datafile>.dbf'
    ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 14877145
    ORA-00607: Internal error occurred while making a change to a data block
    ORA-00602: internal programming exception
    ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
    Based on the error log it seems we are hitting some bug from metalink (document id 460169.1 and 882851.1)
    my question is, the datafile # is given, block# is known too and the data object is also identified. I just verified that object is not that important, is there a way to set the block# to corrupted to be able the recovery to continue? Then I will just drop the table from production so that will also happen in standby, and the block corrupted will be gone too. Is this feasible?
    If its not, can you suggest what's next I can do so the the physical standby will be able to sync again to prod aside from rebuilding the standby?
    Please take note that I also tried to dbv the file to confirm if there is marked as corrupted and the result for that datafile is also good:
    dbv file=/u02/oradata/<sid>/<datafile>_19.dbf logfile=dbv_file_36.log blocksize=16384
    oracle@<server>:[~] $ cat dbv_file_36.log
    DBVERIFY: Release 11.1.0.7.0 - Production on Sun Feb 13 04:35:28 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    DBVERIFY - Verification starting : FILE = /u02/oradata/<sid>/<datafile>_19.dbf
    DBVERIFY - Verification complete
    Total Pages Examined : 3840000
    Total Pages Processed (Data) : 700644
    Total Pages Failing (Data) : 0
    Total Pages Processed (Index): 417545
    Total Pages Failing (Index): 0
    Total Pages Processed (Other): 88910
    Total Pages Processed (Seg) : 0
    Total Pages Failing (Seg) : 0
    Total Pages Empty : 2632901
    Total Pages Marked Corrupt : 0
    Total Pages Influx : 0
    Total Pages Encrypted : 0
    Highest block SCN : 3811184883 (1.3811184883)
    Any help is really appreciated. I hope to hear feedback from you.
    Thanks

    damorgan, i understand the opinion.
    just new with the organization and just inherit a data warehouse database without rman backup. I am still setting up the rman backup thats why i can't use rman to resolve the issue, the only i have is physical standby and its not a standby that automatically sync using dataguard or standard standby setup, i am just checking solution that is applicable in the current situation

Maybe you are looking for

  • Require ability to enter a zero price on service line items

    We have a need to create a service purchase order (item category 'D') with one line item using account assignment 'P'.  We're creating as a 'limit' Purchase order and intend to create more than one service entry sheet. For example - the total expecte

  • Custom Afaria Client not getting installed on IOS devices

    Hello, I am using Afaria SP4 in my organization with no hotfix applied I have created a custom Afaria Client App for IOS devices. I am succesfully able to enroll my IOS devices and install the custom app during enrollment,when i am trying to hit the

  • How can I use bookmark script to deselct sidebar option by default?

    I am trying to include a User Friendly 1-Click link on my site to automatically bookmark a page. Using the Ultimate Bookmark script this works fine in IE, but when the bookmarking window pops up it always has the "Load this bookmark in the sidebar" o

  • SAP Jar finder for NW 7.3

    Hello, I have two classes from SAP Portal (for import) and I need libraries with these classes for NW 7.3. With sapjarfinder.com I can find only SAP libraries for NW 7.0. Can you please tell me how I can find the names and directories (/usr/sap...) o

  • How poor is this practice?

    We have applications at work that spend most of the day rolling back insert statements because of attempts to insert dupe data into a unique indexed table. How poor is this practice to eliminate duplicates? It seems to be a common practice by those u