IAYAA0005E The node is already cataloged with different settings. It is necessary to uncatalog it.

Explanation

When a Db2 for LUW project is created, a node is being cataloged in the Db2 client with the details of the database server that is used for the related project (host, port, SSL settings).

If a node with the same name has already been cataloged with different settings (either by an independent user action or by the creation of another project that uses the same database server), the node cannot be cataloged with the new settings.

As a consequence, the creation of the project will use the old database server settings of the node, which might not be valid anymore.

System action

IBM® AD Build Client will not be able to create the database for the project using the desired database server settings. The project creation process is canceled.

User response

  1. Check the cataloged node settings in the Db2 client command line, by running the following command:
    db2 list node directory
  2. In the results list, identify the node corresponding to the database server that you want to use when creating the project.
  3. If the settings do not match with the latest settings for that database server, uncatalog the node from the Db2 client command line, by running the following command:
    db2 uncatalog node %nodeName%
    Where %nodeName% represents the actual name of the node.
  4. To make sure that the uncatalog command is effective immediately, run the following command:
    db2 terminate
  5. After the node has been uncatalogued, try to re-create the project.