精华内容
下载资源
问答
  • 数据库open时,提示需要介质恢复,恢复时就会报ORA-16433错误。 SQL> alter database open; alter database open * ERROR at line 1: ORA-01113: file 1 needs media recovery ORA-01110: data file 1: '/u01/...

    今天上午刚回到公司,接到开发组同事电话,测试数据库主机被新来的小伙非正常关机了,现在数据库起不来了。

    数据库open时,提示需要介质恢复,恢复时就会报ORA-16433错误。

    SQL> alter database open;
    alter database open
    *
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/u01/oradata/orcl/system01.dbf'
    
    
    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.
    
    
    SQL> alter database open read only;
    alter database open read only
    *
    ERROR at line 1:
    ORA-16433: The database must be opened in read/write mode.
    
    
    SQL> alter database backup controlfile to trace;
    alter database backup controlfile to trace
    *
    ERROR at line 1:
    ORA-16433: The database must be opened in read/write mode.

    由于时测试数据库,没有任何备份,于是决定重建控制文件。

    重建控制文件的语句如下:

    CREATE CONTROLFILE REUSE DATABASE ORCL RESETLOGS  ARCHIVELOG
        MAXLOGFILES 16
        MAXLOGMEMBERS 3
        MAXDATAFILES 100
        MAXINSTANCES 8
        MAXLOGHISTORY 292
    LOGFILE
      GROUP 1 '/u01/oradata/orcl/redo01.log'  SIZE 50M BLOCKSIZE 512,
      GROUP 2 '/u01/oradata/orcl/redo02.log'  SIZE 50M BLOCKSIZE 512,
      GROUP 3 '/u01/oradata/orcl/redo03.log'  SIZE 50M BLOCKSIZE 512
    DATAFILE
      '/u01/oradata/orcl/system01.dbf',
      '/u01/oradata/orcl/sysaux01.dbf',
      '/u01/oradata/orcl/undotbs03.db',
      '/u01/oradata/orcl/users01.dbf',
      '/u01/oradata/orcl/test01.dbf'
    CHARACTER SET WE8MSWIN1252
    ;

    进行recover操作。将所有的redo日志文件都进行了应用,应用第一组redo日志时有报错,根据报错信息,判断redo文件也有坏块。经询问开发组人员,他们尝试了进行恢复,包括重建控制文件,添加隐含参数。

    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 2147582117 generated at 07/26/2021 05:47:47 needed for thread
    1
    ORA-00289: suggestion : /arch/1_1_1078897661.dbf
    ORA-00280: change 2147582117 for thread 1 is in sequence #1
    
    
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /u01/oradata/orcl/redo01.log
    ORA-00283: recovery session canceled due to errors
    ORA-00399: corrupt change description in redo log
    ORA-00353: log corruption near block 3 change 2147582696 time 07/26/2021
    05:47:48
    ORA-00334: archived log: '/u01/oradata/orcl/redo01.log'
    
    
    ORA-01112: media recovery not started
    
    
    SQL>

    停止数据库,修改pfile文件,修改undo_management、undo_tablespace,添加隐含参数_allow_resetlogs_corruption

    *.undo_management='MANUAL'
    *.undo_tablespace='SYSTEM'
    *._allow_resetlogs_corruption=TRUE
    
    使用pfile启动数据库
    
    SQL> shutdown immediate;
    ORA-01109: database not open
    
    
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup nomount pfile='/home/oracle/pfile.ora';
    ORACLE instance started.
    
    Total System Global Area  626327552 bytes
    Fixed Size                  2215944 bytes
    Variable Size             192942072 bytes
    Database Buffers          427819008 bytes
    Redo Buffers                3350528 bytes
    SQL>

    重建控制文件

    SQL> CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS  ARCHIVELOG
      2      MAXLOGFILES 16
      3      MAXLOGMEMBERS 3
      4      MAXDATAFILES 100
      5      MAXINSTANCES 8
      6      MAXLOGHISTORY 292
      7  LOGFILE
      8    GROUP 1 '/u01/oradata/orcl/redo01.log'  SIZE 50M BLOCKSIZE 512,
      9    GROUP 2 '/u01/oradata/orcl/redo02.log'  SIZE 50M BLOCKSIZE 512,
     10    GROUP 3 '/u01/oradata/orcl/redo03.log'  SIZE 50M BLOCKSIZE 512
     11  -- STANDBY LOGFILE
     12  DATAFILE
     13    '/u01/oradata/orcl/system01.dbf',
     14    '/u01/oradata/orcl/sysaux01.dbf',
     15    '/u01/oradata/orcl/undotbs03.db',
     16    '/u01/oradata/orcl/users01.dbf',
     17    '/u01/oradata/orcl/test01.dbf'
     18  --  ,'/u01/oradata/orcl/test_ind01.dbf'
     19  CHARACTER SET WE8MSWIN1252
     20  ;
    
    Control file created.
    
    SQL>

    以resetlog打开数据库,报ORA-00600错误,数据库挡掉了。

    SQL> alter database open resetlogs;
    alter database open resetlogs
    *
    ERROR at line 1:
    ORA-00603: ORACLE server session terminated by fatal error
    ORA-00600: internal error code, arguments: [2662], [0], [2147582701], [0],
    [2147583575], [33554720], [], [], [], [], [], []
    ORA-00600: internal error code, arguments: [2662], [0], [2147582700], [0],
    [2147583575], [33554720], [], [], [], [], [], []
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00600: internal error code, arguments: [2662], [0], [2147582699], [0],
    [2147583575], [33554720], [], [], [], [], [], []
    Process ID: 15912
    Session ID: 1 Serial number: 3
    
    
    SQL>

    alert日志文件中的报错信息如下:

    Mon Jul 26 21:47:05 2021
    SMON: enabling cache recovery
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_15912.trc  (incident=138313):
    ORA-00600: internal error code, arguments: [2256], [0], [2147483648], [0], [2147582696], [], [], [], [], [], [], []
    Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_138313/orcl_ora_15912_i138313.trc
    Mon Jul 26 21:47:13 2021
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_15912.trc  (incident=138314):
    ORA-00600: internal error code, arguments: [2662], [0], [2147582699], [0], [2147583575], [33554720], [], [], [], [], [], []
    Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_138314/orcl_ora_15912_i138314.trc
    Mon Jul 26 21:47:13 2021
    Trace dumping is performing id=[cdmp_20210726214713]
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_15912.trc:
    ORA-00600: internal error code, arguments: [2662], [0], [2147582699], [0], [2147583575], [33554720], [], [], [], [], [], []
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_15912.trc:
    ORA-00600: internal error code, arguments: [2662], [0], [2147582699], [0], [2147583575], [33554720], [], [], [], [], [], []
    Error 600 happened during db open, shutting down database
    USER (ospid: 15912): terminating the instance due to error 600
    Instance terminated by USER, pid = 15912
    ORA-1092 signalled during: alter database open resetlogs...
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_15912.trc  (incident=138315):
    ORA-00600: internal error code, arguments: [2662], [0], [2147582700], [0], [2147583575], [33554720], [], [], [], [], [], []
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00600: internal error code, arguments: [2662], [0], [2147582699], [0], [2147583575], [33554720], [], [], [], [], [], []
    Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_138315/orcl_ora_15912_i138315.trc
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_15912.trc  (incident=138316):
    ORA-00600: internal error code, arguments: [2662], [0], [2147582701], [0], [2147583575], [33554720], [], [], [], [], [], []
    ORA-00600: internal error code, arguments: [2662], [0], [2147582700], [0], [2147583575], [33554720], [], [], [], [], [], []
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00600: internal error code, arguments: [2662], [0], [2147582699], [0], [2147583575], [33554720], [], [], [], [], [], []
    Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_138316/orcl_ora_15912_i138316.trc
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_15912.trc:
    ORA-00600: internal error code, arguments: [2662], [0], [2147582701], [0], [2147583575], [33554720], [], [], [], [], [], []
    ORA-00600: internal error code, arguments: [2662], [0], [2147582700], [0], [2147583575], [33554720], [], [], [], [], [], []
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00600: internal error code, arguments: [2662], [0], [2147582699], [0], [2147583575], [33554720], [], [], [], [], [], []
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_15912.trc:
    ORA-27300: OS system dependent operation:semctl failed with status: 22
    ORA-27301: OS failure message: Invalid argument
    ORA-27302: failure occurred at: sskgpwpost1
    ORA-27303: additional information: semid = 32805
    ORA-00600: internal error code, arguments: [2662], [0], [2147582701], [0], [2147583575], [33554720], [], [], [], [], [], []
    ORA-00600: internal error code, arguments: [2662], [0], [2147582700], [0], [2147583575], [33554720], [], [], [], [], [], []
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00600: internal error code, arguments: [2662], [0], [2147582699], [0], [2147583575], [33554720], [], [], [], [], [], []
    Mon Jul 26 21:47:19 2021
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_15912.trc  (incident=139361):
    ORA-00603: ORACLE server session terminated by fatal error
    ORA-00600: internal error code, arguments: [2662], [0], [2147582701], [0], [2147583575], [33554720], [], [], [], [], [], []
    ORA-00600: internal error code, arguments: [2662], [0], [2147582700], [0], [2147583575], [33554720], [], [], [], [], [], []
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00600: internal error code, arguments: [2662], [0], [2147582699], [0], [2147583575], [33554720], [], [], [], [], [], []
    Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_139361/orcl_ora_15912_i139361.trc
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_139361/orcl_ora_15912_i139361.trc:
    ORA-00603: ORACLE server session terminated by fatal error
    ORA-00600: internal error code, arguments: [2662], [0], [2147582701], [0], [2147583575], [33554720], [], [], [], [], [], []
    ORA-00600: internal error code, arguments: [2662], [0], [2147582700], [0], [2147583575], [33554720], [], [], [], [], [], []
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00600: internal error code, arguments: [2662], [0], [2147582699], [0], [2147583575], [33554720], [], [], [], [], [], []

    设置scn增进,再次拉起数据库。

    本案中设置level为3,关于增进scn是设置level多大合适,请参考另一篇文章在Oracle中增进SCN.

    SQL> alter session set events '10015 trace name adjust_scn level 3';
    
    Session altered.
    
    SQL> alter database open;
    alter database open
    *
    ERROR at line 1:
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/u01/oradata/orcl/system01.dbf'
    
    
    SQL> recover database ;
    ORA-00283: recovery session canceled due to errors
    ORA-16433: The database must be opened in read/write mode.
    
    
    SQL>

    又报了ORA-16433错误,重建控制文件,再来一遍啊。。。

    SQL> shutdown abort;
    ORACLE instance shut down.
    SQL> 
    SQL> 
    SQL> startup nomount pfile='/home/oracle/pfile.ora';
    ORACLE instance started.
    
    Total System Global Area  626327552 bytes
    Fixed Size                  2215944 bytes
    Variable Size             192942072 bytes
    Database Buffers          427819008 bytes
    Redo Buffers                3350528 bytes
    SQL> CREATE CONTROLFILE REUSE DATABASE "ORCL" RESETLOGS  ARCHIVELOG
      2      MAXLOGFILES 16
      3      MAXLOGMEMBERS 3
      4      MAXDATAFILES 100
      5      MAXINSTANCES 8
      6      MAXLOGHISTORY 292
      7  LOGFILE
      8    GROUP 1 '/u01/oradata/orcl/redo01.log'  SIZE 50M BLOCKSIZE 512,
      9    GROUP 2 '/u01/oradata/orcl/redo02.log'  SIZE 50M BLOCKSIZE 512,
     10    GROUP 3 '/u01/oradata/orcl/redo03.log'  SIZE 50M BLOCKSIZE 512
     11  -- STANDBY LOGFILE
     12  DATAFILE
     13    '/u01/oradata/orcl/system01.dbf',
     14    '/u01/oradata/orcl/sysaux01.dbf',
     15    '/u01/oradata/orcl/undotbs03.db',
     16    '/u01/oradata/orcl/users01.dbf',
     17    '/u01/oradata/orcl/test01.dbf'
     18  --  ,'/u01/oradata/orcl/test_ind01.dbf'
     19  CHARACTER SET WE8MSWIN1252
     20  ;
    
    Control file created.
    
    SQL> alter session set events '10015 trace name adjust_scn level 3';
    
    Session altered.
    
    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 2147582121 generated at 07/26/2021 21:47:05 needed for thread 1
    ORA-00289: suggestion : /arch/1_1_1078955221.dbf
    ORA-00280: change 2147582121 for thread 1 is in sequence #1
    
    
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/u01/oradata/orcl/system01.dbf'
    
    
    ORA-01112: media recovery not started
    
    
    SQL> alter database open resetlogs;
    
    Database altered.
    
    SQL>

    到此数据库已经正常打开了。但是日志文件被报错刷屏了。

    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_j001_20026.trc:
    ORA-19624: operation failed, retry possible
    ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
    ORA-01111: name for data file 6 is unknown - rename to correct file
    ORA-01110: data file 6: '/u01/app/oracle/product/11.2.0/db/dbs/MISSING00006'

    重建控制文件时,,丢了一个数据文件。所以在重建控制文件前,一定要检查,不要丢掉任何一个文件重命名数据文件,

    SQL> ALTER DATABASE RENAME FILE 'MISSING00006'
      2    TO '/u01/oradata/orcl/test_ind01.dbf';
    
    Database altered.
    
    SQL> 

    添加tempfile

    SQL> ALTER TABLESPACE TEMP ADD TEMPFILE '/u01/oradata/orcl/temp01.dbf'
      2       SIZE 20971520  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
    
    Tablespace altered.
    
    SQL>

    修改参数文件,去掉隐含参数,重启数据库

    参数改为如下:去掉隐含参数
    
    undo_management="AUTO"
    undo_tablespace="SYSTEM"
    
    
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup
    ORACLE instance started.
    
    Total System Global Area  626327552 bytes
    Fixed Size                  2215944 bytes
    Variable Size             192942072 bytes
    Database Buffers          427819008 bytes
    Redo Buffers                3350528 bytes
    Database mounted.
    Database opened.
    SQL> 
    

    此时数据库可以正常open,但是日志文件里面再次有ORA-00600报错。

    Trace dumping is performing id=[cdmp_20210726230100]
    Doing block recovery for file 8 block 641
    Resuming block recovery (PMON) for file 8 block 641
    Block recovery from logseq 1, block 3207 to scn 3221226677
    Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0
      Mem# 0: /u01/oradata/orcl/redo01.log
    Block recovery completed at rba 1.3209.16, scn 0.3221226679
    Trace dumping is performing id=[cdmp_20210726230101]
    Doing block recovery for file 8 block 368
    Resuming block recovery (PMON) for file 8 block 368
    Block recovery from logseq 1, block 3207 to scn 3221226824
    Recovery of Online Redo Log: Thread 1 Group 1 Seq 1 Reading mem 0
      Mem# 0: /u01/oradata/orcl/redo01.log
    Block recovery completed at rba 1.3265.16, scn 0.3221226825
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_m000_21333.trc  (incident=143234):
    ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
    Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_143234/orcl_m000_21333_i143234.trc
    Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_m000_21333.trc:
    ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []

    说明undo表空间还是有问题的。创建新的undo表空间,删除旧的undo表空间

    SQL> create undo tablespace UNDOTBS4 datafile '/u01/oradata/orcl/undotbs04.db' size 50M;
    
    Tablespace created.
    
    SQL> alter system set undo_tablespace='UNDOTBS4' ;
    
    System altered.
    
    SQL> drop tablespace UNDOTBS3 including contents and datafiles;
    
    Tablespace dropped.
    
    SQL>

    至此数据库恢复正常,至于漏掉的数据文件如何恢复,下回分解。

    展开全文
  • ORA-16433 The database…

    2017-05-02 10:55:36
    SQL> recover database; ORA-00283: recovery session canceled due to ...ORA-16433: The database has not been opened in read-write mode         RMAN Duplicate fails to open CLONE with ORA-01139 when

    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-16433: The database has not been opened in read-write mode

     

     

     

     

    RMAN Duplicate fails to open CLONE with ORA-01139 when the wrong undo tablespace is specified for the auxiliary [ID 1536368.1] 转到底部 


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

    修改时间:2013-3-12类型:PROBLEM状态:MODERATED优先级:3 注释 (0)    
     

    In this Document
     Symptoms
     Cause
     Solution
     References

     

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


    This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.


    Applies to:
    Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
    Information in this document applies to any platform.

    Symptoms
    RMAN Duplicate fails to open CLONE with ORA-01139 when the wrong undo tablespace is specified in auxiliary pfile:

     

    contents of Memory Script:
    {
      Alter clone database open resetlogs;
    }
    executing Memory Script
    }
    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 10/10/2012 14:27:10
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06136: ORACLE error from auxiliary database: ORA-01092: ORACLE instance ter
    minated. Disconnection forced
    ORA-30012: undo tablespace 'UNDOTBS1X' does not exist or of wrong type
     All attempts to clear the issue with manual recovery fail:

    Using SQLPlus

    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.

    SQL> alter database backup controlfile to trace;
    alter database backup controlfile to trace
    *
    ERROR at line 1:
    ORA-16433: The database must be opened in read/write mode.

    Using RMAN


    RMAN> recover clone database;
    RMAN-11003: failure during parse/execution of SQL statement: alter database
    recover if needed
     start until cancel using backup controlfile
    ORA-00283: recovery session canceled due to errors
    ORA-16433: The database must be opened in read/write mode.
     

     

     

    Cause
    Auxiliary pfile specifies an invalid undo_tablespace name that is not present in the database that is being duplicated.
    This causes the auxiliary to fail immediately after opening with  resetlogs.

    <<Bug 14744052>>:  AFTER FAILURE OF DUPICATE COMMAND DURING OPEN RESETLOGS, CLONE RAISES ORA-16433

    Closed:  Not a Bug

    A flag is set in the auxiliary pfile during resetlogs which is then unset by the dictionary check when resetlogs completes successfaully.  As resetlogs did not complete the flag is  still set causing the ORA-16433 to be raised whenever the controlfile is subsquently accessed.  There is no way to clear this flag.
     

    Solution
    Recreate the controlfile using an edited version of the create controlfile script generated from the target:  How to Recreate a Controlfile (Doc ID 735106.1)

    The auxiliary alert log shows that a resetlogs was done and will identify the online log for sequence# 1:

     

    Thread 1 opened at log sequence 1
    Current log# 1 seq# 1 mem# 0: C:\APP\DUP\REDO01.LOG
     
    To  complete the process :

    - correct undo_tablespace parameter in auxiliary pfile
    - remount auxiliary with the newly created controlfile
    - recover and open with resetlogs

     

    SQL> recover database using backup controlfile;
    ORA-00279: change 2023230 generated at 10/10/2012 14:27:01 needed for thread 1
    ORA-00289: suggestion :
    C:\APP\FAST_RECOVERY_AREA\DUP\ARCHIVELOG\2012_10_10\O1_MF_1_1_%U_.ARC
    ORA-00280: change 2023230 for thread 1 is in sequence #1

    Specify log: {=suggested | filename | AUTO | CANCEL}
    C:\APP\DUP\REDO01.LOG
    Log applied.
    Media recovery complete.
    SQL> alter database open resetlogs;

    Database altered.
     

     

    展开全文
  • ora-16433的处理思路

    千次阅读 2014-12-21 18:57:39
    在给一个生产库做灾难恢复的过程中,recover database报错 SQL> recover database;... ORA-16433: The database must be opened in read/write mode.   该库无备份无归档,意外掉电,所以走到这步必须

    在给一个生产库做灾难恢复的过程中,recover database报错
    SQL> recover database;
     ORA-00283: recovery session canceled due to errors
     ORA-16433: The database must be opened in read/write mode.
     
    该库无备份无归档,意外掉电,所以走到这步必须见招拆招的解决。
    于是准备重建控制文件,以noresetlogs拉起数据库
    结果在mount状态下,backup controlfile to trace也报错ORA-16433
    于是手动创建控制文件
    1.archive log list检查归档情况
    2.select * from v$nls_parameters检查字符集情况
    3.SQL> select name from v$datafile order by file#;
      SQL> select group#, member from v$logfile;
      SQL> select name, bytes from v$tempfile order by file#;
    确认各种文件location.

    然后使用以下模版,随便找个库trace都可以,关键是注意标点符号(尤其是logfile与datafile的最后一行,没有逗号)
    CREATE CONTROLFILE REUSE DATABASE "TEST1" NORESETLOGS NOARCHIVELOG
     MAXLOGFILES 16
     MAXLOGMEMBERS 3
     MAXDATAFILES 100
     MAXINSTANCES 8
     MAXLOGHISTORY 292
    LOGFILE
     GROUP 1 '/oradata/test1/redo01.log' SIZE 50M,
     GROUP 2 '/oradata/test1/redo02.log' SIZE 50M,
     GROUP 3 '/oradata/test1/redo03.log' SIZE 50M
    DATAFILE
    '/oradata/test1/system01.dbf',
    '/oradata/test1/undotbs01.dbf',
    '/oradata/test1/sysaux01.dbf',
    '/oradata/test1/users01.dbf',
    '/oradata/test1/cat_tb_1.dbf',
    '/oradata/test1/cat02.dbf'
    CHARACTER SET ZHS16GBK
    ;

    控制文件成功创建,进入下一流程。

    创建文件时标点不清楚会导致
    ORA-00600 [kcfccfl_1] or ORA-00600 [kccccfl_1] or ORA-02236 when Creating Control File (文档 ID 1434813.1)
    ORA-01163: SIZE clause indicates string (blocks), but should match header string
    Cause: The size specified in bytes in the SIZE clause of the CREATE CONTROLFILE statement does not equate to the number of blocks recorded in the header.
    Action: Specify the correct filename and size ( in bytes ).

    展开全文
  • SQL> startup force;...ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance ORACLE instance started. Total System Global Area 296456192 bytes Fixed Size 2252664 bytes
    SQL> startup force;
    
    ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
    ORACLE instance started.


    Total System Global Area  296456192 bytes
    Fixed Size    2252664 bytes
    Variable Size  272629896 bytes
    Database Buffers   16777216 bytes
    Redo Buffers    4796416 bytes
    Database mounted.
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/home/oracle/app/oracle/oradata/orcl2/system01.dbf'




    SQL> recover database using backup controlfile;
    ORA-00283: recovery session canceled due to errors
    ORA-16433: The database must be opened in read/write mode.




    SQL> shutdown immediate
    ORA-01109: database not open




    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount;
    ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
    ORACLE instance started.


    Total System Global Area  296456192 bytes
    Fixed Size    2252664 bytes
    Variable Size  272629896 bytes
    Database Buffers   16777216 bytes
    Redo Buffers    4796416 bytes
    Database mounted.
    SQL> recover database using backup controlfile;
    ORA-00283: recovery session canceled due to errors
    ORA-16433: The database must be opened in read/write mode.




    SQL> @$HOME/recctl_orcl3.sql
    CREATE CONTROLFILE REUSE  DATABASE "ORCL2" RESETLOGS  ARCHIVELOG
    *
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01100: database already mounted




    SQL> startup force nomount;
    ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
    ORACLE instance started.


    Total System Global Area  296456192 bytes
    Fixed Size    2252664 bytes
    Variable Size  272629896 bytes
    Database Buffers   16777216 bytes
    Redo Buffers    4796416 bytes
    SQL> @$HOME/recctl_orcl3.sql


    Control file created.


    SQL> alter database open;
    alter database open
    *
    ERROR at line 1:
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open




    SQL> alter database open resetlogs;
    alter database open resetlogs
    *
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/home/oracle/app/oracle/oradata/orcl2/system01.dbf'




    SQL> recover database using backup controlfile;
    ORA-00279: change 104646296 generated at 03/13/2017 01:04:21 needed for thread
    1
    ORA-00289: suggestion :
    /home/oracle/app/oracle/fast_recovery_area1/ORCL2/log_archive_dest/1_1_938480657
    .dbf
    ORA-00280: change 104646296 for thread 1 is in sequence #1




    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /home/oracle/app/oracle/oradata/orcl2/redo01.log
    Log applied.
    Media recovery complete.
    SQL> alter database open resetlogs;


    Database altered.


    SQL> 
    展开全文
  • 接手后,数据库处于mount状态,之前恢复过程中已经做过resetlogs的操作,也设置了"_allow_resetlogs_corruption"隐藏参数为true,目前直接开库会提示需要恢复,重新进行resetlogs时报错ORA-600 [2662],起初看到这个...
  • 数据库迁移后目标库无法恢复,报错ORA-16433: The database must be opened in read/write mode.有的说是bug,但我还没查到不知确切原因是什么,也暂时没有解决方案,望有大侠能指点12。下面是我的环境和迁移步骤:...
  • ora-16433 重建控制文件恢复

    万次阅读 2013-09-18 18:25:16
    controlfille后恢复导致一系列问题,并最终出现ora-600 2662错误,虽然这个错误很常见,但是你发现推进scn 也是无法open,感觉有点怪,远程了女神的电脑,操作不便,最后将文件压缩传过来,我在自己的vmware进行了...
  • ORA-16433,ORA-01173恢复

    千次阅读 2014-04-17 17:07:53
    同学打包上传了一个有问题的库,正好这几天没啥事,下载下来试着恢复了一下,恢复过程如下: ...+++initorcl.ora文件内容: orcl.__oracle_base='D:\app\oracle'#ORACLE_BASE set from environment *.audit_fil
  • alter database backup controlfile to trace*ERROR at line 1:ORA-16433: The database must be opened in read/write mode. 而正常mount下,是可以执行此命令的。 没办法,只能根据控制文件的语法,查询必要信息,...
  • me.ora' mount; ORACLE 例程已经启动。 Total System Global Area 1060585472 bytes Fixed Size 2182504 bytes Variable Size 771752600 bytes Database Buffers 281018368 bytes ...
  • 故障: Redo日志丢失,重建遭遇ORA-16433处理 在Oracle中,Redo日志文件包含所有的数据库变化历史记录,例如所有的DML变化(INSERT、UPDATE、DELETE和SELECT FOR UPDATE)和所有DDL语句造成的数据字典对象的更改及...
  • 操作系统环境:WIndows 2003 Server (32Bit) 数据库版本:9.2.0.1 ARCHIVED mode 错误现象:写入数据文件11时报告I/O错误,尝试进行recover时报告下列错误:  ORA-00283:恢复会话因错误而取消 ... ORA-0111
  • 12C ORA-错误汇总10 ORA-12500 to ORA-19400

    万次阅读 2016-03-02 21:40:24
    ORA-12500: TNS:listener failed to start a dedicated server process Cause: The process of starting up a dedicated server process failed. The executable could not be found or the environment may be se
  • 本篇接着上一篇ORA-16433: The database must be opened in read/write mode.继续,在重建控制文件后,漏掉了一个数据文件,导致改数据文件时offline状态,那么如何恢复这个文件呢? 查看当前数据文件 SQL> ...
  • ora-600 2662, current redo损坏 环境:开发库 oracle 11.2.0.4 + suse linux 12  故障现象:巡检时发现,数据库已经挂掉。 处理过程: 查看alert日志,发现实例被终结了,且日志里面有如下报错: Errors in file /...
  • 我做了一个这样的实验:归档模式下进行手工热备并进行还原恢复,结果将数据文件还原后,却报出了如下错误:Oracle:ORA-00283: recovery session canceled due to errors,因此开始了艰辛的排错历程 首先看一下我做了...
  • oracle ORA-01033错误的解决方案 分类: 数据库栏目 2010-09-26 20:25 2503人阅读 评论(0) 收藏 举报 oracle数据库sqlsysteminitializationdatabase 问题描述:本人那次用C#程序操作影像数据——将多...
  • 通道 ORA_DISK_1: 正在启动到默认目标的存档日志恢复 通道 ORA_DISK_1: 正在恢复存档日志 存档日志线程 =1 序列=11 通道 ORA_DISK_1: 已恢复备份段 1 段 handle=D: \BACKUP \03J8QJAJ_1_1 tag=TAG20080216T010939 ...
  • ORA-16433: The database must be opened in read/write mode.     SQL> select open_mode from v$database;   OPEN_MODE -------------------- MOUNTED   SQL> recover database; ORA-...
  • ORA-16433: The database must be opened in read/write mode. SQL> alter databse open upgrade; alter databse open upgrade  * ERROR at line 1: ORA-00940: invalid ALTER command SQL> alter database open ...
  • 在Oracle中增进SCN

    2021-07-27 15:01:01
    接上一节,在上一节数据库恢复中(ORA-16433: The database must be opened in read/write mode.),遇到ORA-00600错误,可以通过增进SCN解决。 先看一下报错: SQL> alter database open resetlogs; alter ...
  • 这真是原创的 呵   表空间USER0716为READ ONLY的表空间   SQL> drop tablespace user0716; 表空间已删除。   SQL> recover tablespace user0716;...ORA-00959: 表空间 'USER0716' 不存在 ...ORA-01124:
  • channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/test1/sysaux01.dbf channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/test1/users01.dbf channel...
  • alter database backup controlfile to trace * ERROR at line 1: ORA-16433: The database has not been opened in read-write mode CAUSE Bug 8422605 BACKUP CONTROLFILE TO TRACE GENERATES ORA-16433 AFTER ...
  • 【故障处理】ORA-3113 "end of file on communication channel":http://blog.itpub.net/26736162/viewspace-2283872/ Oracle各种版本下“示例数据库的创建”的创建:...
  • ORA-01111: name for data file 50 is unknown - rename to correct file ORA-01110: data file 50: '/u01/app/oracle/product/11.2.0/db_1/dbs/UNNAMED00050' ORA-01157: cannot identify/lock data file 50 - see...
  • [oracle@leonarding1 trace]$ tkprof LEO1_ora_16433_bind_variable.trc bind_variable.txt sys=no TKPROF: Release 11.2.0.1.0 - Development on Fri Feb 1 13:18:08 2013 Copyright (c) 1982, 2009, Oracle ...

空空如也

空空如也

1 2 3 4
收藏数 61
精华内容 24
关键字:

ora-16433