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 Nov 24, 2017

Truncate incompatible with online backup command

Db2 online backup for warehouse environments running longer depending on database size, online backup command have a lock incompatibility with Truncate table command which is says backup is not fully online. This should be one essential feature that we need to have for next releases of Db2
  • Guest
    Oct 13, 2021

    Hi Michael,

    The link already provided, contains this paragraph, which suggests to me that Backup should not have an issue when TRUNCATE affects DMS tablespace only. But to TRUNCATE has an issue with OLB lock and doesn't give ANY indication, that it simply waiting for backup to complete:


    For SMS (System Managed Space), the TRUNCATE statement is not compatible with online backup because it gets a Z lock on the table and prevents an online backup from running concurrently.

    TRUNCATE will not progress if an online backup is active, as the online backup utility will hold an online back up (OLB) lock which is not compatible with TRUNCATE. In this case, the TRUNCATE will not timeout, regardless of the system defined timeout value. TRUNCATE will wait until the online backup is completed and before starting.

    In Datawarehouse/Datamart DBs, we often use TRUNCATE as part of the ETL processing, and yes, normally backup should NOT run while ETL processing is done. But if backup somehow runs much longer than expected, ETL processing simply 'hangs', which is not that smart. It better should provide a message telling that TRUNCATE can't continue while BACKUP is still running.

    Regards Torsten

  • Guest
    Oct 13, 2021

    At this point, the facts are described in the current documentation

  • Admin
    Michael Roecken
    Oct 13, 2021
    According to documentation, backup has a LOCK incompatibility with truncate only, when truncate affects a table residing in SMS tablespace.

    Can you please provide the link to the documentation you are referring too? Thanks.

  • Guest
    Oct 11, 2021

    According to documentation, backup has a LOCK incompatibility with truncate only, when truncate affects a table residing in SMS tablespace. Thus TRUNCATE of data in DMS or AS Tablespaces should NOT wait until backup completes, at least it should not do so w/o giving an notification that truncate waits for backup to complete!