Temp Tablespace space issues

My temp tb is growing really fast. How do I relase all the space in there so that it is back to 0 again or at least 90% free or so.
Ideally I would like to do this every night on some sort of a script. Can this be done?

Here is my attempt:
Make sure temp file's autoextend is turned off, check with:
select FILE_NAME, AUTOEXTENSIBLE from dba_temp_files;
To turn off autoextend (take care):
alter database tempfile '\u01....\TEMP01.DBF' AUTOEXTEND off;
This shows usage of temp ts:
v$sort_segment has info about every sort segment of the temp ts.
v$sort_usage has current active disk sorts in the instance
OEM showing temp 100% full is ambiguous. Above views show true usage.

Similar Messages

Temp tablesapce space Issue

Hi All
In My Production database we have two temp tablesapces
when user running a concurrent programme it is erroring out with error unable to extend temp segemnt by 16 byte
.....something like that
but in temp tablepace 2 we have enough space
Y is it not useing that space?
Please let me know ASAP
Its a r12 Instance with 10.2.0.2 database
Thanks in Advance ,
Vinay varma

Hi
you can check with below mention query for sessions using TEMP tablespace. if you think some session is not relevant then you can kill them. this is easy way to monitor your temp tablespace.
SELECT b.tablespace, ROUND(((b.blocks*p.value)/1024/1024),2)||'M' "SIZE",
a.sid||','||a.serial# SID_SERIAL, a.username, a.program
FROM sys.v_$session a, sys.v_$sort_usage b, sys.v_$parameter p
WHERE p.name = 'db_block_size' AND a.saddr = b.session_addr ORDER BY b.tablespace, b.blocks;
Regards
Krishna

Temp Tablespace space needed to create an index of 52GB - preventing 01652

Hi,
I've seen quiet a few threads on the subject, but could not find a clear (to me) answer on the subject.
We have a huge table made by 30/40 partitions of roughly 20M records each (each record being about 1k of size), overall 800GB.
The index we already have shows:
1* select sum(bytes/1024/1024) from dba_segments where segment_name like 'CALL_LOG_I0'
SQL> /
SUM(BYTES/1024/1024)
52088
so that I assume it's 52GB in size. Since we have to create another very similar one I would assume the size would be similar.
Command would be:
create index call_log_i0_new on call_log (msisdn, generation_timestamp, cdr_reference_number, Multiple_AMA_Sequence_Number) NOLOGGING online;
Tried the NOSORT option but it's not compatible with the online option.
After a while the TEMP tablespace got filled up (we have about 20GB space in there).
My question is if I need to have a temp tablespace at least as big as the index size (52GB) to let the index be built online.
Thanks in advance !
Cheers,
Mike

Thanks to all, found useful information in Metalink following your suggestions:
You need to add more space to the tablespace where the index is created.
A possible option to reduce sort space usage is to use the NOSORT option.
Your table contains 66 million rows. The average row length is
50-60 bytes and you are indexing 4 of 5 columns in the table.
Example space calculation:
66 million rows * 50 (avg row length) = 3.3 gig of data
Rule of thumb:
upper bound for sort (not guaranteed) is 3 times data_
= about 10 gig of sort space needed
These numbers are scaring since assume that I may need much more space than the index size (about 3x) which is something we cannot afford. Will go with the NOSORT option once the system is brought down and we could skip the online option.
Thanks to all !
Mike

Sizing of the OLAP temp tablespace!!

We are using 10gR2 OLAP along with Disco Plus OLAP to build a prototype. The metadata is built with AWM 10.2.0.1.0A.
Our test data is about 40M records, 1.7G in a flat file. After loaded to a fact table via Sql*loader, it takes about 2G for the tablespace, along with 7 dim tables. Only one cube and one measure are used. A compressed composite with 6 dims in it is associated with the cube.
However, when run the AWM maintenance steps to get a full cube aggregation. The temp tablespace for the AW shot for 30G and then generated an out of disk space error. The AW tablespace remains untouched. The maintenace cannot be finished.
Interesting to note, the data was solved in the Xpress already. When do a eif exp/imp, the result tablespace is about 5G while the eif file takes 1.3G.
Also, before doing this round data, we have sucessfully created and maintained a AW with very small set of data. The data is displayed in Disco Plus correctly.
The disk space for the temp tablespace seems surprisingly demanding. We need to get an idea how much space it really needs. Is there anybody that has some contributable experience on this issue? Please reply this post. Not sure if Oracle has formal publishing on the temp tablespace sizing issue. Believe they should have one.
Thanks,

