ORA-01552: cannot use no tablespace system rollback segment

Hello

When I try to create a table, I got the following error message.

ORA-01552: cannot use tablespace no system "USER" system rollback segment

Select nom_segment, nom_tablespace, initial_extent, status
of dba_rollback_segs;

NOM_SEGMENT NOM_TABLESPACE INITIAL_EXTENT STATUS
------------------------------ ------------------------------ ---------------------- ----------------
114688 ONLINE SYSTEM
_SYSSMU1$ UNDOTBS1 131072 OFFLINE
_SYSSMU2$ UNDOTBS1 131072 OFFLINE
_SYSSMU3$ UNDOTBS1 131072 OFFLINE
_SYSSMU4$ UNDOTBS1 131072 OFFLINE
_SYSSMU5$ UNDOTBS1 131072 OFFLINE
_SYSSMU6$ UNDOTBS1 131072 OFFLINE
_SYSSMU7$ UNDOTBS1 131072 OFFLINE
_SYSSMU8$ UNDOTBS1 131072 OFFLINE
_SYSSMU9$ UNDOTBS1 131072 OFFLINE
_SYSSMU10$ UNDOTBS1 131072 OFFLINE

11 selected lines

One advises will be useful, thanks

Make sure that the return parameters in your database instance.

SEE THE PARAMETER UNDO

You should have UNDO_MANAGEMENT = "AUTO" and UNDO_TABLESPACE = 'UNDOTBS1.

Hemant K Collette

Tags: Database

Similar Questions

ORA-01552: cannot use tablespac system system rollback segment

Hi all
Environment: database Production: Source
Database dev: target
11203 Version database.
Golden gate Version 11.1
Scheme of the Golden Gate: GGATE
Method of replication. DDL replication is ACTIVE
In my production database my Undo tablespace is corrupted. I changed the management to cancel the manual setting and rebounded from the DB and open editing mode. Then I deleted the undo tablespace data file using in offline mode. Then I opened the database.
SQL > alter database datafile ' / u01/app/oracle/oradata/db1/undotbs01.dbf' drop offline;
Database altered.
Issue.
Now, if I try to let drop the tablespace UNDOTBS1 undo or to create the new database of the undo tablespace throws me error as below:
SQL > drop tablespace undotbs1;
Drop tablespace undotbs1
*
ERROR on line 1:
ORA-00604: an error has occurred at the SQL level 1 recursive
ORA-01552: cannot use system for non-system tablespace «GGATE» rollback segment
ORA-06512: at the level of the line 993
ORA-01552: cannot use system for non-system tablespace «GGATE» rollback segment
Here is the status of rollback segment.
SQL > select nom_segment, dba_rollback_segs State;
NOM_SEGMENT STATUS
------------------------------ ----------------
ONLINE SYSTEM
_SYSSMU10_2490256178$ IN OFFLINE MODE
_SYSSMU9_3593450615$ IN OFFLINE MODE
_SYSSMU8_1909280886$ IN OFFLINE MODE
_SYSSMU7_1924883037$ IN OFFLINE MODE
_SYSSMU6_2460248069$ IN OFFLINE MODE
_SYSSMU5_3787622316$ IN OFFLINE MODE
_SYSSMU4_1455318006$ IN OFFLINE MODE
_SYSSMU3_2210742642$ IN OFFLINE MODE
_SYSSMU2_4228238222$ IN OFFLINE MODE
_SYSSMU1_3138885392$ IN OFFLINE MODE
11 selected lines.
SQL > show Cancel parameter
VALUE OF TYPE NAME
------------------------------------ ----------- ------------------------------
UNDO_MANAGEMENT string MANUAL
UNDO_RETENTION integer 900
undo_tablespace string UNDOTBS1
Please anyone suggest me how to manage this problem.
Kind regards
Rohit

Try this:

Conn / as sysdba

SQL > alter system set _system_trig_enabled = false;

SQL > alter trigger sys.cdc_alter_ctable_before DISABLE.

SQL > alter trigger sys.cdc_create_ctable_after DISABLE.

SQL > alter trigger sys.cdc_create_ctable_before DISABLE.

SQL > alter trigger sys.cdc_drop_ctable_before DISABLE.

create undo tablespace, you could do now:

SQL > create undo tablespace undotbs2 datafile 'XX/xX/XXX/XXX/undotbs2.dbf' size XM autoextend on;

