IBM Data & AI

 Welcome to the IBM Data & AI Ideas Portal for Clients! 

We welcome and appreciate your feedback on IBM Data & AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal.  If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback  and suggestions you have for improving our offerings / products!  This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.
  • If you have not registered on this portal please click on the following link and register.  To complete registration you will need to open the email you will receive from Aha to confirm your identity.
Additional Information:
  • The shorter URL for this site is:
  • To view our roadmaps:
  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases
  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

HPL jobs freeze when changing index setting

Problem description and business impact
When HPL is used to load a table with indexes, it does a set indexes
filtering before the loading of the table and does a set indexes enable
after the loading. If I have 1000 tables to load, what I would rather
happened is that it does all the set indexes filtering before the
loading of any table and the set indexes enable only after all the
tables have been loaded, since it needs to flush all the pending writes
before it can flip the index mode. As I was running multiple streams of
load, it paused the other streams every time the index modes are

The way I am doing the HPL load is different from table to table. For
most of the tables, I leave the indexes there. However, for one of the
table, I delete its index and recreate them after the whole table is
loaded, because for the other tables, the delay created by have the
indexes build concurrently as the records are added is insignificant,
while for this one, it slows down the load very significantly.

I prefer to leave the indexes there if all possible, while the table is
being loaded.

Is there an option to run the HPL load jobs this way or at least
suppress the changing of the index mode, since, I can always manually
run all the set indexes filtering DDLs before the jobs and all the set
indexes enable DDLs after they are all completed.
  • Guest
  • Dec 24 2018
  • Needs review
Why is it useful?
Who would benefit from this IDEA?
How should it work?
Idea Priority High
Priority Justification
Customer Name ECOMM
Submitting Organization
Submitter Tags
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions