Site change in Ressources DB doesn't work correctly

We have an odd problem regarding site documents in the Ressources DB.

Usually we wouldn’t notice but we have created a special view that makes this one visible. This special view lists reservation documents categorized by site.

So here’s what happens:

  1. We create a new site document

  2. We change some ressources to the new site

  3. We wait till the AdminP has processed the change

  4. We are surprised to see that our view “categorized by site” still shows the old site name.

We checked the resource documents and they have the current (correct) value. Then we create a new reservation and everything is fine her too.

So we found out that only old reservations aren’t updated correctly. While the resourcename (CN=…) was updated correctly in the reservation document (so the update agent was obviously running) the value in the site-field of the reservation document wasn’t updated (also the script in the update agent says to do so).

Unfortunately this is the value we have choosen to use for our category.

I know there are several workarounds like using the site part of the resource name etc.

But I am interested to hear if this happens just to us or is a common problem (which goes unnoticed for most people for obvious reasons).

Or maybe it’s on purpose that the site field in existing reservations isn’t updated because I can’t see many uses of this field (except for our special view).

Thanks

Harald