Why CA Database Command Center is not able to discover my DB2 server?

Document ID : KB000054462
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

I installed DB2 client on my UDCC machine (CA Database Command Center) and I am able to connect successfully to my remote database server machines. I get the following error in the UDCC using the method of searching the network. What is the cause of this error?

[DBM_ERROR_DISCOVERY_NO_SERVER] Discovery returned no servers. All servers may already be managed and can be found using the Server Management tool.

Solution:

There are a couple of reasons why this error can occur (please note: the DB2 client does need to be configured):-

  1. If a DB2 client is installed after CA Database Command Center was initially installed. To resolve, simply reinstall CA Database Command Center (only that component).

  2. The following items will also produce this problem. This information is outlined in the readme for version 11.2.2

Knowledge Agents for DB2 for Linux, UNIX and Windows

Prior to running any Insight Knowledge Agent configuration for DB2 for Linux, UNIX and Windows, establish your run-time environment for UNIX by sourcing db2profile from the home directory of the DB2 instance owner:

<insthome>/sqllib/db2profile

After sourcing db2profile, execute the following command to ensure INSTHOME is available to the run-time environment:

export INSTHOME

Recycle the Job Administration Service (JAS) if it was already running prior to performing these steps. Execute udmstop followed by udmstart.

DB2 for Linux, UNIX and Windows

You may encounter the following issues specific to DB2 for Linux, UNIX and Windows:

  • Unicenter DCC fails to discover DB2 for Linux, UNIX and Windows instances due to a problem with TCP/IP. Before running auto discovery, perform the following steps using the IBM DB2 Control Center to set communications options:

    1. From the Start Menu, select IBM DB2, Control Center.

    2. On the Control Center window, expand the nodes of the explorer tree to show the instance you want.

    3. Right-click the instance and select Setup communications from the pop-up menu.

    4. With the TCP/IP option selected, click the associated Properties button.

    5. From the Configure TCP/IP - DB2 dialog, click Default to populate the Service Name and Port Number fields.

    6. Click OK to exit the dialogs.

    7. Restart the instance.

  • The connect operation fails to retrieve port information required for alias cataloging if you are not logged in as db2admin.

    If you are using LDAP support, regardless of the implementation, ensure that you or the DB2 Connect gateway can perform the CATALOG DATABASE, NODE, and DCS DATABASE commands. Invoke the following command at the client or gateway to correct the problem:
    UPDATE DBM CFG USING CATALOG_NOAUTH YES
  • When connecting to a local instance of DB2 for Linux, UNIX and Windows, the DB2INSTANCE environment variable must be set to the name of the local instance. If this is not done, you will not be able to connect or Unicenter DCC may terminate abruptly.