Temp usage in system tablespace

Hi
I have oracle 9i with dictionary managed tablespaces.
I have put a trigger to capture sql statement which cause temp errors.
Recently, I have found out that the below sql cause:
ORA-1652: unable to extend temp segment by 5394 in tablespace SYSTEM
select distinct i.*
from PREM i, Summ p
WHERE i.Contract_Branch_Id = p.Pol_Branch_Id
AND i.Product_Code = p.Product_Code
AND i.Contract_Pol_No = p.Pol_No
AND p.Transaction_Type = 'V23'
AND p.Accounting_Prd IN
(TO_NUMBER(TO_CHAR(ADD_MONTHS(SYSDATE, -1),'YYYYMM')), TO_NUMBER(TO_CHAR(SYSDATE, 'YYYYMM')))My question is, how come such a sql uses temp segments in System tablespace rather than normal temp tablespace ?

in sqlplus do the following
SET AUTOTRACE TRACEONLY EXPLAIN STATISTICS
select distinct i.*
from PREM i, Summ p
WHERE i.Contract_Branch_Id = p.Pol_Branch_Id
AND i.Product_Code = p.Product_Code
AND i.Contract_Pol_No = p.Pol_No
AND p.Transaction_Type = 'V23'
AND p.Accounting_Prd IN
(TO_NUMBER(TO_CHAR(ADD_MONTHS(SYSDATE, -1),'YYYYMM')), TO_NUMBER(TO_CHAR(SYSDATE, 'YYYYMM')))
post FORMATTED results back here

