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 Oct 6, 2020

Are sparse files supported by Db2

During a Restore of sparse files - where a large file is allocated, but is not fully created physically (preparation and population of many of the underlying blocks is deferred until they are needed)

Needed by Date Nov 7, 2020
  • Guest
    Oct 22, 2020

    As db2 creates and manages datafiles, containters, tablespace as sparse files. So when we initiate db2 backup command(db2 backup db <DBNAME> online) db2backup preserves the sparseness (holes) of datafiles in backup sets. And when we do db2 restore it aggressively preserves sparseness.

    So it means if underlying file system doesn't have sparse feature, then during db2restore operation -> holes in sparse files will get converted into zeros and restore operation will take more time as compared to restoring on filesystem with sparse feature where holes are restored as holes.

    Sparse feature was introduced in NFSv4.2. However AIX neither supports NFSv4.1 or NFSv4.2

    Sparse is file system property/feature

    A sparse file is a file with empty space, or gaps, left open for future addition of data. If the empty spaces are filled with the ASCII null character and the spaces are large enough, the file will be sparse, and disk blocks will not be allocated to it. Empty space is called holes in sparse file. The information about holes is stored in metadata, if file managed by db then database manages the metadata of sparse file.

    It does not fill the empty space with zero byte blocks, When a process reads the file, those zero byte blocks get generated dynamically as opposed to being stored on physical storage. it does not store the zeros on disk, instead it holds enough data describing the zeros that will be generated

  • Guest
    Oct 21, 2020

    Do IBM db2 on AIX or LUW creates datafiles, containers as sparse files if underlying filesystem has sparse feature enabled.