How Does GroupWise Check Work?

GroupWise® Check begins by comparing three sources of information: the post office database (wphost.db), the guardian database (ngwguard.db), and other database files that reside in the post office directory. The comparisons are based on matching up each user�s file ID (FID) in the various locations.

wphost.db	ngwguard.db	File System
FID abc	userabc.db	userabc.db
The post office database is checked for the FID for the user being checked.	The ngwguard.db database is checked to find out if this user database has been created.	The file system for this post office is checked to see if the database for this user exists. In this case, GroupWise Check found the database in the ofuser subdirectory.

After GroupWise Check makes the database comparisons, it begins processing according to the databases selected and any inconsistencies found.

Case 1 - Missing Entry in the Post Office Database (wphost.db)

In this example, a contents check was either run against all users on the post office or against one user, "abc." The check did not find the FID of one or more users that do not exist in the other databases.

wphost.db	ngwguard.db	File System
?	userabc.db	userabc.db
No entry was found for this user in the post office database.	An entry was found in the guardian database, indicating that the user has been deleted.	A database for this user was also found in the ofuser subdirectory.

GroupWise Check will remove the entry from ngwguard.db, delete userabc.db, and systematically delete all of the user's messages from the message databases that are not still being referenced by other users.

WARNING: If a post office database becomes damaged so that some users are unable to log in, GroupWise Check should not be run until the post office has been rebuilt in ConsoleOne® using Tools > GroupWise Utilities > System Maintenance > Rebuild Database.

Case 2 - Missing Entry in the Guardian Database (ngwguard.db)

In this example, GroupWise Check was either run against all users on the post office or against one user, "abc." A user's FID was found and the user's database was found in the post office, but the user was missing in the guardian database.

wphost.db	ngwguard.db	File System
FID abc	?	userabc.db
The user was found in the post office database.	The guardian database records no user database for this user.	A user database for the user does exist.

GroupWise Check will create the user in the guardian database, using the userabc.db database.

Case 3 - Missing User Database (userxxx.db)

In this example, GroupWise Check was either run against all users on the post office or against one user, "abc." The user's FID was found, as well as the user's record in the guardian database. However, the corresponding user database was not found.

wphost.db	ngwguard.db	File System
FID abc	userabc.db	?
The user was found in the post office database.	The user was also found in the guardian database.	No user database was found.

Contents Check

GroupWise Check deletes all of this user's messages from the message databases if they are not referenced by other users.

Structural Rebuild

GroupWise Check creates a blank user database for this user. Existing messages for this user are ignored.

Re-create User Database

GroupWise Check creates a blank user database for this user and populates it with messages in the message databases that have been sent to or from this user.

WARNING: If a user database has been deleted, do not run a contents check until after a Structural Rebuild or Re-create User Database has been run for that user.

A trademark symbol (® ,™ , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For more information, see Legal Notices.