Db2

Db2

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only
  • 1.  The job archive for MySQL source via DB2 federation

    Posted 2 days ago

    Hello everyone,
    We are performing data archiving from a MySQL source via DB2 Federated access.

    When we archive the table with a limit of 1,000,000 rows, the job completes successfully in about 10 minutes.
    However, when we archive the entire dataset (3,664,153 rows), the job runs for approximately 1 hour and 17 minutes and ends with the following error:

    [IBM][CLI Driver][DB2/LINUXX8664] SQL20357N
    One or more federated one-phase commit data source sites have failed commit or rollback processing.
    As a result, the transaction outcome might not be consistent across all sites.
    Subsequent SQL statements can be processed.
    Reason code "1".
    SQLSTATE=40003

    According to the report, the job has successfully archived all rows that we counted from the source

    DB2 Version: 11.5.8
    MySQL Version: 5.7.44 (Community Edition)

    Please help me resolve this issue.

    Thanks in advance.



    ------------------------------
    Trieu Huu
    ------------------------------


  • 2.  RE: The job archive for MySQL source via DB2 federation

    Posted 2 days ago

    From the explanation of SQLCODE:

    SQL20357N  One or more federated one-phase commit data source sites have
          failed commit or rollback processing. As a result, the transaction
          outcome might not be consistent across all sites. Subsequent SQL
          statements can be processed. Reason code "<reason-code>".

    Explanation:

    A federated server has sent a transaction commit or rollback request and
    one or more of the federated one-phase commit data source sites cannot
    complete the request. This may be caused by a server failure,
    communication link failure, or other failure. The transaction is not
    completely committed or rolled back.

    The reason code indicates the specific situation.
    1. Commit failure does not involve an update federated data source.

    2. Commit failure involves an update federated data source.

    3. Rollback failure does not involve an update federated data source.

    4. Rollback failure involves an update federated data source.

    5. Commit or rollback processing encountered an error due to db2fmp
       process abnormal termination at the federated server, error '-430'.

    User response:

    Check the administration notification log for details. Compensating
    actions may need to be applied manually at the federated one-phase
    commit data source sites. It may be necessary to contact the system
    administrator for assistance.

    For reason 5, disconnect the application from the federated server, e.g.
    issue a 'connect reset' clp command and reconnect.

    sqlcode: -20357

    sqlstate: 40003



    ------------------------------
    Jan Nelken
    Db2 (LUW) DBA
    HCLTech
    Katowice or Krakow
    +48 783 109 863
    ------------------------------