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,
Post an idea
Upvote ideas that matter most to you
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.
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: http://www-01.ibm.com/support/docview.wss?uid=swg21636292 . 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.
Do not place IBM confidential, company confidential, or personal information into any field.