Message-
From: Tim Gorman [mailto:[EMAIL PROTECTED]
Sent: Monday, 27 October 2003 2:44 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: Coalescing tablespace
Ross,
Wow! That's a blast from the past! ALTER TABLESPACE ...
COALESCE didn't
arrive on the scene until v7.3, so prior
Yes, you are right, of course. I messed up.
On 10/27/2003 01:34:25 AM, Cary Millsap wrote:
You mean make your PCTINCREASE 0 so that SMON will *not* coalesce
them. Right? Some comments:
- You don't want SMON coalescing your tablespaces. It is a complete
waste of time. Oracle coalesces on demand
I always saw this note (and hated it):
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_datab
ase_id=NOTp_id=31116.1
Hope it helps,
Waleed
-Original Message-
Sent: Sunday, October 26, 2003 8:04 PM
To: Multiple recipients of list ORACLE-L
Hi,
For those like me
Ah yes, the squashed squirrel demo...
Connor
--- Cary Millsap [EMAIL PROTECTED] wrote:
You mean make your PCTINCREASE 0 so that SMON will
*not* coalesce
them. Right? Some comments:
- You don't want SMON coalescing your tablespaces.
It is a complete
waste of time. Oracle coalesces on
I wasn't feeling quite well when I was replying which made me confuse
things. You, of course are right. SMON was locking fet$ table during
those coalesce session, which was exceptionally dangerous in the OPS
configurations. Coalescing doesn't buy much,the coalesce operation
just combines
Bingo. I've included a few more details in a separate note sent just
prior to my receiving this one.
Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
Upcoming events:
- Performance Diagnosis 101: 10/28 Phoenix, 11/19 Sydney
- SQL Optimization 101: 12/8-12 Dallas
- Hotsos Symposium
It's a note created in response to hundreds of customers shouting about
how VMS and DOS need defragmenting; therefore, Oracle must need
defragmenting, too.
There *was* a cluster bug way back in release 6 that caused CREATE
statements to take a really long time if you ever let a tablespace get
Cary,
Hang on a second. Oracle will not always coalesce on create to the extent
needed. It will go out either 10 or 20 extents (rusty memory here) and then give up.
In this case it will either create an extent of the size requested above all of the
other objects in the tablespace or
Dick,
You said:
I think the Server Technologies folks need to spend a little more time with
SMON. It certainly does not appear to pull it's due.
I think they avoided the issue with Locally Managed Tablespaces. All of
these problems go away with standardized extent sizes.
Tom Mercadante
Tom,
Well if that was the only place SMON seems to be weak, I'd wholeheartedly
agree. But it leave something to be desired when a user terminates their session
ungracefully as well. Yes I know that's primarily PMON's job, but I've been told by
OTS that some of it is also SMON's job
Cary,
Under 7.1, 7.2, and 7.3, there were some very real situations where even the
most careful space management strategies came to naught. Specifically, the
habit of parallel direct-path operations on tables and indexes to trim
the last extent to avoid leaving wasted space above the high-water
Hi,
For those like me still working on an Oracle 716 (hold the laughs), how do
we coalesce a tablespace?
Rgds,
Ross
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Ross Collado
INET: [EMAIL PROTECTED]
Fat City Network Services-- 858-538-5051
Well, having in mind that you're working on version 7 (chuckle) , you should
make your tablespaces have PCTINCREASE 0 (alter tablespace default storage...)
so SMON will coalesce them. You may also try (I'm not sure whether this has
existed before 7.3) with alter tablespace coalesce, which
Ross,
Wow! That's a blast from the past! ALTER TABLESPACE ... COALESCE didn't
arrive on the scene until v7.3, so prior to that version you had to do
something like the following:
alter session set events 'immediate trace name coalesce level NNN';
where the value of the level NNN could be
suggested in a
loop for all tablespaces.
Thanks again and to others for the prompt reply.
Rgds,
Ross
-Original Message-
From: Tim Gorman [mailto:[EMAIL PROTECTED]
Sent: Monday, 27 October 2003 2:44 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: Coalescing tablespace
You mean make your PCTINCREASE 0 so that SMON will *not* coalesce
them. Right? Some comments:
- You don't want SMON coalescing your tablespaces. It is a complete
waste of time. Oracle coalesces on demand during a CREATE statement.
- The SMON coalesce feature was added under protest by the smart
16 matches
Mail list logo
