Optimal size of System - Tablespace

What is the optimal size for the system-tablespace with all option (with JVM and more) with the ORACLE Version 8.1.7 or 9i ?

There is no one-size-fits-all answer. The options you mentioned will have some affect on the size, only because they will add more OBJECTS to the database. The key drivers for how to size SYSTEM are the number of objects and users you anticipate in your database, and the number of database structures (tablespaces, files, logs, etc). The dictionary tables in the SYSTEM tablespace exist to maintain information on everything in the database, and are updated automatically as changes are made to database objects or structures. I usually recommend 200M as a safe starting value unless you know you will be creating a lot of objects, go with 250-300M.
A little story. A while back, I was forced (while protesting quite loudly) to create private synonyms for every table in the database for every user in the database. I warned the people who ordered this that we might encounter problems in SYSTEM, (and in the shared pool) because the total number of OBJECTS (synonyms) being added totalled well over 1 million. As predicted, the system tablespace could not handle the load, and I had to add one new file to SYSTEM, and then another on a DIFFERENT storage volume (no space left on original). When this was done, our SYSTEM tablespace was almost 600M. (The OBJ$ table swelled up like a balloon). When the geniuses who forced me to do this realized it was a really bad idea, they told me to drop the synonyms. But we were left with 3 SYSTEM datafiles when we only needed one (you can't drop them).

Similar Messages

  • Optimal size for TEMP tablespace tempfiles

    Hi all,
    I've rumaged through Oracle documentation on the above topic but can't find the answer I'm seeking:
    How do you determine the optimal size for your tempfiles? Are there rules to guide one in this area? For example for a 50G database, how do you determine if it's 2G, 3G or 4G that's best for the database? What about a 500G database?
    Anwers will be appreciated.
    Regards

    It's the size of the sets, as you say. And in a data warehouse, the data sets can be very large. I'd say that in an OLTP database, then the useage of temp would (should) be low; but in a data warehouse, all bets are off: one-off end of month runs; director wants a monolithic report running; all that sort of DWH-related type of processing, which, by its nature, happens all the time. Similarly, a large number of users (e.g. users of, say, a Third Party BI tool) amy lead to lots of big sorts, owing to the ad hoc nature of their queries. Standard DWH stuff.
    I don't often see tiddly-widdly bits of SQL in data warehouses, like your SELECT COUNT(*) FROM tab$ example. It could be done, sure, but more likely will be bit, fat queries, which a DWH is designed to deal with. And a lot of temp may be required.
    From that 6-years old (but relevant) article (my emphasis): "For example, if you join two *large* tables, and Oracle cannot do the sort in memory (see SORT_AREA_SIZE initialisation parameter), *space will be allocated in a temporary tablespace for doing the sort operation*."
    Regards - Don Lewis

  • 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 Resize --Crusial thing happened

    Hi
    When I disconnected permission on a temporary tablespace
    to a user, I forget his permission on the system tablespace.
    One of his query consumed more than 1 gb size in system
    tablespace.
    Now I am getting ORA-03297 When tried to resize.
    Suggestions are highly appriciated.
    Thanks
    giri

    Narayanan V giri , this script is going to help you
    for checking locks in the database and its sessions.
    Try to kill them before resize.
    col object_name format a20
    col username format a10
    col oracle_username format a10
    col process format a15
    col owner format a10
    prompt ****************************************************************
    prompt *** Object Lock Contention ***
    prompt ****************************************************************
    set pages 0
    set linesize 150
    select 'Date : '||to_char(sysdate,'DD/MM/YYYY')||' Time : '||to_char(sysdate,'HH:MI:SS') from dual;
    select 'Database Name : '||name from sys.v_$database;
    set pages 1000
    SELECT DISTINCT
    O.OBJECT_NAME,
    SH.USERNAME,
    SH.SID,
    SW.USERNAME,
    SW.SID,
    DECODE(LH.LMODE,
    1, 'null',
    2, 'row share',
    3, 'row exclusive',
    4, 'share',
    5, 'share row exclusive',
    6, 'exclusive')
    FROM DBA_OBJECTS O,
    V$SESSION SW,
    V$LOCK LW,
    V$SESSION SH,
    V$LOCK LH
    WHERE LH.ID1 = O.OBJECT_ID
    AND LH.ID1 = LW.ID1
    AND SH.SID = LH.SID
    AND SW.SID = LW.SID
    AND SH.LOCKWAIT IS NULL
    AND SW.LOCKWAIT IS NOT NULL
    AND LH.TYPE = 'TM'
    AND LW.TYPE = 'TM'
    prompt Press Enter to continue ...
    pause
    prompt ************************************************************
    prompt *** Object Lock Information ***
    prompt ************************************************************
    SELECT
    A.OBJECT_NAME,
    A.OWNER,
    C.SERIAL#,
    B.OBJECT_ID,
    B.SESSION_ID,
    B.ORACLE_USERNAME,
    B.OS_USER_NAME,
    B.PROCESS,
    DECODE(B.LOCKED_MODE,
         0,'None',
    1,'Null',
         2,'Row-S (SS)',
         3,'Row-X (SX)',
         4,'Share',
         5,'S/Row-X (SSX)',
         6,'Exclusive') LMODE
    FROM DBA_OBJECTS A, V$LOCKED_OBJECT B, V$SESSION C
    WHERE A.OBJECT_ID = B.OBJECT_ID AND C.SID = B.SESSION_ID
    ORDER BY A.OWNER, A.OBJECT_NAME, C.SERIAL#
    Joel P�rez

  • Minimum System Tablespace Requirement

    Hi all,
    I have created my database, however system tbs boomed when I'm executing catproc.sql
    Due to storage concern, sad story, ain't allocated much storage to setup this db, is there any documentation that indicate the minimum requirement for the storage size for new db setup?
    Eg. What's the minimum size required for system tablespace in order to complete catproc.sql successfully.
    Thanks in advance for any input.
    Eugene

    How much was allocated to SYSTEM tablespace initially and what is the size now?
    In our setups, we allocate 500MB as initial size for SYSTEM tablespace data files. Then it is allowed to extend in chunks of 100MB.

  • Tablespace size. System data vs user data.

    Hi,
    I have Oracle 11.2.0.1 on Solaris 11 x86_64. Software using SYSTEM tablespace. The free space on this tablespace is allmost end,
    When i check what amount of data is collected in database i get strange value:
    select SUM(qq.MB) from (select table_name,(num_rows*avg_row_len)/(1024*1024) MB, num_rows, avg_row_len from user_tables) qq;
    SUM(QQ.MB)            
    6,43802738189697265625
    So i suppose that data using only 6.4MB.... But statistic for this tablespace is
    Tablespace                     Used MB                Free MB                Total MB               Pct. Free             
    SYSAUX                         655                    35                     690                    5                     
    UNDOTBS1                       27                     18                     45                     40                    
    TQTBS                          11                     489                    500                    98                    
    USERS                          0                      5                      5                      100                   
    SYSTEM                         707                    93                     800                    12              
    What is using 700MB?!

    It is a very good thing to use the command line queries to understand these things.  But it is also good to know your tools.  You should check tablespace size with dbconsole, it shows nice little pictures of how much space is used.  Note that your system tablespace is autoextend, and this is a good thing, since as Sybrand noted, that's where the PL/SQL is stored.  As a practical matter, unless you are adding a lot of new code, that tablespace tends to expand to a steady size and just stay there.  You don't want to fix it there, because you might add new code in the future.
    On the other hand, sysaux and your data may need some watching.  If you are curious, you can use the tablespace map function in dbconsole to see what is where in tablespaces (and there are scripts floating about to see it command line style).  But don't stress over it, Oracle is really good about doing things right.  What you have to watch out for is things like auditing or plan maintenance becoming space hogs in sysaux, and some apps, sometimes combined with some bugs, can use too much data space.  But really, you shouldn't bother with it too much unless you see something using way more space than you would reasonably expect. 
    If you want to obsess over something, consider patching.  11.2.0.1 is not a good sign.

  • How do you determine the optimal size for Mozilla Firefox?

    How do you determine the optimal size for cache in Mozilla
    Firefox? I am using Firefox 7.0.1 on a 64-bit Windows 7 Ultimate operating system with 3GB RAM and 300 GB hard drive, but I have other computers running Windows XP. If the answer doesn't apply to all current versions of Firefox on all supported Windows operating systems, please explain the differences. Is there a formula for calculating the best cache size?

    I found that the best idea is to let Firefox decide that itself.

  • 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"?

  • 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

  • Migrating SYSTEM tablespace from DMTS to LMTS in Oracle 9.2.0.7

    Migrating SYSTEM tablespace from DMTS to LMTS in Oracle 9.2.0.7 using
    brspace -f dbcreate
    SAP version: 4.6C
    Oracle: 9.2.0.7
    OS: AIX 5.3
    BRTools: 6.40(42)    /**  6.40(10) or (12) will be sufficient according to SAP ***/
    IMPORTANT ***************************************
    MUST DO:
    1. Create a Full Backup of your system
    2. Test your Restore and recovery of your backup.
    3. Have a copy of all your tablespaces names on hand
    4. Know your SYS and SYSTEM passwords
    5. Run CheckDB in DB13 to ensure it is completed successfully with no warnings. This reduce the chance of hitting errors in the process
    6. Ensure your UNDO tablespace is big enough
    7. OSS 400241 Problems with ops$ or sapr3 connect to Oracle
    NOTE: OSS 706625(Read this note)
    The migration from a dictionary-managed SYSTEM tablespace to a locally-managed tablespace using the PL/SQL procedure DBMS_SPACE_ADMIN.TABLESPACE_MIGRATE_TO_LOCAL is not supported in the SAP environment.
    In UNIX, logon as ora<sid>
    run command: brspace -f dbcreate
    This command will triggers a Menu. The are seven(7) steps to complete the whole process. Do them in sequence, from step 1 to step 7 faithfully. In Step 1, ensure that your settings of PSAPTEMP, PSAPUNDO etc details such as filenames are correct. The rest I leave it as default and they are fine. Do not change redo log group from 8 to 4 even if you only have 4 redo groups. If not, you might need to restore the system! If the seven steps are complete without errors(warnings is acceptable), congrats. Perform a backup again.
    Problems I encountered that caused me to restore system:
    1./ Problem: I changed the redo group from 8 to 4 and in the later stage after the tablespaces and files are dropped, the system prompted me that 4 is not acceptable! I can't go back then so a restore is performed.
    Solution: Leave the default value 8 as it is
    2./ I was using wireless network and the network breaks thus process breaks.
    Solution: This process in user-interactive and requires you to input confirmation along the way so do it using LAN.
    3./ In the process of dropping  tablespace PSAP<SID>, I encountered:
    BR0301E SQL error -604 at location BrTspDrop-2
    ORA-00601: error occurred at recursive SQL level 1
    ORA-01555: snapshot too old: rollback segment number 22 with name '_SYSSMU22$" too small
    Solution: I have not fixed this yet but I think it is because my PSAPUNDO is too small(800M) so I will increase it to a bigger value e.g. 5GB
    4. Problem: Unable to start sap after successfully migrated. OPS$user problem
    Solution: logon as <sid>adm, run R3trans -x in a directory that <sid>adm has read/write permission. R3trans -x will creates a file call trans.log. Read the details and refer to OSS 400241
    Result: I have successfully performed this on one(1) system and doing this on the another one currently but encounter Problem 3. Will update this further if there are more findings.
    REFERENCE:
    OSS 748434 New BRSPACE function "dbcreate" - recreate database
    OSS 646681 Reorganizing tables with BRSPACE
    OSS 541538 FAX: Reorganizations
    Message was edited by:
            Annie Chan
    Message was edited by:
            Annie Chan
    Message was edited by:
            Annie Chan

    The current one I am implementing is a development system. The database is less than 100GB. 800MB of PSAPUNDO is sufficient for our development usage.
    Follow up on Problem 3:
    I created another undo tablespace PSAPUNDO2(undodata.dbf) with size of 5GB. I switched undo tablespace to PSAPUNDO2 and placed PSAPUNDO(undo.data1) offline. With PSAPUNDO2 online and PSAPUNDO offline, I started brspace -f dbcreate and encountered the error below at Step 2 Export User tablespace:
    BR0301E SQL error -376 at location BrStattabCreate-3
    ORA-00376: file 17 cannot be read at this time
    ORA-01110: data file 17: '/oracle/DVT/sapdata1/undo_1/undo.data1'
    ORA-06512: at 'SYS.DBMS_STATS", line 5317
    ORA-06512: at line 1
    I aborted the process and verified that SAP is able to run with this settings. I started CheckDB in DB13 and it shows me these messages:
    BR0301W SQL error -376 at location brc_dblog_open-5
    ORA-00376: file 17 cannot be read at this time
    ORA-01110: data file 17: '/oracle/DEV/sapdata1/undo_1/undo.data1'
    BR0324W Insertion of database log header failed
    I don't understand then. I have already switched the undo tablespace from PSAPUNDO to PSAPUNDO2. Why the message above still appears? Once I put PSAPUNDO online, CheckDB completes successfully without warning.
    I did show parameter undo_tablespace and the result is PSAPUNDO2(5GB).
    So exactly, what's going on? Can anyone advise?
    ===============================================
    I have managed to clear the message in DB13 after dropping PSAPUNDO tablespace including contents and datafiles. This is mentioned is OSS note 600141 pg 8 as below:
    Note: You cannot just set the old rollback-tablespace PSAPROLL to offline instead of deleting it properly. This results in ORA-00376 in connection with ORA-01110 error messages. PSAPROLL must remain ONLINE until it is deleted. (Oracle bug 3635653)
    Message was edited by:
            Annie Chan

  • Setting the size of a tablespace prior to its creation

    Hi guys,
    Oracle version: 10.2.0.x
    OS: Windows 32bit
    I was wondering if there are any 'conditions' in setting the intial size of a tablespace prior to its creation. This is because, one of our customers wants to export and import from one schema into another but set an initial size for a tablespace during its creation and prior to importing data into it, but we have a database wizard tool that creates the accounts/schemas by using the following underlying sql:-
    CRETE TABLESPACE <tbl_name> datafile <path><datafile_name>.dbf SIZE 100M AUTOEXTEND ON NEXT 100M MAXSIZE 32000M DEFAULT STORAGE (INITIAL 256 NEXT 256K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0) ONLINE;
    Under normal circumstances, what he would do is to use our wizard tool and create an account and then import data from an export dump.
    But he wants to create a tablespace using a SQL something like:-
    CRETE TABLESPACE <tbl_name> datafile <path><datafile_name>.dbf SIZE 2000M AUTOEXTEND ON NEXT 500M MAXSIZE 32000M DEFAULT STORAGE (INITIAL 256 NEXT 256K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0) ONLINE;
    He thinks this should be ok because his export dump would be on size 2GB and would want to import all of that 'at once' i.e. without actually using autoextend feature for the first 2GB.
    Does this make any sense? Do you guys see any difference 'performance-wise' between the 2 create tablespace statements?
    I think the second sql (with size 2000M initially) seems to be a more logical approach but I am not really sure of the implications going down the line performance-wise.
    Any help/input much appreciated!
    Thanks guys

    1) Provide the facility in your tool to change the default size of datafiles and keep autoextend off.You won't believe it...we had this option in a previous version but now it isn't there anymore!
    But why turning off AUTOEXTEND? I mean, our customers are not meant to modify anything in the database other than via using our software, hence we would want our customers to just use the software as it is but have their DBAs monitor the growth of any datafiles etc...
    2) Let your tool do what it is doing and then manually increasing the size of the datafiles and making autoextend off once you have created the tablespace and before doing import. This can be done by your tool or loggin to the database.We could do this, but we don't want our customers to manually finger the database as they are/might not be Oracle-efficient and wouldn't want production systems to crash for the same reason.
    Hence we could just give them the SQL to be replaced with the 'default' one and then create a tablespace via the tool which would create a tablespace with an initial size of 2GB+ and with greater autoextend facility (such as autoextend on 500M) rather than 100M so that there are fewer autoextends.
    Also, in your point 2, are you saying to turn off autoextend only for the import and set it back on by alter tablespace....?
    Thank you.

  • SYSTEM tablespace is growing fast in 10g

    Hi,
    Using 10.2.0.1.0 on Linux
    My SYSTEM tablespace is growing much faster on 10g than it was on 9i, in 2 month it went from 350mb to 500mb, I don't to add more disk, incase there are issues with my database, I want to know why it is growing.
    I have read docs on why SYSAUX grows on 10g but not SYSTEM.
    SYSTEM size - 500 mb
    Schema/size on System are:
    SYS______455.8125 mb
    SYSTEM______15.25 mb
    OUTLN______0.5 mb
    In this database I only have 1 very large schema that is 200 GB
    Any ideas, reasons, shall I increase it 700mb?
    In 9i my SYSTEM tablespace was very static.
    Thanks for any help.

    Are you using Oracle's audit feature, either standard or FGA? If you were using standard auditing before moving to 10g check that the purge task is still running successfully.
    Verify that no users have their temp tablespace set to system. If is still possible for this to happen on 10g.
    HTH -- Mark D Powell --

  • 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

  • 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

  • Private strand flush not complete how to find optimal size of redo log file

    hi,
    i am using oracle 10.2.0 on unix system and getting Private strand flush not complete in the alert log file. i know this is due to check point is not completed.
    I need to increase the size of redo log files or add new group to the database. i have log file switch (checkpoint incomplete) in the top 5 wait event.
    i can't change any parameter of database. i have three redo log group and log files are of 250MB size. i want to know the suitable size to avoid problem.
    select * from v$instance_recovery;
    RECOVERY_ESTIMATED_IOS     ACTUAL_REDO_BLKS     TARGET_REDO_BLKS     LOG_FILE_SIZE_REDO_BLKS     LOG_CHKPT_TIMEOUT_REDO_BLKS     LOG_CHKPT_INTERVAL_REDO_BLKS     FAST_START_IO_TARGET_REDO_BLKS     TARGET_MTTR     ESTIMATED_MTTR     CKPT_BLOCK_WRITES     OPTIMAL_LOGFILE_SIZE     ESTD_CLUSTER_AVAILABLE_TIME     WRITES_MTTR     WRITES_LOGFILE_SIZE     WRITES_LOG_CHECKPOINT_SETTINGS     WRITES_OTHER_SETTINGS     WRITES_AUTOTUNE     WRITES_FULL_THREAD_CKPT
    625     9286     9999     921600          9999          0     9     112166207               0     0     219270206     0     3331591     5707793please suggest me or tell me the way how to find out suitable size to avoid problem.
    thanks
    umesh

    How often should a database archive its logs
    Re: Redo log size increase and performance
    Please read the above thread and great replies by HJR sir. I think if you wish to get concept knowledge, you should add in your notes.
    "If the FAST_START_MTTR_TARGET parameter is set to limit the instance recovery time, Oracle automatically tries to checkpoint as frequently as necessary. Under this condition, the size of the log files should be large enough to avoid additional checkpointing due to under sized log files. The optimal size can be obtained by querying the OPTIMAL_LOGFILE_SIZE column from the V$INSTANCE_RECOVERY view. You can also obtain sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control."
    Source:http://download-west.oracle.com/docs/cd/B13789_01/server.101/b10752/build_db.htm#19559
    Pl also see ML Doc 274264.1 (REDO LOGS SIZING ADVISORY) on tips to calculate the optimal size for redo logs in 10g databases
    Source:Re: Redo Log Size in R12
    HTH
    Girish Sharma

Maybe you are looking for