Results 1 to 3 of 3
  1. #1
    Join Date
    Jan 2003
    Posts
    1,605

    Unanswered: When is "db2 TEMINATE" command really required?

    Hi,
    using db2 v10 on Linux.

    I never really know when:
    db2 TERMINATE
    is relly required command to be executed.

    From documentation: https://www-01.ibm.com/support/knowl.../r0001973.html
    Explicitly terminates the command line processor's back-end process. (...) It is recommended that TERMINATE be issued prior to executing the db2stop command.

    Another example example:
    db2 uncatalog database my_database
    DB20000I The UNCATALOG DATABASE command completed successfully.
    DB21056W Directory changes may not be effective until the directory cache is
    refreshed.
    Is it now required "db2 TERMINATE" or is this something else?

    So "db2 terminate" should be used:
    - before db2stop,
    - uncatalog (is it?),
    What else? Or how do I know I have to execute "db2 terminate" command?

    Thanks

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    There is no situation where you must run "db2 terminate". The back-end process caches the catalog, which is why when you change it by adding or removing entries, you get the message to run it. The back-end process may have a connection to a database, which is why it is recommended to terminate it before a dbtstop. What it comes down to, is you need to know what is going on with the system. When you know that, then you know when you need to run it.

    Andy

  3. #3
    Join Date
    Jul 2013
    Location
    Moscow, Russia
    Posts
    666
    Provided Answers: 55
    Sometimes we should run it.
    For example, when we want to switch to another instance (db2 commands can hang for a long time after the switching otherwise) or set another client's codepage in the same session.
    Regards,
    Mark.

Posting Permissions

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