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 Not under consideration
Workspace Db2
Created by Guest
Created on Jul 27, 2016

timeout option for log archiving sessions / db2vend on WINDOWS

We work with DB2 on WINDOWS and an external vendor (EMC Networker) for backups and archive logging. If network or the vendor have a problem, the archive logging forever tries to use the vendor process and in the meantime writes to a FAILARCHPATH on SAN.
Getting out of space means DB2 getting in a standstill!

On WINDOWS you can't kill the vendor process as you can do on aix or Linux. And because DB2 tries to use the log archiving session again and again there is no alternative to stopping and starting the DB2-instance (with all its databases) to heal the situation.

This is extremely undesirable as we provide a 7x24h service and all batch processing on the databases abort.

A mechanism on DB2 side should be implemented to prevent such wait situations for the log archiving sessions, e.g. implemented over a timeout option or a counter (restarting the log archive sessions after n failings).

Also see IDs 87417 and 81543.