Temporary tablespace and alert log

If a temporary tablespace is actually filled and users get error when they are running some query, will it be updated in the alert log?
Thanks

It is ora-01652, and will be written to alert,
Thanks

Similar Messages

  • High redo, log.xml and alert log generation with streams

    Hi,
    We have a setup where streams and messaging gateway is implemented on Oracle 11.1.0.7 to replicated the changes.
    Until recently there was no issue with the setup but for last few days there is an excessive amount of redo and log.xml and alert log generation, which takes up about 50gb for archive log and 20 gb for the rest of the files.
    For now we have disabled the streams.
    Please suggest the possible reasons for this issue.
    Regards,
    Ankit

    Obviously, as no one here has access to the two files with error messages, log.xml and alert log, the resolution starts with looking into those files
    and you should have posted this question only after doing this.
    Now no help is possible.
    Sybrand Bakker
    Senior Oracle DBA

  • Swap, temporary tablespace and sort operations

    Hello.
    I have an Oracle 8.1.7 on Linux RH7.1. I see a very interesting situation: when users begin to execute large selects with many sorts operation swapping grows, but temporary tablespace does'nt grow. As I know, when Oracle has no memory to use as "sort_area_size" it uses temporary tablespace. But looks like that when Oracle ask for memory Linux begin to swap (in order to give memory for Oracle). I mean that Oracle don't use temporary tablespace but use swap instead of it. Is it true? Is it problem? Is it Oracle, Linux or my own configuration bug? Is it better to use swap or to use temporary tablespace? What is faster?
    Thanx for all advises and ideas. ANd sorry for pure English

    login to your database as DBA (SYS AS SYSDBA) and issue the following query:
    SQL> select name, value from v$parameter where name = 'sga_max_size' ;
    see the value defined for this parameter. If this is larger than what you have configured as your SGA size,
    Oracle will assume that it can expand the SGA to "sga_max_size" value, and will try to expand the SGA when
    required. This will result in Oracle asking more memory from the linux kernel and then linux starts to use
    the swap space.
    Try changing the value of this parameter and see if it helps.

  • Temporary Tablespace and transactions

    Hi.
    I have a query regarding temp tablespace ,
    I am on 10gR2 version. with ONE TEMP tablespace and having one tempfiles.
    temp Tablespace TEMP1 = temp01.dbf (1 GB)
    + Let say I have executed a query-1 from Scott user , its runs for 30 min and let assume its consumed 900MB of tempspace during its completion .
    + And another query -2 from scott or another user fired ( let say Query 1 started earlier than Query 2 ) . and it needs around 500MB of tempspace
    == MY Question is
    Q .1 ) Will the Second Query waits until Query 1 completion ? As we have only one Temp file over here . IF both started executing both Queries will hit unable o extend temp space error .
    - Please provide your inputs and corrections.
    -Thanks.

    TEMP Tablespace size : 1GB NO AutoExtend
    First Query uses 900MB
    Second Query starts using space and will eventually need 500MB space
    Both queries will concurrently be allowed to use Temp Space
    If the first query completes before the second query usage hits 100MB, it will release all 900MB for usage by the second query.
    If the first query hasn't completed and is at 900MB, the second query will error out when it attempts to go beyond 100MB.
    If the first query needs more than 900MB and the second query has used 100MB -- i.e. both are growing in usage -- any one of the two queries wil fail.
    NOTE : If Resumable Space Allocation has been enabled either by setting RESUMABLE_TIMEOUT or by ALTER SESSION ENABLE RESUMABLE, the queries will not fail if the TEMP Tablespace is resized within the timeout period. Else, beyond the timeout, either of the queries will fail.
    Hemant K Chitale
    Edited by: Hemant K Chitale on Feb 13, 2013 4:17 PM
    Added Note on Resumable Space Allocation

  • Temporary tablespace and tempfile

    Hi,
    On one of our database, we have a temporary tablespace which is locally managed.
    This tablespace has 3 tempfiles.
    One query, which generate large sort, cause an Oracle error ORA-01652.
    But, when we see the date of tempfiles, it seems that there is only one tempfile which is use :
    rw-rw-rw-   1 iov816   fraud    31465472 Jun  6 18:10 temp2riskv5r.dbf
    -rw-rw-rw-   1 iov816   fraud    20979712 Jun  6 18:14 temp3riskv5r.dbf
    -rw-rw-rw-   1 riskv5r  fraud    152047616 Jun  8 14:47 tempriskv5r.dbf What happens exactly ? This database is a 8.1.6.0.
    Thanks for any explanations.
    Nicolas.

    When using OMF you do not not specify the file names. ASM does not really change the syntax any.
    SQL> create tablespace test_me
      2  datafile size 10m,
      3           size 10m
      4  extent management local uniform size 1m;
    Tablespace created.
    SQL> select file_name from dba_data_files where tablespace_name = 'TEST_ME';
    FILE_NAME
    +TESTDB/sandbox/datafile/test_me.1101.615385691
    +TESTDB/sandbox/datafile/test_me.1097.615385693
    SQL>

  • Recovery lost  undo tablespace and Redo log

    Recovery undo tablespace
    [email protected]> shutdown
    Database closed.
    Database dismounted.
    ORACLE instance shut down.e
    [email protected]> exit
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.1.0 - Production
    [ora920@tkyte-pc-isdn ora920]$ ls
    control01.ctl cwmlite01.dbf indx01.dbf redo02.log redo0B.log temp01.dbf
    users01.dbf
    control02.ctl drsys01.dbf odm01.dbf redo03.log redo0C.log tools01.dbf
    xdb01.dbf
    control03.ctl example01.dbf redo01.log redo0A.log system01.dbf undotbs01.dbf
    [ora920@tkyte-pc-isdn ora920]$ mv undotbs01.dbf undotbs01.dbf.xxx
    [ora920@tkyte-pc-isdn ora920]$ sqlplus /nolog
    SQL*Plus: Release 9.2.0.1.0 - Production on Sat Sep 28 08:33:29 2002
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    idle> connect / as sysdba
    Connected to an idle instance.
    idle> startup
    ORACLE instance started.
    Total System Global Area 143725064 bytes
    Fixed Size 451080 bytes
    Variable Size 109051904 bytes
    Database Buffers 33554432 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: '/usr/oracle/ora920/OraHome1/oradata/ora920/undotbs01.dbf'
    idle> show parameter undo
    NAME TYPE VALUE
    undo_management string AUTO
    undo_retention integer 10800
    undo_suppress_errors boolean FALSE
    undo_tablespace string UNDOTBS1
    idle> alter system set undo_management = manual scope=spfile;
    System altered.
    Note: disabling the undo tablespace here, this'll let us go back to "rollback segments"
    and we'll use the system RBS to get back on our feet
    idle> shutdown
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    idle> exit
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.1.0 - Production
    [ora920@tkyte-pc-isdn ora920]$ !sql
    sqlplus /nolog
    SQL*Plus: Release 9.2.0.1.0 - Production on Sat Sep 28 08:35:34 2002
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    idle> connect / as sysdba;
    Connected to an idle instance.
    idle> startup
    ORACLE instance started.
    Total System Global Area 143725064 bytes
    Fixed Size 451080 bytes
    Variable Size 109051904 bytes
    Database Buffers 33554432 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: '/usr/oracle/ora920/OraHome1/oradata/ora920/undotbs01.dbf'
    Note: we still have to get rid of that thing..
    idle> alter database datafile '/usr/oracle/ora920/OraHome1/oradata/ora920/undotbs01.dbf'
    2 offline drop;
    Database altered.
    idle> alter database open;
    Database altered.
    idle> drop tablespace undotbs1;
    Tablespace dropped.
    idle> create UNDO tablespace undotbs1
    2 datafile '/usr/oracle/ora920/OraHome1/oradata/ora920/undotbs01.dbf' size 25m
    3 autoextend on next 1m maxsize 1024m;
    Tablespace created.
    idle> alter system set undo_management = auto scope=spfile;
    System altered.
    Now, we've put the undo tablespace "back" by creating a new one. Just bounce...
    idle> shutdown
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    idle> exit
    Disconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.1.0 - Production
    [ora920@tkyte-pc-isdn ora920]$ !sql
    sqlplus /nolog
    SQL*Plus: Release 9.2.0.1.0 - Production on Sat Sep 28 08:40:51 2002
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    idle> connect / as sysdba;
    Connected to an idle instance.
    idle> startup
    ORACLE instance started.
    Total System Global Area 143725064 bytes
    Fixed Size 451080 bytes
    Variable Size 109051904 bytes
    Database Buffers 33554432 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    Database opened.
    idle> show parameter undo
    NAME TYPE VALUE
    undo_management string AUTO
    undo_retention integer 10800
    undo_suppress_errors boolean FALSE
    undo_tablespace string UNDOTBS1
    idle>
    and we are right back where we started from
    RECOVERY REDO TABLESPACE
    STARTUP MOUNT;
    RESTORE DATABASE;
    RECOVER DATABASE UNTIL SEQUENCE $v_seq THREAD 1;
    ALTER DATABASE OPEN RESETLOGS;

    [email protected] wrote:
    just ignore first one like title
    Alter database open resetlog is not necessary to open database ?
    Regards
    kmphttp://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/osrecov.htm#i1007426
    About Opening with the RESETLOGS Option
    The RESETLOGS option is always required after incomplete media recovery or recovery using a backup control file.
    You did not do an incomplete media recovery nor a recovery using a backup control file.

  • Removing alert logs and trace files

    Hi everyone!
    I noticed that in all the oracle databases, the trace files are piling and alert log is growing like anything ....
    Thought of making a copy of the trace files somewhere and remove them from the hard disk excluding the most recent ones.
    For alert log, thought of making a copy and renaming the current file so that Oracle can create a new one.
    Any advice if there are better approaches in handling this?
    Thanks in advance.

    user645399 wrote:
    Hi everyone!
    I noticed that in all the oracle databases, the trace files are piling and alert log is growing like anything ....
    Thought of making a copy of the trace files somewhere and remove them from the hard disk excluding the most recent ones.
    For alert log, thought of making a copy and renaming the current file so that Oracle can create a new one.
    Any advice if there are better approaches in handling this?
    Thanks in advance.I would include the alert log file in my backup strategy as it includes many important information; database parameter values,when and how the database was shut down, the important database errors and when they occur , etc ... I usually backup the alert log file once a month and keep 1 year of alert log file copies..

  • Temporary Tablespace Sizing and SNOTE 164925

    Hi All,
    I am facing a dilemma when I look into the temporary tablespace setting.
    I have gone thru the SNOTE 164925, for the sizing parameters of PSAPTEMP.
    There is a calculation on the note for selecting initial extent next extent etc.....
    My PSAPTEMP is locally managed and having default initial extent value of 1 MB but as per the calculation given on SNOTE 164925 solution section.
    But the point is in the How Can I check the specified value section on the same note it says....
    "As of Oracle 8i, SAP recommends using the assignment of locally managed
    temporary tablespaces (see Notes 659946 and 662900). This means that when
    problems with a 'dictionary managed' temporary tablespace occur, you should
    change to a 'locally managed' temporary tablespace instead of optimizing
    the settings of the 'dictionary managed' temporary tablespace."
    Now my question is whther I should still go with the default value or with the new values as per the formula given in the same note.
    I am using Oracle 10g behind SAPR3 4.6D
    Regards,
    Soumen

    Hello Soumen,
    to be honest - i don't really understand your question / problem.
    Just use locally managed temporary tablespace and set an uniform size.
    The values initial, next and pctincrease doesn't matter in this case. Set the uniform size to 1 - 5 MB.
    As you told us you are using oracle 10g .. just check the documenation:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_7003.htm#CJAIDDDB
    Specify LOCAL if you want the tablespace to be locally managed. Locally managed tablespaces have some part of the tablespace set aside for a bitmap. This is the default for permanent tablespaces. Temporary tablespaces are always automatically created with locally managed extents.
    AUTOALLOCATE specifies that the tablespace is system managed. Users cannot specify an extent size. You cannot specify AUTOALLOCATE for a temporary tablespace.
    UNIFORM specifies that the tablespace is managed with uniform extents of SIZE bytes.The default SIZE is 1 megabyte. All extents of temporary tablespaces are of uniform size, so this keyword is optional for a temporary tablespace. However, you must specify UNIFORM in order to specify SIZE. You cannot specify UNIFORM for an undo tablespace.
    Restriction on Dictionary-managed Tablespaces
    You cannot specify DICTIONARY if the SYSTEM tablespace of the database is locally managed or if you have specified the temporary_tablespace_clause.
    Regards
    Stefan

  • Parallel execution and temporary tablespaces

    I have a large long running (1 hour) data warehouse query in a materialized view.
    If I parallelize it using the parallel hint then I run out of temporary tablespace.
    I've tried creating a bunch of temporary tablespaces and putting them into a temp tablespace group but it still runs out of space. Parallel execution seems to use up way more temp tablespace than sequential execution.
    I know it is a very general question, but what are the tips for parallelizing a long running query with respect to temporary tablespace management?
    I've tried searching on the interwebs but I don't find anything that addresses this particular issue.

    And here is the parallel explain plan:
    PLAN_TABLE_OUTPUT
    Plan hash value: 1293981491
    | Id | Operation | Name | Rows | Bytes |TempSpc| Cost (%CPU)| Time | TQ |IN-OUT| PQ Distrib |
    | 0 | SELECT STATEMENT | | 81M| 17G| | 19232 (2)| 00:00:01 | | | |
    | 1 | TABLE ACCESS BY INDEX ROWID | MART$SC_SCORES | 1 | 13 | | 3 (0)| 00:00:01 | | | |
    |* 2 | INDEX UNIQUE SCAN | SSCS_SDCC_FK_I | 1 | | | 2 (0)| 00:00:01 | | | |
    | 3 | PX COORDINATOR | | | | | | | | | |
    | 4 | PX SEND QC (RANDOM) | :TQ10017 | 81M| 17G| | 19232 (2)| 00:00:01 | Q1,17 | P->S | QC (RAND) |
    |* 5 | HASH JOIN RIGHT OUTER BUFFERED | | 81M| 17G| | 19232 (2)| 00:00:01 | Q1,17 | PCWP | |
    | 6 | PX RECEIVE | | 41925 | 491K| | 2 (0)| 00:00:01 | Q1,17 | PCWP | |
    | 7 | PX SEND BROADCAST | :TQ10014 | 41925 | 491K| | 2 (0)| 00:00:01 | Q1,14 | P->P | BROADCAST |
    | 8 | PX BLOCK ITERATOR | | 41925 | 491K| | 2 (0)| 00:00:01 | Q1,14 | PCWC | |
    | 9 | INDEX FAST FULL SCAN | I_DWH_ZIP_ZIPCODE_EIDIID | 41925 | 491K| | 2 (0)| 00:00:01 | Q1,14 | PCWP | |
    |* 10 | HASH JOIN | | 81M| 16G| | 19218 (2)| 00:00:01 | Q1,17 | PCWP | |
    | 11 | JOIN FILTER CREATE | :BF0000 | 6414K| 159M| | 806 (2)| 00:00:01 | Q1,17 | PCWP | |
    | 12 | PX RECEIVE | | 6414K| 159M| | 806 (2)| 00:00:01 | Q1,17 | PCWP | |
    | 13 | PX SEND HASH | :TQ10015 | 6414K| 159M| | 806 (2)| 00:00:01 | Q1,15 | P->P | HASH |
    | 14 | PX BLOCK ITERATOR | | 6414K| 159M| | 806 (2)| 00:00:01 | Q1,15 | PCWC | |
    |* 15 | INDEX FAST FULL SCAN | I_DWH_ADDRESS_COMB_ZIP | 6414K| 159M| | 806 (2)| 00:00:01 | Q1,15 | PCWP | |
    | 16 | PX RECEIVE | | 80M| 14G| | 18397 (2)| 00:00:01 | Q1,17 | PCWP | |
    | 17 | PX SEND HASH | :TQ10016 | 80M| 14G| | 18397 (2)| 00:00:01 | Q1,16 | P->P | HASH |
    | 18 | JOIN FILTER USE | :BF0000 | 80M| 14G| | 18397 (2)| 00:00:01 | Q1,16 | PCWP | |
    |* 19 | HASH JOIN RIGHT OUTER BUFFERED | | 80M| 14G| | 18397 (2)| 00:00:01 | Q1,16 | PCWP | |
    | 20 | PX RECEIVE | | 42M| 409M| | 827 (2)| 00:00:01 | Q1,16 | PCWP | |
    | 21 | PX SEND HASH | :TQ10012 | 42M| 409M| | 827 (2)| 00:00:01 | Q1,12 | P->P | HASH |
    | 22 | PX BLOCK ITERATOR | | 42M| 409M| | 827 (2)| 00:00:01 | Q1,12 | PCWC | |
    | 23 | MAT_VIEW ACCESS FULL | MBI$CMN_ACTION_COST | 42M| 409M| | 827 (2)| 00:00:01 | Q1,12 | PCWP | |
    | 24 | PX RECEIVE | | 80M| 14G| | 17549 (1)| 00:00:01 | Q1,16 | PCWP | |
    | 25 | PX SEND HASH | :TQ10013 | 80M| 14G| | 17549 (1)| 00:00:01 | Q1,13 | P->P | HASH |
    |* 26 | HASH JOIN BUFFERED | | 80M| 14G| | 17549 (1)| 00:00:01 | Q1,13 | PCWP | |
    | 27 | PX RECEIVE | | 6312K| 794M| | 7519 (1)| 00:00:01 | Q1,13 | PCWP | |
    | 28 | PX SEND HASH | :TQ10010 | 6312K| 794M| | 7519 (1)| 00:00:01 | Q1,10 | P->P | HASH |
    |* 29 | HASH JOIN RIGHT OUTER BUFFERED | | 6312K| 794M| | 7519 (1)| 00:00:01 | Q1,10 | PCWP | |
    | 30 | VIEW | | 4443K| 80M| | 2125 (2)| 00:00:01 | Q1,10 | PCWP | |
    | 31 | HASH GROUP BY | | 4443K| 33M| 158M| 2125 (2)| 00:00:01 | Q1,10 | PCWP | |
    | 32 | PX RECEIVE | | 10M| 78M| | 950 (1)| 00:00:01 | Q1,10 | PCWP | |
    | 33 | PX SEND HASH | :TQ10007 | 10M| 78M| | 950 (1)| 00:00:01 | Q1,07 | P->P | HASH |
    | 34 | PX BLOCK ITERATOR | | 10M| 78M| | 950 (1)| 00:00:01 | Q1,07 | PCWC | |
    | 35 | TABLE ACCESS FULL | DWH$PHONE | 10M| 78M| | 950 (1)| 00:00:01 | Q1,07 | PCWP | |
    |* 36 | HASH JOIN | | 6312K| 680M| | 5392 (1)| 00:00:01 | Q1,10 | PCWP | |
    | 37 | PX RECEIVE | | 6329K| 36M| | 130 (2)| 00:00:01 | Q1,10 | PCWP | |
    | 38 | PX SEND HASH | :TQ10008 | 6329K| 36M| | 130 (2)| 00:00:01 | Q1,08 | P->P | HASH |
    | 39 | PX BLOCK ITERATOR | | 6329K| 36M| | 130 (2)| 00:00:01 | Q1,08 | PCWC | |
    | 40 | INDEX FAST FULL SCAN | PK_DWH_DEBTOR | 6329K| 36M| | 130 (2)| 00:00:01 | Q1,08 | PCWP | |
    | 41 | PX RECEIVE | | 6312K| 644M| | 5259 (1)| 00:00:01 | Q1,10 | PCWP | |
    | 42 | PX SEND HASH | :TQ10009 | 6312K| 644M| | 5259 (1)| 00:00:01 | Q1,09 | P->P | HASH |
    |* 43 | HASH JOIN RIGHT OUTER BUFFERED| | 6312K| 644M| | 5259 (1)| 00:00:01 | Q1,09 | PCWP | |
    | 44 | PX RECEIVE | | 3689K| 31M| | 4271 (1)| 00:00:01 | Q1,09 | PCWP | |
    | 45 | PX SEND HASH | :TQ10005 | 3689K| 31M| | 4271 (1)| 00:00:01 | Q1,05 | P->P | HASH |
    | 46 | VIEW | | 3689K| 31M| | 4271 (1)| 00:00:01 | Q1,05 | PCWP | |
    | 47 | HASH GROUP BY | | 3689K| 56M| 84M| 4271 (1)| 00:00:01 | Q1,05 | PCWP | |
    | 48 | PX RECEIVE | | 3689K| 56M| | 3653 (1)| 00:00:01 | Q1,05 | PCWP | |
    | 49 | PX SEND HASH | :TQ10003 | 3689K| 56M| | 3653 (1)| 00:00:01 | Q1,03 | P->P | HASH |
    |* 50 | HASH JOIN | | 3689K| 56M| | 3653 (1)| 00:00:01 | Q1,03 | PCWP | |
    | 51 | BUFFER SORT | | | | | | | Q1,03 | PCWC | |
    | 52 | PX RECEIVE | | 3 | 21 | | 1 (0)| 00:00:01 | Q1,03 | PCWP | |
    | 53 | PX SEND BROADCAST | :TQ10000 | 3 | 21 | | 1 (0)| 00:00:01 | | S->P | BROADCAST |
    | 54 | INLIST ITERATOR | | | | | | | | | |
    |* 55 | INDEX RANGE SCAN | I_DWH_PAYMENT_TYPE_EIDIID | 3 | 21 | | 1 (0)| 00:00:01 | | | |
    | 56 | PX BLOCK ITERATOR | | 28M| 242M| | 3648 (1)| 00:00:01 | Q1,03 | PCWC | |
    |* 57 | TABLE ACCESS FULL | DWH$PAYMENT | 28M| 242M| | 3648 (1)| 00:00:01 | Q1,03 | PCWP | |
    | 58 | PX RECEIVE | | 6312K| 589M| | 986 (2)| 00:00:01 | Q1,09 | PCWP | |
    | 59 | PX SEND HASH | :TQ10006 | 6312K| 589M| | 986 (2)| 00:00:01 | Q1,06 | P->P | HASH |
    |* 60 | HASH JOIN | | 6312K| 589M| | 986 (2)| 00:00:01 | Q1,06 | PCWP | |
    | 61 | PX RECEIVE | | 2937 | 172K| | 5 (20)| 00:00:01 | Q1,06 | PCWP | |
    | 62 | PX SEND BROADCAST | :TQ10004 | 2937 | 172K| | 5 (20)| 00:00:01 | Q1,04 | P->P | BROADCAST |
    |* 63 | HASH JOIN BUFFERED | | 2937 | 172K| | 5 (20)| 00:00:01 | Q1,04 | PCWP | |
    | 64 | PX RECEIVE | | 220 | 1540 | | 2 (0)| 00:00:01 | Q1,04 | PCWP | |
    | 65 | PX SEND HASH | :TQ10001 | 220 | 1540 | | 2 (0)| 00:00:01 | Q1,01 | P->P | HASH |
    | 66 | PX BLOCK ITERATOR | | 220 | 1540 | | 2 (0)| 00:00:01 | Q1,01 | PCWC | |
    | 67 | TABLE ACCESS FULL | DWH$MANDATOR | 220 | 1540 | | 2 (0)| 00:00:01 | Q1,01 | PCWP | |
    | 68 | PX RECEIVE | | 2937 | 152K| | 2 (0)| 00:00:01 | Q1,04 | PCWP | |
    | 69 | PX SEND HASH | :TQ10002 | 2937 | 152K| | 2 (0)| 00:00:01 | Q1,02 | P->P | HASH |
    | 70 | PX BLOCK ITERATOR | | 2937 | 152K| | 2 (0)| 00:00:01 | Q1,02 | PCWC | |
    | 71 | TABLE ACCESS FULL | DWH$PACKAGE | 2937 | 152K| | 2 (0)| 00:00:01 | Q1,02 | PCWP | |
    | 72 | PX BLOCK ITERATOR | | 6312K| 228M| | 980 (1)| 00:00:01 | Q1,06 | PCWC | |
    | 73 | TABLE ACCESS FULL | DWH$CASE | 6312K| 228M| | 980 (1)| 00:00:01 | Q1,06 | PCWP | |
    | 74 | PX RECEIVE | | 78M| 4199M| | 10016 (1)| 00:00:01 | Q1,13 | PCWP | |
    | 75 | PX SEND HASH | :TQ10011 | 78M| 4199M| | 10016 (1)| 00:00:01 | Q1,11 | P->P | HASH |
    | 76 | PX BLOCK ITERATOR | | 78M| 4199M| | 10016 (1)| 00:00:01 | Q1,11 | PCWC | |
    |* 77 | TABLE ACCESS FULL | DWH$ACTION | 78M| 4199M| | 10016 (1)| 00:00:01 | Q1,11 | PCWP | |
    ------------------------------------------------------------------------------------------------------------------------------------------------------------------

  • Group temporary tablespace

    Greetings,
    oracle 10.2.0.4
    suse linux 9
    we have a group temporary tablespace called ATEMP which contains 9 tablespaces ATEMP01 - ATEMP09
    but the in the alert log we have this warning
    WARNING: the following temporary tablespaces contain no files.
    this condition can occur when a backup controlfile has been restored.
    it may be necessary to add files to these tablespace. that can be done using SQL.....
    alternatively, if these temporary tablesapces are no longer needed, then
    they can be dropped. Empty temporary tablespace: ATEMP
    then I was confirmed on this forum after a question that...in this case oracle is using SYSTEM tablespace
    as a temporary tablespace and this has a performance impact and the system may hung if SYSTEM tbs gets
    full. which I totally agree according to oracle documentation
    and my question for today is
    how can I show to somebody that the current temp segments are in SYSTEM tablesapce because as I run
    the query
    SELECT TABLESPACE_NAME,BYTES_USED,BYTES_FREE FROM V$TEMP_SPACE_HEADER;
    the return show the tablespaces are ATEMP01,ATEMP02....instead of SYSTEM which was my expectation.
    thanks

    thank you
    I just passed the query to the view
    select tablespace,contents from v$tempseg_usage
    and what I found is
    ATEMP02 and TEMPORARY
    now what is contradicting for me is that...the alert log is showing as if ATEMP which is a temporary
    tablespace group is not having a file and we need to add files to it ...which implies that SYSTEM tablespace
    is being used as a residing place for the temp segments but the query returns ATEMP02 as the temporary
    tablesapce where temp segment is residing
    can you help me reconsile this seemingly confusing scenario

  • Online material for tablespace and backup

    Hi All,
    As i am a beginner, can anyone please suggest me any online link for better understanding about tablespace and backup for a beginner.
    Thanks in advance
    Arun

    Hi, follow down a resume did for me in my blog:
    Creating Tablespaces Permanent, Temporary and UNDO in ORACLE
    Tablespace Datafiles is a set that contains the physical structure of the data storage system Operacional.Sendo thus tablespace is an allocation of space used to store objects of a given user. To create a tablespace in a database, the user will have to have the grant (permission) of Tablespace and Create to create the SYSAUX tablespace (beside SYSTEM, are the most important database), should have the grant of SYSDBA. A tablespace is a logical unit of database and that is part of the following structure:
    Database> Tablespace (logical drive)> Datafile (physical file)> Segments (logical drive Example: Tables)> Extents (set of blocks, logical drives) >> Blocks Bank Data (logical unit, a smaller structure database)> Blocks Operating System.
    In this article we will be focused on the following types of tablespaces : The permanent tablespaces, the tablespace temporary tablespace and Undo. However, it also will be elucidated creating tablespace with multiple datafiles at once.
    - Permanent Tablespaces: Contains a user objects in a database. These objects are stored in physical structures called Datafiles.
    SQL> create tablespace TBSEXEBRUNORS
    logging
    datafile '/ dbbruno/datafiles/datafile1.dbf'
    size 64m
    autoextend on
    next 64m maxsize 2048m
    Local extent management uniform size 1m; 2 3 4 5 6 7
    Tablespace created.
    Creating a Tablespace with multiple Datafiles at once:
    SQL> create tablespace TBSMISCBRUNORS
    datafile '/ dbbruno/datafiles/datafile2.dbf' size 4M
    '/ Dbbruno/datafiles/datafile3.dbf' size 4M
    '/ Dbbruno/datafiles/datafile4.dbf' size 4M
    logging
    extent management site; 2 3 4 5 6
    Tablespace created.
    It follows a consultation in view DBA_TABLESPACES:
    SQL> SET PAGESIZE 180
    SQL> SET linesize 180
    SQL> SELECT * FROM WHERE DBA_TABLESPACES tablespace_name = 'TBSEXEMPLO' order by 1,2;
    Tablespace_name BLOCK_SIZE INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS MAX_SIZE PCT_INCREASE MIN_EXTLEN STATUS CONTENTS LOGGING FOR EXTENT_MAN
    ALLOCATIO PLU segments DEF_TAB_ RETENTION BIG PREDICA ENC COMPRESS_FOR
    TBSEXEMPLO 8192 65536 1 2147483645 2147483645 65536 ONLINE PERMANENT LOGGING NO LOCAL
    NO SYSTEM AUTO DISABLED NOT APPLY IN THE HOST
    - Clause for managing EXTENTS
    The autoallocate clause specifies that the tablespace is managed by ORACLE , and that users can not specify sizes. Moreover, this clause is not allowed to UNDO tablespaces or Temporary. However, the clause UNIFORM specifies that the tablespace is managed by a user (you can specify sizes) via byte sizes, the default 1M (megabyte) to use this clause. Already the LOCAL clause specifies that the tablespace is locally managed and some part of the tablespace is reserved for Bitmap, which is the DEFAULT option for the type of permanent tablespace. But the DICTIONARY clause specifies that you want the tablespace is managed using the data dictionary.
    - Management of SEGMENTS clause
    The AUTO clause specifies that you want the ORACLE control the free space of segments in the tablespace using BITMAPS. When making use of this option, ORACLE ignores any storage specification later this tablespace. ORACLE strongly recommends using this option. However, this option should only be used in permanent and never tablespaces in a tablespace SYSTEM. However, the clause MANUAL option is not recommended by Oracle, specifies that you want the ORACLE control the free space of segments in the tablespace using freelists (PCTUSED, FREELIST, FREELIST GROUPS).
    - Temporary Tablespaces: Contains temporary data for a given session for a given period of time. Furthermore, this type of tablespace tempfiles and have no, Datafiles. This tablespace is used when a user, to which was assigned temporary tablespace, begins operations. Thus, the tablespace temporary stores temporary data used in transactions of users.
    SQL> create temporary tablespace TEMPEXEBRUNORS
    tempfile '/ dbbruno/datafiles/tempfile1.dbf'
    size 128m
    autoextend on
    next 32m maxsize 2048m
    extent management site; 2 3 4 5 6
    Tablespace created.
    - UNDO Tablespaces or Tablespaces Undo: Tablespace used for operations redone, so that objects can not be created in this tablespace. When this tablespace is created, the ORACLE tablespace SYSTEM takes for you to make such operations. However, the default is to always create an UNDO tablespace when creating the database, so that it is in the mode of automatic undo management.
    SQL> create undo tablespace TBSUNDOBRUNORS
    datafile '/ dbbruno/datafiles/tbs_datafileundobrunors_1.dbf "
    size 200M; 2 3
    Tablespace created.
    It follows a consultation in view DBA_TABLESPACES:
    SQL> SET PAGESIZE 180
    SET linesize 180
    SELECT tablespace_name, STATUS, RETENTION, SEGMENT_SPACE_MANAGEMENT, EXTENT_MANAGEMENT, INITIAL_EXTENT DBA_TABLESPACES FROM WHERE tablespace_name = 'TBSUNDOBRUNORS' order by 1,2; SQL> SQL>
    STATUS tablespace_name RETENTION segments EXTENT_MAN INITIAL_EXTENT
    TBSUNDOBRUNORS NOGUARANTEE MANUAL ONLINE LOCAL 65,536
    - Clause for retaining segments
    The RETENTION GUARANTEE clause specifies that the data store should ORACLE undo expired, even though current operations return fails due to lack of space. This option can be useful in operations FLASHBACK (which is a "flashback" to obtain, for example, the value from a table that was deleted and it is necessary to know the value of that in a certain period). However, the provision RETENTION NOGUARANTEE (as above) specifies that the ORACLE data undo may replace expired undo by new data being processed due to the operations in the current environment, this being the provision pattern.
    I hope I helped, hugs!!
    References:
    http://brunors.com/?p=208

  • How do i know if my query using  SORT_AREA_SIZE   or temporary tablespace ?

    Good Morning  Everyone !
    My DB version is 10.2.0.1
    I have large table  exactly 3 million records.
    SQL> select count(*) from tab1;
    COUNT(*)
       300000
    SQL> select * from tab1 order by no DESC;
    sorting  ... in process
    300000 rows selected.
    in Terminal 2 : I tried to find  sorting details -   ( No rows  selected - why ? )
    SQL> select USERNAME , USER , TABLESPACE , SQL_ID from v$tempseg_usage  ;
    no rows selected
    SQL> /
    no rows selected
    When i google i have seen this ;
    If  Oracle cannot do the sort in memory  (SORT_AREA_SIZE initialisation parameter), space will be allocated in a temporary tablespace for doing the sort operation.
    REF_LINK : TEMPORARY Tablespaces and TEMPFILES | Oracle FAQ
    MY DOUBT QUESTION :   How do i know if my query using  SORT_AREA_SIZE   or temporary tablespace ?
    Thanks in advance.

    @ JohnWatson
    I have seen some articles from ORA - FAQ. Good.
    SQL> select USERNAME , USER , TABLESPACE , SQL_ID from v$tempseg_usage;
    USERNAME                       USER   TABLESPACE                      SQL_ID
       SCOTT                               SYS          TEMP                            fh9vqgyd6m0d1
    PGA management means that sorting only 300000 rows  may well occur in memory
                Is this (3 million rows) -  standard  value for 10g version ?
    Thanks JohnWatson

  • Shrinking a Locally Managed Temporary Tablespace

    So, even thoguh the documentation is pretty clear about how to use this feature, I cannot get it to do what I expect it to do for me.
    And that would be shrinking the tempfile ;)
    Now lets face it, I have a large tempfile and want to resize it without restarting the database:
    C:\Users\Administrator>sqlplus / as sysdba
    SQL*Plus: Release 11.2.0.2.0 Production on Di Nov 20 05:49:59 2012
    Copyright (c) 1982, 2010, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Release 11.2.0.2.0 - 64bit Production
    SQL> select file_name
    , ceil(bytes / 1024 / 1024) "size MB"
    from dba_temp_files
    FILE_NAME size MB
    R:\MXVC01\TEMP01.DBF 31,231
    SQL> select su.username
    , ses.sid
    , ses.serial#
    , su.tablespace
    , ceil((su.blocks * dt.block_size) / 1048576) MB
    from v$sort_usage su
    , dba_tablespaces dt
    , v$session ses
    where su.tablespace = dt.tablespace_name
    and su.session_addr = ses.saddr
    USERNAME SID SERIAL# TABLESPACE MB
    VPXADMIN 15 15 TEMP 14
    VPXADMIN 17 5 TEMP 1,203
    VPXADMIN 17 5 TEMP 1
    VPXADMIN 18 3 TEMP 7
    VPXADMIN 19 3 TEMP 1
    VPXADMIN 144 3 TEMP 1
    VUMADMIN 156 2597 TEMP 1
    7 rows selected.
    Or this one:
    SQL> select tablespace_size/1024/1024 "tablespace_size mb"
    , allocated_space/1024/1024 "allocated_space mb"
    , free_space/1024/1024 "free_space mb"
    from dba_temp_free_space
    tablespace_size mb allocated_space mb free_space mb
    31230,9922 1228,99219 30002
    Documetation from here: http://docs.oracle.com/cd/E11882_01/server.112/e25494/tspaces007.htm#ADMIN12353
    +"Shrinking a Locally Managed Temporary Tablespace+
    +Large sort operations performed by the database may result in a temporary tablespace growing and occupying a considerable amount of disk space. After the sort operation completes, the extra space is not released; it is just marked as free and available for reuse. Therefore, a single large sort operation might result in a large amount of allocated temporary space that remains unused after the sort operation is complete. For this reason, the database enables you to shrink locally managed temporary tablespaces and release unused space.+
    +You use the SHRINK SPACE clause of the ALTER TABLESPACE statement to shrink a temporary tablespace, or the SHRINK TEMPFILE clause of the ALTER TABLESPACE statement to shrink a specific tempfile of a temporary tablespace. Shrinking frees as much space as possible while maintaining the other attributes of the tablespace or tempfile. The optional KEEP clause defines a minimum size for the tablespace or tempfile.+
    +Shrinking is an online operation, which means that user sessions can continue to allocate sort extents if needed, and already-running queries are not affected.+
    +The following example shrinks the locally managed temporary tablespace lmtmp1 to a size of 20M.+
    +ALTER TABLESPACE lmtemp1 SHRINK SPACE KEEP 20M;+
    +The following example shrinks the tempfile lmtemp02.dbf of the locally managed temporary tablespace lmtmp2. Because the KEEP clause is omitted, the database attempts to shrink the tempfile to the minimum possible size.+
    +ALTER TABLESPACE lmtemp2 SHRINK TEMPFILE '/u02/oracle/data/lmtemp02.dbf';"+
    OK, lets do it:
    SQL> alter tablespace temp shrink tempfile 'R:\MXVC01\TEMP01.DBF';
    alter tablespace temp shrink tempfile 'R:\MXVC01\TEMP01.DBF'
    ERROR at line 1:
    ORA-03214: File Size specified is smaller than minimum required
    It seems there is a bug? Should I report it, or is it the expected behaviour?
    Now lets try this one:
    SQL> alter tablespace temp shrink tempfile 'R:\MXVC01\TEMP01.DBF' keep 2048M;
    Tablespace altered.
    SQL> select file_name
    , ceil(bytes / 1024 / 1024) "size MB"
    from dba_temp_files
    FILE_NAME size MB
    R:\MXVC01\TEMP01.DBF 31,231
    So .... this lasts about *10 minutes*, and nothing changes?
    It seems there is a bug? Should I report it, or is it the expected behaviour?
    Could someone enlighten me, what this SHRINK is actually doing?
    Is it worth to report this as bug, if not a software bug it is at least a documentation bug because it doesn't mention under which conditions it is working?
    P.S.: OMG the posting looks terrible, who's the one to blame for this forum software where it is not possible to use fixed size fonts, or format paragraphs as code, or what about the fact that the forum software is using default SQLPlus output as META for some graphical lines?
    Isn't this the forum for Oracle Database users?
    Edited by: Gerrit Haase on 20.11.2012 13:44

    So, you are kidding with me? No? Who are you?
    How can I block users here? Is there a moderator present at this forum?
    Maybe you read my initial post again?
    I didn't look at the wrong place.
    I reported you for general abuse.
    SQL> define
    DEFINE _DATE           = "20.11.12" (CHAR)
    DEFINE CONNECTIDENTIFIER = "MXVC01" (CHAR)
    DEFINE _USER           = "SYS" (CHAR)
    DEFINE _PRIVILEGE      = "AS SYSDBA" (CHAR)
    DEFINE SQLPLUSRELEASE = "1102000200" (CHAR)
    DEFINE _EDITOR         = "Notepad" (CHAR)
    DEFINE OVERSION = "Oracle Database 11g Release 11.2.0.2.0 - 64bit Production" (CHAR)
    DEFINE ORELEASE = "1102000200" (CHAR)
    SQL> SELECT * FROM dba_temp_free_space;
    TABLESPACE_NAME TABLESPACE_SIZE ALLOCATED_SPACE FREE_SPACE
    TEMP 3,2748E+10 1306517504 3,1443E+10
    SQL> select TABLESPACE_SIZE/power(2,20), ALLOCATED_SPACE/power(2,20), FREE_SPACE/power(2,20) from dba_temp_free_space ;
    TABLESPACE_SIZE/POWER(2,20) ALLOCATED_SPACE/POWER(2,20) FREE_SPACE/POWER(2,20)
    31230,9922 1245,99219 29986
    SQL> ALTER TABLESPACE temp SHRINK SPACE;
    Tablespace altered.
    SQL> select TABLESPACE_SIZE/power(2,20), ALLOCATED_SPACE/power(2,20), FREE_SPACE/power(2,20) from dba_temp_free_space ;
    TABLESPACE_SIZE/POWER(2,20) ALLOCATED_SPACE/POWER(2,20) FREE_SPACE/POWER(2,20)
    31230,9922 1244,99219 *29986*
    R:\mxvc01>dir temp
    Volume in drive R is Disk_R
    Volume Serial Number is 248B-61D4
    Directory of R:\mxvc01
    20.11.2012 08:09 32.748.077.056 TEMP01.DBF
    1 File(s) 32.748.077.056 bytes
    0 Dir(s) 8.259.297.280 bytes free
    SQL> alter tablespace temp shrink tempfile 'R:\mxvc01\TEMP01.DBF';
    alter tablespace temp shrink tempfile 'R:\mxvc01\TEMP01.DBF'
    ERROR at line 1:
    ORA-03214: File Size specified is smaller than minimum required
    *It clearly says that there is 29986 MB Space FREE and the above shrink space changes nothing and so does shrink tempfile:*
    SQL> alter tablespace temp shrink tempfile 'R:\mxvc01\TEMP01.DBF';
    alter tablespace temp shrink tempfile 'R:\mxvc01\TEMP01.DBF'
    ERROR at line 1:
    ORA-03214: File Size specified is smaller than minimum required
    SQL> alter tablespace temp shrink tempfile 'R:\mxvc01\TEMP01.DBF' KEEP 20M;
    Tablespace altered.
    R:\mxvc01>dir temp
    Volume in drive R is Disk_R
    Volume Serial Number is 248B-61D4
    Directory of R:\mxvc01
    20.11.2012 08:24 32.748.077.056 TEMP01.DBF
    1 File(s) 32.748.077.056 bytes
    0 Dir(s) 8.259.280.896 bytes free
    *... nothing changes, the tempfile isn't smaller now ...*

  • Create report to get lat 30days Metric alert & Alert log errors Grid

    We would like to create a report to display last 30 day's mertric alert and alert log errros in EM Grid. How we can do it?

    DBMS Direct,
    But in the post How to be notified for all ORA- Errors recorded in the alert.log file
    11iuser complain about that why he/she just get error number without any explain of arrised error.
    In my situation I just get "distinct types of ORA- errors" without even any error code.
    Perhaps I need to change something in emoms.properties or emd.properties.
    By the way I select Message format -- Long Format
    Sorry for my poor English

  • Bigfile Temporary Tablespace?

    Hi,
    --------------------------Oracle 11G Release 11.1.0.6.0, Windows XP 32------------------------------------
    I've tried to find out but not successful. Can I create BIGFILE TEMPORARY TABLESPACE like I've created normal BIGFILE TABLESPACE.
    Secondly, If it is not possible then will creating multiple temporary files will effect performance will doing the sorting?
    ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
    select inst_id, tablespace_name, total_blocks, used_blocks, free_blocks
          from gv$sort_segment;
       INST_ID TABLESPACE_NAME                 TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS
             1 TEMP                                12582144           0    12582144
    I've created 3 temp files of 30G each and get above error i.e unable to extend. adding a temp file will solve this issue, but I was thinking to create one bigfiel temporary file instead of adding files, that might decrease lot of performance.
    Thanks
    Regards

    kam555 wrote:
    Hi,
    --------------------------Oracle 11G Release 11.1.0.6.0, Windows XP 32------------------------------------
    I've tried to find out but not successful. Can I create BIGFILE TEMPORARY TABLESPACE like I've created normal BIGFILE TABLESPACE.
    Secondly, If it is not possible then will creating multiple temporary files will effect performance will doing the sorting?
    ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
    select inst_id, tablespace_name, total_blocks, used_blocks, free_blocks
    from gv$sort_segment;
    INST_ID TABLESPACE_NAME                 TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS
    1 TEMP                                12582144           0    12582144I've created 3 temp files of 30G each and get above error i.e unable to extend. adding a temp file will solve this issue, but I was thinking to create one bigfiel temporary file instead of adding files, that might decrease lot of performance.
    Thanks
    RegardsBigfile tablespaces are supported only for locally managed tablespaces with automatic segment space management, with three exceptions: locally managed undo tablespaces, temporary tablespaces, and the SYSTEM tablespace.
    There is no performance overhead if you have multiple datafiles in a tablespace. That is structure of Oracle: Tablespace may consist of multiple datafiles.

Maybe you are looking for

  • Artboards and EPS size

    Hello all! I'm an experienced CorelDRAW user (so I do have some vector graphic experience) but a noob to Illustrator and trying to evalutate switching. In CorelDRAW when I export an EPS it doesn't matter what size paper the CorelDRAW file uses, the E

  • My Dock is frozen? Finder will not respond

    My Dock is frozen;  I have Force Quit all apps, restarted and can open apps indirectly through links or some reopened by themselves after restarting, but Finder will not respond and neither will other apps in current Dock.  Any suggestions how to res

  • Update query problem

    Hello I'm trying to write an update query either in a single statement or stored procedure that updates a numeric column based on a date column. I do this using: UPDATE DATE SMSCLOSED_CTYWOA SET 'date_action_start' = to_number(to_char('action_date' ,

  • VPRS Pricing Date

    Hi, Our customer is using moving average costing. They sometimes get different cost values between PA and FI because the cost posted to FI is based on the goods issue date whereas the cost posted to PA is based on the invoice date. The pricing date s

  • Downloading program on Laptop and Desktop?

    I purchased lightroom less than a year ago. I downloaded it to my laptop, but would like it on my home desktop as well. How do I re download? can I re-download?