Sizing of the OLAP temp tablespace!!

We are using 10gR2 OLAP along with Disco Plus OLAP to build a prototype. The metadata is built with AWM 10.2.0.1.0A.
Our test data is about 40M records, 1.7G in a flat file. After loaded to a fact table via Sql*loader, it takes about 2G for the tablespace, along with 7 dim tables. Only one cube and one measure are used. A compressed composite with 6 dims in it is associated with the cube.
However, when run the AWM maintenance steps to get a full cube aggregation. The temp tablespace for the AW shot for 30G and then generated an out of disk space error. The AW tablespace remains untouched. The maintenace cannot be finished.
Interesting to note, the data was solved in the Xpress already. When do a eif exp/imp, the result tablespace is about 5G while the eif file takes 1.3G.
Also, before doing this round data, we have sucessfully created and maintained a AW with very small set of data. The data is displayed in Disco Plus correctly.
The disk space for the temp tablespace seems surprisingly demanding. We need to get an idea how much space it really needs. Is there anybody that has some contributable experience on this issue? Please reply this post. Not sure if Oracle has formal publishing on the temp tablespace sizing issue. Believe they should have one.
Thanks,

Chris,
No upgrading was done here. The metadata and objects were defined using AWM model view manually, but matching to the definition on the Xpress side for the same object, like dim order etc. The fact data then dumped to a flat file from Xpress, transferred to the olap db server and loaded to a star schema with sql*loader. AWM mapping and maintenance features were used to build the cube.
I am saying the data was solved means the summary level data was included in the dump. So we know the size of the solved cube. My reasoning is that there should be no place for the size increase to out of control because too much new summary level data was added.
Another fact I should mention last time is all the data are in one time period. 40M is the number of tuples.
Thanks for the help.
Haiyong

Similar Messages

How to identify temp tablespace user in the past

hi,
can anyone guide me on how to identify temp tablespace users and corresponding temp space amount they used in the past?
we have this situation where in we need to identify the top temp tablespace user last jan 1 around a specific time.
is this possible? do these get stored in one of the tables in the dictionary? any sql statement?
thanks.

