DB2 - Problembeschreibung
Problem IC92837 | Status: Geschlossen |
DB2MSCS FAILS WITH ERROR "THE OBJECT ALREADY EXISTS" WHEN ATTEMPTING TO CREATE A NETWORK SHARE THAT ALREADY EXISTS. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
On Windows Server 2008 R2 or higher, the following error may be observed when attempting to cluster a DB2 instance via the db2mscs utility: C:\sqllib\BIN>db2mscs -f:db2mscs.cfg DB21514E The DB2MSCS utility failed to complete because of system error: "The object already exists." This error occurs if the network share resource which is being created by db2mscs already exists. Here is the error seen in the corresponding db2trc flow file: db2trc.flw: 1057 23.604670338 sqloCreateNetworkShare error [probe 100] 1058 23.604678826 | sqloFreeSDMemory entry 1059 23.604680038 | sqloFreeSDMemory data [probe 15] 1060 23.604681251 | | sqloSecFreeMemory entry 1061 23.604681251 | | sqloSecFreeMemory data [probe 10] 1062 23.604682464 | | sqloSecFreeMemory exit 1063 23.604682868 | | sqloSecFreeMemory entry 1064 23.604683272 | | sqloSecFreeMemory data [probe 10] 1065 23.604684080 | | sqloSecFreeMemory exit 1066 23.604684080 | sqloFreeSDMemory exit 1067 23.604684889 sqloCreateNetworkShare exit [rc = 0x80071392 = -2147019886] rc = 0x80071392 corresponds to Win32 error: ERROR_OBJECT_ALREADY_EXISTS | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All DB2 MSCS users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V9.7.0.9 * **************************************************************** | |
Local-Fix: | |
Manually delete the network share resource via the Microsoft Failover Cluster Manager interface. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Lösung | |
Fixed in DB2 V9.7.0.9 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC95381 IC96279 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 05.06.2013 06.01.2014 06.01.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.0.9 | |
Problem behoben lt. FixList in der Version | |
9.7.0.9 | |
9.7.0.9 |