I would clean up the pending records. We've hit this before, cleaned them up and were able to proceed with adding the extended attributes.
There could be some pending entries in OBJSTR:AttributeDefinition, OBJSTR:Pending, OBSTR:Class, OBJSTR:Index forms. Delete these pending records and any records related in Application Pending form.
Just to add to Brians advice, there are a couple of other forms to search and delete too.
Single Sign On (SSO) for the BMC Remedy AR System, MyIT/SmartIT & ITSM
Thanks Danny...You were up late
I would follow Danny advice on that KA. Also there are some others, but roughly:
Manually revert classes to active.
Start with a small change in a small class (a class with no children).
If above works climb up the ladder and try another change in a parent class.
Keep climbing until you find the problem.
If you bump into an issue the best way to figure out what it was it to have cmdb_eng_debug.log in debug mode as well as API/SQL/filter logs from the time of the class change.
I apologies for responding late,
Thanks Brian, Danny & Gustavo for your valuable comment and suggestions.
I agree to the point of Gustavo to cleanup metadata for changing class from change pending to active. But we have 2 entries for base element class and both are in change pending status, which one to choose to move to active is bit a confusion. Any clue on this ?
Once we figure it out this, then we can follow the smallest child class changes as suggested by Gustavo and climb the tree up till BMC_BaseElement class
Thank you for the suggestion, we will remove most recent entry and keep old entry as a active. I will keep you more update once this change has been updated in system.
Thank you once again for assisting me on this.