1 of 1 people found this helpful
If the property is in use, you can only deprecate it as you have found.
What you can try is to set the value back to the default on all objects its used by, then run db cleanup and try to delete it again.
Any suggestions on how to find objects using it? I found the host I'd assigned the instance to, removed and deleted the instance. I've deleted the blpackages that were using the values as well.
What property class is this in ? server, a custom one ?
nm - i see.
so i think what you would do is to create smart group of all servers, set the APP_OMS to the default (right click - set property - APP_OMS - blue circle)
I don't think there can be any more hosts with a value assigned for it. It allowed me to remove the one instance of the class that existed after I found the 2 hosts that had it assigned. But I still can't modify the APP_OMS property that's under the Server.
In case I wasn't clear:
App class: JBOSS_APP_CLASS
I then extended the Built-in Server class with the APP_OMS to be the property class JBOSS_APP_CLASS
Unfortunately I think you may be stuck.
Are there any type of 'brute force' solutions to this problem?
For instance, I saw the problem that Mike is describing six years ago. We were automating the deployment of an application, and using a series of custom properties which were changing. (Hence, the problems with deprecation.)
And in my current environment, I have entire property classes that can't be modified. This is maddening because I have to use existing properties in ways that they weren't intended. (IE, the name of the property in the property class has *nothing* to do with it's real use, which makes code very hard to follow.)
Basically, what would the SQL query look like to find deprecated and/or corrupt properties in the server class?
Right now, no.