JR63116: IDR FOR MYSQL FAILS WITH LOGFILENOTFOUND WHEN ANY ANY BINARY LOGS DID NOT HAVE ANY GTID EVENT PRESENT

APAR status

• Closed as program error.

Error description

• IDR for MySQL Source fails with  "IBM InfoSphere Data
  Replication will
  stop.com.datamirror.ts.scrapers.exception.LogFileNotFoundExcepti
  on IBM Data Replication could not find the required binary log
  for location..." when any binary log in the list of binary logs
  in the binary directory did not have any GTID event present in
  that binary log.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This issue may affect you if you are using IIDR CDC          *
  * 11.4.0.3-5576 or earlier for MySQL as a source.              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Mirroring ends on error "IBM Data Replication could not find *
  * the required binary log for location..." if binary log in    *
  * the binary directory did not have any GTID event present.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IDR 11.4.0.3-5582 or newer for MySQL source.      *
  ****************************************************************
  

Problem conclusion

• Upgrading to IDR 11.4.0.3-5582 or newer for MySQL source
  resolves the issue.
  

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:

Fix information

• Fixed component name

  IS DATA REPLICA

• Fixed component ID

  5725E3000

Applicable component levels