LO90497: CHANGING NTS_AUTO_SCHEMA PARAMETER WITH DB2 MAY CHANGE SCHEMA NAME.
Direct links to fixes
Closed as program error.
Customer switched from NTS_AUTO_SCHEMA=false to NTS_AUTO_SCHEMA=true in production which isn't a problem. However they had been using the default schema name of LNT. Since the default value it didn't have to be set in notes.ini so when change AUTO_SCHEMA settings the schema name also changed unexpectedly. This is only seen when using DB2 as the enterprise DB solution. The fix in this APAR will be to Auto generate the NTS_DB2_SCHEMA=LNT value into the notes.ini when it is detected that NTS_AUTO_SCHEMA is set to false and the customer is using the default schema value. Then switching AUTO_SCHEMA values will work as expected. Additionally the customer will still be able to change the NTS_DB2_SCHEMA value in notes.ini if desired.
Set NTS_DB2_SCHEMA=<schema name> in notes.ini, in this case LNT is the schema name.
Updated the travelerUtil application and the product documentation to indicate that changing the database username could impact the schema and/or database name accessed by the IBM Traveler server.
The IBM Traveler server has been updated to improve the product usability in this scenario.
This fix will be included in IBM Traveler 18.104.22.168 and later releases. For the lastest available Traveler Server 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
Translate this page: