|
Problem IC95382
|
Status: Geschlossen |
THE DB2MSCS UTILITY FAILS TO CLUSTER A DB2 ESE INSTANCE ON WINDOWS SERVER 2012 |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
On Windows Server 2012, the following error is encountered when
attempting to cluster a DB2 ESE instance using the db2mscs
utility:
"DB21514E The DB2MSCS utility failed to complete because of
system error: "The specified resource type cannot be found in
the image file."
Upon inspection of the trace output file, created via the
"db2mscs -d" option, the following trace points will be seen:
DB2MSCS_GetFileServerInfo fnc_errcode 1813
Create_FileShare_Resource non-fatal_err trace_point 6
15 07 00 00
Create_FileShare_Resource fnc_errcode 1813
DB2MSCS_CreateInstanceProfileDirectory non-fatal_err
trace_point 7
15 07 00 00
DB2MSCS_CreateInstanceProfileDirectory fnc_errcode 1514 |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* DB2 MSCS users on Windows Server 2012 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to 10.5.0.3 *
**************************************************************** |
| Local-Fix: |
Manually cluster the DB2 ESE instance by following the
instructions provided in Appendix D of the following whitepaper
document:
ftp://ftp.software.ibm.com/software/dw/dm/db2/0301nomani/0301nom
ani.pdf |
| verfügbare FixPacks: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Lösung |
Problem Fixed In 10.5.0.3 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 27.08.2013
03.03.2014
03.03.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
