Re: My engine goes to quiescent mode

I'm not quite sure how to interpret your problem, but I'll try. When you report a server version, please give the full version number, such as 7.30.UC1 or 7.31.UD7 - there's a difference of about 5 years between those releases, so it matters quite a lot. Why does (did) your system go into quiescent mode? Was there a cron job making it do so? Why did you want to make it quiescent if that was intentional? Did the online log file contain any information about why it switched to quiescent mode? Why do you think you need to reboot your IDS daily? It should run for months at a time without interruption, subject to power supplies and servers staying up for months at a time. Is cron still working? What changed when things started to go wrong? This is always a good question - if something was working and stops working, what changed? I'm really not clear what your problem is - if the questions above don't suggest a solution, please restate your problem more clearly. (I do recognize that English is probably not your primary language - and I sympathize with the difficulty of explaining what is happening in a foreign language. So, please do your best.) For example: * Until about 3 weeks ago, I had a cron job for user 'root' scheduled at 01:00 each day which took my IDS 7.31.UD5 server running on Solaris 7 from online mode to quiescent mode, and then restored it to online mode. * This was to give the DBMS a rest during the night. * Since about 3 weeks ago, this process stopped working; the online log file shows that it does not go quiescent any more. * Any ideas what I changed on my system to prevent cron jobs from working? -- Jonathan Leffler (jleffler@us.ibm.com) STSM, Informix Database Engineering, IBM Data Management 4100 Bohannon Drive, Menlo Park, CA 94025 Tel: +1 650-926-6921 Tie-Line: 630-6921 "I don't suffer from insanity; I enjoy every minute of it!" forum.subscriber@iiug.org wrote on 05/20/2004 09:09:46 PM: > A few weeks ago and until now my instance always go to quiescent mode.. > I had check the online.log file and found that my instance did not > going on the right directions...before this problem happen i had > make scheduled that everyday at 1.00 am it will reboot using > crontab...For your information the informix version is IDS 7.3 > running on solaris 7. > > any response from my question i like to say thank you very much >

I have some Solaris 7 boxes running IDS that have been running well over a year without reboots/restarts. The Solaris SA in me says to avoid rebooting Suns. -----Original Message----- From: Jonathan Le.... [mailto:jleffler@us.ibm.com] Sent: Friday, May 21, 2004 10:38 AM To: ids@iiug.org Subject: Re: My engine goes to quiescent mode [3003] I'm not quite sure how to interpret your problem, but I'll try. When you report a server version, please give the full version number, such as 7.30.UC1 or 7.31.UD7 - there's a difference of about 5 years between those releases, so it matters quite a lot. Why does (did) your system go into quiescent mode? Was there a cron job making it do so? Why did you want to make it quiescent if that was intentional? Did the online log file contain any information about why it switched to quiescent mode? Why do you think you need to reboot your IDS daily? It should run for months at a time without interruption, subject to power supplies and servers staying up for months at a time. Is cron still working? What changed when things started to go wrong? This is always a good question - if something was working and stops working, what changed? I'm really not clear what your problem is - if the questions above don't suggest a solution, please restate your problem more clearly. (I do recognize that English is probably not your primary language - and I sympathize with the difficulty of explaining what is happening in a foreign language. So, please do your best.) For example: * Until about 3 weeks ago, I had a cron job for user 'root' scheduled at 01:00 each day which took my IDS 7.31.UD5 server running on Solaris 7 from online mode to quiescent mode, and then restored it to online mode. * This was to give the DBMS a rest during the night. * Since about 3 weeks ago, this process stopped working; the online log file shows that it does not go quiescent any more. * Any ideas what I changed on my system to prevent cron jobs from working? -- Jonathan Leffler (jleffler@us.ibm.com) STSM, Informix Database Engineering, IBM Data Management 4100 Bohannon Drive, Menlo Park, CA 94025 Tel: +1 650-926-6921 Tie-Line: 630-6921 "I don't suffer from insanity; I enjoy every minute of it!" forum.subscriber@iiug.org wrote on 05/20/2004 09:09:46 PM: > A few weeks ago and until now my instance always go to quiescent mode.. > I had check the online.log file and found that my instance did not > going on the right directions...before this problem happen i had > make scheduled that everyday at 1.00 am it will reboot using > crontab...For your information the informix version is IDS 7.3 > running on solaris 7. > > any response from my question i like to say thank you very much >

Don't fix it unless its broken !!! Now having said that I think either you or some one in your company seems to have messed with the unix script that perform this IDS operation. Create a new unix script to do the work or trouble shoot your sripts to see where the problem is. Also, if it allows then reboot the sun machine, just to start with. Hope this helps. Ravi. "Gentsch, Sam" <Sam.Gentsch@polycom.com> wrote: I have some Solaris 7 boxes running IDS that have been running well over a year without reboots/restarts. The Solaris SA in me says to avoid rebooting Suns. -----Original Message----- From: Jonathan Le.... [mailto:jleffler@us.ibm.com] Sent: Friday, May 21, 2004 10:38 AM To: ids@iiug.org Subject: Re: My engine goes to quiescent mode [3003] I'm not quite sure how to interpret your problem, but I'll try. When you report a server version, please give the full version number, such as 7.30.UC1 or 7.31.UD7 - there's a difference of about 5 years between those releases, so it matters quite a lot. Why does (did) your system go into quiescent mode? Was there a cron job making it do so? Why did you want to make it quiescent if that was intentional? Did the online log file contain any information about why it switched to quiescent mode? Why do you think you need to reboot your IDS daily? It should run for months at a time without interruption, subject to power supplies and servers staying up for months at a time. Is cron still working? What changed when things started to go wrong? This is always a good question - if something was working and stops working, what changed? I'm really not clear what your problem is - if the questions above don't suggest a solution, please restate your problem more clearly. (I do recognize that English is probably not your primary language - and I sympathize with the difficulty of explaining what is happening in a foreign language. So, please do your best.) For example: * Until about 3 weeks ago, I had a cron job for user 'root' scheduled at 01:00 each day which took my IDS 7.31.UD5 server running on Solaris 7 from online mode to quiescent mode, and then restored it to online mode. * This was to give the DBMS a rest during the night. * Since about 3 weeks ago, this process stopped working; the online log file shows that it does not go quiescent any more. * Any ideas what I changed on my system to prevent cron jobs from working? -- Jonathan Leffler (jleffler@us.ibm.com) STSM, Informix Database Engineering, IBM Data Management 4100 Bohannon Drive, Menlo Park, CA 94025 Tel: +1 650-926-6921 Tie-Line: 630-6921 "I don't suffer from insanity; I enjoy every minute of it!" forum.subscriber@iiug.org wrote on 05/20/2004 09:09:46 PM: > A few weeks ago and until now my instance always go to quiescent mode.. > I had check the online.log file and found that my instance did not > going on the right directions...before this problem happen i had > make scheduled that everyday at 1.00 am it will reboot using > crontab...For your information the informix version is IDS 7.3 > running on solaris 7. > > any response from my question i like to say thank you very much > --------------------------------- Do you Yahoo!? Yahoo! Domains - Claim yours for only $14.70/year