Temp DB size

Hi, all,
We just installed a new program which uses SQL 2008 R2 DB. One of the recommended specs was 40 GB of temp DB size. Can anyone please explain what it meant by that?
What I have now is quadcore, dual procs server, tempdb has 1 temp primary file and 9 tempdev.ndf files. Each started with 1 GB initial size and unrestriced autogrowth.
Thank you very much in advance.

For high performance tempdb data and log should be on independent drives.
Disk configuration:
http://www.sqlusa.com/bestpractices/configureharddisk/
>The multiple files reduces the tempdb storage contention adding multiple files definitely a overhead.
Any documentation on that? Putting 10 tempdb files on the same (slow) drive will not improve performance to a significant degree.
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

Similar Messages

Maximum Temp tablespace size you've seen

DB version: 10.2.0.4
Our DB caters a retail application . Total DB Size of 3TB. Its is a bit of mix of both OLTP and Batch processing environment.
Our temp tablespace has 1 file and we had set the tempfile as AUTOEXTEND. Somehow its size has reached 25GB now !
We don't actually need this. Do we?
For a fairly busy DB of around 3TB size, what is the maximum temp tablespace size you've ever seen?
What is the maximum temp tablespace size you've ever seen for Big DB like Telecom, Banking?

The point about temp space is that your requirements are dynamic - the actively used area shrinks and grows.
Comparing apples with oranges, tempfile sizes on system where I am currently here amount to 50 GB but to be honest that's mainly due to a not insignificant number of pretty poor queries, run concurrently, with multipass operations, etc.
Kellyn Pedersen had an example of a process using 720GB here:
http://dbakevlar.com/?p=43
Whilst 25GB may not be earth shattering, a "large" temp area may perhaps be an indicator that you want to review some of your application code.
(What is "large"? "unusual" compared to what is "normal" for your system may be a better metric)
If you're using automatic pga memory management, then there's a limit to what each session can get, it may be that automatic work areas are not suitable for some of your code and some manual sizing is required to prevent operations spilling unnecessarily.
Also, inaccurate CBO estimates on your queries can lead to inaccurately sized work areas that then spill into temp.
There was a reminder of this in one of Randolf Geist's articles on hash aggregation:
http://oracle-randolf.blogspot.com/2011/01/hash-aggregation.html

What should be idea temp tablespace size ?

HI all
My databases size in between 20 gb to 100gb. waht factor should i consider to fix the temp tablespace size ?
What should be my ideal temp tablespace size for the both database ?

Arun Rao wrote:
HI all
My databases size in between 20 gb to 100gb. waht factor should i consider to fix the temp tablespace size ?
What should be my ideal temp tablespace size for the both database ?what is the version?
Temp size wont depends on database size, It purely depends on user sortings. Create the temporary tablespace with autoextend upto maxsize of 32gb approx & see how users performing sortings.
>
Handle:      Arun Rao
Status Level:      Newbie
Registered:      Jul 4, 2010
Total Posts:      10
Total Questions:      8 (7 unresolved)
Name      Arun Rao
Location      Mumbai
Occupation      DBA
>
7 out of 8 unanswered, if already answered why cant you close those threads? Keep the forum clean.
Edited by: CKPT on Jul 2, 2012 2:46 PM

SAP BO system temp required size

Hi all,
Based on the title. I would like to ask a few questions.
During migration will it take up alot of space in /temp?
If yes,what's the /temp size I should allocate in my new environment before migration? Given my current filestore size is about 900GB.
Do I need to allocate another 900GB of space for /temp?
Please forgive if I ask the questions wrongly. Thanks.

Hi Yue,
The error you get because tool is using default value for parameters TEMP and TMP which in your case is /temp.
Please refer below SAP note to change the location for TEMP and TMP variable.
You may choose a path which has enough space.
1964197 - Upgrade Management Tool hangs during 'Export' phase with 'An exception occurred that prevents the reading or writing of an object to or from storage'
Hope this helps.
Regards,
Deepak Kori

TEMP datafile size

Hi,
my TEMP datafile increase to 32G.
Why it do that and how to correct this situation.
Any suggestion, Thanks.

First, if you have your TEMP tablespace set to autoextend without specifying a maximum size, I would address that problem.
Second, how big should your TEMP space be?
Third, if your TEMP space grew to 32 GB, someone was either running a tremendous query or a large number of people were simultaneously running rather large queries. Depending on whether this was appropriate-- maybe someone really needed to generate a report that sorted 32 GB of data-- we can suggest ways to move forward.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

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

2Gb Temp Size Limit / Reports Server

Hi everybody,
We are experiencing a problem with Reports 6i Server (NT) that bugs when the size of the tempfile generated to create the output (in our case : pdf) equals 2Gb ...
My question is : is it a reports server bug ? And, if so, do you know if it is corrected in 10gAS Reports Server ?
Thank you everybody ...

That is
Bug1309259 - ELIMINATE THE 2GB FILE SIZE LIMITATION FOR TEMP FILE SIZE
and is not fixed yet (in 10g).
1) If this is critical to you, and you have a support contract, you can try escalating the bug with Oracle Support.
2) When somebody else reported this for their particular report, how it was solved was that their particular report was tuned and optimised and this issue was solved. (So you can also try tuning your report and SQL queries)

Need help -To Restrict Huge temp file, which grows around 3 GB in OBIEE 11g

Hi Team,
I am working on OBIEE 11.1.1.5 version for a client specific BI application. we have an issue concerning massive space consumption in OBIEE 11g installed linux environment whenever trying to run some detail level drill down reports. While investigating, we found that whenever a user runs the drill down report a temp file named nQS_xxxx_x_xxxxxx.TMP is created and keep's growing in size under the below given folder structure,
*<OBIEE_HOME>/instances/instance1/tmp/OracleBIPresentationServicesComponent/coreapplication_obips1/obis_temp/*
The size of this temp file grows huge as much as around 3 GB and gets erased automatically when the drill down report output is displayed in UI. Hence when multiple users simultaneously try to access these sort of drill down reports the environment runs out of space.
Regarding the drill down reports:
* The drill down report has around 55 columns which is configured to display only 25 rows in the screen and allows the user to download the whole data as Excel output.
* The complete rows being fetched in query ranges from 1000 to even above 100k rows. Based on the rows fetched, the temp file size keeps growing. ie., If the rows being fetched from the query is around 4000 a temp file of around 60 MB is created and gets erased when the report output is generated in screen (Similarly, for around 100k rows, the temp file size grows up to 3 GB before it gets deleted automatically).
* The report output has only one table view along side Title & Filters view. (No Pivot table view, is being used to generate this report.)
* The cache settings for BI Server & BI Presentation services cache are not configured or not enabled.
My doubts or Questions:
* Is there any way to control or configure this temp file generation in OBIEE 11g?
* Why the growing temp file automatically gets deleted immediately after the report output generation in screen. Is there any default server specific settings governing this behaviour?
* As per certain OBIEE article reference for OBIEE 10g, I learnt that for large pivot table based reports the temp file generation is quite normal because of huge in-memory calculations involved . However we have used only Table view in output but still creates huge temp files. Is this behaviour normal in OBIEE 11g. If not, Can any one Please suggest of any specific settings to be considered to avoid generating these huge files or atleast generate a compressed temp file.
* Any other work around solution available for generating a report of this type without the generation of temp files in the environment?
Any help/suggestions/pointers or document reference on this regard will be much appreciated. Please advice
Thanks & Regards,
Guhan
Edited by: 814788 on 11-Aug-2011 13:02

Hello Guhan,
The temp files are used to prepare the final result set for OBI presentation server processing, so as long as long you dataset is big the tmp files will be also big and you can only avoid this by reducing your dataset by for example filtering your report.
You can also control the size of your temp files by reducing the usage of the BI server.I mean by this if you are using any functions like for example sorting that can be handled by your database so just push to the DB.
Once the report finished the BI server removes automatically the tmp files because it's not necessary anymore.you can see it as a file that is used for internal calculations once it's done the server gets rid of it.
Hope this helps
Adil

Error while displaying file " C:Temp Filename.Ext cannot be created"

Dear Friends
Some users face problem while display the file. They get message " C:\Temp\ Filename.Ext cannot be created ". I checked Details. I got explaination as follows.
Caution! You are not authorized to work with temporary storage
Message no. ED204
Diagnosis
You do not have authorization to read or write from or to the temporary storage.
The system uses the temporary storage when you display or change programs using the ABAP Editor.
The system checks to see whether there is a temporary version of the program.
If there is, a dialog box appears in which you must choose whether to use the temporary version or the database version.
The system fills the temporary storage when the editor crashes or you save a temporary version of the program.
System Response
You probably do not have the authorization object S_DATASET.
Procedure
Ask your system administrator to assign you the relevant authorization.*
Actually this problem never occurs frequently. User access the files very frequently creating around 200 Mb to 400 Mb in C:\Temp Folder per day per user. I observerd as per message that User is not have Access right to C drive. Once I get access from IT for that user he is able to display file. But before giving right he is able to display file. But suddenly he is not able to display. I am not getting exact reason why this problem occurs. Some users temp folder size is upto 700 Mb with no acces right to C Drive still he is able to see the image.
In DC20 I have kept C:\Temp as path for temp folder.
I have checked the links also
Request you to provide me
What is exact reason of the error?
Is the solution to problem is giving access rights to the user?
Do I have to give authorization object S_DATASET to a user?
With Regards
Mangesh Pande

Dear Amaresh
Thanks for your reply and solution.
So you mean to say thats this Authorization object has to be provided to user?
But my question is how the user was able to see the file even when this Authorization Object was not assigned.
He was able to display all file. But for particular DIR he is not able to display.
I have checked this thread
http://wiki.sdn.sap.com/wiki/display/PLM/Error26172withSAPGUI710+patch13.
User has SAP GUI 7.10
File Version 7100.1.0.1027
Build 0
Patch Level 0
Request your help
With Warm Regards
Mangesh Pande

Photoshop CS6 temp memory problems

Hi,
My name is George,
I'm working as a web-designer. I heard about new features in Photoshop cs6, like paragraph/character styles (something very good for web-designers).
And tried those new features, works perfectly, but i found a big problem.
When we are working in Photoshop, it instantly creates a PhotoshopTemp file in C:\Users\UserName\AppData\Local\Temp, and when I tried to create new paragraphs styles or character styles the memory of that temp files is increasing until your partition memory is not filed at all, for example at that moment in my C:\ partition I had about 3GB free memory, initially the PhotoshopTemp file had about 200MB, but when I tried to create a new paragraph style, temp file size increased up to 3.2GB, consuming all my C:\ drive free memory
If you have any ideas, please help me...

Pisarenco wrote:
You see, the idea is that 3gb is enougth…
Not even remotely!
Figure on needing 35 to 70 times as much Photoshop scratch disk space—or more—as the size of your largest open file. Multiply that by the number of files you keep open, and add a bunch of GBs for the swap files of the OS.
Additionally, a good rule of thumb is not to let any drive get more than 75%–80% full.
The poster above who replied to your post is not just any Adobe employee, but a top Adobe engineer who has been writing Photoshop code for 16 years or longer. You'll be wise not to dismiss his advice.
Whatever your machine is, it's not adequate for a working web designer.

Increasin the temp tablespace

Hello All,
I am using Oracle 11g R2 i want to increase the temp tablespace size. can i use the below command? can i increase while the database is open and some queries are running and use the temp table space?
ALTER DATABASE TEMPFILE '....../datafile/name_datafile.tmp' RESIZE 100M
Regards,

Hello,
I am using Oracle 11g R2 i want to increase the temp tablespace size. can i use the below command? can i increase while the database is open and some queries are running and use the temp table space?Why do you intend to extend the Temporary Tablespace ? Do you have any ORA-01652 error ?
If not, may be it's not necessary to extend it. Even if it seems to be full Free Extents are reused.
ALTER DATABASE TEMPFILE '....../datafile/name_datafile.tmp' RESIZE 100MYes you can use this statement, but be aware that the Size specified (here 100 Mo) is the target size not the supplemental size.
Hope this help.
Best regards,
Jean-Valentin

The Sky is Falling! ORA-01652: unable to extend temp segment by 128

So we currently have a production problem and I'm not so in the know as a lowly java developer and not an Oracle expert.
We keep getting this error(below) when a certain heavy query hits the DB.
Our DBA claims that the tablespace for 'TABLE_SPACE_NAME_HERE' is 20GB of space and that the problem is the query.
The query has been running fine for many many months but all of a sudden is presenting a problem and we have to do something quick.
We tried bouncing the application server but the error came right back when the big select query gets hit.
Any thoughts? Help! : )
java.sql.SQLException: ORA-01652: unable to extend temp segment by 128 in tablespace TABLE_SPACE_NAME_HERE
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:113)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:754)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:219)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:972)
     at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1074)
     at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:854)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1156)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3415)
     at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3460)
     at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:296)

LosLobo wrote:
So, the next question... what is our lesson learned in this case?It depends on the root cause.
Our DBA thinks 30GB is an unreasonable size for the tablespace and is fingering the select query that was causing the error to occur. Their solution is move to the query to a view and then reduce the tablespace back to 20GB.
My thoughts are shouldn't the DB be able to handle a query that has been running fine for the last couple years? Also, if we do what is suggested what would prevent another query from coming along and causing the same issue all over again?Has the DBA identified the source of the issue? Did the query plan change? It's possible that something with statistics (or with some configuration change) causes Oracle to believe that two different query plans are roughly equally efficient. One plan might take substantially more TEMP space than another. It's possible that Oracle had been choosing the plan that involved less TEMP space being used and recently changed to preferring the plan that takes more TEMP space. If that's the issue, you may want to force Oracle to use the plan that involves less TEMP usage.
Regardless of your TEMP tablespace size, another query may come along that causes TEMP to run out of space. Or data growth may cause TEMP to run out of space. Or an increase in the number of users may cause TEMP to run out of space. Ideally, the DBAs would be identifying how much TEMP space is used over the course of the day so that if things are growing steadily additional space can be added as necessary. If TEMP space increases dramatically because a query plan changes, however, even the best monitoring is unlikely to be able to predict that level of growth.
Whether 30 GB is unreasonable (or whether 20 GB is unreasonable) will depend heavily on your application. We don't know enough to be able to comment. A TB-sized OLTP database serving millions of customers will have very different TEMP requirements than a multi-TB data warehouse which will have very different TEMP requirements than a small department-level application.
My surmising is we must have just crossed a watermark threshold and the simplest most reasonable solution is to just leave the larger tablespace size.Why do you believe this is the case? It is entirely possible that you need more TEMP because your TEMP usage has been growing slowly over time. It is entirely possible that the query in question has always been using more TEMP space than it really should and that you finally have enough usage to cause the problem to bubble to the surface. It is entirely possible that the query used a reasonable amount of TEMP for the past couple years and suddenly started using far more because of a query plan change. Once you identify the source of the problem, we can figure out the appropriate solution. Without knowing the source of the problem, we're all just guessing.
Justin

ORA-01652: unable to extend temp segment by 128 in tablespace TEMP

Hi,
I am getting the following error while executing an insert query.
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP.
I have tried increasing the TEMP tbsp size it got resolved temporarily but occurred again after few days.
When the problem occured, following query shows all insert queries in TEMP tablespace and one of them consumes about 5GB and others are about 24MB.
SELECT S.sid || ',' || S.serial# sid_serial, S.username,
T.blocks * TBS.block_size / 1024 / 1024 mb_used, T.tablespace,
T.sqladdr address, Q.hash_value, Q.sql_text
FROM v$sort_usage T, v$session S, v$sqlarea Q, dba_tablespaces TBS
WHERE T.session_addr = S.saddr
AND T.sqladdr = Q.address (+)
AND T.tablespace = TBS.tablespace_name
ORDER BY S.sid;
The insert query is :
INSERT INTO SEOSDATA (ENTRYID,DOMAINNAME,USERNAME,EVENTTYPE,LOGNAME,TIMSTAMP,SOURCE,COMPUTERNAME,EVENTID,EVENTCATEGORY,SEARCHSTRINGS,MSGTEXT) VALUES (ENTRYID_SEQ.NEXTVAL,:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11)
It is not expected that an insert query consumes such a huge memory.
Can someone help me in figuring out what the problem is.
What might have gone wrong? Seems like sorting is used, why an insert query uses sorting?
Regards
Ishu

Hi,
Insert statement should not use TEMP tablespace. Please check with following query which user and session id is using TEMP tablespace.
SELECT b.tablespace, b.segfile#, b.segblk#, b.blocks, a.sid, a.serial#,
a.username, a.osuser, a.status
FROM v$session a,v$sort_usage b
WHERE a.saddr = b.session_addr
ORDER BY b.tablespace, b.segfile#, b.segblk#, b.blocks;
Dilipkumar Patel.

Query erroring out with lack of temp space?

I have 2 databases. One was cloned from the other on to another server.
On one server the query takes 5 seconds to run on the other server the query errors lack with lack of disk space.
The init files are the same. The Oracle memory is the same. The temp tablespace size is the same.
I'm stuck!
What should I look for to find out what is causing the error?

On both databases the version is 9.2.0.6.
This is the view that worked in database1 and errored in database2...
CREATE OR REPLACE VIEW SAP_STAGE.MTC_STG_MEASURE_POINT_V
EQUIP_NO,
MEASUR_PNTPOS,
CHARACT_NAME,
UNIT,
MEASUR_PNT_DESC,
VALUATION_CODE,
TEXT_FIELD
AS
SELECT DISTINCT xref.equnr AS equip_no, rpmp.*
FROM sap_stage.measuring_point mp JOIN xref_sap_equi xref
ON TRIM (mp.equip_no) = TRIM (xref.groes)
JOIN stg_mtc_msf600 msf600
ON TRIM (mp.equip_no) = TRIM (msf600.equip_no)
AND TRIM (msf600.dstrct_code) in ('347','315')
JOIN rec_prodstat_code_measur_pts rpmp ON 1 = 1
If I qualify all the tables with SAP_STAGE the query runs in 5 seconds in database2.
Why does the query run in database 1 without the schema names?

Relation between temp tablespace and index creation

Hi,
I have my Oracle database (11gR1) on windows 2008 server R1 64 bit..
This is my development database. i have one table which has more than 2 billion rows , the problem i m facing here is while creating the index on this table i m getting temp segment error , while my temp tablespace size is 32 gb.
Here my doubt is :
1.What will happen in temp tablespace when index is created ? Relation between temp and index creation ?
2. how to create the index on a huge table?
3. What is the meaning og logging and no logging in INDEX creation .
4. how can we over come for these kind of problem and manage the temp TS..
Thanks & Regards,
Vikash Chauradia

add another tempfile?
1.What will happen in temp tablespace when index is created ? Relation between temp and index creation ?
index creation needs sort. how much depends on the size of the index.
2. how to create the index on a huge table?
create an interim (temporary? :)) huge temporary space for the very purpose.
http://docs.oracle.com/cd/B28359_01/server.111/b28310/indexes003.htm#i1006643
3. What is the meaning og logging and no logging in INDEX creation .
nologging means you the creation isnt in the logs so if you need to recover you cant get back to it. when using nologging in a prod env you might do it for performance during a period of heavy dml such as a large index creation and then backup afterwards. common enough.
4. how can we over come for these kind of problem and manage the temp TS..
current tempspace size =X
is X big enough? if yes, cup of tea, if no, make X bigger.
It doesnt matter what X is.

Temp DB size

Similar Messages

Maybe you are looking for