SQL > alter system set undo_tablespace = undotbs2 scope = both;

allow them once again:

SQL > alter trigger sys.cdc_alter_ctable_before ENABLE;

SQL > alter trigger sys.cdc_create_ctable_after ENABLE;

SQL > alter trigger sys.cdc_create_ctable_before ENABLE;

SQL > alter trigger sys.cdc_drop_ctable_before ENABLE;

SQL > alter system set _system_trig_enabled = TRUE;

Restart the system.

ORA-01552: cannot use rollback for non-system tablespace system segment

I'm getting following error, according to a previous thread under request.

ORA-01552: cannot use rollback for non-system tablespace system segment

select SEGMENT_NAME, TABLESPACE_NAME, INITIAL_EXTENT,STATUSfrom dba_rollback_segs
SEGMENT_NAME                   TABLESPACE_NAME                INITIAL_EXTENT         STATUS           
------------------------------ ------------------------------ ---------------------- ---------------- 
SYSTEM                         SYSTEM                         114688                 ONLINE           
_SYSSMU1$                      UNDO_TS                        131072                 OFFLINE          
_SYSSMU2$                      UNDO_TS                        131072                 OFFLINE          
_SYSSMU3$                      UNDO_TS                        131072                 OFFLINE          
_SYSSMU4$                      UNDO_TS                        131072                 OFFLINE          
_SYSSMU5$                      UNDO_TS                        131072                 OFFLINE          
_SYSSMU6$                      UNDO_TS                        131072                 OFFLINE          
_SYSSMU7$                      UNDO_TS                        131072                 OFFLINE          
_SYSSMU8$                      UNDO_TS                        131072                 OFFLINE          
_SYSSMU9$                      UNDO_TS                        131072                 OFFLINE          
_SYSSMU10$                     UNDO_TS                        131072                 OFFLINE          
_SYSSMU11$                     UNDO_TS                        131072                 OFFLINE          
_SYSSMU12$                     UNDO_TS                        131072                 OFFLINE          
_SYSSMU13$                     UNDO_TS                        131072                 OFFLINE          
_SYSSMU14$                     UNDO_TS                        131072                 OFFLINE          

 15 rows selected

How can I get them online, I can get them online does this error?

Maybe you should also mention that you make no effort to look for the error in the documentation online or anywhere else.
You get this when your database uses rollback segments, and you have spaces of multiple tables.
To be able to create spaces of multiple tables, you must first create a rollback segment in the system tablespace.

That's why you get the error.
The resolution is clear.

Unfortunately, 99.9 percent of all the people posting here refused to make any effort to resolve errors.

-----------
Sybrand Bakker
Senior Oracle DBA

RMAN-04014: failed to start: ORA-16019: cannot use LOG_ARCHIVE_DEST_1

Hello
I am facing a problem during the cloning of production TEST environment.
Please see the below given error:
' RMAN-04014: failed to start: ORA-16019: cannot use LOG_ARCHIVE_DEST_1 with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST.
And I used the following script to retrieve.
==========================================================================================
------------------------------------------------------------------
VI initTEST.ora
* .db_name = 'TEST '.
* .db_unique_name = 'TEST '.
SQL > startup nomount
=============================
Auxiliary RMAN.
run
{
allocate auxiliary CHANNEL c1 device type disk;
allocate auxiliary CHANNEL c2 device type disk;
allocate auxiliary CHANNEL c3 device type disk;
allocate auxiliary CHANNEL c4 device type disk;
the value of newname for tempfile 1 to ' / testdata/R12/TEST/datafile/temp01.dbf';
the value of newname for tempfile 2 to ' / testdata/R12/TEST/datafile/temp02.dbf';
the value of newname for tempfile 3 to ' / testdata/R12/TEST/datafile/temp03.dbf';
the value of newname for tempfile 4 to ' / testdata/R12/TEST/datafile/temp04.dbf';
the value of newname for tempfile 5 to ' / testdata/R12/TEST/datafile/temp05.dbf';
data duplicated in the 'TEST' backup location ' / backup/PROD_BKP_01_Nov_15 / '.
SPFILE
Define db_name = 'TEST '.
Set db_unique_name = 'TEST '.
Set cluster_database = "false".
Set use_large_pages = 'false '.
Set remote_listener = "
Set local_listener = "
Set listener_networks = "
Set control_files='/testdata/R12/TEST/controlfile_TEST.ctl"
Set diagnostic_dest ='/ oracle/app /'
Set log_archive_dest = "/ testdata/R12/archive.
Set audit_file_dest='/oracle/app/product/11.1.0/db_1/rdbms/audit/"
Db_file_name_convert '+ DATA_P/PROD/DATAFILE', set ' / testdata/R12/TEST/datafile.
Set log_file_name_convert '+ DATA_P/PROD/ONLINELOG', ' / testdata/R12/TEST/datafile ', '+ RECO_P/PROD/ONLINELOG', ' / testdata/R12/TEST/datafile;
switch tempfile;
}
-----------------------------------------------------------------
Then please suggest a solution?
With thanks and greetings
Ngoyi
------------

