Member Avatar for Member #188101

I don't know if this is the right section, so please correct me if I am wrong.

I am using DB2 Monitor from SNIP, a very useful tool. Recently we upgraded from DB2 for LUW 9.1.2 to 9.1.8. Since then I get this error "No cataloged db information found!" when trying to open the application.

When I issue "db2 list db directory" I get a lot of cataloged databases.

Any ideas?

Thanks in advance,

Ferdinand

Edited by happygeek because: link snipped
  • 2 Contributors
  • 2 Replies
  • 194 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by Member #188101

Dani AI

Generated

Short summary and practical checklist based on what discovered: that error usually means the monitoring tool is running against a DB2 home that has no server-side database directory (for example, a client-only installation). Uninstalling the DB2 Client fixed the problem in this case because it removed the conflicting DB2 home; the monitor then used the server installation that actually contains the cataloged databases.

Quick verification steps to try before uninstalling anything:

  • Confirm which DB2 home/instance the monitor process uses (on Unix-like systems check which DB2 binary is first in PATH and the active instance; on Windows check PATH order or launch the DB2 Command Window supplied by the server home).
  • Make sure the server’s DB2 profile/sqllib is being sourced for the user that runs the monitor so environment variables (DB2INSTANCE, DB2HOME, library paths) point to the server installation.
  • If the monitor has a configuration option for DB2 home or command path, point that to the server installation instead of the client.

Remediation options (choose one appropriate for your environment):

  • Remove the redundant client (what solved it here).
  • Keep both but adjust PATH/environment so the server home is used when starting the monitor.
  • Configure the monitor explicitly to use the server DB2 home or start it from a server DB2 Command Window.
  • If other applications require the client, create separate startup scripts or service definitions so each app gets the correct DB2 environment.

Notes and caution: changing/removing DB2 software can affect other apps that rely on a client. Prefer adjusting the environment or monitor settings when possible. If problems remain, check the monitor’s logs for which DB2 home it detects and confirm the server installation’s catalog is intact. Thanks to for the moderation tip earlier.

Recommended Answers

All 2 Replies

Member Avatar for peter_budo

This should be moved to IT Professionals' Lounge for time being as this is best place at the moment.

PS: I would like to see this in Databases section, but not possible. If you would like to see it also there add your opinion here

Edited by peter_budo because: typo
Member Avatar for Member #188101

I got it. I had DB2 Server and DB2 Client installed. After uninstalling DB2 Client it works fine.

Thanks to you all.


Ferdinand

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.