Storage parameter for Temp tablespace

Hi all,
Greetings of the day...
DB version is 10.2.0.4 ..Size of db is 550gb and in that temp tablespace is 40gb... daily and frequently we used to unable to extent temp segments...Saw the storage parameters of temp segments it has only 'EXTENT MANAGEMENT LOCAL UNIFORM SIZE 16777216'
Please suggest as how to define storage parameters for temp tablespace...Am able to find the query which uses temp segments...Just needed to know abt the storage parameters for it..
thanks,
baskar.l

CREATE TEMPORARY TABLESPACE TEMP TEMPFILE
'/u02/TSTLOG/temp01.dbf' SIZE 15360M AUTOEXTEND ON NEXT 100M MAXSIZE 32767M
TABLESPACE GROUP ''
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
Hope this will work.
Regards
Asif Kabir

Similar Messages

How to DB Storage PArameter for DSO

Hi,
I want to change DB storage parameter - Data Type and Size Category for DSO. How to go about it or i need to have a ABAP program to do the same? Presently it is
DATA Type DODS and Size Category 6 but i need to change both of these. Changing option is grayed out. Please suggest me some way out !

Hi
Do u have data in the DSO?
You can change DB Storage and other settings only when the DSO is empty
Please check
Empty out your DSO and change the settings
Cheers

Optimal size for TEMP tablespace tempfiles

Hi all,
I've rumaged through Oracle documentation on the above topic but can't find the answer I'm seeking:
How do you determine the optimal size for your tempfiles? Are there rules to guide one in this area? For example for a 50G database, how do you determine if it's 2G, 3G or 4G that's best for the database? What about a 500G database?
Anwers will be appreciated.
Regards

It's the size of the sets, as you say. And in a data warehouse, the data sets can be very large. I'd say that in an OLTP database, then the useage of temp would (should) be low; but in a data warehouse, all bets are off: one-off end of month runs; director wants a monolithic report running; all that sort of DWH-related type of processing, which, by its nature, happens all the time. Similarly, a large number of users (e.g. users of, say, a Third Party BI tool) amy lead to lots of big sorts, owing to the ad hoc nature of their queries. Standard DWH stuff.
I don't often see tiddly-widdly bits of SQL in data warehouses, like your SELECT COUNT(*) FROM tab$ example. It could be done, sure, but more likely will be bit, fat queries, which a DWH is designed to deal with. And a lot of temp may be required.
From that 6-years old (but relevant) article (my emphasis): "For example, if you join two *large* tables, and Oracle cannot do the sort in memory (see SORT_AREA_SIZE initialisation parameter), *space will be allocated in a temporary tablespace for doing the sort operation*."
Regards - Don Lewis

Determining datafile size for temp tablespace

Is there a rule of thumb for determining the size of the temporary tablespace, or at least a common starting value?
-Thanks
Chuck

Rule of thumb ... trial and error.
That is what your test environment is for.
We have over 200 databases with TEMP ranging from 50Mb up to 56Gb. So go figure!!!

STORAGE parameter in CREATE TABLESPACE

Hello all,
Env: 10gR2
I have the export of a schema of around 70Gb from 9i. I need to Import it to 10g.
This will be used only for 'SELECT', there wont be any DML once i import the data.
There are tables of size upto 20Gb.
What would be the best STORAGE parameters that i should be using along with the CREATE TABLESPACE if my db block size is 8k?
TIA,
JJ

If you are using locally managed tablespace then it is not required to specify storage parameters like initial, next and pctincrease. It is better to create LMT with uniform extent size. For the table with 20GB data create a seperate tablespace with uniform extent size as 1024MB. All tables of size more than 1GB can be allocated to this TS. For tabes of size between 100MB and 1GB create seperate tablespace of extent size 100MB. For all other tables create another TS with extent size 10M.
If you are using dictionary managed tablespace then calculate the size of tables and first create empty tables with the necessary initial and next value. Then import data with the option IGNORE=Y.
Mohan
http://www.myoracleguide.com

Size for TEMP tablespace

I don't know if this is a "valid" question. We have users running reports on our production system. The sometimes complain about the temp space being too small (due to their queries crashing when using too much temp space).
But I also have a feeling that you can keep throwing disks at TEMP space, and that it will never be enough.
What should the size of a database's TEMP space be - is there a rule of thumb for this ?
Dirk

There are several considerations that you should take into account when you try to size your temporary tablespace:
First, how much sort does you average transaction need and how many concurrent transactions does your system need to support. This number gives you a starting point for the minimum workable size for normal operations.
Now, how big is the largest table on your system and do you wish to be able to support select * from biggest order by ? Supporting an unqualified select on your largest table may not be required.
How big is the largest index in your system? It is likely that you need to have enough temp space available to recreate this index in the event of corruption without having to take special action to allocate more space to temp on a temporary basis. But having to add space in the event of a diaster might be acceptable.
Figure out what the largest sort operation you need to be able to support is and then add enough space to handle the number of concurrent average transactions that would be expected to be on the system at the same time. This is the size you should use for your temporary tablespace.
It is better to have all the space you will need for any normal and for any maintenance operation available at all time rather than trying to find additional file space to support special maintenance tasks or diaster recovery operations.
HTH -- Mark D Powell --

Maxsize 0 after autoextend turned off for Temp tablespace!

Hi,
DB:11.1.0.7
We had earlier the tempfiles with maxszie unlimited as below:
select FILE_NAME,TABLESPACE_NAME,BYTES/(1024*1024) "Size",MAXBYTES/(1024*1024) "Maxsize",AUTOEXTENSIBLE from dba_temp_files;
February 10, 2011 Tablespace used by DEV database
===================================
FILE_NAME
TABLESPACE_NAME Size Maxsize AUT
/oradata/DEV/temp01.dbf
TEMP 1024 32767.9844 YES
/oradata/DEV/temp02.dbf
TEMP 1024 32767.9844 YES
/oradata/DEV/temp03.dbf
TEMP 3072 32767.9844 YES
Now after turning autoextend off, why maxsize is showing as '0' instead of being at unlimited as earlier?
Please see below:
select FILE_NAME,TABLESPACE_NAME,BYTES/(1024*1024) "Size",MAXBYTES/(1024*1024) "Maxsize",AUTOEXTENSIBLE from dba_temp_files;
February 10, 2011 Tablespace used by DEV database
===================================
FILE_NAME
TABLESPACE_NAME Size Maxsize AUT
/oradata/DEV/temp01.dbf
TEMP 1024 0 NO
/oradata/DEV/temp02.dbf
TEMP 1024 0 NO
/oradata/DEV/temp03.dbf
TEMP 3072 0 NO
Could anyone please explain?
Thanks for your time!
Regards,

Handle:      user10088255
Status Level:      Newbie
Registered:      Mar 4, 2009
Total Posts:      87
Total Questions:      62 (62 unresolved)
so many questions without ANY answers.
http://forums.oracle.com/forums/ann.jspa?annID=718

INCLUDED_IN_DATABASE_BACKUP for temporary tablespace

Hi,
The query output from v$tablespace shows the INCLUDED_IN_DATABASE_BACKUP value for temp tablespace in my db is "YES". The only way to have the value "NO" is to configure rman to exclude tbs. But you can not exclude temporary tablespace. Based on the size of total full backup files, the temp tablespace does not seem to be backup by rman. Is this a bug or is there other way to set this value for temporary tablespace to "NO"? I'm using 9iR2. Thanks.

>...The only way to have the value "NO" is to configure rman to exclude tbs. But you can not exclude temporary tablespace.
RMAN doesn't include the temporary tablespace in the backups.
SQL> select * from v$tablespace;
       TS# NAME                           INC
         0 SYSTEM                         YES
         7 TEST                           YES
         3 USERS                          YES
        4 TEMP YES
         6 UNDO                           YES
RMAN> list backup of tablespace TEMP;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 01/26/2006 20:04:06
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20202: tablespace not found in the recovery catalog
RMAN-06019: could not translate tablespace name "TEMP"
RMAN> list backup of tablespace UNDO summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Tag
3125    B 0 A DISK        22-JUL-05       1       1       TAG20050722T102731
3207    B 0 A DISK        24-OCT-05       1       1       TAG20051024T163622
3248    B 1 A DISK        02-NOV-05       1       1       TAG20051102T225318
3360    B F A DISK        23-JAN-06       1       1       TAG20060123T172135Aron

Oracle 9i TEMP tablespace backup problem using RMAN!

Oracle8/8i whole backup is ok for our backup software(using RMAN without RC database), but for Oracle 9i, I get following error messages when backing up temp tablespace.
1. RMAN-20202: tablespace not found in the recovery catalog
2. RMAN-06019: could not translate tablespace name "TEMP"
I check some views of Oracle9i, and know some changes happen for temp tablespace in 9i, but how to deal with this problem. Any idea, please!

In 9i RMAN does not restore temporary datafiles. Instead, you should create them after your restore. I believe that Oracle is going to make a change to this in the next release of 9i and have RMAN create the temporary files. You can view the temporary datafiles @ v$tempfile.
I believe RMAN doesn't restore temporary files because they are locally managed and not in the control files. RMAN reads the controlfile of the target database to obtain info about backups, datafiles, etc.
Hope this helps.

Temp tablespace 99%full

What are the suggestion for temp tablespace, if its 99%full, should we keep adding space in it or it will use existing space?
TABLESPACE TOTAL_MB USED_MB FREE_MB PCT_USED GRAPH (X=5%)
TEMP 17,500.00 17,444.00 56.00 99.68 [XXXXXXXXXXXXXXXXXXX-]

Hi,
>>What are the suggestion for temp tablespace, if its 99%full, should we keep adding space in it or it will use existing space?
I think that you don't need worry about, unless you're receiving some ORA- error about out of space in TEMP tablespace. You can see below an SQL output from a database used here in my company for development and tests purposes. The database is up uninterruptedly by 7 months and the space size for the TEMP tablespace have been configured to use 900 MB.
LEGATTI@ORACLE10> SELECT tablespace_name, SUM(bytes_used), SUM(bytes_free)
2 FROM   V$temp_space_header
3 GROUP BY tablespace_name;
TABLESPACE_NAME                SUM(BYTES_USED) SUM(BYTES_FREE)
TEMP                                 943718400               0Cheers
Legatti

Change Storage Parameters for Tablespaces

Hi
I want to change the NEXT_EXTENT parameter to 100M for TS_DATA, TS_DATA1 and TEMP Tablespaces. for the following tablespace below
TABLESPACE_NAME INITIAL_EXTENT NEXT_EXTENT
TS_DATA 65536
TS_DATA1 65536
TEMP 1048576 1048576
Can anyone post the query for changing the parameter.
My database
BANNER
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 Solaris: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production
5 rows selected
Thanks in advance

sybrand_b wrote:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_3002.htm#i2093894
------------- I totally agree here. Try to find an answer in the docs first. It's not that hard to find
However I would like to give you one hint:
select extent_management from dba_tablespaces where tablespace_name in ( 'TS_DATA','TS_DATA1','TEMP');If this returns "LOCAL" as result your tablespace is Locally Managed instead of dictionary managed and therefore the next_extent value can not be changed.
HTH,
FJFranken
My Blog: http://managingoracle.blogspot.com

Storage clause for locally manged tablespace with unifom size extents

in oracle 9i PERSONAL EDITION
I HAVE CREATED A TABLESPACE TEST1 AS LOCALLY MANAGED WITH UNIFORM SIZE AS 256K.MY DB_BLOCK_SIZE IS 4K
I HAVE CREATED A TABLE XYX IN THE TEST1 TABLESPACE WITH THE STORAGE (INITIAL 52K NEXT 52K)
WHEN I QUERIED THE DBA_EXTENTS IT SHOWS THE INITAIL EXTENT AS 256 K
BUT WHEN I QUERIED THE DBA_SEGMENTS IT SHOWS THE INITAL_EXTENT AS 52K.
IS THEIR ANY SIGNIFICANCE OF SPECIFYING THE STORAGE CLAUSE IN LOCALLY MANAGED TABLESPACES.

take a example what is effect of set storage parameter in table whoes tablespace is locally manager and have uniform size
i have a tablespace whoes
[b]uniform size is 32k
but when i create a table then i set initial 128k
now when table is create it create 4 extent
of 32 each(32*4=128)
because tablespace uniform size is 32
if we give intial 256 then it create
8 extent(32*8=256)
like
create tablespace tt_check
datafile 'E:\ORACLE\SAFE_DATA\tt_check.dbf' size 10m
extent management local uniform size 32k;
create table tt_1
(no number)
tablespace tt_check
storage(initial 128k
next 128k);
1* select extent_id,segment_name,tablespace_name,bytes from dba_extents where segment_name='TT_1'
QL> /
EXTENT_ID SEGMENT_NAME TABLESPACE_NAME BYTES
0 TT_1 TT_CHECK 32768
1 TT_1 TT_CHECK 32768
2 TT_1 TT_CHECK 32768
3 TT_1 TT_CHECK 32768
hope it will help you
kuljeet pal singh

Alter the tablespace storage parameter

Hi,
I want to alter the tablespace storage parameter from 1024 to 200 KB. Can anyone please provide me what is the procedure? Its very urgent.
Suman

SQL> select tablespace_name, EXTENT_MANAGEMENT, ALLOCATION_TYPE, SEGMENT_SPACE_M
ANAGEMENT from dba_tablespaces;
Output of the sql
TABLESPACE_NAME EXTENT_MAN ALLOCATIO SEGMEN
SYSTEM DICTIONARY USER MANUAL
PSAPR3E LOCAL SYSTEM MANUAL
PSAPR3E620 LOCAL SYSTEM MANUAL
PSAPR3EUSR LOCAL SYSTEM MANUAL
PSAPTEMP LOCAL UNIFORM MANUAL
PSAPTF60D LOCAL SYSTEM MANUAL
PSAPUNDO LOCAL SYSTEM MANUAL
SYSAUX LOCAL SYSTEM AUTO
PSAPR3E700 LOCAL UNIFORM AUTO
Message was edited by:
 Amit Jain

TEMP datafiles for temporary tablespaces don't have same timestamp

Hi,
This is what I have done:
Installing 10G2 on XP PRO with sample database.
Tried to install Designer Repository with the Wizard, created a user for the toolkit, that failed.
Added 1 temp tablespace size 20Meg from OEM console.
Dropped cascade Toolkit schema owner and recreated it
Tried to install Designer Repository, that failed again
Added 1 temp tablespace size 1giga from OEM console, failed again to import
Dropped cascade Toolkit schema owner and recreated it
Tried to install Designer Repository, that failed again
Gave up for now: I have located a doc about installing manually by running scripts, will do as soon as I feel at ease with OEM.
Then I put the PC on snooze while database was up, crashed it.
Stopped the services, checked the logs, restarted manually and slowly, base up.
Now both extra TEMP datafiles are lagging behind, seen from Windows explorer, but the tablespaces are seen as online from oem, not seen from sqlplus dba_tablespaces view.
So the question is:
Are the TEMP datafiles supposed to stay in sync with the others or is it ok if they show timestamps dating three days back, provided there has not been any users transactions in the database?
I checked the 10G2 DBA online doc, but I can't find where it's mentioned.
Many thanks if you can help.

Hi,
Everything allright, they do show!
I'm a bit wary about resizing anything, maybe you remember the resizing bug for SYSTEM tablespace in version 7?
I have to beef up on DBA tricks.
Since I also have a 1 Giga Users tablespace, I'll do some heavy Inserting and Updating and Sorting see if that tickles the Temps.
Many thanks for your prompt reply.
Message was edited by:
JeanParis

Storage Parameter Settings for Cube

Hi , Thank alot for such a wonderful suggestions, We have 25 millions of records going to cube so for high load performance on cube Can you check and help me Data Base Storage Parameter Settings. can you tell if
Fact Table
1. Data Class for fact tables is DFACT or should i change to any other
2. Size 4 >150 MB or should i change to any other
Dimension Table
1. Data Class DDIM or should i change to any other
2. Size 0 <500 K or should i change to any other
Help me with this.
Thanks
Poonam Roy

Hi,
I don't think that we need to some extra settings at cube , if want to go with Acceletor.
I am not able give good info on it,because I have not yet worked on it. But if you spend some time to go through all the mentioed links,Definately You would not have any doubts on it.
Also refer the help link:
http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/48c0417951d117e10000000a155106/frameset.htm
If you donot have chance to use acceletors, then I suggest you think about Data marts (no of cubes with same structures and with ssame datasource) which holds physically have different range of data.And then use a Multi provider upon it.
And also use Cache methodology for the reports built on these cubes.And use precalculattion to heat up the cache.
Also check the 1025307 note.
With rgds,
Anil Kumar Sharma .P
Message was edited by:
Anil Kumar Sharma
Message was edited by:
Anil Kumar Sharma

Storage parameter for Temp tablespace

Similar Messages

Maybe you are looking for