Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Shipped
Workspace Domino
Categories Administration
Created by Guest
Created on Oct 31, 2018

Recreate a single document in busytime/clubusy

It can happen that there is a corrupt/faulty document in the busytime/clubusy database. Today, you have to recreate the whole database to fix this issue. It would be nice if there is a command to just recreate this single document. "tell sched validate" or "tell rnrmgr validate" is not helping in the most cases!
Recreate busytime/clubusy: http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21086471

  • Attach files
  • Admin
    Thomas Hampel
    Reply
    |
    Jun 2, 2020

    This is already available in the product :

    tell sched rebuild

    Reference:

    tell sched -?
    Purpose: Maintain and update the Domino busytime system.
    Usage: TELL SCHED [options]...
    [options]:
    show UserName Shows busytime data for user UserName.
    check [UserName] Request busytime for user UserName be checked for accuracy.
    If no UserName is provided, all users will be checked
    validate UserName Verifies that UserName is a 'valid' user that belongs
    in busytime. 'Invalid' users are removed from busytime.
    stats Calculate and display current busytime statistics.
    rebuild UserName Rebuilds the busytime record for the specified user.

  • Admin
    Thomas Hampel
    Reply
    |
    Nov 2, 2018

    Have you tried finding out whats causing this type of corruption? Instead of recreating the busytime database or recreating a single document the root cause of the problem should be found. Is there a PMR number we can reference?