Temporary table space?

Hi,
I created view called swartview. and when i execute
select * from swartview i get this error
ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP
wat does 128 denote?? 128 mb or kb..
Is it OK to add a datafile for teh tablespace PSAPTEMP?
If its a temporary tablespace wat is te syntax to add a tempfile??
alter tablespace psaptemp add tempfile..??
Kindly help..

Its a generic error message which comes when temp tbs becomes full and can't extend further. You may try your option after some time by which temp become free from other statements or add a datafile or increase the size of existing datafle of temp tbs.
Following command would be used to add a datafile to temp tbs.
ALTER TABLESPACE PSAPTEMP
ADD TEMPFILE 'TEMP02.ora' SIZE 50M;
Jaffar
Message was edited by:
The Human Fly

Similar Messages

Temporary table space usage

Hi could someone help me ...
for the following query...
SELECT returnflag
, linestatus
, sum(quantity) as sum_qty
, sum(extendedprice) as sum_base_price
, sum(extendedprice * (1 - iscount)) as sum_disc_price
, sum(extendedprice * (1 - iscount) * (1 + l_tax)) as sum_charge
, avg(quantity) as avg_qty, avg(extendedprice) as avg_price
, avg(iscount) as avg_disc, count(*) as count_order
FROM lineitem
WHERE shipdate <= date '1998-12-01'
GROUP BY returnflag, linestatus
ORDER BY returnflag, linestatus;
Explain Plan :
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 5 | 135 | 299K (2)| 01:00:00 |
| 1 | SORT GROUP BY | | 5 | 135 | 299K (2)| 01:00:00 |
|* 2 | TABLE ACCESS FULL| LINEITEM | 57M| 1493M| 297K (1)| 00:59:35 |
Predicate Information (identified by operation id):
2 - filter("L_SHIPDATE"<=TO_DATE(' 1998-09-02 00:00:00',
'syyyy-mm-dd hh24:mi:ss'))
would any parts of this query be carried out on the temporary table space (sums and averages? / sort group by?) ... or what impact would the temp table space have when running this query?
any help would be appriciated

im using 11g r2,
what about usage of temporary table space (approximatly) with the following ..
============================================
create view revenue (supplier_no, total_revenue) as
select
suppkey, sum(extendedprice * (1 - iscount))
from
lineitem
where
shipdate >= date '1994-12-01'
group by
suppkey;
select suppkey, name, address, phone, total_revenue
from supplier, revenue
where suppkey = supplier_no and total_revenue = (select max(total_revenue)from revenue)
order by suppkey;
==========================================================
View created.
Execution Plan
Plan hash value: 2790460729
| Id | Operation | Name | Rows | Bytes |TempSpc| Cost (%CPU)|
Time |
| 0 | SELECT STATEMENT | | 50000 | 5126K| | 381K (1)|
01:16:23 |
| 1 | MERGE JOIN | | 50000 | 5126K| | 381K (1)|
01:16:23 |
| 2 | SORT JOIN | | 100K| 3027K| | 380K (1)|
01:16:09 |
|* 3 | VIEW | REVENUE | 100K| 3027K| | 380K (1)|
01:16:09 |
| 4 | WINDOW BUFFER | | 100K| 2148K| | 380K (1)|
01:16:09 |
| 5 | HASH GROUP BY | | 100K| 2148K| 1207M| 380K (1)|
01:16:09 |
|* 6 | TABLE ACCESS FULL| LINEITEM | 34M| 733M| | 297K (1)|
00:59:35 |
|* 7 | SORT JOIN | | 50000 | 3613K| 8712K| 1182 (1)|
00:00:15 |
| 8 | TABLE ACCESS FULL | SUPPLIER | 50000 | 3613K| | 308 (1)|
00:00:04 |
Predicate Information (identified by operation id):
3 - filter("TOTAL_REVENUE"="ITEM_1")
6 - filter("L_SHIPDATE">=TO_DATE(' 1994-12-01 00:00:00', 'syyyy-mm-dd
hh24:mi:ss'))
7 - access("S_SUPPKEY"="SUPPLIER_NO")
filter("S_SUPPKEY"="SUPPLIER_NO")
Statistics
=========================================================
presumably temp table space will be used for sort and merge joins? .. but how does temp table space work with the view?

Global Temporary Table Space

Hi
Can any one give me some information about GLOBAL TEMPORARY TABLE.
Thnx & Regards
Sunil

http://download-uk.oracle.com/docs/cd/B10501_01/appdev.920/a96590/adg03sch.htm#7794

Clob temporary table space is not released

In our java web application, it uses datasource to call oralce stored procedure and get back data in Clob data type. The oracle version is 8.1.7.4. After the database call, the database connection is closed. But I found that the tablespace for Clob data is not released. Right now it becomes a critical issue of our production database. Anybody has any clue? Really appreciate.

Team,
We have a table of size 550gigs in size and we truncated the table , truncated sucessfully but space is not released in os level, what action we can take to release the space and this table has only one row and contains the binary data.
Thanks
PGR
Hello,
Yes space wont be released immediately .If large extents are in picture which I assume is your case it goes into deferred drop a background process which will execute after some time( time may vary).See below link for details.
As per BOL if extents are more than 128 it goes in deferred drop.
http://msdn.microsoft.com/en-us/library/ms177495.aspx
You should wait for some time .keep checking the free space
Below discussion will surely help you in understanding.See Jonathan's reply
http://social.msdn.microsoft.com/Forums/en-US/4aa2537e-246b-4bfe-818d-3482531d9149/sql-server-2005-massive-400gb-table-dropped-space-not-released
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Permanent tablesspace as temporary table space

Hi friends
I am having a database(8i) which uses normal(permanent) tablesspace as temporary tablespace(TEMPORARY_TABLESPACE). Is it compulsory that we have to create temporary ( I mean 'create temporary tablespace') tablespace for tempoarary tablespace . Is there any performance issue if i am using perment tablespace as temp tablespace.

As mentioned previously, a tablespace of type temporary should be defined for temporary tablespace (for each and every user.)
The purpose of the tablespace is for sorting WHEN THE SORT DOES NOT FIT IN MEMORY (sort_area_size) - and after the sort, the space is released.
It is entirely possible that all activity requiring sorting fits into memory for your system, so you would not see a performance hit. (btw - an index build is usually a sort.) I would recommend checking to see which objects may be in that tablespace.
Either way, I would create a new temporary tablespace of type temporary (new_temp).
Then I would 'alter user ' username temporary tablespace new_temp for each and every user in DBA_USERS.
As for the brevity of responses, I certainly can't blame Hans. After a fair amount of lurking on these boards, I get somewhat discouraged myself. Posts like 'Please Help me do my homework' , 'where can I download Oracle', and my absolute favorite 'What is one the Oracle Certification Test' actually make me chuckle, and mutter RTFM to my display.
What does seem to make me wonder, is how many of these people are 'learners' and how many actually hold a DBA title?

When to use PGA_AGGREGATE_TARGET and when to use temporary table space?

Hi, all.
I am a little confused with regard to when to use pga work area, and
when to use temporary tablespace?
Is there any one who could give me an advice or a document?
Thanks in advance.
Best Regards.
Message was edited by:
user507290

You are more than a little confused... What has one to do with the other, do you think?
All Oracle documentation is at http://tahiti.oracle.com - I suggest you start with the Concepts manual of your version

Temp Tables space problem with ORA-01114 and ORA-27072:

RDBMS :Oracle:9.2.0
OS: Linux AS3
Storage: SAND arrray (RAID 5)
Problem on exeuting dml statement
SQL> select * from myview ;
select * from myview
ERROR at line 1:
ORA-01114: IO error writing block to file 201 (block # 3977)
ORA-27072: skgfdisp: I/O error
Linux Error: 28: No space left on device
Additional information: 3976
ORA-01114: IO error writing block to file 201 (block # 3977)
ORA-27072: skgfdisp: I/O error
Linux Error: 28: No space left on device
Additional information: 3976
With Regards
Joy

Hello joy,
So, still looking for solution. I suggest you a sloution and it works well only if as you mentioned (in your previous post) that file causing error is temp file. So, get rid of this better you create new temporary table space and drop old one and then delete the old files manually.
But this will work only for Temp Tablespace not for normal tablespaces and datafiles. Prepare new temporary tablespace at different location from the previous one, try to make it on different disk beacuse it may be due to corruption of physical medium too.
Try this. If it works... you are through... otherwise i have no other options...
Please update.....

Insert slow into Global Temporary Table...

I am working with a stored procedure that does a select into a global temporary table and it is really slow. I have read up on the append hint and know that it is not a solution since GTT's are in the temporary table space which are thus always appended and never have logs.
Is there something else that I need to know about performance for GTT? I find it hard to believe that Oracle would find it acceptable to take 50 seconds to insert 3300 rows.

My apologies in advance as my skill level with Oracle is not as high as I would like for this type of analysis and remediation.
I had thought of it being the select as well but if I run it by itself it takes about 1 second. The interesting part is when I explain plan on it with the Insert, the SQL plan changes.
Here is the Non-insert explain plan:
<code class="jive-code jive-java">
Plan hash value: 3474166068
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 1 | 51 | 8 (38)| 00:00:01 |
| 1 | HASH GROUP BY | | 1 | 51 | 8 (38)| 00:00:01 |
| 2 | VIEW | VM_NWVW_1 | 1 | 51 | 7 (29)| 00:00:01 |
| 3 | HASH UNIQUE | | 1 | 115 | 7 (29)| 00:00:01 |
| 4 | NESTED LOOPS | | | | | |
| 5 | NESTED LOOPS | | 1 | 115 | 6 (17)| 00:00:01 |
| 6 | NESTED LOOPS | | 1 | 82 | 5 (20)| 00:00:01 |
| 7 | SORT UNIQUE | | 1 | 23 | 2 (0)| 00:00:01 |
| 8 | TABLE ACCESS BY INDEX ROWID| PEAKSPEAKDAYSEG$METERMASTER | 1 | 23 | 2 (0)| 00:00:01 |
|* 9 | INDEX RANGE SCAN | IDX_PDSEG$MTR_SEGID | 1 | | 1 (0)| 00:00:01 |
|* 10 | TABLE ACCESS BY INDEX ROWID | FC_FFMTR_DAILY | 1 | 59 | 2 (0)| 00:00:01 |
|* 11 | INDEX RANGE SCAN | FC_FFMTRDLY_IDX10 | 2461 | | 2 (0)| 00:00:01 |
|* 12 | INDEX UNIQUE SCAN | FC_METER_PK | 1 | | 0 (0)| 00:00:01 |
| 13 | TABLE ACCESS BY INDEX ROWID | FC_METER | 1 | 33 | 1 (0)| 00:00:01 |
Predicate Information (identified by operation id):
9 - access("SM"."SEGID"=584)
10 - filter(TO_DATE(TO_CHAR("V"."MEASUREMENT_DAY"),'YYYYMMDD')>=TO_DATE(' 2002-01-01 00:00:00',
'syyyy-mm-dd hh24:mi:ss') AND TO_DATE(TO_CHAR("V"."MEASUREMENT_DAY"),'YYYYMMDD')<TO_DATE(' 2003-01-01
00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND ("V"."ADJUSTED_TOTAL_VOLUME"<>0.0 OR
ROUND("V"."ADJUSTED_TOTAL_ENERGY",3)<>0.0))
11 - access("V"."METER_NUMBER"="SM"."METER_ID")
12 - access("M"."METER_NUMBER"="V"."METER_NUMBER")
</code>
Here is the Insert explain plan:
<code class="jive-code jive-java">
Plan hash value: 4282493455
| Id | Operation | Name | Rows | Bytes |TempSpc| Cost (%CPU)| Time |
| 0 | INSERT STATEMENT | | 39 | 2886 | | 7810 (1)| 00:01:34 |
| 1 | LOAD TABLE CONVENTIONAL | PEAKDAY_TEMP_CONSECUTIVEVALUES | | | | | |
| 2 | HASH GROUP BY | | 39 | 2886 | | 7810 (1)| 00:01:34 |
|* 3 | HASH JOIN RIGHT SEMI | | 39 | 2886 | | 7809 (1)| 00:01:34 |
| 4 | VIEW | VW_NSO_1 | 1 | 10 | | 2 (0)| 00:00:01 |
| 5 | NESTED LOOPS | | 1 | 27 | | 2 (0)| 00:00:01 |
|* 6 | INDEX UNIQUE SCAN | PK_PEAKSPEAKDAYSEG | 1 | 4 | | 0 (0)| 00:00:01 |
| 7 | TABLE ACCESS BY INDEX ROWID | PEAKSPEAKDAYSEG$METERMASTER | 1 | 23 | | 2 (0)| 00:00:01 |
|* 8 | INDEX RANGE SCAN | IDX_PDSEG$MTR_SEGID | 1 | | | 1 (0)| 00:00:01 |
| 9 | VIEW | PEAKS_RP_PEAKDAYMETER | 3894 | 243K| | 7807 (1)| 00:01:34 |
| 10 | SORT UNIQUE | | 3894 | 349K| 448K| 7807 (1)| 00:01:34 |
| 11 | NESTED LOOPS | | | | | | |
| 12 | NESTED LOOPS | | 3894 | 349K| | 7722 (1)| 00:01:33 |
| 13 | TABLE ACCESS FULL | FC_METER | 637 | 21021 | | 18 (0)| 00:00:01 |
|* 14 | INDEX RANGE SCAN | FC_FFMTRDLY_IDX11 | 6 | | | 10 (0)| 00:00:01 |
|* 15 | TABLE ACCESS BY INDEX ROWID| FC_FFMTR_DAILY | 6 | 354 | | 12 (0)| 00:00:01 |
Predicate Information (identified by operation id):
3 - access("METER_ID"="METER_ID")
6 - access("GS"."SEGID"=584)
8 - access("SM"."SEGID"=584)
14 - access("M"."METER_NUMBER"="V"."METER_NUMBER")
filter(TO_DATE(TO_CHAR("V"."MEASUREMENT_DAY"),'YYYYMMDD')>=TO_DATE(' 2002-01-01 00:00:00', 'syyyy-mm-dd
hh24:mi:ss') AND TO_DATE(TO_CHAR("V"."MEASUREMENT_DAY"),'YYYYMMDD')<TO_DATE(' 2003-01-01 00:00:00', 'syyyy-mm-dd
hh24:mi:ss'))
15 - filter("V"."ADJUSTED_TOTAL_VOLUME"<>0.0 OR ROUND("V"."ADJUSTED_TOTAL_ENERGY",3)<>0.0)
</code>
As you can see there is a real spike in the cost and yet the only thing that was done was the addition of the Insert to GTT. From what I can ascertain the solution may be in an alternate SQL or finding some way to push Oracle into running the query as it would have for the first execution (non-insert).
I tried creating a simple view out of the SELECT statement to see if that would precompile it but in the end it ran exactly the same way.
The next thing that I am going to try is removing the PEAKS_RP_PEAKDAYMETER view by going more direct.
I have not done the trace file analysis yet. Should I still do that?

Life time of data in a Global Temporary Table.

Dear Friends,
I have a global temporary table in which I insert some values via a backend package, when forms start up and accessing it via the same package when user performs some changes in it - storing the value and during exit saving it in the master table. My problem is the data is not accessible while processing. I'm using Oracle9i Enterprise Edition Release 9.2.0.1.0 database and Forms [32 Bit] Version 6.0.8.8.0. I also give you the script in using which I created the temporary table.
CREATE GLOBAL TEMPORARY TABLE GTT_PRA
A1 VARCHAR2(10 BYTE) NOT NULL,
A2 VARCHAR2(15 BYTE) NOT NULL,
A3 VARCHAR2(10 BYTE) NOT NULL
ON COMMIT DELETE ROWS;
Why is that so? Please help me.
With Regards,
Senthil .A. Perumal.

Dear Arun,
Thank you for your script. But I'm accessing a large table, so for each and every process, the table get populated and grows very large giving some space problem, that is why I'm deleting rows when commiting. I would appreciate your help.
Dear Yogesh,
From the same forms I'm calling the backend package - will that be a different session. Once I'm calling to populate the table and next time I'm calling to store the user modified data and finally calling to store the data to master table. I think all are in the same sessions. Please reply me.
Thank you dear friends fr your immediate response. I would really appreciate it.
Regards,
Senthil .A. Perumal.

How to purge data in a global temporary table from another session

I've got a problem with vendor-delivered web-based software (jdbc) that periodically "hangs." When that happens, I have to kill the database session before retrying the process. This "workaround" does NOT clean up the temporary tablespace. Is there anyway (outside of bouncing the database) to truncate temporary tables regardless of sessionid? Thanks.

In 8i the space used by temporary segments is not dropped in a temporary tablespace. The space is available for other queries or temporary tables. This avoids the costs of allocating and releasing space for temporary segments.

Not enough temporary storage space on disk

I'm new to Access. I've imported some tables from a co-worker, who cannot help troubleshoot this issue.
When I run a query, I get the error "Query cannot be completed. Either the size of the query result is larger than the maximum size of the database or there is not enough temporary storage space on the disk to store the completed result."
I've compacted the database.
I've searched online about how to increase the storage space on the disk.
Unsure what to do next

Hi,
Which Access version do you use? The issue might be related to some reasons.
1. Access database has its max size (2GB). While running a query it often needs temporary storage. It means that the normal size plus the temp size hits the 2GB file size limit of Access.
2. Caused by the query, any non-trivial query or operation can use a larger amount of temporary space.
3. Caused by the database, the column name in database is not the same of the output in the transformation.
Thus, we may try:
1. Using SQL Server 2008 Express as back-end database
2. Splitting your database into front-end and back-end - due to the size eventually multiple back-end files- and using linked tables.
http://office.microsoft.com/en-us/access-help/split-an-access-database-HA010342026.aspx
Regards,
George Zhao
TechNet Community Support

UNDO table space in oracle

Hi,
Recently i have added one data file(2GB) to undo table space.Later i gog to know it is not recommend to extent the undo table space.In oracle 9i undo management is handle automatically.(in my init<SID>.ora file undo_management='AUTO')
I have 3 data file undo_1,undo_2,undo_3.
undo_2 is the datafile of 2Gb that i have added.
My question is ....is there any possibility to remove that data file from the DB(undo_2) if possible how can i dod that.
Pls help me.
roshantha

SQL> show parameter undo
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 900
undo_tablespace string UNDOTBS1
SQL>
SQL>
##FIRST : CREATE AN ANOTHER TEMPORARY UNDO TABLESPACE FOR YOUR DATABASE USERS.
SQL> create undo tablespace UNDOTBS_TEMP datafile 'c:\undotbs_temp1.dbf' size 2G;
Tablespace created.
SQL> show parameter undo
SQL> alter system set undo_tablespace=UNDOTBS_TEMP;
System altered.
SQL> show parameter undo
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 900
undo_tablespace string UNDOTBS_TEMP
##NOW DROP YOUR UNWANTED TABLESPACE INCLUDING DATAFILES
SQL> drop tablespace undotbs1;
Tablespace dropped.
SQL> drop tablespace undotbs2 including contents and datafiles;
Tablespace dropped.
##NOW RECREATE THE UNDOTBS and RUSE THE FILE YOU WANTED TO
SQL> create undo tablespace UNDOTBS1 datafile 'C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\UNDOTBS01.DBF' reuse;
Tablespace created.
SQL> alter system set undo_tablespace=UNDOTBS1;
System altered.
SQL> show parameter undo
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 900
undo_tablespace string UNDOTBS1
SQL>
hope it helps :-)
Thanks,
Z

Alter Table Space Autoextend

Hi,
I got an Error like this
"ORA-01630 max # extents (string) reached in temp segment in tablespace string
Cause: A temporary segment tried to extend past MAXEXTENTS."
Is it possible to alter table space to Auto Extend in Oracle 8i With out Shutting down the
Database. What Exact Commands for this? Is this effect the performance of the database?
Please reply
With thanks Naseer

user13098327 wrote:
Hi,
I got an Error like this
"ORA-01630 max # extents (string) reached in temp segment in tablespace string
Cause: A temporary segment tried to extend past MAXEXTENTS."
Is it possible to alter table space to Auto Extend in Oracle 8i With out Shutting down the
Database. What Exact Commands for this? Is this effect the performance of the database?
Please reply
With thanks NaseerThe error you hit and your request is something different:
ORA-01630 - limitation of extents per object or per tablespace.
Tablespace autoextend - May be you mean datafile autoextend option.
Pls, specify.

Grant table create for only temporary tables

I looking for a way to allow user to create only temporary tables. The user does not need to create or drop any public tables.

Hi,
>>This is really a bad suggestion. The user1 can now only select his own tables, no insert or update. It can not be allowed in the "real world".
The OP said "I looking for a way to allow user to create only temporary tables"
I think that you didn't understand what I showed ...
SYSTEM@test> create user user1 identified by user1 default tablespace USERS quota 0 on USERS;
User created.
SYSTEM@test> create user user2 identified by user2 default tablespace USERS quota unlimited on USERS;
User created.
SYSTEM@test> grant create session,create table, create synonym to user1,user2;
Grant succeeded.
SYSTEM@test> connect user2/user2@teste
Connected.
USER2@test> create table x (id number);
Table created.
USER2@test> insert into x values (1);
1 row created.
USER2@test> grant select,delete,insert,update on x to user1;
Grant succeeded.
USER2@test> connect user1/user1@teste
Connected.
USER1@test> create synonym x for user2.x;
Synonym created.
USER1@test> insert into x values (2);
1 row created.
USER1@test> select * from x;
        ID
         1
         2
USER1@test> create table y (id number);
create table y (id number)
ERROR at line 1:
ORA-01536: space quota exceeded for tablespace 'USERS'
USER1@teste> create table user2.y (id number);
create table user2.y (id number)
ERROR at line 1:
ORA-01031: insufficient privileges
USER1@test> drop table user2.x;
drop table user2.x
ERROR at line 1:
ORA-01031: insufficient privileges
USER1@test> create global temporary table y (id number) on commit preserve rows;
Table created.
USER1@test> insert into y values (1);
1 row created.
USER1@test> select * from y;
        ID
         1
USER1@test>Cheers

Temporary Table issue

Hi All
I am using ODI 10.1.3.5
I have a requirement like the temporary tables created during interface execution should not be dropped .
Instead it should truncate and kept it for next execution.
I have used the option DELETE_TEMP_OBJECT to no in flow tab option of interface.
But it is keeping the objects as it is (i.e with data) which will again take memory space.
Is there any other option in ODI or i need to update the KMs to implement the above ???
any feedback will be appreciated.
regards
Gourisankar

Hi,
Add a step(s) to the KM to delete/truncate the temporary table(s). You may want to add an option to control this, similar to drop temp objects, so you do either or via the interface.
Thanks
Bos

Temporary table space?

Similar Messages

Maybe you are looking for