昨天都是好，今天早上一来就不行，出现
报ora-01092错误，进alrt文件中发现是ora-00600报错，
startup mount可以没有出错误，
在alter database open时就报错ORA-03113错误
后来看alrt文件又有ora-00600，都不知道怎么做了alrt文件入下：
Recovery of Online Redo Log: Thread 1 Group 3 Seq 286443 Reading mem 0
Mem# 0 errs 0: E:\ORACLE\ORADATA\M50x_DB\REDO03.LOG
SMON: terminating instance due to error 600
Instance terminated by SMON, pid = 2116
Thu Jun 02 10:19:58 2011
Shutting down instance (abort)
License high water = 9
Thu Jun 02 10:24:58 2011
Instance terminated by USER, pid = 192
Starting up ORACLE RDBMS Version: 8.1.6.0.0.
System parameters with non-default values:
processes = 65
shared_pool_size = 238220288
large_pool_size = 614400
java_pool_size = 20971520
control_files = E:\Oracle\oradata\M50x_DB\control01.ctl, E:\Oracle\oradata\M50x_DB\control02.ctl, E:\Oracle\oradata\M50x_DB\control03.ctl
db_block_buffers = 87238
db_block_size = 8192
compatible = 8.1.0
log_buffer = 32768
log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800
db_files = 1024
db_file_multiblock_read_count= 8
max_enabled_roles = 30
remote_login_passwordfile= EXCLUSIVE
distributed_transactions = 10
instance_name = M50x
service_names = M50x_DB
mts_dispatchers = (PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)
open_links = 4
sort_area_size = 65536
sort_area_retained_size = 65536
db_name = M50x_DB
open_cursors = 100
ifile = E:\oracle\admin\M50x_DB\pfile\INITM50x.ORA
os_authent_prefix =
job_queue_processes = 4
job_queue_interval = 60
parallel_max_servers = 5
background_dump_dest = E:\Oracle\admin\M50x_DB\bdump
user_dump_dest = E:\Oracle\admin\M50x_DB\udump
max_dump_file_size = 10240
oracle_trace_collection_name=
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
SNP0 started with pid=8
SNP1 started with pid=9
SNP2 started with pid=10
SNP3 started with pid=11
Thu Jun 02 10:28:52 2011
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Thu Jun 02 10:28:53 2011
alter database mount
Thu Jun 02 10:29:00 2011
Successful mount of redo thread 1, with mount id 4203551980.
Thu Jun 02 10:29:00 2011
Database mounted in Exclusive Mode.
Completed: alter database mount
Thu Jun 02 10:30:35 2011
alter database open
Thu Jun 02 10:30:35 2011
Beginning crash recovery of 1 threads
Thu Jun 02 10:30:35 2011
Thread recovery: start rolling forward thread 1
Recovery of Online Redo Log: Thread 1 Group 3 Seq 286443 Reading mem 0
Mem# 0 errs 0: E:\ORACLE\ORADATA\M50x_DB\REDO03.LOG
Thu Jun 02 10:30:36 2011
Thread recovery: finish rolling forward thread 1
Thread recovery: 120 data blocks read, 120 data blocks written, 1540 redo blocks read
Crash recovery completed successfully
Thu Jun 02 10:30:36 2011
Thread 1 advanced to log sequence 286444
Thread 1 opened at log sequence 286444
Current log# 1 seq# 286444 mem# 0: E:\ORACLE\ORADATA\M50x_DB\REDO01.LOG
Successful open of redo thread 1.
Thu Jun 02 10:30:36 2011
SMON: enabling cache recovery
SMON: enabling tx recovery
Thu Jun 02 10:30:37 2011
Errors in file E:\Oracle\admin\M50x_DB\bdump\M50xSMON.TRC:
ORA-00600: internal error code, arguments: [4193], [18102], [18110], [], [], [], [], []Recovery of Online Redo Log: Thread 1 Group 1 Seq 286444 Reading mem 0
Mem# 0 errs 0: E:\ORACLE\ORADATA\M50x_DB\REDO01.LOG
SMON: terminating instance due to error 600
Instance terminated by SMON, pid = 624
报ora-01092错误，进alrt文件中发现是ora-00600报错，
startup mount可以没有出错误，
在alter database open时就报错ORA-03113错误
后来看alrt文件又有ora-00600，都不知道怎么做了alrt文件入下：
Recovery of Online Redo Log: Thread 1 Group 3 Seq 286443 Reading mem 0
Mem# 0 errs 0: E:\ORACLE\ORADATA\M50x_DB\REDO03.LOG
SMON: terminating instance due to error 600
Instance terminated by SMON, pid = 2116
Thu Jun 02 10:19:58 2011
Shutting down instance (abort)
License high water = 9
Thu Jun 02 10:24:58 2011
Instance terminated by USER, pid = 192
Starting up ORACLE RDBMS Version: 8.1.6.0.0.
System parameters with non-default values:
processes = 65
shared_pool_size = 238220288
large_pool_size = 614400
java_pool_size = 20971520
control_files = E:\Oracle\oradata\M50x_DB\control01.ctl, E:\Oracle\oradata\M50x_DB\control02.ctl, E:\Oracle\oradata\M50x_DB\control03.ctl
db_block_buffers = 87238
db_block_size = 8192
compatible = 8.1.0
log_buffer = 32768
log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800
db_files = 1024
db_file_multiblock_read_count= 8
max_enabled_roles = 30
remote_login_passwordfile= EXCLUSIVE
distributed_transactions = 10
instance_name = M50x
service_names = M50x_DB
mts_dispatchers = (PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)
open_links = 4
sort_area_size = 65536
sort_area_retained_size = 65536
db_name = M50x_DB
open_cursors = 100
ifile = E:\oracle\admin\M50x_DB\pfile\INITM50x.ORA
os_authent_prefix =
job_queue_processes = 4
job_queue_interval = 60
parallel_max_servers = 5
background_dump_dest = E:\Oracle\admin\M50x_DB\bdump
user_dump_dest = E:\Oracle\admin\M50x_DB\udump
max_dump_file_size = 10240
oracle_trace_collection_name=
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
SNP0 started with pid=8
SNP1 started with pid=9
SNP2 started with pid=10
SNP3 started with pid=11
Thu Jun 02 10:28:52 2011
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Thu Jun 02 10:28:53 2011
alter database mount
Thu Jun 02 10:29:00 2011
Successful mount of redo thread 1, with mount id 4203551980.
Thu Jun 02 10:29:00 2011
Database mounted in Exclusive Mode.
Completed: alter database mount
Thu Jun 02 10:30:35 2011
alter database open
Thu Jun 02 10:30:35 2011
Beginning crash recovery of 1 threads
Thu Jun 02 10:30:35 2011
Thread recovery: start rolling forward thread 1
Recovery of Online Redo Log: Thread 1 Group 3 Seq 286443 Reading mem 0
Mem# 0 errs 0: E:\ORACLE\ORADATA\M50x_DB\REDO03.LOG
Thu Jun 02 10:30:36 2011
Thread recovery: finish rolling forward thread 1
Thread recovery: 120 data blocks read, 120 data blocks written, 1540 redo blocks read
Crash recovery completed successfully
Thu Jun 02 10:30:36 2011
Thread 1 advanced to log sequence 286444
Thread 1 opened at log sequence 286444
Current log# 1 seq# 286444 mem# 0: E:\ORACLE\ORADATA\M50x_DB\REDO01.LOG
Successful open of redo thread 1.
Thu Jun 02 10:30:36 2011
SMON: enabling cache recovery
SMON: enabling tx recovery
Thu Jun 02 10:30:37 2011
Errors in file E:\Oracle\admin\M50x_DB\bdump\M50xSMON.TRC:
ORA-00600: internal error code, arguments: [4193], [18102], [18110], [], [], [], [], []Recovery of Online Redo Log: Thread 1 Group 1 Seq 286444 Reading mem 0
Mem# 0 errs 0: E:\ORACLE\ORADATA\M50x_DB\REDO01.LOG
SMON: terminating instance due to error 600
Instance terminated by SMON, pid = 624
--参考：
--oracle 内部错误
ORA-00600: internal error code
--解决方法之一，变更了一个参数：
--STAR_TRANSFORMATION_ENABLED从原来的TRUE改为FALSE。
E:\Oracle\admin\M50x_DB\bdump\M50xSMON.TRC
rror 600 detected in background process
Dump file E:\Oracle\admin\M20X_DB\bdump\m20xSMON.TRC
Thu Jun 02 10:05:46 2011
ORACLE V8.1.6.0.0 - Production vsnsta=0
vsnsql=e vsnxtr=3
Windows 2000 Version 5.2 Service Pack 2, CPU type 586
Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
Windows 2000 Version 5.2 Service Pack 2, CPU type 586
Instance name: m20xRedo thread mounted by this instance: 1Oracle process number: 6Windows thread id: 2116, image: ORACLE.EXE
*** SESSION ID:(5.1) 2011-06-02 10:05:46.015
Using 4 slaves for 1 dead transactions
Recovered xid: 0x000d.028.000040ea in 40 milliseconds; nchk=0, size=62
*** 2011-06-02 10:05:50.140
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [4193], [18102], [18110], [], [], [], [], []
Current SQL statement for this session:
insert into fet$ (file#,block#,ts#,length) values (:1,:2,:3,:4)
----- Call Stack Trace -----
ora-600是Oracle对于一些内部错误的一个统一的错误号（类似的还有ora-7445）。要判断ora-600错误具体的类型，一般要根据其第一个参数来区分。一个ora-600的例子如下：
ORA-00600: internal error code, arguments: [15700], [3], [0x1DDE1AAB0], [], [], [], [], []
其中15700代表这个错误的具体类型，这是和并行查询相关的一个内部错误，后面的几个参数则是该错误的一些具体参数，不同类型的错误，参数的意义也不尽相同。
ora-600一共有两大类，一类的错误类型以数字标识，另外一类则以字符串标识。数字表示不同的内核层，而字符串则是具体的函数或者模块名
如果是测试库的话，我觉得可以把REDO01.LOG 这个文件干掉，然后执行recover ，然后open resetlogs;打开
http://it.china-b.com/olbf/469810.html
http://blog.sina.com.cn/s/blog_48e13c9e0100jimi.html
状态
1 SYSTEM ONLINE
2 RBSG_SPC ONLINE
3 DATA_SPC ONLINE
4 TEMP_SPC ONLINE
5 TOOLS_SPC ONLINE
6 INDX_SPC ONLINE
7 DRSYS ONLINEelect SEGMENT_NAME,STATUS from dba_rollback_segs
1 SYSTEM ONLINE
2 RBS0 NEEDS RECOVERY
3 RBS1 ONLINE
4 RBS2 ONLINE
5 RBS3 ONLINE
6 RBS4 ONLINE
7 RBS5 ONLINE
8 RBS6 ONLINE
9 RBS7 ONLINE
10 RBS8 ONLINE
11 RBS9 ONLINE
12 RBS10 ONLINE
13 RBS11 ONLINE
14 RBS12 NEEDS RECOVERY
15 RBS13 NEEDS RECOVERY
16 RBS14 NEEDS RECOVERY
17 RBS15 NEEDS RECOVERY
18 RBS16 NEEDS RECOVERY
19 RBS17 OFFLINE
20 RBS18 OFFLINE
21 RBS19 OFFLINE
22 RBS20 OFFLINE
23 RBS21 OFFLINE
24 RBS22 ONLINE
25 RBS23 ONLINE
26 RBS24 OFFLINE
27 RBS25 OFFLINE
28 RBS26 OFFLINE
29 RBS27 OFFLINE
30 RBS28 OFFLINE
晕重启过，居然打都不开，看来只有想办法重建回滚段了，各位有好的办法没有，怎么做
而且回滚段只有一部分是好的
at Jun 04 10:59:58 2011
Recovery of Online Redo Log: Thread 1 Group 1 Seq 287269 Reading mem 0
Mem# 0 errs 0: E:\ORACLE\ORADATA\M20X_DB\REDO01.LOG
Recovery of Online Redo Log: Thread 1 Group 2 Seq 287270 Reading mem 0
Mem# 0 errs 0: E:\ORACLE\ORADATA\M20X_DB\REDO02.LOG
Sat Jun 04 11:00:05 2011
Restarting dead background process SNP0
SNP0 started with pid=8
Sat Jun 04 11:02:11 2011
Errors in file E:\Oracle\admin\M20X_DB\bdump\m20xSNP0.TRC:
ORA-00600: internal error code, arguments: [4193], [18102], [18110], [], [], [], [], []