I am having a problem activating calendar resources (rooms) during the day. It will, however, activate correctly over night.
Example 1, if I changed the room availability from 8am-5pm to 7am-6pm, I would have to wait overnight for this process to update. When I try to reserve a room about 1 hour after requesting this, I will get the 8-5pm availability. This used to take effect within 1/2 hour. We have a clustered environment.
Example 2, if I activate the room availability for reservation from 8am-5pm , I would have to wait overnight for this process to update. This used to take effect within 1/2 hour.
I am able to see my request document the Administration Request DB and confirmed by ADMINISTRATION PROCESS document about 10-15 minutes after I request.
It will, however, process correctly over night. We tried rebuilding our busy time db but no luck.
Any ideas? Thank you in advance.
Subject: Calendar Resource and CluBusy.nsf problem
maybe
Tell RnRMgr validate roomname/site
would push changes through
Subject: Not quite
The “validate” command merely tells the RnRMgr task to check if the given name is a ‘valid’ one (and thus should it be watched for future data).
That command has more use for Schedule Manager (Sched) really. Perhaps I should remove it from RnRMgr, Ill have to think that over a bit.
Bruce
IBM
Subject: Some thoughts
as to whats going on (and corrections to misconceptions)…
Changes to room settings like available hours are processed immediately so if RnRMgr is monitoring your R&R dB then the change should be visible w/in seconds to any client. So something about your installation is making RnRMgr think twice about processing docs/changes in your R&R dB. Sooooo…
First off, is your R&R installation new in R7 or did you upgrade it from a pre-R7 version? If you upgraded your older installation, be sure you replace the design of the R&R dB with the resrc7.ntf one! Refresh will not work as your dB is based off of resrc60.ntf (or resrc50.ntf if you are a long time R&R user). Once you replace the design, you will want to restart the RnRMgr task (or just wait overnight for it to pick it up at 2AM).
Check the console log for any messages that look like:
RnRMgr: The design of resource.nsf is not one supportable by RnRMgr. Autoprocessing is being disabled for this dB.
which is a big indicator that RnRMgr does not like your R&R dBs design and thus will not process stuff in it.
AdminP requests are only used to update the NAB from the R&R template when you add a new room or make changes to it. However some changes are not visible in the NAB such as the available hours or the Limit future bookings settings; they only stay in the dB and are used by RnRMgr when requests come in. Do not look at AdminP requests for this problem; they are just a distraction at best.
In your cluster, are all the servers where you have the R&R dB R7 or later? We allow cluster replicas on R7 or later servers but not pre-R7 servers because of code in the pre-R7 router.
Lastly: There is NO need to rebuild busytime (or clubusy.nsf) unless there is a problem accessing it. The delay in getting data changes into busytime is never going to be fixed by just rebuilding it. You will only manage to make using C&S harder for your users by doing this. VERY early on (~R4.5) we did not yet have a good means for detecting changes and handling ‘upgrading’ busytime so folks were just told to “rebuild busytime and things would be ok”. Well, the need for this is LONG gone but old habits are hard to break…
Bruce
IBM
Subject: RE: Some thoughts
Bruce - these are great suggestions. We’ve upgraded from R5 and R6 so I am sure we’ve got some old templates and design elements hanging around.
I’ll go through these checks to make sure everything is correct and let you know what the results are.
CSU