What to do next III. The free time database busytime. If the database is corrupt, the Schedule Manager will abort and log a failure, and free time lookups will return no data or inaccurate data. To troubleshoot inaccurate free time, start by doing the following: In rare cases, they may not match when a user, room, or resource was renamed and the rename did not complete.
Check the Administration database admin4. What to do next: If you checked all items above and they are correct, follow the steps below. Before executing the console commands below, enable console logging with the following command: This command looks at the free time database and displays the entries for this person sorted chronologically.
The data is placed in log. There is one line per entry except in the case of repeating meetings which are listed with two lines per entry. Schedule Manager will also tell you some information about each entry such as whether it's pencilled in or repeating. You can use this information to match up against entries in the user's actual calendar. Issuing this command displays the user's profile information, tells you when the user is available, writes the data to the log.
This command causes Schedule Manager to check the user's busytime data against the actual calendar documents. If there are any existing busytime entries that are different from the actual entry in the user's calendar, the user's busytime is updated to match the version in the mail file. If the entry does not exist in the mail file, it is removed from the user's busytime record. Entries that do not already exist in the busytime database are not found and added.
This command simply makes the current busytime data match the data in the user's mail file. After running this command, if the busytime is still not accurate, open the calendar entry in Edit mode and modify it by either making a fake change to it press the space bar in the description field or marking it "pencil in".
Run the command again. If you marked the entry as "pencil In", deselect the "Pencil In" checkbox and run the command again. This causes Schedule Manager to check if a user is valid or not on that server.
If the user is valid, Schedule Manager picks up any calendar-related changes that occur in the user's mail file after the command is run. It will NOT pick up any missing updates up to that point. If Schedule Manger is already monitoring for calendar entries, the command has no effect. This command is primarily intended to be used in cases in which new users, rooms, or resources are added to the Domino server but are not immediately reflected in busytime. Schedule Manager will begin to monitor the user's mail file and create a busytime record.
Schedule Manager repeats its startup scans and database validation at 2AM local time so any new user, room, or resource will automatically be found and added to busytime. After all above procedures are executed and the free time system still is not providing accurate results, you may have to recreate the free time database. For more information, refer to "How to re-create the Busytime. If the steps above do not resolve the issue, prepare the following data to be submitted to IBM Technical Support: It will take effect without a restart.
In releases prior to Domino 6. The levels are as follows: This option is for tracing busytime information gathering by Schedule Manager only. This setting is NOT useful for tracking down any busytime lookup-related problems. Changes to this setting DO require a restart of Schedule Manager in order to take effect.
The values are the same but the notes. This debug information should be included for situations on Domino 7. Gather the following data: An operating system OS copy of the busytime. An OS copy of the mail file or Resource Reservations database. An OS copy of the Domino Directory. Any logged output that relates to the problem missing entries, entries that do not belong, and so on including: Although this document was written for R6, the information is still valid in later releases.