DB2 - Problembeschreibung
Problem IC77612 | Status: Geschlossen |
CLIENT REROUTE FAILS DURING HADR TAKEOVER IF IP ADDRESS IS USED IN ALTERNATE SERVER | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
DB2 client fail to reroute connection to alternate server after takeover if IP Address is used in alternate server information. Application reports SQLCODE 1776. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * HADR user using C-client * **************************************************************** * PROBLEM DESCRIPTION: * * DB2 client fail to reroute connection to alternate server * * after takeover if IP Address is used in alternate server * * information. Application will report sqlcode SQL1776. * **************************************************************** * RECOMMENDATION: * * Upgrade to v9.7.5. * **************************************************************** | |
Local-Fix: | |
Use hostname for alternate server | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
Incorrect check in client layer, failed to determinate that server is running HADR. Connections were not rerouted to new primary. Application will report SQLCODE 1776. JDBC ( cli based driver) report error: SQLException messages returned by JDBC/JCC drivers. SQLCODE = -1776 SQLSTATE = Error Message = [jcc][4038][12241][3.62.53] T2LUW exception: SQL1776N The command is not supported on an HADR standby database or on an HADR standby database with the current configuration or state. Reason code = "1". ERRORCODE=-1776, SQLSTATE= DSRA0010E: SQL State = , Error Code -1,776 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 19.07.2011 08.12.2011 08.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |