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.

Modernize dbexport/dbimport and control them from HQ

dbexport and dbimport are useful tools, very easy to use and straight forward. but as the database are growing exponentially, the tool is showing its limitations and a workaroud must be generally be  applied, which are kind of time consuming to write them.

  • Nov 2 2019
  • Needs review
Why is it useful?
Who would benefit from this IDEA? All the customers who want to easily copy databases or part of them without using CDR migrate sever
How should it work?

The idea is the following:
1) control export and import from HQ, no need to log onto the server box
2) ask from which ifmx instance the export is done, and which instance the import is done.
3) ask the name of the source database, and give possibility to give another name to the target database
4) say WHERE the unload files/External tables  will stay (HQ Server, Or SourceServer Or Target server? Copy files or create external table on one of the server?)
5) make export and import faster using INSERT INTO EXTERNAL TABLES instead of 'unload like' commands, and SELECT FROM external tables for 'load like' commands

6) at import time, use RAW tables whenever possible, then turn them to STANDARD

7) give the possibility to include or exclude a list of tables

8) give the possibility to chose to lock the source database or not (under one's responsibility)
9) make both commands (import, export and export+import) executable from the SQL Admin API


That could be a reasonable start

Idea Priority Medium
Priority Justification No that urgent, but would be handy for many customers, mainly developers
Customer Name KandooERP
Submitting Organization
Submitter Tags
  • Attach files
  • Markus Holzbauer commented
    November 14, 2019 09:26

    10) export should unload tables with parallel jobs
          (export_unload temp table with all tables to unload, each job get a table out of temp
           table to unload - and deletes it out of temp table after unload. Each job is running until
           there are no rows in temp table.)
    11) import should load tables with parallel jobs
          (import_load temp table with all tables to load, each job get a table out of temp
           table to load - and deletes it out of temp table after load. Each job is running until
           there are no rows in temp table.)
    12) import should create indexes parallel ..
    13) compressed unload via named pipe.. / uncompressed load via named pipe
    14) external table FORMAT 'INFORMIX' - is faster, but don't work with coltype

    to 6): ALTER TABLE .. TYPE (RAW) during import does only works if there are no
          indexes/constraints inside table definition. So a workaround for this problem could
         INDEX ... ; ALTER TABLE ... ADD CONSTRAINT PRIMARY KEY before export.
    to 10...12): extend sizes should be set correct to size of table/index before loading table/
         creating indexes.


  • Andreas Seifert commented
    December 19, 2019 13:30

    One more topic could be added here. When exporting, all language and codeset relevant variables should be noted in the script file, so that you don't have to speculate with which CLIENT_LOCALE, DBDATE, DBMONEY the export was created.

    dbimport should warn if the current values differ.


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