From: "andrew_webby at hotmail" Newsgroups: comp.databases.oracle.server Subject: Re: Strange Segment called 6.2 in TEMP Date: Wed, 6 Jun 2001 11:09:39 +0100 Message-ID: <991822205.28628.0.nnrp-12.c30bdde2@news.demon.co.uk> References: <0BcT6.2$i91.3032@nsw.nnrp.telstra.net> <3B1DAB89.CCBDCF50@pro-ns.net> NNTP-Posting-Host: mailgate.highland.gov.uk X-NNTP-Posting-Host: mailgate.highland.gov.uk:195.11.221.226 X-Trace: news.demon.co.uk 991822205 nnrp-12:28628 NO-IDENT mailgate.highland.gov.uk:195.11.221.226 X-Complaints-To: abuse@demon.net X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Lines: 48 Temporary segment doesn't contain tables - it holds interrim results between sorting, joining etc (unless you are into creating "global temporary tables" of course). Also, this segment will disappear when you shut the database down, and when you bring it up again (and someone needs to sort on disk), it will be recreated. If your next question is "why is it almost filled the tablespace?", the answer is that it's supposed to be that way. "Alex Filonov" wrote in message news:3B1DAB89.CCBDCF50@pro-ns.net... > Bernie wrote: > > > I have been watching our 7.3 Oracle database and for the last few days, the > > TEMP tablespace has been consumed by a large temporary segment named 6.2. > > > > Does anyone know what this is and if it really should be there? I would have > > thought a temporary segment would be temporary rather than hanging around for > > over 2 days? > > > > The out put of > > SELECT SEGMENT_NAME,OWNER,BYTEs, SEGMENT_TYPE FROM DBA_SEGMENTS WHERE > > TABLESPACE_NAME='TEMP' > > / > > > > is > > SEGMENT_NAME OWNER BYTES SEGMENT_TYPE > > -------------------- ------------------------------ ---------- > > ----------------- > > 6.2 SYS 497827840 TEMPORARY > > > > Bernie > > It's OK. You segment has TEMPORARY type, so it uses special type of allocation > for temp tables. That (6.2) temporary segment actually contains all your temp > tables. Even when you don't have any temporary tables, this segment is visible. > For more on this feature, read documentation. >