You can also rebuild the database at a later time when you have exclusive access to the database
where the data has been lost. See
on page
381.
26.3 Rebuilding Domain or Post Office
Databases
In addition to correcting the physical problems resolved by the database recover process, the rebuild
process updates user and object information in a domain database (wpdomain.db) or post office
database (wphost.db). However, the process requires that no users or GroupWise agents (MTA or
POA) have access to the database during the rebuild process.
You should rebuild a domain or post office database if you encounter any of the following
conditions:
Objects are not being replicated between domains.
The agent that writes to the database went down unexpectedly.
The server where the database resides went down unexpectedly.
You receive an administrative message informing you that an internal database error has
occurred or there is database damage and you think there might be data loss.
You ran the recover database process and received a notification of data loss.
When you rebuild a secondary domain database, information is retrieved from the primary domain.
When you rebuild a post office database, information is retrieved from the domain it belongs to.
During the rebuild process, a backup of the domain or post office database is created as well as a
new wpdomain.db or wphost.db. The records from the primary domain database are copied
into the new wpdomain.db. There should not be any data loss. When the rebuild process is
complete, the temporary database and the backup database are deleted.
Section 26.3, "Rebuilding Domain or Post Office Databases,"
Maintaining Domain and Post Office Databases 381
Need help?
Do you have a question about the GROUPWISE 7 - DATABASES and is the answer not in the manual?
Questions and answers