LOGSIZE change not being picked up

I recently increased the size of the LOGSIZE value in my system. Over the weekend I had a chance to bounce the database (along with the system) during a hardware change. However when looking at onstat -l. it is still showing the log size being 5k pages (which is definitely not the size I picked). DYNAMIC_LOGS = 0. Thoughts? Jonathon Wyza CX & CBORD System Administrator CX Programmer/Analyst Administrative Computing Bethel College (574)-807-SQL5(7755) AIM: Iamwyza Google+ Profile<https://plus.google.com/116243338272317615360/posts>; jonathon.wyza@bethelcollege.edu<mailto:jonathon.wyza@bethelcollege.edu> =============================== SLES 11x64 & IDS 11.50.FC6 JICS 7.4.1 & Cognos 8 "Don't document the problem, fix it." - Atli Björgvin Oddsson

LOGSIZE is the default size when creating logical logs. Once the logic= al logs are created you must drop and re-create them if you want to change their si= ze. John F. Miller III STSM, Embedability Architect miller3@us.ibm.com 503-578-5645 IBM Informix Dynamic Server (IDS) (Embedded image moved to file: pic63543.gif) ids-bounces@iiug.org wrote on 10/31/2011 01:38:06 PM: > From: "Wyza, Jonathon" <wyzaj@bethelcollege.edu> > To: ids@iiug.org > Date: 10/31/2011 01:46 PM > Subject: LOGSIZE change not being picked up [25315] > Sent by: ids-bounces@iiug.org > > I recently increased the size of the LOGSIZE value in my system. Over= the > weekend I had a chance to bounce the database (along with the > system) during a > hardware change. However when looking at onstat -l. it is still showi= ng the > log size being 5k pages (which is definitely not the size I picked). > DYNAMIC_LOGS =3D 0. Thoughts?> > Jonathon Wyza > CX & CBORD System Administrator > CX Programmer/Analyst > Administrative Computing > Bethel College > (574)-807-SQL5(7755) > AIM: Iamwyza > Google+ Profile<https://plus.google.com/116243338272317615360/posts>; > jonathon.wyza@bethelcollege.edu<mailto:jonathon.wyza@bethelcollege.ed= u> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D > SLES 11x64 & IDS 11.50.FC6 > JICS 7.4.1 & Cognos 8 > > "Don't document the problem, fix it." > - Atli Bj=F6rgvin Oddsson > > > ***********************************************************************= ******** > Forum Note: Use "Reply" to post a response in the discussion forum.= >=

Jonathon, You have to create new logical logs with the new size (bigger) and drop the old ones manually using onparams. You should do it, in steps, dropping some logical logs, creating some and do it until all logical logs are as you wish. Best regards, Celso Cabral Coimbra Administrador de Banco de Dados ClearTech Ltda "Trust at the heart of Communications" Tel. (11) 3576-4509 -----Mensagem original----- De: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] Em nome de Wyza, Jonathon Enviada em: segunda-feira, 31 de outubro de 2011 18:38 Para: ids@iiug.org Assunto: LOGSIZE change not being picked up [25315] I recently increased the size of the LOGSIZE value in my system. Over the weekend I had a chance to bounce the database (along with the system) during a hardware change. However when looking at onstat -l. it is still showing the log size being 5k pages (which is definitely not the size I picked). DYNAMIC_LOGS = 0. Thoughts? Jonathon Wyza CX & CBORD System Administrator CX Programmer/Analyst Administrative Computing Bethel College (574)-807-SQL5(7755) AIM: Iamwyza Google+ Profile<https://plus.google.com/116243338272317615360/posts>; jonathon.wyza@bethelcollege.edu<mailto:jonathon.wyza@bethelcollege.edu> =============================== SLES 11x64 & IDS 11.50.FC6 JICS 7.4.1 & Cognos 8 "Don't document the problem, fix it." - Atli Björgvin Oddsson ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

The LOGSIZE parameter is simply the default value that onparams uses when you add a logical log and do not specify another size with the -s option. The only way to change the sizes of the existing logical logs is to add a new batch of logical logs using onparams -a (or the equivalent SQL Admin API function) and then drop the existing ones using onparams -d. You can do this in small batches. To drop any used logs that have not been backed up and the current log you will need to switch the current log to one of the new ones first using "onmode -l", possibly move the latest checkpoint record to one of the new logs using "onmode -c", and back up all of the used logs. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Mon, Oct 31, 2011 at 4:38 PM, Wyza, Jonathon <wyzaj@bethelcollege.edu>wrote: > I recently increased the size of the LOGSIZE value in my system. Over the > weekend I had a chance to bounce the database (along with the system) > during a > hardware change. However when looking at onstat -l. it is still showing the > log size being 5k pages (which is definitely not the size I picked). > DYNAMIC_LOGS = 0. Thoughts?> > Jonathon Wyza > CX & CBORD System Administrator > CX Programmer/Analyst > Administrative Computing > Bethel College > (574)-807-SQL5(7755) > AIM: Iamwyza > Google+ Profile<https://plus.google.com/116243338272317615360/posts>; > jonathon.wyza@bethelcollege.edu<mailto:jonathon.wyza@bethelcollege.edu> > =============================== > SLES 11x64 & IDS 11.50.FC6 > JICS 7.4.1 & Cognos 8 > > "Don't document the problem, fix it." > - Atli Björgvin Oddsson > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --90e6ba6e8ebc5165ee04b09f72c6