IJ37259: REGRESSION IN MICROSOFT ODBC 2017.X.X.X DRIVER RESULTING IN FAILED SQL PROCESSING BY TEPS

IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 12 (6.3.0.7-TIV-ITM-SP0012)

APAR status

• Closed as program error.

Error description

• Environment: TEPS; Windows x86 / x64
  
  Do you think the latest patch applied is involved? No
  
  Customer is running ITM 6.3.0.7 SP5 on a windows server 2016
  with SQL-Database 2017. On upgrading from Microsoft SQL Server
  ODBC Driver Version 10.00.14383 to ODBC Driver for SQL Server
  Version 17.05.0002, the TEPS is not working properly and getting
  error in logs :
  ---
  Microsoft][ODBC Driver 17 for SQL Server][SQL Server]'BLOB' is
  not a recognized built-in function name., GENERIC SQLSTATE:
  42000, ERR: 195
  --- The root cause is a backward compatibility regression
  introduced by Microsoft in all ODBC drivers which begin with a
  release identifier of 2017.  The regression involves an invalid
  return code from one of the ODBC functions which is used by the
  TEPS to distinguish between DBMS types (e.g., DB2, Oracle,
  MS-SQL Server, or Derby).
  
  Detailed Recreation Procedure:
  Reference: SF case TS007995857 and skills case TS008002029.
  
  Related Files and Output:
  /ecurep/sf/TS007/995/TS007995857/
  

Local fix

• Until the APAR fix is available, the customer should continue to
  use the 10.x.x.x ODBC driver release (the release that worked
  previously, before the uplift to the 2017.x.x.x driver was
  attempted).
  

Problem summary

• A regression in Microsoft ODBC v2017.x.x.x driver(s) results in
  failed SQL processing by TEPS on Windows when installing
  application support information into the TEPS DB.
  
  
  Due to a undocumented regression in the Microsoft ODBC drivers
  for Windows with version stamps beginning with 2017.x.x.x, the
  TEPS component is unable to accurately determine which type of
  database is being used to store TEPS-related definitions.  In
  particular, this regression affects database tables involving
  Binary Large Object (BLOB) and image type columns.  INSERT and
  UPDATE operations against tables involving these column types
  will fail.  When this failure occurs, the following error
  message is normally reported in the TEPS trace log(s):
  
  `[SQL Server]'BLOB' is not a recognized built-in function name.`
  

Problem conclusion

• The TEPS component has been updated to use a different, more
  resilient method for determining which type of database is being
   used for TEPS operation.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | service pack | 6.3.0.7-TIV-ITM-SP0012
  

Temporary fix

• When assigning an ODBC System DSN to the TEPS database (which is
   normally accomplished by using the Windows 64-bit ODBC Data
  Sources utility), use only older Microsoft ODBC drivers with
  version stamps beginning with 10.x.x.x.  Do not assign Microsoft
   ODBC drivers with version stamps beginning with 2017.x.x.x or
  above.
  

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

  TEPS

• Fixed component ID

  5724C04PS

Applicable component levels