This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
The good (smart) thing about partition table is that when you take a back up you can tell BRMS to take a back up only on changed partitions.
When altering a tables partitions, the changed timestamp is changed on all partitions, not just only the ones you are altering. This is then a problem when running BRMS. It will then back up all partitions. If you have a lot of partitions and there are a lot of data on them, the back up will take a lot of time.
Can there be a add on to the altering command that says only change timestamp on affected partition?
If you have 250 partions with 1.3 Tb of data and all are changed, then it will take time.
We close and creates new partitions two times per month. This is for having performance when reading the data.
We don't have time to run a total back up on these tables every time we create a new partition on a table.
There fore we would like the altering statement to only update the change timestamp on the actual altered partition, not all of them.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
BM does not intend to provide a solution to this request at this time, so it is being closed.
We understand the difficulty these change dates cause for backup processing. However, our investigation of the design indicates a solution is very complex.
Due to the required system architectural changes that would be needed to implement this request, it is very unlikely to fit in our plan during the next 3-4 years. Therefore, we are declining it at this time.
The irony here is that there is a Last Member Change timestamp already assigned to File Members that is not used for non-Source File objects.