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 NEWMIRRORLOGPATH option to the restore command
This should be a fairly simple change/addition and prevent the possibilty that the mirrorlogs end up in the old databases mirrorlogpath by misstake or during the time it takes for the administrator to do the change manually, since the change will ...
db2 luw restore to avoid O_SYNC writes on the tablespace containers and perform a final fsync()
db2 luw restore performance is very slow. The problem was identified and recommended solution is to avoid O_SYNC writes on the tablespace containers and perform a final fsync() From: David Sciaraffa Date: Tuesday, February 27, 2018 at 6:57 PMTo: R...
Mainly on auditing needs when you have to get some information from the past or when you need to recover just one table only its nowadays you have to do a complete restore. Would be good to have this feature.
The RFE is to improve database integrity, backup and recovery. Db2 has a "history file" that tracks things such as backups, rollforward, log archive, etc. The history file exists in the database path (DBPATH) directory. There are two history files...
Backup Db2 to on premisses S3 API devices (ie. EMC ECS)
Backup Db2 databases to low cost object storage devices such as EMC ECS using the S3 API. The current implementation of the S3 interface only works for a small list of known S3-style endpoints. (ie....s3.amazonaws.com, softlayer.net).
This would ...
I doubt that the concept for a tablespace restore includes reading all other tablespace blocks of the backup image.For me if i restore only a tablespace which is some 10% of the whole database the restore should consider that.
Do not place IBM confidential, company confidential, or personal information into any field.