IBM Db2 Data Management Console

nested-group-icon.png

DB2

Expand all | Collapse all

Error connecting Databases after restart DMC

  • 1.  Error connecting Databases after restart DMC

    Posted Tue September 22, 2020 11:06 AM
    Hi folks!

    I started a thread in the Data Server Manager group, but this is the wrong place.

    Here is the link to my problem:

    https://community.ibm.com/community/user/hybriddatamanagement/communities/community-home/digestviewer/viewthread?MessageKey=d24fa9dd-7502-4f1c-9663-105e6a13851e&CommunityKey=e0967b49-f3c2-42c0-9cca-a415e3896fb3&tab=digestviewer&SuccessMsg=Thank%20you%20for%20submitting%20your%20message.

    Please use this link to help me out of my problems.

    regards
    Joerg

    ------------------------------
    Jörg Burdorf
    ------------------------------


  • 2.  RE: Error connecting Databases after restart DMC

    Posted Tue September 22, 2020 05:33 PM
    Hi Jorg,

    The privilege required for monitor database is described here: https://www.ibm.com/support/knowledgecenter/en/SS5Q8A_3.1.x/com.ibm.datatools.dsweb.ots.monitor.doc/topics/mon_em_tablespaces.html

    Thanks.

    ------------------------------
    Jason Sizto
    ------------------------------



  • 3.  RE: Error connecting Databases after restart DMC

    Posted Tue September 29, 2020 02:49 AM

    Hello,

    we have the same problem after each restart of the DSM Console.

    As a workaround, it helps to reimport the connections with an existing Connection Profile.
    Otherwise a message is displayed that the version is not supported.

    The wrong error message is probably related to the fact that the version is only stored temporarily and is only determined during the import of the connection profile.

    I would prefer a solution without the described workaround.



    ------------------------------
    David Lehmeyer
    ------------------------------



  • 4.  RE: Error connecting Databases after restart DMC

    Posted Tue October 13, 2020 07:58 AM
    Hi Joerg and David,

    Thank you for bringing up this issue. We'll investigate. I created a git issue to track it: https://github.ibm.com/tools-for-aps/zh/issues/20833

    BTW: I think both you are using DMC instead of DSM, right?



    ------------------------------
    KAI DING
    ------------------------------



  • 5.  RE: Error connecting Databases after restart DMC

    Posted Tue October 13, 2020 08:20 AM

    Hi Kai,

    Yes, we use the DMC and hope that the range of functions will soon be extended by the features (reports, scheduling) of the DSM.

    According to https://bigblue.aha.io/published/7fa56b793c07e406f258866976ad051d?page=6 this is in Q4.



    ------------------------------
    David Lehmeyer
    ------------------------------



  • 6.  RE: Error connecting Databases after restart DMC

    Posted Tue October 13, 2020 08:20 AM
    Hi KAI DING!

    Yes, I use DMC. I opened the thread at the wrong board. Sorry for this confusion!
    regards
    Joerg

    ------------------------------
    Jörg Burdorf
    ------------------------------



  • 7.  RE: Error connecting Databases after restart DMC

    Posted Mon October 26, 2020 11:30 PM
    Hi Joerg and David,

    We are investigating the issue, but from your description I'm still not very clear about the issue. Could you please help to provide more details?

    1) When you say "restart console", do you mean "restart server" or just restart console? If it's "restart server", how do you start console?
    2) Are console and repo DB on the same server? Does Db2 get restarted along with console restart?
    3) The concrete operation steps you performed to reproduce the issue
    4) The screen snapshots in every step
    5) The console log files (ibm-datamgmtconsole/logs)

    Thank you for your kind help.


    ------------------------------
    KAI DING
    ------------------------------



  • 8.  RE: Error connecting Databases after restart DMC

    Posted 30 days ago
    @Jörg Burdorf I ran into what looks like the same issue. I was able to provide the development team with a sample system that was showing the behavior your described. It turns out that the Db2 Data Management Console gets confused if the Repository Database isn't available when the Console is starting up. I suspect that may be the issue your have encountered. If you restart the console all your connections should reappear. 

    In my particular system, I run the Db2 Repository database and the Data Management Console on the same Linux machine. Both are automatically started using SYSTEMCTL. When Db2 is installed, the db2fmcd.service is installed. This watchdog service makes sure that Db2 starts up and restarts in the case of a crash. However this means that Db2 starts up slower than the Console. 

    To solve this, I put a 2 minute time delay in the auto start service for the Console and everything seems to work fine now. 

    The development team is adding better messages to help identify this issue in the next update and looking for the best way to make the console more resilient to disruptions in access to the Repository database in the following release. 

    When I get a minute, I will post an example of how to automatically startup the Data Management Console as a Linux service. Let us know if this helps!

    ------------------------------
    Peter Kohlmann
    HDM Digital Technical Engagement
    IBM Canada
    kohlmann@ca.ibm.com
    ------------------------------



  • 9.  RE: Error connecting Databases after restart DMC

    Posted 30 days ago
    Hi Peter!

    We run the DMC on a Windows server and the repository database on a Linux server. The DMC is managed with the Windows Task Manager and started every day at 06:00 am and stoped at 5:15 pm. The repository database runs 24/7 with automatic maintenance. So when the dmc is started in the morning, the database is active.

    regards
    Joerg

    ------------------------------
    Jörg Burdorf
    ------------------------------



  • 10.  RE: Error connecting Databases after restart DMC

    Posted 28 days ago
    Hi Joerg,

    It seems you are hitting a different issue. Could you please help to describe more details and provide more info like:

    1) The concrete operation steps you performed to reproduce the issue
    2) The screen snapshots in every step
    3) The console log files (ibm-datamgmtconsole/logs)

    Thanks.


    ------------------------------
    KAI DING
    ------------------------------