How to monitor temp tablespace

I server in 11gR2 and 10gR2.
Is there a way to monitor its usage, like, who is using it, how much space a session is using, what are the objects crated, ie. temp tables.
Thanks.

Hi
This might helpful
select TABLESPACE_NAME, BYTES_USED, BYTES_FREE from V$TEMP_SPACE_HEADER;Also checkout the below link.
http://blog.flimatech.com/2010/06/15/how-to-monitor-temp-tablespace-usage/
Cheers
Kanchana

Similar Messages

How to identify temp tablespace user in the past

hi,
can anyone guide me on how to identify temp tablespace users and corresponding temp space amount they used in the past?
we have this situation where in we need to identify the top temp tablespace user last jan 1 around a specific time.
is this possible? do these get stored in one of the tables in the dictionary? any sql statement?
thanks.

900666 wrote:
hi ckpt,
thats unfortunate..=(
anyways, any sql that can be used to capture current sessions with their used mb in temp tablespace? for future monitoring.
thansk.Here is example
SQL> SET LINESIZE 145
SQL> SET PAGESIZE 9999
SQL> SET VERIFY   off
SQL>
SQL> COLUMN tablespace_name       FORMAT a15               HEAD 'Tablespace Name'
SQL> COLUMN username              FORMAT a15               HEAD 'Username'
SQL> COLUMN sid                   FORMAT 99999             HEAD 'SID'
SQL> COLUMN serial_id             FORMAT 99999999          HEAD 'Serial#'
SQL> COLUMN contents              FORMAT a9                HEAD 'Contents'
SQL> COLUMN extents               FORMAT 999,999           HEAD 'Extents'
SQL> COLUMN blocks                FORMAT 999,999           HEAD 'Blocks'
SQL> COLUMN bytes                 FORMAT 999,999,999       HEAD 'Bytes'
SQL> COLUMN segtype               FORMAT a12               HEAD 'Segment Type'
SQL>
SQL> BREAK ON tablespace_name ON report
COMPUTE SUM OF extents   ON report
SQL> SQL> COMPUTE SUM OF blocks    ON report
SQL> COMPUTE SUM OF bytes     ON report
SQL>
SQL>
SQL> SELECT
2      b.tablespace          tablespace_name
3    , a.username            username
4    , a.sid                 sid
5    , a.serial#             serial_id
6    , b.contents            contents
7    , b.segtype             segtype
8    , b.extents             extents
, b.blocks              blocks
9   10    , (b.blocks * c.value) bytes
FROM
11   12      v$session     a
13    , v$sort_usage b
14    , (select value from v$parameter
15       where name = 'db_block_size') c
16 WHERE
17        a.saddr = b.session_addr
18 /
Tablespace Name Username           SID   Serial# Contents Segment Type Extents   Blocks        Bytes
TEMP          SYSTEM            1333      4725 TEMPORARY LOB_DATA            1      128    1,048,576
                SYSTEM            1562       444 TEMPORARY SORT               89   11,392   93,323,264
                SYSADM            1602        80 TEMPORARY LOB_DATA            1      128    1,048,576
                SYSTEM            1613     18693 TEMPORARY SORT               89   11,392   93,323,264
sum                                                                          180   23,040 188,743,680
SQL>

How can drop TEMP tablespace

Hi,
Please help me

1) Create new temporary tablespcae
2) Chechk new temp tablespace in default
3) Drop tem pablespace
CREATE TEMPORARY TABLESPACE TEMP2 TEMPFILE’C:\ORACLE\10.2\ORADATA\PROD\temp2_01.dbf’ SIZE 100M AUTOEXTEND ON NEXT 256K
MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP2;
DROP TABLESPACE temp INCLUDING CONTENTS AND datafiles

Doubt in considering temp tablespace's free space

Hi All,
Database: oracle 11.2
Operating System: AIX
I want to know how much free space available in my temp tablespace
I ran below scripts
select sum((bytes_free)/1024/1024/1024) GB from v$temp_space_header
+52.904296875+
select (tablespace_size)/1024/1024/1024 tablespace_size_in_gb,
+(allocated_space)/1024/1024/1024 allocated_space_in_gb,+
+(free_space)/1024/1024/1024 free_space_in_gb+
from dba_temp_free_space
tablespace_size_in_gb: 98.9990234375
allocated_space_in_gb: 46.0947265625
free_space_in_gb:151.81640625
So my doubt is which one from above two script gives actual free space information ?
Also in dba_temp_free_space view why free space size > tablespace size ?

