Re: Resizing Logical Logs

In article <5jfrq1$nn4@cssun.mathcs.emory.edu>, Bill Ennis <ennis@ssax.com> writes >Hi, > >Sizes for logical logs is done when the engine is initialized. >Therefore, you'de have to reinit the engine to change their size; >unless this has been changed recently - anyone? > This has changed in Online 7. Online 5 Admin Guide Page 7-68, adding a logical log using the command line tool (tbparams) Syntax tbparams -a -d dbspace NOTE NO OPTION TO DEFINE SIZE. Online 5 Admin Guide Page 3-22, changing the size of logical log files. "The size of the logical log files is specified as LOGSIZE in the configuration file....To change the size of the logical log files, you must reinitialize disk space, which will destroy all existing data in the process." The maximum number of logical logs you can have (maximum value of LOGSMAX) is around 61 (depends upon the specific port of Online 5 which you have). THIS IS IN THE MANUAL - I JUST CAN NEVER FIND IT... Online 7 Admin Guide Volume 2 Page 40-51 onparams -a -d dbspace [-s size] NOTE OPTION TO DEFINE THE SIZE. Online 7 Admin Guide Volume 2 Page 38-31 The maximum number of logical logs you can have (maximum value of LOGSMAX) is 32767. >What you can do is add more logical logs. This can achieve the same result. >You can add logs up to the LOGSMAX onconfig parameter (you are using >version 7?). BTW LOGSMAX can be changed without reiniting the engine >if it is too low. You will have to bring the engine down/up to make >the change effective. One other thing to note is that the logical >logs need to be backed up before they can be used. > Correct - I normally change TAPEDEV in $INFORMIXDIR/etc/$ONCONFIG to /dev/null whilst I run a level 0 archive to make the new logs usable (ontape -s -L 0). >Hope this helps, >Bill > -- David Williams