Today's database inexplicably landed after the implementation of the report "Communication channel file end error Handling" error, engaged in a half-day did not solve, the first dizzy, finally thanks to the test department Wang Go Help, alas, it seems dizzy when more dizzy people ...
Here are the solutions:
File end error handling for ora-03113 communication channel
Edit the D:/oracle/ora92/network/admin/sqlnet.ora file to lnet.authentication_services= (MTC) or Sqlnet.authentication_ Services= (NTS) is modified to net.authentication_services= (NONE).
The log appears:
Mon Oct 26 17:18:08 2009
Errors in file d:/oracle/product/10.2.0/admin/orcl/udump/orcl_ora_1676.trc:
ORA-07445: Abnormal error: Core dump [access_violation] [_kgllockcursor+279] [pc:0x3fe9971] [addr:0xb8458b4e] [Unable_to_read] []
Mon Oct 26 17:18:08 2009
Errors in file d:/oracle/product/10.2.0/admin/orcl/udump/orcl_ora_1676.trc:
ORA-07445: Abnormal error: Core dump [access_violation] [_kgllockcursor+279] [pc:0x3fe9971] [addr:0xb8458b4e] [Unable_to_read] []
Can reboot the server and empty the data sharing pool
1 Modifying parameters
Sql> alter system set cursor_sharing=similar;
System altered.
elapsed:00:00:00.00
Sql> Show Parameter cursor_sharing
NAME TYPE VALUE
------------------------------------ -------------------------------- ------------------------------
Cursor_sharing string SIMILAR
2 Clear the shared pool
Sql> alter system flush Shared_pool;
System altered.
Again check the function of this error, normal. Attached below are some of the reasons for the bug and related patch
Transfer from