We need to move a Windows 2003 Server running DB2 9.5 to another rack, so I'd like to shut down DB2 as gracefully as possible. This server is used by our website and receives data from Q Apply (running on another server), so it has a variety constant connections on it.
We've bounced this server before just by rebooting it, but I'm always afraid that this'll create corruption or cause other issues given DB2 wasn't gracefully stopped before the reboot. My fear though is that running just a 'db2stop' will hang given all the connections we have to the server.
So in this scenario would 'db2stop force' be sufficient or should I initiate 'db2 force applications all' and/or 'terminate' first? Also what are the differences between doing these or running 'DEACTIVATE DATABASE'? And would using 'QUIESCE DATABASE' help if it were ran in the beginning?
Thanks.
We've bounced this server before just by rebooting it, but I'm always afraid that this'll create corruption or cause other issues given DB2 wasn't gracefully stopped before the reboot. My fear though is that running just a 'db2stop' will hang given all the connections we have to the server.
So in this scenario would 'db2stop force' be sufficient or should I initiate 'db2 force applications all' and/or 'terminate' first? Also what are the differences between doing these or running 'DEACTIVATE DATABASE'? And would using 'QUIESCE DATABASE' help if it were ran in the beginning?
Thanks.