This portal is to open public enhancement requests against products and services offered by the IBM Data & AI 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 updateson 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
R2PRO00006892 - include a matching timestamp for a given activity record in all the tables
Farmers currently retains 4+1 rolling months of WLM activity data involving the following WLM tables, and we would like to add a 'date' column having a default valude current timestamp in these 3 tables:
- ACTIVITYMETRICS_DB2ACTIVITIES_V97 (Note: No date column)
I would like to get your expert opinion to know if there can be any issue with adding this new column to the 3 WLM tables in the Audit Schema.
Maintenance is handled by a manual process that we would like to automate using range partitioned tables. But since the IBM-supplied WLM tables are not range partitioned, and one of the tables doesn't even have a date column, it has been challenging to implement a workable solution. Would any of these be acceptable (from an IBM standpoint)?
We will add a new column using the following command:
- ALTER ADD a YYYYMM column to each of the 3 WLM tables listed above.
Do not place IBM confidential, company confidential, or personal information into any field.