800xA SV5.1 Log Configuration
I use a 800xA system SV5.1-4. Now I found that under some objects there are more than one (tree) Log configuration aspects. One without any logged properies, one with the logging of the property "MC" connected to an Log Template and the last one with the logging of the properties "MC" and "Ack1". The last Log Configuration aspect is also located at the mother object in the object type structure.
Now I tried to delete the first and second Log Configuration, becaus I want to use only the Log Configuration aspect of the "mother object". But it is not possible to delete the aspects. "[Error] Aspect 'Log Configuration' is requiered by the object type. Not allowed to delet it on the instance 'MO001_MO'. Transaction cancelled." I deleted all Logged prperties connected to this Log Configuration, Diabled the Log Configuration aspect. But it's not possible to delet it.
What can I do do delete it?
Voted best answer
This is the downside of using the Auto-Instantiate (aka Copy To Instance) feature to roll out something that wasn’t intended to be used this way.
I have written numerous of times here on AKS about the ”poisonous” Auto-Instantiate feature.
Do not use it if you intend to:
a) change settings on instance level
- or -
b) change settings on type level
Caveat 1: b) will only work as long as a) has not been made.
Caveat 2: delete is not possible, nor ”undo” of a) unless log aspect is restored from backup
Caveat 3: a) will take place IMMEDIATELY at creation of log if IM is in the config
a) is easily spotted by comparing the aspect’s Creation and Modification times.
I sincerely recommend to use Bulk Data Manager instead, or bulk sheet of IM toolkit.
To come out of the current situation try this:
1) backup system
2) backup operateitdata\History folder (with Basic History stopped)
3) bulk out all log configurations
4) sanitize bulk sheet (reduce to single log config aspect per object)
5) reduce log templates in sheet down to a minimum
6) delete log configurations from types
7) use log template to delete all log configs (templates has a button for this)
8) purge obsolete log templates keeping only the ones referenced in bulk sheet
9) bulk in new log configs
Some (all) already logged data may be salvaged. The AdvHtArchiveTool (briefly described in Online Upgrade manual) can push back data from a previous backup (data folder of Basic History) if object GUID and log name in template is same (you can actually temporarily change log name in a template to make a fit, then restore desired name after the tool has made its job).
this sounds not good. Thanks god we use this Object not to often.
I find a way to delete the log configuration. I disable the "Aspect object" in CBM. The result is that the object disapears. A
fter that I enabled "Aspect Object" again and the object apears with only one log configuration aspect. The trend holds the old data too. But I have to download the changes to the controller.
So you think it's better to reduce the inherited aspects in the object type structure to as much as necessary? Can you give me some links to your discussion of the Inheritance.
Thanks a lot for the fast answer.