Topic
2 replies Latest Post - ‏2013-11-25T09:22:22Z by MJCadman
MJCadman
MJCadman
2 Posts
ACCEPTED ANSWER

Pinned topic Data Studio 4.1 bad instance name

‏2013-11-20T23:57:12Z |

Running Data Studio 4.1 on Linux 64 and DB2 v9.7.

The instance name that DS identifies is completely wrong (it should be db2inst1) - it is 18446744073709551615 (which is 2^64 -1) - see pic.

This obviously messes up any comms. Any clues as to where it getting this value from?

DB2 control center does not suffer from this issue.

 

Attachments

Updated on 2013-11-21T00:14:31Z at 2013-11-21T00:14:31Z by MJCadman
  • Sean WANG
    Sean WANG
    7 Posts
    ACCEPTED ANSWER

    Re: Data Studio 4.1 bad instance name

    ‏2013-11-25T05:35:09Z  in response to MJCadman

    Hi MJCadman,

    Actually, we can not see the image you mentioned. Do you mind upload the image again?

    Would you please also provide these information that we could take a deeper investigation?

    1. Run the SQL to see what the actual result in the console

       SELECT INST_NAME FROM TABLE(SYSPROC.ENV_GET_INST_INFO()) as INST_INFO

    2. The log file or error screenshot

    3. The output of "db2pd -fmp" in the console.

     

    Regards,

    Sean

    • MJCadman
      MJCadman
      2 Posts
      ACCEPTED ANSWER

      Re: Data Studio 4.1 bad instance name

      ‏2013-11-25T09:22:22Z  in response to Sean WANG

      1.  SELECT INST_NAME FROM TABLE(SYSPROC.ENV_GET_INST_INFO()) as INST_INFO

      db2inst1

      2. I have attached this again - seems to have worked this time.

      3. Attached.

       

      Attachments

      Updated on 2013-11-25T09:23:21Z at 2013-11-25T09:23:21Z by MJCadman