DB2 - Problem description
Problem IC92793 | Status: Closed |
THE DB2MSCS UTILITY FAILS TO CLUSTER A DB2 ESE INSTANCE ON WINDOWS SERVER 2012 | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * USERS AFFECTED: * * Windows Server 2012 + ESE instance + db2mscs * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fixpack 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 | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Fixed in DB2 Version 10.1 Fixpack 3 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC93098 IC93099 IC95382 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.06.2013 27.09.2013 27.09.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |