Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Workspace Db2
Created by Guest
Created on Aug 4, 2017

DB2 LUW: Intra-tablespace parallelism

Db2 V9.7 FP2: Intra-tablespace parallelism can reduce elapsed time for backups

Starting in Version 9.7 Fix Pack 2, intra-tablespace parallelism was introduced and can be used during backups other than delta and incremental backups. Intra-tablespace parallelism can reduce the time needed for a backup operation by allowing multiple threads to read the same table space in parallel during the whole backup operation.

When you use intra-tablespace parallelism, the table spaces are split into mutually exclusive page ranges. You enable and tune intra-tablespace parallelism using the Db2_ITP_LEVEL registry variable.

The environments that benefit the most from this enhancement are the ones in which the sizes of table spaces vary widely.

DB2_ITP_LEVEL

Operating system: All

Default: 0, Values: 0 - 64

This variable enables intra-tablespace parallelism, which provides additional parallel reading of data in a database-managed space (DMS) or automatic storage table space during backups other than incremental and delta backups. Intra-tablespace parallelism can reduce the time needed for online and offline backups. This variable is available in Version 9.7 Fix Pack 2 and later fix packs.

If you use the default setting (0), intra-tablespace parallelism is not enabled and each table space is assigned a single Db2 thread during backups. Use a setting of 0 to maintain the same behavior as in previous releases.

When intra-tablespace parallelism is enabled, the database manager splits the table spaces into ranges so that multiple Db2 threads can read concurrently each table space, as follows:

If you specify a value of 1, the database manager uses the table space information to determine the range size and the number of ranges to be read in parallel.

If you specify a value of 2 - 64, the database manager uses the table space information to determine a range size, but that size is divided by the value of the variable to determine the final range size.

This variable has no effect on SMS table spaces.

  • Guest
    Reply
    |
    Jul 9, 2020

    some tables are very large where they reside in one table space and parallelism on backup will not help on this skewed senario

  • Guest
    Reply
    |
    Jul 9, 2020

    An example of why this is needed: https://www.reddit.com/r/DB2/comments/ho137z/db2_backup_taking_too_long/

    Most vendors (even IBM) can be bad at physical database design and restrict a DBA from making changes.