IBM Data Platform Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. 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).
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:
Search existing ideas
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 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
Specific links you will want to bookmark for future use
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
The data volume that need to be shipped to standby is the same, just that you use the estabished connection for log records instead of going through file system or TSM.
Transferring the data as it occurs on primary is really intended as only this allows that standby starts replaying at the begin of LOAD.
LOAD copy image files need to be treated as careful as log files. Without them you are lost.
Together with ALSM the additional log space consumed is not a problem with running into active log space full situation.
Is see no problem with the additional data volume that need to get written to log path. This file system should be the fastest in the system. Just sending it to another device and doing disk IO there does not seem to be necessary.
Thanks for the idea request.
For large load jobs, I would think writing the load copy data to the logs would cause a substantial increase in the data that would need to be shipped across the network for log shipping and possibly delay other log writes from being sent over. This would also need an increase in the log space configuration because now images would be stored under logs in the log file paths, where before they could have been in some other path. Most log paths are fixed, pre-determined paths, but a load copy image could be a non-deterministic size thus putting possible disk pressure on the active log paths. This same data would then also need to be archived, which puts another increase on archive space and also could slow down the archiving model.
Shipping across load images using existing HADR communication, but just keeping it outside of the log data is also an alternative.
Thoughts on some of the points mentioned above?