Changing physical log size in non-rootdbs

On IDS 11.5 life is grand, but now a Performance Advisory tells me that I must increase the size of my physical log. Good. This is not raw space. Even though I moved the physical log to a dbspace that is NOT the rootdbs, my estimate of the size of the dbspace was inadequate. Since the Admin Guide says that the space for the physical log must be "contiguous", does that prevent me from just adding a chunk to the dbspace, then using onparams to increase the size of the physical log? Thanks, Laurie

Found the answer by doing. FYI... Take IDS 11.5 to admin mode (quiescent)using onmode -j. Use onparams -p to move log from its non-root-dbspace to another dbspace (where there is enough room for a physical log of the same size). Run fake archive. Drop the dbspace where the physical log was prior to the move (onspaces -d). Run fake archive. Create the dbspace again (onspaces -c) where the physical log was before using the same name but larger size (twice the size in my case). Run fake archive. Use onparams -p to move the log back to the former non-root-dbspace with a larger size. Run real Level zero archive. Whooppeeee!! Laurie

On Thu, Jan 6, 2011 at 12:48 AM, LAURIE S. LITTLEDIKE < laurie.littledike@usurf.usu.edu> wrote: > Found the answer by doing. FYI... > > Take IDS 11.5 to admin mode (quiescent)using onmode -j. > No need... Can be done in online mode. Welcome to XXI century, and 11.50 :) By the way... 11.7 has arrived :) Regards. -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... --000e0cd1fc10deee2e0499233a4a

Fernando: I returned to the Admin Reference Guide for 11.5 and verified what you replied. Thank you very much. Laurie