do NOT set pctincrease to 1 even in this case.
when you allow SMON to coalesce whenever it wants, it does just that,
WHENEVER it wants -- even if you have heavy user activity. So at that
time SMON is ignoring what it has to do for the users.
Also, SMON coalesce does a very small coalesce, (I ca
I think I mentioned this earlier. :)
SMON will do a coalesce if necessary to provide blocks for
an extent, if necessary.
The following link tells all. This may be in the 8i manual, but it
works the same way in the Oracle 7.
http://otn.oracle.com/docs/products/oracle8i/doc_library/817_doc/ser
Cary Millsap, in his 'Myths About Extents' presentation advocates turning
off the auto-coalescing by SMON, stating that the auto-coalesce feature does
more harm than good.
He had presented this at OAUG Database SIG meeting in Hawaii (held in Oct,
2000).
- Kirti
-Original Message-
Se
Okie. To be more specific. This is a siebel application running against a
7.3.4 database. So the 8i features for space management are out of the
question. Second, there are large tables with varied values for initial and
next extent in the tablespace. There are also going to be temporary tables
c
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject: SMON - Does it cause a degrade?
Hey Fellas,
I have an application DBA who insists that the pctincrease at the data
tablespace should be set to 0 so that SMON does not coalesce the
ECTED]
> Sent by: [EMAIL PROTECTED]
> 01/25/02 01:50 PM
> Please respond to ORACLE-L
>
>
> To: Multiple recipients of list ORACLE-L
> <[EMAIL PROTECTED]>
> cc:
> Subject:SMON - Does it cause a degrade?
>
>
> Hey Fellas,
Why the heck would you set pctincrease to anything but 0 at the
tablespace level. All you need is one table, created without storage
parameters and you are fragmented.
Try "Stop Defragmenting and Start Living"... what you want to do is
exactly what your DBA said, with the addition of either local
Thanks Melissa. I was wrong, I guess. For this is what I found on Metalink.
1. Because SMON acquires the Space Transaction (ST) enqueue in exclusive mode, other
processes requiring the enqueue will be
blocked. This is typically manifested by multiple errors.
2. SMON sits in a very tight loop
: [EMAIL PROTECTED]
01/25/02 01:50 PM
Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc:
Subject: SMON - Does it cause a degrade?
Hey Fellas,
I have an application DBA who insists that the pctincrease at the d
Title: RE: SMON - Does it cause a degrade?
Check out meta link note:61997.1 SMON - Temporary Segment Cleanup and Free Space Coalescing. For one explanation.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 25, 2002 4:50 PM
To: Multiple
Hey Fellas,
I have an application DBA who insists that the pctincrease at the data
tablespace should be set to 0 so that SMON does not coalesce the
tablespace. He says coalesce will be performed by using a scheduled batch
job written for that purpose. He states that having SMON to perform an
coal
11 matches
Mail list logo