Author Topic: How Often to Reboot?  (Read 2273 times)

jeffs42885

  • Guest
How Often to Reboot?
« on: June 10, 2014, 10:21:06 AM »
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

Michel de Kraker

  • Full Member
  • ***
  • Posts: 164
    • View Profile
    • SYSBLOX , AIX consultancy
Re: How Often to Reboot?
« Reply #1 on: July 01, 2014, 04: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.

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2231
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: How Often to Reboot?
« Reply #2 on: July 01, 2014, 05:43:37 AM »
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.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

jeffs42885

  • Guest
Re: How Often to Reboot?
« Reply #3 on: July 01, 2014, 06:27:04 AM »
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?