Chris,
No upgrading was done here. The metadata and objects were defined using AWM model view manually, but matching to the definition on the Xpress side for the same object, like dim order etc. The fact data then dumped to a flat file from Xpress, transferred to the olap db server and loaded to a star schema with sql*loader. AWM mapping and maintenance features were used to build the cube.
I am saying the data was solved means the summary level data was included in the dump. So we know the size of the solved cube. My reasoning is that there should be no place for the size increase to out of control because too much new summary level data was added.
Another fact I should mention last time is all the data are in one time period. 40M is the number of tuples.
Thanks for the help.
Haiyong

Free space in temp tablespace

SQL> show parameter block
NAME                                 TYPE        VALUE
db_block_buffers                     integer     0
db_block_checking                    boolean     FALSE
db_block_checksum                    boolean     TRUE
db_block_size                        integer     8192
db_file_multiblock_read_count        integer     8
SQL> SELECT tablespace_name,
       total_blocks,
       used_blocks,
       free_blocks,
    (total_blocks*8)/1024 as total_MB,
    (used_blocks*8)/1024 as used_MB,
    (free_blocks*8)/1024 as free_MB
FROM   v$sort_segment;
   2    3    4    5    6    7    8
TABLESPACE_NAME                 TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS   TOTAL_MB    USED_MB    FREE_MB
TEMP                                   72704        2944       69760        568         23        545
SQL> select (sum(bytes_free)/1024/1024) Size_MB from v$temp_space_header
order by file_id 2
3 /
   SIZE_MB
      1479
SQL>
My version is 9.2.0.7
why temp free space is different in both queries above..
which one is correct.....

why temp free space is different in both queries above..Because you are looking at two different values.
V$SORT_SEGMENT gives details about the sort segment created in a temporary tablespace. The sort segment created may or may not be of the same size as the complete temporary tablespace. In your case, the sort segment has a total size of 568 MB but only 23 MB is being used.
V$TEMP_SPACE_HEADER refers to the physical files allocated to the temporary tablespace; so the other query is giving you the free bytes in those files.

How to exclude undo and temp from "Tablespace Space Used (%)"

Dear All
Is it possible to exclude undo and temp tablespace monitoring from "Tablespace Space Used (%)" matric?
Thanks & Regards
Quazi Abdur Rab

If you use TEMP >=100 as Warning, this warning can still be raised.
What version of the database is it? If Oracle 10g, Grid Control (the agent) searches the alert table in the database for alerts, so the database raises the alert and the agent just passes this alert to Grid Control.
If you are using Oracle 10g, you can use the following statement (connected as sys):
DBMS_SERVER_ALERT.SET_THRESHOLD(
metrics_id => DBMS_SERVER_ALERT.TABLESPACE_PCT_FULL,
warning_operator => DBMS_SERVER_ALERT.OPERATOR_GT,
warning_value => '90',
critical_operator => DBMS_SERVER_ALERT.OPERATOR_GT,
critical_value => '100',
observation_period => 1,
consecutive_occurrences => 1,
instance_name => NULL,
object_type => DBMS_SERVER_ALERT.OBJECT_TYPE_TABLESPACE,
object_name => 'TEMP');
This will create the GT (Greater Than) instead of GE (Greater Equal).
Kind regards,
Dave
ps. I'm using GC 10.2.0.3.0, so thanks for the note that 10.2.0.4 doesn't take 100+ values.

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;

Temp tablespace issue

Hi,
We are facing continuous problem of slow performance in some applications...i found that temp tablespace is becoming full frequently...so after that reports are getting delayed..is there any permanent fix for this problem..
We have recreated the temp tablespace...
Regards,
Joshua

Hi,
pls find the details...
VERSION:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
some info abt temp tablespace:
TABLESPACE_NAME BYTES_COALESCED EXTENTS_COALESCED PERCENT_EXTENTS_COALESCED BLOCKS_COALESCED PERCENT_BLOCKS_COALESCED
TEMP_SCHEMA_USR 50724864 2 100 6192 100
is that means coalescing would solve the problem ?...
We have some limitation that we cant control the users since they are very critical in operation...
Is Adding datafile will solve the problem(bcoz b4 sometime i added one file....no improvement)...

Generating xml using PL/SQL taking a lot of space in TEMP tablespace

