Novell GROUPWISE 7 - TROUBLESHOOTING 2 Troubleshooting Manual page 38

MTA Fails to Update the Domain Database Version
Possible Cause: You installed and started the MTA for the secondary domain before the MTA
Possible Cause: There are one or more closed links between the secondary domain and the
38 GroupWise 7 Troubleshooting 2: Solutions to Common Problems
Problem: You are updating the MTA software in a secondary domain and the MTA fails
to update the database version for the domain. You might see conflicting
database version information depending on whether you are connected to the
secondary domain or the primary domain.
for the primary domain had finished updating the primary domain database.
Action: Wait until the MTA for the primary domain has finished updating the primary
domain database. For a large domain database, you might need to wait as much
as 20 minutes or more. Verify that the primary domain database version has
been updated by checking the Domain object's Identification page in
ConsoleOne. Then stop and restart the MTA for the secondary domain to
update the secondary domain database.
Action: If restarting the MTA for the secondary domain does not update the domain
database version:
1 Compare the dates on the .dc files
secondary domain directory with the dates on the .dc files in the update
source (the GroupWise 7 Administrator CD or the software distribution
directory if it has been updated from the GroupWise 7 Administrator CD).
2 If the dates on the .dc files in the secondary domain are older than the
dates on the .dc files in the update source, copy the .dc files from the
update source into the domain directory.
3 At the MTA console, recover the domain database. See
Domain Database Automatically or
Agent" in the
When the recovery process is finished, the database version should be
updated.
4 In ConsoleOne, connect to the secondary domain, then check the Domain
object's Identification page to verify that the database version has been
updated.
5 Connect to the primary domain database, then check the Identification
page for the primary domain to verify that the database version
information matches in both domain databases.
Action: If recovering the secondary domain database does not update the version, then
connect to the primary domain and rebuild the secondary domain database.
See "Rebuilding Domain or Post Office
GroupWise 7 Administration
primary domain that are preventing the administrative messages from flowing
between the domains to accomplish the database version update.
Action: Check the links between the domains and open any closed links. See
Configuration Status Isn't Open" on page
the secondary domain database. See
Automatically or
GroupWise 7 Administration
(gwdom.dc
Immediately" in
GroupWise 7 Administration
Databases" in "Databases" in the
Guide.
37. After all links are open, recover
"Recovering the Domain Database
Immediately" in "Message Transfer
Guide.
and gwpo.dc) in the
"Recovering the
"Message Transfer
Guide.
"MTA
Agent" in the