Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Not under consideration
Workspace Db2
Components pureScale
Created by Guest
Created on Feb 11, 2015

DB2 to support multiple network interfaces of a system in a HACMP/PowerHA cluster(RIMS)

Background of this requirement is the issue with db2nodes.cfg having IP/hostname defined different from the systems hostname, which is common definition for many customers in HACMP or PowerHA cluster. Db2nodes.cfg for the database instance gets it 'own' service address, which is moved over to the other cluster node in case of a takeover. This works pretty well during normal processing, but not for the upgrade of an instance! The upgrade process requires the nodes hostname to be stored in db2nodes.cfg. Every other IP or hostname is regarded as remote, and thus the db2iupgrade fails. Changing the db2nodes.cfg for the upgrade process is not the right way, especially if so many (several hundred) systems/instances have to be upgraded. So customer requires that DB2 supports multiple 'local' IPs/hostnames to be stored in the db2nodes.cfg. For a single partition database, every entry (there is only one!) should be regarded as local, because it has to be! Otherwise the instance could not have been used. For a DPF database the 'local' entry could be flagged, if it differs from the systems hostname. Using an alias name for the system hostname, defined in the etc/hosts file to be identical on all cluster nodes, is not an option as well, as the cluster system administration requires to have a definitions including the hosts file identical all nodes of the cluster.