Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

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.

Status Delivered
Workspace PowerVC
Created by Guest
Created on May 30, 2016

PowerVC installation issues

When installing PowerVC the customer found several issues:

1. user/group check
In the prereq script ($INSTALL_DIR/lib/ line 355 following) there is hard coded information for user IDs and groups which is not customizable and causes the install script to fail if the numeric IDs are in use.
Reason: installer tries to create users (and groups!) with fixed numeric IDs.
The customer has a company-wide user- and group ID policy based on AD that is not changeable by the local client.

2. DB2 install setting "noexec"
DB2 installation checks for the „noexec“ attribute of a mounted /tmp directory, but not very specific. Since within the customer image there is also a /var/tmp directory with the „noexec“ attribute the simple check fails even if /tmp is executable.

3. DB2 fixed directory for installation (/home/powervcdb)
DB2 installation requires a fixed user („powervcdb“) and a fixed directory for installation (/home/powervcdb); it is not possible to customize these values.
The customer uses with its standard image an automount solution for users. This results in an installer failure since /home is solely as user mountpoint and the installer checks for space in /home as well as trying to create a directory /home/ibm (to check write access for /home/powervcdb creation?)

Idea priority High
  • Guest
    Jan 25, 2017

    These concerns are primarily addressed by virtue of PowerVC switching from DB2 to MariaDB for its OpenStack database to better align with the open source community.

  • Guest
    May 31, 2016

    Creating a new RFE based on Community RFE #89182 in product PowerVC.