Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367

    Unanswered: default location of commandLineTools0.log

    I noticed commandLineTools0.log gets created/updated during fixpack upgrade. This file was created in /xxx/db2/log and my instance home dir is /xxx/db2/db2inst1. /xxx/db2/log is actually where the active transaction logs get stored.

    The file contains:
    .....configuration.tool.ConfigurationTool configure
    SEVERE: IQQD0062E No token was found.


    I found that this has something to do with DB2 Text Search. Ran the following command:

    configTool printAll -configPath /xxx/db2/db2inst1/sqllib/db2tss/config


    and got:

    ...
    configPath /xxx/db2/db2inst1/sqllib/db2tss/config
    installPath /xx/db2/db2inst1/sqllib/db2tss
    logPath ./log
    tempDirPath /tmp/
    ...


    I think logPath is where commandLineTools0.log is supposed to get created by default.


    My question is why it got created in /xxx/db2/log and not /xxx/db2/db2inst1/log? Shouldn't the current directory (.) be the instance home? Anyone knows?

  2. #2
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Has anyone seen commandLineTools0.log on any DB2 servers?

    I find it on every v9.7 server (after installing a new FP).

  3. #3
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    APAR IC92979 got created for this (in case someone else finds this file).

Posting Permissions

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