DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: How to fix ORA-07445: exception encountered: core dump [11] [] [] [] [] []

  1. #1
    Join Date
    Oct 2000
    Posts
    76
    We got this once in a while. I suspect it happens whenever we run a certain sql statement in some program. Anyone know how to fix this or if this pose any danger to the database? I checked the dump trace file. It is like

    Thanks.Tue Nov 21 10:29:20 2000
    *** SESSION ID:(78.46440) 2000.11.21.10.29.20.000
    Exception signal: 11
    ORA-07445: exception encountered: core dump [11] [] [] [] [] []
    ----- Call Stack Trace -----
    calling call entry argument values in hex
    location type point (? means dubious value)
    -------------------- -------- -------------------- ----------------------------
    skdstinit+0xa0 CALL 0 ? 7FFF0480 ? 0 ? 0 ?
    ksedst+0xc0 CALL skdstinit 0 ? 7FFF0480 ? 0 ? 0 ?
    ssexhd+0xcc CALL ksedst B ? 7FFF0480 ? 0 ? 0 ?
    _sigtramp+0x64 CALL ssexhd B ? 7FFF0480 ? 0 ? 0 ?
    _sigtramp+0x64 CALL _sigtramp B ? 7FFF0480 ? 0 ? 0 ?
    _sigtramp+0x64 CALL _sigtramp B ? 7FFF0480 ? 0 ? 0 ?
    _sigtramp+0x64 CALL _sigtramp B ? 7FFF0480 ? 0 ? 0 ?

    And so on.
    J.T.

  2. #2
    Join Date
    Nov 2000
    Location
    Birmingham, UK
    Posts
    360
    Looks like quite a painfull O/S error! Heres the output from the AIX oerr command to analyse ORA errors:

    07445, 00000, "exception encountered: core dump [%s] [%s] [%s] [%s] [%s] [%s]"
    // *Cause: An OS exception occurred which should result in the creation of a
    // core file. This is an internal error.
    // *Action: Contact your customer support representative.


  3. #3
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092

    In general, ORA-7445 and ORA-600 messages should be reported to Oracle. There is most likely a patchset or a work-around that adresses the problem.

    This error probably generated a trace file in your udump or bdump directory. Check that file for the SQL that was running when the error was generated.

  4. #4
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092

    A quick search on metalink revealed that this might be related to a previous SHUTDOWN ABORT that caused block corruption.
    Jeff Hunter

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width