JR41392: MICROSOFT WINDOWS INTEGRATED SECURITY AUTHENTICATION TO SQL SERVER DOES NOT WORK IN 6.5.1

Fix list for IBM InfoSphere Change Data Capture

APAR status

• Closed as program error.

Error description

• Configuration will fail with [CDC][SQLServer JDBC Driver]A
  username was not specified and the driver could not establish a
  connection using Kerberos (type 4) integrated security:
  {pathToFile}/JDBCDriverLogin.conf (No such file or directory)
  when attempting to create a CDC instance with Microsoft Windows
  integrated security authentication
  

Local fix

• Use Microsoft SQL Server Authentication
  

Problem summary

• Configuration will fail with
   CDC  SQLServer JDBC Driver A username was not
  specified and the driver could not establish a
  connection using Kerberos (type 4) integrated
  security: {pathToFile}/JDBCDriverLogin.conf (No
  such file or directory)
  when attempting to create a CDC instance with
  Microsoft Windows integrated security
  authentication
  Any user who wants to use Windows integrated security to
  authenticate CDC to the database
  

Problem conclusion

• Use the latest 6.5.1 InterimFix to fix the
  problem.
  ISCDC 6.5.1 InterimFix 2 for Microsoft.
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

• CDCAPAR
  

Fix information

• Fixed component name

  IS CDC MS SQL S

• Fixed component ID

  5724U7005

Applicable component levels

• R651 PSN

     UP