GroupWise Check (GWCheck) is a tool provided for GroupWise to check and repair GroupWise user, message, library, and resource databases without needing the Admin console. In addition to checking and repairing databases in the post office, it also checks and repairs users’ remote, caching, and archive databases on user workstations or other personal locations.
The GWCheck utility runs on Linux and Windows. You should match the platform of GWCheck to the platform where the databases are located. Linux GWCheck processes databases on Linux. Windows GWCheck processes databases on Windows.
IMPORTANT:GWCheck should not be used to process databases that are located across a network connection between different machines.
The GWCheck utility begins by comparing three databases.
|
WPHOST.DB |
NGWGUARD.DB |
FILE SYSTEM |
|---|---|---|
|
The post office database (wphost.db) is checked for the file ID (FID) of the selected user. |
The guardian database (ngwguard.db) 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 user database (userxxx.db) for this user exists. |
After GWCheck makes the database comparisons, it begins processing according to the databases selected and any inconsistencies found.
In this example, a contents check is run either against all users on the post office or against one user, “ABC.” GWCheck does not find the FID of one or more users.
|
WPHOST.DB |
NGWGUARD.DB |
FILE SYSTEM |
|---|---|---|
|
? |
userabc.db |
userabc.db |
|
No entry for this user is found in the post office database (wphost.db). |
An entry is found in the guardian database (ngwguard.db), indicating that the user has been deleted. |
Also, a user database (userxxx.db) for this user is found in the ofuser folder. |
GWCheck removes the entry from ngwguard.db, deletes userabc.db, and systematically deletes all of the user’s messages from the message databases that are not still being referenced by other users. If the user has been deleted, GWCheck cleans up after that user.
WARNING:If a post office database becomes damaged so some users are unable to log in, GWCheck should not be run until the post office has been rebuilt. For more information, see Section 42.3, Rebuilding Domain or Post Office Databases.
In this example, a GWCheck is run either against all users on the post office or against one user, “ABC.” A user’s FID is found and the user’s database is found in the post office, but the user is missing in ngwguard.db.
|
WPHOST.DB |
NGWGUARD.DB |
FILE SYSTEM |
|---|---|---|
|
FID abc |
? |
userabc.db |
|
The user appears in the post office database (wphost.db). |
The guardian database (ngwguard.db) shows no user database for this user. |
A user database (userxxx.db) for the user does exist in the ofuser folder. |
GWCheck creates the user in ngwguard.db, using database userabc.db. Even if ngwguard.db is damaged, it is unlikely that data is lost.
In this example, a GWCheck is run either against all users on the post office or against one user, “ABC.” The user’s FID is found, as well as the user’s record in ngwguard.db. However, the user’s database is not found.
|
WPHOST.DB |
NGWGUARD.DB |
FILE SYSTEM |
|---|---|---|
|
FID abc |
userabc.db |
? |
|
The user is found in the post office database (wphost.db). |
The user is found in the guardian database (ngwguard.db). |
No user database (userxxx.db) is found in the ofuser folder. |
GWCheck takes action depending on what options are selected.
Contents Check: GWCheck deletes all of this user’s messages from the message databases if they are not referenced by other users.
Structural Rebuild: GWCheck creates a blank user database for this user. Existing messages for this user are ignored.
Re-create User Database: GWCheck 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. For more information, see Section 43.3, Performing a Structural Rebuild of a User/Resource Database and Section 43.4, Re-creating a User/Resource Database.
Two versions of GWCheck are available on Linux, one for a graphical user interface (GUI) environment and one for a text-only environment.
Change to the /opt/novell/groupwise/agents/bin folder.
Enter ./gwcheck to start GWCheck.
Continue with Performing Mailbox/Library Maintenance Using GWCheck.
You can use text-based GWCheck in any environment where the X Window System is not available, such as on a text-only server where a post office and its POA are located. However, you must use GUI GWCheck to create an options file before you can run text-based GWCheck.
Run GUI GWCheck in a convenient location.
For instructions, see Using GUI GWCheck (gwcheck)
Select the maintenance activities that you want GWCheck to perform.
For instructions, see Section 51.1.4, Performing Mailbox/Library Maintenance Using GWCheck.
Save the settings you selected in an options file.
The default options file name is gwcheck.opt.
For instructions, see Saving Mailbox/Library Maintenance Options.
Copy the GWCheck options file you created in Step 3 to the /opt/novell/groupwise/agents/bin folder.
Change to the /opt/novell/groupwise/agents/bin folder.
Enter ./gwcheckt options_file_name to run text-based GWCheck.
Over time, a collection of options files might accumulate. To see what maintenance activities an options file performs, use ./gwcheckt options_file_name --dump.
To remind yourself of these options when you are at your Linux server, view the gwcheckt man page.
You can use GWCheck in any supported Windows environment. See the following sections for current system requirements:
Windows servers: Hardware and Operating System Requirements
Windows workstations: GroupWise Client User Requirements
As an administrator, you can run GWCheck for databases in any post office accessible from the workstation where GWCheck is installed. The GWCheck program performs all database maintenance itself, rather than handing off a task to the POA as the GroupWise Admin console would do to perform database maintenance.
Depending on how GWCheck is installed, users can have a Repair Mailbox item on the GroupWise client Tools menu that enables them to run GWCheck from the client. If the GWCheck program is available to users, users can perform database maintenance on their Remote, Caching, and archive mailboxes, which are not accessible from the GroupWise Admin console.
For the Repair Mailbox item to display on the GroupWise client Tools menu, the following files must be installed in the GroupWise software folder:
gwcheck.exe
gwchkxx.dll (Replace xx with your language code)
gwchkxx.chm (Replace xx with your language code)
The default location for the GroupWise software is c:\Program Files\Novell\GroupWise.
To run GWCheck:
From the Start menu, click Run, then browse to and double-click gwcheck.exe.
Continue with Section 51.1.4, Performing Mailbox/Library Maintenance Using GWCheck.
With only a few differences in interface functionality, as described in the online help, you can perform the same maintenance activities in GWCheck as you can in Mailbox/Library Maintenance in the GroupWise Admin console:
Both GWCheck and Mailbox/Library Maintenance in the GroupWise Admin console use tab options to control the checking process.
To select the types of database to perform the Mailbox/Library Maintenance check on, click Databases.
Depending on the object type and action already selected in the main window, some database types might be unavailable. If all the database types are unavailable, then one or more database types have been preselected for you.
You can perform an action on the following databases when the type is not unavailable:
User: Checks the user databases.
Message Databases: Checks the message databases.
Document: Checks the library and document properties databases.
To specify the name of the file where you want the results of the MailBox/Library Maintenance check to be stored, click Logging.
Specify a file name. By default, the file is created in the home folder of the user who is running GWCheck. Specify a full path to create the log file in a different location.
Click Verbose Logging to log detailed information. Verbose logging might produce large log files and slow execution.
This file is sent to the users selected on the Results tab.
To select users to receive the results of the Mailbox/Library Maintenance check, click Results.
Select Administrator to send the results to the user defined as the GroupWise domain’s notification user. For more information, see Section 24.6, Receiving Notifications of Agent Problems.
Select Individual Users to send each user the results that pertain to him or her. Specify each user’s GroupWise user name or email address in a comma-delimited list. Click Message to include a customized message with the results file.
If you need to run a Mailbox/Library Maintenance check with special options provided by Novell Support, click Misc.
Use the Support Options field to specify command line parameters. Support options are typically obtained from Novell Support representatives when you need assistance resolving specific database problems. Search the Novell Support Knowledgebase for TIDs and Support Pack Readmes that list support options. Ensure that you clearly understand what the Support options do before you use them.
If you want to exclude certain users in the selected post office from having the Mailbox/Library Maintenance check performed on their databases, click Exclude.
Click Add, select one or more users to exclude, then click OK.
For convenience, you can store the options you select in Mailbox/Library Maintenance and GWCheck so that you can retrieve them for later use.
After you have selected all of the options in the Mailbox/Library Maintenance dialog box, click Save.
Browse to the folder where you want to save the options file.
You might want to save it in the domain folder to which you are currently connected.
Specify a file name if you do not want to use the default of gwcheck.opt.
Click Save.
The GWCheck options file is created in XML format on all platforms. Therefore, you can create the GWCheck options file on any platform and use it on any platform interchangeably.
In the Mailbox/Library Maintenance dialog box, click Retrieve.
Browse to and select your saved options file.
Click Open.
The GWCheck program is located in the following folder:
/opt/novell/groupwise/agents/bin
Create a script to execute GWCheck using the following syntax:
/opt/novell/groupwise/agents/bin/gwcheck --opt=options_file --batch
To create an options file, see Saving Mailbox/Library Maintenance Options.
The GWCheck program is located in the following folder:
c:\Program Files\Novell\GroupWise Server\agents\gwcheck
It is also installed along with the GroupWise client software in the gwcheck subfolder of the GroupWise client installation folder.
Use the following syntax to create a batch file to execute GWCheck:
gwcheck /opt=options_file /batch
To create an options file, see Saving Mailbox/Library Maintenance Options.
The following startup switches can be used with GWCheck:
Runs GWCheck in the background, without a user interface. Use an options file to specify the database repair options.
|
Linux GWCheck |
Windows GWCheck |
|---|---|---|
|
Syntax: |
--batch |
/batch |
For example, to specify that you want GWCheck to run it batch mode, you would use:
|
Linux: |
./gwcheck --opt=gwcheck.opt --batch |
|
Windows: |
gwcheck.exe /opt=gwcheck.opt /batch |
Specifies the language to run GWCheck in, using a two-letter language code. You must install GWCheck in the selected language in order for it to display in the selected language.
|
Linux GWCheck |
Windows GWCheck |
|---|---|---|
|
Syntax: |
--lang=language_code |
/lang=language_code |
For a list of current language codes, see Section 7.0, Multilingual GroupWise Systems.
For example, to specify that you want GWCheck to run in Spanish, you would use:
|
Linux: |
./gwcheck --opt=gwcheck.opt --lang=es |
|
Windows: |
gwcheck.exe /opt=gwcheck.opt /lang=es |
Specifies a database maintenance options file created in a GWCheck session. This starts GWCheck with the same options settings as the session in which the options file was created.
The default location of the options file varies by platform:
|
Linux: |
User’s home folder |
|
Windows: |
Folder where gwcheck.exe is installed. |
If the options file is not in the default folder, you must specify the full path name.
|
Linux GWCheck |
Windows GWCheck |
|---|---|---|
|
Syntax: |
--opt=file_name |
/opt=file_name |
For example, to start GWCheck with saved settings, you would use:
|
Linux: |
./gwcheck --opt=gwcheck.opt ./gwcheck --opt=/gwsystem/post1/gwcheck.opt |
|
Windows: |
gwcheck.exe /opt=gwcheck.opt gwcheck.exe /opt=\gwsystem\post1\gwcheck.opt |
Specifies the path to the archive folder.
|
Linux GWCheck |
Windows GWCheck |
|---|---|---|
|
Syntax: |
--pa=path_to_archive |
/pa=path_to_archive |
For example, to specify the archive database that a user keeps is his or her home folder, you would use:
|
Linux: |
./gwcheck --opt=gwcheck.opt --batch --pa=/home/gsmith\of7bharc |
|
Windows: |
gwcheck.exe /opt=gwcheck.opt /batch /pa=\home\gsmith\of7bharc |
Specifies the path to the post office folder.
|
Linux GWCheck |
Windows GWCheck |
|---|---|---|
|
Syntax: |
--po=path_to_post_office |
/po=path_to_post_office |
For example, to specify a post office folder, you would use:
|
Linux: |
./gwcheck --opt=gwcheck.opt --batch --po=/mail/sales |
|
Windows: |
gwcheck.exe /opt=gwcheck.opt /batch /po=\mail\sales |
Specifies the path to the remote mailbox folder.
|
Linux GWCheck |
Windows GWCheck |
|---|---|---|
|
Syntax: |
--pr=path_to_mailbox |
/pr=path_to_mailbox |
For example, to specify the Remote mailbox that a user keeps on a computer at home, you would use:
|
Linux: |
./gwcheck --opt=gwcheck.opt --pr=/novell/groupwise\of7bharc |
|
Windows: |
gwcheck.exe /opt=gwcheck.opt /pr=\novell\groupwise\of7bharc |