ORA-01555: snapshot too old: rollback segment number 14 with name "_SYSSMU14$"
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: ORA-01555: snapshot too old: rollback segment number 14 with name "_SYSSMU14$"

Hybrid View

  1. #1
    Join Date
    Jul 2001
    Posts
    108

    ORA-01555: snapshot too old: rollback segment number 14 with name "_SYSSMU14$"

    Dear Friends,

    I am facing the following error:

    "ORA-01555: snapshot too old: rollback segment number 14 with name "_SYSSMU14$" too small"

    Here are the system and other necessary details...

    Database: Oracle 10204 64-Bit
    OS: SUSE LINUX SLES 10 64-bit X86

    SQL> show parameters undo

    NAME TYPE VALUE
    ------------------------------------ -----------
    undo_management string AUTO
    undo_retention integer 4200
    undo_tablespace string UNDOTBSP


    The size of the UNDO Tablespace: 40GB (10GB files a total of 4)

    TableSpace Size (kb) Free (kb) Used % Free %
    --------------- ------------ ------------ ------ ------------
    UNDOTBSP 40,960,000 39,056,192 5 95

    Max. Bytes/Minutes Avg. Bytes/Minutes Max Space (Mb) Avg Space (Mb)
    ------------------ ------------------ -------------- --------------
    31,291,802 8,035,427 2,089 536


    I still dont understand that, even though we have allocated such a huge space to UNDO tablespace, and it is not even using it 100%..why is the system is throwing the error...

    Thank you,
    Nikee
    -Nikee

  2. #2
    Join Date
    May 2009
    Posts
    32
    May be try seeing the v$undostats performance view, this gives the undo generated in 10min window interval. So that this give you more detailed info.

  3. #3
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,333
    your undo retention isn't long enough for that query

  4. #4
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,554
    Quote Originally Posted by davey23uk View Post
    your undo retention isn't long enough for that query
    Dave is correct - as he is most of the time.

    Check alert log, Oracle wrote down for how long query ran before abend... bet you find query ran for more than 4200 seconds.
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

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