Results 1 to 2 of 2
  1. #1
    Join Date
    Oct 2013
    Location
    Toronto, Canada
    Posts
    23

    Question Unanswered: db2stop force timmed out

    Regarding db2v105 - Could someone please explain in detail what goes on behind the scenes with db2 when db2stop force is running, and how many stages it has (by studying db2diag.log and its messages)..?
    Is it ok if 'db2stop force' times out, if not, which files should we look at for more information on the problem (stacktrace, db2diag.log)?
    do you know where I can find good diagrams related to that? Unfortunately there isn't much on the web (google)...

    Note: I've already read the IC equivalent of db2stop force unfortunately it doesn't have detailed info, just the 'basics' ..

    $ db2stop force
    02/04/2014 12:38:36 10 0 SQL6037N START or STOP DATABASE MANAGER timeout value was reached.
    02/04/2014 12:38:37 20 0 SQL6037N START or STOP DATABASE MANAGER timeout value was reached.
    02/04/2014 12:38:54 30 0 SQL6081N A communication error caused a DB2STOP FORCE command to time out on this node.
    02/04/2014 12:38:54 40 0 SQL6081N A communication error caused a DB2STOP FORCE command to time out on this node.
    SQL6081N A communication error caused a DB2STOP FORCE command to time out on this node.

  2. #2
    Join Date
    May 2005
    Posts
    29
    db2stop force will try to terminate all your connections and shutdown DB2. From your messages, it appears DB2 wasn't able to do that within the Timeout interval.

    Have to go with db2_kill option, which is un-graceful way to shutdown

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •