Delete Reservation in StdR8ResourceReservation/de

Since upgrading the design from our Reservation-Database we have problems with reservations, that were created with the StdR6 Design.

When there is an old recurrent reservation, users cannot “Delete Reservation”. They can only delete all reservation, but not only one of them.

Is there anything to do for upgrading the database ? We only made a Design-Update to the R8-Template, but that it seems that this is not all …

Thanks

Subject: Rooms/Resources

Extract from IBM.

It will not work… When I upgraded I manually created a new database and reentered all the bookings.

  • Resource Reservations has seen significant changes since Domino 6.5. Prior to Domino 7, the resource and reservation functionality was distributed amongst the resource template, the router task, and the schedule manager task.Beginning with Domino 7, this functionality was combined into a single server task: Rooms and Resource Manager or RnRMgr. - If you are upgrading directly from Domino 6.5.x or earlier be aware that Resource Reservations databases (RRDB) based on a 6.x or earlier design do not function properly on Domino 8 servers. - Overbooking of rooms and resources can easily occur if you attempt to use a pre-Domino 7 RRDB on a 7.0 or later server. So you’ll want to replace the design of the Resource Reservation template immediately. In Releases 7.0.2 and later, this is done automatically at server startup. Technote #1363903 - How to upgrade the R&R database from a Domino 6 to a 7 or 8 release. Wiki article - Clustering the Resource Reservations database in Lotus Domino

http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21363903

Subject: TechNote 1363903

is a tad dated as of 8.52. There are some Notes in it:

– The RnRmgr task runs at 2 a.m. This generates a notice to all owners who have not processed documents in the Waiting for Approvals view.
– Users may think they are receiving duplicate notices.

which need to be updated now that 8.52 has shipped. We updated the Waiting-for-Approval feature in 8.52 to:

1: Only send one email to the requesting using. So no more Inbox flood for Chairs.

2: Allow you to better control when WFA nag notices are sent and how many additional ones get sent!

It also does not describe the handling of pre-existing repeating meetings. If a repeating entry is of the R5 format (one doc - many dates) then the template could try to do lots of heavy lifting and splitting of docs OR it could take the simpler approach and just remove the entry for all of the affected dates.

We opt’d for the latter since that would work well for the repeating format that was adopted (or returned to really) in R7 (one doc - one date). To ease the transition I developed the tool that you can get from Support (or Susan it seems) which is described on Technote 1255213.

Bruce

IBM

Subject: This will indeed work

There is a tool available from Support that will convert the older entries to a version that will work properly. It is associated with Technote 1255213, but is not generally available online. If you call support and ask for it, you can get it. Alternatively, you can email me at firstname_last name @ us.ibm.com and I will send it.