IBM Support

JR65202: IDR FOR MYSQL/MARIADB WOULD FAIL WITH UNKNOWN BINARY LOG EVENT TYPE WHEN READING THE FILE HEADER INFO.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When CDC attempts to read the header information that hasn't yet
    been written to the file, the following error appears:
    
    1573	Fatal	2	Scrape/Refresh	true	SHAREDSCRAPE	IBM Data
    Replication has encountered an unknown binary log event type.	c
    om.datamirror.ts.scrapers.mysqlscraper.reader.MySQLLogReader	~!
    ~MySQLNotAbleToRead_Exception~!~kmonaaafhfhcaabdflemgkgbhggbcog
    mgbgoghcoepgcgkgfgdhedljamofijpbahdcjgmacaaaahihaaaaaaaabheaacp
    cphahcgpgehfgdhecpenfjfdfbemcpfeeoffedencpgnhjhdhbgmcngcgjgocng
    dgigbgoghgfgmgpghcodadadfdjdjdg~!~
    	at com.datamirror.ts.scrapers.mysqlscraper.BinaryFileInputStre
    am.readEventFileMetadata(BinaryFileInputStream.java:148)
    	at com.datamirror.ts.scrapers.mysqlscraper.MySQLBinLogEventRea
    der.deserializeEvent(MySQLBinLogEventReader.java:87)
    	at com.datamirror.ts.scrapers.mysqlscraper.reader.MySQLLogRead
    er.readLog(MySQLLogReader.java:226)
    	at com.datamirror.ts.scrapers.cdc.LogReader.execute(LogReader.
    java:394)
    	at com.datamirror.ts.scrapers.cdc.LogReader$LogReaderPipelineJ
    ob.execute(LogReader.java:112)
    	at com.datamirror.ts.engine.component.PipelineThread.runThread
    (PipelineThread.java:217)
    	at com.datamirror.ts.util.TsThread.run(TsThread.java:130)
    	2022-12-13 09:21:58.725
    

Local fix

  • Restart the subscription after sometime.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * This issue might affect you if you are using IDR             *
    * 11.4.0.4-5660 or older for MariaDB source or MySQL source.   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Not available                                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to IDR 11.4.0.4-5661 or newer for MariaDB source and *
    * MySQL source.                                                *
    ****************************************************************
    

Problem conclusion

  • Upgrading to IDR 11.4.0.4-5661 or newer for MariaDB source and
    MySQL source resolves the issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR65202

  • Reported component name

    IDR CDC MYSQL

  • Reported component ID

    5725E30MY

  • Reported release

    B40

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-12-14

  • Closed date

    2022-12-22

  • Last modified date

    2022-12-22

  • 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

    IDR CDC MYSQL

  • Fixed component ID

    5725E30MY

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTRGZ","label":"InfoSphere Data Replication"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B40","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
23 December 2022