OnDemand Users Group

Support Forums => CMOD for Multiplatforms => Topic started by: jeffs42885 on June 10, 2014, 05:21:06 PM

Title: How Often to Reboot?
Post by: jeffs42885 on June 10, 2014, 05:21:06 PM
In my prior assignment, we rebooted our DEV/QA environments once per month, and our BCP/PROD environments staggered every 60 days--aka Jan prod, feb bcp, and so on. The only exception to this is if there is something that would require a reboot (AIX change, TSM change, DB2 change).

How often do you all reboot your boxes? Mostly aimed towards AIX/Linux folks
Title: Re: How Often to Reboot?
Post by: Michel de Kraker on July 01, 2014, 11:52:41 AM
Hi Jeff

In my opinion it is a waste of time to reboot an AIX server especially with a DB2 database running on it. DB2 is maintaining the buffer cache and this caching becomes more efficient the longer db2 stays active. In my environment we only do reboots after applying OS or DB2 updates.

regards,

Michel.
Title: Re: How Often to Reboot?
Post by: Justin Derrick on July 01, 2014, 12:43:37 PM
I've seen everything from weekly reboots for all systems to hasn't-been-rebooted-since-the-last-power-outage (3+ years).

If your company has a policy on reboots, follow it.  It's not going to hurt CMOD in the long term, and it's a good test to ensure that shutdown and startup scripts are working properly.

-JD.
Title: Re: How Often to Reboot?
Post by: jeffs42885 on July 01, 2014, 01:27:04 PM
I guess something was really really messed up in my prior gig then, because we were CONSTANTLY rebooting, not just to support DB2/AIX upgrades. There was some issues where CMOD just wouldn't load files, run out of memory, etc. The fix was always "Reboot" the box.

I am working in a new environment that is much smaller running redhat and oracle, a shared library/object server and a remote oracle server. So is it safe to assume that the CMOD server, it doesn't matter how often it gets rebooted, just the oracle server..which would require coordination in stopping ARSSOCKD?