ORA-07445 [kslgetl()+120] [SIGSEGV]和ORA-00108

最新推荐文章于 2025-07-23 15:21:57 发布

原创最新推荐文章于 2025-07-23 15:21:57 发布 · 585 阅读

0 ·

CC 4.0 BY-SA版权

ORACLE troubleshooting 专栏收录该内容

107 篇文章

订阅专栏

本文记录了一次Oracle数据库中出现大量trace文件的问题排查过程。该问题由hostname与/etc/hosts中的主机名配置不一致引起，导致数据库生成大量错误日志并占用磁盘空间。通过修正主机名配置，成功解决了此问题。

客户一测试库，磁盘空间增长很快，排查问题发现是oracle产生大量trace文件导致，

检查oracle alert日志发现大量如下报错信息：

Tue Aug 4 04:02:03 2015
Errors in file /home/oracle/admin/ccms/bdump/ccms_ora_16626.trc:
ORA-07445: exception encountered: core dump [kslgetl()+120] [SIGSEGV] [Address n
ot mapped to object] [0x000000208] [] []
ORA-00108: failed to set up dispatcher to accept connection asynchronously
Tue Aug 4 04:02:06 2015
found dead dispatcher 'D000', pid = (15, 211)
Tue Aug 4 04:02:06 2015
dispatcher 'D000' encountered error getting listening address
Tue Aug 4 04:02:06 2015
Errors in file /home/oracle/admin/ccms/bdump/ccms_ora_16628.trc:
ORA-07445: exception encountered: core dump [kslgetl()+120] [SIGSEGV] [Address n
ot mapped to object] [0x000000208] [] []
ORA-00108: failed to set up dispatcher to accept connection asynchronously

在metalink上查找了一番，发现是由于hostname与/etc/hosts中的主机名配置不一致导致的

ping hostname发现果然不通，重新配置下，数据库恢复正常。