Troubleshooting data issues is really difficult. I've seen bugs related to concurrency (IE User A doing something while User B is doing something), related to order of operations (setting fields in order A causes an issue but order B works as expected), etc. For data loads using the persistent or non-persistent field when you need to use the other, changing the alternate index on the object structure, etc. I know that's not extremely helpful, but I'm not aware of a bug in this area so I can't quite help explain why it's happening.
Can you confirm that the hierarchy entries are 100% identical? IE same system, same location, same parent, and same site, including case (IE all uppercase)? The reason I ask is there should be a unique index on the database (LOCHIERARCHY_NDX1) that would prevent a duplicate entry. If this is in place, that shouldn't be possible. If you're on a case sensitive platform (Oracle/DB2), you may have data that is slightly different format (IE Site1 and SITE1) that would be allowed via the database but Maximo might retrieve as a duplicate. If you're seeing different cases on the data, it's probably a good indicator of how it's occurring.
------------------------------
Steven Shull
IBM
------------------------------
Original Message:
Sent: 06-25-2021 04:34
From: Meghana Siriveli
Subject: Duplicate hierarchy levels on locations
Hi All,
we had an issue with locations hierarchy in our Prod data.
It is observed that there are duplicate rows at one of the levels on the hierarchical path.
The locations are created and the hierarchy is also updated via Flat files.
I have tried to update the same in lower envs and no such duplicate hierarchy is created either via front end or via MIF.
Can any one shed some light on the possibilities where this kind of duplicate hierarchy is created for a Location.
#Administration
------------------------------
Meghana Siriveli
------------------------------