how to stop all database manager processes even after db2stop
This is a discussion on how to stop all database manager processes even after db2stop within the DB2 forums, part of the Database Server Software category; --> So ... in other words, it is possible that having tried to stop the database with root instead of ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
03-20-2008, 12:46 PM
| ||||
| ||||
 Re: how to stop all database manager processes even after db2stop So ... in other words, it is possible that having tried to stop the database with root instead of the instance owner could have resulted in an "incomplete stoppage". Larry E. stefan.albert wrote: > normally "root" doesn't have the authority to do DB2 stuff - but if > root is in the SYSADM_GROUP and the environment is set correctly for > the instance (source db2profile in $INSTHOME/sqllib) it should work. > Of course the su... Knut wrote is a bit easier. > > What processes do you need? I can't give a "complete" answer for your > setup. > A FP install normally inserts the line in /etc/inittab for fault > monitor (it will be started) > db2start will start all the configured services... > The admin server (if needed) must be started seperately - afaik > > On Mar 17, 5:32 pm, zgh1970 <george.zh...@lombard.ca> wrote: > >>On Mar 17, 7:37 am, "stefan.albert" <stefan.alb...@spb.de> wrote:> slibclean and ipclean ( mentioned in the readmes ) are sometimes >> >>>needed. >>>I normally do: >>> * check for running db2 processes - and kill'em (after db2stop / >>>db2_kill) ; recheck >>> * ipcs / then ipcrm for still existing objects ; recheck >>> * slibclean >>>Of course the health / fault monitors have to be OFF... >>>A reboot is of course a goog thing - if you have your instances not in >>>autostart mode >>>and the db2fmcd is commented out in /etc/inittab >> >>Hi, Stefaan, >>Thank you for the reply. >>When we used db2stop, slibclean and fault monitors OFf. >>then we upgrade db2 instance to 64-bit. >>Will db2satrt make all process required on? >> >>Thanks > >      |
|
03-20-2008, 12:46 PM
| ||||
| ||||
| Re: how to stop all database manager processes even after db2stop On Mar 18, 5:08*am, "stefan.albert" <stefan.alb...@spb.de> wrote: > normally "root" doesn't have the authority to do DB2 stuff - but if > root is in the SYSADM_GROUP and the environment is set correctly for > the instance (source db2profile in $INSTHOME/sqllib) it should work. > Of course the su... Knut wrote is a bit easier. > > What processes do you need? I can't give a "complete" answer for your > setup. > A FP install normally inserts the line in /etc/inittab for fault > monitor (it will be started) > db2start will start all the configured services... > The admin server (if needed) must be started seperately - afaik > > On Mar 17, 5:32*pm, zgh1970 <george.zh...@lombard.ca> wrote: > > > > > On Mar 17, 7:37*am, "stefan.albert" <stefan.alb...@spb.de> wrote:> slibclean and ipclean ( mentioned in the readmes ) are sometimes > > > needed. > > > I normally do: > > > * ** check for running db2 processes - and kill'em (after db2stop / > > > db2_kill) ; recheck > > > * ** ipcs / then ipcrm for still existing objects ; recheck > > > * ** slibclean > > > Of course the health / fault monitors have to be OFF... > > > A reboot is of course a goog thing - if you have your instances not in > > > autostart mode > > > and the db2fmcd is commented out in /etc/inittab > > > Hi, Stefaan, > > Thank *you for the reply. > > When we used db2stop, slibclean and fault monitors OFf. > > then we upgrade db2 instance to 64-bit. > > Will db2satrt make all process required on? > > > Thanks- Hide quoted text - > > - Show quoted text - Hi, Stefan, I means all rpocess we stoped with db2stop, slivclean, db2licd and fault monitor before we db2iupt DB2 to 64-bit. Because we need to stop all DB2 related process. When we use db2start, will it also start db2licd and also fault monitor dameo? TThanks, |
Linear Mode
