changing size of logs

Hi all, I am about to change the number and size of my logical logs from 100 5M logs to 500 1M logs and I wanted to make sure I am going to do this right. 1. change LOGSMAX in onconfig to 600 2. bounce engine and bring it back up in quiescent mode 3. make 500 1M logs with onparams 4. drop 97 of the 5M logs 5. do a level 0 archive 6. force checkpoint into one of the 1M logs 7. drop the remaining 3 5M logs 8. do another level 0 archive 9. bring engine back online. Will this accomplish what I want? Am I missing something critical that may cause something disaterous? Does anyone have any suggestion to make this any easier or safer? Thanks Joe ------------------------------------------------------------------------- Joseph Cullipher <joseph@cannonexpress.com> Standard Disclaimers Apply -------------------------------------------------------------------------

It's OK. You don't need to change LOGSMAX manually. If you do a level 0 after creating your 1M logs you can drop all the %m ones in one fell swoop. But Why?????????????????????????????????????????? Neil Truby Londis Stores Hampton Hill, UK Joseph Cullipher wrote in message <7b1tlq$d67$1@news.xmission.com>... > >Hi all, > >I am about to change the number and size of my logical logs from 100 5M logs >to 500 1M logs and I wanted to make sure I am going to do this right. >1. change LOGSMAX in onconfig to 600 >2. bounce engine and bring it back up in quiescent mode >3. make 500 1M logs with onparams >4. drop 97 of the 5M logs >5. do a level 0 archive >6. force checkpoint into one of the 1M logs >7. drop the remaining 3 5M logs >8. do another level 0 archive >9. bring engine back online. > >Will this accomplish what I want? Am I missing something critical that may >cause something disaterous? Does anyone have any suggestion to make this >any easier or safer? > >Thanks >Joe > >------------------------------------------------------------------------- >Joseph Cullipher <joseph@cannonexpress.com> Standard Disclaimers Apply >------------------------------------------------------------------------- >

Joseph Cullipher wrote: > I am about to change the number and size of my logical logs from 100 > 5M logs to 500 1M logs and I wanted to make sure I am going to do this > right. Step 0. Do a complete archive before you *start* all this. YIKES!! > 1. change LOGSMAX in onconfig to 600 > 2. bounce engine and bring it back up in quiescent mode > 3. make 500 1M logs with onparams > 4. drop 97 of the 5M logs > 5. do a level 0 archive > 6. force checkpoint into one of the 1M logs -----------^^^^^^^^^^ Minor correction - Force log switch (onmode -l) into one of the 1M logs. > 7. drop the remaining 3 5M logs > 8. do another level 0 archive > 9. bring engine back online. > > Will this accomplish what I want? Am I missing something critical that > may cause something disaterous? Does anyone have any suggestion to > make this any easier or safer? Joe, you failed to answer one vital question: # # # # # # ##### # # # # # # # # # # # # # # # # # # # # ####### # ### # # # # # # # # # # # # # ## ## # # # # Monitoring 100 logs was horrendous enough. 500? YARGHH! I think we should establish a new rule of thumb on the number of logs you should have: No more than can be displayed on your screen with a single onstat -l command! I have observed that most users prefer a lower population of larger log files. Good luck! -- -- Jake (Capable of distinguishing his gluteus maximus from his proximal radioulnar articulation) +------------------------------------------------------------+ | I am inhibited by the presence of a lady. I therefore can- | | not properly express my opinion of your ancestry, personal | | habits, morals or destination. | | -- Robert A. Heinlein | +------------------------------------------------------------+

In article <36D5EB62.C9EF5F3D@garpac.com>, Jacob Salomon <jake@garpac.com> writes >you failed to answer one vital question: > ># # # # # # ##### ># # # # # # # # # ># # # # # # # # ># # # ####### # ### ># # # # # # # ># # # # # # > ## ## # # # # > Because smaller logs mean they are backed up quicker. Logs are only backup up to tape once they are full and do not contain an open transaction. Both conditions are met quicker with smaller logical logs. >Monitoring 100 logs was horrendous enough. 500? YARGHH! > >I think we should establish a new rule of thumb on the number of logs >you should have: No more than can be displayed on your screen with a >single onstat -l command! I have observed that most users prefer a >lower population of larger log files. > >Good luck! -- David Williams

Don't you think 1 megabyte logs is taking this a bit too far, though? Neil David Williams wrote in message ... >In article <36D5EB62.C9EF5F3D@garpac.com>, Jacob Salomon ><jake@garpac.com> writes > Because smaller logs mean they are backed up quicker. Logs are only > backup up to tape once they are full and do not contain an open > transaction. Both conditions are met quicker with smaller logical > logs.