Tablespace allocation TEMP

While running a big query I sometimes get this error :ORA01652 unable to extend temp segment by 64 in tablespace TEMP
Looking at tablespace indicates that it is full, does anyone know how discoverer is handling this tablespace?
Thx.

Actually, Discoverer doesn't handle the TEMP tablespace at all. This is a DBA issue. Make sure that your DBA knows that they need to extend the max size of the TEMP tablespace. What is happening is it's trying to autoextend, but is running out of room. Hope this helps.

Similar Messages

How to change "tablespace allocation" Metric chng from 7 days to 1 day?

Hi
I got to change metric collection time from 7 days (i.e once in every week) to every day. I have not find any tab to modify, please let me know how can I modify.
Here are the details.
Metric Name: Tablespace Allocation None
Sub tabs : Tablespace Allocated Space (MB) Not Set
Tablespace Used Space (MB) Not Set
Thanks,
RK

Ah, you can't actually change it, at least not through the front end. From the Oracle® Enterprise Manager Oracle Database and Database-Related Metric Reference Manual
10g Release 2 (10.2)
Part Number B25986-01:
This metric calculates the space allocated for each tablespace. It is not intended to generate alerts. Rather it should be used in conjunction with the Allocated Space Used (MB) metric to produce an historical view of the amount of space being used and unused by each tablespace.
For all target versions, the collection frequency for this metric is every 7 hours.
The metric is only designed for historical information, looks a typo on the 7 hours, mine is also set to 7 days.

Tablespace allocation type system how oracle determines the extent size

HI
It may be silly question but the I have to ask and get some knowdge
Suppose tablespace allocation_type is system then how oracle determins the inital extent and max extent size?

Was this tablespace converted to locally managed from an existing tablespace? If so, the existing extents still exist after the conversion. Also depending on the Oracle version and maybe platform the pct_increase parameter is still honored after the conversion which can lead to odd sizes. The current value of this parameter may not be the value that was in effect when extents were allocated.
Also Oracle enhanced the logic to not leave odd sized extents unused so that if by rights the system should take a 64K extent but there is a 56K extent available (perhaps at the end of a file) it can be used to fill the extent request.
HTH -- Mark D Powell --

Reducing USERS tablespace allocated size.

Is there a way to reduce the size of the USERS database allocation. It is at 4.2 GBs and I have removed schemas and tables so that it is only using 14% of that space.
I have a database that I need to import that is using a couple of tablespaces that I need to set up.
I have tried compacting the database.
Any help would be greatly appreciated.
Mickey

Is there a way to reduce the size of the USERS database allocationYes you can reduce size of every tablespace file, for example:
ALTER DATABASE DATAFILE 'C:\ORACLE\ORADATA\XE\USERS01.DBF' RESIZE 1024M;
will resize tablespace on 1GB.
Note that you must set correct path!
Cheers!

Tablespace allocated size in Oracle SQL developer

Hello,
Currently in my oracle 11g database, there are two datafiles under the users tablespace. Today during one application installation, I ran into this error msg:
ORA-01654: unable to extend index BSANITY.SI_CUID_I7 by 8 in tablespace USERSSo i checked the tablespace status in SQL developer and saw that the USERS tablespace is at 99% used. Datafile #1 is full at max size 32G and #2 is full at max size 4G. So I decided to change dbf #2 maxsize to 32G, I used the following command:
alter database datafile '<file path here>' autoextend on maxsize 32000M;I checked the dba_data_files view and verified the maxbytes change.
However, when I check the tablespace status in SQL developer, it is still showing USERS tablespace as 99% used. I'm wondering is there anything else I need to do after altering the datafile maxsize so that the change gets reflected in SQL developer?
Thank you in advance!
Edited by: 939040 on Jun 11, 2012 12:05 PM

939040 wrote:
Hi,
Thanks for your reply! i'm actually doing troubleshooting for a user, so I have to ask him to try the installation again to see if the problem persists. However, you said the DDL did not change the size of the file, what could be the reason? is there anything i can do to make sure it changes the size?When all else fails Read The Fine Manual
http://docs.oracle.com/cd/B28359_01/server.111/b28310/dfiles003.htm#ADMIN11425

Tablespace allocation

Hi
Please recommend for the following:
1. I have a 30gb data to be transferred to production DB, its a cluster database.
can i create a tablespace with two 15gb datafile having a 30gb tablespace or
three 10gb datafile having 30 gb tablespace.
For a big size data what kind of tablespace creation will you recomend.
TIA
Ravi

I believe in the source DB, it will not be such a large datafile. It is adviseable to keep your datafiles as manageable as possible. Your OS also may not support such size of datafile and if it does, it may not be easy to mange it.
15GB or 10GB single Datafile for me is too big. If the idea if to keep the number of datafiles down for that tablespace, I would suggest a minimum of 6 datafiles. That will give you 5GB each.
BTW - How many datafiles does it have from the source DB?

Temp CLOB tablespace not released - Returning CLOB from SP

I'm trying to call a stored procedure from a .NET application that returns a CLOB as an OUT parameter. The problem that we are experiencing the tablespace allocation from the temporary clob created in the stored procedure is not released after the stored procedure is finished executing. Here is an extract of the code we use to create the CLOB
DBMS_LOB.createTemporary(TempCLOB, FALSE, DBMS_LOB.CALL);
XMLDOM.writeToClob(xmlDocumentNode, TempCLOB); --write the xml results to the clob
Then the TempCLOB is returned to .NET as an OUT parameter. After the procedure is executed the lob locators in v$temporary_lobs rise by one for each execution of the stored procedure. We've tried using DBMS_LOB.freetemporary(TempCLOB) but the CLOB variable is returned to .NET as null.
Anyone have any ideas of how to properly dispose of the temp CLOB?

> Anyone have any ideas of how to properly dispose of the temp CLOB?
Using DBMS_LOB.FreeTemporary() after the temp CLOB has been used..
Have the .NET client call this PL/SQL API call when it is done with the CLOB. Remember that what is passed to the .NET client is a pointer to the temp CLOB - not the temp CLOB itself. Therefore if you release the CLOB and then pass the pointer to the client, that pointer refers to nothing.
The client uses this pointer to access bits and pieces of the CLOB (in temp space on the Oracle Server). When the client is done, it is only good manners on the client's part to inform the server that it is done with that server resource and that it can be released.
Ditto with ref cursors.

How to create temp files in temp tablespace

Dear all,
Due to outage of our SAN, we our out of production for the
last 3 days. By the grace of Almighty we have restored production by
database recovery from our standby backup. Since temp tablespace and
temp data files do not taken as backup for standby, now after recovery
we are getting abap dumps asking for temp_1 and temp_2 datafiles.
Please guide us how to create temp files. v$tablespace is showing tablespace PSAPTEMP but datafile are not there
Abap dumps are giving these errors as mentioned below
====================================================
The exception must either be prevented, caught within the procedure
"DATA_SELECTION"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-01157: cannot identify/lock data file 256 -
see DBWR trace file#ORA-01110: data file 256:
'/oracle/SD1/sapdata4/temp_2/temp.data2'"
Internal call code.........: "[RSQL/FTCH/MARA ]"
===================================================
another one asking for
'/oracle/SD1/sapdata3/temp_1/temp.data1'"
Best Regards
Waqas

if you want to add a new tempfile to your TEMP Tablespace,you can do like that.
ALTER TABLESPACE <name of TEMP Tablespace> ADD TEMPFILE <pfad to the file_and_file name> SIZE <size>;
You can use also the options REUSE autoextend off or on .
e.g:
alter tablespace PSAPTEMP add tempfile '/oracle/SD1/sapdata4/temp_2/temp.data2' SIZE 1000K REUSE;
The directory temp_2 should exist.
Or you can use the BR*Tools to create a new datafile. Enter brtools and follow the instructions or menu.
More to TEMP Tablespaces see please following SAP notes:
659946 - FAQ: Temporary tablespaces
600513 - ORA-25153 after recovery due to missing tempfiles
and the Oracle Note:
160426.1: TEMPORARY Tablespaces : Tempfiles or Datafiles ?
I hope it helps.

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.

To find allocation type in tablespaces

Hi,
I need to find whether my tablespaces allocation type is automatic. Could anyone please assist me with a query?

Hello,
You can find all information about your tablespaces with
select * from dba_tablespaces;Regards,
Sylvie

ORA-1652: unable to extend temp segment by 32 in tablespace TEMP.

