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.
Add the ability to upload Db2 transaction log files to TSM that had been moved manually by DBA
We use Db2 log archiving to TSM servers. No failover archive path has been set yet.
Under rare circumstances we faced situations where log archiving to TSM does not work or slows down and the active log path fills up. To prevent disk full situations our DBAs move inactive log files to a separate disk location. This allows Db2 to keep allocating new log files and our DBAs can address the issue that prevents successful log archiving to TSM.
Though as soon as TSM becomes available again Db2 will attempt to archive the log files that have been moved off the active log path manually. This causes Db2 to ‘forget’ about these log files as it can’t find them in the active log path.
As soon as this happens the log files in question are no longer managed by Db2. We have no option to upload them to TSM in a way that makes these log files visible to Db2 again. A manual upload using the TSM BA client causes different naming within the TSM server. In return this sequence of log files always requires manual handling in recovery situations (OVERFLOWLOGPATH).
We are looking for an option like "db2adutl upload" with the extension to allow upload of transaction log files to TSM that have been moved manually. That would enable a DBA to close a manual intervention (manual transaction log move) and make them visible to Db2s internal management again (automated log file retrieval from TSM in recovery situations).
Do not place IBM confidential, company confidential, or personal information into any field.