DB2 - Problem description
Problem IT35033 | Status: Closed |
CUSTOMERS ENCOUNTERING ASN0569E DUE TO OUT-OF-ORDER REPLICATION LOG RECORDS DURING SAVEPOINT ROLLBACK | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Customers with replication enabled encountered the following error: ASN0569E "Q Capture" : "QASN" : "WorkerThread" : The program encountered an internal error "Missing decode user massive stmt area.". The program will terminate. Investigation has shown that there are out-of-order log records present in the following order (during a save point rollback scenario) : SQLP_LREC_SAVEPOINT_ROLLBACK CDE_LOG_WRITE_ROWS_TO_FILE CDE_LOG_WRITE_ROWS_TO_FILE_END. Therefore it appears as Rollback-Write-End which is not a valid sequence, and causes the error. The Rollback log should occur at the boundary of the Begin-Write-End sequence (i.e. before the Begin, or after the End). This fix will flush the Replicators before writing the ROLLBACK record (adding any code that is needed to accomplish that) in order to make sure the Begin-Write-End sequence is preserved . | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users prior to Db2 v11.5 m4 fp0. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.5.1 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * All users prior to Db2 v11.5 m4 fp0. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.5.1 or higher * **************************************************************** | |
Comment | |
Upgrade to Db2 11.5.5.1 or higher | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.11.2020 01.04.2021 06.04.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |