Troubleshoot > Troubleshooting and Limitations – Discovery Modules > Troubleshooting and Limitations – IBM DB2 Database Discovery

Troubleshooting and Limitations – IBM DB2 Database Discovery

Troubleshooting

Problem: If the target DB2 instance port was not added to the portNumberToPortName.xml file (which means that it is not recognized as db2), the "Multiple Match" warning may appear in UCMDB UI (which means that the target CI is not reported) after running of the Host Applications by Shell job.

Solution: Add the target port to portNumbertToPortName.xml file as a db2 port entry.

Limitations

Limitation when performing DB2 Discovery without Shell Access

The DB2 platform allows specifying a network service name as a listening port for the instance. This network service name is an alias that should be resolved with an appropriate mapping file (/etc/services on Unix and %SystemRoot%\system32\drivers\etc\services on Windows) and needs shell access to get the content of this file. In the case when there is no shell access and only SQL-based access, it is not possible to expand the service name string to a port number. This causes IpServiceEndpoint to not be reported for the connected database. The only workaround for this is to use a real port number when configuring the DB2 instance instead of the service name.