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

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace Db2
Created by Guest
Created on Jan 6, 2021

DB2_DMU_DEFAULT=IMPLICITLYHIDDENMISSING, if set at instance level then we should not need it to be specified again in import command just like 9.7 clients

We are facing an issue for version 11.1. FP5 where we are able to load the data into a table with a column in a table which has IMPLICITLY HIDDEN column, In the past we were able to run the import and not specified the column name and it has worked. With new version, it should work as db2profile registry is set as below .


Informational tokens are "DB2 v11.1.4.5", "special_40265",
"DYN1911120100AMD64_40265", and Fix Pack "5

I tried to do some testing around this and able to run the import without any column names locally without any issues. While testing we found that if they use db2 client version 9.7 it works, however with higher versions like it doesn’t work

with client we get issue below
SQL2437N The data movement command failed because the utility was unable to
resolve how implicitly hidden columns should be processed. No data was moved.

Reason for RFE :: client behaviour has changed from 9.7 onwards, even IBM was able to reproduce the problem in 10.1, 10.5, 11.1

It is not forward compatible and doesn't work in newer versions. As this worked in 9.7 it should work for other versions as well

FIX was ::

db2set DB2_DMU_DEFAULT=IMPLICITLYHIDDENMISSING" on the client side or adding the import command : modified by implicitlyhiddenmissing.

ideally like 9.7clients , server side registry should be honoured

When it is set on server, why it is relying on what is on client. This is clearly a BUG. something which was working 9.7 and stopped working after that.

Needed by Date Mar 1, 2021