900666 wrote:
hi ckpt,
thats unfortunate..=(
anyways, any sql that can be used to capture current sessions with their used mb in temp tablespace? for future monitoring.
thansk.Here is example
SQL> SET LINESIZE 145
SQL> SET PAGESIZE 9999
SQL> SET VERIFY   off
SQL>
SQL> COLUMN tablespace_name       FORMAT a15               HEAD 'Tablespace Name'
SQL> COLUMN username              FORMAT a15               HEAD 'Username'
SQL> COLUMN sid                   FORMAT 99999             HEAD 'SID'
SQL> COLUMN serial_id             FORMAT 99999999          HEAD 'Serial#'
SQL> COLUMN contents              FORMAT a9                HEAD 'Contents'
SQL> COLUMN extents               FORMAT 999,999           HEAD 'Extents'
SQL> COLUMN blocks                FORMAT 999,999           HEAD 'Blocks'
SQL> COLUMN bytes                 FORMAT 999,999,999       HEAD 'Bytes'
SQL> COLUMN segtype               FORMAT a12               HEAD 'Segment Type'
SQL>
SQL> BREAK ON tablespace_name ON report
COMPUTE SUM OF extents   ON report
SQL> SQL> COMPUTE SUM OF blocks    ON report
SQL> COMPUTE SUM OF bytes     ON report
SQL>
SQL>
SQL> SELECT
2      b.tablespace          tablespace_name
3    , a.username            username
4    , a.sid                 sid
5    , a.serial#             serial_id
6    , b.contents            contents
7    , b.segtype             segtype
8    , b.extents             extents
, b.blocks              blocks
9   10    , (b.blocks * c.value) bytes
FROM
11   12      v$session     a
13    , v$sort_usage b
14    , (select value from v$parameter
15       where name = 'db_block_size') c
16 WHERE
17        a.saddr = b.session_addr
18 /
Tablespace Name Username           SID   Serial# Contents Segment Type Extents   Blocks        Bytes
TEMP          SYSTEM            1333      4725 TEMPORARY LOB_DATA            1      128    1,048,576
                SYSTEM            1562       444 TEMPORARY SORT               89   11,392   93,323,264
                SYSADM            1602        80 TEMPORARY LOB_DATA            1      128    1,048,576
                SYSTEM            1613     18693 TEMPORARY SORT               89   11,392   93,323,264
sum                                                                          180   23,040 188,743,680
SQL>

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

Creating a Global Temporary Table on non-default TEMP tablespace.

Hello ,
I am using Oracle 11g.
I have a procedure which create global temporary tables for its functionality. As the data which is going in the global temporary table , mean the data which is going in the default TEMP tablesapce is too huge ..... billions of rows..
So what i want to do is , I want to create the global temporary table in another TEMP2 tablespace ( which is not the default one) so the load of billions of rows of data will be shifted to TEMP2. The default TEMP tablespace will not be affected and it can be used for other transactions.
Is this possible. Can i shift the global temporary table from TEMP( Default temp tablespace) to TEMP2 ( the non-default temp tablespace) ????
Please guide me with proper solutions and examples ....
Thanks in advance ..

DBA4 wrote:
Hello ,
I am using Oracle 11g.
I have a procedure which create global temporary tables for its functionality. As the data which is going in the global temporary table , mean the data which is going in the default TEMP tablesapce is too huge ..... billions of rows..
So what i want to do is , I want to create the global temporary table in another TEMP2 tablespace ( which is not the default one) so the load of billions of rows of data will be shifted to TEMP2. The default TEMP tablespace will not be affected and it can be used for other transactions.
Is this possible. Can i shift the global temporary table from TEMP( Default temp tablespace) to TEMP2 ( the non-default temp tablespace) ????
Global temporary tables are instantiated in the temporary tablespace of the schema that inserts the data - not into "the default" temporary tablespace.
Assume Schema1 creates a GTT and grants all on that table to schema2
Assume schema1 also creates a procedure (authid owner, the default) to insert data into the GTT and grants execute on the procedure to schema2
If schema2 executes: insert into schema1.gtt, the data will appear in the temporary tablespace of schema2
If schema2 executes: execute schema1.procedure, the data will appear in the temporary tablespace of schema1
So if you want to protect the "normal" temporary tablespace, you could just create a special temporary tablespace for the owner of the procedure.
Regards
Jonathan Lewis

Check and identify cause of previous temp tablespace usage

Hi
Our production ERP database is on solaris and on version 9.2.0.8.0. The application tier and database tier are on two separate nodes.
Recently we observed that the temporary tablespace is being consumed more on a particular day. While monitoring the database,we observed the free temp tablespace was less and hence added 10gb space to it. However within 5-6 hours this space was utilised and certain requests/jobs failed due to no space in temp. This happened on 04th December 2012. Though the situation returned to normal post that,we need to find the cause of consumption of temporary tablespace in such large volumes. We are on 9i database and hence tried identifying the queries through statspack report as no views in particular exist for 9i.
We came across many queries which would help us identfy the current temp usage,but in 9i,we didnot find anything which would guide us on the historic temp tablespace usage. Can it be found via statspack? If yes,what exactly to check for in it? Request you to all please advice. Thanks.
Regards
Rdxdba

-- To get historic information for a spesific sid,serial
column temp_mb format 99999999
column sample_time format a25
prompt
prompt DBA_HIST_ACTIVE_SESS_HISTORY
prompt
select sample_time,session_id,session_serial#,sql_id,temp_space_allocated/1024/1024 temp_mb,
temp_space_allocated/1024/1024-lag(temp_space_allocated/1024/1024,1,0) over (order by sample_time) as temp_diff
from dba_hist_active_sess_history
--from v$active_session_history
where
session_id=&1
and session_serial#=&2
order by sample_time asc
prompt
prompt ACTIVE_SESS_HIST
prompt
select sample_time,session_id,session_serial#,sql_id,temp_space_allocated/1024/1024 temp_mb,
temp_space_allocated/1024/1024-lag(temp_space_allocated/1024/1024,1,0) over (order by sample_time) as temp_diff
--from dba_hist_active_sess_history
from v$active_session_history
where
session_id=&1
and session_serial#=&2
order by sample_time asc
=========================================================================
---- For global temp usage info
col sid_serial format a10
col username format a17
col osuser format a15
col spid format 99999
col module format a15
col program format a30
col mb_used format 999999.999
col mb_total format 999999.999
col tablespace format a15
col statements format 999
col hash_value format 99999999999
col sql_text format a50
col service_name format a15
prompt
prompt #####################################################################
prompt #######################LOCAL TEMP USAGE#############################
prompt #####################################################################
prompt
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;
prompt
prompt #####################################################################
prompt #######################LOCAL TEMP USERS#############################
prompt #####################################################################
prompt
SELECT S.sid || ',' || S.serial# sid_serial, S.username, S.osuser, P.spid,
--S.module,
--P.program,
s.service_name,
SUM (T.blocks) * TBS.block_size / 1024 / 1024 mb_used, T.tablespace,
COUNT(*) statements
FROM v$tempseg_usage T, v$session S, dba_tablespaces TBS, v$process P
WHERE T.session_addr = S.saddr
AND S.paddr = P.addr
AND T.tablespace = TBS.tablespace_name
GROUP BY S.sid, S.serial#, S.username, S.osuser, P.spid,
S.module,
P.program,
s.service_name,TBS.block_size, T.tablespace
ORDER BY mb_used;
--prompt
--prompt #####################################################################
--prompt #######################LOCAL ACTIVE SQLS ############################
--prompt #####################################################################
--prompt
-- SELECT sysdate "TIME_STAMP", vsu.username, vs.sid, vp.spid, vs.sql_id, vst.sql_text,vsu.segtype, vsu.tablespace,vs.service_name,
-- sum_blocks*dt.block_size/1024/1024 usage_mb
-- FROM
-- SELECT username, sqladdr, sqlhash, sql_id, tablespace, segtype,session_addr,
-- sum(blocks) sum_blocks
-- FROM v$tempseg_usage
--     group by username, sqladdr, sqlhash, sql_id, tablespace, segtype,session_addr
-- ) "VSU",
-- v$sqltext vst,
-- v$session vs,
-- v$process vp,
-- dba_tablespaces dt
-- WHERE vs.sql_id = vst.sql_id
-- AND vsu.session_addr = vs.saddr
-- AND vs.paddr = vp.addr
-- AND vst.piece = 0
-- AND vs.status='ACTIVE'
-- AND dt.tablespace_name = vsu.tablespace
-- order by usage_mb;
--prompt
--prompt #####################################################################
--prompt #######################LOCAL TEMP SQLS##############################
--prompt #####################################################################
--prompt
--SELECT S.sid || ',' || S.serial# sid_serial, S.username, Q.sql_id, Q.sql_text,
--T.blocks * TBS.block_size / 1024 / 1024 mb_used, T.tablespace
--FROM    v$tempseg_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 mb_used;
--

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.

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.

ORA-01652 in TEMP Tablespace

Hi,
We have the following errors:
RMAN> crosscheck archivelog all;
starting full resync of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of crosscheck command at 01/07/2009 14:26:10
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 01/07/2009 14:26:10
ORA-01652: unable to extend temp segment by in tablespace
RMAN>
We have tried to increase the size of the TEMP tablespace, but this operation keeps using up the entire temp tablespace. It's the temp tablespace in the target database that is filling up.
We cannot keep increasing the size of the TEMP ts to fill the disk.
We have also tried to create a new repository but this had the same outcome.
I reckon there is something in the database tables, as one of our backups used the target control file as its repository. Should I remove the entries from these tables in the target tablespace to make the repository think there is no re-synching to be done?
Regards,
Tim.

If you are sure that it is on the target DB what you can do is enable a trace for the event to see what triggers this error
it doesnt have to be on temporary table because there are temp segments on normal tables used for index creation type operations as well so you need to find the problem before assuming it is temp tablespace error
alter system set events '1652 trace name errorstack level 1';
to turn off
alter system set events '1652 trace name context off';
If you cant find anything from trace then you can send the trace output here maybe somebody can catch something.
Coskan Gundogar
http://coskan.wordpress.com
Edited by: coskan on Mar 30, 2009 4:28 PM

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

