This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 Message Tracking application is unnecessarily slow when querying for specific records in MAXINTMSGTRK.
Details:
In Message Tracking, if I search for an exact message ID, it takes 16 seconds to return a single record in a table that has 400,000 records. (Using either the list view to search for the record -or- the Find Message ID textbox in the top left corner. The result is the same either way.)
Why so slow? I believe Maximo generates the WHERE clause incorrectly. It wraps the MEAMSGID field in a function, which means the database can't utilize the index on MEAMSGID.
Screenshot: https://i.stack.imgur.com/16ZNc.png
In contrast, if I write the the WHERE clause manually, removing the UPPER() function, then it executes instantly (0.1 seconds) because the database index is being used:
meamsgid = '2765716276627860479179'
But I shouldn't need to modify Maximo's WHERE clauses to get them to run properly. The Message Tracking application should be able to construct proper WHERE clauses without my help.
Please make it so Maximo doesn't wrap MEAMSGID field in a function.
Idea priority | Medium |
Needed By | Month |
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.
Thank you submitting your idea. This looks like some issue with the idexes and we need to enhance the feature to get this fixed. This will be lined up for a future release.