v$temp_space_header shows you how big the temp tablespace has got since the database was restarted. It doesn't give you the current free/used space.
See the link for dba_temp_free_space, but I think it may be the way it reports free space which is why you're seeing it as more than the actual tablespace. As you can see form the description "space that is currently allocated and available for resuse" is calculated for both allocated space and free space.
http://docs.oracle.com/cd/B28359_01/server.111/b28320/statviews_5056.htm
>
ALLOCATED_SPACE = space that is currently allocated and used + space that is currently allocated and available for reuse
FREE_SPACE = space that is currently allocated and available for reuse + space that is currently unallocated>
I use the below script which I've plagiarised from somewhere ages ago to get the used/free temp space.
SELECT   A.tablespace_name tablespace, D.mb_total,
         SUM (A.used_blocks * D.block_size) / 1024 / 1024 mb_used,
         D.mb_total - SUM (A.used_blocks * D.block_size) / 1024 / 1024 mb_free
FROM     v$sort_segment A,
         SELECT   B.name, C.block_size, SUM (C.bytes) / 1024 / 1024 mb_total
         FROM     v$tablespace B, v$tempfile C
         WHERE    B.ts#= C.ts#
         GROUP BY B.name, C.block_size
         ) D
WHERE    A.tablespace_name = D.name
GROUP by A.tablespace_name, D.mb_total;

Calculate TEMP tablespace

Hi,
Please advise, how to calculate TEMP tablespace size in bytes?
Thanks

user1170666 wrote:
Hi,
Please advise, how to calculate TEMP tablespace size in bytes?
Thanksquery view below
SQL> desc dba_temp_files;
Name                                      Null?    Type
FILE_NAME                                          VARCHAR2(513)
FILE_ID                                            NUMBER
TABLESPACE_NAME                           NOT NULL VARCHAR2(30)
BYTES                                              NUMBER
BLOCKS                                             NUMBER
STATUS                                             VARCHAR2(7)
RELATIVE_FNO                                       NUMBER
AUTOEXTENSIBLE                                     VARCHAR2(3)
MAXBYTES                                           NUMBER
MAXBLOCKS                                          NUMBER
INCREMENT_BY                                       NUMBER
USER_BYTES                                         NUMBER
USER_BLOCKS                                        NUMBERHandle:     user1170666
Status Level:     Newbie
Registered:     Jul 20, 2010
Total Posts:     39
Total Questions:     11 (11 unresolved)
why do you waste time here when you NEVER get any question answered?

10g temp tablespace

how to drop temp tablespace group and temp tablespace in 10g

Am example1.
WHENEVER OSERROR EXIT FAILURE ROLLBACK
WHENEVER SQLERROR EXIT FAILURE ROLLBACK
SPOOL recreate_temp_tablespaces_LOG
SET FEEDBACK ON
SET ECHO ON
SET TRIMSPOOL ON
SET PAGESIZE 0
SET LINESIZE 30000
CREATE TEMPORARY TABLESPACE xyzzy_dummy
TEMPFILE '/data/oracle/misa/xyzzy_dummy01.dbf'
SIZE 100M REUSE
AUTOEXTEND ON
NEXT 100M
MAXSIZE 1000M
EXTENT MANAGEMENT LOCAL;
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE xyzzy_dummy;
DROP TABLESPACE TEMP;
CREATE TEMPORARY TABLESPACE TEMP
TEMPFILE '/data/oracle/misa/temp01.dbf'
SIZE 3788800K REUSE
AUTOEXTEND ON
NEXT 640K
MAXSIZE 4096000K
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP
DROP TABLESPACE xyzzy_dummy INCLUDING CONTENTS AND DATAFILES
EXIT;
V.

Unusual Temp Tablespace Growth

