Customers that use INGEST to populate their tables using CLP scripts are prevented from using restartable INGEST actions in shared dtabases. The reason is that IBM does not pre-create SYSTOOLS.INGESTRESTART in shared databases, and also IBM prevents end users from calling sysproc.sysinstallobjects('INGEST','C',...) Customers are forced to use RESTART OFF option for their ingest actions. This seems too restrictive. The INGEST command does not allow to specify a user-created table in a user-owned schema for the restart-table.
|Who would benefit from this IDEA?||Any customer that wants to use restartable INGEST with a shared database.|
How should it work?
When creating a shared database, IBM please consider pre-creating SYSTOOLS.INGESTRESTART by running the relevant sysproc.sysinstallobjects stored procedure.
|Priority Justification||Alternatives: import (more slow), load client (fast) are available , so not forced to use ingest.|
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 "email@example.com" 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