Oracle数据库Immediate Kill Session错误解决方案

1.错误信息Immediate Kill Session#: 1024, Serial#: 9855Immediate Kill Session: sess: 7000001cc9bb9e8 OS pid: 799228 2.原因：This is caused by unpublished Bug 6955040 ALL THE SESSIONS LOST CONNECTION AFTER KILLING CRSD.BIN.The problem is when CRSD is killed or crashed and restarted,CRSD will run resource check action but CRS resource status will not be available at that time. Then in instance check action, it fails to get the preferred node VIP resource status and considered the preferred node VIP resource is not running.Therefore, instance check action will remove the default database service nameand disconnect sessions connected using default database service name.简单地说，就是，会话session失去了连接。欲进行资源确认，可是资源状态信息却得不到。于是，就认为资源没有在运行。然后，就断开使用默认数据库服务名的session。然后就没有然后了。。。3.解决方案方案一：升级数据库到10.2.0.5或以上版本The fix is included in 10.2.0.5 patchset and 11.1.0.7 patchset. Apply the patchset once they are available.方案二：更改服务名，不与db_name一致。Configure a service name other than the default one （same as db_name）,and get user to use the non-default service name for connection.具体步骤如下1，获得实例名： select instance_name from v$instance; 2，获得当前service_names：SQL> show parameter name NAME TYPE VALUE------------------------------------ ----------- -------------db_file_name_convert stringdb_name string orcldb_unique_name string orclglobal_names boolean FALSEinstance_name string orcllock_name_space stringlog_file_name_convert stringservice_names string orcl3.更改service_names：alter system set service_names = "orcl1" scope=MEMORY sid="orcl";Oracle 创建函数实例Oracle数据库Process OS id : 799228 alive after kill相关资讯 Oracle错误日志

Oracle 11g安装中遇到的问题及解决（11/30/2012 18:49:13）
重启数据库遇到PRCR-1079，CRS- （08/17/2012 09:40:27）
ORA-32004 的错误处理（08/04/2012 15:46:08）

ORA-01652，temp表空间不足的相关（10/15/2012 15:50:12）
ORA-00245 错误解决（08/17/2012 09:37:43）
ORA-04031错误的解决思路（07/30/2012 15:14:18）

本文评论查看全部评论（0）