SMON is blocking temp tablespace drop
Hi all,
My TEMP TBS became 47G and I want to get rid of that monster. I created the second TEMP TBS, switched default TBS and wanted to drop the huge one, but it hangs there for ever... When I look on the database to see what's going on i see the following:
09:47:33 db_manager@odsp8> @blocking
BLOCKING_STATUS
@bla-bla-bla-bla ( SID=329 ) is blocking SYS@bla-bla-bla-bla ( SID=301 )
09:55:42 db_manager@odsp8> @whois
Enter value for sid: 329
old 3: where sid=&sid
new 3: where sid=329
USERNAME STATUS OSUSER MACHINE PROGRAM
ACTIVE oracle bla-bla-bla-bla oracle@bla-bla-bla-bla *(SMON)*
Definitely, am not gonna kill SMON, but I also need to throw this big TEMP away ASAP.
Does anybody know how to do that and overcome the lock?
Thanks in advance.
M
PS: Oracle 10.2.0.4 RHEL4 64bit
Edited by: MarGur on Jul 20, 2010 9:04 AM
>
sqlplus
/ as sysdba
shutdown immediate
startup mountAnd then ??
As soon as you open the database, SMON will pick up where it left .
Even with another temp tablespace set to as default, SMON will continue cleaning up (coalescing) the extents.
If I remember correctly, we had this also some years ago, we issued:
ALTER DATABASE DATAFILE 'your tempfile' OFFLINE DROP;Then shutdown and restart the database in mount mode and drop the tablespace.
After that open the database for use.
This was then our last - most dirty - solution, while we had waited for 3 days for SMON to finish.
HTH,
FJFranken
My Blog: http://managingoracle.blogspot.com
P.S. If this answers your question, please set the thread to answered and award the points. It is appreciated
Similar Messages
-
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 컬럼이 안들어가서
수정하였습니다. 죄송합니다. -
Drop Temp tablespace hangs...
I have created a new TEMP tablespace and made it default TEMP one.
Now I want to drop TEMP3 tablespace, because it has become fulll...
when I drop it through EM, it hangs...
Once a tablespace has been dropped, the objects and data in it will no longer be available. To recover them can be a time consuming process. Oracle recommends a backup before and after dropping a tablespace.
Are you sure you want to delete Tablespace TEMP3?
Delete associated datafiles from the OS
When I checked at EM, there are locks too..
SMON has locked the system
What should I do now?The_Rock wrote:
I have created a new TEMP tablespace and made it default TEMP one.
Now I want to drop TEMP3 tablespace, because it has become fulll...
when I drop it through EM, it hangs...
Once a tablespace has been dropped, the objects and data in it will no longer be available. To recover them can be a time consuming process. Oracle recommends a backup before and after dropping a tablespace.
Are you sure you want to delete Tablespace TEMP3?
Delete associated datafiles from the OS
When I checked at EM, there are locks too..
SMON has locked the system
What should I do now?Refer
Drop Temp Tablespace Command Hangs [ID 214371.1]
How to Drop Temporary Tablespace Having Enteries in V$SORT_USAGE [ID 285993.1] -
DB 10.2.0.4
AIX 5.2
PROD
I am trying to drop temp tablespace as below command. It is running since nine hours I am not understand why it is taking too much time. FYI I have created a new temp and assigned to default temporary tablespace. Even I connected with new session and run “drop tablespace temp” it is also running since one hour. Suggest me.
DROP TABLESPACE temp INCLUDING CONTENTS AND DATAFILES;
Thanksuser11969485 wrote:
FYI Holder session is "oracle@devdb (SMON)"
Edited by: user11969485 on Jan 7, 2012 12:49 AMYes, Looks like you hitting a BUG.
Check this note Bug 3833893: SMON GETS "TT ENQUEUE" OF TEMP IF DATEFILE OF TEMP DOESN'T EXIST
It saying to drop files from mount status. Lets try :)
Keep Close the Threads, So it meaningful as those answered.
user11969485 Newbie
Handle: user11969485
Status Level: Newbie (10)
Registered: Oct 27, 2009
Total Posts: 302
Total Questions: 66 (57 unresolved)
Edited by: CKPT on Jan 7, 2012 2:36 PM -
Drop temp tablespace goes forever
Hi,
Trying to drop temp tablespace.
I made new default temp tablespace and that part went fine. I can see system using it immediately.
Then I tried to drop the old one.
drop tablespace temp including contents and datafiles;
.... no go .... altough content is gone now. Tablespace was full before this now it's empty.
My command still hangs in sqlplus.
Any idea?
Oracle 10.2.0.1 on Linux x86.You either wait until it's finish. Or kill the session that held it.
SELECT s.sid,
s.serial#,
s.osuser,
s.program
FROM v$session s;
ALTER SYSTEM KILL SESSION 'sid,serial#' -
Hi,
Please help me1) Create new temporary tablespcae
2) Chechk new temp tablespace in default
3) Drop tem pablespace
CREATE TEMPORARY TABLESPACE TEMP2 TEMPFILE’C:\ORACLE\10.2\ORADATA\PROD\temp2_01.dbf’ SIZE 100M AUTOEXTEND ON NEXT 256K
MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP2;
DROP TABLESPACE temp INCLUDING CONTENTS AND datafiles -
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?
thanksHi 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 -
DROP and RECREATE TEMP TABLESPACE
Hey,
is it ok just to drop the TEMP tablespace and recreate it?
Will data get lost? Will developers kill me if I do? ;o)
Can i reuse the datafile?
Is it possible to change name on the tablespace?
Thanks
KjerstiHey there is absolutely no problem. Only ensure that only system is logged on and no other user is using the database. Best thing is to shut down the database and restart in restricted session and then create the temp tablespace. give tempfile instead of datafile.
-
Restored coldbackup and having trouble with TEMP tablespace
Hi, i succesfully restored from a coldbackup on solaris.(oracle 9.2)
i can log on to database using toad, query the database, but when i try to take an export or something i got the error
EXP-00056: ORACLE error 1157 encountered
ORA-01157: cannot identify/lock data file 203 - see DBWR trace file
ORA-01110: data file 203: '/sun2int1/oracle92/app/oracle/product/9.2.1/oradata/TPRS/temp03.dbf'
ORA-06512: at "SYS.DBMS_LOB", line 424
ORA-06512: at "SYS.DBMS_METADATA", line 1140
ORA-06512: at line 1
EXP-00000: Export terminated unsuccessfully
when i did the restore, i simply renamed the datafiles and redo logs.
But i didnt rename the TEMP datafile, as you can not rename it with a "alter database rename file ..." command
so thats the problem!
i planned to create a new default temp. tablespace, and simply make it default and drop the other one. but it does not work!
i tried to execute:
CREATE TEMPORARY TABLESPACE temp4 TEMPFILE '/oracleAS/TPRS/oradata/TPRS/temp4.dbf' SIZE 5M REUSE AUTOEXTEND ON NEXT 1M MAXSIZE unlimited
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
create temporary tablespace temp01 tempfile '/oracleAS/TPRS/oradata/TPRS/temp01.dbf' size 100M;
but they all hang! i wait, but nothing happens! (and alert log does not log anything too)
and finally i tried to drop the default tablespace, and i couldnt drop it as i thought. (ORA-12906: cannot drop default temporary tablespace
So, im stuck and i beleive i have to RENAME the datafile for temporary tablespace. how can i do this?
Edited by: merope on Jun 9, 2009 11:32 AMSQL> col file_name for a50
col status for a15
col tablespace_name for a15
col PROPERTY_VALUE for a20
select file_name,tablespace_name,bytes/1024/1024 as "SIZE_IN_MB",status,autoextensible from dba_temp_files;
SELECT PROPERTY_NAME,PROPERTY_VALUE FROM DATABASE_PROPERTIES where PROPERTY_NAME='DEFAULT_TEMP_TABLESPACE';
SQL> SQL> SQL> SQL> SQL> SQL> ERROR:
ORA-01157: cannot identify/lock data file 202 - see DBWR trace file
ORA-01110: data file 202: '/izmir1/oradbTPRS/temp1.db'
no rows selected
SQL>
PROPERTY_NAME PROPERTY_VALUE
DEFAULT_TEMP_TABLESPACE TEMP3
This is not the actual directory: /izmir1/oradbTPRS/temp1.db
it is the old location, but in the restored db, the temp1.db file is in some other directory
how can i rename this?
Edited by: merope on Jun 9, 2009 11:50 AM -
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. -
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;
-- -
Hi
I am having problem in executing the SQL query with certain parameters in the WHERE clause.
ORA-01114: IO error writing block to file 4 (block # 524242)
ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
OSD-04026: Invalid parameter passed. (OS 524247)
ORA-01114: IO error writing block to file 4 (block # 524242)
ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
OSD-04026: Invalid parameter passed. (OS 524247)
I get the above listed error. And i assumed there may be some issue due to Temp tablespace. I also verified the space occupied by the TEMP tablespace and it was 99% occupied.
Kindly let me know is there a way to extend the space without affecting the existing DB content
Regards
Srinivasan BDidn't you got a answer in your Getting error while executing the SQL ( ver 8.1.7.0.0), did you ?
Furthermore, don't worry about the TEMP tablespace utilization, Oracle doesn't freed space until you need it. By the way, how your TEMP tbs is defined (AUTOEXTEND, DATAFILE/TEMPFILE...) ?
Anyway, you have to be sure about the free space on your device. And check on metalink website to get some notes advices.
Nicolas. -
TEMP tablespace is always full in Enterprise Manager
The TEMP tablespace is always (99.99%) full in Enterprise Manager console. How can I release it and check it?
Yes, Kamal did give the answer. owever, it still remains confusing to most people.
The temp tablespace, like all tablespaces, is used to hold SEGMENTS. There are several kinds of temporary segments, including sort segments and segments for global temporary tables.
WHen a segment is allocated, it takes time to find the blocks that are free and to format those blocks.
Oracle's performance measure to counter the cost of finding and formatting free blocks is to leave the segment allocated at that kind of block. When a session terminates, any temprary segments it holds will be released to the free pool of 'that type of temprary segment', and another session can then (as you say) reuse the space.
Still, this is frustrating for the new DBA who has not read the concepts manual and not searched the forum on 'v$sort' or 'temporary tablespace usage'.
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14220/logical.htm#sthref399 -
Hi all,
We have an Oracle 10.2.0.4 Reporting database, of which every night al lot of data is refreshed from production databases.
For this refresh this database uses complex Materialized View definitions.
We recently keep running out of TEMP tablespace during the refresh of these MV's. The TEMP tablespace has lately been increased several times ( in total from 15Gb to 25Gb the last months).
The largets MV is just 3Gb's big. Especially the one that ran out of TEMP tablespace last night is only 1Gb big.
The error message:
ORA-12008: error in materialized view refresh path
ORA-12801: error signaled in parallel query server P002
ORA-01652: unable to extend temp segment by 64 in tablespace TEMP
Can anyone tell me what could cause this behaviour ??
Some specs:
Oracle 10.2.0.4
Platform: AIX 5.3 TL06
sga_target = 3504M
parallel_max_servers=8
temp_tablespace_size=25600Mb
Thanks in advanceThey are COMPLETE refreshes.
Statement of the view:
SELECT /*+ NO_USE_HASH_AGGREGATION */
mon.mon_description AS mon_mon_descr, mon.mon_code AS mon_mon_code,
mon.yer_code AS mon_yer_code, cus.iet_descr AS cus_iet_descr,
prd.igp_nr AS prd_igp_nr, prd.igp_descr_german AS prd_igp_descr_ger,
prd.igp_descr_dutch AS prd_igp_descr_dut,
prd.igp_descr_english AS prd_igp_descr_eng,
prd.igp_descr_czech AS prd_igp_descr_ces,
prd.igp_descr_russian AS prd_igp_descr_rus, prd.pgp_nr AS prd_pgp_nr,
prd.pgp_descr_german AS prd_pgp_descr_ger,
prd.pgp_descr_dutch AS prd_pgp_descr_dut,
prd.pgp_descr_english AS prd_pgp_descr_eng,
prd.pgp_descr_czech AS prd_pgp_descr_ces,
prd.pgp_descr_russian AS prd_pgp_descr_rus, prd.dvs_nr AS prd_dvs_nr,
prd.dvs_descr_german AS prd_dvs_descr_ger,
prd.dvs_descr_dutch AS prd_dvs_descr_dut,
prd.dvs_descr_english AS prd_dvs_descr_eng,
prd.dvs_descr_czech AS prd_dvs_descr_ces,
prd.dvs_descr_russian AS prd_dvs_descr_rus,
cus.pce_descr AS cus_pce_descr, cus.smk_descr AS cus_smk_descr,
cus.org_descr AS cus_org_descr, cus.dpm_descr AS cus_dpm_descr,
cus.cmp_descr AS cus_cmp_descr, cus.cgp_descr AS cus_cgp_descr,
cus.cus_nr AS cus_cus_nr, cus.cus_descr AS cus_cus_descr,
cus.cus_billto_nr AS cus_billto_nr,
SUM (fin.invoice_discount_eur) AS invoice_discount_eur,
SUM (fin.invoice_discount_gbp) AS invoice_discount_gbp,
SUM (fin.invoice_line_discount_eur) AS invoice_line_discount_eur,
SUM (fin.invoice_line_discount_gbp) AS invoice_line_discount_gbp,
SUM (fin.turnover_cr_eur) AS turnover_cr_eur,
SUM (fin.turnover_cr_gbp) AS turnover_cr_gbp,
SUM (fin.turnover_deb_eur) AS turnover_deb_eur,
SUM (fin.turnover_deb_gbp) AS turnover_deb_gbp,
SUM (fin.turnover_eur) AS turnover_eur,
SUM (fin.turnover_gbp) AS turnover_gbp,
SUM (fin.count_credit_slips) AS count_credit_slips,
cus.srp_nr AS cus_srp_nr, cus.srp_descr AS cus_srp_descr,
COUNT (*) AS total_records,
COUNT (fin.count_credit_slips) AS num_count_credit_slips,
cus.cus_branch AS cus_branch_nr, cus.cus_district AS cus_district_nr,
SUM (fin.profit_eur) AS profit_eur,
SUM (fin.profit_gbp) AS profit_gbp,
SUM (fin.cost_price_eur) AS costs_eur,
SUM (fin.cost_price_gbp) AS costs_gbp,
SUM (fin.invoice_discount_chf) AS invoice_discount_chf,
SUM (fin.invoice_line_discount_chf) AS invoice_line_discount_chf,
SUM (fin.turnover_cr_chf) AS turnover_cr_chf,
SUM (fin.turnover_deb_chf) AS turnover_deb_chf,
SUM (fin.turnover_chf) AS turnover_chf,
SUM (fin.profit_chf) AS profit_chf,
SUM (fin.cost_price_chf) AS costs_chf,
SUM (fin.invoice_discount_czk) AS invoice_discount_czk,
SUM (fin.invoice_line_discount_czk) AS invoice_line_discount_czk,
SUM (fin.turnover_cr_czk) AS turnover_cr_czk,
SUM (fin.turnover_deb_czk) AS turnover_deb_czk,
SUM (fin.turnover_czk) AS turnover_czk,
SUM (fin.profit_czk) AS profit_czk,
SUM (fin.cost_price_czk) AS costs_czk,
SUM (fin.invoice_discount_rub) AS invoice_discount_rub,
SUM (fin.invoice_line_discount_rub) AS invoice_line_discount_rub,
SUM (fin.turnover_cr_rub) AS turnover_cr_rub,
SUM (fin.turnover_deb_rub) AS turnover_deb_rub,
SUM (fin.turnover_rub) AS turnover_rub,
SUM (fin.profit_rub) AS profit_rub,
SUM (fin.cost_price_rub) AS costs_rub,
COUNT (fin.invoice_discount_eur) AS cnt_invoice_discount_eur,
COUNT (fin.invoice_discount_gbp) AS cnt_invoice_discount_gbp,
COUNT
(fin.invoice_line_discount_eur)
AS cnt_invoice_line_discount_eur,
COUNT
(fin.invoice_line_discount_gbp)
AS cnt_invoice_line_discount_gbp,
COUNT (fin.turnover_cr_eur) AS cnt_turnover_cr_eur,
COUNT (fin.turnover_cr_gbp) AS cnt_turnover_cr_gbp,
COUNT (fin.turnover_deb_eur) AS cnt_turnover_deb_eur,
COUNT (fin.turnover_deb_gbp) AS cnt_turnover_deb_gbp,
COUNT (fin.turnover_eur) AS cnt_turnover_eur,
COUNT (fin.turnover_gbp) AS cnt_turnover_gbp,
COUNT (fin.profit_eur) AS cnt_profit_eur,
COUNT (fin.profit_gbp) AS cnt_profit_gbp,
COUNT (fin.cost_price_eur) AS cnt_costs_eur,
COUNT (fin.cost_price_gbp) AS cnt_costs_gbp,
COUNT (fin.invoice_discount_chf) AS cnt_invoice_discount_chf,
COUNT
(fin.invoice_line_discount_chf)
AS cnt_invoice_line_discount_chf,
COUNT (fin.turnover_cr_chf) AS cnt_turnover_cr_chf,
COUNT (fin.turnover_deb_chf) AS cnt_turnover_deb_chf,
COUNT (fin.turnover_chf) AS cnt_turnover_chf,
COUNT (fin.profit_chf) AS cnt_profit_chf,
COUNT (fin.cost_price_chf) AS cnt_costs_chf,
COUNT (fin.invoice_discount_czk) AS cnt_invoice_discount_czk,
COUNT
(fin.invoice_line_discount_czk)
AS cnt_invoice_line_discount_czk,
COUNT (fin.turnover_cr_czk) AS cnt_turnover_cr_czk,
COUNT (fin.turnover_deb_czk) AS cnt_turnover_deb_czk,
COUNT (fin.turnover_czk) AS cnt_turnover_czk,
COUNT (fin.profit_czk) AS cnt_profit_czk,
COUNT (fin.cost_price_czk) AS cnt_costs_czk,
COUNT (fin.invoice_discount_rub) AS cnt_invoice_discount_rub,
COUNT
(fin.invoice_line_discount_rub)
AS cnt_invoice_line_discount_rub,
COUNT (fin.turnover_cr_rub) AS cnt_turnover_cr_rub,
COUNT (fin.turnover_deb_rub) AS cnt_turnover_deb_rub,
COUNT (fin.turnover_rub) AS cnt_turnover_rub,
COUNT (fin.profit_rub) AS cnt_profit_rub,
COUNT (fin.cost_price_rub) AS cnt_costs_rub
FROM /* dwh_internal_external_dim iet */
dwh_customers_dim cus /* department */
, dwh_products_dim prd /* itemgroup */
, dwh_months_dim mon
, dwh_financial_fct fin
WHERE fin.mon_code = mon.mon_code
AND fin.prd_id = prd.prd_id
AND fin.cus_cus_id = cus.cus_id
GROUP BY mon.mon_description,
mon.mon_code,
mon.yer_code,
cus.iet_descr,
prd.igp_nr,
prd.igp_descr_german,
prd.igp_descr_dutch,
prd.igp_descr_english,
prd.igp_descr_czech,
prd.igp_descr_russian,
prd.pgp_nr,
prd.pgp_descr_german,
prd.pgp_descr_dutch,
prd.pgp_descr_english,
prd.pgp_descr_czech,
prd.pgp_descr_russian,
prd.dvs_nr,
prd.dvs_descr_german,
prd.dvs_descr_dutch,
prd.dvs_descr_english,
prd.dvs_descr_czech,
prd.dvs_descr_russian,
cus.pce_descr,
cus.smk_descr,
cus.org_descr,
cus.dpm_descr,
cus.cmp_descr,
cus.cgp_descr,
cus.cus_nr,
cus.cus_descr,
cus.cus_billto_nr,
cus.srp_nr,
cus.srp_descr,
cus.cus_branch,
cus.cus_district;
Explain plan:
Plan
SELECT STATEMENT CHOOSE Cost: 278,496 Bytes: 13,752,541,260 Cardinality: 18,864,940
25 PX COORDINATOR
24 PX SEND QC (RANDOM) PARALLEL_TO_SERIAL SYS.:TQ10005 :Q1005 Cost: 278,496 Bytes: 13,752,541,260 Cardinality: 18,864,940
23 SORT GROUP BY PARALLEL_COMBINED_WITH_PARENT :Q1005 Cost: 278,496 Bytes: 13,752,541,260 Cardinality: 18,864,940
22 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1005 Cost: 278,496 Bytes: 13,752,541,260 Cardinality: 18,864,940
21 PX SEND HASH PARALLEL_TO_PARALLEL SYS.:TQ10004 :Q1004 Cost: 278,496 Bytes: 13,752,541,260 Cardinality: 18,864,940
20 SORT GROUP BY PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 278,496 Bytes: 13,752,541,260 Cardinality: 18,864,940
19 HASH JOIN PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 26,390 Bytes: 13,752,541,260 Cardinality: 18,864,940
4 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 55 Bytes: 11,394,614 Cardinality: 70,774
3 PX SEND BROADCAST PARALLEL_TO_PARALLEL SYS.:TQ10000 :Q1000 Cost: 55 Bytes: 11,394,614 Cardinality: 70,774
2 PX BLOCK ITERATOR PARALLEL_COMBINED_WITH_CHILD :Q1000 Cost: 55 Bytes: 11,394,614 Cardinality: 70,774
1 TABLE ACCESS FULL TABLE PARALLEL_COMBINED_WITH_PARENT MIS_RUN.DWH_CUSTOMERS_DIM :Q1000 Cost: 55 Bytes: 11,394,614 Cardinality: 70,774
18 HASH JOIN PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 26,300 Bytes: 10,715,285,920 Cardinality: 18,864,940
8 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 2 Bytes: 2,052 Cardinality: 108
7 PX SEND BROADCAST PARALLEL_TO_PARALLEL SYS.:TQ10001 :Q1001 Cost: 2 Bytes: 2,052 Cardinality: 108
6 PX BLOCK ITERATOR PARALLEL_COMBINED_WITH_CHILD :Q1001 Cost: 2 Bytes: 2,052 Cardinality: 108
5 TABLE ACCESS FULL TABLE PARALLEL_COMBINED_WITH_PARENT MIS_RUN.DWH_MONTHS_DIM :Q1001 Cost: 2 Bytes: 2,052 Cardinality: 108
17 HASH JOIN PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 26,264 Bytes: 10,356,852,060 Cardinality: 18,864,940
12 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 305 Bytes: 178,954,440 Cardinality: 426,082
11 PX SEND HASH PARALLEL_TO_PARALLEL SYS.:TQ10002 :Q1002 Cost: 305 Bytes: 178,954,440 Cardinality: 426,082
10 PX BLOCK ITERATOR PARALLEL_COMBINED_WITH_CHILD :Q1002 Cost: 305 Bytes: 178,954,440 Cardinality: 426,082
9 TABLE ACCESS FULL TABLE PARALLEL_COMBINED_WITH_PARENT MIS_RUN.DWH_PRODUCTS_DIM :Q1002 Cost: 305 Bytes: 178,954,440 Cardinality: 426,082
16 PX RECEIVE PARALLEL_COMBINED_WITH_PARENT :Q1004 Cost: 11,396 Bytes: 2,433,577,260 Cardinality: 18,864,940
15 PX SEND HASH PARALLEL_TO_PARALLEL SYS.:TQ10003 :Q1003 Cost: 11,396 Bytes: 2,433,577,260 Cardinality: 18,864,940
14 PX BLOCK ITERATOR PARALLEL_COMBINED_WITH_CHILD :Q1003 Cost: 11,396 Bytes: 2,433,577,260 Cardinality: 18,864,940
13 TABLE ACCESS FULL TABLE PARALLEL_COMBINED_WITH_PARENT MIS_RUN.DWH_FINANCIAL_FCT :Q1003 Cost: 11,396 Bytes: 2,433,577,260 Cardinality: 18,864,940
Thanks again -
Does rebuild of indexes uses temp tablespace or system tablespace?
Does rebuild of indexes uses temp tablespace or system tablespace?
If so why?If you combine the answers from Aman and Burleson, they cover most of the picture.
When rebuilding an index, you may end up sorting a large amount of information. The sort may spill into the temporary tablespace - if you haven't configured your database and users properly, it is possible that the SYSTEM tablespace may be used for the temporary tablespace.
As the new copy of the index is built, it has to be built in the right place (tablespace), and the space used to build it will be marked as a temporary segment as the build takes place. When the build is complete, this temporary segment will take on the name of the origrinal index, and the original index will be re-badged as a temporary segment and dropped. (Again, you might see temporary segments in the SYSTEM tablespace if the index was originally in, or was rebuilt into, the SYSTEM tablespace).
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
Maybe you are looking for
-
Where this field (BSEG-AUFNR) gets populated from ? Some threads says it is an internal order. What does it mean ? Thanks Rita
-
How do I import and use the Keynote themes that I've downloaded?
I'm sure this is a stupid question, but I searched this forum & didn't immediately find the answer I needed. I've downloaded some Keynote themes (they have a .kth extension). How do I import these into Keynote 08 so that Keynote will recognize and us
-
Connection PDA through virtual USB controller in Virtualbox
hi! i need some guideness for doing the connection with my pda device and usb controller in virtualbox i ve found what to do on user guide of virtualbox. i'm placing the the specific part that i found in the page 49.here it is user manual of virtualb
-
I'm due to be installed with BT Infinity 2 on Monday 30/09/13 with delivery of the router expected on Thursday 26/09/13. As I work full time I will not be in the house at the time and was wondering if a signature is required or will they post it thro
-
Any more information on :IMAQ Count Objects" vi?