IBM Data and AI Ideas Portal for Customers


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 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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


Add a new idea Subscribe
Status Not under consideration
Workspace Planning Analytics
Created by Guest
Created on Jul 30, 2024

RELATED IDEAS

Clean Dimensions after Element Deletion

When in debug logging, it was noticed that deleted elements in dimensions would throw errors on cube load.

e.g

9/2024 4:54 PM TM1.Cube Loading body for cube }StatsByRule

21116 Debug 07/29/2024 4:54 PM TM1.Cube.Loading Could not find element "Gen Security Control" in dimension "}Cubes"

21116 Debug 07/29/2024 4:54 PM TM1.Cube.Loading Could not find element "pln Personnel Input" in dimension "}Cubes"


In some dimensions this is resulting in 1000's of lines of errors on each cube that used that dimensions.

This makes the logs nuisance to use because 1000's of lines of useless errors that are not really errors. i.e. it not loading a Element that no longer exists - who cares.


So this is per Support expected behavior as the load here will not update the "missing/deleted" elements in the dimension until data is input the cube in question. This can see seen by opening the DIM file in an editor, you can see the deleted elements. they cannot be seen the dimension editor because deleted

Of course some dimension are used everywhere so you have to update each cube with a data entry so that it stops erroring in start up. Rather bothersome. Especially at the intersection of }CellSecurity cubes that are 100% rule driven.



Desired Solution: some sort of TI? command, that will "really really delete, deleted Element in all dimensions" even if it means locking the server for a few minutes, and a sort of maintenance operation.


Having such Ghost elements in dimensions is both esthetically annoying, and there's NO reason to keep them around, and it causes these debug level annoyance in Logs filling up logs with garbage.






Needed By Not sure -- Just thought it was cool
  • Guest
    Reply
    |     Aug 1, 2024

    Thanks for the response, Mr. King


    While I understand that debug logs are intentionally verbose, and that they could be filtered, the presence of what a literally "fake errors" which are not really errors, because there's hidden cruft ( long deleted elements in Dimensions somehow tagged by cube to prevent for some unknown reason) in .Dim files seems ... inelegant.


    Is the supposedly deleted data associated to those supposesedly deleted elements also stuck in some invisible cube halflife/limbo?


    Tm1 has to be "tagging" those old long- gone elements in the dimensions as "dead/do not show/do not use" in some fashion, so they are not seen in dimension editors, set editors, so why not really get rid of them.

    I have to imagine they cause overhead as they have to be processed, and reprocessed, and suppressed all the time. A couple here or there in a dimension, probably isn't a big deal, but when some dimension has thousands of ghost elements and it never goes away because one cube never has direct data entry?


    On the other had it answers a long standing mystery of why some .dim files do not appear to change size when elements are changed


    thanks for your consideration, and I understand if it;s not a huge priority, but it would be a nice behind the scenes clean up

  • Admin
    Stuart King
    Reply
    |     Aug 1, 2024

    This idea is not under consideration. The debug logs are intentionally verbose and can be filtered in modern logging services.

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.