LO92881: ONE SYNC QUERY NOT USING INDEX OPTIMALLY.

IBM Traveler 9.0.1.19 for Windows
IBM Traveler 9.0.1.19 for Linux
IBM Traveler 9.0.1.19 for IBMi

APAR status

• Closed as program error.

Error description

• Customer reported high CPU on the database server with one
  particular query.  The query in questions looks like this:
  
  SELECT M.TS_DEVICE_RECORD_ID FROM ts_record_mapping M,guidmap G
  WHERE G.BACKEND_GUID=@P0 AND G.CAF_GUID=M.TS_GUD_RECORD_ID AND
  M.TS_DEVICE_ID=@P1
  
  In general this query should run quickly, however depending on
  the optimizations provided by the Database engine its possible
  that it will not be used efficiently.  This APAR will be used to
  update this query so it is more efficient.
  

Local fix

• NA
  

Problem summary

• The select portion of this query was only supplying the second
  field of a three field index, thus is not optimal.  The fix is
  to supply both the first and second field for the index so the
  index use is optimal.
  

Problem conclusion

• The IBM Traveler server had been updated to handle this scenario
  correctly.
  

Temporary fix

• This fix will be included in IBM Traveler 9.0.1.19 and all later
  releases.  For the latest available maintenance release see this
  technote:
  
  http://www.ibm.com/support/docview.wss?uid=swg24019529
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  LOTUS NOTES TRA

• Fixed component ID

  5724E6204

Applicable component levels

• R901 PSY

     UP