onparams -p -s

Hola, les cuento que tenemos instalado informix 9.21 en un servidor con windows server 2003, el problema es que no levanta el servicio "Informix IDS 2000 - ol_produccion ", pero si levanta con oninit -v, el log lo que indica es lo siguiente: WARNING! Physical Log size 2000 is too small. Physical Log overflows may occur during peak activity. Recommended minimum Physical Log size is 20 times maximum concurrent user threads. asi que lo que hice fue ejecutar "onparams -p -s 15360" pero hace 20 horas que esta en la fase: Recovering, please wait ... Esto no debe ser normal, porque puede ocurrir? sera que se estropeo el rootdbs? Puedo reiniciar el servicio? que hago? Desde ya Gracias! Laura

Though I don't understand the language, I am going to guess about what the problems is. The command onparams should be executed while in quiescent mode; in fact, the system should not allow you to execute it when you are not in that mode. When the command itself is executed, it should attempt to recycle the instance down and backup up again, in a matter of seconds. I am guessing that horas is hours ... and that is WAY TOO LONG. Are you able to take a look at the MESSAGE LOG to see if the process has actually completed but the communication of this fact was not displayed? Was this change noted in the $ONCONFIG file? Since you are attempting to bring up the instance for the first time, you might want to simply modify the $ONCONFIG to the size you are wanting to use and perform a oninit -i to re-initialize your new instance. Take care. Clifton -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of LAURA LURBé Sent: Tuesday, November 14, 2006 9:05 AM To: ids@iiug.org Subject: onparams -p -s [7810] Hola, les cuento que tenemos instalado informix 9.21 en un servidor con windows server 2003, el problema es que no levanta el servicio "Informix IDS 2000 - ol_produccion ", pero si levanta con oninit -v, el log lo que indica es lo siguiente: WARNING! Physical Log size 2000 is too small. Physical Log overflows may occur during peak activity. Recommended minimum Physical Log size is 20 times maximum concurrent user threads. asi que lo que hice fue ejecutar "onparams -p -s 15360" pero hace 20 horas que esta en la fase: Recovering, please wait ... Esto no debe ser normal, porque puede ocurrir? sera que se estropeo el rootdbs? Puedo reiniciar el servicio? que hago? Desde ya Gracias! Laura **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum.