PMON report error,next,all rollback segments become full
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: PMON report error,next,all rollback segments become full

  1. #1
    Join Date
    Sep 2001
    Posts
    1

    Question

    PMON always report error like below
    *** SESSION ID:(1.1) 2001.09.28.20.41.35.850
    *** 2001.09.28.20.41.35.850
    kssxdl: error deleting SO: c00000000ff612b0, type: 15, owner: c00000000ffa4fa8, flag:
    I/-/-/0x00:
    ORA-24756: transaction does not exist

    and later (after a few days)

    my db's all rollback segments become full

    and I have to shutdown abort

    can anyone help me?

    thank you






  2. #2
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938
    Could be that your Oracle version is not patched enough, you might be hitting some Oracle bug.



  3. #3
    Join Date
    Sep 2001
    Location
    Fort Smith
    Posts
    184
    what version you are running and how many patches you have applied .. all these details shall help us help you
    sonofsita
    http://www.ordba.net

  4. #4
    Join Date
    Sep 2001
    Location
    Makati, Philippines
    Posts
    857
    Is there an OCI/procedures that manipulate lob data?

    If there is, I suggest you separate the lob column into
    a separate table with the key of the original table. Then
    create a big rollback segment, and use the
    SET TRANSACTION USE ROLLBACK SEGMENT BIG_RBS
    before the manipulation of data is called.


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