Similar Messages

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

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

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

  • Does rebuild of indexes uses temp tablespace or system tablespace?

    Does rebuild of indexes uses temp tablespace or system tablespace?
    If so why?

    If you combine the answers from Aman and Burleson, they cover most of the picture.
    When rebuilding an index, you may end up sorting a large amount of information. The sort may spill into the temporary tablespace - if you haven't configured your database and users properly, it is possible that the SYSTEM tablespace may be used for the temporary tablespace.
    As the new copy of the index is built, it has to be built in the right place (tablespace), and the space used to build it will be marked as a temporary segment as the build takes place. When the build is complete, this temporary segment will take on the name of the origrinal index, and the original index will be re-badged as a temporary segment and dropped. (Again, you might see temporary segments in the SYSTEM tablespace if the index was originally in, or was rebuilt into, the SYSTEM tablespace).
    Regards
    Jonathan Lewis
    http://jonathanlewis.wordpress.com
    http://www.jlcomp.demon.co.uk

  • Temp tablespace + system tablespace

    Is there any difference between adding datafiles in user tables and temp or system tablespace?

    at your leisure,
    CREATE TEMPORARY TABLESPACE MYTEMP
    TEMPFILE '/oradata/data/temp'
    SIZE 250M AUTOEXTEND ON next 256K maxsize 1000M
    Extent management local
    Uniform size 256K;
    Thanks,
    Z

  • System Tablespace unexpected usage

    Hi
    this is my Oracle version:
    Oracle9i Enterprise Edition Release 9.0.1.1.1 - Production.
    The problem I'm having is that my System tablespace fills up quicker than expected (for example 500mb in less than a week and it is not a very 'buisy' server either) and it does not reduce in size.
    No other user objects use the system table-space.
    I have a separate Temp tablespace.
    I am aware of the Autoextend parameter.
    Can anyone please explain why this happens and what can be a solution.
    Thank you.

    Thanks Virag for ur suggestions.
    I have tried to do this:
    SQL> VARIABLE total_blocks NUMBER
    SQL> VARIABLE total_bytes NUMBER
    SQL> VARIABLE unused_blocks NUMBER
    SQL> VARIABLE unused_bytes NUMBER
    SQL> VARIABLE lastextf NUMBER
    SQL> VARIABLE last_extb NUMBER
    SQL> VARIABLE lastusedblock NUMBER
    SQL> exec DBMS_SPACE.UNUSED_SPACE('SCOTT', 'EMP', 'TABLE', :total_blocks, -
    :total_bytes,:unused_blocks, :unused_bytes, :lastextf, -
    :last_extb, :lastusedblock);and got a result.
    But how do I do the same for the SYSTEM tablespace.
    And, is there any other way to monitor the SYSTEM tablespace growth?
    Thank You.

  • System Tablespace Usage

    Hi to all,
    I am a bit new to DBA admin and have was wondering how I can see what size each table is in the System Tablespace and list them in order of size?
    Thanks to all that reply

    sybrand_b wrote:
    select t.owner, t.table_name, s.bytes/1024 kb
    from dba_segments s inner join dba_tables t
    on (s.segment_name = t.table_name)
    order by 3 desc;
    Wrong.
    Joiining dba_tables to dba_segments eliminates information about lots of things that the user may want to see, for example:
    <ul>
    Index organized tables - their data segments have an index component and an overflow component, and only the overflow appears from this query.
    Nested tables (holding data from tables with columns of type table) disappear from this view
    Tables in clusters - the segment_name is the cluster name (and the clusters in the system tablespace can be big).
    LOB segments - shouldn't space due to the LOB columns in the tables be reported as well ? They don't show up in dba_tables, so will disappear from this report.
    </ul>
    To the OP.
    If you want detailed information about space usage in the SYSTEM tablespace it's not a trivial task. A starting point is simply to list the segments allocated in the tablespace. If you want to drill down from their, you need to know what the segment type represents and where it comes from. For more detail you may then want to consider how much of the space inside the segment has been used and how much may have been overallocated.
    Start with something simple like:
    column segment_name format a32
    select
         owner, segment_name, segment_type, bytes/1024 kb
    from
         dba_segments
    where
         tablespace_name = 'SYSTEM'
    order by
         kb desc,
         owner
    ;Regards
    Jonathan Lewis
    http://jonathanlewis.wordpress.com
    http://www.jlcomp.demon.co.uk
    To post code, statspack/AWR report, execution plans or trace files, start and end the section with the tag {noformat}{noformat} (lowercase, curly brackets, no spaces) so that the text appears in fixed format.
    "There's no sense in being precise when you don't even know what you're talking about"
    John von Neumann                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Problem with purge temp and system tablespace

    hi,
    i am purging tablespec with sys user and it seems doing it, but tablespaces are still full
    also wanted to drop a datafile
    alter tablespace system drop
    datafile 'C:\oraclexe\files\sys.bf'
    and it giving the following error
    Error starting at line 28 in command:
    alter database datafile 'C:\oraclexe\files\sys.bf' offline drop
    Error report:
    SQL Error: ORA-01541: system tablespace cannot be brought offline; shut down if necessary
    01541. 00000 - "system tablespace cannot be brought offline; shut down if necessary"
    *Cause:    Tried to bring system tablespace offline
    *Action:   Shutdown if necessary to do recovery
    but if i shutdown how i drop it? or delete manually the file?
    sorry for the 2 question in one thread
    thanks

    but if i shutdown how i drop it? or delete manually the file?Operate in MOUNT state.
    But If you need to resize your system tablespace, You have to check HWM.
    On XE, I think it's easy to use full exp -> recreate -> full imp..
    Regards,

  • Shrink system tablespace, or any laternate to reduce disk space usage!

    Dear All,
    My Database is 11gR1 and Linux is the operating system.
    My System tablespace is consuming 24,000 MB disk space, The user i have created that contain all the objects is another tablespace.
    I just want to know is there any way to shrink system tablespace or anything else that can be done to reduce its size?
    Plus what are the directories from where we can delete logs and other files that do not affect the running of database. My disk space is 99% full and i have to delete files.
    Regards, Imran

    misterimran wrote:
    Dear All,
    My Database is 11gR1 and Linux is the operating system.
    My System tablespace is consuming 24,000 MB disk space, The user i have created that contain all the objects is another tablespace.
    I just want to know is there any way to shrink system tablespace or anything else that can be done to reduce its size?
    Plus what are the directories from where we can delete logs and other files that do not affect the running of database. My disk space is 99% full and i have to delete files.
    Regards, ImranFirst, do this:
    sql> select distinct owner from dba_segments where tablespace_name = 'SYSTEM';Make sure the only objects in the SYSTEM ts are owned by legit users of that ts - SYS, SYSTEM, and OUTLN
    As for log files .. look at your listener log. look at your alert log. look at any trace files in adump, bdump and udump that are old enough you don't want them any more.

  • System tablespace space not regained when objects are dropped

    Mine is a Oracle 10g 10.2 on windows.
    I am importing a export file into a user ,It takes some amount of space in SYSTEM and another tablespace .When I drop the user space in system tablespace is not coming back. ANY IDEA WHY
    BEFORE IMPORT
    SQL> select sum(bytes)/1024/1024 from dba_segments where owner='SYSTEM';
    SUM(BYTES)/1024/1024
    22.1875
    SQL> select sum(bytes)/1024/1024 from dba_segments where owner='SYS';
    SUM(BYTES)/1024/1024
    544.1875
    SQL> select sum(bytes)/1024/1024 from dba_segments where segment_name='SOURCE$';
    SUM(BYTES)/1024/1024
    41
    I use the following commands to import
    SQL>create user <username> identified by <password> default tablespace <tsname> quota unlimited on <tsname>;
    SQL>grant create session,imp_full_database to <username>;
    imp system file=filename.dmp log=logname.log fromuser=<username> touser=<username> statistics=none
    AFTER IMPORT
    SQL> select sum(bytes)/1024/1024 from dba_segments where segment_name='SOURCE$';
    SUM(BYTES)/1024/1024
    53
    SQL> select sum(bytes)/1024/1024 from dba_segments where owner='SYSTEM';
    SUM(BYTES)/1024/1024
    22.1875
    SQL> select sum(bytes)/1024/1024 from dba_segments where owner='SYS';
    SUM(BYTES)/1024/1024
    728.375
    AFTER DROPPING THE USER/SCHEMA
    SQL> select sum(bytes)/1024/1024 from dba_segments where owner='SYS';
    SUM(BYTES)/1024/1024
    728.375
    SQL> select sum(bytes)/1024/1024 from dba_segments where owner='SYSTEM';
    SUM(BYTES)/1024/1024
    22.1875
    SQL> select sum(bytes)/1024/1024 from dba_segments where segment_name='SOURCE$';
    SUM(BYTES)/1024/1024
    53
    I even tried deleting the objects first and then dropping the user
    SQL> delete from source$ where obj# in(select object_id from dba_objects where owner='USERNAME');
    211252 rows deleted.
    SQL> commit;
    Commit complete.
    SQL> drop user USERNAME cascade;
    User dropped.
    The space used by the schema on system tablespace is not coming back.

    Hi user509593!
    Adding objects to a tablespace requires space in that tablespace. This space is managed in segments and extents. If an extent is fully used (that means 100 % usage) a new extent will be added to a segment. Oracle uses a mechanism called "High Water Mark" to mark the last used extent.
    Your problem is that oracle don't set this High Water Mark back if you are dropping objects from a tablespace. Once an extent is marked as it it retains marked as used.
    Before Adding Objects:
    u = used Extent
    x = free Extent
    | = High Water Mark
    uuuuuuxxxxx
    ...........|
    After Adding Objects:
    uuuuuuuxxxx
    ............|
    After dropping objects:
    uuuuuuuxxxx
    ............|
    The only chance to get your "unused" space back is to reorganized your tablespace. But before you reorganize something please read the documentation to know all about the costs and traps that comes with reorganization.
    Hope this help!
    null

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

  • 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

  • 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

  • SYSTEM tablespace extend issue

    Hello, I am migrating from 8.1.7 to 9i and I got following error:
    ORA-1652: unable to extend temp segment by 3200 in tablespace SYSTEM
    As part of migration I added a new data file to system with 100 MB. So in total I have 250 MB of SYSTEM tablespace. Can someone tell mw what I can do?
    thanks
    Suresh

    I have 6 other dBs in 9i and I want to bring all dBs to same level before moving to 10g. Plan is to upgrate to 10g by end of this year.
    Can I just add more space and restart the migration or do I need to restore a backup copy and then start the migration?
    thanks
    Suresh

  • System tablespace 92% full

    Oracle 9.2.0.1
    Linux 7.3
    I am on a test machine.
    The system tablespace is 92%full.Is it an appropriate value?
    What should be the size of the system tablespace?
    I checked in DBA_USERS,all users have users tablespace ,few system users have system tablespace as there default tablespace.There is a separate temp tablespace for temporary segments.

    few system users have system tablespace as there default tablespacei think the OP mentioned users are the one that are created during the creation of database
    Once the user has been assigned a tablesapce ..whatever he creates after that by default will be created under the default tablesapce unless it is redirected to use a different tbs provided he has the privilge on that

