oracle问题，高手来抢分了。。。 ( 积分: 200 )

我使用的是oralce9i，一下是我截取跟踪文件的片断。<br>Windows&nbsp;thread&nbsp;id:&nbsp;3900,&nbsp;image:&nbsp;ORACLE.EXE<br>***&nbsp;2007-11-06&nbsp;09:54:20.000<br>***&nbsp;SESSION&nbsp;ID48.24557)&nbsp;2007-11-06&nbsp;09:54:20.000<br>FATAL&nbsp;ERROR&nbsp;IN&nbsp;TWO-TASK&nbsp;SERVER:&nbsp;error&nbsp;=&nbsp;12571<br>***&nbsp;2007-11-06&nbsp;09:54:20.000<br>ksedmp:&nbsp;internal&nbsp;or&nbsp;fatal&nbsp;error<br>Current&nbsp;SQL&nbsp;statement&nbsp;for&nbsp;this&nbsp;session:<br>select&nbsp;count(*)&nbsp;from&nbsp;(SELECT&nbsp;OFFICE_WorkflowInstance.WorkflowInstance_GUID&nbsp;FROM&nbsp;OFFICE_WorkflowInstance,OFFICE_WorkflowInstanceActors&nbsp;WHERE&nbsp;OFFICE_WorkflowInstanceActors.WorkflowInstance_GUID=OFFICE_WorkflowInstance.WorkflowInstance_GUID&nbsp;AND&nbsp;OFFICE_WorkflowInstance.WORKFLOW_GUID='{00000000-0000-0000-0000-000000000062}'&nbsp;AND&nbsp;OFFICE_WorkflowInstance.InstanceDeleted&nbsp;=&nbsp;0&nbsp;AND&nbsp;(OFFICE_WorkflowInstance.InstanceStatus&nbsp;=&nbsp;2&nbsp;OR&nbsp;OFFICE_WorkflowInstance.InstanceStatus&nbsp;=&nbsp;3&nbsp&nbsp;AND&nbsp;OFFICE_WorkflowInstanceActors.Actors_Classify&nbsp;=&nbsp;1&nbsp;AND&nbsp;OFFICE_WorkflowInstanceActors.Person_Guid&nbsp;=&nbsp;'{3BF5831B-ED6A-DE4E-A8DE-76BC4FC700A2}'&nbsp;ORDER&nbsp;BY&nbsp;OFFICE_WorkflowInstance.UpdateDate&nbsp;desc)<br>===<br>请问：出现这个错误的原因是什么？如何解决？

自己顶一下。。。请高手指点。。

我也顶一下。头都看混了

当数据库执行完查询，返回结果时，session已经不存在了<br><br>可能和网络断开，客户端异常退出有关<br><br>该SQL语句应该为查询某用户经办流程个数，多做了排序操作<br><br>不排除由于SQL执行太慢，应用层超时自动终止session的可能性

以下是metalink中的描述：<br><br>fact:&nbsp;Oracle&nbsp;Server&nbsp;-&nbsp;Enterprise&nbsp;Edition<br>symptom:&nbsp;Errors&nbsp;appear&nbsp;in&nbsp;alert&nbsp;file&nbsp;<br>symptom:&nbsp;FATAL&nbsp;ERROR&nbsp;IN&nbsp;TWO-TASK&nbsp;SERVER:<br>symptom:&nbsp;ERROR&nbsp;=&nbsp;12571<br>symptom:&nbsp;trace&nbsp;file&nbsp;generated<br>symptom:&nbsp;Database&nbsp;operations&nbsp;continue&nbsp;successfully<br>cause:&nbsp;The&nbsp;most&nbsp;common&nbsp;cause&nbsp;for&nbsp;the&nbsp;above&nbsp;error&nbsp;is&nbsp;an&nbsp;ungraceful&nbsp;<br>disconnection&nbsp;of&nbsp;a&nbsp;session&nbsp;from&nbsp;the&nbsp;oracle&nbsp;db&nbsp;while&nbsp;the&nbsp;db&nbsp;is&nbsp;currently&nbsp;running&nbsp;<br>a&nbsp;dml&nbsp;statement&nbsp;issued&nbsp;by&nbsp;that&nbsp;session.&nbsp;&nbsp;The&nbsp;error&nbsp;is&nbsp;recorded&nbsp;when&nbsp;oracle&nbsp;<br>attempts&nbsp;to&nbsp;reply&nbsp;back&nbsp;to&nbsp;the&nbsp;session&nbsp;with&nbsp;the&nbsp;results&nbsp;of&nbsp;the&nbsp;dml&nbsp;and&nbsp;cannot&nbsp;<br>access&nbsp;the&nbsp;session.&nbsp;&nbsp;Overall&nbsp;database&nbsp;operations&nbsp;are&nbsp;usually&nbsp;not&nbsp;affected.<br><br>An&nbsp;ungraceful&nbsp;disconnection&nbsp;could&nbsp;cause&nbsp;by&nbsp;but&nbsp;is&nbsp;not&nbsp;limited&nbsp;to&nbsp;any&nbsp;of&nbsp;the&nbsp;<br>following:<br>-&nbsp;the&nbsp;client&nbsp;machine&nbsp;crashed<br>-&nbsp;the&nbsp;network&nbsp;connection&nbsp;crashed<br>-&nbsp;the&nbsp;user&nbsp;exited&nbsp;the&nbsp;session&nbsp;improperly&nbsp;(not&nbsp;issuing&nbsp;the&nbsp;'exit'&nbsp;command)&nbsp;<br>-&nbsp;the&nbsp;user&nbsp;application&nbsp;allows&nbsp;the&nbsp;user&nbsp;to&nbsp;exit&nbsp;the&nbsp;application&nbsp;without&nbsp;properly&nbsp;<br>terminating&nbsp;the&nbsp;session.<br><br>The&nbsp;above&nbsp;can&nbsp;cause&nbsp;problems&nbsp;with&nbsp;corrupted&nbsp;rollback&nbsp;segments&nbsp;if&nbsp;occurring&nbsp;on&nbsp;a&nbsp;<br>regular&nbsp;basis&nbsp;and&nbsp;is&nbsp;not&nbsp;addressed.&nbsp;&nbsp;This&nbsp;would&nbsp;require&nbsp;db&nbsp;recovery&nbsp;and&nbsp;<br>possibly&nbsp;a&nbsp;db&nbsp;rebuild&nbsp;(not&nbsp;a&nbsp;light&nbsp;matter)<br><br>PMON&nbsp;will&nbsp;usually&nbsp;rollback&nbsp;most&nbsp;transactions&nbsp;in&nbsp;the&nbsp;rollback&nbsp;segments&nbsp;for&nbsp;a&nbsp;<br>session&nbsp;if&nbsp;it&nbsp;finds&nbsp;that&nbsp;the&nbsp;session&nbsp;has&nbsp;been&nbsp;ungracefully&nbsp;disconnected,&nbsp;but&nbsp;<br>there&nbsp;is&nbsp;always&nbsp;a&nbsp;chance&nbsp;that&nbsp;it&nbsp;cannot&nbsp;and&nbsp;this&nbsp;will&nbsp;lead&nbsp;to&nbsp;rollback&nbsp;segment&nbsp;<br>corruption.<br><br><br><br>fix:<br><br>The&nbsp;dml&nbsp;and&nbsp;the&nbsp;user&nbsp;that&nbsp;issued&nbsp;the&nbsp;dml&nbsp;can&nbsp;be&nbsp;determined&nbsp;from&nbsp;the&nbsp;trace&nbsp;file.&nbsp;<br>&nbsp;The&nbsp;current&nbsp;dml&nbsp;is&nbsp;in&nbsp;the&nbsp;tracefile&nbsp;header&nbsp;section.&nbsp;The&nbsp;user&nbsp;can&nbsp;be&nbsp;found&nbsp;in&nbsp;<br>the&nbsp;process&nbsp;state&nbsp;dump&nbsp;of&nbsp;the&nbsp;trace.&nbsp;&nbsp;The&nbsp;process&nbsp;state&nbsp;shows&nbsp;the&nbsp;machine,&nbsp;<br>o/suser,&nbsp;and&nbsp;user&nbsp;for&nbsp;the&nbsp;session.<br><br>The&nbsp;DBA&nbsp;can&nbsp;use&nbsp;this&nbsp;information&nbsp;to&nbsp;determine&nbsp;what&nbsp;the&nbsp;user&nbsp;was&nbsp;doing&nbsp;at&nbsp;the&nbsp;<br>time&nbsp;and&nbsp;if&nbsp;there&nbsp;was&nbsp;an&nbsp;ungraceful&nbsp;exit&nbsp;from&nbsp;the&nbsp;session&nbsp;the&nbsp;user&nbsp;was&nbsp;<br>utilizing.<br><br>The&nbsp;DBA&nbsp;should&nbsp;then&nbsp;address&nbsp;the&nbsp;cause&nbsp;of&nbsp;the&nbsp;ungraceful&nbsp;exit&nbsp;to&nbsp;reduce&nbsp;the&nbsp;<br>possibility&nbsp;of&nbsp;recurrence.