Hello everyone,
After the Domino upgrade from Release 6.5.4 to Release 8.5FP1 HF384 we are experiencing many problems with our Resource Reservation database.
There are different problems like: receiving duplicate notifications, receiving notifications after the meeting was approved by the owner, reservation that don’t appear and that are not processed, etc. I found the following technote http://www-01.ibm.com/support/docview.wss?rs=463&uid=swg21385676 and I tested everything from there, but that didn’t helped at all. Is there any method to solve the problems without upgrading the infrastructure to Domino 8.5.1?
Thank you
Subject: Technote 1255213 / R6RnRFix / Need more info…
Did you check out Technote 1255213 ? Its titled “Potential for double bookings in Domino 7 when repeating reservations are deleted by the Delete Reservation action” and can be found here.
There were some issues with the docs created in pre-R7 R&R both by the template and by some Agents that customers have run that we discovered early in 7.x deployments.
To correct this, I developed a tool (R6RnRFix) that customers can get by contacting Technical Support. This tool will correct the known bad R&R doc cases and fix up the R&R dB to be healthy. Once you run it, you simply need to rebuild your busytime dB (to remove the cruft and start fresh) and then restart RnRMgr.
The tool does not fix some of the odd things you describe like reservations not appearing (or disappearing). For that I need more details like do the requests get accepted and then disappear or do they never appear at all?
I have never heard of WFA notices going out after an Owner acts on them except when there is a race between cluster replication and cluster failover. If the Owner acts on a request when the R&R server is down then when failover happens they could get an extra notice. However that should only be a 1 time deal and not something that repeats. If this is something you see often then look at the $CSTrack on the notice the Owner acted on. Look towards the bottom of the values to see what is going on and if there are any errors that are being reported / logged there.
Bruce
IBM