Stoping recovery process....ORA-01110

Hi experts;
I have created physical Standby. I am getting archives when I start the recovery process by issuing
alter database recover managed standby database using current logfile disconnect;
But when I stop this process & alter database open
alter database recover managed standby database cancel
logs reports no error but I get when "alter database open"
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u02/app/oracle/oradata/orcl/system01.dbf'
this. Actually I had copied all datafiles without issuing "ALter database begin backup"
So please provide me the solution
Thanks in Advance

Fayn_dba wrote:
Hi experts;
I have created physical Standby. I am getting archives when I start the recovery process by issuing
alter database recover managed standby database using current logfile disconnect;
But when I stop this process & alter database open
alter database recover managed standby database cancel
logs reports no error but I get when "alter database open"
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u02/app/oracle/oradata/orcl/system01.dbf'
this. Actually I had copied all datafiles without issuing "ALter database begin backup"What procedure you used exactly?
what is the version you are using?
Why cant use RMAN duplicate?
When you start MRP(recovery) do you see any progress there as it is applying?
Read methods to take backups when database is open and do the same.
http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmintro.htm

Similar Messages

  • Error in Recover Database -  ORA-01547 , ORA-01194 and ORA-01110

    Hello folks,
    I am facing a problem when recovering a database..
    I made each tablespace in backup mode, then copied the datafile. I revert back the tablespace status to normal status.Once all datafiles are copied to target location, i created the control file from the source db.
    I started the target db by
    sqlplus "/ as sysdba"
    then i executed the control file
    SQL>@ctrlfile.sql
    Control file got created.
    SQL>recover database until cancel using backup controlfile;
    it asked for archives. I gave the path one by one until everything was done.Now i gave 'cancel' as below.
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 377 needs more recovery to be consistent
    ORA-01110: data file 377: '<path>/xxfndx01.dbf'
    ORA-01112: media recovery not started
    Could anyone please tell me where I went wrong and how can I move ahead from this stage???
    Later on, when I gave open resetlogs, it gave the same error(as below)
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 377 needs more recovery to be consistent
    ORA-01110: data file 377: '<path>/xxfndx01.dbf'
    Please let me know the mistake I made, how to avoid that and how to proceed now ???
    Thanks,
    Cherrish Vaidiyan
    [email protected]

    Hello Cherrish,
    A very good question you have asked. I hope you realize that you're doing an incomplete recovery. There is some amount of information that is still there in the online redo-log, that would not be applied on your target db. Moreover when you're using backup controlfile, you do not know till which point you need to apply archive logs.
    For incomplete recovery, Oracle for some reason has been very strict about the recover database command. i.e.
    recover database using backup controlfile
    recover database using backup controlfile until cancel
    Is not same. It also applies to the command that you had given. By giving the command 'recover database using backup controlfile until cancel', you're telling Oracle that incomplete recovery is in process, and you would do resetelogs, to make sure all files are in sync. This is required when you have lost the redo-logs
    In case you have just lost the control file. All latest redo-logs, archive-logs and datafiles are okay (or have been restored), then recover database using backup controlfile; would work perfectly okay. and resetlogs would not be required.. and that would be a complete recovery
    I hope this all makes sense to you
    Regards
    Sudhanshu

  • ORA-00376,ORA-01110 의 조치 방법

    제품 : ORACLE SERVER
    작성날짜 : 2003-01-15
    ORA-00376,ORA-01110 의 조치 방법
    ================================
    Purpose
    ORA-00376: file 29 cannot be read at this time
    ORA-01110: data file 29: '/db/GICORP_4/axix01.dbf'
    Problem Description
    datafile의 size가 os에서 허용하는 filesize를 초과해서
    발생하는 에러입니다.
    Solution Description:
    unix의 ulimit filesize를 확인해 보시기 바랍니다.
    그리고 datafile size 보다 크도록 수정해 주어야 합니다.
    1. unix ulimit filesize를 증가 시킨다
    C shell인 경우
    % limit filesize <number>
    Bourne 이나 Korn shell 인 경우
    $ ulimit -f <number>
    2. archivelog mode인지 확인합니다
    SVRMGR> select * from v$database;
    NAME CREATED LOG_MODE CHECKPOINT ARCHIVE_CH
    GICORP 05/17/00 13:44:56 ARCHIVELOG 36290290 36284249
    1 row selected.
    3. media recovery가 필요한 datafiles를 찾습니다
    SVRMGR> select * from v$recover_file;
    FILE# ONLINE ERROR CHANGE# TIME
    9 OFFLINE 36287415 12/20/00 23:30:55
    23 OFFLINE 36289350 12/21/00 08:40:54
    28 OFFLINE 36287415 12/20/00 23:30:55
    29 OFFLINE 36287415 12/20/00 23:30:55
    37 OFFLINE 36287415 12/20/00 23:30:55
    5 rows selected.
    4. 각각의 datafile에 대해서 다음을 실행해 줍니다
    SVRMGR> recover datafile '/db/GICORP_4/axix01.dbf';
    Media recovery complete.
    SVRMGR> alter database datafile '/db/GICORP_4/axix01.dbf' ONLINE;
    Statement processed.
    5. database를 restart합니다
    SVRMGR> shutdown
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SVRMGR> startup
    ORACLE instance started.
    Total System Global Area 54578916 bytes
    Fixed Size 69348 bytes
    Variable Size 20783104 bytes
    Database Buffers 33554432 bytes
    Redo Buffers 172032 bytes
    Database mounted.
    Database opened.
    SVRMGR>
    Reference Ducumment
    ---------------------

    Hi,
    You have deleted the data files then how can you expect to query the data :). You need to recover from a valid backup to get the database back. You CAN NOT open database if current undo tablespace data file is gone
    Salman

  • HOW TO RESOLVE ORA-01110 during RMAN restoration in oracle 11g

    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    C:\Documents and Settings\tanmoy>rman
    Recovery Manager: Release 11.1.0.6.0 - Production on Fri Mar 29 22:55:02 2013
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    RMAN> connect target orcl
    target database Password:
    connected to target database (not started)
    RMAN> startup nomount;
    Oracle instance started
    Total System Global Area 535662592 bytes
    Fixed Size 1334380 bytes
    Variable Size 150995860 bytes
    Database Buffers 377487360 bytes
    Redo Buffers 5844992 bytes
    RMAN> restore controlfile from autobackup;
    Starting restore at 29-MAR-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=153 device type=DISK
    recovery area destination: D:\app\administrator\flash_recovery_area
    database name (or database unique name) used for search: ORCL
    channel ORA_DISK_1: AUTOBACKUP D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\AUT
    OBACKUP\2012_12_12\O1_MF_S_801849930_8DJQHTTW_.BKP found in the recovery area
    AUTOBACKUP search with format "%F" not attempted because DBID was not set
    channel ORA_DISK_1: restoring control file from AUTOBACKUP D:\APP\ADMINISTRATOR\
    FLASH_RECOVERY_AREA\ORCL\AUTOBACKUP\2012_12_12\O1_MF_S_801849930_8DJQHTTW_.BKP
    channel ORA_DISK_1: control file restore from AUTOBACKUP complete
    output file name=D:\APP\ADMINISTRATOR\ORADATA\ORCL\CONTROL01.CTL
    output file name=D:\APP\ADMINISTRATOR\ORADATA\ORCL\CONTROL02.CTL
    output file name=D:\APP\ADMINISTRATOR\ORADATA\ORCL\CONTROL03.CTL
    Finished restore at 29-MAR-13
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> catalog recovery area;
    Starting implicit crosscheck backup at 29-MAR-13
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=153 device type=DISK
    Crosschecked 5 objects
    Finished implicit crosscheck backup at 29-MAR-13
    Starting implicit crosscheck copy at 29-MAR-13
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 29-MAR-13
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_12_12\O
    1_MF_1_1450_8DK6YO0M_.ARC
    File Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_12_13\O
    1_MF_1_1451_8DLPSYDY_.ARC
    File Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_12_13\O
    1_MF_1_1452_8DLVBJZ7_.ARC
    File Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_12_13\O
    1_MF_1_1452_8DM0LM1L_.ARC
    File Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_12_13\O
    1_MF_1_1453_8DM0LM1L_.ARC
    File Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_12_13\O
    1_MF_1_1454_8DM0NQ8X_.ARC
    File Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\AUTOBACKUP\2012_12_12\O
    1_MF_S_801849930_8DJQHTTW_.BKP
    searching for all files in the recovery area
    List of Files Unknown to the Database
    =====================================
    File Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_12_13\O
    1_MF_1_1453_8DLXCJOB_.ARC
    Do you really want to catalog the above files (enter YES or NO)? Y
    cataloging files...
    no files cataloged
    List of Files Which Where Not Cataloged
    =======================================
    File Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2012_12_13\O
    1_MF_1_1453_8DLXCJOB_.ARC
    RMAN-07517: Reason: The file header is corrupted
    RMAN> list backup;
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    512 245.35M DISK 00:00:39 12-DEC-12
    BP Key: 512 Status: AVAILABLE Compressed: NO Tag: TAG20121212T160059
    Piece Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012
    _12_12\O1_MF_ANNNN_TAG20121212T160059_8DJQ7OF3_.BKP
    List of Archived Logs in backup set 512
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 1440 487654314 09-DEC-12 487695982 10-DEC-12
    1 1441 487695982 10-DEC-12 487719639 10-DEC-12
    1 1442 487719639 10-DEC-12 487741536 10-DEC-12
    1 1443 487741536 10-DEC-12 487741634 10-DEC-12
    1 1444 487741634 10-DEC-12 487771824 10-DEC-12
    1 1445 487771824 10-DEC-12 487803737 12-DEC-12
    1 1446 487803737 12-DEC-12 487810247 12-DEC-12
    1 1447 487810247 12-DEC-12 487819910 12-DEC-12
    1 1448 487819910 12-DEC-12 487837944 12-DEC-12
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    513 Full 1.94G DISK 00:03:18 12-DEC-12
    BP Key: 513 Status: AVAILABLE Compressed: NO Tag: TAG20121212T160150
    Piece Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012
    _12_12\O1_MF_NNNDF_TAG20121212T160150_8DJQ92L5_.BKP
    List of Datafiles in backup set 513
    File LV Type Ckp SCN Ckp Time Name
    1 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01.D
    BF
    2 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSAUX01.D
    BF
    3 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\UNDOTBS01.
    DBF
    4 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\USERS01.DB
    F
    5 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\EXAMPLE01.
    DBF
    6 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_SMILE.
    DBF
    7 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_GENERA
    L.DBF
    8 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_EMR.DB
    F
    9 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_DIAGNO
    STICS.DBF
    10 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_PHARMA
    CY.DBF
    11 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_PATIEN
    T.DBF
    12 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_ACCOUN
    T.DBF
    13 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_INVENT
    ORY.DBF
    14 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_HR.DBF
    15 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_DUMMY.
    DBF
    16 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_AUDIT.
    DBF
    17 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_FACILI
    TIES.DBF
    19 Full 487837993 12-DEC-12 D:\APP\ADMINISTRATOR\ORADATA\ORCL\HMS_COMMON
    .DBF
    BS Key Size Device Type Elapsed Time Completion Time
    514 222.00K DISK 00:00:06 12-DEC-12
    BP Key: 514 Status: AVAILABLE Compressed: NO Tag: TAG20121212T160520
    Piece Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2012
    _12_12\O1_MF_ANNNN_TAG20121212T160520_8DJQHGS1_.BKP
    List of Archived Logs in backup set 514
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 1449 487837944 12-DEC-12 487838190 12-DEC-12
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    515 Full 12.17M DISK 00:00:00 12-DEC-12
    BP Key: 515 Status: AVAILABLE Compressed: NO Tag: TAG20121212T160530
    Piece Name: D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\AUTOBACKUP\201
    2_12_12\O1_MF_S_801849930_8DJQHTTW_.BKP
    SPFILE Included: Modification time: 12-DEC-12
    SPFILE db_unique_name: ORCL
    Control File Included: Ckp SCN: 487838210 Ckp time: 12-DEC-12
    RMAN> run {Set until sequence 1450;
    2> Restore database;
    3> Recover database;
    4> }
    executing command: SET until clause
    Starting restore at 29-MAR-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\SYSTEM01.DBF
    channel ORA_DISK_1: restoring datafile 00002 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\SYSAUX01.DBF
    channel ORA_DISK_1: restoring datafile 00003 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\UNDOTBS01.DBF
    channel ORA_DISK_1: restoring datafile 00004 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\USERS01.DBF
    channel ORA_DISK_1: restoring datafile 00005 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\EXAMPLE01.DBF
    channel ORA_DISK_1: restoring datafile 00006 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_SMILE.DBF
    channel ORA_DISK_1: restoring datafile 00007 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_GENERAL.DBF
    channel ORA_DISK_1: restoring datafile 00008 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_EMR.DBF
    channel ORA_DISK_1: restoring datafile 00009 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_DIAGNOSTICS.DBF
    channel ORA_DISK_1: restoring datafile 00010 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_PHARMACY.DBF
    channel ORA_DISK_1: restoring datafile 00011 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_PATIENT.DBF
    channel ORA_DISK_1: restoring datafile 00012 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_ACCOUNT.DBF
    channel ORA_DISK_1: restoring datafile 00013 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_INVENTORY.DBF
    channel ORA_DISK_1: restoring datafile 00014 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_HR.DBF
    channel ORA_DISK_1: restoring datafile 00015 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_DUMMY.DBF
    channel ORA_DISK_1: restoring datafile 00016 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_AUDIT.DBF
    channel ORA_DISK_1: restoring datafile 00017 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_FACILITIES.DBF
    channel ORA_DISK_1: restoring datafile 00019 to D:\APP\ADMINISTRATOR\ORADATA\ORC
    L\HMS_COMMON.DBF
    channel ORA_DISK_1: reading from backup piece D:\APP\ADMINISTRATOR\FLASH_RECOVER
    Y_AREA\ORCL\BACKUPSET\2012_12_12\O1_MF_NNNDF_TAG20121212T160150_8DJQ92L5_.BKP
    channel ORA_DISK_1: piece handle=D:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\B
    ACKUPSET\2012_12_12\O1_MF_NNNDF_TAG20121212T160150_8DJQ92L5_.BKP tag=TAG20121212
    T160150
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:05:15
    Finished restore at 29-MAR-13
    Starting recover at 29-MAR-13
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 03/29/2013 23:03:53
    ORA-19698: D:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO01.LOG is from different databa
    se: id=1339157974, db_name=ORCL
    RMAN> alter database open resetlogs;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 03/29/2013 23:07:08
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: 'D:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01.DBF'

    Hi,
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 03/29/2013 23:03:53
    ORA-19698: D:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO01.LOG is from different databa
    se: id=1339157974, db_name=ORCL
    RMAN> alter database open resetlogs;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 03/29/2013 23:07:08
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: 'D:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01.DBF'Restore finished successfully. But Recover is not.
    Can you delete or move D:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO01.LOG - redolog files to othere directory.
    And recover again. Because this redo log files is belonging to other database.
    Regards
    Mahir M. Quluzade

  • ORA-01503 and ORA-01110 Errors while running adcfgclone.pl dbTier

    Hi,
    I am working on R12 on IBM AIX as I am cloning from one system to another I am facing some errors while running adcfgclone.pl for database tier.
    Following is the log from the adcfgclone.pl as it fails;
    Creating the control file for CLONE_test database ...
    SQL*Plus: Release 11.1.0.7.0 - Production on Mon Sep 6 10:32:43 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to an idle instance.
    ORACLE instance shut down.
    Connected to an idle instance.
    ORA-32006: USER_DUMP_DEST initialization parameter has been deprecated
    ORA-32006: BACKGROUND_DUMP_DEST initialization parameter has been deprecated
    ORACLE instance started.
    Total System Global Area 1068937216 bytes
    Fixed Size                  2160600 bytes
    Variable Size             427821096 bytes
    Database Buffers          624951296 bytes
    Redo Buffers               14004224 bytes
    CREATE CONTROLFILE REUSE SET DATABASE "CLONE"
    *+
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01159: file is not from same database as previous files - wrong database id
    ORA-01110: data file 22: '/u04/oracle/proddata/applsysx01.dbf'
    alter database open resetlogs
    *+
    ERROR at line 1:
    ORA-01507: database not mounted
    alter tablespace TEMP add tempfile '/u03/oracle/proddata/temp01.dbf' REUSE
    *+
    ERROR at line 1:
    ORA-01109: database not open
    ALTER DATABASE RENAME GLOBAL_NAME TO "CLONE.testcom.com"
    *+
    ERROR at line 1:
    ORA-01109: database not open
    ORA-01507: database not mounted
    ORACLE instance shut down.
    Connected to an idle instance.
    ORA-32006: USER_DUMP_DEST initialization parameter has been deprecated
    ORA-32006: BACKGROUND_DUMP_DEST initialization parameter has been deprecated
    ORACLE instance started.
    Total System Global Area 1068937216 bytes
    Fixed Size                  2160600 bytes
    Variable Size             427821096 bytes
    Database Buffers          624951296 bytes
    Redo Buffers               14004224 bytes
    ORA-03113: end-of-file on communication channel
    Process ID: 1278120
    Session ID: 1105 Serial number: 3
    ERROR:
    ORA-03114: not connected to ORACLE
    ORA-24324: service handle not initialized
    ORA-01041: internal error. hostdef extension doesn't exist
    Connected.
    ORA-01031: insufficient privileges
    ERROR:
    ORA-01012: not logged on
    ERROR:
    ORA-01012: not logged on
    ERROR:
    ORA-01012: not logged on
    ERROR:
    ORA-01012: not logged on
    ERROR:
    ORA-01012: not logged on
    ERROR:
    ORA-01012: not logged on
    Disconnected
    exit_code=1
    Checking for errors ...
    The database has not been successfully created. Shutting down the instance ...
    SQL*Plus: Release 11.1.0.7.0 - Production on Mon Sep 6 10:33:12 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to an idle instance.
    ORACLE instance shut down.
    Disconnected
    +.end std out.+
    +.end err out.+
    I have checked the log for preclone from the source machine but there are no errors. Below are the last lines of preclone log file
    Zip2 - Completed native zipping sh -c "cd /u02/oracle/proddb/10.2.0/appsutil/out/PROD_testcom/; zip  -q  -y /u02/oracle/proddb/10.2.0/appsutil/clone/data/stage/adcrdb.zip -@ ; echo ERRORCODE = $? ERRORCODE_END"
    Done...
    +#############################################################+
    StageDBTier Finished at Tue Aug 31 16:50:19 GMT03:00 2010+
    Status: Completed Successfully
    +#############################################################+
    Please advice.
    Regards

    Hi user:
    1. Yes the database and lsnr were closed as the tar files were created. So, i assume thate there are no any oracle session avalibale when you copy files from source to target
    2. Yes I would also like to mention that it already had an old instance. So this is just a new clone. So, i mention you have valid entery on /etc/hosts file
    3. Please can you describe what permissions as from root user it was done as
    chown -R oratest:dba <db tier folders> If your target user is oratest than syntax seems correct, did you copy oracle_home too from source to target and this home owner is oratest again right?
    Regard
    Helios

  • ORA 01180 and ORA 01110 during restore

    Hi there
    Env: Oracle 10g R2 EE on ASM (10.2.0.5.0) - non-RAC, RHEL 5.8 64bit
    RMAN backup location: /ora_backup
    I have a database on PROD server. I took full RMAN backup of this database and it is stored in "/ora_backup".
    I have a new DEV server which has this "/ora_backup" mounted on it. DEV has same Oracle version/patches, directory structure, etc.
    I have to create the database with same name as in PROD on the DEV server.
    I create the ASM instance with required diskgroups (same names and size as in PROD) and creating same directories on the filesystem for the database. I copied the pfile from PROD to the DEV server and started the database in NOMOUNT mode. I issued following commands to initiate the restore.
    $ RMAN target /
    RMAN> restore controlfile from '/ora_backup/CA411/autobackup/2013_11_28/o1_mf_s_832702400_99hmjjhr_.bkp';
    Starting restore at 28-NOV-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=320 devtype=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:11
    output filename=+DATA/ca411/controlfile/current.257.832712891
    output filename=+RECOVERY/ca411/controlfile/current.260.832712891
    Finished restore at 28-NOV-13
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> restore database;
    Starting restore at 28-NOV-13
    Starting implicit crosscheck backup at 28-NOV-13
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=320 devtype=DISK
    Crosschecked 172 objects
    Finished implicit crosscheck backup at 28-NOV-13
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /ora_backup/CA411/autobackup/2013_11_28/o1_mf_s_832702400_99hmjjhr_.bkp
    File Name: /ora_backup/CA411/autobackup/2013_11_13/o1_mf_n_831408851_988495gc_.bkp
    using channel ORA_DISK_1
    creating datafile fno=1 name=+DATA/ca411/datafile/system.284.822662475
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/28/2013 21:08:41
    ORA-01180: can not create datafile 1
    ORA-01110: data file 1: '+DATA/ca411/datafile/system.284.822662475'
    RMAN> list incarnation;
    List of Database Incarnations
    DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
    1       1       CA411    3492870531       PARENT  1          05-AUG-13
    2       2       CA411    3492870531       CURRENT 13405519   13-NOV-13
    RMAN> list backup summary;
    List of Backups
    ===============
    Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
    785     B  F  A DISK        28-NOV-13       1       1       YES        TAG20131128T175829
    786     B  F  A DISK        28-NOV-13       1       1       YES        TAG20131128T175829
    787     B  F  A DISK        28-NOV-13       1       1       YES        TAG20131128T175829
    788     B  F  A DISK        28-NOV-13       1       1       YES        TAG20131128T175829
    789     B  F  A DISK        28-NOV-13       2       1       YES        TAG20131128T175829
    790     B  F  A DISK        28-NOV-13       1       1       NO         TAG20131128T181244
    791     B  A  A DISK        28-NOV-13       1       1       NO         TAG20131128T181308
    792     B  A  A DISK        28-NOV-13       1       1       NO         TAG20131128T181308
    793     B  A  A DISK        28-NOV-13       1       1       NO         TAG20131128T181308
    794     B  F  A DISK        28-NOV-13       1       1       NO         TAG20131128T181320
    795     B  F  A DISK        13-NOV-13       1       1       NO         TAG20131113T185411
    RMAN>
    ========================
    SQL> select db.DBID,NAME,db.CREATED,db.CONTROLFILE_TIME, db.VERSION_TIME,dbinc.RESETLOGS_TIME, dbinc.PRIOR_RESETLOGS_TIME
    from v$database db, v$database_incarnation dbinc where dbinc.INCARNATION# = db.LAST_OPEN_INCARNATION#;
          DBID NAME      CREATED   CONTROLFI VERSION_T RESETLOGS PRIOR_RES
    3492870531 CA411     05-AUG-13 28-NOV-13 28-NOV-13 05-AUG-13
    SQL>
    =========================================
    drwxrwxr-x   7 oracle  oinstall   420 Nov 15 06:20 ora_backup
    I used this exact same method to restore the database on TEST server with no issues. I am not sure what is the problem?
    Since I was able to restore the database on TEST server, this is definitely not due to the bug mentioned in MOS.
    I have read some posts on the forum including these MOS docs (727655.1, 1265151.1, 392237.1) but none fits my situation or solves the problem.
    Any clues?
    Best regards

    yes this is the error but I don't know the cause because I followed exact same steps to restore the DB to TEST server.
    ASM does have free space.
    ASMCMD> lsdg
    State    Type    Rebal Unbal  Sector  Block AU  Total_MB  Free_MB Req_mir_free_MB Usable_file_MB  Offline_disks  Name
    MOUNTED  EXTERN  N N         512   4096 1048576   1705984  1705853                0         1705853              0 DATA/
    MOUNTED  EXTERN  N N         512   4096 1048576    602112   601939                0          601939              0 RECOVERY/
    Best regards

  • Errors-Ora-01157,ORA-01110,ORA-01033

    HI all,
    i am unable to login into database,i will explain clearly what has happened,please help me out...my /home directory was 100%,so i was unable to login,what i have did is i have not deleted
    archive files but i have moved to other directory /ora_bkp,then i was able to login,today i have rebboted the system and later i have started database,started listener,but when i try to login
    through sql*plus or toad i am getting this error.....ORA-01033 (ORACLE INITIALIZATION OR SHUTDOWN IN PROGRESS),and when i have tried to check from sql promt ....i am getting this
    error....ORA-01157(CANNOT IDENTIFY/LOCK DATAFILE 6 -SEE DBWR TRACE FILE),& ORA-01110(DATA FILE 6: '/SAPDATA/SPO'...
    HOW SHOULD I RECTIFY MY PROBLEM...AS I AM VERY NEW IAM TRYING TO EXPLAIN CLEARLY ...PLEASE HELP ME IN SOLVING THIS ISSUE....I HAVE EVEN TRIED ALTER DATABASE OPEN...I AM GETTING ERRORS OF ORA-01157,ORA-01110....WHAT IS MY PROBLEM HOW SHOULD I RECTIFY IT..PLEASE SORT THIS....
    THANKS,
    MIKE

    Well, did you check f.i. your alert.log and other dumps?
    They will be on your server in the bdump, udump, cdump directories:
    Where to Find Files for Analyzing Errors
    Oracle records information about important events that occur in your Oracle RAC environment in trace files. The trace files for Oracle RAC are the same as those in single-instance Oracle databases. As a best practice, monitor and back up trace files regularly for all instances to preserve their content for future troubleshooting.
    Information about ORA-600 errors appear in the alert_SID.log file for each instance where SID is the instance identifier. For troubleshooting, you may need to also provide files from the following bdump locations:
    * $ORACLE_HOME/admin/db_name/bdump on UNIX-based systems
    * %ORACLE_HOME%\admin\db_name\bdump on Windows-based systems
    Some files may also be in the udump directory.
    In addition, the directory cdmp_timestamp contains in-memory traces of Oracle RAC instance failure information. This directory is located in ORACLE_HOME/admin/db_name/bdump/cdmp_timestamp, where timestamp is the time at which the error occurred.
    Trace dump files are stored under the cdmp directory. Oracle creates these files for each process that is connected to the instance. The naming convention for the trace dump files is same as for trace files, but with .trw as the file extension.
    (http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/appsupport.htm#RACAD512)

  • ORA-01180 and ORA-01110 error when restoring database by RMAN in 11.1.0.6.0

    I have a new installed database running in ARCIHVELOG mode on SUSE 10SP3. Catalog is not used. When I try to restore the database from a level 0 backup based on SCN, ORA-01180 and ORA-01110 were raised out today. Please help me through this. Thx. The senario follows:
    1. I got the current SCN by "select dbms_flashback.get_system_change_number from dual". Say it's 12345;
    2. I did a level 0 hot backup with current control file, archived logs and parameter files. Everything went well;
    3. Some other DMLs are applied to the database;
    4. I want to do a SCN-based incomplete recovery for this database to SCN 12345. Then I
    1) shutdown immediate;
    2) startup nomount;
    3) restore the control file from backupset;
    5) startup mount;
    6) catalog start with "[backupset path]";
    7) restore database until scn 12345.
    Just at step 4.7, ORA-01180 and ORA-01110 were raised out, saying cannot create data file 1. Note: Backup files are existing and file permissions are all OK.
    Then I issues "list incarnation of database". There is just one record with incarnation id 1.
    So I queried v$log_history, found serveral record there. The most recent one has NEXT_SCN later than 12345, say 12400. Then I tried to restore database until this SCN. It WORKED! The restore and recovery succeeded.
    My questions are:
    1. Why cannot I restore the database to a previous SCN, say 12345, but 12400 is OK?.
    2. If the database was RESETLOG prior to my recovery, should I reset database to the incarnation where I took my backup? What can I do if there is no that incarnation information in my control file?
    Waiting for your suggestion.

    Hi guys. There is one update.
    This issue is caused by the incorrect SCN vs. backup set. I got this SCN before the backup started. According to Oracle docs, it's not allowed for an SCN based recovery.
    Now, I changed the sequence of my operations, so that SCN is got once backup is done, which is exact the "most recent sequence# and least SCN" mentioned by some thread in this forum. It works now.
    Anyone could explain why the SCN got prior to the level 0 backup is not recognized by restore/recovery phase? Thanks.

  • Recovery process applies old archivelogs on standby database

    Right now my standby database is in sync with my primary database and is waiting for the archived log sequeuence# 8378 to arrive.
    But when I stop the recovery process (alter database recover managed standby database cancel;) and re-start it (alter database recover managed standby database disconnect), it starts all over again and starts applying archive logs starting from the sequence# 5739 (looks like its scanning thru the logs). To catchup with primary it takes 2+ hours as it need to skim thru all the logs starting from 5739 to 8377.
    Please let me know if you need any further information to fix this.
    Thank you
    Sunny boy
    Details:
    Database version: 11.2.0.3
    OS : RHEL 5
    On Standby Database
    SQL> SELECT THREAD#, MAX(SEQUENCE#) AS "LAST_APPLIED_LOG"
    FROM V$LOG_HISTORY
    GROUP BY THREAD#; 2 3
    THREAD# LAST_APPLIED_LOG
    1 8377
    Alert log
    alter database recover managed standby database disconnect
    Attempt to start background Managed Standby Recovery process (MNODWDR)
    Tue May 08 16:13:09 2012
    MRP0 started with pid=28, OS id=26150
    MRP0: Background Managed Standby Recovery process started (MNODWDR)
    started logmerger process
    Tue May 08 16:13:15 2012
    Managed Standby Recovery not using Real Time Apply
    Parallel Media Recovery started with 8 slaves
    Waiting for all non-current ORLs to be archived...
    All non-current ORLs have been archived.
    Completed: alter database recover managed standby database disconnect
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/arch/mnodw_1_5739_765032423.arc
    Tue May 08 16:13:48 2012
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5740.1466.781015749
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5741.1468.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5742.1474.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5743.1473.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5744.1477.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5745.1478.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5746.1472.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5747.1475.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5748.1469.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5749.1470.781017203
    Tue May 08 16:13:57 2012
    Edited by: Sunny boy on May 8, 2012 5:29 PM

    Hello;
    V$LOG_HISTORY is the information from the control file. I would use a different query to check :
    From the Primary :
    SET PAGESIZE 140
    COL DB_NAME FORMAT A10
    COL HOSTNAME FORMAT A14
    COL LOG_ARCHIVED FORMAT 999999
    COL LOG_APPLIED FORMAT 999999
    COL LOG_GAP FORMAT 9999
    COL APPLIED_TIME FORMAT A14
    SELECT
       DB_NAME, HOSTNAME, LOG_ARCHIVED, LOG_APPLIED, APPLIED_TIME, LOG_ARCHIVED-LOG_APPLIED LOG_GAP
    FROM
    ( SELECT
       NAME DB_NAME
    FROM
       V$DATABASE
    SELECT
       UPPER(SUBSTR(HOST_NAME,1,(DECODE(INSTR(HOST_NAME,'.'),0,LENGTH(HOST_NAME), (INSTR(HOST_NAME,'.')-1))))) HOSTNAME
    FROM
       V$INSTANCE
    SELECT
       MAX(SEQUENCE#) LOG_ARCHIVED
    FROM
       V$ARCHIVED_LOG
    WHERE
       DEST_ID=1
    AND
       ARCHIVED='YES'
    SELECT
       MAX(SEQUENCE#) LOG_APPLIED
    FROM
       V$ARCHIVED_LOG
    WHERE
       DEST_ID=2
    AND
       APPLIED='YES'
    SELECT
       TO_CHAR(MAX(COMPLETION_TIME),'DD-MON/HH24:MI') APPLIED_TIME
    FROM
       V$ARCHIVED_LOG
    WHERE
       DEST_ID=2
    AND
       APPLIED='YES'
    );Change DEST_ID as needed for your system. I would also bump the parameter LOG_ARCHIVE_MAX_PROCESSES assuming its set to default to a higher value up to 30.
    Maybe instead of stopping the recovery process you should DEFER on the Primary
    alter system set log_archive_dest_state_2=defer;Change the _n from 2 to what your system requires. I use this and have watch DG catch up 200 archives in about 15 minutes.
    You have Standby Redo setup and are using the same size as your redo right?
    Have never seen the Standby try to apply twice.
    ORA-600 [3020] "Stuck Recovery" [ID 30866.1] ( But I do not see your issue )
    Metalink Note 241438.1 Script to Collect Data Guard Physical Standby Diagnostic Information
    Metalink Note 241374.1 Script to Collect Data Guard Primary Site Diagnostic Information
    Best Regards
    mseberg
    Edited by: mseberg on May 8, 2012 5:16 PM

  • ORA-01110,ORA-01114,ORA-27063 error

    I am running oracle 10.2.0.1.0 on Solaris 10 OS on Sparc machine.
    My oracle server often goes shutdown when i am performing the update operation on different tables. I could not understand the reason for its shutdown. According to log file, error occurred due to media failure but disk was fine and on starting up the oracle instance, every thing became fine. Can anybody kindly, tell me the reason for its shutdown ?
    Following is the info of log file.
    Thread 1 advanced to log sequence 1414
    Current log# 3 seq# 1414 mem# 0: /datafiles/mqa/redo03.log
    Thu Apr 3 15:49:42 2008
    Errors in file /u01/app/oracle/product/10.2.0/admin/mqa/bdump/mqa_ckpt_27978.trc:
    ORA-01110: data file 160: '/OracleStorage/MQA_Data/mqa_SM_Anl3_HS_data.dbf'
    ORA-01114: IO error writing block to file 160 (block # 1)
    ORA-27063: number of bytes read/written is incorrect
    SVR4 Error: 5: I/O error
    Additional information: -1
    Additional information: 8192
    Thu Apr 3 15:50:21 2008
    Thread 1 advanced to log sequence 1415
    Current log# 1 seq# 1415 mem# 0: /datafiles/mqa/redo01.log
    Thu Apr 3 15:51:13 2008
    Thread 1 cannot allocate new log, sequence 1416
    Checkpoint not complete
    Current log# 1 seq# 1415 mem# 0: /datafiles/mqa/redo01.log
    Thread 1 advanced to log sequence 1416
    Current log# 2 seq# 1416 mem# 0: /datafiles/mqa/redo02.log
    Thu Apr 3 15:51:45 2008
    KCF: write/open error block=0xd21d1 online=1
    file=114 /OracleStorage/MQA_Data/mqa_MSCI2D_data.dbf
    error=27063 txt: 'SVR4 Error: 5: I/O error
    Additional information: -1
    Additional information: 8192'
    Thu Apr 3 15:51:45 2008
    Errors in file /u01/app/oracle/product/10.2.0/admin/mqa/bdump/mqa_dbw0_27974.trc:
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01114: IO error writing block to file 114 (block # 860625)
    ORA-01110: data file 114: '/OracleStorage/MQA_Data/mqa_MSCI2D_data.dbf'
    ORA-27063: number of bytes read/written is incorrect
    SVR4 Error: 5: I/O error
    Additional information: -1
    Additional information: 8192
    DBW0: terminating instance due to error 1242
    Termination issued to instance processes. Waiting for the processes to exit
    Instance terminated by DBW0, pid = 27974

    Hi Mozzam
    the memory manager on 10.2 sends these messages but they are said not to be fatal (i.e. shutting down your database) unless you get a 4031. Read the metalink doc 330239.1 about that. Have you tried to size your sga properly? Is your db still crashing after you switched async io off?
    Best regards
    Matti
    Message was edited by:
    matti

  • Cancel or restart recovery process for a datafile?

    We have a data file for which recovery seems to have been started but cannot finish. Any suggestions on how to cancel or restart the recovery of a datafile?
    We are getting the following errors:
    SQL> alter database recover datafile 4;
    ORA-00275: media recover has already been started
    SQL > alter database datafile 4 offline;
    Database altered
    SQL > alter database open;
    ERROR at line 1:
    ORA-01156: recovery in progress may need access to files
    SQL> alter database datafile 4 online;
    ORA-01113: file 4 needs media recovery
    ORA-01110: data file 4: ‘D:\ORACLE\PRODUCT\10.1.0\ORADATA\TRAIN\NDX.DBF’
    SQL> alter database recover datafile 4;
    ORA-00275: media recover has already been started
    This is a noarchivelog 10g database.

    Recovering a dbf in noarch mode?

  • ORA-01110: data file 1024:

    Hi ,
    Hi,
    While doing patch post installtion, that is running catbundle sql scripts I got the below error.
    Patch : 12419331 ( DATABASE PSU 11.2.0.2.3 (INCLUDES CPUJUL2011) )
    Processing components and files for bundle 1: PSU 11.2.0.2.1
    Processing components and files for bundle 2: PSU 11.2.0.2.2
    Exception - patch NOT installed
    ORA-01157: cannot identify/lock data file 1024 - see DBWR trace file
    ORA-01110: data file 1024: '/u01/oradata/mydbsid/temp01.dbf'
    PL/SQL procedure successfully completed.
    Checked on server and found a different path for temp tablespace .
    it is '/v01/oradata/mydbsid/temp01.dbf' . I mean FS is different .
    Could you please let me know where to change the file path .
    Thanks ,
    Mahesh

    on executing below I am seeing this .
    is dropping and recreating the solution . Why it is picking up the wrong path ?
    SYS@igodevrp AS SYSDBA>select * from dba_temp_files
    ERROR at line 1:
    ORA-01157: cannot identify/lock data file 1024 - see DBWR trace file
    ORA-01110: data file 1024: '/u01/oradata/mydbsid/temp01.dbf'
    Edited by: 871048 on Sep 8, 2011 5:36 AM
    Edited by: 871048 on Sep 8, 2011 5:37 AM

  • Ora-01110 ora- 01113   ora-00376

    Hi,
    Database Verion:10.2.0
    OS: windows Server 2003.
    I am facing a typical error ora-01110 01113 ora-00376.
    I did google and many many docs say tha I need a simple recovery for the datafile.
    Unfortunately, when I do recovery it is searching for archive logs and that arch logs are deleted manually.
    To overcome this I did a crosscheck, still i face the same issue.
    Thanks and regards,

    What happened to that datafile?
    Is it a production database?
    Do you have RMAN backups? If not, then WHY?
    Withouth having archived redo log files or incremental backup, you can't recover the datafile. Make it offline and drop it
    Kamran Agayev A.
    Oracle ACE
    My Oracle Video Tutorials - http://kamranagayev.wordpress.com/oracle-video-tutorials/

  • ORA-01110: ORA-01207: on sysaux01.dbf file

    Hi,
    I have a an Oracle 11.2 database running on SuSE Linux, and I did a cold linux backup of the database (shutdown database, and tar all file system to tape). Now I have restored all the files on a new server, and when I try to start the database, it brings the below error.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 1603411968 bytes
    Fixed Size 2213776 bytes
    Variable Size 872417392 bytes
    Database Buffers 721420288 bytes
    Redo Buffers 7360512 bytes
    Database mounted.
    SQL>
    SQL> alter database open
    2 /
    alter database open
    ERROR at line 1:
    ORA-01122: database file 2 failed verification check
    ORA-01110: data file 2: '/data1/oradata/prod01/sysaux01.dbf'
    ORA-01207: file is more recent than control file - old control file
    When I do the restore, all the files have the same datestamp. But After the alter open database command, control01.dbf and system01.dbf files changed their timestamp to today.
    Help.
    Kevin

    Oracle Error :: ORA-01207
    file is more recent than control file - old control file
    Cause
    The control file change sequence number in the data file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.
    Action
    Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery.

  • Ora 01547 ora 01195 ora 01110

    Hi,
    while clonning(hot) the database i have got the above errors
    i have given the command sql>alter database begin backup;
    and coppied the all the dbf to paticular location.
    and created contolfile trace, created pfile
    and after that
    exported the database export ORACLE_SID=clone
    sql>startup nomount
    sql>@contol.ctl--created contol file
    nd given
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01195: online backup of file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/u01/ijmj/clone/system.dbf'
    nd after that recreated contol file and given the cmd
    SQL> RECOVER DATABASE using backup controlfile until cancel;
    auto
    got the error ora01547warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ora01195 online backup of file 1 needs more recovery to be consistent
    ora 0110 data file 1: '/u01/ijmj/clone/system.db

    Hi,
    Well, i assume that you still can perform recovery of your cloned database.
    So, do perform the log switch, and copy all new (not copied yet) archive log files to target db.
    Then issue the recover command and submit all remaining archive log, then 'cancel', and open with reset logs.
    Otherwise, if you still have all archive logs since your previous hot backup, you could take a new hot backup of the problematic tablespace (with finishing with a log switch), and recover your database.
    HTH,
    Thierry

Maybe you are looking for

  • Using USB 6009 on Ubuntu 12.04

    So I've read many forums on this and it seems to be a common issue, which no one has figured out (from what I've read so far). I need to have the USB 6009 working on Ubuntu 12.04 for some field experiments and I don't have alternatives / options. I d

  • Preview for Developers Windows 8.1

    Hi guys i want to know the size of Windows 8.1 developer preview...? can i install through mobile data...?

  • Package permissions problem with Snow Leopard

    Under Leopard, changing permissions at the Get Info window for a package file also changes the package contents to the same permission settings. This no longer works in Snow Leopard. For example, I have tried adding another user name with read & writ

  • To change Font size and style in a cell

    HI! . I would to know if it is possible to change to the source and the text of alv. I have seen that with class CL_SALV_WD_UIE_TEXT_VIEW and method SET_DESIGN, Font size and style in a cell can be changed, but i don´t know how do it and what objects

  • My App Store won't open on my new iPad

    My App Store opened once and then the next day it just shows a blank screen.  What happened?