Is there any way to alter temp tablespace into normal tablespace

Even though It might be stupid question, i want to know the solution for that...
Is it possible to alter TEMP tablespace into Normal tablespace?
One more question, is it possible to create user with TEMP tablespace,
(I know the usage of temp tablespace also, and we cannot create user with temp tablespace.)
If some trick or any solution, share with me.
Thanks in advance.

1) Can you explain why you want such an unusual situation. By understanding your requirement, perhaps we can suggest alternatives
2) The requirements and restrictions are described in the CREATE USER command in the SQL Reference manual for whatever version you are using. (The stupid part of your question happens by not specifying any version range. <g>)
The requirement to use a TEMPORARY tablespace is documented and enforced in 9i. In 8i, we only required a tablespace to be named.
3) On 10gR2 you see the following response:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Hans>sqlplus system/oracle
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jun 18 06:33:31 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> create user test1 identified by test account unlock
2 default tablespace temp
3 temporary tablespace temp;
create user test1 identified by test account unlock
ERROR at line 1:
ORA-12910: cannot specify temporary tablespace as default tablespace
SQL> create user test2 identified by test account unlock
2 default tablespace users
3 temporary tablespace users;
create user test2 identified by test account unlock
ERROR at line 1:
ORA-10615: Invalid tablespace type for temporary tablespace
SQL> create user test3 identified by test account unlock
2 default tablespace users
3 temporary tablespace temp;
User created.
SQL Rem Just on case it's complaining about using the same temp tablespace
SQL> create temporary tablespace temp2 tempfile 'C:\ORACLE\ORADATA\XE\TEMP2.DBF'
size 10m;
Tablespace created.
SQL> create user test4 identified by test account unlock
2 default tablespace temp
3 temporary tablespace temp2;
create user test4 identified by test account unlock
ERROR at line 1:
ORA-12910: cannot specify temporary tablespace as default tablespace
SQL>

Move db-file of system temp tablespace

Hallo all,
There is the need to move the system temp tablespace file to another disk. The database version is 9.2.0.1 and runs on an M$ Windows 2000 version 5.00.2195 sp 4 Server.
What is the work around for this task?
Thanks!
Best regards

Hallo!
Thanks for your efforts.
I followed your instructions exactly and it's works for e. g. "system01.dbf". But it doesn't work for the datafile or temp tablespace (TEMP01.DBF). Here is a print out of alert.log. It shows the error-messages and the status of the database:
Tue Feb 15 07:18:17 2005
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Feb 15 07:18:17 2005
ALTER DATABASE MOUNT
Tue Feb 15 07:18:22 2005
Successful mount of redo thread 1, with mount id 3673729017.
Tue Feb 15 07:18:22 2005
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Tue Feb 15 07:22:57 2005
alter database rename file 'D:\oracle\oradata\ho01\temp01.dbf' to 'D:\oracle\oradata\TS-temp\temp01.dbf'
Tue Feb 15 07:22:57 2005
ORA-1511 signalled during: alter database rename file 'D:\oracle\oradata\ho01...
Tue Feb 15 07:26:55 2005
alter database rename file 'D:\oracle\oradata\HO01\TEMP01.DBF' to 'D:\oracle\oradata\TS-temp\TEMP01.DBF'
Tue Feb 15 07:26:55 2005
ORA-1511 signalled during: alter database rename file 'D:\oracle\oradata\HO01...
May be there is something sqecial with this datafile.
Bye!
Stefan

