In certain situations, for example: the Post Office Agent (POA) will not start, the POA IP Address has changed while the POA was not running, the database has incorrect information in it, etc. It will be necessary to rebuild the wphost.db file from the owning GroupWise domain.
Before rebuilding the post office database, it is considered best practices to ensure that the owning domain is up to date and contains accurate information. If the domain is not up to date, then the rebuilt post office database will only be populated with incorrect information.
1. Open the GroupWise Admin Console and connect to the owning domain of the post office that needs to be rebuilt. For this example, the database for Post03 owned by domain Secondary01 needs to be rebuilt.
2. Select the <domain object> | Maintenance | Validate database | Run. This will not require the MTA to be stopped. It will clean the domain database from any obsolete records and might also reduce a size of the database file.
3. If the Validate Database passes successfully, skip to step 4. Otherwise, perform a Recover Database operation to correct structural inconsistencies in the database.
4. Open the properties of the POA for the post office to be rebuilt. If the status shows as running, select the Stop Agent button.
5. For backup purposes and to ensure that a clean database is built, it is best to rename the current post office database (wphost.db) file. When renaming the file, do not leave the .db extension in place. For example: wphost.mmddyy.
6. In the GroupWise Admin Console | Post Offices | <post office to be rebuilt> | select Maintenance | Post Office Database
7. Select Rebuild Database. Ensure the POA Status = Stopped. Select Run. The rebuild it's self typically only lasts a few seconds.
8. After the rebuild completes, select Close. Then select Start Agent to load the POA. The rebuild database operation has been competed.
In situations where the POA agent will not stop from the Admin Console or there is a java based error when attempting to perform the rebuild, it will be necessary to rebuild the database manually.
1. Open a putty session or terminal window on the domain server that owns the post office (where the MTA is running).
2. Create a temporary folder off the root drive called: /rebuild
3. Change to the /rebuild folder.
4. Run the gwadminutil command like:
gwadminutil rebuild -d /<path to domain> -n <name of PO> -o /<path to PO>
5. Stop the POA by running the command: rcgrpwise stop <poName.DomainName>
6. For backup purposes and to ensure that a clean database is built, it is best to rename the current post office database (wphost.db) file. When renaming the file, do not leave the db extension in place. For example: wphost.mmddyy.
7. If the post office is running on the same server as the owning domain, simply copy the wphost.db file from the /rebuild folder to the production post office folder. Otherwise, use WinSCP or another tool to copy the wphost.db from the domain server onto the post office server and into the production folder.
8. Start the POA by running the command: rcgrpwise start
The rebuild database operation has been competed.
Access article on support portal