LO74164: HA SCHEMA MIGRATION ERRORS RESULTS IN INCORRECT SCHEMA VERSION
Closed as program error.
During upgrade to 853UP2, from multiple stand alone servers , and moving to HA environment, after the first server is migrated to HA, the other servers joining the pool may cause incorrect schema version in the database because of migration errors.
If the schema migration from one of the stand alone servers succeeded and that traveler server is up and running , that indicates that the HA database schema is correct. However when migrating another stand alone traveler server to HA pool when you see errors like "awaiting schema version", the Database administrator can open up the HA datbase and manually edit the SCHEMAVERSION table and change the MAXVERSION to 220.127.116.11.20120831
Exception during migration could incorrectly set the schema version to the wrong value even though it is correct.
The Notes Traveler server has been updated to handle the exceptions correctly and not set an incorrect schema version for the Enterprise DB.
This fix is included in Notes Traveler 8.5.3 Upgrade Pack 2 Interim Fix 1 and will be included in all future releases. See this technote for the latest maintenance information: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels