Re: Root DBspace confusion

Mark, I like your suggested clarifications for this paragraph -- to not say "resize", but instead say "use a minimal log size when you first initialize the database server", and then do all the steps to move and resize the logs after initialization to keep the root dbspace small. We are currently updating this paragraph and will incorporate your suggestions. Thanks! Virginia At 11:37 AM 11/29/00 , mrh@panix.com wrote: >> >> Hi Michael and Mark, >> >> Yes, this paragraph does not address what to do when you resize the >> root dbspace after you've already defined your dbspaces, chunks, etc. >> This section addresses sizing estimates BEFORE you start the >> database server the first time. We recommend elsewhere that the >> physical and logical logs should be in separate dbspaces from the >> root dbspace for better performance, and I think this paragraph was >> alluding to that recommendation for the initial sizing. >> > >Maybe we shuld just make the whole thing clear and stop saying "RESIZE the >root dbspace". I understand that you can *add* space and then drop those >chunks, but the passage in question is specifically dealing with the >original size estimates and the fact that after moving the logs out of the >root, your root will have extra space it doesn't need. At that point it >mentions the ability to resize the space.... clearly meaning to make it >smaller and reclaim that "wasted" space. > >> >> We will clarify this section in the next version of the Administrator's >> Guide to indicate the following: >> >> - this estimate is the initial root dbspace size prior initializing >> the database server the first time > >Ok.. that looks right. > >> >> - the initial size of the root dbspace depends on whether or not you >> plan to store other physical and logical units of storage (such as >> logs or temp tables) there. If you're expecting a lot of update >> activity, you might want to start with the logs in separate dbspaces >> from the root. > >Now, hold on. The original "oninit -i", or 'onmonitor' depending on your >preference, initialization will create the Logical Logs and the Physical Log >in root dbspace automatically. There is *NO* way around this! You cannot >"start with the logs in separate dbspaces from the root". Totally impossible. > >What you might want to say, though, is to use as minimal a log size as possible >(I believe 1000K) and as minimal a number (3 logical). Once initalization is >complete, create new dbspaces, move and resize the logfiles, and drop the logs >from the root dbspace. This will keep rootdb at a minimal size. > >Michael Hoffman >