Hello everybody,
i have a problem with our temp tablespace:
we are running Oracle 9.2.0.5 with 1000 concurrent sessions.
I have now the the situation that in the normal buisiness the temp tablespace is full, that means no free space in the tablespace.
How I can find out, which 'user' (query) uses this space.
Thanks for yout advice
Thomas Kindermann
DBA,Cologne

but look at this:
Tablespace Name : Temp
KBytes : 3,942,400
Used : 3,942,360
Free : 40
Used % 100.0
Largest: 40
SQL> select * from v$sort_usage;
no rows selected
SQL>

Temp tablespace drop 관련 질문임다!

temp tablespace가 거의 100%사용이어서, db shutdown하고 다시 살렸는데도
줄지 않아서 (사실 이것도 왜 안주는지 궁금하거등요~!)
우선 old_temp tablespace를 new_temp tablespace를 만들었습니다.
즉,,,제가 한작업들을 개략 적어보면요
1) create temporary tablespace new_temp tempfile~~~~;
2) drop tablespace old_temp;
3) alter database default temporary tablespace new_temp;
하고 나서 모든 유저에 지정되어있는 temporary tablespace를 new_temp로 지정
해줘야 하쟎아요
즉, alter user scott temporary tablespace new_temp; 이렇게요...
근데 이걸 안해줬는데도 에러없이 scott유저는 소트를 수행하드라구요...
이거...정상인건가요????
***추가질문~!
그리고 템프싸이즈가 줄지않고 계속늘어날때의 원인과 체크포인트좀 부탁드립니다.

