Temp Tablespace Group or Not

Hi Gurus,
We are in desiging phase of databse and wanted to look at the benefits for temporary tablespace group over the conventional temporary tablespace.
Any idea?
Thoughts are welcome
Can somebody move this thread to Database General? I think I have posted it at wrong place
Regards,
Virendra
Edited by: Virendra.K1.Yadav on Oct 1, 2012 1:32 PM

The thrust of my replies is that OP hasn't really determined 'the type of thing' that needs done so, as yet, there IS no target to aim at. The solution could be as simple as enabling PARALLEL operations that are disabled server wide for some reason. The example doesn't resemble the temp tablespace group as PARALLELISM by default is enabled but temp tablespace group is not. As mentioned by John I am still in design phase of new database as we are migrating from orace 10gR2 to 11gR2 and was thinking of option. In 10g temp space is around 700G and we are trying to decrease it as low as possible without affecting the query performance at least (if not improve).
Certainly it can be informative to study and learn Oracle features, what they are for, relevant scenarios, etc. But you still wind up with a solution waiting for an appropriate problem. One can not wait for the bug to be hit and then apply PSU. There are two things proactive and reactive. Waiting for problem to occur and then go for solution is not a good idea for me and I consider more investment in designing than in maintaining.
It is the problem/cause definitions that are lacking here. Until an appropriate problem has been identified there isn't really any basis for applying any particular solution.I don't agree, sitting idle and waiting for problem to occur and then applying solution.
Regards,
Virendra

Similar Messages

TEMP Tablespace Groups

In Datawarehouse environment, Database verion 10gR2:
Created two temp tablespaces TEMP1 and TEMP2 with 10GB each in a temp tablespace group(TEMP_GROUP) and assigned the TEMP_GROUP as default temporary tablespace to user "BATCH", expecting the batch user can use 20GB of temp tablespace.
When a process needs a temp tablespace of more than 10GB, the process fails with an error unable to extend temp tablespace. It is not utilizing the other 10GB TEMP tablespace.
When I assign a dedicated TEMP tablespace TEMP3 with 15GB as the default temp tablespace, the process succeeds.
It looks like when a session starts it assigns one TEMP tablespace(from group), if that fills up it is not taking advantage of the other TEMP tablespace in the group, which makes me think that Groups are not helping here.
Is there an other way around to utilize multiple temp tablespaces for a single user.
Can we expect an improvement of this feature in the future releases or is that not a possible scenario?

-- Using a tablespace group, rather than a single temporary tablespace, can alleviate problems caused where one tablespace is inadequate to hold the results of a sort, particularly on a table that has many partitions. A tablespace group enables parallel execution servers in a single parallel operation to use multiple temporary tablespaces.
CREATE TEMPORARY TABLESPACE TEMP2 TEMPFILE '/u10/oracle/oradata/dbt1/datafile/temp02.dbf'
SIZE 20M
TABLESPACE GROUP tempgroup1;
CREATE TEMPORARY TABLESPACE TEMP3 TEMPFILE '/u10/oracle/oradata/dbt1/datafile/temp03.dbf'
SIZE 20M
TABLESPACE GROUP tempgroup2;
ALTER TABLESPACE temp TABLESPACE GROUP tempgroup1;
select * from v$tempfile ;
select * from dba_tablespace_groups ;
alter user ABCD temporary tablespace tempgroup1 ;
-- Verify that temp group is assigned to user
select * from dba_users where username='ABCD' ;
After you assign the group to the user abcd then retry your operation as abcd user.
This time it will use both the temporary tablespaces for sort operations.
Thanks
GC

Qeustion regarding temp tablespace group

Hi All,
I am new to this concept. I've been reading about it but there is something I am not sure to understand.
If I have a temp tablespace group using tablespace temp1 and temp2 and a user submit a large query, will the query use both temp1 and temp2 or just 1 of them?
Group Name: temp
Tablespace: temp01 (1 datafile temp01.dbf)
Tablespace: temp02 (1 datafile temp02.dbf)
Thank you!

1. A single workarea execution can't use space from more a single tablespace even when the user is assigned a temporary tablespace group. Or in other words: A single workarea execution can only allocate a single temporary segment, and segments in general can't span multiple tablespaces in Oracle, i.e. they must fit into a single tablespace.
2. Even multiple workareas for a single session can't use space from the multiple temporary tablespaces available. So this looks like a session attribute, i.e. assigned to the session, and all workareas of that session will use the single temporary tablespace assigned (taken from the group)
3. Multiple sessions of the same user can be assigned to different temporary tablespaces taken from the group.
4. Parallel execution slave sessions can do the same, they can be assigned to different temporary tablespaces taken from the group.
So in order to leverage the power of temporary tablespace groups you need either multiple sessions running serial SQL or the parallel execution option.
Source:http://oracle-randolf.blogspot.in/2009/06/temporary-tablespace-groups.html
Regards
Girish Sharma

Why temp tablespace automatic extent not allow

why we cannot use automatic extent allocation for tempoary tablespace plz tel me the reason

Hi,
Its Optional Caluse, but you need to understand the things what it peforms. Basically what will be the advantage of Autoallocate Option, its going to allocated the extents based on the increase in requirement of Extents based on the data. Think off , due to think is it necessary to use that Option, that too where the data is going to be reside for temporary sake. I don't think. One more thing the data persits with respect to session.
Main purpose of Temporary tablespaces is to improve the concurrency of multiple sort operations that do not fit in memory and can improve the efficiency of space management operations during sorts. Do remember it is Optional Clause as I said before by default it creates temporary tablespaces with locally managed extents of a uniform size.
- Pavan Kumar N

Temporary tablespace groups - all available temp files not used

We have a temporary tablespace group TEMP_GROUP made of the following pre-existing temp files. I have placed the size in MB in brackets. Names have been changed to protect our privacy. NLS is spanish
SQL> select * from dba_tablespace_groups;
TEMP_GROUP TEMP1 --(1024)
TEMP_GROUP TEMP2 --(2000)
TEMP_GROUP TEMP3 --(8048)
This tablespace group is the default temp tablespace of this database, and is the default temp tablespace of sys in the example that follows
connect sys/password
alter INDEX schema1.idx1 rebuild
ERROR en línea 1:
ORA-01652: no se ha podido ampliar el segmento temporal con 128 en el tablespace TEMP1
-- this coinicdes with the TEMP1 showing 100% used
NOTE that the message refers to the tempfile TEMP1 and not the TEMP_GROUP, which has 11GB of space available
The size of the index is small enough to be handled by this TEMP_GROUP, although quite large to be handled by TEMP1 on its own.
SQL> SELECT sum(bytes)/1048576 Megs, segment_name
2 FROM dba_extents
3 WHERE segment_name = 'IDX1'
4 GROUP BY segment_name
5 /
MEGS SEGMENT_NAME
840 IDX1
What appears to be happening is that when the rebuild index has used all the space available in TEMP1 tempfile, it does not go on to use the space available in the other two tempfiles that make up the TEMP_GROUP. This seems to be contrary to the very idea of having set up a TEMP_GROUP.
This suposition is born out by the repitition of the operation using the owner of the index, whose default temp file is not TEMP_GROUP as a whole, but the component tempfile TEMP_3 which has 8048MB available
connect schema1/password
SQL> alter INDEX schema1.idx1 rebuild
Índice modificado.
-- This time the index does get rebuilt, pesumably because there is space available in TEMP_3 to carry out the rebuild.
My questions are
1. ¿Why does the original operation fail out when it has reached the limit of tempfile TEMP1 instead of using the further space availbel within TEMP_GROUP? ¿Isn´t the point of temporary tablespace groups the explicit avoidance of this type of issue?
2. Depending on the answer to #1, and asuming that the behaviour is normal (ie, that a rebuild index should not be expected to take place using more than one temp file), does anyone have any idea ¿what dicatates the order of usage of the component temp files in a group?. ¿Is it alphabetical order of tempfile name?, ¿file create time? or ¿something else?
3. As I mentioned the group was created out of existing tempfiles, rather than creating some temp file specifically to form the group. ¿Could this fact explain the inability of the operation to move onto the next temp file, once the first is exhausted. There is nothing in the documentation to suggest that there should be any difference in behaviour between a temp group created with new temp files, or the inclusion of existing temp files when creating a temp group.
As you can see, we have worked round this problem, but it is an issue of importance given that it may affect other operations that leverage this temp file group. Any information or pointers to documented instances of similar occurances would be greatly appreciated. Thank you.
Edited by: user602617 on 06-may-2009 0:57

