Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: bad error ORA-07445 with KSEDMP in trace file

Re: bad error ORA-07445 with KSEDMP in trace file

From: Ian M <me_at_NOSPAM.com>
Date: Thu, 29 Jun 2006 17:42:59 +0200
Message-ID: <44a3f4ae$0$31651$e4fe514c@news.xs4all.nl>


"Patrox" <fake_email_at_I_hate_spammmm.org> wrote in message news:44a3d7fa$0$6660$4d4eb98e_at_read.news.fr.uu.net...
> hi !
> does anyone already met (and solve if possible) this error ?
> it happens in 9.2.0.7 on a sun solaris sparc 64 bits
>
> in alert.log
> ORA-07445: exception encountered: core dump [0000000101428ABC] [SIGSEGV]
> [Address not mapped to object] [0x000000000] [] []
>
> and in trace file located in udump :
> *** SESSION ID:(21.4) 2006-06-29 15:05:18.224
> Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object),
> addr: 0x0, PC: [0x1
> 01428abc, 0000000101428ABC]
> *** 2006-06-29 15:05:18.238
> ksedmp: internal or fatal error
> ORA-07445: exception encountered: core dump [0000000101428ABC] [SIGSEGV]
> [Address not mappe
> d to object] [0x000000000] [] []
> ----- Call Stack Trace -----
> calling call entry argument values in hex
> location type point (? means dubious value)
> -------------------- -------- --------------------
> ----------------------------
> ksedmp()+328 CALL ksedst() 00000000B ? 000000000 ?
> 000000000 ? 10335A2A8 ?
> 00000003E ?
> FFFFFFFF7FFF4C18 ?
> ssexhd()+676 CALL ksedmp() 00010378B ? 10378B000 ?
> 10378B268 ? 103790000 ?
> 000102C00 ? 000000000 ?
> sigacthandler()+44 PTR_CALL 0000000000000000 000103793 ?
> FFFFFFFF7FFFBCB0 ?
> 103793000 ? 103790430 ?
> 000000000 ? 1037933B0 ?
> knipbains()+348 PTR_CALL 0000000000000000 00000000B ?
> FFFFFFFF7FFFBCB0 ?
> FFFFFFFF7FFFB9D0 ?
> 000000000 ? 000007FFF ?
> 10347EFF8 ?
> knipdis()+3104 PTR_CALL 0000000000000000 FFFFFFFF7CD5FEE0 ?
> 000000000 ? 00010347E ?
> FFFFFFFF7CD5FE68 ?
> 00000000A ?
> FFFFFFFF7CD5FE78 ?
> kporrcv()+4112 CALL knipdis() FFFFFFFF7FFFC448 ?
> FFFFFFFF7CD5FC58 ?
> 10378B608 ?
> FFFFFFFF7CD5FEE0 ?
> 000102C00 ? 000102F30 ?
> kpostr()+860 PTR_CALL 0000000000000000 00010378D ? 000000000 ?
> 10378DCA0 ? 000000001 ?
> FFFFFFFF7CD5FE78 ?
> 000000005 ?
> opiodr()+1696 PTR_CALL 0000000000000000 000000001 ? 000000020 ?
> 000102C00 ? 000102F20 ?
> FFFFFFFF7FFFC448 ?
> 102F20000 ?
> ttcpip()+1560 PTR_CALL 0000000000000000 000000000 ? 101924DA0 ?
> 103793640 ? 10378B608 ?
> 10378DB48 ?
> FFFFFFFF7FFFCAB0 ?
> opitsk()+968 CALL ttcpip() 103793638 ? 000000011 ?
> 000000000 ? 000000000 ?
> FFFFFFFF7FFFDBB8 ?
> FFFFFFFF7FFFDBB4 ?
> opiino()+1572 CALL opitsk() 000000000 ? 1037935C8 ?
> 000000000 ? 000000000 ?
> 10378DB30 ? 103793640 ?
> opiodr()+1696 PTR_CALL 0000000000000000 000380007 ? 103792488 ?
> 1038837A8 ?
> FFFFFFFF7FFFF760 ?
> 000000000 ? 3C3CFFC18 ?
> opidrv()+764 CALL opiodr() 000000000 ? 101027300 ?
> 103793640 ? 10378B608 ?
> 10378DB48 ?
> FFFFFFFF7FFFF280 ?
> sou2o()+16 CALL opidrv() 00010378B ? 000000004 ?
> 10378B608 ? 00000003C ?
> 10378B608 ? 10378B268 ?
> main()+184 CALL sou2o() FFFFFFFF7FFFF780 ?
> 00000003C ? 000000004 ?
> FFFFFFFF7FFFF760 ?
> 00003B7B0 ? 000000000 ?
> _start()+380 CALL main() 000000002 ?
> FFFFFFFF7FFFF8C8 ?
> FFFFFFFF7FFFF8E0 ?
> 000000000 ? 000000000 ?
> 100000000 ?
>
> --------------------- Binary Stack Dump ---------------------
>
> ========== FRAME [1] (ksedmp()+328 -> ksedst()) ==========
> %l0 0000000000000008 %l1 FFFFFFFF7FFF4380 %l2 000000000000000C
> %l3 FFFFFFFF7FFF4320 %l4 000000000000000C %l5 FFFFFFFF7FFF42B8
> ... etc. etc.
>
> thx and regards,
> P.

The KSEDMP is not the failing function it like the other two are part of the dump, it looks like KNIPBAINS - advanced replication?

What where you doing at the time of the error? was is an update on a replicated table? If so it might be worth taking a look at note 4036921.8 on metalink.

Regards,
Ian. Received on Thu Jun 29 2006 - 10:42:59 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US