This is what Oracle says:

ORA-16019: can't use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST

Cause: One of the following events caused a mismatch:

(1) setting LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the LOG_ARCHIVE_DEST_n specified (n = 1.. 31) or parameter DB_RECOVERY_FILE_DEST occurred during extraction of initialization parameters.

(2) LOG_ARCHIVE_DUPLEX_DEST or LOG_ARCHIVE_DEST parameter was used when an attempt is made to use an ALTER SYSTEM or ALTER SESSION command to set a value for the specified parameter LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST.

(3) a command ALTER SYSTEM ARCHIVE LOG START FOR was in effect when the specified parameter LOG_ARCHIVE_DEST_n met during extraction of initialization parameters.

(4) an ALTER SYSTEM ARCHIVE LOG START FOR order was in effect when an attempt is made to a command ALTER SYSTEM or ALTER SESSION allows you to set a value for the specified parameter LOG_ARCHIVE_DEST_n.

Action: Eliminate all inconsistent parameter definitions.

ORA-19838: cannot use this control file to open the database

Dear all,
While making RMAN cloning, we are facing problem,
SQL > alter database open resetlogs;
ALTER database open resetlogs
*
ERROR on line 1:
ORA-19838: cannot use this control file to open the database
Concerning
Villi Kumar

Dear all,

While checking the database,

Control the name of the database file is PROD

In the instance, database name is TEST.

So we took the PROD and edited control file trace file based on the TEST environment.

Then run the script published in the TEST database trace file.

Now we can open the database by using below command

ALTER database open resetlogs;

Concerning

Villi Kumar

ORA-12032: cannot use column rowid
Hello
8.1.7 I have the following error:
ORA-12032: cannot use the rowid column of materialized view log on 'chain '. "' string '.
The solution is:
Action: A full refresh is necessary before the next quick update. Add columns ROWID in the materialized view log, if necessary.

How can I do a complete refresh before the next fast refresh or ROWID columns add? How do I know whether the ROWID columns add?
Thank you.

PS:
my script is:
................
..............
START WITH TO_DATE (July 6, 2010 17:57:48 "," dd-mon-yyyy hh24:mi:ss')
NEXT SYSDATE + 1/24
user522961 wrote:
Hello
8.1.7 I have the following error:
ORA-12032: cannot use the rowid column of materialized view log on 'chain '. "' string '.
The solution is:
Action: A full refresh is necessary before the next quick update. Add columns ROWID in the materialized view log, if necessary.

How can I do a complete refresh before the next fast refresh or ROWID columns add? How do I know whether the ROWID columns add?
Thank you.

run up
```
EXECUTE DBMS_MVIEW.REFRESH('MV_NAME','C');
```

ORA-22992: cannot use LOB Locators selected from the remote tables...
Oracle 10.2.1.0.4
Solaris 10

We try to access a table in another database via a db_link.

The table we are trying to access has a LOB.

We get the following error: ora-22992: cannot use LOB Locators selected from the remote tables.

Is there a way to get around this? We need the data in the BLOB field.

Thank you.
See on metalink:

ORA-22992 has a workaround solution in 10 gr 2
DOC - ID: 436707.1

Werner

ORA-01555: snapshot too old: number of rollback segments

Therefore on Oracle 11.2.0.2 on Solaris. High level, we have a pretty large table on one of our Oracle dev instances, lines 430mil, where the data was populated by a large data load. Two of our date fields have been left NULL so that we have to go back and update every row after the fact with SYSDATE values (some downstream applications require having some sort of date in this area).
in any case, I wrote a script for this (truncated a bit for brevity):
```
DECLARE
...
    ln_limit      NUMBER  := 10000; -- Max amount of records to process in a single bulk update statement    
    lv_total_rows INTEGER := 0;
    lv_count      NUMBER;
    lv_rowid      VARCHAR(18);
  
    CURSOR tco_cursor IS
        SELECT ROWID
        FROM LXRO
        WHERE LxModDate IS NULL;
  
    TYPE t_rows IS TABLE OF ROWID;
    lv_rowids t_rows;
  
BEGIN
...
    OPEN tco_cursor;
    LOOP
  
        FETCH tco_cursor BULK COLLECT INTO lv_rowids LIMIT ln_limit;
      
        FORALL i IN 1 .. lv_rowids.COUNT
            UPDATE LXRO
            SET LxModDate = SYSDATE
            WHERE ROWID = lv_rowids(i);

...     -- (writes to log table here)          
        COMMIT;

        EXIT WHEN lv_rowids.COUNT < ln_limit;    
    END LOOP;

    CLOSE tco_cursor;
    COMMIT;
  
    EXCEPTION
    WHEN OTHERS THEN
        dbms_output.put_line(TO_CHAR(lv_rowid) || ' - ' || sqlerrm || ' - ' || TO_CHAR (ln_counter));
END;
/
```
Only, the work runs for an hour and updates 37mil lines in a same test, and then gets the following error:
ORA-01555: snapshot too old: rollback segment number 30 with name ' _SYSSMU30_4136132754$ ' too small
I did some research on the error and read something interesting:
Do not look around is committed. In other words, don't fetch on a slider was opened before the last commit, especially if the data surveyed by the slider is changed in the current session.
Also, if the query is a loop with a commit in it, it can do the same without other queries, because finally the next iteration requires looking at his own first generation, cannot do so and barfs.
Upping undo_retention may help, or not, as the real cause. See also v$ undostat, you may still have information in there, if it is current (or not, since at the time where you check the necessary info can be gone).
I think that our UNDO tablspace has 16 GB now. I do not try to hold back the 400 million lines in temp would be feasible, that's why I am committed all 10 k rows, more we ran into problems of memory with a version non-bulk this script before. It will only be a time process (we have set our data migration to fill in these fields in future iterations). Am I better choose to simply keep this job and re - keep on running for hours all the hours given the amount of data? Is - this naïve to think that I could make this many updates without error in a single task running?

Simply change the column and set the DEFAULT as SYSDATE clause. Now, you would not have to perform the update at all.

And for the current issue, a single update could have questioned the size of the CANCELLATION. I guess that's what you're talking like memory problem. Good thing for you to do is to work with your DBA and Set configure your CANCELLATION as a result. If not enough UNDO available then you can split the update in the form of fixed numbers and run them, something like that.

I used a 10-million limit. But you can work with your DBA and attempt to set even more.

loop

Update lxro set lxmoddate = sysdate where lxmoddate has the value null and rownum<=>

commit;

When the output sql % rowcount<>

end;

/

Collect bulk copy the data in the PGA (private memory). It is a very expensive operation. Collect bulk was introduced mainly to reduce the change of context. But its performance is mediocre compared to direct SQL. So try to make your work in SQL right front.

Cannot use Winodws XP System Restore utility

I wonder if anyone can help. I can't get my laptop to restore as soon as possible. I have it and have used control points and manually restore points but it will not restore.

Don't stop of saying impossible to restore. No changes have been made.

Hello

Check it please this page http://www.theeldergeek.com/system_restore_not_functioning.htm

Good luck!

ORA-22992 cannot use LOB Locators selected remote tables
Hello.
I have a problem.
When I want to create a table select o sing a table a dblink, and the remote table has a clob field returns the error.
I'll fix it, using dblink. Is there a way to fix? export/tax free.

Thank you.

PD: 10 gr 2.
Hello
Insert of canoe read you a remote via dblink database table when that table has a clob or blob column.

If you must use inport / export option.

Use the Data Pump functionality in 10g. Then, you can export and import only your table without major issues.

Thank you

* If the answer is correct please mark.

ORA-01555, snapshot too old: number of rollback segment 2 with the name '_SYSSMU1 '.
Hello
Oracle 10g,
Im getting this error during the execution of a query

Autoextend is enabled for the undo data file

There are 6 GB of free space in the undo tablespace

Before him was for undo_retention 18000.

I have reset it using alter system command set to 25000.

But it still gives the same error
Please think about what could be the problem
```
SQL> select (62057/60)/60 query,(25000/60)/60 retention
  2    from dual
  3  /

     QUERY  RETENTION
---------- ----------
17.2380556 6.94444444
```
Your question exectuing mandate is 17 hours while your cancel retention is about 7 hours, change your retention period of 20% extra with your queries execution order and then check your question again.

at least the value cancel retention 75000, also you had better address your question why its too take so long?

Khurram

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

Hello world!

I encountered this error: "cannot use the non-system"TEMP tablespace system rollback segment.

So what I did to check the cancellation stuffs 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 do I bring them online?

I tried this but did not 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.

Must I bring each segment online separately? Please guide me.
Nith

Published by: user645399 on February 23, 2011 14:52

user645399 wrote:
Shouldn't have 2 undo tablespace?

Is that what you mean?

Yes, above statements completely wrong.
If you use single instance database (non-RAC) and then use an undo tablespace

can not create the rollback segment
Hello
in 8i on Win 2003
Unfortunately, I dropped rollback tablespace. Now when I get ORA-01552:
```
SQL> CREATE PUBLIC ROLLBACK SEGMENT "RBS1"
  2      TABLESPACE "RBS"
  3      STORAGE ( INITIAL 204k NEXT 10K MINEXTENTS 2 MAXEXTENTS
  4      32);
CREATE PUBLIC ROLLBACK SEGMENT "RBS1"
*
ERROR at line 1:
ORA-01552: cannot use system rollback segment for non-system tablespace 'RBS'
```
Any solution?
Thank you.
MetaLink Note 112479.1
Or the same solution but without explanation here:
http://www.freelists.org/post/askdba/DBA-gurus-ORA01552-cannot-create-a-rollback-segment, 2

General - rollback segments
Read manuals, I have a few question to clarify about rollback segments (cancellation automatic management side and can leave undo tablespace)

(1) rollback segments can be created in a tablespace - is there a limit/maximum size that can be specified for a rollback segment to use within a tablespace? -To read manuals, does not mention the clause of storage on the size/max limit for a rollback segment; is it possible for the rollback segment to fill tablespace (UH because of some queries Wired [consistent playback] / transaction)?

(2) we can create a separate rollback tablespace and have several rollback segments.

If there are 3 user tablespaces (T1, T2, T3), 1 (RT) rollback tablespace.
-J' I create 1 rollback segment in tablespace T1, T2, T3
-J' I create 2 rollback segments in a tablespace rollback RT

A user with "tablespace T1 default" when you run a transaction, what rollback segment will be used by this user (when the rollback segment is not specified explicitly)?

Oracle-student
user11359766 wrote:

The transaction will overflow to the second rollback segment (IE start using the 2nd rollback segment that is available and not used by another active transaction) or oracle returns an error since the first segment of cancellation assigned is full and that the transaction is always active?

This will apply to both SMU and MMU.

The same link above.
http://download.Oracle.com/docs/CD/B10501_01/server.920/a96524/b_deprec.htm#634941

For the duration of a transaction, the associated user process writes restore only information for the assigned rollback segment.

I hope that its explicit transaction cannot roll any other rear roller segment once its own lot of space. In the case of EMS, also, if the undo datafile cannot grow, your transaction would be arrested.

HTH
Aman...

ORA-12913 cannot create the dictionary managed during import tablespace
Greetings,
I'm a newbie om moving databases between servers.

I get the following error: "ora-12913 cannot create tablespace dictionary managed" when executing the data pump import. It is a 10.2.0.4 database that I'm moving from HP - UX PA-RISC to HP-UX-Itanium. It seems that all managed tablespaces locally were ok. Some of the successful dictionary tablespaces had problems (DRSYS, INDX, RBS, TOOLS)

Should I convert all tablespaces dictionary managed locally managed tablespaces before data pump export/import? Note that this is a very small database with little use, then what better practical performance I'd like to hear.

Thanks colin

Published by: YJC on Aug 17, 2010 15:16
>
(1) should all be converted to Locall managed?
(2) can the RBS safely deleted, given that an UNDO tablespace that uses the DB.
>

Only the SYSTEM will have to be migrated to managed locally. The RBS tablespace can be deleted if there is a separate UNDO tablespace and the database uses undo automatic management.

HTH
Srini

ORA-01552: cannot use no tablespace system rollback segment

Similar Questions

Maybe you are looking for