We have been using Resource Reservations in R6.5 for a few months, and have the same reocurring issue popping up time and time again.
When a resource is cancelled noone can ever book it again. Although it no longer appears in the Resource Reservations database, or the users calendar , the database seems to keep a hold of this booking and won’t let it show correctly as being free anymore. This is even the case if you wait a few days and try and rebook it again at that same time and date.
We use clustered servers, so the only way to get round this seems to be to delete and recreate the clubusy.nsf on a regular basis, or reloading sched onto the server. I even tried disabling replication of the clubusy.nsf on my other clustered servers but this did not resolve the problem. My resource reservations database does not have a replica elsewhere.
Does IBM have any comment on this? I have trawled this forum and found similiar postings with no solution that is applicable to my case. It is very frustrating, and my users have already lost confidence in this solution.
Thanks.