Maybe you are looking for

  • I need to display a keynote on 2 flat screens with my MacBook Air via hdmi. I am not sure how to do it.

    I Am giving a presentation and was just informed that I will be using 2 flat screen tvs as my monitors and I need to use hdmi cables. I am lost as to how to do this. I know there is a thunderbolt to hdmi adapter but is there a splitter so I can put i

  • How to chnage the row text in report

    Hi We have a  tailored requirement. Kindly help me out. In our report , the rows are defined and it has characteristic Account number ( GL ) . In our report GL  we want to change the description of rows ( GL account number ) for non account user. So

  • Reply-All Adds Me to the "cc" Line and I Don't Want This

    When I select "Reply All" on an e-mail in iPhone, my name gets added to the "cc" list automatically (not the bcc list). In order to prevent myself from receiving my own reply in my Inbox, I have to delete my name from the "cc" line. Is there a way to

  • User/connection list

    is it possible to get a list from the router to see what is connected to it? (wrt54G) i see the dhcp list..but it lists only 2 computers and i can communicate with a gaming adapter that is out there but does not show up on the list. 

  • Compiling custom.pll requires an outage?

    Hi, We need to compile the custom.pll in production. Does this require an outage to do that? What is the impact of compiling custom.pll without an outage? -Ritesh