|
Problem IC94301
|
Status: Closed |
PURESCALE FAILS TO START MEMBER WHERE ONE OR MORE OF ITS ASSOCIATED GPFS FILESYSTEMS IS SET TO AUTOMOUNT |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
In a AIX DB2 pureScale environment, a member may fail to start
with the following error:
$ db2start
12/18/2012 11:48:09 1 0 SQL1063N DB2START processing
was successful.
12/18/2012 11:48:59 0 0 SQL1677N DB2START or DB2STOP
processing failed due to a DB2 cluster services error.
SQL6032W Start command processing was attempted on "2" node(s).
"1" node(s) were successfully started. "0" node(s) were already
started. "1" node(s) could not be started.
The following error is seen in the db2diag.log at this time:
2012-12-18-11.53.48.188126+060 I19455A370 LEVEL:
Warning
PID : 15204568 TID : 1 PROC :
db2instance
INSTANCE: db2inst1 NODE : 000
HOSTNAME: aixhost01
EDUID : 1
FUNCTION: DB2 UDB, high avail services,
sqlhaCheckMountResourcesOnHost,
probe:4126
DATA #1 : <preformatted>
The mount db2mnt-db2-rs is not online on host aixhost01
Additionally, the state of the resource as seen in the lssam
output is set to "Stuck Online":
Online IBM.ResourceGroup:db2mnt-db2-rg
Control=MemberInProblemState Nominal=Online
'- Stuck online IBM.Application:db2mnt-db2-rs
Control=MemberInProblemState
|- Stuck online
IBM.Application:db2mnt-db2-rs:aixhost01
|- Online
IBM.Application:db2mnt-db2-rs:aixhost02
|- Online
IBM.Application:db2mnt-db2-rs:aixhost03
'- Online
IBM.Application:db2mnt-db2-rs:aixhost04
This issue is due to the filesystem, "/db2" in this case, having
auto-mounting enabled. That is the mount attribute of its entry
within the "/etc/filesystems" file is set to either "true" or
"automatic". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 pureScale users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1.0.4. *
**************************************************************** |
| Local Fix: |
Disable auto-mounting for the filesystem in question by setting
its "mount" attribute to "false" in the "/etc/filesystems" file. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 version 10.1.0.4. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC95861
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.07.2013
02.06.2014
02.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