We wrote a stored procedure that generate xml which will be stored in a CLOB column. Environment is 9i on Windows 2003.
The gnerated xml is about 800K. In the procedure there is one big cursor that will retrieve 200 records of 55 fields and many other small dynamic cursors that open and close here and there. The fields are pretty small. Biggest ones are like varchar2(30). The query for the big cursor does using union and need sorting.
Can anyone explain why it takes about 15G of TEMP tablespace to accomplish this job and is there a way to avoid this?

The version is Enterprise Edition 9.2.0.1.0.
Below is the query.
SELECT ROWNUM + ( SELECT NVL(MAX(WQX_ACTIVITY_GEN_ID), 0) FROM WQX_ACTIVITY ) as WQX_ACTIVITY_GEN_ID
     , A.ACTIVITYIDENTIFIER2            as ACTIVITY_IDENTIFIER
     , (SELECT MAX(O.ORGANIZATION_NAME) FROM SYS_ORGANIZATION O WHERE O.ORGANIZATION_ID = 111242) as ORGANIZATION_NAME
     , (SELECT MAX(P.PROJECT_IDENTIFIER) FROM SYS_PROJECT P WHERE P.PROJECT_ID = 111242) as PROJECT_IDENTIFIER
     , A.ACTIVITYTYPECODE               as ACTIVITY_TYPE_CD
     , A.ActivityMediaName              as ACTIVITY_MEDIA_NAME
     , A.ActivityMediaSubDivisionName   as MEDIA_SUB_DIVISION
     , A.ActivityStartDate              as ACTIVITY_START_DATE
     , CASE WHEN A.ActivityStartTime is not NULL THEN
                 substr(A.ActivityStartTime,1,2)||':'||substr(A.ActivityStartTime,3,2)||':00'
            WHEN A.ActivityStartTime is NULL THEN ''
       END as ACTIVITY_START_TIME
--   , substr(A.ActivityStartTime,1,2)||':'||substr(A.ActivityStartTime,3,2)||':00' as ACTIVITY_START_TIME
     , A.ACTIVITYENDDATE                as ACTIVITY_END_DATE
     , CASE WHEN A.ACTIVITYENDTIME is not NULL THEN
                 substr(A.ACTIVITYENDTIME,1,2)||':'||substr(A.ACTIVITYENDTIME,3,2)||':00'
            WHEN A.ACTIVITYENDTIME is NULL THEN ''
       END as ACTIVITY_END_TIME
--   , substr(A.ACTIVITYENDTIME,1,2)||':'||substr(A.ACTIVITYENDTIME,3,2)||':00' as ACTIVITY_END_TIME
     , A.TIMEZONECODE1                  as TIME_ZONE_CD
     , A.ActivityRelativeDepthName      as RELATIVE_DEPTH_NAME
     , NULL                             as DEPTH_HEIGHT_MEASURE
     , NULL                             as DEPTH_HEIGHT_UNIT
     , 111242              as MONITORING_LOC_ID
     , A.ACTIVITYCOMMENTTEXT            as COMMENT_
     , A.SamplerName                    as SAMPLER_NAME
     , A.ActivityArea                   as ACTIVITY_AREA
     , A.ReportingRound                 as REPORTING_ROUND
     , A.SamplePanel                    as SAMPLEPANEL
     , A.DataIncludedinReport           as DATA_INCLUDED_IN_REPORT
     , A.FlowStatusIndicator            as FLOW_STATUS_IND
     , A.SampleChainOfCustody           as SAMPLE_COC
     , A.ActivitySeason                 as ACTIVITY_SEASON
     , A.RunoffImpact                   as RUNOFF_IMPACT
     , (111242)            as MONI_LOC_ID
     , (SELECT MAX(B.MONI_LOC_IDENTIFIER) FROM WQX_MONITORING_LOC B WHERE B.MONI_LOC_IDENTIFIER = A.MONITORINGLOCATIONIDENTIFIER) as MONI_LOC_IDENTIFIER
     , 111242                     as PROJECT_ID
     , NULL                             as BIO_ASSEMB_SAMPLED_NAME
     , NULL                             as BIO_TOXICITY_TEST_TYPE
     , A.METHODIDENTIFIER1              as SAMPLE_COLLECT_METHOD_IDENTIFI
     , A.METHODIDENTIFIERCONTEXT1       as SAMPLE_COLLECT_METHOD_CONTEXT
     , A.METHODNAME1                    as SAMPLE_COLLECT_METHOD_NAME
     , NULL                             as SAMPLE_COLLECT_QUALIFIER_TYPE
     , A.METHODDESCRIPTIONTEXT1         as SAMPLE_COLLECT_DESC
     , A.SampleCollectionEquipmentName as SAMPLE_COLLECT_EQUIP_NAME
     , A.SAMPLECOLLECTIONEQUIPMENTTXT   as SAMPLE_COLLECT_EQUIP_DESC
     , A.METHODNAME2                    as SAMPLE_PREP_METHOD_NAME
     , A.METHODIDENTIFIER2              as SAMPLE_PREP_METHOD_IDENTIFIER
     , A.METHODIDENTIFIERCONTEXT2       as SAMPLE_PREP_METHOD_CONTEXT
     , NULL                             as SAMPLE_PREP_QUALIFIER_TYPE
     , A.METHODDESCRIPTIONTEXT1         as SAMPLE_PREP_DESC
     , A.SampleContainerTypeName        as SAMPLE_CONTAINER_TYPE
     , A.SampleContainerColorName       as SAMPLE_CONTAINER_COLOR
     , A.ChemicalPreservativeUsedName   as CHEM_PRESERVATIVE_USED
     , A.ThermalPreservativeUsedName    as THERMAL_PRESERVATIVE_USED
     , A.SAMPLETRANSPORTSTORAGEDESC     as SAMPLE_TRANS_STORAGE
     , A.AnalysisStartTime              as AnalysisStartTime
     , A.AnalysisEndTime                as AnalysisEndTime
     , A.MethodSpeciationName           as MethodSpeciationName
     , A.ResultLaboratoryCommentCode    as ResultLaboratoryCommentCode
     , A.UnidentifiedSpeciesIdentifier as UnidentifiedSpeciesIdentifier
