Metadata field -Tree update don't work from Config mgr and database

Question

Hi All,
I am using UCM 11g. I have a Information field of type 'Memo' which is based on a Option list which uses tree. Updating it is giving me the following problems:
1. When i update a value in the tree using UCM CS configuration manager, sometimes the change doesn't get reflected on the update info form of a document (immediately and even after several hours)
2. When i update directly through database end, sometimes the change is not reflected in the config mgr - information field. And sometimes it reflects there immediately but not in update form.
Once Publishing schema and clearing browser's cookie/temp files worked, but not every time.
Currently, i have added some data from db end, and the data is not showing up on config mgr, and even in the views there. I have tried clearing browser's cache, publish schema, publish schema base, publish schema config and data, but nothing worked.
I don't want to go for bouncing the server option every time for such changes. Sometimes, everything does work fine instantly.
Is there some cache etc maintained by UCM and how to clear it so that it picks up the changes in the underlying table data immediately? Please help asap as i have been stuck in this for a long time.
P.S. I am doing it from db end in the correct manner, and doing so because i have hundreds of values to be added/updated in the metadata taxonomy tree so don't want to do it manually from ucm config mgr ui.

Answer 1

'*Is there any UCM notification mechanism which we can use so as to tell it that there is some change in the underlying database or in configuration manager metadata tree; or some in built cache that we can clear so that it picks up the change*'.Nothing I would be aware of. Since you can just login directly to the database (e.g. via sqlplus) and insert/update/delete rows directly such a mechanism would have to be in the database (a trigger), but that would be an overkill.
Updates in the database - when run from the Config Mgr, for instance - work differently - first a change is done, than a service to update the schema is called (a change, actually, means both changing the scheme and its metadata). I don't know how exactly changes in taxonomy are implemented, but I'd expect something similar - note that a lot of information is cached due to performance reasons and changes like adding/modifying a profile, option lists, or trees might require purging this cached data. Usually, at least closing the browser/re-login helps. If there is a mechanism that can force 'push-model', I'm not aware of that.