ORA-00279

Hello
in 10g R2 in HP unix, standby alertlog I have:
ORA-279 signalled during: ALTER DATABASE RECOVER  standby database until change 1106544632 PARALLEL (DEGREE 6)  ...
Tue May  3 10:02:41 2011
ALTER DATABASE RECOVER    CONTINUE DEFAULT
And in the documentation:
ORA-00279: change string generated at the necessary level for string of thread string
Cause: The required journal is required to proceed to the recovery.
Action: Please provide the newspaper asked with "ALTER DATABASE RECOVER LOGFILE < Filename >" or cancel the recovery with "ALTER DATABASE RECOVER CANCEL.

Then, if she can't find log file why she KEEPS by DEFAULT?

What is Eve? And why nothing in alertlog since 10:02?

Thank you.

Salvation;

Please see below which could be useful for your question:
A principal database and synchronization of relief due to the transfer of journal gap. [150214.1 ID]
Data protection Wizard: create Standby failure Ora-279 [ID 381536.1]

Respect of
HELIOS

Tags: Database

Similar Questions

  • ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error

    Dear all,

    While making RMAN cloning we get the error in the trace as file

    Trace file E:\ORACLE\TESTDB\11.2.0\ADMIN\TEST_TESTDB\diag\rdbms\hrdev\test\trace\test_pr00_3980.trc

    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production

    With partitioning, OLAP, Data Mining and Real Application Testing options

    Windows Server 2003 V5.2 Service Pack 2 Version

    CPU: 2 - type 586, 2 physical cores

    Process affinity: 0 x 0 x 00000000

    Memory (success/Total): Ph: 15587 M / 16383 M, Ph + FCP: 32981 M / 34549 M, GOES: 708 M / 2047 M

    Instance name: hrdev

    Redo thread mounted by this instance: 1

    Oracle process number: 20

    Windows thread ID: 3980, image: ORACLE. EXE (PR00)

    2015-07-03 18:30:47.577

    Has started the recovery of parallel media

    2015-07-03 18:30:47.983

    Dumping table incarnation of database:

    RESETLOGS 0 Yvert and time: 0x0003.660c2a42 01/09/2014 19:37:43

    Incarnation of recovery target = 2, = 0 activation ID

    The flow buffer limit = 37200 min (50% x 74400, 100000)

    Start the recovery to the thread 1 ckpt SNA 15900955092 logseq 2726 block 469796

    Initial size of the buffers: read 1024K, 832K overflow, change 805K

    2015-07-03 18:30:48.030

    Add a Media Recovery redo thread 1

    2015-07-03 18:30:48.827

    Fall of Media Recovery redo thread 1

    DDE: Key problem "ORA 1110' was the controlled flood (0 x 1) (incident)

    ORA-01110: data file 1: ' F:\ORACLE\TESTDATA\SYSTEM01. DBF'

    2015-07-03 18:30:49.405

    Completed media recovery

    ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error

    ORA-01194: file 1 needs a recovery more match

    ORA-01110: data file 1: ' F:\ORACLE\TESTDATA\SYSTEM01. DBF'

    Concerning

    Villi Kumar

    Dear all,

    We have fixed this problem.

    Solution:

    E:\oracle\testdb\11.2.0>sqlplus sys as sysdba

    SQL * more: Production of liberation 11.2.0.3.0 Fri Jul 3 19:00:20 2015

    Copyright (c) 1982, 2011, Oracle.  All rights reserved.

    Enter the password:

    Connected to:

    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production

    With partitioning, OLAP, Data Mining and Real Application Testing options

    SQL >

    SQL > RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE;

    ORA-00279: change 15900955092 generated at 02/07/2015 17:30:06 to

    thread 1

    ORA-00289: suggestion:

    E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002726_0836422663.0001

    ORA-00280: change 15900955092 thread 1 is in sequence #2726

    Specify the log: {= suggested |} Filename | AUTO | CANCEL}

    F:\oracle\arch\TEST\ARC0000002726_0836422663.0001

    ORA-00279: change 15900962042 generated at 02/07/2015 18:30:06 to

    thread 1

    ORA-00289: suggestion:

    E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002727_0836422663.0001

    ORA-00280: change 15900962042 thread 1 is in sequence #2727

    ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002726_0836422663.0001' not

    longer needed for recovery

    Specify the log: {= suggested |} Filename | AUTO | CANCEL}

    F:\oracle\arch\TEST\ARC0000002727_0836422663.0001

    ORA-00279: change 15900962052 generated at 02/07/2015 18:30:16 needed to

    thread 1

    ORA-00289: suggestion:

    E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002728_0836422663.0001

    ORA-00280: change 15900962052 thread 1 is in sequence #2728

    ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002727_0836422663.0001' not

    longer needed for recovery

    Specify the log: {= suggested |} Filename | AUTO | CANCEL}

    F:\oracle\arch\TEST\ARC0000002728_0836422663.0001

    ORA-00279: change 15901106577 generated at 03/07/2015 06:23:19 needed to

    thread 1

    ORA-00289: suggestion:

    E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002729_0836422663.0001

    ORA-00280: change 15901106577 thread 1 is in sequence #2729

    ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002728_0836422663.0001' not

    longer needed for recovery

    Specify the log: {= suggested |} Filename | AUTO | CANCEL}

    F:\oracle\arch\TEST\ARC0000002729_0836422663.0001

    ORA-00279: change 15901247230 generated at 03/07/2015 06:33:53 required for

    thread 1

    ORA-00289: suggestion:

    E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002730_0836422663.0001

    ORA-00280: change 15901247230 thread 1 is in sequence #2730

    ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002729_0836422663.0001' not

    longer needed for recovery

    Specify the log: {= suggested |} Filename | AUTO | CANCEL}

    F:\oracle\arch\TEST\ARC0000002730_0836422663.0001

    ORA-00279: change 15901413113 generated at 03/07/2015 06:45:53 required for

    thread 1

    ORA-00289: suggestion:

    E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002731_0836422663.0001

    ORA-00280: change 15901413113 thread 1 is in sequence #2731

    ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002730_0836422663.0001' not

    longer needed for recovery

    Specify the log: {= suggested |} Filename | AUTO | CANCEL}

    F:\oracle\arch\TEST\ARC0000002731_0836422663.0001

    ORA-00279: change 15901578404 generated at 03/07/2015 06:56:49 to

    thread 1

    ORA-00289: suggestion:

    E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002732_0836422663.0001

    ORA-00280: change 15901578404 thread 1 is in sequence #2732

    ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002731_0836422663.0001' not

    longer needed for recovery

    Specify the log: {= suggested |} Filename | AUTO | CANCEL}

    F:\oracle\arch\TEST\ARC0000002732_0836422663.0001

    ORA-00279: change 15901715991 generated at 03/07/2015 07:05:32 needed to

    thread 1

    ORA-00289: suggestion:

    E:\ORACLE\TESTDB\11.2.0\RDBMS\ARC0000002733_0836422663.0001

    ORA-00280: change 15901715991 thread 1 is in sequence #2733

    ORA-00278: save the file 'F:\oracle\arch\TEST\ARC0000002732_0836422663.0001' not

    longer needed for recovery

    Specify the log: {= suggested |} Filename | AUTO | CANCEL}

    Cancel

    SQL > alter database open resetlogs;

    Concerning

    Villi Kumar

  • recover the database up to the time, ORA-600 [2619]

    Oracle 11.2.0.3.9

    Solaris 10

    I have a database of pending that I would copy and activate the copy in another recovery base autonomous disaster.  I took a "Save as copy" of the day before and generated a controlfile primary with «alter database backup controlfile to trace...» ».

    I edited the controlfile, but now course issues with my recover.  I want to get back at 11:00, but I get an error ORA-600 at the end of the restoration and data files have a 10:40:46 checkpoint_time.  Here's the problem:

    Hood > sqlplus / as sysdba

    SQL * more: Production release 11.2.0.3.0 Wed Oct 8 11:35:47 2014

    Copyright (c) 1982, 2011, Oracle.  All rights reserved.

    Connected to:

    Oracle Database 11 g Enterprise Edition Release 11.2.0.3.0 - 64 bit Production

    With partitioning, OLAP, Data Mining and Real Application Testing options

    SQL > restore database using backup controlfile until time ' 2014 - 10 - 08:11:00:00';

    ORA-00279: change 90406997774 generated at 08/10/2014 10:40:46 needed to

    thread 1

    ORA-00289: suggestion: /oracle/logs/NFDR/arch_598887_1_527943760.dbf

    ORA-00280: change 90406997774 thread 1 is in sequence #598887

    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}

    Auto

    ORA-00600: internal error code, arguments: [2619], [598887], [] [], [], [],.

    [], [], [], [], [], []



    SQL > select file #, to_char (checkpoint_time, 'YYYYMMDD HH24:MI:SS') from v$ datafile_header by 2.

    FOLDER # TO_CHAR (CHECKPOIN

    ---------- -----------------

    1 20141008 10:40:46

    2 20141008 10:40:46

    ...


    I have provided all archivelogs (even more) to the new database.  On the primary:


    SELECT the name of sequence #, first_time next_time OF V$ ARCHIVED_LOG WHERE SEQUENCE # < = 598889 AND name! = 'nfpo_stby' ORDER BY DESC SEQUENCE #.


    /archive01/NFPO/arch_598889_1_527943760.dbf59888908/10/2014 11:34:0508/10/2014 11:55:26
    /archive01/NFPO/arch_598888_1_527943760.dbf59888808/10/2014 11:09:4408/10/2014 11:34:05
    /archive01/NFPO/arch_598887_1_527943760.dbf59888708/10/2014-10:40:4608/10/2014 11:09:44
    /archive01/NFPO/arch_598886_1_527943760.dbf59888608/10/2014-09:57:1508/10/2014-10:40:46
    /archive01/NFPO/arch_598885_1_527943760.dbf59888508/10/2014-09:03:0308/10/2014-09:57:15
    /archive01/NFPO/arch_598884_1_527943760.dbf59888408/10/2014-08:30:1108/10/2014-09:03:03
    /archive01/NFPO/arch_598883_1_527943760.dbf59888308/10/2014 08:07:2308/10/2014-08:30:11
    /archive01/NFPO/arch_598882_1_527943760.dbf59888208/10/2014 08:05:5308/10/2014 08:07:23
    /archive01/NFPO/arch_598881_1_527943760.dbf59888108/10/2014-07:33:2908/10/2014 08:05:53


    SQL > show parameter log_archive_dest;

    VALUE OF TYPE NAME

    ------------------------------------ ----------- ------------------------------

    Log_archive_dest chain

    Log_archive_dest_1 string LOCATION = / oracle/logs/NFDR

    ...


    Hood > cd/oracle/logs/NFDR

    Hood > ls - lah

    Total 3170612

    DBA oracle drwxr-xr-x 2 512 8 Oct 11:35.

    DBA oracle drwxr-xr-x 4 512 8 Oct 09:01...

    -rw - r - 1 oracle dba 173M 8 Oct 11:03 arch_598881_1_527943760.dbf

    -rw - r - 1 oracle dba M 174, 8 Oct 11:04 arch_598882_1_527943760.dbf

    -rw - r - 1 oracle dba M 175, 8 Oct 11:04 arch_598883_1_527943760.dbf

    -rw - r - 1 oracle dba 169M 8 Oct 11:04 arch_598884_1_527943760.dbf

    -rw - r - 1 oracle dba 168M 8 Oct 11:04 arch_598885_1_527943760.dbf

    -rw - r - 1 oracle dba 168M 8 Oct 11:04 arch_598886_1_527943760.dbf

    -rw - r - 1 oracle dba 200M 8 Oct 11:04 arch_598887_1_527943760.dbf

    -rw - r - 1 oracle dba M 121, 8 Oct 11:34 arch_598888_1_527943760.dbf

    -rw - r - 1 oracle dba 200M 8 Oct 11:35 arch_598889_1_527943760.dbf

    Why my database only get over not at 10:40, 11:00?

    Just a semantic quibble: you can't have a recovery with noarchivelog database.  (Unless I'm missing something)

  • ORA-00312: wire 3 1 online journal: ' C:\ORACLE\ORADATA\XE\REDO03. JOURNAL"

    Hello

    My operating system is windows7 and Oracle Database 11 g Enterprise Edition Release 11.2.0.1.0 - 64 bit Production
        SQL> alter database open;  
        alter database open  
        *  
        ERROR at line 1:  
        ORA-00354: corrupt redo log block header  
        ORA-00353: log corruption near block 75760 change 5605346 time 01/07/2012  
        11:41:31  
        ORA-00312: online log 3 thread 1: 'C:\ORACLE\ORADATA\XE\REDO03.LOG'  
    I followed the recovery of corrupted log file again in no archived db 10 g

    What I've done so far:
    SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 1;
    
    Database altered.
    
    SQL> alter database open resetlogs;
    alter database open resetlogs
    *
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: 'C:\ORACLE\ORADATA\XE\SYSTEM01.DBF'
    
    SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE 'C:/Oracle/oradata/XE/REDO03.log';
    ALTER DATABASE CLEAR UNARCHIVED LOGFILE 'C:/Oracle/oradata/XE/REDO03.log'
    *
    ERROR at line 1:
    ORA-01624: log 3 needed for crash recovery of instance xe (thread 1)
    ORA-00312: online log 3 thread 1: 'C:\ORACLE\ORADATA\XE\REDO03.LOG'
    
    
    SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE 'C:/Oracle/oradata/XE/REDO03.log';
    ALTER DATABASE CLEAR UNARCHIVED LOGFILE 'C:/Oracle/oradata/XE/REDO03.log'
    *
    ERROR at line 1:
    ORA-01624: log 3 needed for crash recovery of instance xe (thread 1)
    ORA-00312: online log 3 thread 1: 'C:\ORACLE\ORADATA\XE\REDO03.LOG'
    
    
    SQL> RECOVER DATABASE UNTIL CANCEL;
    ORA-00279: change 5587909 generated at 01/06/2012 10:31:25 needed for thread 1
    ORA-00289: suggestion :
    C:\ORACLE\FLASH_RECOVERY_AREA\XE\ARCHIVELOG\2012_01_23\O1_MF_1_216_%U_.ARC
    ORA-00280: change 5587909 for thread 1 is in sequence #216
    
    
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Cancel
    ORA-10879: error signaled in parallel recovery slave
    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: 'C:\ORACLE\ORADATA\XE\SYSTEM01.DBF'
    Please help me

    Thank you in anticipation

    Oracle Universal Installer should be used to uninstall

  • Issue of DB: error ORA-00333 &amp; ORA-01589: must use RESETLOGS or NORESETLOGS

    Hello

    I have question DB Oracle 9.2.0.6.0 all start-up:

    DB mount OK,

    SQL > alter database open;
    change the database open
    *
    ERROR on line 1:
    ORA-00333: make the mistake of reading newspaper block 106498 County 8192


    then I tried some recovery as below, but always error:
    =================================
    SQL > recover database until cancel;
    ORA-00279: change 9228925192024 September at 2010-12-29 15:20:48 needed to screw 1
    ORA-00289: suggestion: /ora/datafile/archive/1_250.dbf
    ORA-00280: change 9228925192024 thread 1 is in sequence #250


    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}

    ORA-00308: cannot open archived log ' / ora/datafile//archive/1_250.dbf'
    ORA-27037: unable to get file status
    Linux error: 2: no such file or directory
    Additional information: 3


    ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
    ORA-01194: file 1 needs a recovery more match
    ORA-01110: data file 1: ' / ora/datafile/system01.dbf'

    ----------------------------------------

    SQL > alter database open resetlogs;
    ALTER database open resetlogs
    *
    ERROR on line 1:
    ORA-01194: file 1 needs a recovery more match
    ORA-01110: data file 1: ' / ora/datafile/system01.dbf'

    ----------------------------------------

    SQL > alter database open;
    change the database open
    *
    ERROR on line 1:
    ORA-01589: must use RESETLOGS or NORESETLOGS option of database open
    ====================================================

    Please guide to do this,

    Thank you and best regards,
    Vishnu

    If the Redo Log file CURRENT (status in V$ LOG or reading the alert.log indicating that the switch in this journal of recovery has been done) is corrupt, the only recourse is to RESTORE the database from a previous backup and then BACK up to the previous to redo log / ArchivedLog.

    See the documentation on the various scenarios:

    http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14191/recoscen.htm#CACFFJFB

    Hemant K Collette

  • ORA-00289: suggestion: /db01/icp/archivelogs/icp.arc1_505.l

    I have applied the required journal and open the db, but I want to just delete my concepts,

    What happens if I need to open db and do not have this available archvielog?
    Why this archivelog is required to open db, I don't even have the data up to this point?
    What is the work around to overcome this? If any



    SQL > recover database until cancel using backup controlfile;
    ORA-00279: change 4447754631511 September at 2009-09-14 10:49:04 needed to
    thread 1
    ORA-00289: suggestion: /tulppwradb_db01/rcicp/archivelogs/rcicp.arc1_505.log
    ORA-00280: change 4447754631511 thread 1 is in sequence #505


    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}
    Cancel
    ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
    ORA-01194: file 1 needs a recovery more match
    ORA-01110: data file 1: ' / tulppwradb_db01/rcicp/system01.dbf'
    ORA-01112: media recovery not started

    Of your data file is Fuzzy mode, check that one by doing:

    Select file #, STATUS, FUZZY from v$ datafile_header;

    Apply several newspapers archive to get this data out of this mode file.

    This error may occur because you must always apply the journal online redo current during recovery. Although this remake online journal and then open the database with resetlogs.

    concerning

  • The database recovery

    Hi all

    EBS R12.2.4

    OEL6

    I play with the recovery of database > restore database using backup controlfile until cancel;

    but I encountered error:

    ORA-00279: change 5965308871319 September at 29/11/2015 10:49:20 needed to

    thread 1

    ORA-00289: suggestion: /home/ARCH/1_212_894234402.dbf

    ORA-00280: change 5965308871319 thread 1 is in sequence #212

    ORA-00278: log file ' / home/ARCH/1_211_894234402.dbf' is no longer necessary for this

    recovery

    ORA-00283: cool cancelled due to errors

    ORA-01244: datafile (s) without a name added to the control file by the media recovery

    ORA-01110: data file 42: ' / home/oraprod/PROD/data/a_txn_ind10.dbf'

    ORA-01112: media recovery not started

    SQL > shutdown immediate;

    ORA-01109: database is not open

    The database is dismounted.

    ORACLE instance stops.

    SQL > bootable media.

    ORACLE instance started.

    Total System Global Area 2137886720 bytes

    Bytes of size 2230072 fixed

    452987080 variable size bytes

    1660944384 of database buffers bytes

    Redo buffers 21725184 bytes

    Mounted database.

    SQL > restore database using backup controlfile until cancel;

    ORA-00283: cool cancelled due to errors

    ORA-01111: 42 data file name is unknown - rename it to the correct file

    ORA-01110: data file 42: ' / home/oraprod/PROD/11.2.0/dbs/UNNAMED00042'

    ORA-01157: cannot identify/lock data file of 42 - see DBWR trace file

    ORA-01111: 42 data file name is unknown - rename it to the correct file

    ORA-01110: data file 42: ' / home/oraprod/PROD/11.2.0/dbs/UNNAMED00042'

    SQL >

    Help, please...

    Thank you

    JC

    You cannot copy directly, but you can save only data file with rman "backup datafile 42. However, the RCS in the header of the data file would be different now, and you cannot recover.

    You said in one of the message that the file without a NAME no longer exists? You rename it using 'alter database rename file '?

    You can use:

    ALTER database create datafile 42 as ' / home/oraprod/PROD/data/a_txn_ind10.dbf';

    Then run:

    RECOVER THE DATABASE AUTOMATICALLY USING BACKUP CONTROLFILE UNTIL CANCEL

  • Restore the backup from primary to the DR Server online

    Hello

    I'm on Oracle 10.2 and restore an online backup of the main server on server of DR. Online backup has been taken: 30.11.2015 21:00 and ends at 01.12.2015 01:23:16.

    The first redo log when the backup began 60588 and the last roll forward log is 60596 when the backup is complete according to the backup log.

    However, it is beyond ask 60596 when you are recovering:

    SQL > restore database to sleep by using backup controlfile until cancel;

    ORA-00279: change 952123702 generated at 01/12/2015 04:50:25 needed for thread

    1

    ORA-00289: suggestion: L:\ORACLE\A30\ORAARCH\A30ARCH\ARC60598_0681431456.001

    ORA-00280: change 952123702 thread 1 is in sequence #60598

    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}

    ORA-00279: change 952134239 generated at 01/12/2015 05:50:32 needed for thread

    1

    ORA-00289: suggestion: L:\ORACLE\A30\ORAARCH\A30ARCH\ARC60599_0681431456.001

    ORA-00280: change 952134239 thread 1 is in sequence #60599

    ORA-00278: save the file 'L:\ORACLE\A30\ORAARCH\A30ARCH\ARC60598_0681431456.001' not

    longer needed for recovery

    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}

    ORA-00279: change 952145796 generated at 01/12/2015 06:51:06 needed for thread

    1

    ORA-00289: suggestion: L:\ORACLE\A30\ORAARCH\A30ARCH\ARC60600_0681431456.001

    ORA-00280: change 952145796 thread 1 is in sequence #60600

    ORA-00278: save the file 'L:\ORACLE\A30\ORAARCH\A30ARCH\ARC60599_0681431456.001' not

    longer needed for recovery

    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}

    ORA-00279: change 952155617 generated at 01/12/2015 07:51:51 needed for thread

    1

    ORA-00289: suggestion: L:\ORACLE\A30\ORAARCH\A30ARCH\ARC60601_0681431456.001

    ORA-00280: change 952155617 thread 1 is in sequence #60601

    ORA-00278: save the file 'L:\ORACLE\A30\ORAARCH\A30ARCH\ARC60600_0681431456.001' not

    longer needed for recovery

    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}

    ORA-00308: cannot open archived log

    'L:\ORACLE\A30\ORAARCH\A30ARCH\ARC60601_0681431456.001 '.

    ORA-27041: could not open the file

    04002 - OSD: could not open the file

    S/O-error: (OS 2) the system cannot find the file specified.

    ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error

    ORA-01152: 1 no file has been restored from a sufficiently old backup

    ORA-01110: data file 1: ' Z:\ORACLE\A30\SAPDATA1\SYSTEM_1\SYSTEM. DATA1'

    SQL > ALTER DATABASE ENABLE PENDING DATA base;

    ALTER DATABASE ACTIVATE STANDBY DATABASE

    *

    ERROR on line 1:

    ORA-01152: 1 no file has been restored from a sufficiently old backup

    ORA-01110: data file 1: ' Z:\ORACLE\A30\SAPDATA1\SYSTEM_1\SYSTEM. DATA1'

    I noticed after I applied 60598, he said:


    ORA-00278: log "L:\ORACLE\A30\ORAARCH\A30ARCH\ARC60598_0681431456.001" file is no longer needed for recovery


    This means 60598 is really not necessary for recovery?

    No idea why she asked newspaper after 60596?

    How can I check which is the last log to roll forward to complete recovery?

    V$ RECOVERY_LOG shows nothing.

    Thank you.

    Hello

    If you try to enable the database, please make sure the SNA aligns with... In your case, controlfile raised YVERT YVERT/bass.

    If you try to re-create the controlfile.

    After you re-create the controlfile, you can run a fake recovery and open in resetlogs.

    After you re-create the controlfile

    SQL > restore database using backup controlfile until cancel;

    SQL > alter database open resetlogs;

    Thank you

  • How to COPY a BACKUP as the... CONTROLFILE can be used for the OPEN database

    I create a document such as a "How To" to move a position for a Junior DBA controlfile.

    But it seems that I'm the Junior because I am facing the following...

    Action plan:

    Move/rename a Controlfile

    Version of the database: 11.2.0.3

    Controlfiles moving of:

    / goldengate/ORCL/ORADATA /.

    TO:

    / GoldenGate/ORCL/controlfile

    Step 1: Set up environment variables

    $> export ORACLE_SID = ORCL1

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    $> echo $ORACLE_SID

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    ORCL1

    $> export ORACLE_BASE = / u01/app/oracle

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    $> echo $ORACLE_BASE

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    / u01/app/Oracle

    $> export ORACLE_HOME=$ORACLE_BASE/product/11.2.0.3/dbhome_1

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    $ echo $ORACLE_HOME

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    /U01/app/Oracle/product/11.2.0.3/dbhome_1

    Step 2: Check control_files parameter

    $> echo "see THE PARAMETER control_files | sqlplus-s "virtue sysdba".

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    VALUE OF TYPE NAME

    ------------------------------------ ----------- ------------------------------

    control_files string/goldengate/ORCL/ORADATA/control

    ol01. CTL, / goldengate/ORCL/ORA

    DATA/control02.ctl

    Step 3: Closing the open database

    $> echo 'SHUTDOWN IMMEDIATE'; | sqlplus-s "virtue sysdba".

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    The database is closed.

    The database is dismounted.

    ORACLE instance stops.

    Step 4: Editing of the database

    $> echo "STARTUP MOUNT"; | sqlplus-s "virtue sysdba".

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    ORACLE instance started.

    Total System Global Area 4275781632 bytes

    Bytes of size 2235208 fixed

    822084792 variable size bytes

    3439329280 of database buffers bytes

    Redo buffers 12132352 bytes

    Mounted database.

    Step 5: Creating a copy of the current controlfile

    $> echo "AS BACKUP COPY CURRENT CONTROLFILE FORMAT ' / goldengate/ORCL/CONTROLFILE/control01.copy.ctl'; ' | RMAN target / nocatalog

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Recovery Manager: release 11.2.0.3.0 - Production Fri Oct 22 17:03:27 2015

    Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

    connected to target database: ORCL (DBID = 1420762587, is not open)

    using the control file of the target instead of recovery catalog database

    RMAN >

    From 22 October 15 backup

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: SID = 58 type of device = DISK

    channel ORA_DISK_1: from data file copy

    copy the current control file

    tag name=/goldengate/ORCL/CONTROLFILE/control01.copy.ctl output file = RECID = 1 STAMP = 893783011 TAG20151022T170329

    channel ORA_DISK_1: datafile copy complete, duration: 00:00:03

    Backup finished at 22 October 15

    RMAN >

    Complete recovery manager.

    Step 6: Change of parameter control_files

    $> echo "ALTER SYSTEM SET control_files='/goldengate/ORCL/CONTROLFILE/control01.copy.ctl' SCOPE = SPFILE;" | sqlplus-s "virtue sysdba".

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Modified system.

    Step 7: Closing of the mounted database

    $> echo 'SHUTDOWN IMMEDIATE'; | sqlplus-s "virtue sysdba".

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    ORA-01109: database is not open

    The database is dismounted.

    ORACLE instance stops.

    Step 8: Installation of the database

    $> echo "STARTUP MOUNT"; | sqlplus-s "virtue sysdba".

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    ORACLE instance started.

    Total System Global Area 4275781632 bytes

    Bytes of size 2235208 fixed

    822084792 variable size bytes

    3439329280 of database buffers bytes

    Redo buffers 12132352 bytes

    Mounted database.

    Step 9: Check control_files parameter

    $> echo "see THE PARAMETER control_files | sqlplus-s "virtue sysdba".

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    VALUE OF TYPE NAME

    ------------------------------------ ----------- ------------------------------

    control_files string/goldengate/ORCL/CONTROLFILE/c

    ontrol01. Copy.CTL

    Step 10: Open the mounted database

    $> echo "ALTER DATABASE OPEN"; | sqlplus-s "virtue sysdba".

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    ALTER DATABASE OPEN

    *

    ERROR on line 1:

    ORA-01589: must use RESETLOGS or NORESETLOGS option of database open

    $> echo "ALTER DATABASE OPEN NORESETLOGS"; | sqlplus-s "virtue sysdba".

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    ALTER DATABASE OPEN NORESETLOGS

    *

    ERROR on line 1:

    ORA-01610: recovery using BACKUP CONTROLFILE option must be

    Then...

    $> sqlplus/nolog

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    SQL * more: Production release 11.2.0.3.0 the game Oct 22 17:14:43 2015

    Copyright (c) 1982, 2011, Oracle.  All rights reserved.

    SQL > CONNECT sysdba virtue

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Connected.

    SQL > RECOVER DATABASE with the HELP of BACKUP CONTROLFILE until CANCEL;

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    ORA-00279: change 621941 September at 22/10/2015 16:57:33 needed to screw 1

    ORA-00289: suggestion:

    /U01/app/Oracle/product/11.2.0.3/dbhome_1/DBS/arch1_11_892981851.dbf

    ORA-00280: change 621941 thread 1 is in sequence #11

    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}

    Cancel

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Cancelled media recovery.

    SQL > ALTER DATABASE OPEN;

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    ALTER DATABASE OPEN

    *

    ERROR on line 1:

    ORA-01589: must use RESETLOGS or NORESETLOGS option of database open

    Issues related to the:

    What am I misunderstanding? BACKUP COPY THAT isn't really a COPY.

    Why I can't use the 'copy' of the controlfile created by RMAN?

    Note:

    If I just copy the controlfile to the new location when the database shuts down everything works fine.

    Thanks in advance.

    Juan M


    Recovery Manager (RMAN)

    It is also mentioned in https://docs.oracle.com/cd/E11882_01/server.112/e25494/control.htm#ADMIN11288

    Create additional Copies, rename and move the control files

  • Recovery media - cannot find the archived log

    Oracle 10g Release 2

    Database works in mode noarchive - isn't my choice, so I'm stuck with it.

    SQL> select startup_time,status,database_status from v$instance;
    
    STARTUP_T STATUS       DATABASE_STATUS
    --------- ------------ -----------------
    20-AUG-15 MOUNTED      ACTIVE
    
    SQL> alter database open;
    alter database open
    *
    ERROR at line 1:
    ORA-01113: file 2 needs media recovery
    ORA-01110: data file 2: '/ads/database06/oracle/oradata/ODB1/UNDOTBS03.dbf'
    
    SQL> recover datafile '/ads/database06/oracle/oradata/ODB1/UNDOTBS03.dbf';
    ORA-00279: change 24699944499 generated at 08/08/2015 01:07:04 needed for thread 1
    ORA-00289: suggestion :
    /oracle/product/10.2.0/flash_recovery_area/ODB1/archivelog/2015_08_21/o1_mf_1_698472_%u_.arc
    ORA-00280: change 24699944499 for thread 1 is in sequence #698472
    
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    
    ORA-00308: cannot open archived log
    '/oracle/product/10.2.0/flash_recovery_area/ODB1/archivelog/2015_08_21/o1_mf_1_698472_%u_.arc'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    
    $ cd /oracle/product/10.2.0/flash_recovery_area/ODB1/archivelog/2015_08_21
    
    $ ls o1_mf_1_698472_%u_.arc
    o1_mf_1_698472_%u_.arc: No such file or directory
    
    The entire directory is empty.
    

    There is no data for August 21, 2015, the database is offline for a few days.

    The database has been cloned by the system administrator, so nobody was on this database. New server.

    orclrunner wrote:

    That was my thought as well. They have made a copy ' hot' all the files. I think they should have stop the database before copying files.

    a ' hot' copy can succeed but each tablespace must have been in online BACKUP before doing the copy of OS files.

    With DB mode noarchive, a copy hot may or may not succeed according to the DML activity & duration of the COPY

    It's better to STOP NOW before copy of OS

  • Regarding the backup problem

    Hi all

    Recently, my database is down during backup. I tried to open the database, but it gave the error «File needs more recovery»

    I checked the backup mode is not active. I used the command "recover database until cancel using backup control file" (which should not be used) instead of only "recover the database.

    Now the database is looking in the backup control file and asking for more log archiving of recovery which has not yet occurred. do I have to cancel this backup control file to use the original control file to recover the database.

    Please notify.

    Thanks in advance

    Amit Dwivedi

    Hello

    1. Once you have used the backup control file option, there is no way you can do DB forget "backup control file is used.

    2. even after that application to redo online still records DB should be opened with RESETLOGS.

    3. Please be aware of the risk of open with RESETLOGS, this is the last recommended option.

    NOTE: If there is a system very important and crucial then it is recommended to register a service request with support.

    Refer to: backup and recovery scenarios (Doc ID 94114.1)

    Kind regards

    Ramana Rao - Oracle

    Here it is an example that is set up on 11g DB 11.2.0 on Linux x86_64 only for demonstration purposes:

    -Example Demo starts here-

    SQL > alter tablespace test begin backup;

    Tablespace altered.

    SQL > the judgment;

    ORACLE instance stops.

    -----------------------------------------------------------------------------------------------------------------------

    Comments: Force DB have a script failed

    -----------------------------------------------------------------------------------------------------------------------

    SQL > startup

    ORACLE instance started.

    Total System Global Area 534462464 bytes

    Bytes of size 2230072 fixed

    444598472 variable size bytes

    Buffers data 83886080 bytes

    Redo buffers 3747840 bytes

    Mounted database.

    ORA-10873: file 7 must be either switched off mode backup or recovered media

    ORA-01110: data file 7: ' / home/oracle/app/oracle/oradata/orcl/tet1.dbf'

    -----------------------------------------------------------------------------------------------------------------------

    Comments: DB Complains that a file is in need of recovery backup mode or media

    -----------------------------------------------------------------------------------------------------------------------

    SQL > restore database using backup controlfile until cancel;

    ORA-00279: change 3258225 September at 24/07/2015 05:10:47 necessary to screw 1

    ORA-00289: suggestion: /home/oracle/app/oracle/fast_recovery_area/ORCL/archivelog/2015_07_24/o1_mf_1_93_%u_.arc

    ORA-00280: change 3258225 thread 1 is in sequence #93

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    Comments: on purpose we use here backup control file option to simulate the same error condition

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    SQL > select FIRST_CHANGE #, NEXT_CHANGE #, name from v$ archived_log;

    FIRST_CHANGE # NEXT_CHANGE # NAME

    ------------- ------------------- -----------------------------------------------------------------------------------------------

    3244150 3254238 /home/oracle/app/oracle/fast_recovery_area/ORCL/archivelog/2015_07_24/o1_mf_1_88_bv3ys3h1_.arc

    3254238 3256570 /home/oracle/app/oracle/fast_recovery_area/ORCL/archivelog/2015_07_24/o1_mf_1_89_bv406xf3_.arc

    3256570 3257119 /home/oracle/app/oracle/fast_recovery_area/ORCL/archivelog/2015_07_24/o1_mf_1_90_bv407l01_.arc

    3257119 3257697 /home/oracle/app/oracle/fast_recovery_area/ORCL/archivelog/2015_07_24/o1_mf_1_91_bv4085h7_.arc

    3257697 3258225 /home/oracle/app/oracle/fast_recovery_area/ORCL/archivelog/2015_07_24/o1_mf_1_92_bv408qpq_.arc

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    Comments: The archive log asked o1_mf_1_93_%u_.arc is not yet produced.

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    SQL > select file #, checkpoint_change # from v$ datafile_header;

    FILE # CHECKPOINT_CHANGE #.

    --------------    -----------------------------------------

    1 3258225

    2 3258225

    3 3258225

    4 3258225

    5 3258225

    6 3258225

    7 3263717<><>

    7 selected lines.

    SQL > alter database end backup;

    Database altered.

    SQL > alter database open;

    change the database open

    *

    ERROR on line 1:

    ORA-01589: must use RESETLOGS or NORESETLOGS option of database open

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    Comments: Safe Option: end DB back up and open.

    But DB is aware of this backup control file is used so refuses to open.

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    SQL > alter database open noresetlogs;

    ALTER database open noresetlogs

    *

    ERROR on line 1:

    ORA-01588: must use RESETLOGS open database option

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    Comments: Safe Option: open with NORESETLOGS.

    But DB is aware of this backup control file is used so refuses to open.

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    SQL > restore database;

    ORA-00283: cool cancelled due to errors

    ORA-01610: recovery using BACKUP CONTROLFILE option must be

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    Comments: Safe Option: try with database recovery

    But DB is aware of this backup control file is used therefore requires to use the backup controlfile option

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    SQL > restore database using backup controlfile

    ORA-00279: change 3258225 September at 24/07/2015 05:10:47 necessary to screw 1

    ORA-00289: suggestion: /home/oracle/app/oracle/fast_recovery_area/ORCL/archivelog/2015_07_24/o1_mf_1_93_%u_.arc

    ORA-00280: change 3258225 thread 1 is in sequence #93

    Specify the log: {= suggested |} Filename | AUTO | CANCEL}

    /Home/Oracle/app/Oracle/oradata/ORCL/redo01.log

    ORA-00310: archived log contains sequence 91; sequence required 93

    ORA-00334: archived log: ' / home/oracle/app/oracle/oradata/orcl/redo01.log'

    SQL > restore database using backup controlfile

    ORA-00279: change 3258225 September at 24/07/2015 05:10:47 necessary to screw 1

    ORA-00289: suggestion: /home/oracle/app/oracle/fast_recovery_area/ORCL/archivelog/2015_07_24/o1_mf_1_93_%u_.arc

    ORA-00280: change 3258225 thread 1 is in sequence #93

    Specify the log: {= suggested |} Filename | AUTO | CANCEL}

    /Home/Oracle/app/Oracle/oradata/ORCL/redo02.log

    ORA-00310: archived log contains sequence 92; sequence required 93

    ORA-00334: archived log: ' / home/oracle/app/oracle/oradata/orcl/redo02.log'

    SQL > restore database using backup controlfile;

    ORA-00279: change 3258225 September at 24/07/2015 05:10:47 necessary to screw 1

    ORA-00289: suggestion: /home/oracle/app/oracle/fast_recovery_area/ORCL/archivelog/2015_07_24/o1_mf_1_93_%u_.arc

    ORA-00280: change 3258225 thread 1 is in sequence #93

    Specify the log: {= suggested |} Filename | AUTO | CANCEL}

    /Home/Oracle/app/Oracle/oradata/ORCL/redo03.log

    Application log.

    Complete media recovery.

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    Comments: Applied online redo logs manually.

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    SQL > alter database open;

    change the database open

    *

    ERROR on line 1:

    ORA-01589: must use RESETLOGS or NORESETLOGS option of database open

    SQL > alter database open noresetlogs;

    ALTER database open noresetlogs

    *

    ERROR on line 1:

    ORA-01588: must use RESETLOGS open database option

    SQL > alter database open resetlogs;

    Database altered.

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    Comments: Only able to open with the RESETLOGS Option.

    ---------------------------------------------------------------------------------------------------------------------------------------------------

    ------------------------------- Example Demo Ends here --------------------------------------------

  • Corrupted Redo on 11i?

    Hi all

    EBS 11Ii

    9i Db

    I begin our 11i apps/database using:

    [oradev@oratrng5 ~] start of /u02/oradev/devdb/9.2.0/appsutil/scripts/DEV_oratrng5/addbctl.sh $

    You are running version 115.8 addbctl.sh

    From the DEV database...

    SQL * more: release 9.2.0.6.0 - Production Sat Jun 13 18:01:32 2015

    Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

    Connect to an instance is idle.

    ORACLE instance started.

    Total System Global Area 581506668 bytes

    Bytes of size 452204 fixed

    402653184 variable size bytes

    167772160 of database buffers bytes

    Redo buffers 10629120 bytes

    Mounted database.

    ORA-00354: corrupted redo log block header

    ORA-00353: journal corruption close change 204333 block 5977336119449 time

    21:50:16 12/06/2015

    ORA-00312: wire 3 1 online journal: ' / u02/oradev/devdata/log03b.dbf'

    ORA-00312: wire 3 1 online journal: ' / u02/oradev/devdata/log03a.dbf'

    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production

    With partitioning, OLAP and Oracle Data Mining options

    Release 9.2.0.6.0 - Production jserver

    addbctl.sh: exit with status 0

    [oradev@oratrng5 ~] $

    ===========================

    It was still good since yesterday

    What causes this corruption?

    I tried to run 'recover data' but nothing helped.

    Help, please...

    Thank you very much.

    JC

    Hi all

    I put > _allow_resetlogs_corruption = TRUE

    And I was able to OPET the database resetlogs.

    SQL > recover database until cancel;

    ORA-00279: change 5977336119448 September at 13/06/2015 to 07:10:45

    thread 1

    ORA-00289: suggestion: /u02/oradev/devdb/9.2.0/dbs/arch/1_30.dbf

    ORA-00280: change 5977336119448 thread 1 is in sequence #30

    Specify the log: {= suggested |} Filename | AUTO | CANCEL}

    Cancel

    ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error

    ORA-01194: file 1 needs a recovery more match

    ORA-01110: data file 1: ' / u02/oradev/devdata/system01.dbf'

    ORA-01112: media recovery not started

    SQL > alter database open resetlogs;

    Database altered.

    ============

    Is it enough now? The docs said to create the database after its opening.

    But has not explained how and why?

    Thank you very much.

  • recovery - request to get next sequence archive # to apply

    Hello guys,.

    I'm working on a database of Eve by script and I need to get the next archive sequence # to get it back.

    When I run the recovery database he knows who is the current change # and what is the next sequence archive #.

    SQL > restore database using backup controlfile;

    ORA-00279: change 5634463917 at 11/05/2015 September 02:13:50 needed for thread

    1

    ORA-00289: suggestion: /u01/archive/archive_1_142116_848080349.arch

    ORA-00280: change 5634463917 for thread 1 is in sequence #142116


    I just need a query for change # or the sequence #.

    Any help will be appreciated.

    Thank you.

    Jonas

    Hi John,.

    I think I got it.

    Select sequence #.

    v $ archived_log

    where first_change # in (select min(change#) from v$ recover_file);

    Don't know if this is the best way, but seems to work...

    Thanks for your help.

    Jonas

  • How to recover the database with RMAN avoiding blur

    Hi gurus,


    I'm stuck in a situation and need your help.

    We check if our backups are valid or not. So it gave me a new server and backups/archives to a 2 TB database I need to restore/recovery. I followed steps below.

    (1) copied the prod parameter file to test.

    (2) make the necessary changes in the init file.

    db_file_name_convert, etc..

    (3) start db in nomount mode.

    (4) restore the backup control file

    Restore controlfile to ' / oraback/ARCH/prod/backup_controlfiles/c-250795000-20141030-01';

    (5) mount the database.

    (6) created under the rman script and executed.

    Run {}

    Catalogue start with ' / oraback/RMAN/test "noprompt.

    Catalogue start with ' / oraback/ARCH/test "noprompt.

    allocate channel C1 device type disk;

    allocate channel C2 device type disk;

    allocated channel C3 device type disk;

    allocate channel C4 device type disk;

    allocate channel C5 device type disk;

    allocate channel C6 device type disk;

    allocate channel C7 device type disk;

    allocate channel C8 device type disk;

    @rename_datafiles.lst

    @rename_logfiles.lst

    until the SNA 144390584718.

    restore the database;

    switch datafile;

    recover the database

    }

    Questions-

    -Restore completed successfully, but I found that few archives are missing.

    -I pulled from database to recover until cancel using backup controlfile; There is a below error

    ORA-01152: 1 no file has been restored from a sufficiently old backup

    ORA-01110: data file 1: ' / u02/oradata/testsystem01.dbf'

    -Then tried to restore the archive of available backup archive and few of archives have been restored.

    i.e. of sequence between 759529 and 759552.

    And then I pulled the database until cancel using backup controlfile recovery and I got errors below.

    SQL > restore database using backup controlfile until cancel;

    ORA-00279: change 144185396330 September at 26/10/2014 to 08:14:01

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759541_535023608.arc

    ORA-00280: change 144185396330 thread 1 is in sequence #759541

    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}

    Auto

    ORA-00279: change 144187549215 September at 26/10/2014 to 08:22:05

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759542_535023608.arc

    ORA-00280: change 144187549215 thread 1 is in sequence #759542

    ORA-00278: log file ' / oraback/ARCH/arch_1_759541_535023608.arc' is no longer

    necessary for this recovery

    ORA-00279: change 144187559176 September at 26/10/2014 08:28:41 needed to

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759543_535023608.arc

    ORA-00280: change 144187559176 thread 1 is in sequence #759543

    ORA-00278: log file ' / oraback/ARCH/arch_1_759542_535023608.arc' is no longer

    necessary for this recovery

    ORA-00279: change 144188388865 September at 26/10/2014 08:36:51 needed to

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759544_535023608.arc

    ORA-00280: change 144188388865 thread 1 is in sequence #759544

    ORA-00278: log file ' / oraback/ARCH/arch_1_759543_535023608.arc' is no longer

    necessary for this recovery

    ORA-00279: change 144188399424 September at 26/10/2014 08:46:40 needed to

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759545_535023608.arc

    ORA-00280: change 144188399424 thread 1 is in sequence #759545

    ORA-00278: log file ' / oraback/ARCH/arch_1_759544_535023608.arc' is no longer

    necessary for this recovery

    ORA-00279: change 144189462436 September at 26/10/2014 08:54:04 needed to

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759546_535023608.arc

    ORA-00280: change 144189462436 thread 1 is in sequence #759546

    ORA-00278: log file ' / oraback/ARCH/arch_1_759545_535023608.arc' is no longer

    necessary for this recovery

    ORA-00279: change 144189469985 September at 26/10/2014 08:58:13 needed to

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759547_535023608.arc

    ORA-00280: change 144189469985 thread 1 is in sequence #759547

    ORA-00278: log file ' / oraback/ARCH/arch_1_759546_535023608.arc' is no longer

    necessary for this recovery

    ORA-00279: change 144189577217 September at 26/10/2014 to 09:01:38

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759548_535023608.arc

    ORA-00280: change 144189577217 thread 1 is in sequence #759548

    ORA-00278: log file ' / oraback/ARCH/arch_1_759547_535023608.arc' is no longer

    necessary for this recovery

    ORA-00279: change 144189584836 September at 26/10/2014 to 09:05:26

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759549_535023608.arc

    ORA-00280: change 144189584836 thread 1 is in sequence #759549

    ORA-00278: log file ' / oraback/ARCH/arch_1_759548_535023608.arc' is no longer

    necessary for this recovery

    ORA-00279: change 144189699671 September at 26/10/2014 to 09:09:23

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759550_535023608.arc

    ORA-00280: change 144189699671 thread 1 is in sequence #759550

    ORA-00278: log file ' / oraback/ARCH/arch_1_759549_535023608.arc' is no longer

    necessary for this recovery

    ORA-00279: change 144189708674 September at 26/10/2014 to 09:14:23

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759551_535023608.arc

    ORA-00280: change 144189708674 thread 1 is in sequence #759551

    ORA-00278: log file ' / oraback/ARCH/arch_1_759550_535023608.arc' is no longer

    necessary for this recovery

    ORA-00279: change 144189715134 September at 26/10/2014 to 09:21:51

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759552_535023608.arc

    ORA-00280: change 144189715134 thread 1 is in sequence #759552

    ORA-00278: log file ' / oraback/ARCH/arch_1_759551_535023608.arc' is no longer

    necessary for this recovery

    ORA-00279: change 144189715148 September at 26/10/2014 to 09:21:52

    thread 1

    ORA-00289: suggestion: /oraback/ARCH/arch_1_759553_535023608.arc

    ORA-00280: change 144189715148 thread 1 is in sequence #759553

    ORA-00278: log file ' / oraback/ARCH/arch_1_759552_535023608.arc' is no longer

    necessary for this recovery

    ORA-00308: cannot open archived log ' / oraback/ARCH/arch_1_759553_535023608.arc'

    ORA-27037: unable to get file status

    IBM AIX RISC System/6000 error: 2: no such file or directory

    Additional information: 3

    ORA-10879: error reported in parallel recovery slave

    ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error

    ORA-01194: file 6 recovery needs more match

    ORA-01110: data file 6: ' / u01/oradata/testchgtwy_data01.dbf'

    -Now when I tried to open the database with resetlogs it gives below error.

    SQL > alter database open resetlogs;

    ALTER database open resetlogs

    *

    ERROR on line 1:

    ORA-01194: file 6 recovery needs more match

    ORA-01110: data file 6: ' / u01/oradata/testchgtwy_data01.dbf'

    -I found that sequence backup archives are missing 759553 to 759599. This is not present in the primary also.

    -I tried to check the blur of datafiles and achieved lower results.

    ALTER session set nls_date_format = 'DD-MON-YYYY HH24:MI:SS ";

    Set of feedback on

    topic on the value

    set pagesize 1000

    set linesize 175

    format of column checkpoint_change # 999999999999999999999

    Select the State, checkpoint_change #, fuzzy,.

    TO_CHAR (checkpoint_time, ' ' MON-DD-YYYY HH24:MI:SS) as checkpoint_time,.

    Count (*)

    v $ datafile_header

    Status group, checkpoint_change #, fuzzy, checkpoint_time

    order of the State, checkpoint_change #, fuzzy, checkpoint_time;

    STATUS CHECKPOINT_CHANGE # CHECKPOINT_TIME FUZZY COUNT (*)

    --------------------- ---------------------- --------- -------------------- ----------

    144189715148. ONLINE NO 26 OCTOBER 2014 09:21:52 123

    ONLINE 144375495577 YES 29 OCTOBER 2014 20:30:23 1

    ONLINE 144375495581 YES 29 OCTOBER 2014 20:30:23 1

    ONLINE 144375891732 YES 29 OCTOBER 2014 20:52 1

    ONLINE 144375891955 YES 29 OCTOBER 2014 20:52:03 1

    144376850545. ONLINE NO 29 OCTOBER 2014 21:13:10 1

    ONLINE 144376866610 YES 29 OCTOBER 2014 21:13:36 1

    ONLINE 144377230506 YES 29 OCTOBER 2014 21:31:42 1

    ONLINE 144377313738 YES 29 OCTOBER 2014 21:35:47 1

    144377571340. ONLINE NO 29 OCTOBER 2014 21:53:33 1

    ONLINE 144377625895 YES 29 OCTOBER 2014 21:57:39 1

    ONLINE 144378445278 YES 29 OCTOBER 2014 22:13:37 1

    ONLINE 144378578727 YES 29 OCTOBER 2014 22:20:43 1

    ONLINE 144378877241 YES 29 OCTOBER 2014 22:35:59 1

    ONLINE 144378912130 YES 29 OCTOBER 2014 22:42:25 1

    ONLINE 144379435791 YES 29 OCTOBER 2014 22:57:31 1

    ONLINE 144379545905 YES 29 OCTOBER 2014 23:03:17 1

    ONLINE 144379631677 YES 29 OCTOBER 2014 23:18:53 1

    ONLINE 144379637933 YES 29 OCTOBER 2014 23:24:18 1

    ONLINE 144380039550 YES 29 OCTOBER 2014 23:37:44 1

    ONLINE 144380054601 YES 29 OCTOBER 2014 23:41:40 1

    ONLINE 144380099883 YES 29 OCTOBER 2014 23:54:16 1

    ONLINE 144380114063 YES 29 OCTOBER 2014 23:59:41 1

    ONLINE 144380676881 YES 30 OCTOBER 2014 00:13:27 1

    ONLINE 144380869308 YES 30 OCTOBER 2014 00:20:33 1

    ONLINE 144381101372 YES 30 OCTOBER 2014 00:32:49 1

    ONLINE 144381124605 YES 30 OCTOBER 2014 00:40:54 1

    ONLINE 144381393417 YES 30 OCTOBER 2014 00:51:20 1

    ONLINE 144382166578 YES 30 OCTOBER 2014 01:00:46 1

    ONLINE 144382500313 YES 30 OCTOBER 2014 01:10:11 1

    ONLINE 144382666697 YES 30 OCTOBER 2014 01:18:47 1

    ONLINE 144382861398 YES 30 OCTOBER 2014 01:30:02 1

    ONLINE 144383132266 YES 30 OCTOBER 2014 01:37:38 1

    ONLINE 144383283837 YES 30 OCTOBER 2014 01:48:24 1

    ONLINE 144383580087 YES 30 OCTOBER 2014 01:55:49 1

    ONLINE 144384682269 YES 30 OCTOBER 2014 02:06:55 1

    ONLINE 144384792040 YES 30 OCTOBER 2014 02:12:50 1

    144385726601. ONLINE NO OCTOBER 30, 2014 02:24:16 1

    144385779382. ONLINE NO OCTOBER 30, 2014 02:29:51 1

    ONLINE 144385956865 YES 30 OCTOBER 2014 02:41:27 1

    ONLINE 144386015770 YES 30 OCTOBER 2014 02:46:22 1

    ONLINE 144386151651 YES 30 OCTOBER 2014 02:59:08 1

    ONLINE 144386317681 YES 30 OCTOBER 2014 03:04:13 1

    ONLINE 144386563076 YES 30 OCTOBER 2014 03:16:59 1

    ONLINE 144386565235 YES 30 OCTOBER 2014 03:18:44 1

    ONLINE 144386699656 YES 30 OCTOBER 2014 03:31:40 1

    144386801438. ONLINE NO OCTOBER 30, 2014 03:36:15 1

    144387128892. ONLINE NO OCTOBER 30, 2014 03:52:31 1

    ONLINE 144387143873 YES 30 OCTOBER 2014 03:53:56 1

    144387490033. ONLINE NO OCTOBER 30, 2014 04:09:52 1

    ONLINE 144387501235 YES 30 OCTOBER 2014 04:11:27 1

    144388180516. ONLINE NO OCTOBER 30, 2014 04:26:44 1

    ONLINE 144388433270 YES 30 OCTOBER 2014 04:31:19 1

    ONLINE 144388902410 YES 30 OCTOBER 2014 04:42:55 1

    ONLINE 144388917251 YES 30 OCTOBER 2014 04:53:11 1

    ONLINE 144389534812 YES 30 OCTOBER 2014 05:01:56 1

    ONLINE 144389556024 YES 30 OCTOBER 2014 05:08:42 1

    ONLINE 144389674922 YES 30 OCTOBER 2014 05:19:48 1

    ONLINE 144389831920 YES 30 OCTOBER 2014 05:26:13 1

    144389957543. ONLINE NO OCTOBER 30, 2014 05:42:59 1

    ONLINE 144389982414 YES 30 OCTOBER 2014 05:46:24 1

    144390137798. ONLINE NO OCTOBER 30, 2014 05:56:40 1

    ONLINE 144390460229 YES 30 OCTOBER 2014 06:12:36 1

    ONLINE 144390474106 YES 30 OCTOBER 2014 06:13:11 1

    144390582132. ONLINE NO OCTOBER 30, 2014 06:27:27 1

    144390582634. ONLINE NO OCTOBER 30, 2014 06:28:02 1

    (1) how to proceed from here.

    (2) all the changes I need to do to the RMAN script. As I need to automate the process of restoration.

    (3) I don't want to use under hidden settings

    _ALLOW_RESETLOGS_CORRUPTION = TRUE

    _CORRUPTED_ROLLBACK_SEGMENTS = (Automatic Undo segments comma-separated list)

    Thank you for the support.

    You can not ignore the archivelogs.

    If the archivelogs are not available, you need a database backup that was created after missing the last archivelog point.

    Hemant K Collette

  • A few Questions about the manual recovery

    DB version: 11.2.0.3.0
    Platform: Oracle Linux 6.4

    I'm not an expert in recovery.

    We had a level of SAN cloning of a RAC database. We store online Redo logs in the diskgroup RL_DG and ARCH_DG diskgroup Archive redo logs.

    After the plan of SAN cloning (EMC BCV Synch), we tried to start up of the DB using srvctl start database-d < MyDBName > and we got the following error message.

    CRS-5017: the action "ora.msblprd.db start" resource has met the following error:
    ORA-01113: file 4 should media recovery
    ORA-01110: data file 4: "+ MBL_DATA/msblprd/datafile/users.271.803502221".

    We realized that a lot of data (not justs users.dbf) need recovery files. Thus, we tried to run to RECOVER the DATABASE. But it errored out. So, we ran to RECOVER database with the HELP of BACKUP CONTROLFILE until CANCEL ;  command.

    [oracle@mssrpt01dbp1001 ~] $ sqlplus / as sysdba

    SQL * more: Production of the 11.2.0.3.0 version kills him Jun 10 14:41:41 2014

    Copyright (c) 1982, 2011, Oracle.  All rights reserved.

    Connect to an instance is idle.

    SQL > bootable media.
    ORACLE instance started.

    System Global area 8.5516E + 10 bytes
    Bytes of size 2237776 fixed
    Size variable 2.4428E + 10 bytes
    6.0935E + 10 bytes database buffers
    Redo buffers 151142400 bytes
    Mounted database.
    SQL > SELECT MEMBER FROM V$ LOG G, V$ LOGFILE F WHERE G.GROUP # = F.GROUP # AND G.STATUS = 'CURRENT ';

    MEMBERS
    --------------------------------------------------------------------------------
    +RL_DG/msblprd/onlinelog/group_3.258.834497269
    +RL_DG/msblprd/onlinelog/group_3.258.834497283
    +RL_DG/msblprd/onlinelog/group_13.262.834498753
    +RL_DG/msblprd/onlinelog/group_13.262.834498735
    +RL_DG/msblprd/onlinelog/group_32.269.834527443
    +RL_DG/msblprd/onlinelog/group_32.269.834527459
    +RL_DG/msblprd/onlinelog/group_44.267.834526221
    +RL_DG/msblprd/onlinelog/group_44.267.834526237

    8 selected lines.

    SQL >
    SQL >
    SQL > RECOVER DATABASE;
    ORA-00283: cool cancelled due to errors
    ORA-01610: recovery using BACKUP CONTROLFILE option must be

    SQL > RECOVER DATABASE with the HELP of BACKUP CONTROLFILE until CANCEL;
    ORA-00279: change 7996788033403 September at 10/06/2014 04:57:12 to put on 2
    ORA-00289: suggestion: + ARCH_DG
    ORA-00280: change 7996788033403 thread 2 is in sequence #16085


    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}
    +RL_DG/msblprd/onlinelog/group_3.258.834497269
    ORA-00325: journal archived for thread 2, wrong thread # 1 in the header
    ORA-00334: archived log: "+ RL_DG/msblprd/onlinelog/group_3.258.834497269".


    ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
    ORA-01194: file 1 needs a recovery more match
    ORA-01110: data file 1: '+ SBL_DATA/msblprd/datafile/system.260.803502221 '.

    SQL > RECOVER DATABASE with the HELP of BACKUP CONTROLFILE until CANCEL;
    ORA-00279: change 7996788033403 September at 10/06/2014 04:57:12 to put on 2
    ORA-00289: suggestion: + ARCH_DG
    ORA-00280: change 7996788033403 thread 2 is in sequence #16085


    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}
    +RL_DG/msblprd/onlinelog/group_3.258.834497283
    ORA-00325: journal archived for thread 2, wrong thread # 1 in the header
    ORA-00334: archived log: "+ RL_DG/msblprd/onlinelog/group_3.258.834497283".


    ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
    ORA-01194: file 1 needs a recovery more match
    ORA-01110: data file 1: '+ SBL_DATA/msblprd/datafile/system.260.803502221 '.

    SQL > RECOVER DATABASE with the HELP of BACKUP CONTROLFILE until CANCEL;
    ORA-00279: change 7996788033403 September at 10/06/2014 04:57:12 to put on 2
    ORA-00289: suggestion: + ARCH_DG
    ORA-00280: change 7996788033403 thread 2 is in sequence #16085


    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}
    +RL_DG/msblprd/onlinelog/group_13.262.834498753
    ORA-00310: archived log contains sequence 16107. 16085 sequence required
    ORA-00334: archived log: "+ RL_DG/msblprd/onlinelog/group_13.262.834498753".


    ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
    ORA-01194: file 1 needs a recovery more match
    ORA-01110: data file 1: '+ SBL_DATA/msblprd/datafile/system.260.803502221 '.

    -I tried to enter AUTO

    SQL > RECOVER DATABASE with the HELP of BACKUP CONTROLFILE until CANCEL;
    ORA-00279: change 7996788033403 September at 10/06/2014 04:57:12 to put on 2
    ORA-00289: suggestion: + ARCH_DG
    ORA-00280: change 7996788033403 thread 2 is in sequence #16085


    Specify the log: {< RET > = suggested |} Filename | AUTO | CANCEL}
    Auto
    ORA-00308: cannot open archived log "+ ARCH_DG".
    ORA-17503: ksfdopn:2 cannot open file + ARCH_DG
    ORA-15045: ASM '+ ARCH_DG' file name is not in the form of reference


    Attempts above did not work because oracle was looking for the archived logs that was not present in ARCH_DG, RMAN has backed it up to the band and issued "delete entry".

    But I have a few basic questions.

    Question1. Why the command RECOVER DATABASE fail with ORA-01610?

    Question2. RECOVER the DATABASE and recover database using BACKUP CONTROLFILE until CANCEL commands will look only archivelogs not redo logs online. Right? I understand that this database will try to retrieve media by the application online Redo Logs when the STARTUP OPEN command is issued. Right?

    Question3. In the command RECOVER database using BACKUP CONTROLFILE until CANCEL that BACKUP CONTROLFILE, we refer to the?

    Question4. What does AUTO option? in calls it "Specify log" as I have indicated above in red

    Question1. Why the command RECOVER DATABASE fail with ORA-01610?

    Oracle has detected that the controlfile was 'old' (for example had a low point control #) as the database.  If she recognized the controlfile as a BACKUP CONTROLFILE.  You make a full recovery, that can be done if the real current controlfile and redo log files are consistent and 'newer' database in a DATABASE files to RECOVER normal.

    Question2. RECOVER the DATABASE and recover database using BACKUP CONTROLFILE until CANCEL commands will look only archivelogs not redo logs online. Right? I understand that this database will try to retrieve media by the application online Redo Logs when the STARTUP OPEN command is issued. Right?

    N ° N ° (in the normal case) the RECOVERY DATABASE can automatically identify the online redo log file must be applied to make a full recovery.  In your case, Oracle has already tried an incomplete recovery.  It will have to be provided (or be able to AUTOMATICALLY generate) the archivelog file names.  Apply of Redo Log files online only happens to a recovery of Instance - a START after a crash or abort.  Your case is a Media Recovery (again because of the backup control file).

    Question3. In the command RECOVER database using BACKUP CONTROLFILE until CANCEL that BACKUP CONTROLFILE, we refer to the?

    The controlfile you have on the disk is 'old' - it is recognized as a backup controlfile.

    Question4. What does AUTO option? in calls it "Specify log" as I have indicated above in red

    (in the normal case) Oracle can generate the name of the 'next' archivelog file based on the last archivelog applied and the log_archive_dest log_archive_format and.  Given that you had not applied all archivelog and yet, he would not be able to generate the next archivelog expected - this happens also in the RAC recovery where it can generate automatically the archivelog next to (for example) wire #1 file name because the archivelog to thread #1 has been applied, but can still generate automatically for wire #2 until an archivelog was applied.

    You will also notice the inadequacy of sever between the online redo log header and the newspaper WAITED

    > archived log contains sequence 16107. 16085 sequence required

    This means that the data files is much older than the online redo log. Given that your ad doesn't show 22 redo log groups, it is likely that the snapshot log redo DG and DG database files don't match no - the second is much older than the first.  You need an archivelog to apply, not the online redo log.

    Your query on V$ LOG and V$ LOGFILE should always optimasation THREAD # (when CAR is running) and SEQUENCE # (each Thread has it's own sequence)

    You can also view your alerts log. This could indicate that Oracle was trying to recover the datafiles Fuzzy - what would happen if your snapshot was taken without the database in BACKUP mode.

    Talk to EMC and Oracle support for the good tips on how to make a snapshot backup of an Oracle database.  Otherwise, you'll be toast when you need to perform a recovery of real Production database.  I suspect that your DGs and EMC volume is not configured properly to create synchronized instant backups.

    Hemant K Collette

    Post edited by: Hemant K Chitale
    Added sentence "' I suspect that your DGs and EMC volume is not configured properly to create instant backups synchronized." "

Maybe you are looking for

  • Crashing several times per day

    After the update a few days ago, Firefox has started breaking more than once a day. I could just use Facebook or something sudden and it crashes... Maybe it has something to with Java?

  • Satellite A660 Win7 - power management system action center is missing driver

    I replaced the battery on my laptop Toshiba A660-15J and a few months, is back with the battery high capacity and now Action Center 7 win keeps popping up with the message that I need to download and install the missing driver for power management sy

  • Windows Games___.

    Load Windows 7 Professional 32 bit on a new computer... Can not find games (menu) to the right of the control panel as usual comes with all editions of Windows... Don't have microsoft such as Free Cell games, etc. of Mahjong tiles that are normally p

  • Full hard drive space

    I have an alert on my PC the drive backup is saved on the States don't have enough space.  I have two hard drives on my lap top is local disc(C:) qui a l'espace et l'autre est reprise (d), which is one that is almost out of space.)  I never saved bef

  • Hard drive not recognized by BIOS in Dell Precision T7910 workstation

    Greetings, I recently acquired a Dell Precision T7910 workstation without all the hard drives installed, so I went to the store and buy a 240 GB Sandisk SSD put in the hard drive and then installed caddy caddy in port 0 (I also tried port 1 with the