FROM TMP_CHEMACTIVITYRESULTS A
WHERE A.SUBMISSION_ID = 111242
   AND A.ACTIVITYIDENTIFIER2 NOT IN
     ( SELECT ACTIVITY_IDENTIFIER FROM WQX_ACTIVITY )
UNION
SELECT X.WQX_ACTIVITY_GEN_ID                                             as WQX_ACTIVITY_GEN_ID
     , A.ACTIVITYIDENTIFIER2                                             as ACTIVITY_IDENTIFIER
     , (SELECT MAX(O.ORGANIZATION_NAME) FROM SYS_ORGANIZATION O WHERE O.ORGANIZATION_ID = 111242) as ORGANIZATION_NAME
     , (SELECT MAX(P.PROJECT_IDENTIFIER) FROM SYS_PROJECT P WHERE P.PROJECT_ID = 111242) as PROJECT_IDENTIFIER
     , NVL(A.ACTIVITYTYPECODE, (SELECT MAX(ACTYP_CD) FROM REF_ACTIVITY_TYPE WHERE TO_CHAR(ACTYP_UID) = TO_CHAR(X.ACTIVITY_TYPE_CD))) as ACTIVITY_TYPE_CD
     , NVL(A.ActivityMediaName, X.ACTIVITY_MEDIA_NAME)                   as ACTIVITY_MEDIA_NAME
     , NVL(A.ActivityMediaSubDivisionName, X.MEDIA_SUB_DIVISION)         as MEDIA_SUB_DIVISION
     , NVL(A.ActivityStartDate, TO_CHAR(X.ACTIVITY_START_DTTM, 'YYYY-MM-DD')) as ACTIVITY_START_DATE
     , CASE WHEN A.ActivityStartTime is not NULL THEN
                 substr(A.ActivityStartTime,1,2)||':'||substr(A.ActivityStartTime,3,2)||':00'
            WHEN A.ActivityStartTime is NULL THEN ''
       END as ACTIVITY_START_TIME
--   , NVL((substr(A.ActivityStartTime,1,2)||':'||substr(A.ActivityStartTime,3,2)||':00'), TO_CHAR(X.ACTIVITY_START_DTTM, 'HH24:MI:SS')) as ACTIVITY_START_TIME
     , NVL(A.ACTIVITYENDDATE, TO_CHAR(X.ACTIVITY_END_DTTM, 'YYYY-MM-DD'))     as ACTIVITY_END_DATE
     , NVL(A.ACTIVITYENDDATE, TO_CHAR(X.ACTIVITY_END_DTTM, 'HH24:MI:SS'))     as ACTIVITY_END_TIME
     , NVL(A.TIMEZONECODE1, X.TIME_ZONE_CD)                              as TIME_ZONE_CD
     , NVL(A.ActivityRelativeDepthName, X.RELATIVE_DEPTH_NAME)           as RELATIVE_DEPTH_NAME
     , X.DEPTH_HEIGHT_MEASURE                                            as DEPTH_HEIGHT_MEASURE
     , X.DEPTH_HEIGHT_UNIT                                               as DEPTH_HEIGHT_UNIT
     , NVL(111242, X.MONITORING_LOC_ID)                     as MONITORING_LOC_ID
     , NVL(A.ACTIVITYCOMMENTTEXT, X.COMMENT_)                            as COMMENT_
     , NVL(A.SamplerName, X.SAMPLER_NAME)                                as SAMPLER_NAME
     , NVL(A.ActivityArea, X.ACTIVITY_AREA)                              as ACTIVITY_AREA
     , NVL(A.ReportingRound, X.REPORTING_ROUND)                          as REPORTING_ROUND
     , NVL(A.SamplePanel, X.SAMPLEPANEL)                                 as SAMPLEPANEL
     , NVL(A.DataIncludedinReport, X.DATA_INCLUDED_IN_REPORT)            as DATA_INCLUDED_IN_REPORT
     , NVL(A.FlowStatusIndicator, X.FLOW_STATUS_IND)                     as FLOW_STATUS_IND
     , NVL(A.SampleChainOfCustody, X.SAMPLE_COC)                         as SAMPLE_COC
     , NVL(A.ActivitySeason, X.ACTIVITY_SEASON)                          as ACTIVITY_SEASON
     , NVL(A.RunoffImpact, X.RUNOFF_IMPACT)                              as RUNOFF_IMPACT
     , (111242)                                             as MONI_LOC_ID
     , (SELECT MAX(B.MONI_LOC_IDENTIFIER) FROM WQX_MONITORING_LOC B WHERE B.MONI_LOC_IDENTIFIER = A.MONITORINGLOCATIONIDENTIFIER) as MONI_LOC_IDENTIFIER
     , 111242                                                      as PROJECT_ID
     , X.BIO_ASSEMB_SAMPLED_NAME                                         as BIO_ASSEMB_SAMPLED_NAME
     , X.BIO_TOXICITY_TEST_TYPE                                          as BIO_TOXICITY_TEST_TYPE
     , NVL(A.METHODIDENTIFIER1, X.SAMPLE_COLLECT_METHOD_IDENTIFI)        as SAMPLE_COLLECT_METHOD_IDENTIFI
     , NVL(A.METHODIDENTIFIERCONTEXT1, X.SAMPLE_COLLECT_METHOD_CONTEXT) as SAMPLE_COLLECT_METHOD_CONTEXT
     , X.SAMPLE_COLLECT_METHOD_NAME                                      as SAMPLE_COLLECT_METHOD_NAME
     , X.SAMPLE_COLLECT_QUALIFIER_TYPE                                   as SAMPLE_COLLECT_QUALIFIER_TYPE
     , NVL(A.METHODDESCRIPTIONTEXT1, X.SAMPLE_COLLECT_DESC)              as SAMPLE_COLLECT_DESC
     , NVL(A.SampleCollectionEquipmentName, X.SAMPLE_COLLECT_EQUIP_NAME) as SAMPLE_COLLECT_EQUIP_NAME
     , NVL(A.SAMPLECOLLECTIONEQUIPMENTTXT, X.SAMPLE_COLLECT_EQUIP_DESC) as SAMPLE_COLLECT_EQUIP_DESC
     , NVL(A.METHODNAME2, X.SAMPLE_PREP_METHOD_NAME)                     as SAMPLE_PREP_METHOD_NAME
     , NVL(A.METHODIDENTIFIER2, X.SAMPLE_PREP_METHOD_IDENTIFIER)         as SAMPLE_PREP_METHOD_IDENTIFIER
     , NVL(A.METHODIDENTIFIERCONTEXT2, X.SAMPLE_PREP_METHOD_CONTEXT)     as SAMPLE_PREP_METHOD_CONTEXT
     , X.SAMPLE_PREP_QUALIFIER_TYPE                                      as SAMPLE_PREP_QUALIFIER_TYPE
     , NVL(A.METHODDESCRIPTIONTEXT1, X.SAMPLE_PREP_DESC)                 as SAMPLE_PREP_DESC
     , NVL(A.SampleContainerTypeName, X.SAMPLE_CONTAINER_TYPE)           as SAMPLE_CONTAINER_TYPE
     , NVL(A.SampleContainerColorName, X.SAMPLE_CONTAINER_COLOR)         as SAMPLE_CONTAINER_COLOR
     , NVL(A.ChemicalPreservativeUsedName, X.CHEM_PRESERVATIVE_USED)     as CHEM_PRESERVATIVE_USED
     , NVL(A.ThermalPreservativeUsedName, X.THERMAL_PRESERVATIVE_USED)   as THERMAL_PRESERVATIVE_USED
     , NVL(A.SAMPLETRANSPORTSTORAGEDESC, X.SAMPLE_TRANS_STORAGE)         as SAMPLE_TRANS_STORAGE
     , NVL(A.AnalysisStartTime, '')                                      as AnalysisStartTime
     , NVL(A.AnalysisEndTime, '')                                        as AnalysisEndTime
     , NVL(A.MethodSpeciationName, '')                                   as MethodSpeciationName
     , NVL(A.ResultLaboratoryCommentCode, '')                            as ResultLaboratoryCommentCode
     , NVL(A.UnidentifiedSpeciesIdentifier, '')                          as UnidentifiedSpeciesIdentifier
FROM TMP_CHEMACTIVITYRESULTS A
       JOIN WQX_ACTIVITY X ON A.ACTIVITYIDENTIFIER2 = X.ACTIVITY_IDENTIFIER
WHERE A.SUBMISSION_ID = 111242;

9i on Linux. Problems with Temp tablespace cleanup

I am currently running Oracle 9i Enterprise on SUSE Linux 7.2.
I am executing queries against the new XMLType datatype and every query adds to the Temp tablespace, which doesn't get cleaned up. Eventually, the tablespace will run out of space and Oracle will issue and error:
ORA-01652: unable to extend temp segment by 128 in tablespace <name>
The only way to clean up the Temp tablespace seems to be by restarting the server.
Is that happening on other platforms as well? I would appreciate any help.

Hi
You can connect to the database as DBA (Sys or System) and make a bigger temporal tablespace. Or create a new bigger temporary tablespace and assign it to the user.
A10!
PS: Temporary tablespace is used when no memory available for the session, for example when a big ORDER BY is done. Try to increase the memory assigned, just look at initXXX.ora (sort_size)

Need help on extending my TEMP tablespace (Ora ver - 8.1.7.0.0)

Hi
I am having problem in executing the SQL query with certain parameters in the WHERE clause.
ORA-01114: IO error writing block to file 4 (block # 524242)
ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
OSD-04026: Invalid parameter passed. (OS 524247)
ORA-01114: IO error writing block to file 4 (block # 524242)
ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
OSD-04026: Invalid parameter passed. (OS 524247)
I get the above listed error. And i assumed there may be some issue due to Temp tablespace. I also verified the space occupied by the TEMP tablespace and it was 99% occupied.
Kindly let me know is there a way to extend the space without affecting the existing DB content
Regards
Srinivasan B

Didn't you got a answer in your Getting error while executing the SQL ( ver 8.1.7.0.0), did you ?
Furthermore, don't worry about the TEMP tablespace utilization, Oracle doesn't freed space until you need it. By the way, how your TEMP tbs is defined (AUTOEXTEND, DATAFILE/TEMPFILE...) ?
Anyway, you have to be sure about the free space on your device. And check on metalink website to get some notes advices.
Nicolas.

Queries are not releasing temp tablespace in 11g standard edition

Queries are not releasing temp tablespace in 11g standard edition

user8928004 wrote:
Hi any one faced one issue.... please help
Patience, Grasshopper
You posted this follow-up a mere two minutes after your previous post.
This forum is not a chat line, and it is not paid support.
Everyone here has a job for which they are paid, and this forum is not it.
No one is responsible for monitoring it and giving a quick response.
Furthermore, it is a global forum. The person with the information you seek may very well live 20 time zones away from you and was going to bed just as you posted. He will not even see your post for several more hours.
Your original post went up in the middle of the night for half the world.
No one with the information you seek is deliberately withholding it until you sound sufficiently desperate.
======================================================
Please present evidence to backup your assertion that "Queries are not releasing temp tablespace"
From the very fine 11g Database Administrator's Guide, at Managing Tablespaces
Space Allocation in a Temporary Tablespace
You can view the allocation and deallocation of space in a temporary tablespace sort segment using the V$SORT_SEGMENT view. The V$TEMPSEG_USAGE view identifies the current sort users in those segments.
When a sort operation that uses temporary space completes, allocated extents in the sort segment are not deallocated; they are just marked as free and available for reuse.

CLOB processing consuming large memory in temp tablespace

We are having a stored procedure, which is called from a Java process to enqeue a message in to AQ. The input for the procedure is CLOB.
In some installations where oracle standard editions is used, the temp tablespace is growing in large volumes and the only process accessing the temp tablespace is the procedure. Oracle version is 9i 9.2.0.5.0
We are doing a trim on the clob variable inside the procedure. Will that cause any issues like this ?
Procedure is as below
procedure enq_msg
(queue_name varchar2, msg_text in clob,p_result out number) as
queue_options DBMS_AQ.ENQUEUE_OPTIONS_T;
message_properties DBMS_AQ.MESSAGE_PROPERTIES_T;
message_id RAW(16);
v_msg_text               clob default msg_text;
v_queue_name          varchar2(40) deafult queue_name;
BEGIN
v_msg_text := trim(v_msg_text);
v_queue_name := queue_name;
DBMS_AQ.ENQUEUE(queue_name => v_queue_name,
                         enqueue_options => queue_options,
                         message_properties => message_properties,
                         payload => v_msg_text,
                         msgid => message_id
     commit;
     p_result := 0;
exception
when no_data_found then
p_result := 1;
     rollback;
when others then
     rollback;
p_result := sqlcode;
END enq_msg;

Is there a reason you have v_msg_text and v_queue_name defined? You can use queue_name directly in the call to dbms_aq.enqueue and also payload => trim(msg_text)
This would eliminate the copying of the clob that is currently occurring and may help your space issue.
Is trim really needed?
I'm not familiar with any CLOB related bugs in 9i but the above is just some things I would try or question.

Temp tablespace - why so big?

Temp tablespace (size 6gb) is twice the size of my data and index tablespace combined. I am running into space issues and am wondering is it possible to resize this tablespace and/or take some other action to prevent the temp tablespace getting so relatively large?
Thanks in advance.

The Temporary Tablespace holds only 1 Temporary Segment shared all by all user sessions. Each session takes one or more extents. When a session finishes its operation, it "releases" the extent it used for use by another session but the size of the Segment does NOT shrink.
Therefore, the Segment would grow to the peak concurrent temporary extent usage -- eg at some point in time, if you had 4 very large queries running concurently taking up 8GB then the segment would have grown to 8GB. However, even if you never have such concurrent usage (for example the normal load is for 20 users concurrently taking up 500MB only !), the segment remains at 8GB.
In some environments, the Temporary tablespace could grow during periodic (say Monthly Reporting) batch jobs after which it is dropped and recreated again.
This segment is used not just for "SORT" operations. It is also used for HASH JOIN overflows to disk and also for SORT MERGE operations.
You can monitor the size of the segment in V$SORT_SEGMENT. You can monitor users currently using it in V$SORT_USAGE or V$TEMPSEG_USAGE.
Hemant K Chitale
http://hemantoracledba.blogpsot.com

Droping TEMP tablespace

hi folks,
i have a production database in a high traffic environment base on oracle 8.1.7.0.0
i lost TEMP tablespace's datafile because of that i just offlined the tablespace ( just one datafile per tablespace TEMP ) but i can not drop or add a datafile to this tablespace.
i just added a TEMPX tablespace and changed TEMPORARY TABLESPACE of users to use this new temporary tablespace.
really how can i renew TEMP tablespace?
thanks in advanced

Well, the tablespace's offline. ok. Is it a TEMPORARY TABLESPACE or a PERMANENT with TEMPORARY option?
Can you issue the queries:select tablespace_name,file_name from dba_temp_files where tablespace_name='TEMP';
select tablespace_name,file_name from dba_data_files where tablespace_name='TEMP';to check this?
OEM show the used space because it checks in some data dictionary views which still contains info about the TEMP tablespace.
You should really try dropping the datafile/tempfile first via "ALTER DATABASE DATAFILE 'filename' OFFLINE DROP" before dropping the tablespace.
You should also check the status of the session in which you drop the tablespace before cancelling. It may take some time to complete.

Temp Tablespace space issues

Similar Messages

Maybe you are looking for