Re: tbinit spawned itself ??

In article 6l0@emory.mathcs.emory.edu, calvinng@technet.sg (Calvin Ng) writes: > >I recently encountered a case of tbinit (OnLine version 5.0) spawning >itself for no apparent reason. > It has been running with just two daemons (tbinit) for quite a while >like say a month. Then it spawned itself a week ago, and is running >with three ever since. Note that the engine is never shut down since >it is started. It is meant to be a 24x7 production system. >The additional daemon is not causing any problem so far, but I still need >to explain to my users why such a thing can happen?? >So, any help?? Check your online.log file for any abnormal messages that appeared when this happened. At a guess it is a tbundo process that was spawned by tbinit to rollback a transaction that could not be completed by a dying sqlturbo process. Run a tbstat -u and check the second user listed. Ordinarily it will have no stats and a pid of 0. This is kept as a spare slot in case a rollback process is required. Once spawned that slot will have a valid process id (of the spawned rollback process) and will hang around waiting to see if any more work is to be done. If this is the case the extra daemon is not a problem and can be ignored. Simon