Hi ,
We have noticed unsual temp tablespace growth when concurrent users are accessing OLAP cube through BI Bean crosstabs.
On an average 3 to 4 GB temp tablespace is consumed for each new user. OLAP cube has 7 dimensions and 1.2 million records and is fully precalculated.
This causes the system to fail as a result of temp tablespace getting full.
Can somebody please let me know what can be the root causes?.
Thanks in advance.
Harry

Hi there,
It is not unusual for OLAP queries to make significant use of temp tablespace. 3-4GB doesn't sound unreasonable to me. The actual amount used depends on factors such as the type of activity and the number of users.
There is a brief description of how OLAP uses temp tablespace here :- http://download.oracle.com/docs/cd/B28359_01/olap.111/b28124/admin.htm#sthref442
Note the lower than standard setting 'EXTENT MANAGEMENT LOCAL UNIFORM SIZE 256K' - if you are not already using this setting then you may find that it lowers temp space usage as the default setting is usually 1024K or even 4096K
I hope this helps
Stuart

How to exclude UNDO and temp tablespace using monitoring template

hi,
as per MOS note id 816920.1 undo and temp tablespace is excluded from monitoring starting version 11G onwards.It says that thresholds will need to be explicitly set if undo and temp needs to be monitored
we have grid 12C implemented now with monitoring templates which sets thresholds for all tablespaces. does it apply that thresholds to undo and temp too?? we are receiving alerts for undo and temp tablespaces and we wish to disable them. We have undo tablespaces with different names in many databases as per naming conventions for that line of business.
How can i exclude undo and temp tablespaces from monitoring using grid 12C monitoring templates. is there a way through templates where i can set thresholds of permanent tablespaces only???

In EM12c, go to the 'Enterprise' menu, then 'Job', then 'Library'. There should be an out-of-the-box job called "DISABLE TABLESPACE USED (%) ALERTS FOR UNDO AND TEMP TABLESPACES" that you can run against your database targets, and that job will disable database-generated alerts.
If a previous admin has set up EM12c-generated alerts for undo and temp, then yes, a monitoring template will take care of disabling them. Either remove those alerts from the existing monitoring template and apply them to your targets, or create a new monitoring template based on one database's current settings, remove those warning/critical thresholds for your undo and temp tablespaces, and apply it to your targets.

How to create temp files in temp tablespace

Dear all,
Due to outage of our SAN, we our out of production for the
last 3 days. By the grace of Almighty we have restored production by
database recovery from our standby backup. Since temp tablespace and
temp data files do not taken as backup for standby, now after recovery
we are getting abap dumps asking for temp_1 and temp_2 datafiles.
Please guide us how to create temp files. v$tablespace is showing tablespace PSAPTEMP but datafile are not there
Abap dumps are giving these errors as mentioned below
====================================================
The exception must either be prevented, caught within the procedure
"DATA_SELECTION"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-01157: cannot identify/lock data file 256 -
see DBWR trace file#ORA-01110: data file 256:
'/oracle/SD1/sapdata4/temp_2/temp.data2'"
Internal call code.........: "[RSQL/FTCH/MARA ]"
===================================================
another one asking for
'/oracle/SD1/sapdata3/temp_1/temp.data1'"
Best Regards
Waqas

if you want to add a new tempfile to your TEMP Tablespace,you can do like that.
ALTER TABLESPACE <name of TEMP Tablespace> ADD TEMPFILE <pfad to the file_and_file name> SIZE <size>;
You can use also the options REUSE autoextend off or on .
e.g:
alter tablespace PSAPTEMP add tempfile '/oracle/SD1/sapdata4/temp_2/temp.data2' SIZE 1000K REUSE;
The directory temp_2 should exist.
Or you can use the BR*Tools to create a new datafile. Enter brtools and follow the instructions or menu.
More to TEMP Tablespaces see please following SAP notes:
659946 - FAQ: Temporary tablespaces
600513 - ORA-25153 after recovery due to missing tempfiles
and the Oracle Note:
160426.1: TEMPORARY Tablespaces : Tempfiles or Datafiles ?
I hope it helps.

How to add a datafile in the temp tablespace

how i can add a datafile in the temp tablespace.
becuase i am getting tyhe following error
SQL> select aa.question_desc,a.answer_desc from answer a ,
2 (select * from question_t where rownum <=100 order by dbms_random.random) aa
3 where a.question_id = aa.question_id
4 /
select aa.question_desc,a.answer_desc from answer a ,
ERROR at line 1:
ORA-01652: unable to extend temp segment by 256 in tablespace TEMP

select * from question_t where rownum <=100 order by dbms_random.random After all the discussion about random select a random generated number... why don't you go for one of the suggestion like : 
select *
from (select * from question_t order by dbms_random.random)
where rownum <=100 The result is different. 
In your query, you take 100 rows and order randomly, in the second query, order randomly, and take 100 first rows... 
As you can see above, with your last query, output row are always same, but in different order : 
SCOTT@demo102> select ename from emp where rownum<=5 order by dbms_random.random;
ENAME
SMITH
ALLEN
MARTIN
JONES
WARD
SCOTT@demo102> /
ENAME
MARTIN
JONES
SMITH
ALLEN
WARD
SCOTT@demo102> /
ENAME
JONES
ALLEN
MARTIN
SMITH
WARD
SCOTT@demo102> /
ENAME
ALLEN
SMITH
WARD
MARTIN
JONES
SCOTT@demo102> 
Anyway, I don't restart this discussion here. 
For your actual problem, Pierre has already give you a suggestion. 
 
Nicolas.

How to find the sessions/user consuming more temp tablespace

Environment details
IBM-AIX 64 bit
Oracle 10.2.0.4.0
Recently we encountered the issue of sudden peak in CPU utilization and temp tablespace usage. We are noticing this issue after Apr CPU 2009 patch and upgrade to 10.2.0.4.
Recently temp space was full and we added 18 GB of space to temp tablespace, within few hours, they are also consumed.
Application team is telling that they did not modify any code. ADDM report suggests most of the recommendations related to SQL tuning only
not sure about the real issue. Can somebody tell me how I can find what are all sessions/user consuming high temp tablespace
Edited by: user1368801 on Sep 1, 2009 5:32 PM

