The message just logs the fact that the operation occurred; it's not
necessarily a problem. Any particular reason you were concerned about
db2start happening at the reported times?
Regards,
- Steve P.
--
Steve Pearson, DB2 for Linux, UNIX, and Windows, IBM Software Group
DB2 "Portland" Development Team, IBM Beaverton Lab, Beaverton, OR, USA
aj - 17 Jan 2007 00:27 GMT
Thanks for the reply Steve.
Why is a db2start occurring when a db2stop did not /first/ occur? The
instance is online both before and after this message appears.
I am /not/ issuing a db2stop or a db2start... ??????
Might this have something to do w/ fmcd?
aj
> The message just logs the fact that the operation occurred; it's not
> necessarily a problem. Any particular reason you were concerned about
[quoted text clipped - 5 lines]
> Steve Pearson, DB2 for Linux, UNIX, and Windows, IBM Software Group
> DB2 "Portland" Development Team, IBM Beaverton Lab, Beaverton, OR, USA