ORA-01548: active rollback segment

Hi, I'm a junior DBA .
     I have 1 problem.
I have create a new undo tablespace and set it to undo tablespace of instance
ora11> alter system set
undo_tablespace=undotbs2;
but we can not drop the original one:
ora11> drop tablespace undotbs1 including contents and datafiles; drop tablespace undotbs1 including contents and datafiles
ERROR at line 1: ORA-01548: active rollback segment ‘_SYSSMU2_6654314$’ found, terminate dropping tablespace
how can solved this problem?

These are all the question asked by RHELSENSEI and answered by Anar Godjaev. Check RHELSENSEI activity
https://forums.oracle.com/thread/2593502
https://forums.oracle.com/thread/2592693
https://forums.oracle.com/thread/2591625
https://forums.oracle.com/thread/2590123
https://forums.oracle.com/thread/2589495
https://forums.oracle.com/thread/2590123
https://forums.oracle.com/thread/2589495
https://forums.oracle.com/thread/2589494
https://forums.oracle.com/thread/2589494
https://forums.oracle.com/thread/2589025
https://forums.oracle.com/thread/2588204
https://forums.oracle.com/thread/2588264
https://forums.oracle.com/thread/2587557
https://forums.oracle.com/thread/2587091
https://forums.oracle.com/thread/2586768
https://forums.oracle.com/thread/2586765

Similar Messages

  • Cannot drop old undo tablespace. Cause: active rollback segment

    dear all.
    db: oracle 10.2.0.1
    os: rhel as version 5 64 bits.
    This is a testing database. And my database is online and open. But i can free the external usb disk that contains my ols undotbs.
    I want to drop old undo tablespace but this is not possible.
    1.- In order to open my database i had my datafile( '/mnt/hdext/back_plelds/undotbs02.dbf') offline drop, and then i can to open my database.
    2.- When i try to delete my old undo tablespace im getting this error:
    SQL> drop tablespace undotbs1 including contents and datafiles;
    drop tablespace undotbs1 including contents and datafiles
    ERROR at line 1:
    ORA-01548: active rollback segment '_SYSSMU1$' found, terminate dropping
    tablespace
    3.- My default undo_tablespace is another that i was created before step 1.
    SQL> sho parameter undo_ta
    NAME TYPE VALUE
    undo_tablespace string UNDOTMP
    SQL>
    Well i search in metalink ORA-01548 code error and in 18947.1 doc whows me that the solution is:
    Action: Shut down instances that use the active rollback segments in the
    tablespace and then drop the tablespace.
    4.- I try to shutdown but im getting:
    SQL> shutdown immediate;
    ORA-00376: file 10 cannot be read at this time
    ORA-01110: data file 10: '/mnt/hdext/back_plelds/undotbs02.dbf'
    SQL>
    This /mnt/hdext is an external USB disk and i have all permissions. I exported tables without any problem and i can read all files.
    i search un metalink again ora codes (ORA-00376 ORA-01110) and the doc id: 427801.1 shows in the solution:
    Drop the old undo tablespace instead of making it offline.
    but when i try to drop the tablespace it shows the error describe in the step 2.
    Facts:
    - my tablespace UNDOTBS1 is ONLINE. I put in offline and this is not the solution.
    - This is the status of my rollback segments:
    SQL> select segment_name, status from dba_rollback_segs where
    2 tablespace_name='UNDOTBS1';
    SEGMENT_NAME STATUS
    _SYSSMU1$                      NEEDS RECOVERY
    _SYSSMU2$                      NEEDS RECOVERY
    _SYSSMU3$                      NEEDS RECOVERY
    _SYSSMU4$                      NEEDS RECOVERY
    _SYSSMU5$                      NEEDS RECOVERY
    _SYSSMU6$                      NEEDS RECOVERY
    _SYSSMU7$                      NEEDS RECOVERY
    _SYSSMU8$                      NEEDS RECOVERY
    _SYSSMU9$                      NEEDS RECOVERY
    _SYSSMU10$                     NEEDS RECOVERY
    _SYSSMU11$                     OFFLINE
    SEGMENT_NAME STATUS
    _SYSSMU12$                     OFFLINE
    12 rows selected.
    SQL>
    - I have the note (Unable to drop und tablespace In this article describe the problem but this is not the same. The difference is that i cannot drop the rollback segment that describe in step 2.
    SQL> drop rollback segment "_SYSSMU1$";
    drop rollback segment "_SYSSMU1$"
    ERROR at line 1:
    ORA-30025: DROP segment '_SYSSMU1$' (in undo tablespace) not allowed
    in metalink the doc id: 173696.1 shows the solution:
    Action:     Check the undo segment name and reissue statement if necessary.
    i cannot drop the rollback_segment
    What can i do ???
    thanks a lot.

    in step 4 did you try with shutdown abort?
    If its still does not work then create another new table space with new file and then swtich to that tablespace http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/undo.htm#sthref1504Khurram

  • What is the table for active rollback segments

    Hi,
    Can anyone please let me know what is the table name for 'Active Rollback Segments', is it dba_rollback_segs?
    Regards,
    - Sri

    Yes, this is the view which will report you the rollback segment name, owner and other information about the rollback segments.
    You can also query dba_undo_extents view.

  • ORA-01548 after bounce the Database...

    Hi All,
    User has run some job which occupied 50G in undo tablespace. Now job is finished and I want to reclaim that 50G from undo.
    So I created another undo tbs of small size say 2G and switch to new undo tbs.. all segment is online with new undotbs but one segment having "partial available" status with old undotbs.
    I bounce the DB also but still when going to delete older undotbs its throwing me this error:
    drop tablespace undotbs2 including contents and datafiles
    ERROR at line 1:
    ORA-01548: active rollback segment '_SYSSMU23$' found, terminate dropping
    tablespace
    when I check how many extent with this "_SYSSMU23$" segment..it gives 384 rows with "ACTIVE" status.
    select owner,segment_name,tablespace_name,status from dba_undo_extents where segment_name='_SYSSMU23$';
    how can I reclaim my undo space ?
    Any suggestion?
    Thanks...

    Hi Nagendra,
    select tablespace_name,status,count(*) as HOW_MANY from dba_undo_extents group by tablespace_name,status
    TABLESPACE_NAME STATUS HOW_MANY
    UNDOTBS2 EXPIRED 1195
    TESTUND EXPIRED 294
    TESTUND UNEXPIRED 116
    from the above query it shows UNDOTBS2 having expired extents but with one of the segment it showing "active" status as below:
    SQL> select owner,segment_name,tablespace_name,status from dba_undo_extents where segment_name='_SYSSMU23$';
    OWN SEGMENT_NAME TABLESPACE_NAME STATUS
    SYS _SYSSMU23$                     UNDOTBS2                       ACTIVE       
    SYS _SYSSMU23$                     UNDOTBS2                       ACTIVE       
    SYS _SYSSMU23$                     UNDOTBS2                       ACTIVE                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • ROLLBACK SEGMENT의 MINEXTENTS를 20 이상으로 하면 좋은 이유

    제품 : ORACLE SERVER
    작성날짜 : 2003-06-19
    ROLLBACK SEGMENT의 MINEXTENTS를 20 이상으로 하면 좋은 이유
    =========================================================
    PURPOSE
    이 자료는 다음과 같은 주제에 대하여 소개하는 자료이다.
    이 문서는 database application의 요구 사항을 충족시키기 위해 고려되어
    져야 할 rollback segment tablespace 구성에 관한 내용을 담고 있다.
    Creating, Optimizing, and Understanding Rollback Segments
    -Rollback Segment 구성과 기록 방식
    -Transaction에 Rollback Segment를 할당하는 Oracle 내부 메커니즘
    -Rollback Segment 크기와 갯수
    -Rollback Segment의 크기와 갯수 결정을 위한 테스트
    -Rollback Segment extent의 크기와 갯수
    -Rollback Segment의 minextents를 20 이상으로 하면 좋은 이유?
    -Rollback Segment의 Optimal storage parameter와 Shrink
    Explanation
    Rollback Segment 구성과 기록 방식
    Rollback segment는 extent라 불리는 연속적인 여러 개의 block으로 구성된다.
    Rollback segment는 ordered circular 방식으로 extent를 쓰게 되는데,
    current extent가 full이 되면 next extent로 옮겨 가며 사용하게 된다.
    Transaction은 rollback segment 내의 current location에 record를 쓴 다음,
    record의 size 만큼 current pointer를 옮겨 간다.
    Rollback segment에 현재 record가 쓰여지고 있는 위치를 "Head"라고 한다.
    또한, "Tail"이란 용어는 rollback segment에서 가장 오래된 active
    transaction record의 시작 위치가 되는 부분을 말한다.
    Transaction에 Rollback Segment를 할당하는 Oracle 내부 메커니즘
    새로운 transaction이 rollback segment 를 요청하면, 각 rollback segment
    를 이용하고 있는 active transaction 갯수를 확인하여 가장 적은 갯수의
    active transaction 을 가진 rollback segment를 할당하게 된다.
    Rollback segment는 transaction load를 처리하기에 충분한 크기를 가져야
    하고, 필요한 만큼의 rollback segment를 사용할 수 있도록 적당한 갯수의
    rollback segment를 가져야 한다.
    1. 한 transaction은 단 하나의 rollback segment만을 사용할 수 있다.
    2. 같은 extent에 여러 transaction이 기록할 수 있다.
    3. Rollback segment의 Head는 Tail에 의해 현재 사용 중인 extent를
    침범하지 않는다.
    4. 링 형태로 구성되어 있는 rollback segment의 extent들은 다음 extent를
    찾을 때 절대 건너 뛰는 일이 없으며, 순서를 뒤바꾸어 사용하지도 않는다.
    5. Head가 next extent를 찾지 못하면, 새로운 extent를 추가로 할당하고,
    그 extent를 링 안에 포함시킨다.
    위와 같은 원리를 감안할 때, transaction size 뿐만 아니라 transaction
    time도 상당히 중요한 고려 사항이라는 것을 알 수 있다.
    Rollback Segment 크기와 갯수
    Rollback segment size가 충분한지 판단하는 기준은 transaction activity에
    직접적으로 영향을 받는다. 주로 일어나는 transaction activity에 근거하여
    rollback segment size를 결정하여야 하고, 잘 일어나지 않는 특수한 경우의
    큰 transaction이 문제라면 별도의 rollback segment로 관리되어야 한다.
    Transaction 발생 중 Head가 너무 빨리 wrap around 시켜서 tail을 catch하
    지 않도록 하여야 하며, 자주 변경되는 data에 대해 long-running query가
    수행되었을 경우 read-consistency가 유지될 수 있도록 rollback segment
    가 wrap around되지 않아야 한다.
    Rollback segment 갯수를 적당히 잡아야 하는 이유는 process들 간에
    contention을 방지하기 위함이고, V$WAITSTAT, V$ROLLSTAT, V$ROLLNAME
    view를 통해서 contention을 확인할 수 있으며, 조회문은 다음과 같다.
    sqlplus system/manager
    select rn.name, (rs.waits/rs.gets) rbs_header_wait_ratio
    from v$rollstat rs, v$rollname rn
    where rs.usn = rn.usn
    order by 1;
    위의 query에 의해 조회된 rbs_header_wait_ratio 가 0.01 보다 크면,
    rollback segment 갯수를 추가한다.
    Rollback Segment의 크기와 갯수 결정을 위한 테스트
    1. Rollback segment tablespace 생성
    2. 테스트하기 위해 생성할 Rollback segment 갯수 결정
    3. 같은 크기의 extent로 rollback segment 생성
    extent 갯수는 최대 확장 시 10 - 30 개 정도가 되도록 extent 크기를 결정
    4. Rollback segment의 minextents는 2이다.
    5. 테스트할 rollback segment와 system rollback segment만 online 상태로 한다.
    6. Transaction을 수행하고, 필요하면 application을 load한다.
    7. Rollback segment contention을 확인한다.
    8. Rollback segment가 최대 얼마까지 확장하는지 모니터링한다.
    Rollback Segment extent의 크기와 갯수
    Rollback segment가 자라나는 최대 사이즈를 알 수 있는데, 이 수치를
    "minimum coverage size"라 한다. 만약, contention이 발생한다면 rollback
    segment 갯수를 늘려 가면 테스트를 반복한다. 또한, extent 갯수가 10개
    미만이나 30개 이상이 될 필요가 있다면 extent 크기를 늘리거나 줄이면서
    테스트를 반복해 나가면 된다.
    Rollback segment의 extent 크기를 정할 때, 각 extent는 모두 같은 크기로
    생성할 것을 recommend한다.
    Rollback tablespace의 크기는 extent size의 배수로 지정한다.
    최적의 성능을 위한 rollback segment의 minextents는 20 이상이어야 한다.
    Rollback Segment의 minextents를 20 이상으로 하면 좋은 이유?
    Rollback segment는 dynamic하게 allocate되고, 더 이상 필요 없게 되었을 때
    (만약, Optimal parameter가 셋팅되어 있으면) 모두 commit된 extent에
    대해서는 optimal size 만큼만 남기고 release(deallocate)된다.
    Rollback segment가 적은 수의 extent를 가질 수록, space 할당/해제 시
    extent 수가 많을 때보다 큰 사이즈의 space가 할당되고, 해제된다.
    다음과 같은 예를 들어 보자.
    200M 정도의 rollback segment가 있는데, 100M 짜리 2개의 extent로 이루어져
    있다고 가정해보자. 이 rollback segment에 추가로 space를 할당해야 할 일이
    생겼을 때, 모든 rollback segment extent는 같은 크기를 가져야 한다는 점을
    감안할 때, 100M 짜리 extent를 하나 더 할당해야 할 것이다.
    이 결과 직전의 rollback segment 크기에 비하여 50% 만큼의 크기 증가분이
    생겨나게 된 것인데, 실제 필요로 하는 space보다 더 많은 space가 할당되었을
    것이다.
    이와 반대로, 10M 짜리 extent 20개로 구성된 200M 짜리 rollback segment를
    생각해보자.
    여기에 추가로 space를 할당해야 할 일이 생겼을 때, 10M 짜리 extent 하나만
    추가되면 되는 것이다.
    Rollback segment가 20개 또는 그 이상의 extent로 구성되어 있다면 extent가
    하나 더 증가할 경우가 생겼을 때, rollback segment의 전체 크기가 5% 이상은
    늘어나지 않는다는 것이다.
    즉, space의 할당과 해제 작업이 보다 유연하고 쉽게 일어날 수 있다.
    요약하면, rollback segment의 extent 갯수를 20 이상으로 잡으면 space
    할당과 해제가 "보다" 수월해진다.
    실제로 extent 갯수를 20 이상으로 잡았을 때, 처리 속도가 훨씬 빨라진다는
    사실이 많은 테스트 결과 밝혀졌다.
    한가지 확실한 사실은, space를 할당하고 해제하는 작업은 cost가 적게 드는
    작업이 아니라는 사실이다.
    실제로 extent가 할당/해제되는 작업이 일어날 때, performance가 저하되는
    일이 발생한다는 것이다.
    Extent 하나에 대한 cost는 별 문제가 안 된다고 할지라도, rollback segment
    는 끊임없이 space를 할당하고 해제하는 작업을 반복하기 때문에 작은 크기의
    extent를 갖는 것이 cost 측면에서 훨씬 효율적이라는 결론이다.
    Rollback Segment의 Optimal storage parameter와 Shrink
    Optimal은 deallocate 시에 rollback segment 내에 optimal size 만큼의
    extents를 유지하기 위해 사용하는 rollback segment storage parameter이다.
    다음과 같은 명령으로 사용한다.
    alter rollback segment r01 storage (optimal 1m);Optimal size는 storage 절 안에서 기술되어야 한다.
    Optimal size 이상이 되면, 모두 commit된 extent에 대해서는 optimal size
    만큼만 남기고 release된다.
    즉, optimal에서 지정한 크기 만큼만 rollback segment를 유지하겠다는
    뜻이며, 일정한 크기로 늘어났다가 다음번 tx이 해당 rbs를 취할 경우
    optimal size만큼 resize하는 option이다.
    rbs의 가장 최근에 사용된 extent가 다 차서 다른 extent를 요구할 때
    이 optimal size와 rbs size를 비교하게 되며, 만약 rbs size가 더 크다면
    active tx에 관여하지 않는 tail extent에 대하여 deallocation이 이루어진다.
    특정 rollback segment가 너무 큰 space를 차지해서 다른 rollback segment가
    extent를 발생할 수 있는 여유 공간을 부족하게 만들기 때문에 이를 극복하기
    위해서 optimal size를 지정할 필요가 있다.
    즉, optimal parameter를 지정하면 space availability 측면에서 효율적이다.
    다음과 같이 shrink 명령을 수행하는데, size를 지정하지 않으면 optimal
    size 만큼 shrink된다.
    alter rollback segment [rbs_name] shrink to [size];Shrink 명령 수행 후, 바로 줄어들지 않는 경우가 있는데,
    transaction이 있는 경우는 줄어들지 않고, transaction이 종료되면 줄어든다.
    Optimal이 적용되는 시간은 session이 빠져 나가고 약 5~10 분 정도 걸린다.
    적당한 OPTIMAL SIZE?
    => 20 ~ 30 extents 정도가 적당한데, batch job의 성격에 따라 size는 달라
    지며 각 optimal의 합이 datafile의 size를 넘어도 전혀 상관없다.
    Optimal size를 initial, next와 같게 주면 extent가 발생하는 매번 shrink가
    일어나므로 좋지 않다.
    RBS들의 평균 크기를 구하여 이것을 optimal 크기로 지정하여 사용하는 것을
    권한다.
    다음의 query를 이용하여 peak time에 rollback segment들의 평균 크기를 구한다.
    select initial_extent + next_extent * (extents-1) "Rollback_size", extents
    from dba_segments
    where segment_type ='ROLLBACK';
    이 크기의 평균값(bytes)을 rollback segment들의 optimal size로 사용할 수
    있다.
    주의할 사항은 너무 자주 shrink된다거나 optimal 값을 너무 작게 주면
    ora-1555 : snapshot too old error가 발생할 확률이 높아지므로,
    사용하지 않는 것이 좋을 수도 있고, 되도록 큰 값으로 셋팅해야 한다.
    Rollback segment의 optimal size를 확인할 수 있는 view는 V$ROLLSTAT
    이라는 dynamic view로서 OPTSIZE column에서 확인이 가능하다.
    Example
    none
    Reference Documents
    <Note:69464.1>

  • Rollback segment  creation problem

    When i try to create rollback segment on oracle 9iRelease2 database in linux operating system, i got the following error, ORA-30019: Illegal rollback Segment operation in Automatic Undo mode.
    I have already modified Undo_management as manual in init file.
    How can i solve this problem?
    Thanks

    In SQL*Plus, can you check what your undo_management is set to, just to verify that it is picking up the change?
    show parameter undo_managementJustin
    Distributed Database Consulting, Inc.
    www.ddbcinc.com/askDDBC

  • Datafile containing rollback segment crashed

    Hi,
    In one of our production box (oracle 8.1.7.4 and HP UX), datafile containing rollback segment crashed. To open the database, i commented rollback segment line in init file and started the db and brought the crashed datafile to offline for dropping as
    alter database datafile '/db10/rollback/rbs01.dbf' offline drop;
    and then tried to drop the tablespace containing that datafile but it threw an error saying an active rollback segment R0 is still there in the tablespace. I donot know how to drop this and create new rollback segments. Any help would be greatly appreciated.
    Thanks
    Guna

    Hi,
    Serious case. In case of a failure the instance recovery is automatic but the rollback segments are needed. Having the database open does not mean everything is OK. Just read that :
    Crash or instance recovery consists of the following steps:
    +# Rolling forward to recover data that has not been recorded in the datafiles, yet has been recorded in the online redo log, including the contents of rollback segments. This is called cache recovery.+
    +# Opening the database. Instead of waiting for all transactions to be rolled back before making the database available, Oracle allows the database to be opened as soon as cache recovery is complete. Any data that is not locked by unrecovered transactions is immediately available.+
    +# Marking all transactions system-wide that were active at the time of failure as DEAD and marking the rollback segments containing these transactions as PARTLY AVAILABLE.+
    +# Rolling back dead transactions as part of SMON recovery. This is called transaction recovery.+
    +# Resolving any pending distributed transactions undergoing a two-phase commit at the time of the instance failure.+
    +# As new transactions encounter rows locked by dead transactions, they can automatically roll back the dead transaction to release the locks. If you are using Fast-Start Recovery, just the data block is immediately rolled back, as opposed to the entire transaction.+
    What did you do exactly after the crash ? Can you post commands/output + last 50-100 lines of your alert.log ?
    Best regards
    Phil

  • Cannot use system rollback segment for non-system tablespace 'TEMP

    Hi everyone!
    I encountered this error: "Cannot use system rollback segment for non-system tablespace 'TEMP"
    So this is what I did to check if the undo stuffs are online.
    SQL> select tablespace_name,status from dba_tablespaces;
    TABLESPACE_NAME                STATUS
    SYSTEM                         ONLINE
    UNDO                           ONLINE
    SYSAUX                         ONLINE
    TEMP                           ONLINE
    LARGEDATA                      ONLINE
    LARGEINDEXES                   ONLINE
    MEDIUMDATA                     ONLINE
    MEDIUMINDEXES                  ONLINE
    SMALLDATA                      ONLINE
    SMALLINDEXES                   ONLINE
    XSMALLDATA                     ONLINE
    TABLESPACE_NAME                STATUS
    XSMALLINDEXES                  ONLINE
    XXSMALLTABS                    ONLINE
    USERS                          ONLINE
    CONVTABLES                     ONLINE
    UNDO_02                        ONLINE
    16 rows selected.
    SQL>  SELECT tablespace_name, sum((bytes/1024)/1024) free FROM DBA_FREE_SPACE gr
    oup by tablespace_name;
    TABLESPACE_NAME                      FREE
    LARGEDATA                      18.3105469
    SMALLDATA                        10.46875
    SYSAUX                           106.5625
    UNDO_02                            67.125
    XXSMALLTABS                    13.0078125
    CONVTABLES                     170.039063
    MEDIUMDATA                             22
    USERS                           37.265625
    SYSTEM                             55.875
    LARGEINDEXES                   30.5175781
    XSMALLINDEXES                    17.34375
    TABLESPACE_NAME                      FREE
    UNDO                             546.9375
    MEDIUMINDEXES                       33.25
    SMALLINDEXES                    31.015625
    XSMALLDATA                     23.6328125
    15 rows selected.
    SQL> select file#,status from v$datafile;
         FILE# STATUS
             1 SYSTEM
             2 ONLINE
             3 ONLINE
             4 ONLINE
             5 ONLINE
             6 ONLINE
             7 ONLINE
             8 ONLINE
             9 ONLINE
            10 ONLINE
            11 ONLINE
         FILE# STATUS
            12 ONLINE
            13 ONLINE
            14 ONLINE
            15 ONLINE
    15 rows selected.
    SQL> select segment_name, tablespace_name, initial_extent,status
      2  from dba_rollback_segs;
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    SYSTEM                         SYSTEM                                 102400
    ONLINE
    _SYSSMU1$                      UNDO                                   131072
    OFFLINE
    _SYSSMU2$                      UNDO                                   131072
    OFFLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU3$                      UNDO                                   131072
    OFFLINE
    _SYSSMU4$                      UNDO                                   131072
    OFFLINE
    _SYSSMU5$                      UNDO                                   131072
    OFFLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU6$                      UNDO                                   131072
    OFFLINE
    _SYSSMU7$                      UNDO                                   131072
    OFFLINE
    _SYSSMU8$                      UNDO                                   131072
    OFFLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU9$                      UNDO                                   131072
    OFFLINE
    _SYSSMU10$                     UNDO                                   131072
    OFFLINE
    _SYSSMU11$                     UNDO_02                                131072
    OFFLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU12$                     UNDO_02                                131072
    OFFLINE
    _SYSSMU13$                     UNDO_02                                131072
    OFFLINE
    _SYSSMU14$                     UNDO_02                                131072
    OFFLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU15$                     UNDO_02                                131072
    OFFLINE
    _SYSSMU16$                     UNDO_02                                131072
    OFFLINE
    _SYSSMU17$                     UNDO_02                                131072
    OFFLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU18$                     UNDO_02                                131072
    OFFLINE
    _SYSSMU19$                     UNDO_02                                131072
    OFFLINE
    _SYSSMU20$                     UNDO_02                                131072
    OFFLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU21$                     UNDO_02                                131072
    OFFLINE
    22 rows selected.How should I be bringing them online?
    I tried this but didn't work for me.
    SQL> alter rollback segment _SYSSMU1$ online;
    alter rollback segment _SYSSMU1$ online
    ERROR at line 1:
    ORA-00911: invalid character
    SQL> alter rollback segment '_SYSSMU1$' online;
    alter rollback segment '_SYSSMU1$' online
    ERROR at line 1:
    ORA-02245: invalid ROLLBACK SEGMENT name
    SQL> alter rollback segment _SYSSMU21$ online;
    alter rollback segment _SYSSMU21$ online
    ERROR at line 1:
    ORA-00911: invalid character
    SQL> alter rollback segment SYSSMU21$ online;
    alter rollback segment SYSSMU21$ online
    ERROR at line 1:
    ORA-01534: rollback segment 'SYSSMU21$' doesn't exist
    SQL> alter rollback segment '_SYSSMU21$' online;
    alter rollback segment '_SYSSMU21$' online
    ERROR at line 1:
    ORA-02245: invalid ROLLBACK SEGMENT name
    SQL> alter rollback segment "_SYSSMU21$" online;
    alter rollback segment "_SYSSMU21$" online
    ERROR at line 1:
    ORA-30017: segment '_SYSSMU21$' is not supported in MANUAL Undo Management mode
    SQL> ALTER SYSTEM SET UNDO_MANAGEMENT=AUTO SCOPE=SPFILE;
    System altered.Should I be bringing every segment online separately? Please guide me.
    Nith
    Edited by: user645399 on Feb 23, 2011 2:52 PM

    SQL> select segment_name, tablespace_name, initial_extent,status
      2  from dba_rollback_segs;
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    SYSTEM                         SYSTEM                                 102400
    ONLINE
    _SYSSMU1$                      UNDO                                   131072
    ONLINE
    _SYSSMU2$                      UNDO                                   131072
    ONLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU3$                      UNDO                                   131072
    ONLINE
    _SYSSMU4$                      UNDO                                   131072
    ONLINE
    _SYSSMU5$                      UNDO                                   131072
    ONLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU6$                      UNDO                                   131072
    ONLINE
    _SYSSMU7$                      UNDO                                   131072
    ONLINE
    _SYSSMU8$                      UNDO                                   131072
    ONLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU9$                      UNDO                                   131072
    ONLINE
    _SYSSMU10$                     UNDO                                   131072
    ONLINE
    _SYSSMU11$                     UNDO_02                                131072
    OFFLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU12$                     UNDO_02                                131072
    OFFLINE
    _SYSSMU13$                     UNDO_02                                131072
    OFFLINE
    _SYSSMU14$                     UNDO_02                                131072
    OFFLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU15$                     UNDO_02                                131072
    OFFLINE
    _SYSSMU16$                     UNDO_02                                131072
    OFFLINE
    _SYSSMU17$                     UNDO_02                                131072
    OFFLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU18$                     UNDO_02                                131072
    OFFLINE
    _SYSSMU19$                     UNDO_02                                131072
    OFFLINE
    _SYSSMU20$                     UNDO_02                                131072
    OFFLINE
    SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT
    STATUS
    _SYSSMU21$                     UNDO_02                                131072
    OFFLINEStill undo_02's segments are offline.

  • ROLLBACK SEGMENTS OPERATION

    Hello Everyone
    This is the first time I am a forum member and I'm figuring out how it works because I have a very big problem
    Look, I'm a support engineer and, as you know, the code of the application is not own by me.
    Three weeks ago I received a report which is related with the Rollback operation.
    There's a process which delete old data from my database and, normally, this process has three parts, as shown in the alert_dbinstance.log:
    Wed May 17 03:00:08 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE
    Wed May 17 03:00:08 2000
    Completed: alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE
    Wed May 17 04:52:25 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 SHRINK
    Wed May 17 04:52:26 2000
    Completed: alter ROLLBACK SEGMENT CLEANUP_RS0 SHRINK
    Wed May 17 04:52:26 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 OFFLINE
    Completed: alter ROLLBACK SEGMENT CLEANUP_RS0 OFFLINE
    But, one day, the server crashed and this process didn't finish:
    Sat May 20 03:00:03 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE
    Sat May 20 03:00:03 2000
    Completed: alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE
    Sat May 20 04:39:09 2000
    the next messages about this process are these:
    Sun May 21 03:00:04 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE
    Sun May 21 03:00:04 2000
    ORA-1636 signalled during: alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE...
    Sun May 21 03:10:10 2000
    Thread 1 advanced to log sequence 303
    Current log# 1 seq# 303 mem# 0: /usr/users/fraude/dblinks/redo_db/dbfraude_log0.dbf
    Sun May 21 03:11:48 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 SHRINK
    Sun May 21 03:11:49 2000
    Completed: alter ROLLBACK SEGMENT CLEANUP_RS0 SHRINK
    Sun May 21 03:11:49 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 OFFLINE
    Completed: alter ROLLBACK SEGMENT CLEANUP_RS0 OFFLINE
    Since this day, the delete process sends this message:
    --- Fault (4) Notify (3) : 2000-06-01 03:00:01 ---
    Message (400020): Database Operation Failed
    Partition: 0
    Module (13000): Daily Cleanup
    Description: ORA-00955: name is already used by an existing object
    My question here is : Is there a way, using oracle, to identify this object? Can I find the objects with a failure register in a table? in a log file?
    thanks for your comments and your efforts. I'll be very thankful.
    null

    It seems you should look here:
    ORA-1636 signalled during: alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE...
    Looks like you have ORA-01636 error:
    rollback segment 'string' is already online
    I suggest you check Oracle documentation about this error. Seems to me your process try to access rollback segment that is already in use.
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by German Garcia Ibarra ([email protected]):
    [b]Hello Everyone
    This is the first time I am a forum member and I'm figuring out how it works because I have a very big problem
    Look, I'm a support engineer and, as you know, the code of the application is not own by me.
    Three weeks ago I received a report which is related with the Rollback operation.
    There's a process which delete old data from my database and, normally, this process has three parts, as shown in the alert_dbinstance.log:
    Wed May 17 03:00:08 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE
    Wed May 17 03:00:08 2000
    Completed: alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE
    Wed May 17 04:52:25 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 SHRINK
    Wed May 17 04:52:26 2000
    Completed: alter ROLLBACK SEGMENT CLEANUP_RS0 SHRINK
    Wed May 17 04:52:26 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 OFFLINE
    Completed: alter ROLLBACK SEGMENT CLEANUP_RS0 OFFLINE
    But, one day, the server crashed and this process didn't finish:
    Sat May 20 03:00:03 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE
    Sat May 20 03:00:03 2000
    Completed: alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE
    Sat May 20 04:39:09 2000
    the next messages about this process are these:
    Sun May 21 03:00:04 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE
    Sun May 21 03:00:04 2000
    ORA-1636 signalled during: alter ROLLBACK SEGMENT CLEANUP_RS0 ONLINE...
    Sun May 21 03:10:10 2000
    Thread 1 advanced to log sequence 303
    Current log# 1 seq# 303 mem# 0: /usr/users/fraude/dblinks/redo_db/dbfraude_log0.dbf
    Sun May 21 03:11:48 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 SHRINK
    Sun May 21 03:11:49 2000
    Completed: alter ROLLBACK SEGMENT CLEANUP_RS0 SHRINK
    Sun May 21 03:11:49 2000
    alter ROLLBACK SEGMENT CLEANUP_RS0 OFFLINE
    Completed: alter ROLLBACK SEGMENT CLEANUP_RS0 OFFLINE
    Since this day, the delete process sends this message:
    --- Fault (4) Notify (3) : 2000-06-01 03:00:01 ---
    Message (400020): Database Operation Failed
    Partition: 0
    Module (13000): Daily Cleanup
    Description: ORA-00955: name is already used by an existing object
    My question here is : Is there a way, using oracle, to identify this object? Can I find the objects with a failure register in a table? in a log file?
    thanks for your comments and your efforts. I'll be very thankful.
    <HR></BLOCKQUOTE>
    null

  • Create rollback segment

    Anyone knows why I can not create rollback segment in 9i?? I
    used same script in 8i and it works.
    "create rollback segment lims_rollback tablespace lims_rollback;"
    ERROR at line 1:
    ORA-30019: Illegal rollback Segment operation in Automatic Undo
    mode
    what is automatic Undo mode???

    Automatic undo mode is the default behavior in Oracle 9i where
    Oracle server itself manages creation/sizing etc of rollback
    segments. I believe if you want to do it the old 8i/8/7.x way,
    you need to change some parameter to not use Automatic Undo

  • ORA-01555: snapshot too old: rollback segment number 6 with name "R05" too

    Can someone please help me how to overcome this dreaded ORA-01555 and how to know what exactly is causing this. There can be number of reasons this can occur :
    1. Fewer and smaller rollback segments for a very actively changing database
    2. Corrupted rollback segment
    3. Fetch across commit
    4. Fetch across commits with delayed block clean out
    Thanks

    http://asktom.oracle.com/pls/ask/f?p=4950:8:802460143396322798::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:275215756923
    <quote source="asktom">
    the only CAUSE of a 1555 is improperly sized rollback segments.
    </quote>
    http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:275215756923#10100046218454
    Message was edited by:
    Kamal Kishore

  • ORA-01555: snapshot too old: rollback segment number 3 with name "_SYSSMU3$

    A Materalized view is scheduled to update every 12 hours . When it has tried to update it has thrown the error ...
    ORA-12008: error in materialized view refresh path
    ORA-01555: snapshot too old: rollback segment number 3 with name "_SYSSMU3$"
    too small
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 803
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 860
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 841
    ORA-06512: at line 1

    Hi,
    Can you increase the size of the UNDO Tablespace ?
    For more information, you can find on this link below:
    http://forums.oracle.com/forums/search.jspa?threadID=&q=ORA-01555&objID=c84&dateRange=all&userID=&numResults=15
    Cheers

  • ORA-01581: attempt to use rollback segment...

    We've started getting "ORA-01581: attempt to use rollback segment (31) new extent (3) which is being allocated" messages in our production database over the last couple of days. Of course, each time we get these the rollback segment number is different, and we are getting these randomly from different applications that connect to the same database. We are using automatic undo management, so the rollback segments are not really under our control. The action in the Oracle docs for this error message doesn't give any specific actions that we should take, but we continue to get these.
    We started to get these about the same time as we ran out of available sessions on the database (sessions = 1500 and we had 1500 open sessions). Could these be related? Could there be some open session that may be causing the rollback segment issue? Would a restart of the database fix this? Of course the max sessions issue was cleaned up two days ago but the rollback segment issue is a lingering problem.
    Any help would be appreciated. We couldn't find anything for this online and Oracle hasn't responded to our service request yet.
    Thanks,
    Bobby

    As I understand it, you can not explicitly set the size for the undo segments in automatic undo management mode. From the Concepts guide:
    "In automatic undo management mode, the system controls exclusively the assignment of transactions to undo segments, and controls space allocation for undo segments."
    It looks like we are also using the default storage options that are set when the UNDO tablespace was created. Here is the DDL used to create this tablespace:
    CREATE SMALLFILE UNDO TABLESPACE "UNDOTBS" DATAFILE '/alpha/oradata/prod01/undotbs01.dbf' SIZE 750M REUSE AUTOEXTEND ON NEXT 25600K MAXSIZE 2000M , '/alpha/oradata/prod01/undotbs03.dbf' SIZE 2000M REUSE AUTOEXTEND ON NEXT 51200K MAXSIZE 2000M , '/alpha/oradata/prod01/undotbs04.dbf' SIZE 2000M REUSE AUTOEXTEND ON NEXT 104K MAXSIZE 2000M , '/alpha/oradata/prod01/undotbs02.dbf' SIZE 2000M REUSE AUTOEXTEND ON NEXT 25600K MAXSIZE 2000M

  • Rollback segment error ORA-1628

    Hellow
    Currently we are working on Oracle 8i database.The database contain spatial data around 10GB.We have a tablespace RBS containing 4 rollback segments. The issue is whenever we try to insert spatial data we get this error message (in the alert file)
    ORA-1628: max # extents 121 reached for rollback segment R01
    Failure to extend rollback segment 2 because of 1628 condition
    FULL status of rollback segment 2 cleared.
    I extended the size of RBS tablespace by adding another datafile, but still it doesn't help.
    Also i found that RBS tablespace is marked as PERMANENT...it means the rollback data does not get flushed out periodically?Also Should this tablespace be temporary? How can i counter this problem?
    Regards
    Sam

    Hi,
    01628, 00000, "max # extents (%s) reached for rollback segment %s"
    // *Cause:  An attempt was made to extend a rollback segment that was
    //          already at the MAXEXTENTS value.
    // *Action: If the value of the MAXEXTENTS storage parameter is less than
    //          the maximum allowed by the system, raise this value. => Alter your RBS and allow more than 121 extents to be created in this RBS.
    Also i found that RBS tablespace is marked as PERMANENT.Yes, it's normal.
    ..it means the rollback data does not get flushed out periodically?No
    Also Should this tablespace be temporary? No, this can't be
    How can i counter this problem?Free advise: RTFM about Rollback Segments! Start here (8i doc) or read the Concepts book.
    Regards,
    Yoann.

  • ORA-1650: unable to extend rollback segment

    Hi,
    We have 20 RBS's and in our production instance we got very frequent alerts related to ORA-1650: unable to extend rollback segment continuously. When I looked for select STATUS from v$rollstat; I could see most of them are with FULL status. after couple of hours they disappeared and status became online.
    How to avoid these type of alerts?
    REgards

    What version of Oracle?
    If you are 9ir2 or later, you should be going to automatic undo management. Though it won't help your 'we cannot add space' restriction. That's not an Oracle problem, that's a corporate issue.
    This problem may be caused by poor transaction design with too many processing doing too infrequent commits. That's not an Oracle problem either, that's a corporate/development issue.
    So...you don't have an Oracle problem.
    You can't stop the 1650s from occurring if you are unwilling to add space or address application issues. However, you can set up an email filter so that any emails containing ORA-01650 in the header or body get automatically sent to the trash.
    <sarcasm>
    If you can't solve a problem, then just ignore it!
    </sarcasm>

Maybe you are looking for