DB2 - Problem description
Problem IC75302 | Status: Closed |
SEAMLESS ACR IS NOT DRIVEN EVEN IF ALL THE CONDITION FOR SEAMLESS ACR IS TRUE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
In the CLI application against sysplex setup when enableACR and enableseamlessACR set to TRUE in the cfg file, if the fail-over happens after doing the rollback in the application, ACR will be non-seamless even though it should have been seamlessACR. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * CLI users using ACR feature. * **************************************************************** * PROBLEM DESCRIPTION: * * After rollback, forcing the ACR, but CLI fails to driver * * * * seamlessACR, doing non-seamless even though enableACR and * * * * enableseamlessACR set to TRUE in the cfg file. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 9.7.4 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
since all the with hold cursors are closed after transaction rollback, we have to driver the ACR seamless after rollback. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.03.2011 28.04.2011 28.04.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |