Orphaned reservations in clubusy.nsf

This is mostly to help me remember these commands but I figured they might help someone else too. The information comes from this Technote.

This morning I got a helpdesk ticket indicating that a conference room was showing up as unavailable even though there were no reservation documents in the Room & Resource database that held the room.

By running the tell RnRMgr show roomname/sitename command on the server console I could see that clusbusy.nsf did indeed think there was a reservation for the times in question. So just to be safe I ran the following commands:

  • tell RnRMgr check roomname/sitename
  • tell RnRMgr validate roomname/sitename

I then ran the original tell RnRMgr show roomname/sitename command and verified that the orphaned reservation had been removed from the clusbusy.nsf. Then I tried to create a new reservation for that particular room resource for the time in question and this time it showed as available.


You can leave a response, or trackback from your own site.

3 Responses to “Orphaned reservations in clubusy.nsf”

  1. CV says:

    I have just come across this recent open mic:
    http://www-01.ibm.com/support/docview.wss?uid=swg27023671&aid=1

    in which one of the slides mentions that the check should run after validate, something that the technote does not mention.

    I did not find out why and looking at what each does, cannot understand why. Any idea?

  2. Ray J Bilyk says:

    Hi Garrett!

    I attended that session as well, and highly recommend it, even for some of us ‘old timers’…

    Here more info on the session:
    http://www-10.lotus.com/ldd/nd85forum.nsf/DateAllThreadedWeb/8d5a3a16c62765a0852579d0006690de?OpenDocument

    Take care! Keep the paint up, and the rubber down!

Leave a Reply

Subscribe to RSS Feed Follow me on Twitter!