ORA-00283

Hello
I am using Oracle XE on Linux. I want to create a backup server in case my production server is down the backup server has the most recent backup available.
To do this I taken a Cold backup of the Production DB and copied the files at the same location at my Backup server. Backup DB started fine.
From onwards I don't want to down my Production server and therefore I taken the backup of production controlfile by using
   ALTER DATABASE BACKUP CONTROLFILE ........Then I copied all the archivelogs from production to the Backup server. On the backup server I connected SQL Plus and wrote:
SQL> startup mount;
ORACLE instance started.
Total System Global Area  536870912 bytes
Fixed Size                  1259932 bytes
Variable Size             427820644 bytes
Database Buffers          104857600 bytes
Redo Buffers                2932736 bytes
Database mounted.                       
SQL> recover database using backup controlfile;
ORA-00279: change 27442002 generated at 03/23/2009 10:05:52 needed for thread 1
ORA-00289: suggestion :                                                       
/home/omer/flash_recovery_area/XE/archivelog/2009_03_24/o1_mf_1_3167_%u_.arc  
ORA-00280: change 27442002 for thread 1 is in sequence #3167                  
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43565 change 3028861204237 time 03/23/2009
10:05:52
ORA-00334: archived log:
'/home/oracle/flash_recovery_area/XE/archivelog/2009_03_22/o1_mf_1_3167_4wf77s3d_.
arc'
ORA-01112: media recovery not started Kindly help me in doing this.
Habib

H a b i b wrote:
SQL> recover database using backup controlfile;
ORA-00279: change 27442002 generated at 03/23/2009 10:05:52 needed for thread 1
ORA-00289: suggestion :
/home/omer/flash_recovery_area/XE/archivelog/2009_03_24/o1_mf_1_3167_%u_.arc
ORA-00280: change 27442002 for thread 1 is in sequence #3167
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00283: recovery session canceled due to errors
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block 43565 change 3028861204237 time 03/23/2009
10:05:52
ORA-00334: archived log:
'/home/oracle/flash_recovery_area/XE/archivelog/2009_03_22/o1_mf_1_3167_4wf77s3d_.
arc'You have corrupted archive log. Maybe during copying not all file copied. Copy once more this particular file from production server and try again to recover.

