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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - 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

Status Not under consideration
Workspace Db2
Created by Guest
Created on May 4, 2017

Allow offline backup to automatically force all Allow offline utilities such as backup, restore, rollforward to auconnections

Modern enterprise applications are often using connection pooling for database access. Connection pools are usually monitored by application servers, and dead connections are reestablished with minimal delays.
For offline backup operations, this leads to the need to shut down application (or at least to terminate the connection pool component) in order to reliably perform the backup. The reasons for that are explained in the following technote:
The suggested workarounds are all instance-level (e.g. restarting instance in restricted mode or disabling TCPIP communications), and, therefore, have some drawbacks in cases when the single instance hosts multiple databases.
As application servers have their own management tools and are usually running remotely from DB2, it is not very simple/feasible to integrate the required application management procedures (stopping the application or the connection pool) with DB2 automated backup operations.
A better approach would be to add the new option to the (offline) DB2 backup command, which would disallow new connections to the database, force all existing connections and deactivate the database before starting the backup.
The possible syntax: BACKUP DB name FORCE OFFLINE, where FORCE OFFLINE could be specified where ONLINE keyword is currently allowed (of cause, ONLINE and FORCE OFFLINE are incompatible options).
Automatic backup, enabled by setting AUTO_BACKUP=ON, should use this new BACKUP option in order to achieve 100% reliable backups, without ever hitting SQL1035N.