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 coalesce of the tablespace could cause an performance degrade??? I have never heard of such a thing, but then I dont wanna argue with him. He's got wrinkles on his face, and grey hair ;-)
My argument would be, go back to the drawing board, get your tables sized properly, if you anticipate fragmentation. And SMON does not cause a performance degrade? It wakes up every 5 minutes, does hold ST enqueue locks if a tablespace needs coalescing, but it does not cause a performance degrade? Or does it??? Now, can I have a definitive word on this? Any sites, white papers, to refer to that says so, or to the contrary. I need to convince the higher ups. Raj -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
