先是node1 alert日志下出现大量的
ARC0: Identified other thread error
ARC0: Identified other thread error
在metalink上并没有发现此类的信息描述,个人理解另一个归档进程出现错误。上述错误大量爆出后后续就出现无法连接数据库的下列情形。
[oracle@rac101 ~]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Aug 16 16:50:33 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options
SQL> show parameter processes;
ORA-03135: connection lost contact
SQL> conn / as sysdba
Connected.
SQL> show parameter processes;
ERROR:
ORA-01012: not logged on
Node1的alert日志:
Errors in file /db/oracle10grac/product/10.2.0/db/admin/benguo/bdump/benguo1_dbw0_9654.trc:
ORA-00600: internal error code, arguments: [1433], [60], [], [], [], [], [], []
Thu Aug 16 16:50:42 2012
Errors in file /db/oracle10grac/product/10.2.0/db/admin/benguo/bdump/benguo1_j000_4977.trc:
ORA-00600: internal error code, arguments: [1433], [60], [], [], [], [], [], []
Thu Aug 16 16:50:43 2012
Errors in file /db/oracle10grac/product/10.2.0/db/admin/benguo/bdump/benguo1_rbal_9836.trc:
ORA-00471: DBWR process terminated with error
查看metalink的关于ora-00600 [1433] [60]的解释
Applies to:
Oracle Server - Enterprise Edition - Version 10.2.0.1 to 10.2.0.3 [Release 10.2]
Information in this document applies to any platform.
*** Checked for relevance on 07-Jan-2011 ***
*** Checked for relevance on 08-Aug-2012 ***
刚好系统是10.2.0.1.0的oracle.
Symptoms:
ORA-00600: internal error code, arguments: [1433], [60], [], [], [], [], [], []
DBW0: terminating instance due to error 471
ORA-00471: DBWR process terminated with error
系统的alert日志中确实是先出现ora-00600[1433] ,[60]而后出现了ORA-00471导致了dbw0异常而后instance中断。
If the above is true, you are hitting Bug:5578157.
This bug is fixed in 10.2.0.4.
No backport can be created for versions < 10.2.0.4.
Workaround for Versions < 10.2.0.4:
------------------------------------
Set the following in the sqlnet.ora on both Primary and Standby database:
sqlnet.outbound_connect_timeout=20
***WARNING***
The usage of the sqlnet.outbound_connect_timeout can create problems for clients attempting to connect and should be used with great care. There have been several reported unpublished bugs in relationship to setting this parameter and therefore the preferred recommendation is to upgrade to 10.2.0.4
Metalink上要测试解决最直接还是直接upgrade 10.2.0.4了。
[@more@]
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/25362835/viewspace-1059198/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/25362835/viewspace-1059198/