- 作者: 三十而立
- 时间：2009年10月06日 3:36:28
- 本文出自 “inthirties（三十而立）”博客，转载请务必注明作者和保留出处http://blog.csdn.net/inthirties/archive/2009/10/06/4635022.aspx
*** 2009-06-02 10:26:34.757
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [kprball()+483] [SIGSEGV] [Address not mapped to object] [0x138] [] []
Current SQL statement for this session:
select 'x' from dual
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
*** 2009-06-02 10:26:34.521
*** ACTION NAME:(Main session) 2009-06-02 10:26:34.123
*** MODULE NAME:(PL/SQL Developer) 2009-06-02 10:26:34.123
*** SERVICE NAME:(modb) 2009-06-02 10:26:34.123
*** SESSION ID:(1007.14350) 2009-06-02 10:26:34.123
Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0x138, PC: [0x97b1e03, kprball()+483]
Registers:
检查Metalink，发现如下一个Bug：5206570
说的是：Using Oracle SQL Developer it is possible to get a dump in ksusrs() or kprball() when disconnecting after the session has been marked as sniped due to idle time (max_idle_time ) limitation.
也就是说当设置了idle time的profile限制时，使用Oracle SQL Developer时，可能会因为超时等原因，在会话中断时出现该错误；看来不仅是Oracle SQL Developer会出现这个问题，现在PL/SQL Developer也会出现这个问题。
检查profile
SQL> select username,profile from dba_users where profile <>'DEFAULT';
是不是设置了limits timeouth
- 三十而立 想流泪，流不出；想说苦，欲说还休
- 专业论坛 http://www.inthirties.com
- 技术博客 http://blog.csdn.net/inthirties
- 个人站点 http://blog.inthirties.com