TEMP tablespace increasing

I have a problem with storage space of my default temporary table space.
For my application, I specified the default table space as "DEFTBSPACE" with size 4000MB and temporary table space as "TEMP" with size 14486MB. Now, my usage of my temporary table space is increasing rapidly (Now, the used temp tablespace is 14485MB almost 99.99%). What could be the reason..? Is there any thing going into TEMP tablespace by mistake?.
Please help.
Reagrds,
Satish.

Can we deallocate manually the data file or a part of the datafile so that the usage space is reduced. What's the solution to reduce the usage space of this TEMP tablespace.If you bounce the db, you will get all used space.
I heared, dropping and recreating the TEMP tablespace is the only the solution for this..??Is it true?
Yes it is absolutely true.
Create another temp tabelspace and set as default temp tablespace and drop the previous one. However, make sure no one is currently using that temp tablespace.
The reason that you haven't get any result query v$sort_usge is that no one is using temp currently.
You can also use v$tempseg_usage.
Jaffar
OCP DBA

Rac temp tablespace

Hi
In Rac environment, every node has its own undo and redolog files
However, each instance uses the same temp tablespace,
what is the purpose of this?

The Temporary Tablespace assignment is at Database and User level
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE tablespace_name;
ALTER USER username TEMPORARY TABLESPACE tablespace_name;However, the Undo Tablespace assignment is at Instance level with the parameter
UNDO_TABLESPACETwo instances are not allowed to share an Undo tablespace as the management of the Undo tablespace (being in Automatic Undo Management) is done by the Instance, based on the sessions, transactions and queries present in the instance.
Redo Logs are created by Threads (THREAD# in V$LOG) and each Instance is assigned it's own Redo Thread to "use" (This is parameter "thread" in V$PARAMETER). Two instances cannot use the same Redo Thread.
Hemant K Chitale
http://hemantoracledba.blogspot.com

CMS Repository Database Temp Tablespace Sizing

1. While running some large reports Business Objects (XI 3.1 FP2.7) received an ORA-01652 (Unable to extend temp segment in tablespace TEMP) error for the CMS repository. The CMS database is running in an independent Oracle instance with the auditing database, so only the Business Objects engine would be using the temp tablespace. All the report information is extracted from other database instances. This tablespace was sized at 4GB when this error occurred.
2. What is Business Objects using the CMS repository temp tablespace for? What are some sizing guidelines, should this tablespace be sized based on estimated report sizes, report rows, concurrent users, etc?

I'd say this has nothing to do with Webi processing and has everything to do with your Auditing DB.
Auding DB always growing and that's where that message comes.
Audit guide has more info on managing Audit DB.

To shrink the size of TEMP tablespace

Dear all,
There is a databse with RAC, now in OEM the size of TEMP tablespace has been reached at 99.9%. now we want to shrink the size of TEMP tablespace.
how to we do that???????
plz help me...........

Temporary tablespaces usually show they are full, however this space is not actually in use. It is rather allocated. Oracle has evaluated the best way to obtain the most of performance, and he said it is better to allocate once than allocate-deallocate-reallocate extents, so temporary space is not 'released'.
If you want to feel psychologically more confortable with lower allocated space, you can drop your tablespace (create an interim default temporary tablespace first) and recreate it.
You can also rebuild temporary datafiles:
alter tablespace temp add tempfile 'C:\ORACLE\ORACLEXE\ORADATA\XE\TEMP01.dbf' size 32m;
SQL> select name from v$tempfile;
NAME
C:\ORACLE\ORACLEXE\ORADATA\XE\TEMP.DBF
C:\ORACLE\ORACLEXE\ORADATA\XE\TEMP01.DBF
SQL> alter database tempfile 'C:\ORACLE\ORACLEXE\ORADATA\XE\TEMP01.DBF' drop including datafiles;
Database altered.

Sizing of the OLAP temp tablespace!!

Similar Messages

Maybe you are looking for