LO88010: SCHEMA MAX VERSION NOT UPDATED DURING UPGRADE OF HA ENVIRONMENT WITH DB/2 ON AIX
Direct links to fixes
Closed as program error.
After upgrade from Traveler 126.96.36.199 to 188.8.131.52, customer noticed the following Warning when running the [096C:0006-1950] tell traveler version [18D4:0014-17EC] 02/09/2016 12:03:18 PM Traveler: IBM Traveler 184.108.40.206 Build 201601150235_20 [18D4:0014-17EC] 02/09/2016 12:03:18 PM Traveler: running on IBM Domino server Release 9.0.1FP4 HF409 September 18, 2015 on Windows/64 running on a VM with number of processors of 1 [18D4:0014-17EC] 02/09/2016 12:03:18 PM Traveler: Warning - invalid schema configuration detected, using 20160111 with min 20140619 and max 20150909 database schema configuration. Searching the NTSAtivity log after a server startup, we see that DBSchemaMigrator.migrateDBSchema was not called during the first startup of the server and therefore the max schema version was not updated. ########## Database Configuration Information (Tue Feb 16 04:04:44 EST 2016) ########## Description: IBM Traveler Database Configuration Information. Database Product Name: DB2/AIX64 Database Product Version: SQL10014 Database Version Major.Minor: 10.1 Database Driver Major.Minor: 4.0
Only saw this issue running DB2 on AIX. The JDBC driver returned slightly different value for no error than on other platforms. Minor change to check for this value.
The IBM Traveler server has been updated to handle this unexpected return code.
This fix will be included in IBM Traveler 220.127.116.11 and all future releases. For the latest available maintenance release see this technote: http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
NoSpecatt / Xsystem
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