ora-03113 通信通道的文件结束和ORA-07445: 出现异常错误: 核心转储
2009-10-26 18:33
681 查看
今天数据库莫名其妙地出现登陆后执行报“通信通道的文件结束错误处理”的错误,搞了半天没解决,头一下晕了,最后幸亏测试部王哥帮忙,唉,看来头晕时更晕人。。。
以下是各个解决方案:
ora-03113 通信通道的文件结束错误处理
编辑D:/oracle/ora92/network/admin/sqlnet.ora文件,将LNET.AUTHENTICATION_SERVICES= (MTC)或者SQLNET.AUTHENTICATION_SERVICES= (NTS)修改为NET.AUTHENTICATION_SERVICES= (NONE).
当日志中出现:
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: 出现异常错误: 核心转储 [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: 出现异常错误: 核心转储 [ACCESS_VIOLATION] [_kglLockCursor+279] [PC:0x3FE9971] [ADDR:0xB8458B4E] [UNABLE_TO_READ] []
可以重启服务器,清空数据共享池
1 修改参数
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 清空一下共享池
SQL> alter system flush shared_pool;
System altered.
再检查这个报错的功能,正常了!下面附上一些600 BUG的原因和相关的PATCH
转自 <http://www.blogjava.net/hwpok/archive/2009/01/13/251121.html>
以下是各个解决方案:
ora-03113 通信通道的文件结束错误处理
编辑D:/oracle/ora92/network/admin/sqlnet.ora文件,将LNET.AUTHENTICATION_SERVICES= (MTC)或者SQLNET.AUTHENTICATION_SERVICES= (NTS)修改为NET.AUTHENTICATION_SERVICES= (NONE).
当日志中出现:
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: 出现异常错误: 核心转储 [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: 出现异常错误: 核心转储 [ACCESS_VIOLATION] [_kglLockCursor+279] [PC:0x3FE9971] [ADDR:0xB8458B4E] [UNABLE_TO_READ] []
可以重启服务器,清空数据共享池
1 修改参数
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 清空一下共享池
SQL> alter system flush shared_pool;
System altered.
再检查这个报错的功能,正常了!下面附上一些600 BUG的原因和相关的PATCH
转自 <http://www.blogjava.net/hwpok/archive/2009/01/13/251121.html>
相关文章推荐
- exists出现的错误:ora-03113 通信通道的文件结束
- oracle反序索引导致出现“ORA-03113: 通信通道的文件结束”错误
- ORA-07445: 出现异常错误: 核心转储 [evaopn3()+252]
- ORA-07445: 出现异常错误: 核心转储 [ldxsnf()+625] [SIGSEGV
- ORA-03113:通信通道的文件结束 ORA-03113错误分析
- 20120411_ORACLE9206导出错误修改_ora-03113 通信通道的文件结束
- ora-03113 通信通道的文件结束错误处理
- ORA-07445: 出现异常错误: 核心转储(oracle bug)
- oracle异常:ORA-27101: shared memory realm does not exist ;ORA-03113: 通信通道的文件结尾(错误解决)
- oracle异常:ORA-27101: shared memory realm does not exist ;ORA-03113: 通信通道的文件结尾(错误解决)
- ORA-07445: 出现异常错误: 核心转储 [qctosop()+1263] [ACCESS_VIOLATION] [ADDR:0x170] [PC:0x9556D97] [UNABLE_TO_R
- ORA-03113: 通信通道的文件结尾(错误解决)
- ORA-03113: 通信通道的文件结束
- ORA-03113: 通信通道的文件结束
- ora-03113 通信通道的文件结束
- 关于“ORA-03113: 通信通道的文件结束”
- Oracle错误——ORA-03113:通信通道的文件结尾 解决办法
- Oracle错误——ORA-03113:通信通道的文件结尾
- ORA-03113: 通信通道的文件结尾(错误解决)
- (oracle)ORA-03113: 通信通道的文件结尾错误处理