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

Similar Messages

  • Illegal rollback Segment operation in Automatic Undo mode

    Hi,
    I use oracle database 9.2.0.1 and I try to install SCM repository but when I run ckcreate I saw an error message in
    the log file that Illegal rollback Segment operation in Automatic Undo mode because oracle 9.2 use automatic undo mode .So how can i install the repository.
    Ghassan Hallaq

    ORA-30019: Illegal rollback Segment operation in Automatic Undo mode
    You have hit bug '2108361'. I think you could safely ignore it in your case.

  • 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

  • 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

  • When to backup the rollback segments?

    Does anyone know when do I need to backup the rollback segments and what for? How are they used during restore/recovery?
    I'm using RMAN in Oracle 9.2. We have databases with both manual and automatic undo management. Does the undo management type make any difference?
    Thanks,
    Niki

    Does anyone know when do I need to backup the rollback segments and what for? How are they used during restore/recovery?
    Your question is a little large to answer but I am going to summary the most important.
    The database works with transactions in commit and in not commit mode. While a transaction has not commit , this transaction has not finished. While the transaction has not finished the rollback segments or undo segments are used to store the image of blocks with changes and without changes. That is the method that Oracle uses to ensure that a block is not going to be modified definitevely until the transaction gets commit.
    When you have a point of failure you are going to have transactions with commit and transactions with no commit and that tablespace ( RBS or UNDO ) is needed to carry to the database to a consistent point carrying to disk all transactions with commit and the rest have to suffer a rollback operation. That means that those operations without commit are not going to be complete transactions for the database.
    When you want to recover a database all tablespaces are need excepting the temp tablespace because that tablespace is only needed to carry out sorts and operation likeness.
    Does the undo management type make any difference?
    if you use rollback segments you have to administer them and the management instead if you work with undo tablespace. If you work with undo tablespace it by itself manage its segments you do not have to worry about.
    I think that I have answered your questions if you have any doubt or something like that feel free to follow asking.
    Good Luck!
    Joel P�rez

  • Alter rollback segment command giving error.

    Hi all ,
    i am novice to Oracle 9i i am altering rollback segment but getting following error messages.
    ORA-30021: Operation not allowed on Undo Tablespace
    ORA-25150:Altering of extent parameters not permitted
    (in this i am trying to alter maxextents parameter of rollback segment )

    Apparently you are using undo segments, as opposed to rollback segments.
    You should use undo segments, and they are located in a separate undo tablespace (see the first error message)
    Oracle manages the undo tablespace. You can't do anything about it.
    However, Oracle is still using 'rollback segment' and 'undo segment' interchangeably.
    Likely, your rollback segment is an undo segment, and you can not change it, nor do you need to.
    Sybrand Bakker
    Senior Oracle DBA

  • Rollback segments - database logging

    Got a problem...
    We are trying to move data from one database to another using: INSERT INTO table1 (SELECT a,b,c FROM table2@db2). The problem we are having is that the amount of data being moved with this in sert command is too great - we are getting an error indicating that our rollback segment is not large enough - ORA-01562: failed to extend rollback segment number 4.
    Unfortunately, we are not going to be able to increase the size of the rollback segment any further than we already have. Is there a way to disable the database logging that occurs?
    I tried using INSERT INTO table1 dbms_disable_logging (SELECT a,b,c FROM table2@db2), but noticed no difference - same error.
    Any ideas?
    Thank you,
    Dan

    We use select..into all the time in an unlogged mode for speed and rollback space reasons.
    We replicate fifty million row tables with a minimal amount of rollback segment (<50MB).
    In unlogged mode we can replicate 50 million rows in under forty minutes - that's smokin!
    Oracle version 8 or greater introduced this concept. I am running 8.1.6.
    You need to alter the table to disable logging and then perform the select into.
    The table alter only takes seconds.
    ALTER TABLE IDMDBO.DIM_PLANS NOLOGGING
    Then do the select into and then turn logging back on (if so desired).
    You can also disable logging at the table space level.
    Keep in mind there are only a few database operations that can be performed unlogged and select..into is one of them.
    There is currently no way to carte blanche disable transaction logging - hopefully this will be coming soon!
    Cheers.
    - Brendan Sullivan
    null

  • Rollback segment for index creation

    Hi,
    I want to assign a specific (big) rollback segment to the transactions used by InterMedia Text while creating the index.
    However a 'SET TRANSACTION USE ROLLBACK SEGMENT create_index' directly before the 'CREATE INDEX ...' seems not to work, as I saw that the inserts performed by InterMedia Text (e.g. into the $i and $k tables) were done using other rollback segments (e.g. RBSxx).
    Is there any way to InterMedia Text to tell which rollback segments it should use for its internal operation?
    Cheers,
    Johannes

    we can't assign the rollback segment to particular user.
    For better performance place different table
    spaces in different disks.
    by
    ramana
    null

  • Export backup failing with ORA-1555snapshot too old: rollback segment ERROR

    DB version =8.1.7.4
    OS=Solaris =5.10.
    I know this is outdated. But still we are supporting this version of database.
    We are facing ORA-1555 error daily when we are running the export backup of database. Consistent parameter is set to N .
    I needed to know why export uses rollback segments during export operation. even though CONSISTENT parameter is N.
    Thanks,
    Edited by: ahshivap on Dec 12, 2012 5:19 AM

    Hi,
    Consistent=y just mean the tables are consistent with each other. Oracle still has to guarantee that each individual table is at least consistent with itself. That's your issue.
    Regards,
    Harry

  • Corrupted ROLLBACK segment

    Hi,
    on 8.1.7 I have the following in alertlog :
    Errors in file u:\oradata\MYDB\bdump\MYDBSMON.TRC:
    ORA-01578: ORACLE data block corrupted (file # 2, block # 348131)
    ORA-01110: data file 2: 'T:\ORADATA\MYDB\01_RBS_01.DBF'
    Can I drop this file and add another to ROLLBACK tablespace ?
    If not any other solution ?
    Many thanks.

    It depends, if your rollback segment is required to perform a recovery action, then it is not possible.
    If you have your database configured in archivelog mode and your backup is valid, then simply perform a complete recovery operation with the rollback tablespace. Otherwise you will have to perform a procedure that involves declaring the rollback segments unavailable by declaring this instance parameter:
    offlinerollback_segments=RBS01, RBS02, RBS03, RBS04, RBS05, RBS06, RBS07, RBS08, RBS09, RBS10
    rollback_segments=SYSTEM, SYSROL
    (depending on the rollback segments you have declared in this tablespace).
    I have documented the procedure here --> Re: Error while Droping Undo Tablespace.
    ~ Madrid
    http://hrivera99.blogspot.com/

  • ORA-01555 Snapshot too old, rollback segment  too small after flashback tab

    Hello
    Further to an update on a table in database, I realize that I have done an error and I want to come back in the state of table before this operation.
    For this I use 'Flashback table' as this command :
    flashback table 'table_name' to timestamp to_timestamp('2010-11-08 08:00:00 AM','YYYY-MM-DD HH:MI:SS PM')
    and I get this error :
    ORA-01555 :Snapshot Too Old rollback segment N° x , "_SYSSMU9$", too small
    What I can do to not have this problem ? can I avoid it ?
    Please helps .
    Regards
    Edited by: 794982 on 12 nov. 2010 05:05
    Edited by: 794982 on 12 nov. 2010 05:05
    Edited by: 794982 on 12 nov. 2010 05:06

    To set the undo retention period:
    Do one of the following:
    • Set UNDO_RETENTION in the initialization parameter file.
    UNDO_RETENTION = 1800
    • Change UNDO_RETENTION at any time using the ALTER SYSTEM statement:
    ALTER SYSTEM SET UNDO_RETENTION = 2400;
    The effect of an UNDO_RETENTION parameter change is immediate, but it can only be honored if the current undo tablespace has enough space.
    For more reference.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/undo.htm

  • Transaction table in rollback segments

    hi guys,
    I have read the following, but am still having a little difficulty conceptualising. Would someone be kind enough to give me a very brief example?
    thanks
    For each rollback segment, Oracle maintains a transaction table--a list of all transactions that use the associated rollback segment and the rollback entries for each change performed by these transactions.

    First of all, the statement is talking about old manual undo management using rollback segment.
    If you check the preceding two paragraph of the statement then it's easier to understand,
    It basically says, Rollback segment hold rollback entries of transaction. To make it easier to track transactions and undo entries, Oracle maintain a table to save such info.
    Rollback segment , transaction and undo entries are one to many relationships.
    Rollback Segment --< Transactions --< Undo Entries
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96524/b_deprec.htm
    Contents of a Rollback Segment
    Information in a rollback segment consists of several rollback entries. Among other information, a rollback entry includes block information (the file number and block ID corresponding to the data that was changed) and the data as it existed before an operation in a transaction. Oracle links rollback entries for the same transaction, so the entries can be found easily if necessary for transaction rollback.
    Neither database users nor administrators can access or read rollback segments. Only Oracle can write to or read them. (They are owned by the user SYS, no matter which user creates them.)
    How Rollback Entries Are Logged
    Rollback entries change data blocks in the rollback segment, and Oracle records all changes to data blocks, including rollback entries, in the redo log. This second recording of the rollback information is very important for active transactions (not yet committed or rolled back) at the time of a system crash. If a system crash occurs, then Oracle automatically restores the rollback segment information, including the rollback entries for active transactions, as part of instance or media recovery. When recovery is complete, Oracle performs the actual rollbacks of transactions that had been neither committed nor rolled back at the time of the system crash.
    When Rollback Information Is Required
    For each rollback segment, Oracle maintains a transaction table--a list of all transactions that use the associated rollback segment and the rollback entries for each change performed by these transactions. Oracle uses the rollback entries in a rollback segment to perform a transaction rollback and to create read-consistent results for queries.

  • Set rollback segment

    Hi,
    Is it possible in OWB to set the rollback segment that owb must use for e certain mapping?

    You can define a pre-map trigger (use the Post Mapping Process operator within a map) which is a PLSQL function/procedure that sets the rollback segment for the transaction;
    SET TRANSACTION USE ROLLBACK SEGMENT RBS_ONE;
    This goes for other custom initialization code too.
    Cheers
    David

  • Creating rollback segments

    I would like to know how to create the perfect rollback segments.
    I currently have a database that is up and running, but I feel that the rollback segments, are not running at there best.
    I know that the minextents should be set to 20 extents, inital and next are to be the same, but I don't know what the best optimal figure should be.
    Looking at the view $waitstat, "undo header" is at a non-zero figure, so this has prompted me to re-configure the rollback segments. Currently the highest HWMSIZE is 45m, and the highest AVEACTIVE is 3m.
    Can anyone help?

    Hi
    ORA-01552: cannot use system rollback segment for non-system tablespace &apos;string&apos;
    Cause: An attempt was made to use the system rollback segment for operations involving non-system tablespace. If this is a clone database then this will happen when attempting any data modification outside of the system tablespace. Only the system rollback segment can be online in a clone database.
    Action: Create one or more private/public segment(s), shut down and restart. May need to modify the initialization parameter ROLLBACK_SEGMENTS to acquire private rollback segment. If this is a clone database being used for tablespace point in time recovery then this operation is not allowed.
    Hope this helps
    -Aditi

  • Why Oracle10g uses System Rollback Segment....????

    Hi ,
    Just a wonder....!!!!
    Why Oracle10g uses System Rollback Segment....and not System undo tablespace... since rollback segment as a method to rollback transactions has been depreciated.....?????
    Thanks.....
    Sim

    System Rollback Segment is reserved for Oracle internal operation.
    I believe it is used only by SYS and programs invoked using SYS authorization manipulating dictionary tables. In which case the complexity has been understood and managed over several generations of Oracle.
    I suspect the system (manual) roillback segment will be very useful when creating a new database, which includes creating whole bunches of tables and views (updating whole bunches of internal tables), at which time no undo segment (or background process for automating that management?) exists.
    Please point to the document or link that says rollback segments are deprecated.
    Even now, manual rollback segments may be of benefit to specific programs and environments that run batch jobs managed by DBA whoy has studied them for a long time under specific circumstances.
    But, just like the various SGA pools should be evaluated and potentially resized when workload changes, the rollback segment configuration needs to be evaluated and potentially resized when workload changes. Few DBAs have the knowledge or skill or time to do so - the automatic adjustments may be the best generic compromise.

Maybe you are looking for