Hi,
Run below query to check if it is used by any session.
select sum(a.BYTES_USED)/1024/1024 used_mb, sum(b.bytes)/1024/1024 total_mb,
sum(a.BYTES_USED)/sum(b.bytes)*100 pct_used
from V$TEMP_EXTENT_POOL a, v$tempfile b
where a.file_id(+) = b.file#
Check who is using it by the below query.
SELECT s.sid,s.serial#,osuser,process,program,s.sql_hash_value,u.extents, u.blocks
FROM v\$session s, v\$sort_usage u
WHERE s.saddr = u.session_addr order by extents,blocks desc
Hope this solves your issue.
Regards
Regards,
Satishbabu Gunukula
Click here to improve RMAN backup Performance using [Block change tracking in Oracle 10g|http://oracleracexpert.blogspot.com/2009/09/block-change-tracking-in-oracle-10g.html]
http://oracleracexpert.blogspot.com

How could I extend temp tablespace safely ?

I am beginner of Oracle DB.
We are making DEV environment of Oracle Insight.
How could I extend temp tablespace safely ?

It is normal to see the temp tablespace full. Oracle finds it the most efficient way to allocate an extent and mange it rather than allocate - deallocate.

Query using large(in GB) temp tablespace, how to tune it?

Hi,
Below query is using large Temp tablespace, please guide for tuning this query so that it can use minimal temp space.
SELECT DISTINCT cust_alt.cust_acct_alt_id, cust_alt.cust_acct_alt_id_type_cd,
                trans.legal_entity_id, trans.exchange_id,
                trans.stamp_update_dtime, trans.book_alt_id,
                trans_alt.trans_alt_id, trans_alt.trans_alt_vers_id,
                trans_alt.src_sys_short_name, event.trans_event_sequence_id,
                event.trans_event_type_cd, prod_alt.product_alt_id,
                prod_alt.product_alt_id_type_cd, trans.buy_sell_cd,
                trans.trade_date, item.setlmt_date, item.trans_price_amt,
                item.price_yield_ind, item.trans_dirty_price_amt,
                item.trans_qty, item.trans_item_type_cd,
                event.trans_event_dtime,
                DECODE (extnn.confirm_generation_elig_ind,
                        'Y', 'In Progress',
                        NULL, 'Not Processed',
                        'Confirm Ineligible'
                       ) confirm_status,
                event_ref.trans_event_type_desc
           FROM ods_trans_event_type_ref event_ref,
                ods_trans_type_ref trans_type,
                ods_cust_acct_alt_id cust_alt,
                ods_product_alt_id prod_alt,
                ods_trans_item item,
                ods_trans_alt_id trans_alt,
                ods_trans trans,
                ods_trans_extnn extnn,
                ods_trans_event event
          WHERE event_ref.trans_event_type_cd = event.trans_event_type_cd
            AND trans_type.trans_type_id = trans.trans_type_id
            AND prod_alt.product_id = trans.product_id
            AND cust_alt.cust_acct_id = trans.cust_acct_id
            AND item.trans_vers_id = trans.trans_vers_id
            AND item.trans_id = trans.trans_id
            AND extnn.trans_vers_id(+) = trans.trans_vers_id
            AND extnn.trans_id(+) = trans.trans_id
            AND trans_alt.trans_link_reason_cd = 'FOID'
            AND trans_alt.trans_vers_id = trans.trans_vers_id
            AND trans_alt.trans_id = trans.trans_id
            AND trans.trans_vers_id = event.trans_vers_id
            AND trans.trans_id = event.trans_id
            AND item.trans_item_type_cd IN ('MAIN', '1', '2')
            AND cust_alt.cust_acct_alt_id != 'BOOKTOBOOK'
         order by trans_alt.trans_alt_id, event.trans_event_sequence_idThe Explain for this query is
| Id | Operation                                      | Name                        | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                          |                             |    79 | 23384 | 1404   (1)| 00:00:17 |
|   1 | HASH UNIQUE                                   |                             |    79 | 23384 | 1404   (1)| 00:00:17 |
|* 2 |   TABLE ACCESS BY INDEX ROWID        | ODS_TRANS_ITEM       |     1 |    53 |     4   (0)| 00:00:01 |
|   3 |    NESTED LOOPS                                |                             |    79 | 23384 | 1403   (1)| 00:00:17 |
|   4 |     NESTED LOOPS OUTER                    |                             |    73 | 17739 | 1144   (1)| 00:00:14 |
|   5 |      NESTED LOOPS                              |                             |    73 | 16717 |   965   (0)| 00:00:12 |
|   6 |       NESTED LOOPS                             |                             |    73 | 15476 |   819   (0)| 00:00:10 |
|   7 |        NESTED LOOPS                            |                             |    73 | 14089 |   673   (0)| 00:00:09 |
|   8 |         NESTED LOOPS                           |                             |    73 | 10439 |   672   (0)| 00:00:09 |
|   9 |          NESTED LOOPS                          |                             |    90 | 9810 |   312   (0)| 00:00:04 |
|* 10 |           TABLE ACCESS BY INDEX ROWID| ODS_TRANS_ALT_ID            |    92 | 3680 |    52   (0)| 00:00:01 |
|* 11 |            INDEX RANGE SCAN               | ODS_TRANS_ALT_ID_X1         |   119 |       |     5   (0)| 00:00:01 |
| 12 |           TABLE ACCESS BY INDEX ROWID| ODS_TRANS                   |     1 |    69 |     3   (0)| 00:00:01 |
|* 13 |            INDEX UNIQUE SCAN              | ODS_TRANS_PK                |     1 |       |     2   (0)| 00:00:01 |
| 14 |          TABLE ACCESS BY INDEX ROWID | ODS_TRANS_EVENT             |     1 |    34 |     4   (0)| 00:00:01 |
|* 15 |           INDEX RANGE SCAN                | ODS_TRANS_EVENT_PK          |     1 |       |     3   (0)| 00:00:01 |
| 16 |         TABLE ACCESS BY INDEX ROWID | ODS_TRANS_EVENT_TYPE_REF    |     1 |    50 |     1   (0)| 00:00:01 |
|* 17 |          INDEX UNIQUE SCAN                | ODS_TRANS_EVENT_TYPE_REF_PK |     1 |       |     0   (0)| 00:00:01 |
| 18 |        TABLE ACCESS BY INDEX ROWID   | ODS_PRODUCT_ALT_ID          |     1 |    19 |     2   (0)| 00:00:01 |
|* 19 |         INDEX RANGE SCAN                  | ODS_PRODUCT_ALT_ID_PK       |     1 |       |     1   (0)| 00:00:01 |
|* 20 |       TABLE ACCESS BY INDEX ROWID    | ODS_CUST_ACCT_ALT_ID        |     1 |    17 |     2   (0)| 00:00:01 |
|* 21 |        INDEX RANGE SCAN                   | ODS_CUST_ACCT_ALT_ID_PK     |     1 |       |     1   (0)| 00:00:01 |
| 22 |      TABLE ACCESS BY INDEX ROWID     | ODS_TRANS_EXTNN             |     1 |    14 |     3   (0)| 00:00:01 |
|* 23 |       INDEX UNIQUE SCAN                   | SYS_C0026927                |     1 |       |     2   (0)| 00:00:01 |
|* 24 |     INDEX RANGE SCAN                      | ODS_TRANS_ITEM_PK           |     1 |       |     3   (0)| 00:00:01 |
--------------------------------------------------------------------------------------------------------------------Cant avoid the order by and distinct clauses. Cant avoid Outer joins. Indexes are used properly.

Just to add on to Mark's excellent points--
1) The Oracle optimizer is estimating that your query is only going to return 79 rows. If it is using a great deal of TEMP space, that estimate would seem to be wildly incorrect which implies that you have a problem with your statistics.
2) Are you certain that you need the DISTINCT? Lots of people either throw DISTINCT clauses into their queries "just in case" or throw in a distinct when they are unexpectedly getting duplicate rows because they are missing a join condition. If that's the case here, removing the DISTINCT and figuring out which join condition is missing (if applicable) would cause much less TEMP space to be used.
Justin

How do I empty TEMP tablespace in Oracle8.1.7.4

Hi,
I need to empty the temp tbl using Oracle8.1.7.4
Any advice will be appreciated.
Kind Regards,

It is normal to see the temp tablespace full. Oracle finds it the most efficient way to allocate an extent and mange it rather than allocate - deallocate.

Should I increase TEMP tablespace size here ?

Version: 10.2.0.4
Platform : RHEL 5.8
Currently we are running a batch job in a schema. The default temporary tablespace for that schema is TEMP.
But I see that the tablespace is full.
SQL> select file_name, bytes/1024/1024/1024 gb from dba_temp_files where tablespace_name = 'TEMP';
FILE_NAME                                                                 GB
/prd/fdms/oradata_db18/fdmsc1sdb/oradata/ts_temp/temp01.dbf               10
SQL> SELECT     TABLESPACE_NAME, FILE_ID,
        BYTES_USED/1024/1024,
        bytes_free/1024/1024
FROM V$TEMP_SPACE_HEADER where tablespace_name = 'TEMP' 2    3    4 ;
TABLESPACE_NAME                             FILE_ID BYTES_USED/1024/1024 BYTES_FREE/1024/1024
TEMP                                              1                10240
So, far the application users have not complained and I didn't see any 'unable to extend' error in the alert log yet, but the above scenario is dangerous. Right? I mean SQL statements with sorting can error out. Right ? Unlike UNDO, with temp tablespace, temp segments cannot be reused. Right ?

Hello,
As said previously, the Sort Segments can be reused, the Views V$SORT_SEGMENT and V$TEMPSEG_USAGE are relevant to monitore the usage of the Temporary Tablespace.
You'll find in the Note below a way to control over time the Temporary Tablespace:
How Can Temporary Segment Usage Be Monitored Over Time? [ID 364417.1]
More over, you may also check for any ORA-01652 in the Alert Log.
But don't worry to much to get a Full Temporary Tablespace, here "Full" doesn't mean "unreusable".
Hope this help.
Best Regards,
Jean-Valentin Lubiez

How to monitor temp tablespace

Similar Messages

Maybe you are looking for