8i에서는 tempfile이란 개념은 있었으나 default temporary tablespace라는
개념은 없었습니다. 그래서 유저에게 직접 default tablespace를 지정해주어야
했었습니다.
하지만.. 9i부터는 alter database default temporary tablespace new_temp;
명령을 하기만 하면 모든 유저의 default temporary tablespace가 default로
지정되어 있지 않으면 new_temp로 됩니다.
물론 이 경우에도 수동으로 temp를 지정할 수 있으니 실제로 유저가
temp공간을 어디에 사용하는지는..
select username, temporary_tablespace from dba_users; 를 통해서
확인해야 합니다.
scott유저는 default temporary tablespace로 지정되어서 그 쪽 temp를
사용하게 되니, 에러가 나지 않겠죠.
default temporary tablespace가 무엇으로 지정되어 있는지는,
select * from database_properties; 또는 select * from sys.props$; 로 조회하면
temporary tablespace라는 이름으로 어떤 값이 들어가 있는지 보입니다.
그리고 temp는 DB를 내렸다가 올리면 smon프로세스가 clear시켜줍니다.
temp는 아시다 싶이 당연히 sort를 해서 발생하는 것이구요. 그렇다면..
temp가 계속해서 full이 난다면.. temp를 사용하는 세션을 확인하고
temp를 사용하는 세션의 쿼리를 뽑아낸다면 쉽게 해결이 되겠죠.
아래는 제가 경험해서 처리한 것입니다.
저는 temporary tablespace가 full 났는데 도대체 쿼리를 못잡는 것이었습니다.
그래서 어떻게 했을까요? Secure CRT에 세션로그를 걸어두고 모니터링을 했죠.
vi stat.sh
interval=30 # Sleep interval in seconds
reps=1000000 # n times
j=1 # Loop variable
while [ $j -le ${reps} ]
do
echo " ----cycle ${j} / ${reps} --------"
sqlplus -s system/패스워드<<EOF
@sw.sql ${j}
exit
EOF
cat sess_${j}.dat >> sw.dat
rm sess_${j}.dat
sleep ${interval}
j=`expr ${j} + 1`
done
exit 0
vi sw.sql
set line 150
set concat "+"
col username format a10
col osuser format a10
col tablespace format a15
spool sess_&1.dat
SELECT b.tablespace,
b.segfile#,
b.segblk#,
b.blocks,
a.sid,
a.serial#,
c.spid,
a.username,
a.osuser,
a.status,
a.sql_hash_value
FROM v$session a,
v$sort_usage b,
v$process c
WHERE a.saddr = b.session_addr and a.paddr=c.addr
ORDER BY b.tablespace, b.segfile#, b.segblk#, b.blocks;
spool off
stats.sh 를 수행하고 PC킨 상태로 그냥두고 다음날 왔더니 아래처럼 temp를
계속 쓰는 넘이 나온거죠..
딱걸렸습니다.ㅎㅎ
TEMP 93 2550817 13824 92 58284 3193 PVB oracle ACTIVE 1126923165
----cycle 1792 / 1000000 --------
TEMP 93 2550817 43008 92 58284 3193 PVB oracle ACTIVE 1126923165
----cycle 1793 / 1000000 --------
TEMP 93 2550817 72192 92 58284 3193 PVB oracle ACTIVE 1126923165
----cycle 1794 / 1000000 --------
TEMP 93 2550817 101376 92 58284 3193 PVB oracle ACTIVE 1126923165
----cycle 1795 / 1000000 --------
TEMP 93 2550817 131072 92 58284 3193 PVB oracle ACTIVE 1126923165
----cycle 1796 / 1000000 --------
TEMP 93 2416673 18944 123 5171 3197 PVB oracle ACTIVE 1126923165
TEMP 93 2550817 159744 92 58284 3193 PVB oracle ACTIVE 1126923165
----cycle 1797 / 1000000 --------
TEMP 93 2416673 48128 123 5171 3197 PVB oracle ACTIVE 1126923165
TEMP
sql_hash_value값이 1126923165 이니 아래 쿼리에다가 넣으면 full 쿼리가 나오죠..
결국엔 개발자가 모든 소스코드에서 변경을 했어야 했는데.. 그렇게 하지 않아서
일부 웹서버에서의 쿼리가 이상하게 where조건없이 수행되었고 그래서 temp가
full 났던 것이랍니다.
vi sidhashsql.sql
set pages 1000
col sql_text format a120
select sql_text from v$sqltext_with_newlines
where hash_value=&hash_value order by piece;
SQL> @sidhashsql
Enter value for hash_value: 1126923165
old 2: where hash_value=&hash_value order by piece
new 2: where hash_value=1126923165 order by piece
SQL_TEXT
boan~~~~!!
아래 너무 자세하게 나와있죠?
No. 18484
TEMPORARY TABLESPACE에서 TEMPFILE 과 DATAFILE의 차이점 (8.1.X ~ 9I)
============================================================
PURPOSE
이 문서에서는 Oracle 7.3부터 사용되어 오던 create tablespace ... temporary
형태와, 8i부터 사용되는 create temporary tablespace... 의 차이점을 정리해
본다.
tablespace의 temporay type과 permanent type에 대한 비교는 <Bulletin#: 11938>
를 참조하도록 하고 여기에서는 permanent에 대해서는 논외로 한다.
Explanation
temporary segment가 생성 가능한 tablespace의 type과 temporary tablesapce에서
datafile과 tempfile의 차이점을 설명한다.
1. temporary segment를 생성가능한 tablespace type 정리
temporary tablespace의 tempfile과 datafile을 비교하기 전에, tablespace의
type들을 확인해 보고, 이 중 temporary segment가 생성될 수 있는 tablespace
type을 version별로 정리해본다.
tablespace는 7.2까지는 permanent type으로 dictionary managed방식으로
space를 할당/해제하던 방식만이 존재했다. db user의 temporary tablespace로
임의의 tablespace를 지정가능하였고, 해당 db user의 sort operation은
지정된 tablespace에서 발생하며, 다른 tablespace와 특별히 구분되는 것은
없었다.
이후, 7.3에 temporary type이 추가되고, 8i에서 locally managed type과 일반
datafile이 아닌 tempfile이 소개되면서 8i를 기준으로 기본적으로 다음과 같이
4가지 형태의 tablespace 형태가 가능하다.
이중 (1) ~ (3)번까지는 일반 datafile형태이고, (4)번의 경우는 이 문서에서
자세히 살펴볼 tempfile이다.
(locally managed와 dictionary managed의 차이점 및 사용 방법은
<Bulletin #: 18261>과 <Bulletin #: 11860> 참조)
(1) permanent-dictionary managed
(2) permanent-locally managed
(3) temporary-dictionary managed
(4) tempfile-locally managed
[주의] 위의 종류에 temporary datafile에 locally managed 형태의 tablespace는
없는것에 주의한다.
그리고 만약 system tablespace가 locally managed로 이미 생성된 경우에는
이후 모든 tablespace는 locally managed로 생성이 가능하고, dictionary
managed 형태는 생성하면 ORA-12913 (Cannot create dictionary managed
tablespace) 오류가 발생하게 된다.
이러한 여러가지 type의 tablespace중 temporary segment를 생성할 수 있는
tablespace에 제약이 존재한다.
- 8i: 어떠한 형태의 tablespace라도 db user의 temporary tablespace로 지정
가능하다. 단, permanent-locally managed 형태의 tablespace에 sort가
발생하게 되면 ORA-3212 (Temporary Segment cannot be created in
locally-managed tablespace) 오류가 발생하게 된다.
SQL> alter user scott temporary tablespace PERM_LOCAL;
User altered.
connect scott/tiger
SQL> select * from dept order by 1;
ORA-03212: Temporary Segment cannot be created in locally-managed
tablespace
- 9i: db user의 default temporary tablespace 지정 자체가 다음 두 가지
type만이 가능한다.
-temporary-dictionary managed
-tempile-locally managed
만약 permanent type의 tablespace를 db user의 tempoary tablespace로
지정하면, ORA-12911 (permanent tablespace cannot be temporary tablespace)
오류가 발생한다.
2. tempfile과 datafile의 비교
아래에서 tablespace지정시 tempfile과 datafile형태를 비교하게 되는데,
단, datafile형태의 경우 permanent type에 대해서는 언급하지 않는다.
(1) tempile의 특징
Oracle7.3에서 tablespace에 생성시 temporary option을 이용하여 생성되는
tablespace를 구성하는 화일은 datafile이다. 단지 이것이 기존의 permanent
type과 구별되는것은 이 tablespace에 생성되는 segment들이 매번 sort
operation마다 별도로 생성되는 대신, 하나의 segment로 만들어지면서
다른 session에서의 sort operation이 같은 segment를 공유하는 것이다.
(자세한 것은 <Bulletin#: 11938> 참조)
Oracle8.1부터 추가된 tempfile형태의 중요한 특징은 tempfile에 발생하는
변경사항은 redo log file에 기록되지 않는다는 것이다. tempfile에
checkpoint정보도 기록하지 않고 이에 따라 datafile recovery시에도
tempfile에 대해서는 recovery가 필요없게 된다.
이와 같은 이유로 standby database에서 read-only mode로 open하고
조회시 sort가 발생하여 tempfile이 변경되는것은 문제가 되지 않아
사용이 가능하다.
그리고 이미 앞에서 설명한 것과 같이 tempfile은 항상 locally managed
type으로만 생성이 되며, datafile형태의 temporary tablespace는 다음과
같이 locally managed type으로 생성 자체가 불가능하다.
SQL> create tablespace temp_datafile_local
2 DATAFILE '/ora/oradata/V920/temp_data.dbf' size 100M
3 TEMPORARY
4 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K;
ORA-25144: invalid option for CREATE TABLESPACE with TEMPORARY contents
(2) temporary tablespace 생성 방법 비교
- tempfile형태의 경우
tempfile로 temporary tablespace를 생성하는 경우는 다음과 같이
생성하여야 하며, 반드시 locally managed 형태로만 생성 가능하다.
SQL> create TEMPORARY tablespace temp_tempfile_local
2 TEMPFILE '/ora/V920/temp_temp.dbf' size 100M
3 EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K;
아래 명령어에서 3번 line을 제거하고 생성하여도 default로 locally
managed로 생성이 되며, dictionary managed 형태로 생성하고자
3번 line대신 storage option을 추가하면
ORA-2180 (invalid option for CREATE TABLESPACE) 오류가 발생한다.
- datafile형태의 경우
다음과 같은 형태로 생성하게 되면, dictionary managed type의
temporary datafile형태로 tablespace가 만들어진다. 단, 9i의 경우
이미 앞에서 언급한대로 system tablespace가 locally managed인 경우에는
이와 같은 dictionary managed tablespace 생성은 ORA-12913이 발생하면서
불가능하게 된다.
SQL> create tablespace temp_datafile_dict
2 datafile '/ora/oradata/V920/temp_data.dbf' size 100M
3 TEMPORARY;
(3) dictionary view 의 차이
먼저 dba_tablespaces를 통해
SQL> select tablespace_name, contents, extent_management,
allocation_type from dba_tablespaces;
TABLESPACE_NAME CONTENTS EXTENT_MAN ALLOCATIO
TEMP_TEMPFILE_LOCAL TEMPORARY LOCAL UNIFORM
TEMP_DATAFILE_DICT TEMPORARY DICTIONARY
- tempfile의 경우
SQL> select STATUS, ENABLED, NAME from v$tempfile;
STATUS ENABLED NAME
ONLINE READ WRITE /ora/V920/temp_temp.dbf
SQL> select FILE_NAME, TABLESPACE_NAME from dba_temp_files;
FILE_NAME TABLESPACE_NAME
/ora/V920/temp_temp.dbf TEMP_TEMPFILE_LOCAL
- datafile 형태의 경우
다음과 같이 v$datafile과 dba_data_files를 통해 조회한다.
SQL> select STATUS, ENABLED, NAME from v$datafile;
STATUS ENABLED NAME
ONLINE READ WRITE /ora/oradata/V920/temp_data.dbf
SQL> select FILE_NAME, TABLESPACE_NAME from dba_data_files;
FILE_NAME TABLESPACE_NAME
/ora/oradata/V920/temp_data.dbf TEMP_DATAFILE_DICT
(4) tempfile의 삭제에 대해서
datafile의 경우 tablespace를 삭제하지 않고 datafile만 삭제하는 방법은
존재하지 않는다. 물론 alter database datafile 'filename' offline drop;
과 같은 command가 있지만 이것도 datafile을 데이타베이스에서 지워주는
것이 아니며 이렇게 offline drop된 datafile을 포함하는 tablespace는
recovery가 불가능한 경우라면 tablespace자체를 삭제해야 한다.
그런데 tempfile의 경우는 temporary tablespace는 그대로 유지한 채,
tempfile만 삭제하는 것이 가능하다.
SQL> alter database tempfile '/oradata/V817/temp_temp01.dbf'
2 drop;
8i의 경우라면 이와 같은 명령어 후 실제 directory로 이동하여 직접
tmep_temp01.dbf를 삭제하여야 한다.
9i에서는 drop뒤에 including datafiles 라는 option을 추가하여 tempfile의
drop시 바로 os상에서도 삭제되도록 할 수 있다.
SQL> alter database tempfile '/oradata/V817/temp_temp01.dbf'
2 drop including contents;
만약 이러한 방법으로, tempfile을 해당 temporary tablespace에서 모두
삭제한 경우, 실제 해당 tablespace에 disk sort가 필요하게 되면,
그때는 ORA-25153 (Temporary Tablespace is Empty) 오류가 발생하게 된다.
이때는 다음과 같이 임의의 tempfile을 다시 추가할 수 있다.
SQL> alter tablespace TEMP_TEMPFILE_LOCAL
2 add tempfile '/oradata/V817/temp_temp02.dbf';
Reference Documents
<Note:160426.1> TEMPORARY Tablespaces : Tempfiles or Datafiles ?
글 수정:
민천사 (민연홍)
글 수정:
민천사 (민연홍)
가장 중요한 v$session의 sql_hash_value 컬럼이 안들어가서
수정하였습니다. 죄송합니다.

Reasons to use separate temp tablespace for user tablespace

Hi,
I know that guideline says is not use system tablespace for user tables. But need i create for user tablespace separate TEMP teblespace or i can use same TEMP tablespace for all tablespaces?

Hi,
>>But need i create for user tablespace separate TEMP tablespace or i can use same TEMP tablespace for all tablespaces?
You can use one temp tablespace for a database , Temp tablespace usage are for sorting the data.
for more detail you can go with :Creating Tablespaces
HTH

Issue in deleting temp file.

Hi experts ,
i am using Oracle 10g and my database is in archive log mode my default temporary tablespace is temp and there are 3 tempfiles in it by name temp01.dbf,temp02.dbf,temp03.dbf i am trying to drop temp03.dbf through sql prompt
sql > alter tablespace temp drop tempfile '/path/temp03.dbf' ;
and got a error ora-02142 missing or invalid alter tablespace option.
then i made this tempfile offline and again tried to drop this tempfile with the same command and again i got the same error please tell me why i am getting this error and how to drop that temp file .
thanks .

Try it!
ALTER DATABASE TEMPFILE '<YOUR TEMPFILE NAME>' DROP INCLUDING DATAFILES;
Cheers,
Jonathan Ferreira
http://oracle4dbas.blogspot.com

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

Tablespace allocation TEMP

Similar Messages

Maybe you are looking for