ORA-00028 Your session has been killed
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: ORA-00028 Your session has been killed

  1. #1
    Join Date
    May 2000
    Location
    Huntsville, AL. USA
    Posts
    52
    I have a client who is using a third party application to attach to an Oracle database. Recently the user has described a problem where the machine disconnects (or appears to do this) periodically. Looking in the application logs I see ORA-00028 errors. What situations can this occur besides someone intentionally disconnecting them by killing the session on the server?

  2. #2
    Join Date
    Feb 2001
    Location
    Paris, France
    Posts
    809
    it can happen :
    1) when someones issues a alter system kill session 'SID,serial#'
    2) if a limit defined in a profile has been reached (very often it's the idle time)

  3. #3
    Join Date
    May 2000
    Location
    Huntsville, AL. USA
    Posts
    52

    Found the answer

    It turned out that the system admin had setup a script to look for transactions which were taking too long and it killed the session. I presume this was to keep it from appearing that the application was locked up during a long running SQL. What are other ways developers accomplish this? Aren't there timeouts which will just abort the transaction without killing the session (which means the user has to exit the app and re-enter)?

  4. #4
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

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