Similar Messages

  • ORA-00283:,ORA-19909:,ORA-19909:

    Hi,
    I am doing recovery with hot backup (whiout using RMAN) in my stand by database dupdb but getting below error.
    SQL> select name, open_mode from v$database;
    NAME      OPEN_MODE
    DUPDB     MOUNTED
    SQL> set logsource 'D:\app1\Archivelocation';
    SQL> recover database using backup controlfile until cancel;
    ORA-00283: recovery session canceled due to errors
    ORA-19909: datafile 1 belongs to an orphan incarnation
    ORA-01110: data file 1: 'D:\APP1\APP\HIMANSHU\ORADATA\DUPDB\SYSTEM01.DBF'
    Please let me know What wrong I am doing here.
    Thanks,
    Michel

    HI, welcome to OTN form,
    fb767351-a660-4b18-9a9f-73bc141f6a0c wrote:
    Hi,
    I am doing recovery with hot backup (whiout using RMAN) in my stand by database dupdb but getting below error.
    SQL> select name, open_mode from v$database;
    NAME      OPEN_MODE
    DUPDB     MOUNTED
    SQL> set logsource 'D:\app1\Archivelocation';
    SQL> recover database using backup controlfile until cancel;
    ORA-00283: recovery session canceled due to errors
    ORA-19909: datafile 1 belongs to an orphan incarnation
    ORA-01110: data file 1: 'D:\APP1\APP\HIMANSHU\ORADATA\DUPDB\SYSTEM01.DBF'
    From Metalink: (Oracle Support)
    From Metaclick
    Error:     ORA-19909 (ORA-19909)
    Text:     datafile %s belongs to an orphan incarnation
    Cause:     Either the specified datafile was restored from a backup that was
         taken during a period of time that has already been discarded by a
         resetlogs operation, or Oracle cannot identify which database
         incarnation the file belongs to. The alert log contains more
         information.
    Action:     Restore a backup of this file that belongs to either the current
         or a prior incarnation of the database. If you are using RMAN to
         restore, RMAN will automatically select a correct backup.
    Thank you

  • ORA-00283: recovery session canceled due to errors

    Dear All,
    I have standby database in which STANDBY_FILE_MANAGEMENT was MANUAL. I have shrink undo table-space in primary database. After 2 days I tried to recover standby database. I got following error.
    ORA-00283: recovery session canceled due to errors
    ORA-01274: cannot add data file '/home/app/oracle/oradata/OMNDB/undotbs01.dbf'
    - file could not be created
    I am unable to shrink undo table-space in standby database as I did in primary database as it is not open.
    please anyone help me to get clarify this issue.
    In Standby_
    SQL> select name from v$datafile;
    NAME
    /home/app/oracle/oradata/OMNDB/system01.dbf
    /home/app/oracle/oradata/OMNDB/undotbs01.dbf
    /home/app/oracle/oradata/OMNDB/sysaux01.dbf
    /home/app/oracle/oradata/OMNDB/MY_oms_ts01.dbf
    /home/app/oracle/oradata/OMNDB/nologging_ts01.dbf

    Thank you CKPT for reply.
    this is the output when MRP
    SQL> recover standby database;
    ORA-00283: recovery session canceled due to errors
    ORA-01111: name for data file 2 is unknown - rename to correct file
    ORA-01110: data file 2: '/home/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00002'
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01111: name for data file 2 is unknown - rename to correct file
    ORA-01110: data file 2: '/home/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00002'
    this is in the alert log
    ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...
    Tue Jan 29 09:17:53 2013
    db_recovery_file_dest_size of 10240 MB is 0.00% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Tue Jan 29 10:29:57 2013
    ALTER DATABASE RECOVER standby database
    Tue Jan 29 10:29:57 2013
    Media Recovery Start
    Managed Standby Recovery not using Real Time Apply
    Tue Jan 29 10:29:57 2013
    Media Recovery failed with error 1111
    ORA-283 signalled during: ALTER DATABASE RECOVER standby database ...

  • ORA-00283: recovery session canceled due to errors. Help me.

    Something appears to be wrong with my control file backup. Upon
    moving the backed up files to my "test" machine, I place them in the
    data directory, and rename my control file backup to the correct name
    and run this procedure:
    - I start the instance
    - I mount the database
    - I issue a recover database
    I then receive the following error:
    ORA-00283: recovery session canceled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    Does anyone have any thoughts around this?

    Hi,
    Have you taken backup of control file?
    (alter database backup controlfile to trace)
    Does the path of datafiles on test machine is same as that of production machine from where you have copied files?
    Steps:
    1> startup nomount
    2> copy create controlfile command from tracefile
    If paths are different change them.
    3> recover database until cancel using backup controlfile
    It will ask archive logs path, specify path.
    Press cancel after you have applied all archivelogs.
    4> alter database open resetlogs
    5> add tempfile in database.

  • Ora -00283 & ora-01610

    Hello
    i got the following errors on creation of database. after the command alter database open resetlogs i got the above error
    i checked the status of datafile and it shows as recover.
    so after mounting the database i ran the command recover datafile 'location of datafile' , but it gave me error ora-06101 saying : recovery using the backup controlfile option must be done
    i went thr some of the forums on metalink on this error.
    i ran the command
    SQL> recover database until cancel using backup controlfile;
    following was the O/P
    ORA-00279: change 475702716 generated at 09/07/2004 19:04:58 needed for thread
    ORA-00289: suggestion : E:\ARCH_DEV\ARC01162.001
    ORA-00280: change 475702716 for thread 1 is in sequence #1162
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log 'E:\ARCH_DEV\ARC01162.001'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    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: 'E:\ORACLE\ORA92\DEV\SYSITCH.DB1'
    could anyone tell me how to proceed thr next step
    thanks
    Kedar

    Well, the error is it can't find the archive log - is the path and file name correct?
    DO you still have your archive logs? If you have ran out of archivelogs, then you can look into your REDO logs and see which one contains the SCN (system change number) that is being asked for and enter that as the log for recovery. (using the same process you used above)
    good luck

  • 恢复报错ORA-01139

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

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

  • Ora-00600: internal error on 11g database in windows 2007 environment

    Hello , i have these problems please help me to solve it.
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    C:\Windows\system32>emctl status dbconsole
    Environment variable ORACLE_SID not defined. Please define it.
    C:\Windows\system32>set ORACLE_SID=testsid
    C:\Windows\system32>emctl status dbconsole
    Oracle Enterprise Manager 11g Database Control Release 11.1.0.6.0
    Copyright (c) 1996, 2007 Oracle Corporation.  All rights reserved.
    https://local:1158/em/console/aboutApplication
    Oracle Enterprise Manager 11g is not running.
    Logs are generated in directory C:\app\23333941\product\11.1.0\db_3/local_testsid/sysman/log
    C:\Windows\system32>sqlplus sys/@**** as sysdba
    SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 09:27:37 2013
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    SQL*Plus: Release 11.1.0.6.0 - Production
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    Use SQL*Plus to execute SQL, PL/SQL and SQL*Plus statements.
    Usage 1: sqlplus -H | -V
        -H             Displays the SQL*Plus version and the
                       usage help.
        -V             Displays the SQL*Plus version.
    Usage 2: sqlplus [ [<option>] [<logon>] [<start>] ]
      <option> is: [-C <version>] [-L] [-M "<options>"] [-R <level>] [-S]
        -C <version>   Sets the compatibility of affected commands to the
                       version specified by <version>.  The version has
                       the form "x.y[.z]".  For example, -C 10.2.0
        -F             Enables the failover mode for a RAC environment.
        -L             Attempts to log on just once, instead of
                       reprompting on error.
        -M "<options>" Sets automatic HTML markup of output.  The options
                       have the form:
                       HTML [ON|OFF] [HEAD text] [BODY text] [TABLE text]
                       [ENTMAP {ON|OFF}] [SPOOL {ON|OFF}] [PRE[FORMAT] {ON|OFF}]
        -R <level>     Sets restricted mode to disable SQL*Plus commands
                       that interact with the file system.  The level can
                       be 1, 2 or 3.  The most restrictive is -R 3 which
                       disables all user commands interacting with the
                       file system.
        -S             Sets silent mode which suppresses the display of
                       the SQL*Plus banner, prompts, and echoing of
                       commands.
      <logon> is: (<username>[/<password>][@<connect_identifier>] | /)
                  [AS SYSDBA | AS SYSOPER | AS SYSASM] | /NOLOG | [EDITION=value]
        Specifies the database account username, password and connect
        identifier for the database connection.  Without a connect
        identifier, SQL*Plus connects to the default database.
        The AS SYSDBA, AS SYSOPER and AS SYSASM  options are database
        administration privileges.
        <connect_identifier> can be in the form of Net Service Name
        or Easy Connect.
          @[<net_service_name> | [//]Host[:Port]/<service_name>]
            <net_service_name> is a simple name for a service that resolves
            to a connect descriptor.
            Example: Connect to database using Net Service Name and the
                     database net service name is ORCL.
               sqlplus myusername/mypassword@ORCL
            Host specifies the host name or IP address of the database
            server computer.
            Port specifies the listening port on the database server.
            <service_name> specifies the service name of the database you
            want to access.
            Example: Connect to database using Easy Connect and the
                     Service name is ORCL.
               sqlplus myusername/mypassword@Host/ORCL
        The /NOLOG option starts SQL*Plus without connecting to a
        database.
        The EDITION specifies the value for Application
        Edition
      <start> is: @<URL>|<filename>[.<ext>] [<parameter> ...]
        Runs the specified SQL*Plus script from a web server (URL) or the
        local file system (filename.ext) with specified parameters that
        will be assigned to substitution variables in the script.
    When SQL*Plus starts, and after CONNECT commands, the site profile
    (e.g. $ORACLE_HOME/sqlplus/admin/glogin.sql) and the user profile
    (e.g. login.sql in the working directory) are run.  The files may
    contain SQL*Plus commands.
    Refer to the SQL*Plus User's Guide and Reference for more information.
    C:\Windows\system32>sqlplus sys/1118@testsid as sysdba
    SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 09:29:03 2013
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    ERROR:
    ORA-12154: TNS:could not resolve the connect identifier specified
    Enter user-name: sysdba
    Enter password:
    ERROR:
    ORA-01033: ORACLE initialization or shutdown in progress
    Process ID: 0
    Session ID: 0 Serial number: 0
    Enter user-name: sys
    Enter password:
    ERROR:
    ORA-01033: ORACLE initialization or shutdown in progress
    Process ID: 0
    Session ID: 0 Serial number: 0
    SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
    C:\Windows\system32>sqlplus/nolog
    SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 09:32:59 2013
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    SQL> connect/as sysdba
    Connected.
    SQL> create table test(id number, id1 number);
    create table test(id number, id1 number)
    ERROR at line 1:
    ORA-01109: database not open
    SQL> select status from v$instance;
    STATUS
    MOUNTED
    SQL> alter database open;
    ERROR at line 1:
    ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0x51434A54],
    [2], [], [], [], [], []
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    C:\Windows\system32>startup mount
    'startup' is not recognized as an internal or external command,
    operable program or batch file.
    C:\Windows\system32>sqlplus/nolog
    SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 10:05:42 2013
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    SQL> connect/as sysdba
    Connected.
    SQL> startup mount;
    ORA-01081: cannot start already-running ORACLE - shut it down first
    SQL> recover database;
    Media recovery complete.
    SQL> select GROUP#,SEQUENCE#,ARCHIVED,STATUS from v$log order by SEQUENCE#;
        GROUP#  SEQUENCE# ARC STATUS
             2        539 NO  INACTIVE
             3        540 NO  ACTIVE
             1        541 NO  CURRENT
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-00264: no recovery required
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    C:\Windows\system32>sqlplus/nolog
    SQL*Plus: Release 11.1.0.6.0 - Production on Fri Jul 5 10:17:10 2013
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    SQL> connect / as sysdba
    Connected.
    SQL> startup mount
    ORA-01081: cannot start already-running ORACLE - shut it down first
    SQL> shutdown immediate;
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup;
    ORACLE instance started.
    Total System Global Area  313860096 bytes
    Fixed Size                  1332892 bytes
    Variable Size             276826468 bytes
    Database Buffers           29360128 bytes
    Redo Buffers                6340608 bytes
    Database mounted.
    Database opened.
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-01124: cannot recover data file 1 - file is in use or recovery
    ORA-01110: data file 1:
    'C:\APP\23333941\ORADATA\TEST\DATAFILE\O1_MF_SYSTEM_8XB8TY3S_.DBF'
    SQL> select GROUP#,SEQUENCE#,ARCHIVED,STATUS from v$log order by SEQUENCE#;
        GROUP#  SEQUENCE# ARC STATUS
             3        540 NO  INACTIVE
             1        541 NO  INACTIVE
             2        542 NO  CURRENT
    SQL> restore database;
    SP2-0734: unknown command beginning "restore da..." - rest of line ignored.
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-01124: cannot recover data file 1 - file is in use or recovery
    ORA-01110: data file 1:
    'C:\APP\23333941\ORADATA\TEST\DATAFILE\O1_MF_SYSTEM_8XB8TY3S_.DBF'
    SQL>
    Thanks with regards Ganaa;

    What happened prior that resulted in the disaster scenario that you posted/
    When was the last time the DB opened with out error?
    What changed since then?

  • "ORA-01203 - wrong creation SCN" got during copy of a db on another machine

    Hello colleagues,
    I copy a database from a machine to a second one through this procedure:
    I set each tablespace (data and temp) in backup mode
    I copy the datafiles (data and temp)
    I copy the control file
    I copy archived redo logs
    On the second machine I try to startup the database by the command
    On the second machine I try to startup the database but the following errors are got:
    SQL> @/usr/Systems/1359HA_9.0.0_Master/HA_EOMS_1_9.0.0_Master/tmp/oracle/CACH
    E/apply_redo.sql;
    ORACLE instance started.
    Total System Global Area 423624704 bytes
    Fixed Size 2044552 bytes
    Variable Size 209718648 bytes
    Database Buffers 209715200 bytes
    Redo Buffers 2146304 bytes
    Database mounted.
    alter database recover automatic from '/usr/Systems/1359HA_9.0.0_Master/HA_EOMS_1_9.0.0_Master/data/warm_rep
    l/WarmArchive/CACHE' database until cancel using backup controlfile
    but the following errors are got:
    SQL> @/usr/Systems/1359HA_9.0.0_Master/HA_EOMS_1_9.0.0_Master/tmp/oracle/CACH
    E/apply_redo.sql;
    ORACLE instance started.
    Total System Global Area 423624704 bytes
    Fixed Size 2044552 bytes
    Variable Size 209718648 bytes
    Database Buffers 209715200 bytes
    Redo Buffers 2146304 bytes
    Database mounted.
    alter database recover automatic from '/usr/Systems/1359HA_9.0.0_Master/HA_EOMS_1_9.0.0_Master/data/warm_rep
    l/WarmArchive/CACHE' database until cancel using backup controlfile
    ERROR at line 1:
    ORA-00283: recovery session canceled due to errors
    ORA-01110: data file 1: '/cache/db/db01/system_1.dbf'
    ORA-01122: database file 1 failed verification check
    ORA-01110: data file 1: '/cache/db/db01/system_1.dbf'
    ORA-01203: wrong incarnation of this file - wrong creation SCN
    You see the mount command and the error got.
    What can I do to troubleshoot the problem?
    thanks for the support
    Enrico
    The complete copy procedure is the following:
    #!/bin/ksh
    # Step 2 -- Verifying the DBMS ARCHIVELOG mode
    $ORACLE_HOME/bin/sqlplus /nolog << EOF
    connect / as sysdba
    spool ${ORACLE_TMP_DIR}/archive.log
    archive log list;
    spool off
    EOF
    grep NOARCHIVELOG ${ORACLE_TMP_DIR}/archive.log >/dev/null 2>&1
    # Step 3 -- Creating DB_filenames.conf / DB_controfile.conf fles
    [ -f ${ORACLE_TMP_DIR}/DB_filenames.conf ] && rm -f ${ORACLE_TMP_DIR}/DB_filenames.conf
    [ -f ${ORACLE_TMP_DIR}/DB_controfile.conf ] && rm -f ${ORACLE_TMP_DIR}/DB_controfile.conf
    [ -f ${ORACLE_TMP_DIR}/DB_TEMP_filenames.conf ] && rm -f ${ORACLE_TMP_DIR}/DB_TEMP_filenames.conf
    $ORACLE_HOME/bin/sqlplus /nolog << EOF
    connect / as sysdba
    set linesize 600;
    spool ${ORACLE_TMP_DIR}/DB_filenames.conf
    select 'TABLESPACE=',tablespace_name from sys.dba_data_files;
    select 'FILENAME=',file_name from sys.dba_data_files;
    select 'LOGFILE=',MEMBER from v\$logfile;
    spool off
    EOF
    $ORACLE_HOME/bin/sqlplus /nolog << EOF
    connect / as sysdba
    set linesize 600;
    spool ${ORACLE_TMP_DIR}/DB_controfile.conf
    select name from v\$controlfile;
    spool off
    EOF
    $ORACLE_HOME/bin/sqlplus /nolog << EOF
    connect / as sysdba
    set linesize 600;
    spool ${ORACLE_TMP_DIR}/DB_TEMP_filenames.conf
    select 'TABLESPACE=',tablespace_name from sys.dba_temp_files;
    select 'FILENAME=',file_name from sys.dba_temp_files;
    spool off
    EOF
    note "Executing cp ${ORACLE_TMP_DIR}/DB_filenames.conf ${INSTANCE_DATA_DIR}/DB_filenames.conf ..."
    cp ${ORACLE_TMP_DIR}/DB_filenames.conf ${INSTANCE_DATA_DIR}/DB_filenames.conf
    [ $? -ne 0 ] && error "Error executing cp ${ORACLE_TMP_DIR}/DB_filenames.conf ${INSTANCE_DATA_DIR}/DB_filenames.conf!"\
         && LocalExit 1
    chmod ug+x ${INSTANCE_DATA_DIR}/DB_filenames.conf
    note "Executing cp ${ORACLE_TMP_DIR}/DB_controfile.conf ${INSTANCE_DATA_DIR}/DB_controfile.conf ..."
    cp ${ORACLE_TMP_DIR}/DB_controfile.conf ${INSTANCE_DATA_DIR}/DB_controfile.conf
    [ $? -ne 0 ] && error "Error executing cp ${ORACLE_TMP_DIR}/DB_controfile.conf ${INSTANCE_DATA_DIR}/DB_controfile.conf!"\
         && LocalExit 1
    chmod ug+x ${INSTANCE_DATA_DIR}/DB_controfile.conf
    note "Executing cp ${ORACLE_TMP_DIR}/DB_TEMP_filenames.conf ${INSTANCE_DATA_DIR}/DB_TEMP_filenames.conf ..."
    cp ${ORACLE_TMP_DIR}/DB_TEMP_filenames.conf ${INSTANCE_DATA_DIR}/DB_TEMP_filenames.conf
    [ $? -ne 0 ] && error "Error executing cp ${ORACLE_TMP_DIR}/DB_TEMP_filenames.conf ${INSTANCE_DATA_DIR}/DB_TEMP_filenames.conf!"\
         && LocalExit 1
    chmod ug+x ${INSTANCE_DATA_DIR}/DB_TEMP_filenames.conf
    set -a
    set -A arr_tablespace `grep "^TABLESPACE=" ${INSTANCE_DATA_DIR}/DB_filenames.conf | awk '{ print \$2 }'`
    index=`grep "^TABLESPACE" ${INSTANCE_DATA_DIR}/DB_filenames.conf | wc -l`
    backup_status=0
    i=0
    while [ $i -lt $index ]
    do
    note "tablespace=${arr_tablespace[$i]}"
    $ORACLE_HOME/bin/sqlplus /nolog << EOF
    connect / as sysdba
    set linesize 600;
    spool ${ORACLE_TMP_DIR}/tablespace.log
    select 'FILENAME=',file_name from sys.dba_data_files where tablespace_name='${arr_tablespace[$i]}';
    spool off
    alter tablespace ${arr_tablespace[$i]} end backup;
    spool ${ORACLE_TMP_DIR}/backup_tablespace.log
    alter tablespace ${arr_tablespace[$i]} begin backup;
    spool off
    EOF
    set -A arr_filename `grep "^FILENAME=" ${ORACLE_TMP_DIR}/tablespace.log | awk '{ print \$2 }'`
    index1=`grep "^FILENAME" ${ORACLE_TMP_DIR}/tablespace.log | wc -l`
    h=0
    while [ $h -lt $index1 ]
    do
    name=`basename ${arr_filename[$h]}`
    note "filename = ${arr_filename[$h]}"
    $ORACLE_HOME/bin/sqlplus /nolog << EOF
    connect / as sysdba
    host compress -c ${arr_filename[$h]} > ${BACKUP_AREA}/$name.Z
    EOF
    h=`expr $h + 1`
    done
    $ORACLE_HOME/bin/sqlplus /nolog << EOF
    connect / as sysdba
    spool ${ORACLE_TMP_DIR}/backup_tablespace.log
    alter tablespace ${arr_tablespace[$i]} end backup;
    spool off
    EOF
    i=`expr $i + 1`
    done
    [ $backup_status -eq 1 ] && LocalExit 1
    set -a
    set -A arr_tablespace `grep "^TABLESPACE=" ${INSTANCE_DATA_DIR}/DB_TEMP_filenames.conf | awk '{ print \$2 }'`
    index=`grep "^TABLESPACE" ${INSTANCE_DATA_DIR}/DB_TEMP_filenames.conf | wc -l`
    ${ORACLE_TMP_DIR}/tablespace.logi=0
    while [ $i -lt $index ]
    do
    note "tablespace=${arr_tablespace[$i]}"
    $ORACLE_HOME/bin/sqlplus /nolog << EOF
    connect / as sysdba
    set linesize 600;
    spool ${ORACLE_TMP_DIR}/tablespace.log
    select 'FILENAME=',file_name from sys.dba_temp_files where tablespace_name='${arr_tablespace[$i]}';
    spool off
    EOF
    set -A arr_filename `grep "^FILENAME=" ${ORACLE_TMP_DIR}/tablespace.log | awk '{ print \$2 }'`
    index1=`grep "^FILENAME" ${ORACLE_TMP_DIR}/tablespace.log | wc -l`
    h=0
    while [ $h -lt $index1 ]
    do
    name=`basename ${arr_filename[$h]}`
    note "filename = ${arr_filename[$h]}"
    $ORACLE_HOME/bin/sqlplus /nolog << EOF
    connect / as sysdba
    host compress -c ${arr_filename[$h]} > ${BACKUP_AREA}/$name.Z
    EOF
    h=`expr $h + 1`
    done
    i=`expr $i + 1`
    done
    # "log switch & controlfile backup"
    $ORACLE_HOME/bin/sqlplus /nolog << EOF
    connect / as sysdba
    spool ${ORACLE_TMP_DIR}/backup_controlfile.log
    alter database backup controlfile to '${BACKUP_AREA}/ctrl_pm.ctl' reuse;
    host chmod a+rw ${BACKUP_AREA}/ctrl_pm.ctl
    alter system archive log current;
    spool off
    spool ${ORACLE_TMP_DIR}/archive_info.log
    archive log list;
    spool off
    EOF
    # Step 5 -- Copying the DBMS on the companion node
    note "transferring archived redo log files from ACT to SBY host"
    name=`grep 'Archive destination' ${ORACLE_TMP_DIR}/archive_info.log| awk '{ print \$3 }'`
    set -A vett_logfiles `grep "^LOGFILE=" ${INSTANCE_DATA_DIR}/DB_filenames.conf | awk '{ print \$2 }'`
    index=`grep "^LOGFILE" ${INSTANCE_DATA_DIR}/DB_filenames.conf | wc -l`
    i=0
    while [ $index -gt 0 ]
    do
    name=`basename ${vett_logfiles[$i]}`
    ###MOD001
    $ORACLE_HOME/bin/sqlplus /nolog << EOF
    connect / as sysdba
    host cp ${vett_logfiles[$i]} ${BACKUP_AREA}/$name
    host chmod a+rw ${BACKUP_AREA}/$name
    EOF
    if [ $? -ne 0 ]; then
    error "Error copying logfile on LOCAL_BACKUP_AREA"
    LocalExit 1
    fi
    note "log_file=${vett_logfiles[$i]}"
    index=`expr $index - 1`
    i=`expr $i + 1`
    done
    note "Executing RemoteCopy ${COMPANION_HOSTNAME} ${INSTANCE_DATA_DIR}/DB_filenames.conf ${INSTANCE_DATA_DIR}/DB_filenames.conf 0 -k -ret 2 ..."
    RemoteCopy ${COMPANION_HOSTNAME} ${INSTANCE_DATA_DIR}/DB_filenames.conf ${INSTANCE_DATA_DIR}/DB_filenames.conf 0 -k -ret 2
    if [ $? -ne 0 ]; then
    error "Error executing RemoteCopy ${COMPANION_HOSTNAME} ${INSTANCE_DATA_DIR}/DB_filenames.conf ${INSTANCE_DATA_DIR}/DB_filenames.conf 0 -ret 2!"
    LocalExit 1
    fi
    note "Executing RemoteCopy ${COMPANION_HOSTNAME} ${INSTANCE_DATA_DIR}/DB_TEMP_filenames.conf ${INSTANCE_DATA_DIR}/DB_TEMP_filenames.conf 0 -k -ret 2 ..."
    RemoteCopy ${COMPANION_HOSTNAME} ${INSTANCE_DATA_DIR}/DB_TEMP_filenames.conf ${INSTANCE_DATA_DIR}/DB_TEMP_filenames.conf 0 -k -ret 2
    if [ $? -ne 0 ]; then
    error "Error executing RemoteCopy ${COMPANION_HOSTNAME} ${INSTANCE_DATA_DIR}/DB_TEMP_filenames.conf ${INSTANCE_DATA_DIR}/DB_TEMP_filenames.conf 0 -ret 2!"
    LocalExit 1
    fi
    note "Executing RemoteCopy ${COMPANION_HOSTNAME} ${INSTANCE_DATA_DIR}/DB_controfile.conf ${INSTANCE_DATA_DIR}/DB_controfile.conf 0 -k -ret 2 ..."
    RemoteCopy ${COMPANION_HOSTNAME} ${INSTANCE_DATA_DIR}/DB_controfile.conf ${INSTANCE_DATA_DIR}/DB_controfile.conf 0 -k -ret 2
    if [ $? -ne 0 ]; then
    error "Error executing RemoteCopy ${COMPANION_HOSTNAME} ${INSTANCE_DATA_DIR}/DB_controfile.conf ${INSTANCE_DATA_DIR}/DB_controfile.conf 0 -k -ret 2!"
    LocalExit 1
    fi
    note "Executing RemoteCopy ${COMPANION_HOSTNAME} ${BACKUP_AREA} ${RECOVER_AREA} 0 -k -ret 2 ..."
    RemoteCopy ${COMPANION_HOSTNAME} ${BACKUP_AREA} ${RECOVER_AREA} 0 -k -ret 2

    If the Operating system is same :
    Working Machine
    ================
    Shutdown the database and copy everything
    Copy the init.ora
    Copy the pdf,ctl,and log
    Copy the bdump, udump etc..
    On the second machine
    ==================
    Copy your file in the same path as original i.e
    C:\oracle..<dbname>\system.dbf
    C:\oracle..<dbname>\system.dbf
    Start the database
    If your paths in second machine does not match as original update this thread again
    Michael
    http://mikegeorgiou.blogspot.com

  • ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type

    OS Version : AIX 6.1
    DB Version : 11.2.0.1
    I am duplicating database and got below error:
    contents of Memory Script:
       Alter clone database open resetlogs;
    executing Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    RMAN-10041: Could not re-create polling channel context following failure.
    RMAN-10024: error setting up for rpc polling
    RMAN-10005: error opening cursor
    RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
    RMAN-03002: failure of Duplicate Db command at 02/16/2013 17:20:02
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
    Process ID: 44040326
    Session ID: 65 Serial number: 3
    Error is because in target database undo tablespace is UNDOTBS_NEW and in auxiliary database undo tablespace name in init file is UNDOTBS. I followed the meatlink doc 433992.1 which suggest following steps to recover from above error:
    1) edit the parameter UNDO_MANAGEMENT to "MANUAL"
    2) start database again
    3) drop the UNDO tablespace
    4) recreate UNDO tablespace which matches to name in init file.
    5) shutdown & start DB again.
    Now, i edited init file and tried to start DB and got following error:
    oracore@cph-core-db01-s $ sqlplus /nolog
    SQL*Plus: Release 11.2.0.1.0 Production on Sat Feb 16 17:22:11 2013
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    SQL> conn sys as sysdba
    Enter password:
    Connected to an idle instance.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 4275781632 bytes
    Fixed Size                  2213632 bytes
    Variable Size             822085888 bytes
    Database Buffers         3439329280 bytes
    Redo Buffers               12152832 bytes
    Database mounted.
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/u04/oradata/CORE/CORE_DUP/system01.dbf'I don't want to run duplicate command with correct UNDO tablespace name. Any other work around for this ?

    STARTUP MOUNT
    RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
    CANCEL
    ALTER DATABASE OPEN RESETLOGS
    Above option is not working for CORE_DUP, i am getting very strange error, while trying to recover i am getting very strange error as below:
    oracore@cph-core-db01-s $ export ORACLE_SID=CORE_DUP
    SQL*Plus: Release 11.2.0.1.0 Production on Mon Feb 18 11:17:25 2013
    Copyright (c) 1982, 2009, Oracle.  All rights reserved.
    SQL> conn sys as sysdba
    Enter password:
    Connected to an idle instance.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 4275781632 bytes
    Fixed Size                  2213632 bytes
    Variable Size             822085888 bytes
    Database Buffers         3439329280 bytes
    Redo Buffers               12152832 bytes
    Database mounted.
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    SQL> recover database using backup controlfile until cancel;
    ORA-00283: recovery session canceled due to errors
    ORA-16433: The database must be opened in read/write mode.Primary database initfile:
    event="10298 trace name context forever, level 32"
    db_block_size=8192
    db_file_multiblock_read_count=16
    open_cursors=300
    db_name=CORE
    cursor_sharing='SIMILAR'
    global_names=FALSE
    diagnostic_dest=/u01/app/oracore/diag/CORE
    #background_dump_dest=/u01/app/oracore/diag/rdbms/bdump
    #core_dump_dest=/u01/app/oracore/diag/rdbms/cdump
    #user_dump_dest=/u01/app/oracore/diag/rdbms/udump
    control_files=("/u01/oradata/CORE/control01.ctl", "/u02/oradata/CORE/control02.ctl", "/u03/oradata/CORE/control03.ctl")
    log_archive_dest_1='LOCATION=/u05/oradata/CORE/'
    log_archive_format='CORE_%s%t%r.ARC'
    job_queue_processes=10
    compatible=11.2.0.1
    processes=150
    fast_start_mttr_target=300
    filesystemio_options='SETALL'
    pga_aggregate_target=500M
    recyclebin='OFF'
    remote_login_passwordfile='EXCLUSIVE'
    session_cached_cursors=100
    sga_target=4G
    undo_management='AUTO'
    undo_tablespace='UNDOTBS_NEW'
    nls_date_format='DD-MON-RRRR'
    nls_length_semantics='CHAR'initfile for CORE_DUP
    event="10298 trace name context forever, level 32"
    db_block_size=8192
    db_file_multiblock_read_count=16
    open_cursors=300
    db_name=CORE_DUP
    cursor_sharing='SIMILAR'
    global_names=FALSE
    diagnostic_dest=/u01/app/oracore/diag/CORE/CORE_DUP
    control_files=("/u01/oradata/CORE/CORE_DUP/control01.ctl", "/u02/oradata/CORE/CORE_DUP/control02.ctl", "/u03/oradata/CORE/CORE_DUP/control03.ctl")
    log_archive_dest_1='LOCATION=/u05/oradata/CORE/CORE_DUP/'
    log_archive_format='CORE_DUP%s%t%r.ARC'
    job_queue_processes=10
    compatible=11.2.0.1
    _compression_compatibility="11.2.0"
    processes=150
    fast_start_mttr_target=300
    filesystemio_options='SETALL'
    pga_aggregate_target=500M
    recyclebin='OFF'
    remote_login_passwordfile='EXCLUSIVE'
    session_cached_cursors=100
    sga_target=4G
    undo_management='AUTO'
    undo_tablespace='UNDOTBS'
    nls_date_format='DD-MON-RRRR'
    nls_length_semantics='CHAR'
    log_file_name_convert='/CORE','/CORE/CORE_DUP'
    db_file_name_convert='/CORE','/CORE/CORE_DUP'Duplicate steps are as:
    oracore@cph-core-db01-s $ rman target sys/zzzz@core catalog rmantst10/zzzzz@catdb auxiliary /
    Recovery Manager: Release 11.2.0.1.0 - Production on Mon Feb 18 15:50:00 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: CORE (DBID=913972022)
    connected to recovery catalog database
    connected to auxiliary database: CORE_DUP (not mounted)
    RMAN> duplicate target database to CORE_DUP;
    Starting Duplicate Db at 18-FEB-13
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=96 device type=DISK
    allocated channel: ORA_AUX_DISK_2
    channel ORA_AUX_DISK_2: SID=127 device type=DISK
    contents of Memory Script:
       sql clone "create spfile from memory";
    executing Memory Script
    sql statement: create spfile from memory
    contents of Memory Script:
       shutdown clone immediate;
       startup clone nomount;
    executing Memory Script
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area    4275781632 bytes
    Fixed Size                     2213632 bytes
    Variable Size                838863104 bytes
    Database Buffers            3422552064 bytes
    Redo Buffers                  12152832 bytes
    contents of Memory Script:
       sql clone "alter system set  db_name =
    ''CORE'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
       sql clone "alter system set  db_unique_name =
    ''CORE_DUP'' comment=
    ''Modified by RMAN duplicate'' scope=spfile";
       shutdown clone immediate;
       startup clone force nomount
       restore clone primary controlfile;
       alter clone database mount;
    executing Memory Script
    sql statement: alter system set  db_name =  ''CORE'' comment= ''Modified by RMAN duplicate'' scope=spfile
    sql statement: alter system set  db_unique_name =  ''CORE_DUP'' comment= ''Modified by RMAN duplicate'' scope=spfile
    Oracle instance shut down
    Oracle instance started
    Total System Global Area    4275781632 bytes
    Fixed Size                     2213632 bytes
    Variable Size                838863104 bytes
    Database Buffers            3422552064 bytes
    Redo Buffers                  12152832 bytes
    Starting restore at 18-FEB-13
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=96 device type=DISK
    allocated channel: ORA_AUX_DISK_2
    channel ORA_AUX_DISK_2: SID=127 device type=DISK
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1
    channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5fo246k3_175_1 tag=LEVEL1
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
    output file name=/u01/oradata/CORE/CORE_DUP/control01.ctl
    output file name=/u02/oradata/CORE/CORE_DUP/control02.ctl
    output file name=/u03/oradata/CORE/CORE_DUP/control03.ctl
    Finished restore at 18-FEB-13
    database mounted
    contents of Memory Script:
       set until scn  1217601;
       set newname for datafile  1 to
    "/u04/oradata/CORE/CORE_DUP/system01.dbf";
       set newname for datafile  2 to
    "/u04/oradata/CORE/CORE_DUP/sysaux01.dbf";
       set newname for datafile  4 to
    "/u04/oradata/CORE/CORE_DUP/users01.dbf";
       set newname for datafile  5 to
    "/u04/oradata/CORE/CORE_DUP/users02.dbf";
       set newname for datafile  6 to
    "/u04/oradata/CORE/CORE_DUP/users03.dbf";
       set newname for datafile  9 to
    "/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
       restore
       clone database
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 18-FEB-13
    using channel ORA_AUX_DISK_1
    using channel ORA_AUX_DISK_2
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_1: restoring datafile 00004 to /u04/oradata/CORE/CORE_DUP/users01.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00005 to /u04/oradata/CORE/CORE_DUP/users02.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00006 to /u04/oradata/CORE/CORE_DUP/users03.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1
    channel ORA_AUX_DISK_2: starting datafile backup set restore
    channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_2: restoring datafile 00001 to /u04/oradata/CORE/CORE_DUP/system01.dbf
    channel ORA_AUX_DISK_2: restoring datafile 00002 to /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
    channel ORA_AUX_DISK_2: restoring datafile 00009 to /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
    channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1
    channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_56o246fe_166_1 tag=LEVEL0
    channel ORA_AUX_DISK_2: restored backup piece 1
    channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:01:15
    channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L0_CORE_16022013_55o246fe_165_1 tag=LEVEL0
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:35
    Finished restore at 18-FEB-13
    contents of Memory Script:
       switch clone datafile all;
    executing Memory Script
    datafile 1 switched to datafile copy
    input datafile copy RECID=24 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/system01.dbf
    datafile 2 switched to datafile copy
    input datafile copy RECID=25 STAMP=807724355 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy RECID=26 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy RECID=27 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
    datafile 6 switched to datafile copy
    input datafile copy RECID=28 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
    datafile 9 switched to datafile copy
    input datafile copy RECID=29 STAMP=807724356 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
    contents of Memory Script:
       set until scn  1217601;
       recover
       clone database
        delete archivelog
    executing Memory Script
    executing command: SET until clause
    Starting recover at 18-FEB-13
    using channel ORA_AUX_DISK_1
    using channel ORA_AUX_DISK_2
    channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00001: /u04/oradata/CORE/CORE_DUP/system01.dbf
    destination for restore of datafile 00002: /u04/oradata/CORE/CORE_DUP/sysaux01.dbf
    destination for restore of datafile 00009: /u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1
    channel ORA_AUX_DISK_2: starting incremental datafile backup set restore
    channel ORA_AUX_DISK_2: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00004: /u04/oradata/CORE/CORE_DUP/users01.dbf
    destination for restore of datafile 00005: /u04/oradata/CORE/CORE_DUP/users02.dbf
    destination for restore of datafile 00006: /u04/oradata/CORE/CORE_DUP/users03.dbf
    channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1
    channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5eo246k2_174_1 tag=LEVEL1
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/DF_L1_CORE_16022013_5do246k2_173_1 tag=LEVEL1
    channel ORA_AUX_DISK_2: restored backup piece 1
    channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:01
    starting media recovery
    archived log for thread 1 with sequence 1718 is already on disk as file /u05/oradata/CORE/CORE_17181807276264.ARC
    archived log for thread 1 with sequence 1719 is already on disk as file /u05/oradata/CORE/CORE_17191807276264.ARC
    archived log for thread 1 with sequence 1720 is already on disk as file /u05/oradata/CORE/CORE_17201807276264.ARC
    archived log for thread 1 with sequence 1721 is already on disk as file /u05/oradata/CORE/CORE_17211807276264.ARC
    archived log for thread 1 with sequence 1722 is already on disk as file /u05/oradata/CORE/CORE_17221807276264.ARC
    archived log for thread 1 with sequence 1723 is already on disk as file /u05/oradata/CORE/CORE_17231807276264.ARC
    archived log for thread 1 with sequence 1724 is already on disk as file /u05/oradata/CORE/CORE_17241807276264.ARC
    archived log for thread 1 with sequence 1725 is already on disk as file /u05/oradata/CORE/CORE_17251807276264.ARC
    archived log for thread 1 with sequence 1726 is already on disk as file /u05/oradata/CORE/CORE_17261807276264.ARC
    archived log for thread 1 with sequence 1727 is already on disk as file /u05/oradata/CORE/CORE_17271807276264.ARC
    archived log for thread 1 with sequence 1728 is already on disk as file /u05/oradata/CORE/CORE_17281807276264.ARC
    archived log for thread 1 with sequence 1729 is already on disk as file /u05/oradata/CORE/CORE_17291807276264.ARC
    archived log for thread 1 with sequence 1730 is already on disk as file /u05/oradata/CORE/CORE_17301807276264.ARC
    archived log for thread 1 with sequence 1731 is already on disk as file /u05/oradata/CORE/CORE_17311807276264.ARC
    archived log for thread 1 with sequence 1732 is already on disk as file /u05/oradata/CORE/CORE_17321807276264.ARC
    archived log for thread 1 with sequence 1733 is already on disk as file /u05/oradata/CORE/CORE_17331807276264.ARC
    archived log for thread 1 with sequence 1734 is already on disk as file /u05/oradata/CORE/CORE_17341807276264.ARC
    archived log for thread 1 with sequence 1735 is already on disk as file /u05/oradata/CORE/CORE_17351807276264.ARC
    archived log for thread 1 with sequence 1736 is already on disk as file /u05/oradata/CORE/CORE_17361807276264.ARC
    archived log for thread 1 with sequence 1737 is already on disk as file /u05/oradata/CORE/CORE_17371807276264.ARC
    archived log for thread 1 with sequence 1738 is already on disk as file /u05/oradata/CORE/CORE_17381807276264.ARC
    archived log for thread 1 with sequence 1739 is already on disk as file /u05/oradata/CORE/CORE_17391807276264.ARC
    archived log for thread 1 with sequence 1740 is already on disk as file /u05/oradata/CORE/CORE_17401807276264.ARC
    archived log for thread 1 with sequence 1741 is already on disk as file /u05/oradata/CORE/CORE_17411807276264.ARC
    archived log for thread 1 with sequence 1742 is already on disk as file /u05/oradata/CORE/CORE_17421807276264.ARC
    archived log for thread 1 with sequence 1743 is already on disk as file /u05/oradata/CORE/CORE_17431807276264.ARC
    archived log for thread 1 with sequence 1744 is already on disk as file /u05/oradata/CORE/CORE_17441807276264.ARC
    channel ORA_AUX_DISK_1: starting archived log restore to default destination
    channel ORA_AUX_DISK_1: restoring archived log
    archived log thread=1 sequence=1710
    channel ORA_AUX_DISK_1: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1
    channel ORA_AUX_DISK_2: starting archived log restore to default destination
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1711
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1712
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1713
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1714
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1715
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1716
    channel ORA_AUX_DISK_2: restoring archived log
    archived log thread=1 sequence=1717
    channel ORA_AUX_DISK_2: reading from backup piece /oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1
    channel ORA_AUX_DISK_1: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_16022013_5jo24jp8_179_1 tag=ARC_1HR
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC thread=1 sequence=1710
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17101807276264.ARC RECID=3041 STAMP=807724360
    channel ORA_AUX_DISK_2: piece handle=/oraclebackup/CORE/ARC_1HR_CORE_18022013_5ko296uf_180_1 tag=ARC_1HR
    channel ORA_AUX_DISK_2: restored backup piece 1
    channel ORA_AUX_DISK_2: restore complete, elapsed time: 00:00:08
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC thread=1 sequence=1711
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17111807276264.ARC RECID=3042 STAMP=807724362
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC thread=1 sequence=1712
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17121807276264.ARC RECID=3043 STAMP=807724363
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC thread=1 sequence=1713
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17131807276264.ARC RECID=3044 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC thread=1 sequence=1714
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17141807276264.ARC RECID=3048 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC thread=1 sequence=1715
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17151807276264.ARC RECID=3046 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC thread=1 sequence=1716
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17161807276264.ARC RECID=3045 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC thread=1 sequence=1717
    channel clone_default: deleting archived log(s)
    archived log file name=/u05/oradata/CORE/CORE_DUP/CORE_DUP17171807276264.ARC RECID=3047 STAMP=807724367
    archived log file name=/u05/oradata/CORE/CORE_17181807276264.ARC thread=1 sequence=1718
    archived log file name=/u05/oradata/CORE/CORE_17191807276264.ARC thread=1 sequence=1719
    archived log file name=/u05/oradata/CORE/CORE_17201807276264.ARC thread=1 sequence=1720
    archived log file name=/u05/oradata/CORE/CORE_17211807276264.ARC thread=1 sequence=1721
    archived log file name=/u05/oradata/CORE/CORE_17221807276264.ARC thread=1 sequence=1722
    archived log file name=/u05/oradata/CORE/CORE_17231807276264.ARC thread=1 sequence=1723
    archived log file name=/u05/oradata/CORE/CORE_17241807276264.ARC thread=1 sequence=1724
    archived log file name=/u05/oradata/CORE/CORE_17251807276264.ARC thread=1 sequence=1725
    archived log file name=/u05/oradata/CORE/CORE_17261807276264.ARC thread=1 sequence=1726
    archived log file name=/u05/oradata/CORE/CORE_17271807276264.ARC thread=1 sequence=1727
    archived log file name=/u05/oradata/CORE/CORE_17281807276264.ARC thread=1 sequence=1728
    archived log file name=/u05/oradata/CORE/CORE_17291807276264.ARC thread=1 sequence=1729
    archived log file name=/u05/oradata/CORE/CORE_17301807276264.ARC thread=1 sequence=1730
    archived log file name=/u05/oradata/CORE/CORE_17311807276264.ARC thread=1 sequence=1731
    archived log file name=/u05/oradata/CORE/CORE_17321807276264.ARC thread=1 sequence=1732
    archived log file name=/u05/oradata/CORE/CORE_17331807276264.ARC thread=1 sequence=1733
    archived log file name=/u05/oradata/CORE/CORE_17341807276264.ARC thread=1 sequence=1734
    archived log file name=/u05/oradata/CORE/CORE_17351807276264.ARC thread=1 sequence=1735
    archived log file name=/u05/oradata/CORE/CORE_17361807276264.ARC thread=1 sequence=1736
    archived log file name=/u05/oradata/CORE/CORE_17371807276264.ARC thread=1 sequence=1737
    archived log file name=/u05/oradata/CORE/CORE_17381807276264.ARC thread=1 sequence=1738
    archived log file name=/u05/oradata/CORE/CORE_17391807276264.ARC thread=1 sequence=1739
    archived log file name=/u05/oradata/CORE/CORE_17401807276264.ARC thread=1 sequence=1740
    archived log file name=/u05/oradata/CORE/CORE_17411807276264.ARC thread=1 sequence=1741
    archived log file name=/u05/oradata/CORE/CORE_17421807276264.ARC thread=1 sequence=1742
    archived log file name=/u05/oradata/CORE/CORE_17431807276264.ARC thread=1 sequence=1743
    archived log file name=/u05/oradata/CORE/CORE_17441807276264.ARC thread=1 sequence=1744
    media recovery complete, elapsed time: 00:00:33
    Finished recover at 18-FEB-13
    contents of Memory Script:
       shutdown clone immediate;
       startup clone nomount;
       sql clone "alter system set  db_name =
    ''CORE_DUP'' comment=
    ''Reset to original value by RMAN'' scope=spfile";
       sql clone "alter system reset  db_unique_name scope=spfile";
       shutdown clone immediate;
       startup clone nomount;
    executing Memory Script
    database dismounted
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area    4275781632 bytes
    Fixed Size                     2213632 bytes
    Variable Size                838863104 bytes
    Database Buffers            3422552064 bytes
    Redo Buffers                  12152832 bytes
    sql statement: alter system set  db_name =  ''CORE_DUP'' comment= ''Reset to original value by RMAN'' scope=spfile
    sql statement: alter system reset  db_unique_name scope=spfile
    Oracle instance shut down
    connected to auxiliary database (not started)
    Oracle instance started
    Total System Global Area    4275781632 bytes
    Fixed Size                     2213632 bytes
    Variable Size                838863104 bytes
    Database Buffers            3422552064 bytes
    Redo Buffers                  12152832 bytes
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CORE_DUP" RESETLOGS ARCHIVELOG
      MAXLOGFILES     32
      MAXLOGMEMBERS      4
      MAXDATAFILES      500
      MAXINSTANCES     1
      MAXLOGHISTORY     2298
    LOGFILE
      GROUP  1 ( '/u02/oradata/CORE/CORE_DUP/redo01a.log', '/u03/oradata/CORE/CORE_DUP/redo01b.log' ) SIZE 10 M  REUSE,
      GROUP  2 ( '/u02/oradata/CORE/CORE_DUP/redo02a.log', '/u03/oradata/CORE/CORE_DUP/redo02b.log' ) SIZE 10 M  REUSE,
      GROUP  3 ( '/u02/oradata/CORE/CORE_DUP/redo03a.log', '/u03/oradata/CORE/CORE_DUP/redo03b.log' ) SIZE 10 M  REUSE
    DATAFILE
      '/u04/oradata/CORE/CORE_DUP/system01.dbf'
    CHARACTER SET AL32UTF8
    contents of Memory Script:
       set newname for tempfile  1 to
    "/u04/oradata/CORE/CORE_DUP/temp01.dbf";
       switch clone tempfile all;
       catalog clone datafilecopy  "/u04/oradata/CORE/CORE_DUP/sysaux01.dbf",
    "/u04/oradata/CORE/CORE_DUP/users01.dbf",
    "/u04/oradata/CORE/CORE_DUP/users02.dbf",
    "/u04/oradata/CORE/CORE_DUP/users03.dbf",
    "/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf";
       switch clone datafile all;
    executing Memory Script
    executing command: SET NEWNAME
    renamed tempfile 1 to /u04/oradata/CORE/CORE_DUP/temp01.dbf in control file
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf RECID=1 STAMP=807724423
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/users01.dbf RECID=2 STAMP=807724423
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/users02.dbf RECID=3 STAMP=807724423
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/users03.dbf RECID=4 STAMP=807724423
    cataloged datafile copy
    datafile copy file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf RECID=5 STAMP=807724423
    datafile 2 switched to datafile copy
    input datafile copy RECID=1 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/sysaux01.dbf
    datafile 4 switched to datafile copy
    input datafile copy RECID=2 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users01.dbf
    datafile 5 switched to datafile copy
    input datafile copy RECID=3 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users02.dbf
    datafile 6 switched to datafile copy
    input datafile copy RECID=4 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/users03.dbf
    datafile 9 switched to datafile copy
    input datafile copy RECID=5 STAMP=807724423 file name=/u04/oradata/CORE/CORE_DUP/undotbs_new01.dbf
    contents of Memory Script:
       Alter clone database open resetlogs;
    executing Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    RMAN-10041: Could not re-create polling channel context following failure.
    RMAN-10024: error setting up for rpc polling
    RMAN-10005: error opening cursor
    RMAN-10002: ORACLE error: ORA-03114: not connected to ORACLE
    RMAN-03002: failure of Duplicate Db command at 02/18/2013 15:53:50
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-30012: undo tablespace 'UNDOTBS' does not exist or of wrong type
    Process ID: 3670170
    Session ID: 33 Serial number: 7
    oracore@cph-core-db01-s $

  • ORA-01124: cannot recover data file 1 - file is in use or recovery

    I am trying to recover standby database, but it is giving the below error.
    ORA-00283: recovery session canceled due to errors
    ORA-01124: cannot recover data file 1 - file is in use or recovery, recovery is already stated
    ORA-01110: data file 1: 'I:\ORACLE\QAS\SAPDATA1\SYSTEM_1\SYSTEM.DATA1'
    when i checked in the alert log the recovery is not started. and later i hae given "alter database recover cancel' and the command end up with the below line
    "media recovery not started".
    it seems that the recovery has stuck in between.
    please advise me how to kill the recovery session that's stuck. because i dont want to bounce the standby database.
    thanks in advance.

    Without dataguard and MRP, you are running a scripted standby.
    In a scripted standby, a RECOVER DATABASE session would have an UNTIL clause (most likely UNTIL SEQUENCE). At the end of the recovery to that point (SEQUENCE#), it exits and shuts down the database.
    Also, the scripting is such that when one RECOVER session is active, another session is not allowed to start. It may loop in wait state or exit and retry at the next scheduled interval.
    Apparently your standby scripting is not robust enough to prevent another RECOVER session from starting off even as the first is active (and/or it doesn't have a proper UNTIL clause and stop, exit, shutdown actions)
    What you have is a custom implementation of a standby database. Without complete details of the script, the "locking" between sessions (to prevent a second RECOVER from starting when one is already running) etc .... we really cannot do much to help you.
    Your scripts should be maintaing status information . It should be possible for you to discover the "other" sqlplus session that has issued a RECOVER DATABASE but not yet exited (e.g. ... how about a simple "ps -ef |grep sql" and "ps -ef | grep ora" combination ??)
    Hemant K Chitale
    Edited by: Hemant K Chitale on May 29, 2013 5:47 PM

  • 11.2.0.3 dbca 建库时报ORA-704

    在安装RMS过程中,11.2.0.3的数据库DBCA时使用自带的模板克隆数据库时报:
    ORA-00704: bootstrap process failure
    ORA-39700: database must be opened with UPGRADE option
    alert 日志:
    ORACLE_BASE from environment = /u01/app/oracle
    Tue Sep 18 10:40:10 2012
    Create controlfile reuse set database "testdb"
    MAXINSTANCES 8
    MAXLOGHISTORY 1
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 1000
    Datafile
    '/u01/app/oracle/oradata/testdb/system01.dbf',
    '/u01/app/oracle/oradata/testdb/sysaux01.dbf',
    '/u01/app/oracle/oradata/testdb/undo_ts01.dbf'
    LOGFILE GROUP 1 ('/u01/app/oracle/oradata/testdb/redo1a.log', '/u01/app/oracle/oradata/testdb/redo1b.log') SIZE 102400K,
    GROUP 2 ('/u01/app/oracle/oradata/testdb/redo2a.log', '/u01/app/oracle/oradata/testdb/redo2b.log') SIZE 102400K,
    GROUP 3 ('/u01/app/oracle/oradata/testdb/redo3a.log', '/u01/app/oracle/oradata/testdb/redo3b.log') SIZE 102400K RESETLOGS
    WARNING: Default Temporary Tablespace not specified in CREATE DATABASE command
    Default Temporary Tablespace will be necessary for a locally managed database in future release
    Successful mount of redo thread 1, with mount id 2577639946
    Completed: Create controlfile reuse set database "testdb"
    MAXINSTANCES 8
    MAXLOGHISTORY 1
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 1000
    Datafile
    '/u01/app/oracle/oradata/testdb/system01.dbf',
    '/u01/app/oracle/oradata/testdb/sysaux01.dbf',
    '/u01/app/oracle/oradata/testdb/undo_ts01.dbf'
    LOGFILE GROUP 1 ('/u01/app/oracle/oradata/testdb/redo1a.log', '/u01/app/oracle/oradata/testdb/redo1b.log') SIZE 102400K,
    GROUP 2 ('/u01/app/oracle/oradata/testdb/redo2a.log', '/u01/app/oracle/oradata/testdb/redo2b.log') SIZE 102400K,
    GROUP 3 ('/u01/app/oracle/oradata/testdb/redo3a.log', '/u01/app/oracle/oradata/testdb/redo3b.log') SIZE 102400K RESETLOGS
    Stopping background process MMNL
    Stopping background process MMON
    Starting background process MMON
    Tue Sep 18 10:40:13 2012
    MMON started with pid=15, OS id=16133
    Starting background process MMNL
    ALTER SYSTEM enable restricted session;
    alter database "testdb" open resetlogs
    Tue Sep 18 10:40:13 2012
    MMNL started with pid=16, OS id=16135
    RESETLOGS after incomplete recovery UNTIL CHANGE 489306
    Errors in file /u01/app/oracle/diag/rdbms/testdb/testdb/trace/testdb_ora_16127.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Clearing online redo logfile 3 /u01/app/oracle/oradata/testdb/redo3a.log
    Clearing online log 3 of thread 1 sequence number 0
    Errors in file /u01/app/oracle/diag/rdbms/testdb/testdb/trace/testdb_ora_16127.trc:
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u01/app/oracle/diag/rdbms/testdb/testdb/trace/testdb_ora_16127.trc:
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Tue Sep 18 10:40:22 2012
    Clearing online redo logfile 3 complete
    Online log /u01/app/oracle/oradata/testdb/redo1a.log: Thread 1 Group 1 was previously cleared
    Online log /u01/app/oracle/oradata/testdb/redo1b.log: Thread 1 Group 1 was previously cleared
    Online log /u01/app/oracle/oradata/testdb/redo2a.log: Thread 1 Group 2 was previously cleared
    Online log /u01/app/oracle/oradata/testdb/redo2b.log: Thread 1 Group 2 was previously cleared
    Online log /u01/app/oracle/oradata/testdb/redo3a.log: Thread 1 Group 3 was previously cleared
    Online log /u01/app/oracle/oradata/testdb/redo3b.log: Thread 1 Group 3 was previously cleared
    Tue Sep 18 10:40:22 2012
    Setting recovery target incarnation to 2
    Tue Sep 18 10:40:23 2012
    Assigning activation ID 2577639946 (0x99a3aa0a)
    Thread 1 opened at log sequence 1
      Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/testdb/redo1a.log
      Current log# 1 seq# 1 mem# 1: /u01/app/oracle/oradata/testdb/redo1b.log
    Successful open of redo thread 1
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Tue Sep 18 10:40:23 2012
    SMON: enabling cache recovery
    Errors in file /u01/app/oracle/diag/rdbms/testdb/testdb/trace/testdb_ora_16127.trc:
    ORA-00704: bootstrap process failure
    ORA-39700: database must be opened with UPGRADE option
    Errors in file /u01/app/oracle/diag/rdbms/testdb/testdb/trace/testdb_ora_16127.trc:
    ORA-00704: bootstrap process failure
    ORA-39700: database must be opened with UPGRADE option
    Error 704 happened during db open, shutting down database
    USER (ospid: 16127): terminating the instance due to error 704
    Instance terminated by USER, pid = 16127
    ORA-1092 signalled during: alter database "testdb" open resetlogs...
    opiodr aborting process unknown ospid (16127) as a result of ORA-1092
    Tue Sep 18 10:40:26 2012
    ORA-1092 : opitsk aborting process/u01/app/oracle/diag/rdbms/testdb/testdb/trace/testdb_ora_16127.trc 的内容:
    Trace file /u01/app/oracle/diag/rdbms/testdb/testdb/trace/testdb_ora_16127.trc
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1
    System name:     Linux
    Node name:     bitest
    Release:     2.6.18-194.el5
    Version:     #1 SMP Mon Mar 29 22:10:29 EDT 2010
    Machine:     x86_64
    VM name:     VMWare Version: 6
    Instance name: testdb
    Redo thread mounted by this instance: 0 <none>
    Oracle process number: 17
    Unix process pid: 16127, image: oracle@bitest (TNS V1-V3)
    *** 2012-09-18 10:40:10.935
    *** SESSION ID:(17.1) 2012-09-18 10:40:10.935
    *** CLIENT ID:() 2012-09-18 10:40:10.935
    *** SERVICE NAME:() 2012-09-18 10:40:10.935
    *** MODULE NAME:(sqlplus@bitest (TNS V1-V3)) 2012-09-18 10:40:10.935
    *** ACTION NAME:() 2012-09-18 10:40:10.935
    Control file created with size 1064 blocks
    *** 2012-09-18 10:40:11.012
    Stopping background process MMNL
    *** 2012-09-18 10:40:12.013
    Stopping background process MMON
    *** 2012-09-18 10:40:13.084
    Prior to RESETLOGS processing...
    ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE start
    Database is not in archivelog mode
    ALTER SYSTEM ARCHIVE LOG ALL USING BACKUP CONTROLFILE complete
    DDE rules only execution for: ORA 312
    ----- START Event Driven Actions Dump ----
    ---- END Event Driven Actions Dump ----
    ----- START DDE Actions Dump -----
    Executing SYNC actions
    ----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
    Successfully dispatched
    ----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (SUCCESS, 2 csec) -----
    Executing ASYNC actions
    ----- END DDE Actions Dump (total 2 csec) -----
    DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    DDE rules only execution for: ORA 313
    ----- START Event Driven Actions Dump ----
    ---- END Event Driven Actions Dump ----
    ----- START DDE Actions Dump -----
    Executing SYNC actions
    ----- START DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
    DDE Action 'DB_STRUCTURE_INTEGRITY_CHECK' was flood controlled
    ----- END DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (FLOOD CONTROLLED, 196018181 csec) -----
    Executing ASYNC actions
    ----- END DDE Actions Dump (total 0 csec) -----
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    *** 2012-09-18 10:40:13.166 4320 krsh.c
    Clearing online redo logfile 1 /u01/app/oracle/oradata/testdb/redo1a.log
    DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/testdb/redo1a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    *** 2012-09-18 10:40:16.793
    *** 2012-09-18 10:40:16.793 4320 krsh.c
    Clearing online redo logfile 1 complete
    DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    *** 2012-09-18 10:40:16.794 4320 krsh.c
    Clearing online redo logfile 2 /u01/app/oracle/oradata/testdb/redo2a.log
    DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/testdb/redo2a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    *** 2012-09-18 10:40:20.294
    *** 2012-09-18 10:40:20.294 4320 krsh.c
    Clearing online redo logfile 2 complete
    DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    *** 2012-09-18 10:40:20.294 4320 krsh.c
    Clearing online redo logfile 3 /u01/app/oracle/oradata/testdb/redo3a.log
    DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    DDE: Problem Key 'ORA 312' was flood controlled (0x1) (no incident)
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    DDE: Problem Key 'ORA 313' was flood controlled (0x1) (no incident)
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3b.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/testdb/redo3a.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    *** 2012-09-18 10:40:22.819
    *** 2012-09-18 10:40:22.819 4320 krsh.c
    Clearing online redo logfile 3 complete
    *** 2012-09-18 10:40:22.819
    *** 2012-09-18 10:40:24.620
    ORA-00704: bootstrap process failure
    ORA-39700: database must be opened with UPGRADE option
    ORA-00704: bootstrap process failure
    ORA-39700: database must be opened with UPGRADE option
    *** 2012-09-18 10:40:24.629
    USER (ospid: 16127): terminating the instance due to error 704

    SQL> startup upgrade pfile='/u01/app/oracle/admin/testdb/scripts/init.ora';
    ORACLE instance started.
    Total System Global Area 1570009088 bytes
    Fixed Size 2228704 bytes
    Variable Size 436211232 bytes
    Database Buffers 1124073472 bytes
    Redo Buffers 7495680 bytes
    Database mounted.
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/u01/app/oracle/oradata/testdb/system01.dbf'
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-16433: The database must be opened in read/write mode.

  • ORA 600, duplicate from RAC to NON-RAC

    Hi Experts,
    I'm trying to restore Production database for development purpose point in time recovery
    environment:
    ASM: 11gR1
    DB: 10gR2
    At the end of internal duplicate steps i have faced error
    contents of Memory Script:
    Alter clone database open resetlogs;
    executing Memory Script
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 12/16/2010 05:37:06
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01152: file 3 was not restored from a sufficiently old backup
    ORA-01110: data file 3: '+DG1/dev/datafile/sysaux.534.737875511'Later i try to apply archives from production.. i have copied those and i started recovery .. i faced internal errors.
    SQL> recover database using backup controlfile;
    ORA-00283: recovery session canceled due to errors
    ORA-00600: internal error code, arguments: [kcvhvdf_1], [], [], [], [], [], [],
    [], [], [], [], []after a lot of workaround i found one doc from metalink
    *Duplicate from active database raises ORA-01194 if one thead is closed [ID 1059699.1]*
    but i checked thread status by gv$thread.. it is looking open from last month..
    any other way to find closed threads?
    so what could be the reason.
    I have no time to raise an SR now.. any ideas will be highly appriciated.
    Thanks
    Edited by: CKPT on Dec 17, 2010 11:09 PM

    I am about to use this hidden parameter (_allow_resetlogs_corruption=true
    ) due to the almost identical problem you experienced.
    What are the risks and what next to do when I open the database?There is lot of RISK
    I tried to recover manually using existing archives, But no use.
    Raised an SR. as a last option provided by support and used that parameter, But this parameter is not suggestible, Before doing such thing, better to take backup of database(mount - cold backup).
    This thread is almost 7 months old, if you have any issue create a new thread.

  • ORA-01033 Error... Please Help!

    Dear all expert,
    After Re-boot the computer, The system show the following error code; Kindly provide solution for me to fixed this case..
    Thank of all Expert.
    The Error message reference to the following:
    SQL&gt; shutdown immediate
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SQL&gt;
    SQL&gt; startup
    ORACLE instance started.
    Total System Global Area 135338868 bytes
    Fixed Size 453492 bytes
    Variable Size 109051904 bytes
    Database Buffers 25165824 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    ORA-00333: redo log read error block 90114 count 8192

    Dear Donald Spry
    I have try you suggestion to run the command in SQL Plus. But Have The following Error:
    SQL*Plus: Release 9.2.0.1.0 - Production on Mon May 12 22:53:58 2003
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Connected to:
    Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.1.0 - Production
    SQL> startup mount;
    ORA-01081: cannot start already-running ORACLE - shut it down first
    SQL> shutdown abort
    ORACLE instance shut down.
    SQL> startup mount;
    ORACLE instance started.
    Total System Global Area 135338868 bytes
    Fixed Size 453492 bytes
    Variable Size 109051904 bytes
    Database Buffers 25165824 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    SQL> alter database recover automatic;
    alter database recover automatic
    ERROR at line 1:
    ORA-00283: recovery session canceled due to errors
    ORA-00333: redo log read error block 90114 count 8192
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-00333: redo log read error block 90114 count 8192
    Please Let me know how can I do? Is it need me to re-install the Oracle 9i?
    Thousand Thanks!!
    Best Regrads
    Vincent Chan

  • Ora 01033 strange error

    hi,
    i think the database is crashed an when i try recover database
    SQL> recover database
    ORA-00283: recovery session canceled due to errors
    ORA-00333: redo log read error block 8194 count 8192
    when i try to connect it gives 01033 error.
    would anyone suggest me

    I did both your suggestions
    First of all all clients are working properly till yesterday without any problem. Today I faced this problem in all clients around 10 clients same time. I feel it is may be Host machine database /network setting problem. How we can trace?
    When I restart Listner using lsnrctl command in server , then I can connect from client using SQLplus but a while only. When I Establish another connection in the same client or from any other client, it won't allow me. Also , connected session getting error.
    When I issue lsnrctl status command in server it is displaying like this. Maxnew is the one that have problem.
    lsnrctl> status
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for 32-bit Windows: Version 8.1.7.0.0 - Produc
    tion
    Start Date 03-APR-2006 14:30:06
    Uptime 0 days 0 hr. 17 min. 53 sec
    Trace Level analysis
    Security OFF
    SNMP OFF
    Listener Parameter File D:\oracle\ora81\network\admin\listener.ora
    Listener Log File D:\oracle\ora81\network\log\listener.log
    Listener Trace File D:\ORACLE\MAXNEW.TRC
    Services Summary...
    MAXNEW has 1 service handler(s)
    maxnew has 3 service handler(s)
    MAXPRD has 1 service handler(s)
    MAXPRD has 2 service handler(s)
    MAXTEST has 1 service handler(s)
    MAXTEST has 1 service handler(s)
    PLSExtProc has 1 service handler(s)
    NBDDATA has 1 service handler(s)
    nbddata has 1 service handler(s)
    The command completed successfully
    Please advise?
    James
    Message was edited by:
    [email protected]

  • ORA-00314, ORA-00312 during restore

    Hi.
    I have (I should say I had) a database in archivelog mode.
    Arch logs multiplexed on c:, e:.
    Online redo logs multiplexed on c:, e:.
    Controlfile multiplexed on c:, e:.
    I also had a copy of spfile on e:
    I also made a backup on e:
    configure default device type to disk;
    configure retention policy to redundancy 1;
    configure channel device type disk format 'e:\backup\ora_040506_%t_s%s_s%p';
    configure controlfile autobackup on;
    configure controlfile autobackup format for device type disk to 'e:\backup\sp%F';
    configure backup optimization on;
    backup database format 'e:\backup\ora_040506_%t_s%s_s%p';
    Then I had a problem on c: (lost local datafiles, controlfiles), and wanted to restore.
    So I stopped db, copied controlfile, spfile, archive logs and redo logs from e: to c:
    I ran:
    rman nocatalog target / @restoredb.sql
    and restoredb holds:
    restore database;
    recover database;
    exit;
    In alert log I can read:
    Mon Dec 06 11:23:18 2010
    Full restore complete of datafile 2 C:\ORACLEXE\ORADATA\XE\UNDO.DBF. Elapsed time: 0:00:15
    checkpoint is 1853242
    Full restore complete of datafile 4 C:\ORACLEXE\ORADATA\XE\USERS.DBF. Elapsed time: 0:00:19
    checkpoint is 1853242
    Mon Dec 06 11:23:50 2010
    Full restore complete of datafile 1 C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF. Elapsed time: 0:00:47
    checkpoint is 1853242
    Full restore complete of datafile 3 C:\ORACLEXE\ORADATA\XE\SYSAUX.DBF. Elapsed time: 0:00:55
    checkpoint is 1853242
    Mon Dec 06 11:24:05 2010
    alter database recover datafile list clear
    Mon Dec 06 11:24:05 2010
    Completed: alter database recover datafile list clear
    Mon Dec 06 11:24:05 2010
    alter database recover datafile list
    1 , 2 , 3 , 4
    Completed: alter database recover datafile list
    1 , 2 , 3 , 4
    Mon Dec 06 11:24:05 2010
    alter database recover if needed
    start
    Media Recovery Start
    Mon Dec 06 11:24:06 2010
    Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_3860.trc:
    ORA-00314: journal 1, thread 1, numéro de séq. attendu 78 ne correspond pas à 58
    ORA-00312: journal en ligne 1 thread 1 : 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_5F60S79R_.LOG'
    Mon Dec 06 11:24:08 2010
    Media Recovery failed with error 314
    ORA-283 signalled during: alter database recover if needed
    start
    What happens?
    I can't recover a database in archivelog!

    Iam going to be more complete:
    XE on windows
    I have a laptop.
    Install XE, as default.
    HDD on c:, sd card on e:
    I have
    * put db in archivelog,
    * created online redo log groups #3,4,5, with members on c: and e:
    * dropped default online redo log groups 1 and 2
    * set up 2 controlfile multiplexing on c:, e:
    * set up 2 archive log dest (one on c: and one on e:)
    * copied spfile to e:
    * set up a backup to e: every 2 weeks.
    The laptop has worked one year then laptop crashed (hdd down), but I still have My sd card to restore datas.
    => To restore I installed a new laptop, the default XE install, stopped db, overwrite from e: -> c: :
    * the controlfile
    * the spfile
    * archivelog and redolog
    then startup mount.
    select * from v$logfile;
    => Show only groups 1 and 2 (and 1 is stale)
    select * from v$log;
    => sequences are 78,79 ( and 79 is current)
    The archive logs I have go from 77->106.
    +++++++++++++++++++++++++++++++++++++++++++++
    1st issue (or bug?): redo log groups 3,4,5 are declared in control file but not taken into account when restoring controlfile!
    I stopped new db, copied controlfile from e: (with redo logs 3,4,5 declared) to the one on c:, then restarted db.
    Can someone tell me if I can do this without "guessing" which were the redo log member names and typing ALTER DATABASE ADD LOGFILE GROUP..., then repeat (alter system switch logfile; alter database drop logfile; and drop groups 1 and 2) (and repeating this several times while group 1 or 2 still exists).
    +++++++++++++++++++++++++++++++++++++++++++++
    =>rman target /
    restore database;=>OK no error but v$logfile still shows only groups 1 and 2 (and 1 is stale)
    recover database;=>error on screen:
    dÚmarrage de la rÚcupÚration aprÞs dÚfaillance matÚrielle
    Úchec de la rÚcupÚration aprÞs dÚfaillance matÚrielle
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: Úchec de la commande recover Ó 12/23/2010 17:13:49
    ORA-00283: recovery session canceled due to errors
    RMAN-11003: erreur lors de l'analyse ou de l'exÚcution d'une instruction SQL : a
    lter database recover if needed
    start
    ORA-00283: session de rÚcupÚration annulÚe pour cause d'erreurs
    ORA-00314: journal 1, thread 1, numÚro de sÚq. attendu 78 ne correspond pas Ó 42
    ORA-00312: journal en ligne 1 thread 1 : 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_
    AREA\XE\ONLINELOG\O1_MF_1_5F60S79R_.LOG'
    Gestionnaire de rÚcupÚration (Recovery Manager) terminÚ.
    and in alert_log:
    Full restore complete of datafile 3 C:\ORACLEXE\ORADATA\XE\SYSAUX.DBF. Elapsed time: 0:00:56
    checkpoint is 1853242
    Thu Dec 23 17:13:45 2010
    alter database recover datafile list clear
    Thu Dec 23 17:13:45 2010
    Completed: alter database recover datafile list clear
    Thu Dec 23 17:13:45 2010
    alter database recover datafile list
    1 , 2 , 3 , 4
    Completed: alter database recover datafile list
    1 , 2 , 3 , 4
    Thu Dec 23 17:13:45 2010
    alter database recover if needed
    start
    Media Recovery Start
    Thu Dec 23 17:13:46 2010
    Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2080.trc:
    ORA-00314: journal 1, thread 1, numéro de séq. attendu 78 ne correspond pas à 42
    ORA-00312: journal en ligne 1 thread 1 : 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_5F60S79R_.LOG'
    Thu Dec 23 17:13:48 2010
    Media Recovery failed with error 314
    ORA-283 signalled during: alter database recover if needed
    start
    => The problem is not seq 78.
    Where does # 42 come from?
    Is it possible to dump the controlfile?
    I loiked into archive logs:
    in # 77 in beginning I have: Seq# 0000000077, SCN 0x0000001bf6b3-0x0000001c473a
    in # 78 in beginning I have: Seq# 0000000078, SCN 0x0000001c473a-0x0000001c96eb
    in # 79 in beginning I have: Seq# 0000000079, SCN 0x0000001cb0bf-0x0000001cffc4
    in # 80 in beginning I have: Seq# 0000000080, SCN 0x0000001cffc4-0x0000001d5a56
    Furthermore:
    If I look at dates; arch log 77 & 78 dates are newer than 79 and next ones. Probably they have been crashed due to question above (redo log groups)?
    Regards,
    Alain

Maybe you are looking for