Half solved. This thread seems to suggest that there should be n expectation that a sort operation will begin to use the n+1 member of a temp tablespace group once it has exhausted member n.
TEMP Tablespace Groups
But this does not answer my secondary question as to how to determine which temp tablespace member is used first. I guess the solution would be to drop the the group and recreate it with three adequatly sized temp tablespaces.

Can we create a table in temp tablespace?

Hi Support ,
I have confused about on point that Can we create a table in temp tablespace.
thanks

I so not think the question is so bad except that it was as suggested something you can determine for yourself in 20 seconds:
> /
create table mark (fld1 number) tablespace tmp
ERROR at line 1:
ORA-02195: Attempt to create PERMANENT object in a TEMPORARY tablespace
Other database products allow users to create tables in the temporary tables such as SQL Server. I just tested using SQL Server 2008 R2 and I could create a table in TEMPDB.
SQL Server also creates temporary tables, create table #table_name, in TEMPDB. You can see these objects while in use.
IMHO -- Mark D Powell --

10g temp tablespace

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

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

Smon not clearing my temp tablespace

hi guys,
even after I shutdown and restart my instance, my temp tablespace is showing as having 27.5 out of 30G used. why is this happening?
thanks

Hi OracleGuy777,
It is "normal" that temp tablespaces appear full, as the segments are not de-allocated. To know how much space is being used by active queries and to know if your are about to run out of temp tablespace use v$sort_usage and v$sort_segment.
E.g.:
These were for 8i/9i - should be OK in 10:
select TABLESPACE_NAME,TOTAL_BLOCKS,USED_BLOCKS,
FREE_BLOCKS, round((used_blocks/total_blocks), 2) "PERC_USED"
from v$sort_segment;Or:
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;or for user details:
SELECT a.sid, a.username, a.osuser, a.program, a.tablespace_name,
a.bytes "BYTES_USED", round(a.blocks / b.total_blocks,3) "PERC_USED"
from (select sor.tablespace_name, ses.sid, ses.username,
ses.osuser, ses.program, sor.blocks, sor.bytes
from (select /*+ optimizer rule */ u.tablespace "TABLESPACE_NAME", u.session_addr,
sum(u.blocks) blocks, sum(u.blocks) * &blksize bytes
FROM v$sort_usage u GROUP BY u.session_addr, u.tablespace) sor,
(select /*+ optimizer rule */ saddr, sid, username, osuser, program from v$session) ses
where ses.saddr=sor.session_addr) a, (select tablespace_name, sum(decode(maxblocks,0,blocks,maxblocks)) "TOTAL_BLOCKS"
from dba_temp_files group by tablespace_name) b
where a.tablespace_name=b.tablespace_name order by a.bytesCheers,
Francisco Munoz Alvarez
http://www.oraclenz.com

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.

One Temp Tablespace vs 2 Temp Tablespaces in a Group

I run a massive group by that generally takes up about 325GB of temp and on the system that it works on I have 1 tablespace this size that it works on, but I'm building a new system that has my Temp tablespaces on much faster disks, but I was trying to utilize 2 temporary tablespaces to get some parallelism accomplished, so I have 2 196GB tablespaces, but one of them fills up before the other one does...is their anyway to regulate what temp tablespace is used..should these 2 equally distribute the load when one fills up? My query just keeps blowing up when it runs out of the one temp tablespace. Any help is appreciated.

I run a massive group by that generally takes up about 325GB of temp and on the system that it works on I have 1 tablespace this size that it works on, but I'm building a new system that has my Temp tablespaces on much faster disks, but I was trying to utilize 2 temporary tablespaces to get some parallelism accomplished, so I have 2 196GB tablespaces, but one of them fills up before the other one does...is their anyway to regulate what temp tablespace is used..should these 2 equally distribute the load when one fills up? My query just keeps blowing up when it runs out of the one temp tablespace. Any help is appreciated.

Can you tell me why my temp tablespace can not release automatically?

when i up the database, the temp tablespace is used by o,but after some time it is used 99.99%,even all the task are finished,it is still used 99.99%,and can not release automatically!
who can tell me than is why?

Are you receiving an error ?
A "Temporary" tablespace manages it's allocation differently than a normal tablespace. The idea is to avoid the overhead of extent allocation, etc.
Take a look at:
http://asktom.oracle.com/pls/ask/f?p=4950:8:134496932618587661::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:108812348061,
or
http://asktom.oracle.com/pls/ask/f?p=4950:8:134496932618587661::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:1384603628260,
or (these URLs don't seem to be pasting correctly)
go to Ask Tom and search on "temporary" in the "page contains" option in advance search.
Ken

PDB without local TEMP Tablespace

Due to the Oracle Database 12c Concepts Guide it should be possible to create a PDB without a local TEMP Tablespace and the create PDB syntax includes the option (MAX_SHARD_TEMP_SIZE).
But I cannot find any hint how to create a PDB without a TEMP Tablespace or how to change the default temp tablespace to point to the CDB:
Any help will be appreciated.

There is no standard way to create a PDB without a TEMP tablespace
Yes - there is. But you CLEARLY don't want to do things the standard way. You want to use some particular non-standard way.
It is not 'standard' to create a database without a temporary tablespace. That is almost ALWAYS a mistake. That generally happens when you use the CREATE DATABASE command and don't specify it properly.
When you create a database you do NOT have to create a temporary tablespace. That has been the RULE from the very beginning and it is still true for 12c. For proof see the DBA Guide:
http://docs.oracle.com/cd/E16655_01/server.121/e17636/create.htm#i1009290
Creating a Default Temporary Tablespace
The DEFAULT TEMPORARY TABLESPACE clause of the CREATE DATABASE statement creates a default temporary tablespace for the database. Oracle Database assigns this tablespace as the temporary tablespace for users who are not explicitly assigned a temporary tablespace.
You can explicitly assign a temporary tablespace or tablespace group to a user in the CREATE USER statement. However, if you do not do so, and if no default temporary tablespace has been specified for the database, then by default these users are assigned the SYSTEM tablespace as their temporary tablespace. It is not good practice to store temporary data in the SYSTEM tablespace, and it is cumbersome to assign every user a temporary tablespace individually. Therefore, Oracle recommends that you use the DEFAULT TEMPORARY TABLESPACE clause of CREATE DATABASE.
You don't have to believe me or the docs.
Try it yourself. That is the best way to learn. Post your results here for all to see.
That is what that 12c doc says and what ALL of the docs for the versions before say. See for yourself. Here is the doc link for Oracle 7.3 so you can see the CREATE DATABASE systax yourself
http://docs.oracle.com/cd/A57673_01/DOC/server/doc/SQL73/ch4a.htm#createdatabase
Without a temp tablespace Oracle is forced to use the SYSTEM tablespace for the temporary.
These are the STANDARD ways:
1. Create PDB with a temporary tablespace.
2. Use the DBCA with a custom template
3. Create your own PDB seed database without a temp tablespace and then clone your seed to create other PDBs without a temp tablespace
4. Use CREATE DATABASE to create a DB without a temp tablespace and then plug it in to your CDB root container.
Those are ALL standard methods. The last three result in PDBs withoug a temp tablespace.
#1 is what you should be using.
1. Create PDB with a temporary tablespace.
2. Shrink/resize the temp tablespace down to a minimum if you want
3. Assign the users to the CDB temp tablespace if you don't want them using the PDB temp
I would appreciate if you only answer to questions if you have tested it or have a precise answer to it!
I have done BOTH of those things. Your failure to recognize that is NOT my problem.
I have created a PDB without a temp tablespace using DBCA and a custom template.
I have also created a PDB without a temp tablespace by using the historical standard method of CREATE DATABASE without a temp tablespace and then plugging it into the CDB and a PDB.
It is YOUR responsibility to RTFM and YOUR responsibility to actually put your fingers on the keyboard and try things.
The forum is NOT a coding service so you have no right to expect someone to write code for you and no right to get upset if they don't.
dbca doesn't use any other commands than the one's I've already tried!
Your reality is different than Oracle's. Support your reality with some facts.
I just created a PDB (create pluggable database) and no wonder that one comes with a temp tablespace.
I don't see where you posted ANYTHING that shows:
1. exactly WHAT you did
2. exactly HOW you did it
3. exactly what results you got.
If you want help with the code or a process you are using you have to POST that code or process.
We can NOT see your computer screen to see what screens you see or what entries you make.
Complain about the messenger all you want.
But you will NOT be successful with 12c if you refuse to RTFM and refuse to try things yourself. Making unsubstantiated statements or trying to attack me may make you feel better but you won't learn anything from it.

10G: TEMPORARY TABLESPACES GROUP

제품 : ORACLE SERVER
작성날짜 : 2004-05-25
10G: TEMPORARY TABLESPACES GROUP
==================================
PURPOSE
이 문서에서는 10g New Feature 인 Temporary tablespace 의 group 에 대해 알아 보도록 한다.
Explanation
10g 에서는 temporary tablespaces 에 대해 group 을 지정하여 생성할 수 있고
consumer group 을 지정하여 resource manager 와 함께 적용하여 사용이 가능하다.
다음은 Temporary tablespace group 지정을 위한 기본적이 사항이다.
1. 하나의 temporary tablespace group 은 적어도 하나의 tablespace 가 존재해야 하고
maximum number tablespace 에 대한 limit 은 정해져 있지 않다.
2. Ttemporary tablespace 와 group name 을 동일하게 지정할 수 없다.
3. Temporary tablespace group 은
     1) 한 group 에서 다른 group 으로 move 가 가능하고
     2) Group 내에서 삭제 될 수 있으며
     3) 추가적으로 add 가 가능하다.
4. Temporary tablespace group 사용으로 인해
     1) Sort 결과를 유지하여 space 낭비를 막을 수 있고
     2) 동시에 여러개의 session connect 시에도 서로 다른 temporary tablespaces 를 사용함으로써
     temporary tablespaces 의 사용을 분산 시킬 수 있다.
     3) Parallel operation 시에도 multiple temporary tablespaces 사용이 가능하다.
Example
1. GROUP1 을 지정하고 GROUP1 에 속하는 temporary tablespace LMTEMP 1 를 생성한다.
이 때 GROUP 1 을 따로 생성할 필요 없고 temporary tablespace 생성시에 지정하도록 한다.
SQL> create temporary tablespace LMTEMP 1
tempfile 'D:\ORACLE10\ORCL\temp1_01.dbf' size 50M
tablespace group GROUP1;
SQL> select * from dba_tablespace_groups;
GROUP_NAME TABLESPACE_NAME
GROUP1 LMTEMP1
2. LMTEMP2 를 GROUP1 에 새로 추가한다.
SQL> create temporary tablespace lmtemp2
tempfile 'D:\ORACLE10\ORCL\temp1_02.dbf' size 2M
tablespace group group1;
Tablespace created.
SQL> select * from dba_tablespace_groups;
GROUP_NAME TABLESPACE_NAME
GROUP1 LMTEMP1
GROUP1 LMTEMP2
3. 기존에 존재하는 LMTEMP1 를 GROUP2 로 move 한다.
SQL> alter tablespace LMTEMP1 tablespace group GROUP2 ;
Tablespace altered.
SQL> select * from dba_tablespace_groups;
GROUP_NAME TABLESPACE_NAME
GROUP2 LMTEMP1
GROUP1 LMTEMP2
4. LMTEMP1 이 속해 있던 GROUP2 에서 LMTEMP1 를 제외 시키고 다시 포함시킬 수 있다.
SQL> alter tablespace LMTEMP1 tablespace group '';
Tablespace altered.
SQL> select * from dba_tablespace_groups;
GROUP_NAME TABLESPACE_NAME
GROUP1 LMTEMP2
SQL> select tablespace_name from dba_tablespaces where contents='TEMPORARY';
TABLESPACE_NAME
TEMP
LMTEMP1
LMTEMP2
SQL> alter tablespace LMTEMP1 tablespace group GROUP1;
Tablespace altered.
5. Temporary tablespace 와 group name 을 동일하게 지정할 경우 ORA-10918 에러가 발생한다.
즉, temporary tablespace 와 group name 을 동일하게 지정이 불가능하다.
SQL> create temporary tablespace lmtemp5
tempfile 'D:\ORACLE10\ORCL\temp1_05.dbf' size 50M
tablespace group lmtemp5;
create temporary tablespace lmtemp5
ERROR at line 1:
ORA-10918: TABLESPACE GROUP name cannot be the same as tablespace name
6. 존재하던 모든 temporary tablespaces 를 drop 하게 되면 group 은 자동으로 remove 된다.
SQL> create temporary tablespace LMTEMP3
tempfile 'D:\ORACLE10\ORCL\temp1_03.dbf' size 2M
tablespace group GROUP2;
Tablespace created.
SQL> create temporary tablespace LMTEMP4
tempfile 'D:\ORACLE10\ORCL\temp1_04.dbf' size 2M
tablespace group GROUP2;
Tablespace created.
SQL> select * from dba_tablespace_groups;
GROUP_NAME TABLESPACE_NAME
GROUP1 LMTEMP1
GROUP1 LMTEMP2
GROUP2 LMTEMP3
GROUP2 LMTEMP4
SQL> drop tablespace lmtemp3 including contents and datafiles;
Tablespace dropped.
SQL> drop tablespace lmtemp4 including contents and datafiles;
Tablespace dropped.
SQL> select * from dba_tablespace_groups;
GROUP_NAME TABLESPACE_NAME
GROUP1 LMTEMP1
GROUP1 LMTEMP2
7. Group 에 user 사용이 가능하도록 지정할 수 있다.
SQL> alter user scott temporary tablespace GROUP1;
User altered.
8. Temporary tablespace group 을 database level 의 default temporary tablespace 로도 지정할 수 있다.
SQL> alter database <db_name> default temporary tablespace GROUP1;
Database altered.
만약, temporary tablespaces 가 default database temporary tablespace group 에 속해 있는경우
drop 시 ORA-10921 에러가 발생하게 된다. 즉, default temporary tablespace group 에 속해 있는 경우
drop 할 수 없다.
SQL> drop tablespace LMTEMP2 including contents and datafiles;
drop tablespace lmtemp2 including contents and datafiles
ERROR at line 1:
ORA-10921: Cannot drop tablespace belonging to default temporary tablespace
group
Reference Documents
<NOTE. 245645.1>

