Results 1 to 3 of 3
  1. #1
    Join Date
    Mar 2002
    Posts
    5

    Angry Unanswered: FATAL ERROR IN TWO-TASK SERVER: error = 12571

    Hi,
    I've got this error 2, 3 times a day, I'm running Oracle 8.1.6 on NT 4.0 SP 6.
    The trace file is like this: ORA0021.TRC (I've attached the trace file for more details)

    --------------------

    Dump file D:\Oracle\admin\hs\udump\ORA00221.TRC
    Wed May 15 19:49:52 2002
    ORACLE V8.1.6.3.0 - Production vsnsta=0
    vsnsql=e vsnxtr=3
    Windows NT Version 4.0 Service Pack 6, CPU type 586
    Oracle8i Release 8.1.6.3.0 - Production
    JServer Release 8.1.6.3.0 - Production
    Windows NT Version 4.0 Service Pack 6, CPU type 586
    Instance name: hs

    Redo thread mounted by this instance: 1

    Oracle process number: 17

    Windows thread id: 221, image: ORACLE.EXE


    *** 2002-05-15 19:49:52.687
    *** SESSION ID26.1827) 2002-05-15 19:49:52.312
    FATAL ERROR IN TWO-TASK SERVER: error = 12571
    *** 2002-05-15 19:49:52.781
    ksedmp: internal or fatal error
    Current SQL statement for this session:
    SELECT UNIQUE
    1 UNIONPART,
    ..........
    ORDER BY SERVEDATESTR, ROOMLOCDECODE, UPPERNAME, PATRONID, MEALORDER, RECCATDECODE
    *** 2002-05-15 19:50:13.500
    ----- Call Stack Trace -----
    calling call entry argument values in hex
    location type point (? means dubious value)
    -------------------- -------- -------------------- ----------------------------
    _ksedmp+a8 CALLrel _ksedst+0
    50FE4F0
    _opitsk+f1c CALLrel _ksedmp+0 2
    _opiino+4fd CALLrel _opitsk+0 0
    _opiodr+506 CALLreg 00000000 3C 4
    450FFBFC
    _opidrv+384 CALLrel _opiodr+0 3C 4
    450FFBFC
    0
    _sou2o+19 CALLrel _opidrv+0
    _opimai+10c CALLrel _sou2o+0
    _OracleThreadStart@4+49f CALLrel _opimai+0 2
    450FFE78
    77F04EED CALLreg 00000000
    ----- Argument/Register Address Dump -----
    Argument/Register addr=450fe4f0.
    Dump of memory from 0x450FE4B0 to 0x450FE5F0
    450FE4B0 00000003 00000000 6552210E 00000033 [.........!Re3...]
    450FE4C0 00000000 00000003 450FE485 00000000 [...........E....]
    ..........

    --------------------

    Please, if someone could help me!!!
    Thanks
    Attached Files Attached Files

  2. #2
    Join Date
    May 2002
    Location
    San Clemente
    Posts
    3
    We have seen similar errors but not recently. First, I would post this to Oracle's support. It is probably a bug related to some kind of memory leak. You should also check for any pataches specific to you installation. There are many known problems with 8.1.6

    Our issues related to bugs in SQL*Net. But I have seen that error as a result of the SQL enging in the server.

    Finally, you will get that error whenever you clober a shadow process. I don't know how you would do that on NT since the shadow processes are threeds in the servers process space.

  3. #3
    Join Date
    Jul 2003
    Posts
    2

    Lightbulb

    This msg is usually related to ungracefully disconnecting clients, while the server executes pl/sql. The error occurs when the pl/sql finishes and the session isnt't there anymore.

    So in effect, it can mean

    a) unstable network
    b) impatient users
    c) slow pl/sql

    I've experienced this msg due optimizer_mode = choose, refreshed statistics and a changed execution plan, which made a formerly msec-query take 45 minutes.... (case c).

    You see, this msg sounds very special, but in fact it relates to a very common problem with many different possible reasons. Oracle should change it, like "session terminated during pl/sql execution"

Posting Permissions

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