最近的错误日志，，可是看不懂 ORA-600 signalled during: alter database open... Tue Dec 09 19:04:37 2003 Errors in file c:\oracle\admin\ora9\bdump\ora9_qmn0_2320.trc: ORA-00600: internal error code, arguments: [ktuincrustat_1], [], [], [], [], [], [], []Tue Dec 09 19:05:29 2003 Restarting dead background process QMN0 QMN0 started with pid=9 Tue Dec 09 19:06:34 2003 Errors in file c:\oracle\admin\ora9\bdump\ora9_qmn0_2272.trc: ORA-00600: internal error code, arguments: [ktuincrustat_1], [], [], [], [], [], [], []Tue Dec 09 19:10:35 2003 Restarting dead background process QMN0 QMN0 started with pid=9 Tue Dec 09 19:11:38 2003 Errors in file c:\oracle\admin\ora9\bdump\ora9_qmn0_2264.trc: ORA-00600: internal error code, arguments: [ktuincrustat_1], [], [], [], [], [], [], []Tue Dec 09 19:15:36 2003 Restarting dead background process QMN0 QMN0 started with pid=9 Tue Dec 09 19:16:38 2003 Errors in file c:\oracle\admin\ora9\bdump\ora9_qmn0_2232.trc: ORA-00600: internal error code, arguments: [ktuincrustat_1], [], [], [], [], [], [], []Shutting down instance: further logons disabled Shutting down instance (immediate) License high water = 3 Waiting for dispatcher 'D000' to shutdown Waiting for shared server 'S000' to die All dispatchers and shared servers shutdown
这是我查的ORA600错误，属于其中的操作超时，是因为我建立了一个资源计划，将其中的某一项做了修改，结果无论如何都登陆不了，提示操作超时。 然后我将RESOURCE_MANAGER_PLAN改想清空，提示无法解析连接描述符中指定的SID. ORA-600的错误经常伴随跟踪文件的状态转储（系统状态和进程状态），系统状态存储将包括ORACLE RDBMS持有的当前对象的信息，进程状态转储则将显示特殊进程持有的对象，当进程符合了某错误条件时，经常是由于一些信息取自它持有的一个块，如果我们知道这些错误进程持有的块，就容易跟踪问题的来源。解决方法：一般来说出现这个错误我们本身是无法解决的，只有从提高系统本身各方面来解决这个内部问题，如增加硬件设备，调整系统性能，使用OPS（当然OPS从某种意义上说并不是一种好的解决方式）等。ORA-600错误的第一个变量用于标记代码中错误的位置（代码中的每个部分的第一变量都不一样），从第二个到第五个变量显示附加信息，告诉OSS代码在哪里出现了错误。一个报错例子如下：ORA-00600: internal error code, arguments: [1237], [], [], [], [], [], [], []相应的英文如下：Cause:This is a catchall internal error message for Oracle program exceptions.It indicates that a process has met a low-level,unexpected condition.Various causes of this message include:Time-outs（超时）File corruption(文件太老)Failed data checks in memory（内存检索失败）Hardware,memory,or I/O errors（硬件、内存或者磁盘错误）Incorrectly restored files（错误的重建文件
应该是那个资源文件的问题，
提示无法解析连接描述符中指定的ora9
可是我的SID并没有改
我急得要命
位置oracle_home\admin\”数据库实例名“\bdump
ORA-600 signalled during: alter database open...
Tue Dec 09 19:04:37 2003
Errors in file c:\oracle\admin\ora9\bdump\ora9_qmn0_2320.trc:
ORA-00600: internal error code, arguments: [ktuincrustat_1], [], [], [], [], [], [], []Tue Dec 09 19:05:29 2003
Restarting dead background process QMN0
QMN0 started with pid=9
Tue Dec 09 19:06:34 2003
Errors in file c:\oracle\admin\ora9\bdump\ora9_qmn0_2272.trc:
ORA-00600: internal error code, arguments: [ktuincrustat_1], [], [], [], [], [], [], []Tue Dec 09 19:10:35 2003
Restarting dead background process QMN0
QMN0 started with pid=9
Tue Dec 09 19:11:38 2003
Errors in file c:\oracle\admin\ora9\bdump\ora9_qmn0_2264.trc:
ORA-00600: internal error code, arguments: [ktuincrustat_1], [], [], [], [], [], [], []Tue Dec 09 19:15:36 2003
Restarting dead background process QMN0
QMN0 started with pid=9
Tue Dec 09 19:16:38 2003
Errors in file c:\oracle\admin\ora9\bdump\ora9_qmn0_2232.trc:
ORA-00600: internal error code, arguments: [ktuincrustat_1], [], [], [], [], [], [], []Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water = 3
Waiting for dispatcher 'D000' to shutdown
Waiting for shared server 'S000' to die
All dispatchers and shared servers shutdown
然后我将RESOURCE_MANAGER_PLAN改想清空，提示无法解析连接描述符中指定的SID.
ORA-600的错误经常伴随跟踪文件的状态转储（系统状态和进程状态），系统状态存储将包括ORACLE RDBMS持有的当前对象的信息，进程状态转储则将显示特殊进程持有的对象，当进程符合了某错误条件时，经常是由于一些信息取自它持有的一个块，如果我们知道这些错误进程持有的块，就容易跟踪问题的来源。解决方法：一般来说出现这个错误我们本身是无法解决的，只有从提高系统本身各方面来解决这个内部问题，如增加硬件设备，调整系统性能，使用OPS（当然OPS从某种意义上说并不是一种好的解决方式）等。ORA-600错误的第一个变量用于标记代码中错误的位置（代码中的每个部分的第一变量都不一样），从第二个到第五个变量显示附加信息，告诉OSS代码在哪里出现了错误。一个报错例子如下：ORA-00600: internal error code, arguments: [1237], [], [], [], [], [], [], []相应的英文如下：Cause:This is a catchall internal error message for Oracle program exceptions.It indicates that a process has met a low-level,unexpected condition.Various causes of this message include:Time-outs（超时）File corruption(文件太老)Failed data checks in memory（内存检索失败）Hardware,memory,or I/O errors（硬件、内存或者磁盘错误）Incorrectly restored files（错误的重建文件
说句实话，csdn真不怎么样