Ora-00600 Internal Error Code Arguments 2662 37
resetlogs * ERROR at line 1: ORA-00603: ORACLE server session terminated by fatal error ORA-00600: internal error code, arguments: [2662], [0], [25501152], [0], [25521272], [12583040], [], [], [], [], [], [] ORA-00600: internal error code, arguments: ora 00600 internal error code arguments 2662 1 [2662], [0], [25501151], [0], [25521272], [12583040], [], [], [], [], [], [] ORA-01092: ORACLE ora-16433: the database must be opened in read/write mode. instance terminated. Disconnection forced ORA-00600: internal error code, arguments: [2662], [0], [25501149], [0], [25521272], [12583040], [], [], [], [], [], [] Process ID: 10846 Session ID: 1 Serial number: 5 _allow_resetlogs_corruption=true ------------OR 1. shutdown immediate; 2. backup all 3. startup mount; 4. alter session set events '10015 trace name adjust_scn level 1'; 5. alter database open; ------------OR alter session set events '10015 trace name adjust_scn level 1'; Subject: How to Force the Database Open Creation Date: 12-OCT-1999 There are times when it may become necessary to force a database open. This document identifies one way to attempt to get the database open. You may need to use this procedure because something happened to the database that required you to perform recovery. The recovery completed, but you receive the following error message: ORA-01194 - file 1 needs more media recovery to be consistent You have determined that there is nothing else that can be done to get the database to a consistent state. You tried opening the database using RESETLOGS, but that also failed. Procedure: ========== To ATTEMPT to force the database open, perform the following steps: 1. Add the parameter _ALLOW_RESETLOGS_CORRUPTION = TRUE to the init.ora file 2. STARTUP MOUNT the database 3. Issue the appropriate RECOVER DATABASE command: a) RECOVER DATABASE UNTIL CANCEL or b) RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL 4. Enter CANCEL to cancel recovery - there are NO archive logs applied. 5. Enter ALTER DATABASE OPEN RESETLOGS 6. Try selecting from a table - for example, SELECT SYSDATE FROM DUAL If you get a row back, the database is open and "functional" - you could try to select from a couple of other tables just to make sure. If the instance crashed, check for trace files in the background dump destination. If you find a trace file, check to see if the trace file has an ORA-00600 [2662] error in it - this may also show up in the alert.log file. If this is true, then perform the following steps: 7. SHUTD
上海Oracle用户组 网站地图 Exadata专题 Maclean写的Oracle入门书 Oracle Latch全解 Oracle SQL性能优化专题 Oracle Database 12c新特性 12c PDB/CDB特性专题 blogs.oracle.com上的镜像 Oracle Feed World 自学Oracle之窗 24*7 Oracle紧急服务 诗檀软件PRM-DUL 下载PRM Oracle灾难恢复软件 Oracle数据恢复专题 Oracle DUL Data Unloader数据恢复工具 Oracle DUL LEARN MORE Database Force open example 2010/08/27 by Maclean Liu 3 http://myoracledbablogon.blogspot.com/2010/09/all-that-ive-found-to-recover-database.html Comments 帮网友强制打开了一个没有备份的测试库,这个库没有备份也没有打开归档,因为之前也出现过active日志文件损毁,一直使用隐式参数才能正常打开: _allow_resetlogs_corruption= TRUE 如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复! 诗檀软件专业数据库修复团队 服务热线 : 13764045638 QQ号:47079569 邮箱:service@parnassusdata.com 这次一开始这个库报ORA-600[2662]错误: Mon Aug 23 09:37:00 2010 Errors in file /oracle/QAS/saptrace/usertrace/qas_ora_852096.trc: ORA-00600: internal error code, http://www.askmaclean.com/archives/database-force-open-example.html arguments: [2662], [0], [130131504], [0], [130254136], [4264285], [], [] Mon Aug 23 09:37:02 2010 Errors in file /oracle/QAS/saptrace/usertrace/qas_ora_852096.trc: ORA-00600: internal error code, arguments: [2662], [0], [130131506], [0], [130254136], [4264285], [], [] ORA-600 [2662] "Block SCN is ahead of Current SCN"错误是当数据块中的SCN领先于current SCN,由于后台进程或服务进程都会比对UGA中的dependent SCN和数据库当前的SCN,如果数据库当前SCN小于dependent SCN,那么该进程就会报ORA-600 [2662]错误,如果遭遇该错误的是服务进程,那么服务进程一般会异常终止;如果遭遇该错误的是后台进程譬如SMON,则会导致实例CRASH。 ORA-600 [2662]错误可以能由以下几种情况引起: 1.启用隐含参数_ALLOW_RESETLOGS_CORRUPTION后,以resetlogs形式打开数据库;这种情况下发生2662错误,根本原因是没有完全前滚导致控制文件中的SCN滞后于数据块中的SCN。 2.硬件故障导致数据库没法写控制文件和联机日志文件 3.错误的部分恢复数据库 4.恢复了控制文件,但是没有使用recover database using backup controlfile进行恢复 5.数据库crash后设置了_DISABLE_LOGGING隐含参数 6.在并行服务器环境中DLM存在问题 该错误的5个参数的具体含义如下: ARGUMENTS: Arg [a] Current SCN WRAP Arg [b] Current SCN BASE Arg [c] dependent SCN WRAP Arg [d] dependent SCN BASE Arg [e] Where present this is
PDSERVICE's blog > ORA-00600: internal error code, arguments:[4000] ORA-00704: bootstrap process failure错误一例 ORA-00600: internal error code, arguments:[4000] ORA-00704: bootstrap process failure错误一例 ORA-00600: internal error code, http://www.parnassusdata.com/en/node/999?language=en arguments:[4000] ORA-00704: bootstrap process failure错误一例 Posted by PDSERVICE on Jun 01, 2016 In 节前帮网友打开了一套断电后无法正常启动的10.2.0.1数据库,该库使用非归档模式且没有任何备份。 主机断电后,该网友尝试重启数据库实例,但是遇到了ORA-00600:[kccpb_sanity_check_2]内部错误: ORA-00600: internal error code, arguments:[4000] ORA-00704: bootstrap process failure错误一例 如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复! 诗檀软件专业数据库修复团队 服务热线 : 13764045638 QQ号:47079569 邮箱:service@parnassusdata.com SQL> select status from v$instance; STATUS ------------ STARTED SQL> SQL> shutdown immediate; ORA-01507: database not mounted ORACLE instance internal error shut down. SQL> startup mount; ORACLE instance started. Total System Global Area 2147483648 bytes Fixed Size 1220432 bytes Variable Size 486539440 bytes Database Buffers 1644167168 bytes Redo Buffers 15556608 bytes ORA-00600: internal error code, arguments: [kccpb_sanity_check_2], [8198], [8175], [0x0], [], [], [], [] 该kccpb_sanity_check_2内部错误常由不正确的control file中seq#记录引起,MOS note