Hi,
Take a look in
1 - DBA_TEMP_FILES :http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96536/ch2398.htm
2 - V$TEMPFILE: http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96536/ch3225.htm
Cheers,
Marcello M.

Chmod 640 (Datafile,UNDO,TEMP Tablespace, Controlfile, Redo Log Files, Arch

If i change the permssion of these file to 640, will this break any thing?
what are the suggested permission of Oracle files and directories?

here i am doing to secure my DBs Just doing research that it dont break any thing
These are the permission i am going to change in my DBs , any suggestion?
chmod 750 /u02/oradata/sid_name
Chmod 640 (Datafile,UNDO,TEMP Tablespace, Controlfile, Redo Log Files, Archivelogs)
chmod 644 (alert Logs, init.ora files, config.ora files)
Chmod 640 $ORACLE_HOME/rdbms/admin/utlpwdmg.sql
Verify umask = 022 - type "umask" - should return 022; if not, modify in .profile
Verify all files are readable--run the following:
select file_name, status from dba_data_files where status != 'AVAILABLE'--should return 0 rows
SUN - ls -al /var/opt/oracle/oratab = should be owner=oracle group=dba
IF NOT, OPEN SR TO UNIX TEAM TO CHANGE
Verify oraInst.loc - look at /u01/app/oracle/security/*.info - setting A271-
/var/opt/oracle/oraInst.loc - owned by oracle:dba
*IF NOT, OPEN SR TO UNIX TEAM TO CHANGE
Verify ownership of $ORACLE_HOME/network/admin/listener.ora,$ORACLE_HOME/network/admin/tnsnames.ora
= oracle:dba
*IF NOT, OPEN SR TO UNIX TEAM TO CHANGE
Verification:
1. run gsd331 scan and verify fixed--
execute /u01/app/oracle/security/orashc -m -a *output will go to [email protected]
BACKOUT:
Change permission back to 755

ORA-30928: "Connect by filtering phase runs out of temp tablespace"

i have created a query that is sued to display a data in a label. This particular query will then be stored into a program that we use. The query runs just fine until this morning when it returns the error ORA-30928: "Connect by filtering phase runs out of temp tablespace". I have Googled and found out that I can do any of the following:
Include a NO FILTERING hint - but did not work properly
Increase the temp tablespace - not applicable to me since this runs in a production server that I don't have any access to.
Are there other ways to fix this? By the way, below is the query that I use.
SELECT * FROM(
SELECT
gn.wipdatavalue
, gn.containername
, gn.l
, gn.q
, gn.d
, gn.l2
, gn.q2
, gn.d2
, gn.l3
, gn.q3
, gn.d3
, gn.old
, gn.qtyperbox
, gn.productname
, gn.slot
, gn.dt
, gn.ws_green
, gn.ws_pnr
, gn.ws_pcn
, intn.mkt_number dsn
, gn.low_number
, gn.high_number
, gn.msl
, gn.baketime
, gn.exptime
, NVL(gn.q, 0) + NVL(gn.q2, 0) + NVL(gn.q3, 0) AS qtybox
, row_number () over (partition by slot order by low_number) as n
FROM
SELECT
tr.*
, TO_NUMBER(SUBSTR(wipdatavalue, 1, INSTR (wipdatavalue || '-', '-') - 1)) AS low_number
, TO_NUMBER(SUBSTR(wipdatavalue, 1 + INSTR ( wipdatavalue, '-'))) AS high_number
, pm.msllevel MSL
, pm.baketime BAKETIME
, pm.expstime EXPTIME
FROM trprinting tr
JOIN CONTAINER c ON tr.containername = c.containername
JOIN a_lotattributes ala ON c.containerid = ala.containerid
JOIN product p ON c.productid = p.productid
LEFT JOIN otherdb.pkg_main pm ON trim(p.brandname) = trim(pm.pcode)
WHERE (c.containername = :lot OR tr.SLOT= :lot)
)gn
LEFT JOIN otherdb.intnr intn ON TRIM(gn.productname) = TRIM(intn.part_number)
connect by level <= HIGH_NUMBER + 1 - LOW_NUMBER and LOW_NUMBER = prior LOW_NUMBER and prior SYS_GUID() is not null
ORDER BY low_number,n
WHERE n LIKE :n AND wipdatavalue LIKE :wip AND ROWNUM <= 300 AND wipdatavalue NOT LIKE 0
I am using Oracle 11g too.
Thanks for the help everyone.

Hi,
The documentation implies that the START WITH and CONNECT BY clauses should come before the GROUP BY clause. I've never known it to make a difference before, but you might try putting the GROUP BY clause last.
If you're GROUPing by LEVEL, what's the point of SELECTing MAX (LEVEL)? MAX (LEVEL) will always be the same as LEVEL.
What are you trying to do?
Post some sample data (CREATE TABLE and INSERT statements) and the results you want from that data, and somebody will help you get them.

Temp Tablespace Group or Not

Similar Messages

Maybe you are looking for