Db2

dmctop - unexpected behavior when connecting to a remote instance/database

  • 1.  dmctop - unexpected behavior when connecting to a remote instance/database

    Posted Mon June 29, 2020 10:29 AM
    Last Friday, I downloaded and tried dmctop.  So far, so good, but I've noticed an interesting/unexpected behavior. 
    This was observed when trying to connect to a remote instance by specifying:
    • the -d, -n and -r options and 
    • if either one - or both - of the -u and -p options are left out

    In the above case, dmctop connects to the local database specified by -d option, if a database with the matching name exists on the local instance, of course.

    An example of this scenario could be a HADR cluster.  Say database primary replica is on node B, but user session is on node A.  If user tries to connect dmctop to HADR primary replica on node B, and executes dmctop -d dbname -r nodeB -n port_no without specifying either the -u or -p (or both) parameters, dmctop attempts to connect to the dbname on node A, which is HADR standby.  

    I think the expectation would be to have dmctop either:
    1. Query for credentials (or the missing credential component), or
    2. Fail


    ------------------------------
    Luke Numrych
    ------------------------------

    #Db2