InterMedia leaves garbage in the system tablespace

During the creation of a context(interMedia) index, I shutdown
the Oracle server with abort. I started the server up and
proceeded to delete the bad index. When I tried to create a new
index with the same name an error occured. I looked in some
tables in the system tablespace under the ctxsys user, and found
references to my corrupted index. Is there a way to clear out
this bad data w/o having to re-install Oracle?

You don't say what the error is so I can't be sure, but I
suspect that deleting the entry in dr$index (owned by ctxsys)
for your 'bad' index will allow you to recreate it.

Similar Messages

  • Why the system tablespace increase a lot?

    I have noticed that the system tablespace of my prod Oracle 10g R2 on AIX 5.3L reaches over the 85% warning level now, and the size has increased from ~68% to 88% of 1.6G total assigned capacity during the last 7 months. How do i find out what reason causes the increase? can I remove some "fat" out of them? or just keep increasing the size? My fresh backup AIX 5.3L system with the same 10g R2 only takes 38% of 1.6 G.

    SEGMENT_NAME SEGMENT_TYPE MBYTES
    SYS_LOB0000125172C00039$$ LOBSEGMENT 152
    C_OBJ#_INTCOL# CLUSTER 136
    I_CON1 INDEX 104
    C_OBJ# CLUSTER 96
    C_COBJ# CLUSTER 88
    HIST_HEAD$ TABLE 57
    CON$ TABLE 41
    I_COL1 INDEX 41
    C_FILE#_BLOCK# CLUSTER 38
    I_HH_OBJ#_COL# INDEX 34
    I_HH_OBJ#_INTCOL# INDEX 34
    SOURCE$ TABLE 32
    I_CON2 INDEX 27
    IDL_UB1$ TABLE 26
    I_CDEF4 INDEX 26
    I_H_OBJ#_COL# INDEX 25
    I_COL2 INDEX 20
    OBJ$ TABLE 19
    I_COL3 INDEX 19
    I_CCOL1 INDEX 19
    I saw some LOB segments in SYS; however my fresh new 10g R2 (v SE) on other AIX machine does not list those. Where are they from?
    I checked the user_lobs, Here are the tables which has LOB seg stored the system tablespace
    AW_OBJ$
    VIEWCON$
    SNAP$
    SNAP$
    TABPART$
    INDPART$
    TABSUBPART$
    INDSUBPART$
    TABCOMPART$
    INDCOMPART$
    DEFSUBPART$
    KOTTD$
    KOTTB$
    KOTAD$
    KOTMD$
    KOTTBX$
    KOTADX$
    SUM$
    SUM$
    SQL$TEXT
    METASTYLESHEET
    EXTERNAL_TAB$
    EXTERNAL_TAB$
    JIREFRESHSQL$
    AUD$
    AUD$
    FGA_LOG$
    FGA_LOG$
    PS$
    STREAMS$_DEF_PROC
    STREAMS$_DEF_PROC
    STREAMS$_DEF_PROC
    REDEF_DEP_ERROR$
    NCOMP_DLL$
    EXPIMP_TTS_CT$
    ATTRIBUTE_TRANSFORMATIONS$
    RULE$
    RULE$
    REG$
    AQ_EVENT_TABLE
    AQ_SRVNTFN_TABLE
    AQ_SRVNTFN_TABLE
    SCHEDULER$_JOBQTAB
    SCHEDULER$_JOBQTAB
    SCHEDULER$_JOB_ARGUMENT
    SCHEDULER$_PROGRAM_ARGUMENT
    SCHEDULER$_EVENT_QTAB
    KUPC$DATAPUMP_QUETAB
    KUPC$DATAPUMP_QUETAB
    KUPC$DATAPUMP_QUETAB
    KUPC$DATAPUMP_QUETAB
    KUPC$DATAPUMP_QUETAB
    KUPC$DATAPUMP_QUETAB
    KUPC$DATAPUMP_QUETAB
    STREAMS$_INTERNAL_TRANSFORM
    AQ$_MEM_MC
    AQ$_MEM_MC
    AQ$_KUPC$DATAPUMP_QUETAB_P
    AQ$_KUPC$DATAPUMP_QUETAB_P
    AQ$_KUPC$DATAPUMP_QUETAB_P
    AQ$_KUPC$DATAPUMP_QUETAB_P
    AQ$_KUPC$DATAPUMP_QUETAB_P
    AQ$_KUPC$DATAPUMP_QUETAB_P
    AQ$_KUPC$DATAPUMP_QUETAB_P
    AQ$_KUPC$DATAPUMP_QUETAB_D
    SYS_EXPORT_FULL_01
    SYS_EXPORT_FULL_02
    Does not look like any non-system user here?
    Message was edited by:
    user508054

  • Backup everything except the system tablespace

    Is there a way to backup everything except the system tablespace without having to specify every individual tablespace?
    version is 10.1.0.5 on HP-UX itanium.
    The reason for this is the database was upgraded from 7.3.4->8i->10.1.0.5 and we are now migrating to using RMAN instead of user managed backups however we have encountered a bug when backing up index blocks in the system tablesapce this only impacts compressed backupsets so If I can exlude the system tablespace I can run two backups one uncompressed that captures the system tablespace then another that captures everything else. I'd really like to avoid specifying the tablespaces in a script as it then introduces the possibility that a new tablespace is added and isn't included in the backups.

    Unfortunatly this database is used by a third party application and the aplpication vendor only supports 10.1.0.5 at the moment, plans are to upgrade next year and tidy up the number of tablespaces at the same time.
    looks like I'll have to backup the system tablespace uncompressed and then all the other tablespaces as a compressed backupset and setup an alert on files not backed up.

  • How to shrink the system tablespace datafile Size

    iam using oracle 9i R2 and i want to reduce my datafile size but it's show's that error when i try to resize it. ORA-03297

    Hi,
    We can directly resize datafilesTEST.SQL>SELECT FILE_NAME, BYTES FROM DBA_DATA_FILES WHERE TABLESPACE_NAME='SYSTEM';
    FILE_NAME
         BYTES
    /.../dbsGNX.dbf
    419430400
    TEST.SQL>ALTER DATABASE DATAFILE '/.../dbsGNX.dbf' RESIZE 390M;
    Database altered.
    TEST.SQL>SELECT FILE_NAME, BYTES FROM DBA_DATA_FILES WHERE TABLESPACE_NAME='SYSTEM';
    FILE_NAME
         BYTES
    /.../dbsGNX.dbf
    408944640But the minimum file size is the size of the extend the furthest in the datafile:TEST.SQL>SELECT FILE_ID,FILE_NAME FROM DBA_DATA_FILES WHERE TABLESPACE_NAME='SYSTEM';
       FILE_ID
    FILE_NAME
             1
    /.../dbsGNX.dbf
    TEST.SQL>SELECT MAX(BLOCK_ID) MBID FROM DBA_EXTENTS WHERE FILE_ID=1;
          MBID
         25129
    TEST.SQL>SELECT SEGMENT_NAME,OWNER,SEGMENT_TYPE FROM DBA_EXTENTS WHERE FILE_ID=1 AND BLOCK_ID=25129;
    SEGMENT_NAME                                                                      OWNER                          SEGMENT_TYPE
    I_OBJAUTH2                                                                        SYS                            INDEX
    TEST.SQL>SHOW PARAMETER BLOCK_SIZE
    NAME                                 TYPE                             VALUE
    db_block_size                        integer                          8192
    TEST.SQL>SELECT 8192*25129 FROM DUAL;
    8192*25129
    205856768about 200M.
    Regards,
    Yoann.

  • How to reduce the size of SYSTEM tablespace?

    * Solaris
    * Oracle 9.2.0.4.0
    * Locally managed database (since SYSTEM is locally managed TS)
    I have a Oracle 9i database with is around 7 months old. Over the 7 months it had around 400 schema’s at most and SYSTEM tablespace was increased to 850MB. Now it only has around 120 schema’s and size of the SYSTEM tablespace still 850MB and it’s 99% used.
    How can I get more free space on system tablespace?
    * I have made sure that non-sys(tem) user don’t have objects on SYSTEM tablespace.
    * I understand that dropping schema does not give you all the space back, since objects are store as row in System tables etc.
    Increasing disk is not an option for me. Any tips to free space on system welcome.
    Thanks,
    Nazrul Islam

    Thanks Joel Pérez for trying to help.
    SQL> select segment_name, owner from
    dba_segments
    where owner not in
    ('SYS','SYSTEM','OUTLN','MDSYS','ORDSYS','WMSYS')
    and
    TABLESPACE_NAME='SYSTEM';
    SEGMENT_NAME                   OWNER
    TOAD_PLAN_SQL                  TOAD
    TOAD_PLAN_TABLE                TOAD
    PLSQL_PROFILER_RUNS            TOAD
    PLSQL_PROFILER_UNITS           TOAD
    PLSQL_PROFILER_DATA            TOAD
    TPSQL_IDX                      TOAD
    TPTBL_IDX                      TOAD
    SYS_C006895561                 TOAD
    SYS_C006895563                 TOAD
    SYS_C006895566                 TOAD
    10 rows selected.
    SQL> select owner from dba_segments where
    tablespace_name='SYSTEM'
    group by owner;
    OWNER
    OUTLN
    SYS
    SYSTEM
    TOAD
    WMSYSHere is my query (to show TOAD is taking very little
    space):r.- That is true, the space used by TOAD is little
    >
    SQL> select owner, SUM(bytes)/1048576 AS "TOTAL
    (MB)"
    from dba_segments
    where tablespace_name = 'SYSTEM'
    group by owner order by "TOTAL (MB)" desc;
    OWNER                 TOTAL (MB)
    SYS                     820.4375
    SYSTEM                      20.5
    WMSYS                     3.6875
    TOAD                       .6875
    OUTLN                       .375Looks like, I have to grow system. Or since I have a
    fixed number of schema now, I think I will have to
    recreate a DB to reduce SYSTEM size.
    Joel one other info that might explain why
    this happening. Part of our build process is to drop
    4 schemas and roles and recreate them.
    e.g.
    drop user nislam cascade;
    create user nislam ....And we do many builds a day. Maybe Oracle uses more
    space in doing that since new userid, better might be
    drop objects from the schema. WHAT do you
    say?
    r.- In theorical lines. Both must give the same results but... I would recommend you to carry out some intensive test about it in a test enviroment testing both methods to monitor the behavior of the growth of the tablespace system. As you said, perhaps dropping the user objects will get better results.
    >
    Regards,
    Nazrul IslamJoel Pérez
    http://otn.oracle.com/experts

  • SYSTEM Tablespace Segment Management

    When creating a new database (11.1.0.7) on AIX 5.3, what are the benefits of creating a SYSTEM tablespace with MANUAL segment management? This question may not be limited to 11g databases, but I was curious if the SYSTEM tablespace could be set to AUTO segement management and what drawbacks I might see in doing so?
    Most of the databases I help manage have been established years ago and most, if not all, are set to MANUAL.
    Thanks

    This is the default. I do not think you or I know better than the Oracle designers ho to best setup the SYSTEM tablespace. You are best to leave it alone.
    SQL> exec print_table('select * from dba_tablespaces where tablespace_name = ''SYSTEM''');
    TABLESPACE_NAME               : SYSTEM
    BLOCK_SIZE                    : 8192
    INITIAL_EXTENT                : 65536
    NEXT_EXTENT                   :
    MIN_EXTENTS                   : 1
    MAX_EXTENTS                   : 2147483645
    MAX_SIZE                      : 2147483645
    PCT_INCREASE                  :
    MIN_EXTLEN                    : 65536
    STATUS                        : ONLINE
    CONTENTS                      : PERMANENT
    LOGGING                       : LOGGING
    FORCE_LOGGING                 : NO
    EXTENT_MANAGEMENT             : LOCAL
    ALLOCATION_TYPE               : SYSTEM
    PLUGGED_IN                    : NO
    SEGMENT_SPACE_MANAGEMENT      : MANUAL
    DEF_TAB_COMPRESSION           : DISABLED
    RETENTION                     : NOT APPLY
    BIGFILE                       : NO
    PREDICATE_EVALUATION          : HOST
    ENCRYPTED                     : NO
    COMPRESS_FOR                  :
    -----------------As you can see, SYSAUX is set up a bit different. System being special, you are best to leave it alone.
    SQL> exec print_table('select * from dba_tablespaces where tablespace_name = ''SYSAUX''');
    TABLESPACE_NAME               : SYSAUX
    BLOCK_SIZE                    : 8192
    INITIAL_EXTENT                : 65536
    NEXT_EXTENT                   :
    MIN_EXTENTS                   : 1
    MAX_EXTENTS                   : 2147483645
    MAX_SIZE                      : 2147483645
    PCT_INCREASE                  :
    MIN_EXTLEN                    : 65536
    STATUS                        : ONLINE
    CONTENTS                      : PERMANENT
    LOGGING                       : LOGGING
    FORCE_LOGGING                 : NO
    EXTENT_MANAGEMENT             : LOCAL
    ALLOCATION_TYPE               : SYSTEM
    PLUGGED_IN                    : NO
    SEGMENT_SPACE_MANAGEMENT      : AUTO
    DEF_TAB_COMPRESSION           : DISABLED
    RETENTION                     : NOT APPLY
    BIGFILE                       : NO
    PREDICATE_EVALUATION          : HOST
    ENCRYPTED                     : NO
    COMPRESS_FOR                  :
    -----------------

  • RMAN duplicate target database for standby from active fails to create newname for system tablespace/datafile

    When executing 'duplicate target database for standby from active'  the system tablespace/datafile (datafile 1)  is not cloned.  All other datafiles clone successfully.  The RMAN process aborts with the following errors while attempting to clone the system tablespace/datafile.
    ORA-19558: error de-allocating device
    ORA-19557: device error, device type: DISK, device name:
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
    ORA-03135: connection lost contact
    Here are the details:
    Primary is 11.2.0.2 RAC database  on an Exadata platform
    Standby is 11.2.0.2 Single Instance database (same patch level as primary) on a Red Hat Linux box
    This is an ASM to ASM duplication.
    This is not unique to this database.  We tried another database and go the same behavior - all datafiles clone successfully with the exception of the system tablespace/datafile.
    We have traced the RMAN execution and it seems to fail when it is trying to assign a NEWNAME to the system tablespace/datafile.
    We even issued an explicit SET NEWNAME command but RMAN ignored it.
    We also shutdown the primary and started is up in mount mode thinking that something had ahold of the System Tablespace/datafile.
    We also opened up the network firewall to allow permit any,any traffic.
    We increased the max_server_processes
    and added TCP.NODELAY=yes to the sqlnet.ora file.
    There seems to be some artifact present in our Primary System tablespace/data file that is preventing it form being cloned.
    checked all alert files grid, asm,  and dbhome - no abnormal messages.
    We are in the process of restoring the database from a backup but we would prefer to get this working using the 'Active Database' methodology

    I successfully created the standby database using RMAN backup and recovery.
    I started the managed recovery.  Archive logs are being sent from the primary to the standby ( I can see them in ASM), but the standby is not applying them.
    I get the following messages in the standby alert log...
    Fetching gap sequence in thread 2, gap sequence 154158-154257
    Tue Nov 26 16:19:58 2013
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
    Tue Nov 26 16:20:01 2013
    Fetching gap sequence in thread 2, gap sequence 154158-154257
    Tue Nov 26 16:20:11 2013
    Fetching gap sequence in thread 2, gap sequence 154158-154257
    Tue Nov 26 16:20:22 2013
    Fetching gap sequence in thread 2, gap sequence 154158-154257
    Tue Nov 26 16:20:32 2013
    Fetching gap sequence in thread 2, gap sequence 154158-154257
    I don't see any MRP processes:
    select process,
    status,
        thread#,
        sequence#,
       block#,
      blocks
      7     from v$managed_standby;
    PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
    ARCH      CLOSING               2     154363          1        132
    ARCH      CONNECTED             0          0          0          0
    ARCH      CONNECTED             0          0          0          0
    ARCH      CONNECTED             0          0          0          0
    ARCH      CONNECTED             0          0          0          0
    ARCH      CONNECTED             0          0          0          0
    ARCH      CONNECTED             0          0          0          0
    ARCH      CONNECTED             0          0          0          0
    RFS       IDLE                  0          0          0          0
    RFS       IDLE                  1     145418        121          1
    RFS       IDLE                  0          0          0          0
    PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
    RFS       IDLE                  0          0          0          0
    12 rows selected.
    SQL>  SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
       THREAD#  SEQUENCE# APPLIED
             2     154356 NO
             2     154357 NO
             1     145411 NO
             2     154358 NO
             2     154360 NO
             2     154361 NO
             1     145414 NO
             1     145415 NO
             2     154362 NO
             2     154363 NO
             1     145416 NO
    11 rows selected.
    I do have the archive logs that cover sequences 154158-154257
    Crosschecked 38 objects
    Crosschecked 62 objects
    Finished implicit crosscheck backup at 26-NOV-13
    Starting implicit crosscheck copy at 26-NOV-13
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    Crosschecked 2 objects
    archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154377.344.832521989 RECID=29 STAMP=832521990
    validation succeeded for archived log
    archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154378.346.832521991 RECID=31 STAMP=832521993
    Crosschecked 31 objects

  • How to create a system tablespace as  locally manged in 8.1.7

    After a good time looking for it I still haven't found an example of how to create a database with the system tablespace as locally managed in release 8.1.7
    I'm trying this, that isn't OK at all:
    create database CSR
    character set "WE8ISO8859P15"
    datafile '/home/oracle/create/CSR/system/sysCSR.dbf' size 75M
    extent management local
    DEFAULT TEMPORARY TABLESPACE tsp_temp
    DATAFILE '/home/oracle/create/CSR/temp/tempCSR.dbf'
    SIZE 80M REUSE
    logfile '/home/oracle/create/CSR/redo/redo1CSR.log' SIZE 500k,
         '/home/oracle/create/CSR/redo/redo2CSR.log' SIZE 500k,
         '/home/oracle/create/CSR/redo/redo3CSR.log' SIZE 500k;
    Can someone tell me what is wrong, please?

    I'm trying this, that isn't OK at allAre there any errors? can you explain what is not "OK"?

  • No privileges on system tablespace?

    I am a new dba & have succesfully created tables and added constraints.
    Today I tried to add a constraint to an existing table, and received the message
    ORA-01950: no privileges on tablespace 'SYSTEM'
    I tried to add the constraint as the owner of the table, as a user with granted privs on the table, and finally as SYS, and get the same error.
    The system tablespace is only about 60% full, and I have not changed any user privs since I last sucessfully added constraints.
    If someone would give me a clue as to what's going on, I would really appreciate it.
    Thanks, Helen

    I granted unlimited tablespace to the user that owns the table, and the constraint was added successfully.
    I don't know if a user should have unlimited tablespace on SYSTEM...any advice on what a good limit would be? My system tablespace is 325 M and about 60% full. Would it make sense to grant sys unlimited tablespace on SYSTEM?
    Thanks very much for your help. You gave me the incentive to keep trying things until something worked.

  • Adding datafile to ASM file system tablespace

    Hi
    Can some one plz help in writing a script to add a datafile to the system tablespace on ASM filesystems.
    below is the result of the query ..
    select file_name, bytes, autoextensible, maxbytes from dba_data_files where tablespace_name='SYSTEM';
    FILE_NAME BYTES AUT MAXBYTES
    +DATA1/cir_p/datafile/system.260.6037360 5892997120 NO 0
    Thanks

    790072 wrote:
    Hi
    Can some one plz help in writing a script to add a datafile to the system tablespace on ASM filesystems.
    below is the result of the query ..
    select file_name, bytes, autoextensible, maxbytes from dba_data_files where tablespace_name='SYSTEM';
    FILE_NAME BYTES AUT MAXBYTES
    +DATA1/cir_p/datafile/system.260.6037360 5892997120 NO 0
    Thanks
    You can use
    ALTER TABLESPACE "SYSTEM" ADD DATAFILE '+DATA1' SIZE 1024M
    Cheers

  • How can I reduce size of the SYSTEM datafile?

    Hi All,
    I recently installed Oracle 9i Enterprise addition on Windows XP Pro. Everything went smoothly. However, I foolishly created a database with large space requirements in the default tablespace (SYSTEM) and this caused the datafile for the SYSTEM tables space to grow to 8 Gig. I dropped the tables and tried to shrink the datafile with the 'alter database datafile resize' command but the command failed indicating that the tablespace had data byond the reize amount. However, this is claerly not true since the OEM indicates that the tablespace is only 4% utilized.
    How can I reset the high water mark for the SYSTEM tablespace so that I can resize the datafile?

    Hi All,
    I recently installed Oracle 9i Enterprise addition on Windows XP Pro. Everything went smoothly. However, I foolishly created a database with large space requirements in the default tablespace (SYSTEM) and this caused the datafile for the SYSTEM tables space to grow to 8 Gig. I dropped the tables and tried to shrink the datafile with the 'alter database datafile resize' command but the command failed indicating that the tablespace had data byond the reize amount. However, this is claerly not true since the OEM indicates that the tablespace is only 4% utilized.
    How can I reset the high water mark for the SYSTEM tablespace so that I can resize the datafile? at one time (perhaps during the install) the extents may have been used and although you see only 4% used those extents have been allocated nonetheless.
    you'll have to rebuild the db if you can't resize the system ts
    to reset the high water mark you would have to truncate the system tables, don't think you want to do that
    steve

  • Doubts in the rollback tablespace

    Dear Gurus,
    I created a database using dbca to do it...
    The creation was fine, but when I looked at the rollback segments at OEM I saw that the tablespace of the rollback is the system tablespace....
    Now I have a doubt, the tablespace of the rollback segment wasn´t to be the UNDOTBS1?
    Thnks...

    rollback segments show the active undo segments used in ur database (database vide), as system segment is created as the database created for system table space undo activities, further the oracle by default create and drop undo segments automatically and will not show in rollback segments , u can view the active created segments in v$rollstat view which are system generated. you can create your custom undo segments but for that u have to set parameters in initial parameter file and have to tell oracle to manage undo segments manually.

  • SYSTEM Tablespace issue (10.2.0.1 database)

    Hi ,
    Oracle database 10.2.0.1 (upgraded from 8.1.7.0 via 8.1.7.4)...successfully upgraded
    Now when we open dbcontrol, we are getting alerts regarding the Tablespace.
    It shows two critical alert messages as below :-
    1) Tablesapace SYSTEM (dictionary managed) is 95.16 % full
    2) 1 segment in SYSTEM tablespace is unable to extend.
    Now how to deal with this type of issues ?
    Can we extend the size of datafile of SYSTEM Tablespace which is dictionary managed ? or can we add another new datafile to system tablespace ? what is appropriate solution ?SYSTEM Tablespace
    How to solve the point no. (2) as the TS is dictionary managed ?
    With Regards

    hi ,
    Plz add the datafile to the system tablespace tp increase its size , and the conver the system tablespace from dictionary managed to local.
    To Change SYSTEM tablespaces to locally managed follow the below procedures:
    Before the SYSTEM tablespace can be migrated to locally managed format, you should ensure the following:
    The database has a default temporary tablespace which is not SYSTEM
    There are not any rollback segments in dictionary managed tablespaces
    There is at least one online rollback segment in a locally managed tablespace, or an undo tablespace (if using automatic undo management mode) should be online.
    All tablespaces other than the tablespace containing the undo space (undo tablespace or the tablespace containing the rollback segment) and the default temporary tablespace are in read-only mode.
    There is a complete backup of the system.
    The system is in restricted mode.
    Notr, that we already have an UNDO Tablespace. The following query determines whether the SYSTEM tablespace is locally managed:
    SQL> SELECT ts# FROM ts$ WHERE ts# = 0 AND bitmapped <> 0;
    If 0 rows are returned, then the SYSTEM tablespace is dictionary managed. Otherwise, the SYSTEM tablespace is locally managed.
    Steps to change SYSTEM tablespaces to locally managed
    SQL> shutdown immediate
    SQL> startup restrict
    SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL ('SYSTEM');
    ERROR at line 1:
    ORA-10644: SYSTEM tablespace cannot be default temporary tablespace
    ORA-06512: at "SYS.DBMS_SPACE_ADMIN", line 227
    ORA-06512: at line 1
    SQL> ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp;
    SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL ('SYSTEM');
    ERROR at line 1:
    ORA-10647: Tablespace other than SYSTEM, UNDO, TEMP not
    found in read only mode
    ORA-06512: at "SYS.DBMS_SPACE_ADMIN", line 227
    ORA-06512: at line 1
    SQL> select tablespace_name from dba_tablespaces;
    TABLESPACE_NAME
    SYSTEM
    TEMP
    USERS
    TAB
    IDX
    SYSAUX
    UNDO
    SQL> alter tablespace USERS read only;
    SQL> alter tablespace TAB read only;
    SQL> alter tablespace IDX read only;
    SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL ('SYSTEM');
    ERROR at line 1:
    ORA-10648: Tablespace SYSAUX is not offline
    ORA-06512: at "SYS.DBMS_SPACE_ADMIN", line 227
    ORA-06512: at line 1
    SQL> alter tablespace SYSAUX offline;
    SQL> execute DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL ('SYSTEM');
    PL/SQL procedure successfully completed.
    Regards,
    Mohd Mehraj Hussain
    http://mehrajdba.wordpress.com

  • System tablespace Vs User Tablespace

    I'm running oracle 8i at Win2000 Server.
    I have a database which have two SYSTEM tablepspaces and One User tablespace. Both SYSTEM Tablepspaces are near to FULL. Right now , The database performance is very poor. I can't understand why my SYSTEM tablespaces are growing fastly instead of User Tablepspace.

    You cannot have multiple SYSTEM tablespaces... Do you mean that you have multiple datafiles associated with your SYSTEM tablespace?
    Unless you assign users a default tablespace, objects that they create without specifying a tablespace will be placed in the SYSTEM tablespace, which is a bad thing. You probably have user objects in your SYSTEM tablespace.
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • System tablespace

    I have created a table in the system tablespace. I am able to rename the column in the table, add a new column to the table, modify the column in the table. But when I tried to drop the column in the table, the following error is raised.
    ORA-12988: cannot drop column from table owned by SYS
    The user is connected as a sysdba. What is the logic that goes behind this error, as we are able to create a new table in system tablespace, rename the column, modify the column in the table and add new columns to the table. But we couldn't drop a column in the same table.

    I have created a table in the system tablespace. Wrong idea
    I am able to rename the column in the table, add a new
    column to the table, modify the column in the table.
    But when I tried to drop the column in the table, the
    following error is raised.
    ORA-12988: cannot drop column from table owned by
    SYS
    Connect as SYS and drop it.
    The user is connected as a sysdba. What is the logic
    that goes behind this error, as we are able to create
    a new table in system tablespace, rename the column,
    modify the column in the table and add new columns to
    the table. But we couldn't drop a column in the same
    table.Creating a new table in system tablespace is one thing. Creating a table connected as SYSDBA is a different thing.
    So you have two wrongs to correct.
    1. Do not create new tables in system tablespace. Create a new tablespace for users (if you do not have one).
    2. Do not connect as sysdba to create new tables. Connect as that user without sysdba.

Maybe you are looking for

  • Error while submitting standard import purchase order program

    Hi, iam submitting Standard import purchase order concurrent program, iam getting error in view - output like Enter value for 12: EXEC FND_CONC_STAT.COLLECT; Enter value for 14: in view-log like To get the log messages for PDOI, please use the follow

  • Error in COR1 - Material not allowed to use

    Hi, Material is in the stock "unrestricted use " but does not allow to use in a production process order. All related options are verified for example : MB51, MMBE, Date of production is prior to use, Quality is OK, Not in blocked stock, not reserved

  • Missing package in gnome-extra group

    The package gnopernicus in the gnome-extra group depends on gnome-speech package which doesn't exist. Neither the package itself exists nor does have an entry in the database file. pacman -Si gnopernicus You'll find that it depends on gnome-speech pa

  • Check In Page Customisation

    We need to change the default content check-in page in UCM, and haven't had luck finding info in the documentation. The two things we want to do are: 1. Change True/False and Yes/No option lists to check/tick boxes 2. Change width of metadata fields

  • Dynamic url in readonly with xml

    Hello everybody, The link works fine, but I do not want the field to be editable. And when the field is read only, the link no longer works because of the event Have you a solution for the field link can not be editable ? Sorry i speak french ;o) tha