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.
New Database Parameter to Open Db2 for LUW Backup Files in Read-Only Mode for Deleting It
Refer to case TS005462380 for more details. Due to the rise in hackers targeting backup data files, our company has implemented Retention Lock on all backup files, including Db2 database backup files and archive log files, by changing the file permission from read/write to read-only. When the Db2 backup files or archive log files are ready to be deleted by Db2, Db2 can not delete these files, because Db2 opens the files for read/write. A database parameter to regulate this behavior would be a great enhancement to help accommodate the Retention Lock that our storage system has implemented for security reasons.
Currently, we have to delete these files using a script that executes a Linux “rm -f” command. This can be problematic and error prone, putting all backups at risk of being deleted if not done right.
As more companies implement Retention Lock on their backup files, the Read/Write restriction will become more of an issue.
Do not place IBM confidential, company confidential, or personal information into any field.