Server Restart

ratheeshknair · #1 (**permalink**) 10-21-09, 01:33

Hi Experts,

Do we need to restart server regularly .

Our hosted team said they are going to reboot every 90 days as a best practice.

I've searched the web but can't find anything definitive.

Here is our Server info.

DB2 v9.5.0.808, Fix Pack 0.

Operating System Information:

OSName: WIN32_NT
Version: 5.1
Release: Service Pack 3

TIA

dr_te_z · #2 (**permalink**) 10-21-09, 05:14

No. DB2 can operate 24x7. It is not a database issue, it might be an O.S. issue and then you're asking in the wrong forum.

ratheeshknair · #3 (**permalink**) 10-21-09, 06:05

Thanks dr_te_z ,

I have not mentioned about any issues here.

What happens if restarted server at frequent intervals?

TIA

stolze · #4 (**permalink**) 10-21-09, 08:12

The point is that you shouldn't have to restart the server. Why do you think this is "best practice"? I'd call it "worst practice"...

ARWinner · #5 (**permalink**) 10-21-09, 08:22

To have to schedule rebooting the server at regular intervals is not a good thing for DB2. It is strictly for the OS, which in your case is Windows which does seem to need periodic rebooting due issues/inadequacies of the OS. When you reboot a server, all of the bufferpool and caches are lost and will have to be rebuilt. The worst thing is the package cache that has to be rebuilt and thus all dynamic SQL will need to be reoptimized and have access plans regenerated.

I have had (non-windows) DB2 servers up and running for 6 months or more without incident and without having to reboot the server. The only down time is scheduled maintenance (applying fixpacks, OS upgrades, etc).

Andy

ratheeshknair · #6 (**permalink**) 10-21-09, 08:38

Hi Stolze,

There should be some credible reason or points to prove that you are right.

DO you have any link for the same?

rahul_s80 · #7 (**permalink**) 10-21-09, 09:12

It can be a memory leak prob. with O.S. / DB2 or someother Application.

I recall we had a memory leak problem on windows with fixpak 8.2.something which was resolved after IBM provided with a fix in 8.2.something+1 release.

dr_te_z · #8 (**permalink**) 10-22-09, 03:15

If you do re-start you system from time-to-time and if you do have a maintenance window:
take some time, between O.S.boot and DB2-instance-start, to defrag your filesystem, escpecially your tablespacecontainers. I recommend "contig.exe" by sysInternals for this.
In that case DB2 also benefits.

srastescra · #9 (**permalink**) 10-22-09, 03:42

b back l8er, bro, :-)

Internet Services

Web Development

Digital Marketing

Consumer Tech